yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] l7777:
See http://xdaforums.com/showthread.php?t=816271 and http://xdaforums.com/showthread.php?t=818981 for info on the 850 band and euro modems. It does work, but there are hoops to jump through.
[Captivate Android Development] killer23d:
To get the JPP modem to work in 850Mhz, see the bottom part of my thread:

http://xdaforums.com/showpost.php?p=8856818&postcount=1

This as been tested and confirmed working by many members here!

OP should add this to his first post as he made the same mistake I did!! :-)
[Captivate Android Development] Jay120171:
Flashed this and am having no problems using the 'Suggested and tested configuration(Advanced)'.

I was averaging 12-13 MFLOPS on xcaliburinhand's 2.1.2 over Tayutama 1.0.3 lite.

I am now averaging 15-16 MFLOPS with this over Tayutama 1.0.3 lite without any OC/UV tweaking.

A big thanks to the OP for putting this together and making it too easy for a noob like me.
[Captivate Android Development] Dani897:
my setup is no rfs advanced (second from the bottom) but binds disabled.

this from the advance menu as recomended in the op

ext4

ext4

ext4

ext2

ext2

ext2

false

volts are -75 low and -100 high. which to the best of my knowledge was the most stable setting i used in unhelfuls kernels .875 for idle and 1.200 for over clock if the information i've sen is correct. lower may be possible. im gonna try -100,-125 if the kernel lets me.
[Captivate Android Development] joedon3:
Good work on this! I'm stable at -75 and -50. Scored 16.66Mflops on NBench, up to 17.1Mflops on Linpak.
[Captivate Android Development] TheTodFather:
I think I have found the reason why we cant mount to JFS. I went to szupys thread and found what i think is the explanation and that the pit file needs to be changed for using jfs file systems.

Here is a quote I took from sztupy.

Remarks

It seems that formatting dbdata as rfs only works, if you use the 512 PIT file (more exacty it only works if you have used the 512 PIT file the last time you've ticked re-partition in odin). This is probably due to the fact thet the 512 and 803 pit files reserve different space for the dbdata and for the system partition (the 803 pit file reserves 40 units less for the dbdata than the 512 pit file)

So it seems that in order for this to work we need to switch from a 803 pit to a 512 pit because this kernel maybe be precooked with a 803. I'm not running this so I can't test it. Im busy with a few other things but if anyone wants to try this out. This may help. I do know that JFS has been magic for battery life. I plan on using it soon.
[Captivate Android Development] xcaliburinhand:
BLN issue looks to be a simple fix. I will reach out to the dev with the solution.
[Captivate Android Development] SetiroN:
Fixed JFS filesystem support, still looking into BLN and Voodoo Color (I'm a bit overwhelmed with work right now, sorry).

Unsure if Update.zip versions work.
[Captivate Android Development] joedon3:
How can we check to see if Voodoo Color is working correctly? My screen looks great.
[Captivate Android Development] vw671:
Please report back how well JJ4 is working with this Kernel. From personal experience and many xda reports the JI6 modems cause soft reboots with I9000 kernels with extended use.
[Captivate Android Development] ragingclue:
Yeah this kernel is great. With JFS overkill, I'm seeing 16.844 MFLOPS on top of Tayutama's 1.0.3
[Captivate Android Development] arffer:
a=JFS lagfix works now

Advanced JFS lagfix a=jfs is working great on the new version, thanks!
[Captivate Android Development] arffer:
Home button

This kernel is based on X's reorient, which fixes the 'Home' button on I9000 roms.

BUT, my 'Home' button is acting like a 'Back' button now on SetiroN's V1.0.1 running on Tat's SuperliteCaptivate rom.

I don't recall this problem on SetiroN's V1.0.0 kernel
[Captivate Android Development] opcow:
$ mount | grep jfs

mount | grep jfs

/dev/block/mmcblk0p2 /data jfs rw,noatime,nodiratime,errors=continue 0 0

/dev/block/stl10 /dbdata jfs rw,noatime,nodiratime,errors=continue 0 0

/dev/block/stl11 /cache jfs rw,noatime,nodiratime,errors=continue 0 0

$

Thanks!
[Captivate Android Development] opcow:
Home button

Just installed 1.0.1 with jfs and my home button thinks it's the back button.
[Captivate Android Development] TheTodFather:
Hey Setirons, I haven't had a chance to say thanks. You said you where not going to provide support. LOL thanks man. Your far to kind sir!
[Captivate Android Development] TheTodFather:
hey opp cow. do you still have 3 button fix recovery? Odd..seems if that happend their should be a few other little things that may be reversed. If thats all you can just remap the buttons!

OPcow what ROM are you on ???
[Captivate Android Development] SetiroN:
I'm sorry guys, while working on the BLN I replaced the wrong file and the keypad ended up switched - the corrected version will be up shortly.

EDIT: Files UP.
[Captivate Android Development] MikeyMike01:
Can you elaborate?
[Captivate Android Development] crazililazn:
Hmm if you use the overkill lag fixes. And disable the bind data to dbdata, will u still get the "running out of memory" message with the ext2 loops?

EDIT: OMG reoriented kernel 2.1.4 has correct headphone logic now!!! I'm sure Setiron is working on getting it into the next release. CANT WAIT!!! :3
[Captivate Android Development] bts0uth:
Anyone got all ext2 lagfix to work? I tried going from ext4nj to ext2 and it got stuck in a boot loop. Luckily going back to ext4nj fixed it and I didn't have to reflash.

Also, cant wait till a 1280 version is out. 1360 keeps freezing randomly so im stable on 1200
[Captivate Android Development] Shammyh:
Is there any chance we can get separate GPU control in an upcoming release?

With Eclair, Unhelpful figured out how and his code is still on Github: https://github.com/Unhelpful/linux-galaxy/tree/unhelpful-v1.7. Maybe someone smarter than me can figure it out.
[Captivate Android Development] rusty815:
i installed this on several different roms, couldnt get the camera to work, the camera freezes when i try to use it with v1.5 and i have to reboot to be able to use my phone again. dont have this problem with v1.4.3

also, i would like a 1280MHz version as well, i get freezing problems with 1360MHz as well, and i would like to take advantage of ext4 with no journaling (not in v1.4.3)
[Captivate Android Development] RKight:
I couldn't use v1.5 with either Perception 5 or 7. I tried flashing over 1.4.3, as well as doing a one-click to JF6 and starting fresh. It makes it to the boot screen, then I get a force-close vibration and get stuck in a boot loop. I've tried both with and without the lagfix enabled, as well as trying with tweaks enabled and disabled. Nothing I do is letting me use this kernel. I guess I'll just have to stick with 1.4.3. FWIW, I'm using the 1280 version of the 1.4.3 kernel, so if 1.5 runs at 1200 by default, I shouldn't have any issues with it.
[Captivate Android Development] bts0uth:
You were using XT version weren't you? I have found normal version doesn't freeze the camera but XT (and CogKernel2) do have camera problems. It has to do with config optimizations I believe
[Captivate Android Development] MikeyMike01:
Apparently it breaks the normal microphone on calls.

Sent from my Captivate.
[Captivate Android Development] SetiroN:
You have to enable it from CWM Tweaks.

Slightly higher performance/smoothness at the cost of battery life and potential instability, requiring lower UV settings.

I'm afraid there's no magic involved, just plain luck. :)

Of course it does: that file is a trigger. As soon as it's set to 1, the frequency table gets updated and the file goes back to 0 so that you can update it again.

That means you haven't (correctly?) enabled high frequencies.

Hope 1288 and 1344 are alright.

Exactly the same, also note that because of the issues most people seem to have above that voltage (forgive me for writing this way, I don't mean to be rude, just want people to notice)

on v1.5 14xxMHz voltage went back to 1.3v, lower your UV accordingly

You're welcome, better safe than sorry. :P

ext2 offers no advantage (even theoretically) over ext4nj, but Hardcore's tests have demonstrated an higher chance of file corruption. I suggest not to use it.

You already have separate GPU clocks, there'd be no way to reach 1.4+GHz otherwise. That doesn't mean you can set it to whatever frequency you want, only integer dividers are available so you can only set it at stock clocks every 1200MHz, every step in-between has an odd GPU freq which can work for some but not for others.

No problems here plain or XT? Anyone else?

v1.5.1 OUT

DELETE USER GENERATED SCRIPTS IN /system/etc/init.d/ BEFORE UPGRADING

- optimized RAM utilization (minfree settings)

- optimized frequency jumps for better battery life

- workaround for the highest frequency step being sometimes briefly used during bootup and recovery operation

- effectively set 1200MHz as the default frequency

- corrected wrong display of highest frequency in Quadrant

- added frequencies scheduler script in the CWM zip package with a visual aid

- reorganized performance levels with a few additions:

1600MHz CPU	200MHz GPU	1350mV
1552MHz CPU	194MHz GPU	1350mV
1504MHz CPU	188MHz GPU	1350mV
1464MHz CPU	183MHz GPU	1300mV
1456MHz CPU	208MHz GPU	1300mV
1400MHz CPU	200MHz GPU	1300mV
1344MHz CPU	192MHz GPU	1300mV
1288MHz CPU	184MHz GPU	1300mV
1200MHz CPU	200MHz GPU	1300mV
1000MHz CPU	200MHz GPU	1275mV
800MHz CPU	200MHz GPU	1200mV
400MHz CPU	200MHz GPU	1050mV
200MHz CPU	200MHz GPU	950mV
100MHz CPU	100MHz GPU	950mV

One of the various internal clocks regulates the GPU's as well as other internal components' frequency. Lower clocks have a chance to cause instability as well, so you might want to try an higher step with the GPU closer to stock (200). Those internal components play mostly a role in benchmarks like Linpack, although actual performance during normal use relies predominantly on CPU clock.

Sorry the forum logged me out, give me a few minutes to re-upload.
[Captivate Android Development] crupp:
going to try 1.51 couple of questions. I have not done this before so i appologize for the noob questions.

Does the .tar7z go in the phone area of odin?

Should I diable the lag fix in my current ROM (assonance 3.0)?

Does installin this Kernel wipe my data?
[Captivate Android Development] existz:
Nice to have 1.28 back :) ... hopefully this time I can boot
[Captivate Android Development] shaolin95:
WOW, I doubt my phone takes all that but I am sure trying...this after I spent 3 days testing 1.5 and my new rom and themes to make sure before flashing my final config! LOL
[Captivate Android Development] KeeganX:
Is anyone else unable to download 1.5.1 from the download link?
[Captivate Android Development] crupp:
I can't. get not a valid link message
[Captivate Android Development] shaolin95:
He is reuploading...he said he had some issues .
[Captivate Android Development] crupp:
couple of questions: first time I am using his kernels. Sorry if these have been previosuly addressed.

1. put .tar file in phone seciton of Odin?

2. Does this wipe my info?

3. SHould I disable the lagfix in my current ROM (assonance 3.0)?

thanks for the help
[Captivate Android Development] shaolin95:
1. Yes or use the CWR file which you can flash from recovery itself.

2. No but ALWAYS create a back up just in case.

3. Not needed.

I am about to break my F5 key in desperation! :D
[Captivate Android Development] lpsi2000:
LOL, I was saying the same thing. Here we go again. I hope I don't have start all over again, but I know better:)
[Captivate Android Development] shaolin95:
I feel like a junkie here desperately pressing F5 ! LOL
[Captivate Android Development] DAGr8:
its been along time he said that now

lol

btw shaolin you d be surprised with decent kernel most hummingbird can take 1.6
[Captivate Android Development] shaolin95:
Yeah I have read that they should be able to handle that so cross my fingers this is that decent kernel! :D

At 1600Mhz it would just be a dream! Like having a next year phone already.
[Captivate Android Development] DAGr8:
tbh at 1.46 phone is freakin flying the rom doesnt matter so much anymore ,

good gps and nice theme is all that matters once we can run Oced cpu and GPU at stock clock ..

edit : right click / reload ... F5 .... right click/ reload ... F5 I feel in boot loop mode
[Captivate Android Development] shaolin95:
Thats true...even at 1.4 I was already now focusing on themes since I finally got a pretty freakin good GPS with my current ROM.
[Captivate Android Development] DAGr8:
OP should mention if you make the /system/etc/init.d/ folder R/W and save settings with the UV app itself it will delete those 2 lines :

echo 0 0 1 0 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table

echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/update_states

Edit : I wonder how many ppl have reported link not working to the admins ( lol )
[Captivate Android Development] shaolin95:
I need to go out and stop staring at my screen...just pushing for 1460 in the mean time! lol
[Captivate Android Development] lpsi2000:
Nice trick, how is that ROM you are using?
[Captivate Android Development] DAGr8:
you know what they say light a cigarette and the bus will arrive , well there you go we are both away now so seti will update thread
[Captivate Android Development] shaolin95:
My favorite ROM so far and finally usable GPS. Its still new but I like it a lot.
[Captivate Android Development] lpsi2000:
Where are you located? do you have any dropped call issues with JK3 modem?
[Captivate Android Development] shaolin95:
Utah and no drop calls at all.
[Captivate Android Development] lpsi2000:
okay, this might have been an issue with Axura ROM and that modem. I waiting for this kernel to give that ROM a spin:D
[Captivate Android Development] Cezar`:
Links are down... :(
[Captivate Android Development] shaolin95:
Coolio but it seems Setiron went to sleep LOL

Where in the World is Setiron SanDiego?
[Captivate Android Development] lpsi2000:
LOL, that would early to go sleep in San Diego. May be he needed a power nap
[Captivate Android Development] shaolin95:
Sorry I had a typo , just fixed it...it was a reference to an old game I use to play in my C64! lol

GameLink
[Captivate Android Development] slider2828:
I love that game... Carmen San Diego!!!

It was a show too... super awesome trying to find the bad guys and answer geological and landmark's of the world questions....

Awesome game, played on my x286....
[Captivate Android Development] slider2828:
No drop calls but i am using Doc's JK3 i9000m kernel and the gps is horrendous.... JK3 as well... I might try assonance...
[Captivate Android Development] shaolin95:
It was horrible for me too with the last perceptions so I was like not even paying attention to it until I got Assonance. Let me know!
[Captivate Android Development] bts0uth:
Lol I hope SetiroN is alive! Maybe hes gonna go straight to 1.5.2 and skip this one lol
[Captivate Android Development] shaolin95:
He is going for 2Ghz and unlocking a hidden second core! Ok maybe not but gosh, you are killing us ! :D
[Captivate Android Development] crazililazn:
LOL, i just hope he is taking his time incorporating the new reoriented kernel which fixes the headset mic/button issues :]
[Captivate Android Development] shaolin95:
Thats it I am sending a rescue team to locate Setiron RIGHT NOW!
[Captivate Android Development] MikeyMike01:
The suspense is killing me!
[Captivate Android Development] DAGr8:
I died 2-3 pages ago

/me plays dead
[Captivate Android Development] MikeyMike01:
HE'S ONLINE!!!!!

zomg zomg zomg zomg zomg zomg

Between this and Cataclysm just 2 hours away, I think I might have a heart attack.
[Captivate Android Development] shaolin95:
I was to reflash...I need to hold now ! lol
[Captivate Android Development] timur525:
this broke my phone.... if you can't handle >1280 flash back to a older version or u'll get ****ed, like me... here's my story

Last Saturday, my house, playing Call of duty...

My thoughts: Lets check the XDA app for new stuff.

2 mins later: Oh look! New Setirion Kernel! Gotta flash this real quick!

2 mins later: Damn! 1460 mhz! This is crazy!

1 min later: Oh no! Everything is fcing!

1 min later Lets turn it off for the night

9hours later: Oh goody! Its all better!

(Worked fine all day)

Next day, at school: Phone won't boot What??

After i got home: Plug this ***** in the charger? WHat? now it boots? FTW?!

30sec later: WTF! EVERYTHING FC's!

5 hours later: ill flash back to stock.

5mins later: it worked

(booting)

1 min later: WTF? E:can't mount dev/stl10? WTF IS THIS?!

30 mins later: Try a diff firmware.

5 mins Later: Yeey! It worked! Wait, WTF! STILL CANT MOUNT!!!

5 mins later: Lets warn the good people on the XDA forums.

So there you have it folks, i'm ****ed. Any suggestions? i started a thread butdidnt get **** for an answer...
[Captivate Android Development] shaolin95:
Make that too...he must be uploading with dial up! :D
[Captivate Android Development] DAGr8:
he stayed online about an hour and left :cool:

lol were hopeless , IM goin to bed , thx foro the teaser SETIRON !
[Captivate Android Development] bts0uth:
Can't wait till the new version is posted. Even though he teased us today he is still awesome. Im sure we will see something nice tomorrow.

Posted from my Captivate
[Captivate Android Development] moosefist:
Am i seeing this right? the new version scales up to 1.6?

I might have to give it a shot :)
[Captivate Android Development] bamonkey:
had to reboot to be able to make changes in init.d folder scripts. edited s99 script per instructions in OP but maybe i dont understand correctly. am i only able to change the OC that is allowed at boot? i tried enabling via the s99 script per instructions in the OP but changing from 1.2 to 1.4 does not hold as my cpu/temp widget still show 1.2. will try to change boot to 1.4 but that will suck since if it DOES hang ill have to flash the kernel again. im probably doing it wrong but hey im trying to read and follow directions here :)

edit: just as i feared, will need to reflash..then again my phone might just not like to OC over 1200..
[Captivate Android Development] amtrakcn:
looking forward to a version that solve wired headset issue:p
[Captivate Android Development] yokozuna82:
Sorry for this question I'm sure it's been answered

I tried to install it via Odin but the.

.zZ wont let me put it in the karnel area

How would I install this?
[Captivate Android Development] bamonkey:
.7z you mean right? Its a 7 zip archive so you have to extract it first then you should see the .tar file you can put in the kernel area
[Captivate Android Development] InobleI:
Extract it first
[Captivate Android Development] yokozuna82:
Cool thanks ill try it
[Captivate Android Development] mrxjhsnx:
Just flashed with Axura RC1 and seems to be working fine so far, going to tweak the uv settings next

Edit- So far 1400 is fine with uv tweaks waiting for more testing before i go higher
[Captivate Android Development] SetiroN:
I've updated the OP with detailed instructions, hope to finally make it clear.
[Captivate Android Development] Banditlol:
Love your work, long time fan first time question, well clarification, but by manually changing the values of the states_enabled_table and the update_states the phone actually starts running at the higher frequencies at that time? no reboot is needed?
[Captivate Android Development] SetiroN:
That's correct.
[Captivate Android Development] bamonkey:
Hero points :D I didnt actually realize you could choose to NOT have certain frequencies, i was just enabling all 1's up to the desired selection:o

Very good write up i think i know exactly how this is all done now.

Again thanks for everything as always!
[Captivate Android Development] Banditlol:
awesome thanks
[Captivate Android Development] crupp:
Can this just be added, without any additional tweaking,and still realize performance increases?
[Captivate Android Development] shaolin95:
So to clarify, do you think in order to have a decent shot at 1.6Ghz..should I enable all freq for a smoother transition or better yet only the ones with GPU at 200mhz since my phone does not like anything that messes up with the GPU so like 1000, 1200, 1400, 1600 ?
[Captivate Android Development] bts0uth:
Wow thank you SetiroN. Amazing work.

1400 freezes for me on quadrant graphic tests, 1344 is working great though.

Posted from my Captivate
[Captivate Android Development] shaolin95:
Getting max speed is complicated because at least on my system I have to keep checking until I find voltages that are good for both GPU and CPU...many hours :eek:
[Captivate Android Development] DAGr8:
THX a lot will test in afew hours need m phone for now .. or maybe not :eek:

lol
[Captivate Android Development] shaolin95:
Not having much lock so far so I am going to reflash from zero since my late night flash was a bit shaky to begin wiht.
[Captivate Android Development] Cezar`:
I cant use anything newer than 1.4.1

I have huuuge problems with Setiron's kernels starting with version 1.4.2. I still run 1.4.1 at 1.28GHz and it works amazing. But from 1.4.2 i had:

- ROM locks

- not rebooting in recovery or download after issuing the command in adb on the pc

- not turning off completely, after turning off I had to pull out the battery to turn it back on.

I dont understand whats the problem.. I did not have any additional frequency enabled when these issues were happening.
[Captivate Android Development] shaolin95:
This is a guess on my part but it seems each kernel stresses different components even at the same speeds so perhaps your phone is not a good OCer. Mine for example, anything that touches GPU speed messes my phone up. And for other things I struggle to find a balance with the voltages as for example, 1400Mhz -50 was great for my GPU running Neocore looping forever but my CPU would freeze running the stability test. My CPU needed -0 to run fine but then the GPU will lock with Neocore....so finding the middle ground with my phone is a pain.

Each phone seems to be a world of its own making it hard to troubleshoot or offer assistance when it comes to OCing.
[Captivate Android Development] Cezar`:
From what batch is your phone from? Mine is from 1006. You can find it below the battery.
[Captivate Android Development] lpsi2000:
Exactly, I also spent countless hours doing the same thing.
[Captivate Android Development] eSPyeL:
solution for not mounting /system rw

SetiroN,

I have a simple script to place in init.d that makes it unnecessary to mount /system as rw. The script checks for the existence of /data/data/com.darekxan.voltagecontrol/files/S_volt_scheduler

If that file exists it simply runs it. If it doesn't exist it's sets all the defaults however you want. Using this method the VoltageControl app doesn't need to write to /system/etc/init.d.

This is for your 1.4.3 kernel so it will need to be tweaked for the newer kernel.

#S80volt_schedule

#!/system/bin/sh
VOLTSCHED="/data/data/com.darekxan.voltagecontrol/files/S_volt_scheduler"
if [ ! -e $VOLTSCHED ]; then
#set UV
echo "0 0 0 0 0 0 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
#set scheduler for stl, bml and mmc
for i in `ls /sys/block/stl*` /sys/block/bml* /sys/block/mmcblk*
do
echo "noop" > $i/queue/scheduler
done
else
`$VOLTSCHED`
fi

I'm adding this to my rom so it isn't OC or UV by default. The user will have to use the VoltageControl app to enable it.
[Captivate Android Development] bts0uth:
Mines 1006 and I can O/C to 1344 and its perfectly stable. 1400 however freezes on quadrant graphic tests.

Posted from my Captivate
[Captivate Android Development] lpsi2000:
It looks like the new kernel already have this stuff layed out already
[Captivate Android Development] existz:
Same with mine, its 1006 and anything over 1.3ghz it doesn't like.. I still think we need just a plain 1.28-1.3ghz version .. something for us to just be able to flash and go on with it.

Maybe a "Lite" version