yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] eSPyeL:
From the Changelog:

mount /system R/W - could be dangerous, but solves script creation issues

My method solves the script creation issue without having to mount /system R/W. It also sticks through reboots.
[Captivate Android Development] shaolin95:
First try at 1.6Ghz....instant lock! lol

Trying a different voltage just for kicks.
[Captivate Android Development] l7777:
I'm going to add a +1 to using his method as a solution. If something is going to be dangerous, I'd rather have to do something myself to initiate said dangerous action. I simply created a script that would mount the system as RW when I wanted to make a change. As it stands, we now have to do something to our phones after every reboot to put the back into a "safe" state. If someone can't figure out how to mount the system as RW, they probably shouldn't be messing around overclocking or undervolting.
[Captivate Android Development] lpsi2000:
Well it does not look like I have any script creation issues with Assonance 3.1. And also the it looks like the frequency scripts is also created separately from the voltage scripts. Some of the stuff mentioned in the changelog seems to have been incorporated in the kernel package (especially if you flashed kernel separately from the ROM:D). I think that is why I don't have issues with the script. Take a look at the kernel packages
[Captivate Android Development] johan8:
Headset issue has been fixed in xcaliburinhand re-oriented

Is it also support in 1.5.2 ?

And how to disable OC to 1.3G and above ?

They are not stable in my Captivate.
[Captivate Android Development] SetiroN:
Let me quote the changelog:

The default frequency is 1200MHz, higher frequencies are disabled unless you follow the procedure described in the OP.

That's strange. Are you sure you're not using the XT variant? Have you tried disabling optimization scripts from CWM? I assume v1.5.2 still gives you such problems? Have you ever reflashed your ROM since having them?

Why? I believe the personalization capabilities of v1.5 should make everyone happy, I really can't see a reason why I should go through the trouble of compiling a variant to do something already possible because somebody is too lazy to switch a 0 and a 1 to disable 1.2GHz and enable 1.288. :p

Much appreciated. :)
[Captivate Android Development] junktzu:
@SetiroN

Hey I just wanted to say thanks for your hard work and a double thanks for the detailed explanation of how to get everything setup! Expect a donation soon! ;)

EDIT: Conf. #88X96227Y4787102R
[Captivate Android Development] johan8:
Thank you so much !!

;)
[Captivate Android Development] shaolin95:
1007 here

Having issues booting up with Voltage settings not resetting from my last failed attempt...this is going to be hard lol
[Captivate Android Development] slider2828:
Hey Shaolin, just tried Asonance 3.1 and the GPS is awesome.... Wayyy better than any DocRom or Perception 2+ GPS fix.... Thanks for the tip!
[Captivate Android Development] SetiroN:
Boot in recovery, adb root, adb shell, rm /system/etc/init.d/S_volt_scheduler ;)
[Captivate Android Development] shaolin95:
You are welcome mate..not sure how the triple fix combo works but it does lol

I lost you there...boot in recovery then use ADB from windows to enter those commands?

Its odd cause the s99_volt.sh file is there but it ignores it when booting back up.
[Captivate Android Development] bts0uth:
1.5.2 is working great. Thank you so much SetiroN.

I have all tweaks enabled and per hardcores suggestion im only using ext4nj on data and rfs on the others.

Not sure about battery yet seems to be draining a little fast but ill wait a few days before I judge it

Posted from my Captivate
[Captivate Android Development] lpsi2000:
I am on 1007 too and it seems to be working okay for me but I now going up 1.4

I have been using this ever since you been building kernels. The funny part is I discovered this by accident.:D

I will be testing GPS too so I am looking forward to the same experience you are having.
[Captivate Android Development] slider2828:
Hey guys maybe a quick question, I understand setting the cpu freq, but can you say enable replace stock frequencies like 800 then 1000 to 1200 then 1280?

Or is it better keep 1000?

-Ken
[Captivate Android Development] lpsi2000:
You need to keep them, because you have the remember you want to conserve battery when you are idle or when the phone does not need the juice. I don't see a point on removing the lower frequencies especially if that is where the processor leaves most of time.
[Captivate Android Development] shaolin95:
Do you mind explaining to me how that ADB thing Setiron told me is done? :)
[Captivate Android Development] lpsi2000:
Sure::p

Boot to recovery mode

Plug the phone to the USB hooked up to your PC

Go to your PC

Goto Command Prompt

Go to the location where the ADB stuff located on your PC

type: ADB root

wait for 1 minute

type: ADB Shell

from here on you can navigate to the location and make your modification.

you can also use ADB to push and pull files

I hope that helps.
[Captivate Android Development] shaolin95:
Sorry I made you do that and I figured it out! lol

Still, shouldnt I be removing the s99_volt.sh file instead or I am I missing something?
[Captivate Android Development] lpsi2000:
There is no S99_volt.sh with the new kernel. There is an S_vol_scheduler and s99_freq_scheduler.sh. Unless you were placing that one yourself there. I use the Voltage app to make changes to S_volt_scheduler. I manually edit S99_freq_scheduler.sh to enable various frequencies.

Also all of the research we have done with version 1.5 still applies with 1.5.2. Meaning the voltage seems to be same for each frequencies leading all of the way to 1.456. Which is good thing for some of us who spent great deal of time getting it right with 1.5
[Captivate Android Development] shaolin95:
ah so no need to rename the file to S99_volt.sh....that explains why it was not changing for me at boot to what I wanted LOL

For anyone OCing now...preliminary tests for me seem to indicate that enabling all steps prior to the speed you want helps the ocing. I was having issues getting 1400Mhz stable and by enabling the steps between 1400 and 1200, I finally got it.

Can someone confirm if they have the same issue adding a wall paper using gallery when the CPU is not stable or is that just one odd behavior by my CPU? I love it cause its a quick test of stability for me lol
[Captivate Android Development] bts0uth:
My handset and speakerphone volume is really low. Is the kernel causing it or my rom? Even at max volume I have to tell everyone to speak up

Posted from my Captivate
[Captivate Android Development] chrism0483:
Hey guys I'm still learning a lil and a lol unfamiliar with these different versions. Would anyone mind giving me some info in what version I should flash and how I would set the values or whatever u need to to optimize the performance. I am currently using axura rc1. I would really appriciate someone taking the time to lend me a hand and put me on the right direction. I want to thank anyone who can help ahead of time you have no idea how muxh I would appriciate the guidance/help
[Captivate Android Development] shaolin95:
I think mine is going to be stuck at 1.4Ghz...not that I am complaing about 400Mhz of free extra power and that deserves and extra donation next Wednesday for da man here!

Anyone having any luck with the 1.6Ghz? I am beginning to feel that it may not be as easy to achieve as previously thought.
[Captivate Android Development] slider2828:
Can you post your hard work settings? hahaaha.....
[Captivate Android Development] DAGr8:
yea for some reason the echo script didnt work for me ???

did it manually for testing non XT gives me : 1504 with linpack 20 at UV set at 0 phoen will freeze if I go in gallery ,,, just like it did in 1.43 @1460 so again I suspect GPU issues

XT gives me :1504 with linpack 20.5 at UV set at 0 phone will freeze if I go in gallery ,,, just like it did in 1.43 @1460 so again I suspect GPU issues

SetiroN : is it possible to know witch (of the higher ) frequencies has GPU over or underclocked ?
[Captivate Android Development] shaolin95:
LOL why not!

All speeds are active for me.

1600MHz CPU	-25

1552MHz CPU	-25

1504MHz CPU	-25

1464MHz CPU	-25

1456MHz CPU	-25

1400MHz CPU	-25

1344MHz CPU	-50

1288MHz CPU	-50

1200MHz CPU	-50

1000MHz CPU	-100 (not sure why I left it like this but it got me 1.4 stable so I aint changing it but probably should be -50)

800MHz CPU	-75

400MHz CPU	-100

200MHz CPU	-100

100MHz CPU	-100

With those settings I am able to activate 1600 but if I it will freeze if I try to open the Gallery right away. I am going to try -50 for 1600 or 0 to see which way it wants to go.
[Captivate Android Development] DAGr8:
well 1.50 was treating me better running at 1460 phone was flying ...

now im at 1456 .. phone doesnt feel as fast and linpack are a bit lower so must be somtihgn else .. seti ???
[Captivate Android Development] lpsi2000:
Yep, 1.4 seems to be only stable frequencies for us on model 1007. I was able to get 1.46 to run but it was not stable.

Based on my observation, it seems as anything I can't UV won't be stable. If you can only use it at 0 and UV freezes then that frequency will not be reliable.
[Captivate Android Development] shaolin95:
Mine handles 1600Mhz better than 1456 (instant crash and errors) for example...mine just does not accept pretty much anything that touches the GPU it seems...oh well, I am happy anyway lol
[Captivate Android Development] lpsi2000:
What did you stet your uv to for 1.6
[Captivate Android Development] DrCruelty:
I flashed 152 and now it freezes in recovery. Default 1200 untouched. Works fine in OS, benchmarking ect. Consistently freezes in recovery only. Haven't been able to apply lagfix as a result. Any suggestions?
[Captivate Android Development] shaolin95:
So far I have tried -25 , -50 and 0 but the ones below also play a role so it is going to take a while to test all possible combinations :-)

I assume that just like a normal CPU if it does not restart automatically at least I am not yet too low on voltage.
[Captivate Android Development] mikewong27:
Flash over [ROM][Spaceman] aospMOD v 1.1 (11-26-10)?

Hi All,

I just installed the [ROM][Spaceman] aospMOD v 1.1 (11-26-10) few days ago. I'm using the kernel 2.6.32.0 jetaek.lee@sept-11 kernel with baseband I897UCJI6. I'm also using the "One Click Lag Fix" on my captivate. I'm wondering if it's safe to flash this kernel on top of aospMOD v1.1? Will it erase all of my data? Do I need to disable the "OCLF" first? Please let me know. I've been waiting to OC my captivate for a long time.

Thanks,

Mike
[Captivate Android Development] slider2828:
Wholly crap seriously? WOW.... I actually use 3d Gallery, so yeah it ain't going to fly with me.... My freaking file system blew up and it was getting stuck on scanning media. SUCKS!! So now back to JF6 and loading all that crap....
[Captivate Android Development] shaolin95:
Yeah this seems arent as tuff as my pc with OCing...too many crashes and is restoring time baby lol
[Captivate Android Development] Peaster111:
+1 ...same here
[Captivate Android Development] slider2828:
Did you run the super curio rfs fix? All else time to redo everything as the infamous STEP #3 style LOL
[Captivate Android Development] DrCruelty:
I was previously running 1.4.3. Thanks to kernal flashing being quick, I flashed back to 1.4.3 and all is normal again.
[Captivate Android Development] SetiroN:
Now that you make me look at it volume does sound a little low, could be related to the headset fix...

Flash the latest version and read the OP thoroughly, everything should be clear enough.

Start by booting recovery, select the suggested lagfix and enable all tweaks.

When the conversion ends, install Xan's Voltage Control and lower voltage by 50mV, check if you're stable (it should be) and you're done. For more advanced settings, read. :p

There are no issues with that ROM as long as you flash JK3 modem aswell, your data won't be erased and yes you do have to disable OCLF first.

I'll look into it.

Guys, you know for a fact I don't mind helping out, but you should really check out the OP before asking questions, I spend a lot of time updating information and you make it feel pointless. The whole frequency table is actually repeated twice.

v1.5.3 OUT

- /system mounts as RO

- added workaround script inside the update.zip to execute voltage control boot settings directly from the program's data dir, eliminating the necessity to remount /system

- corrected frequencies script, should now work on every ROM

- only available as a CWM update.zip to make sure everyone has working init scripts

- increased default voltages for 1456-1464MHz to 1325mV, 1504-1544MHz to 1375mV and 1600MHz to 1400mV, regulate your UV settings BEFORE upgrading

- gained an additional MB of RAM thanks to kernel size optimization
[Captivate Android Development] ReedX50v:
Thank You. I can't ever finish cutomizing my rom before another release is out. ;)
[Captivate Android Development] shaolin95:
So I was using the tar file to add it to the ROM I flash to avoid flashing one kernel then the update.

Do you think I need to flash the ROM and boot then restart in recovery to upgrade to 1.5.3 and that should be just as good?
[Captivate Android Development] slider2828:
Great timing!!! I just loaded my bare Asonance Rom!!! Putting this into it now!!! RAWR!!!
[Captivate Android Development] mikewong27:
"There are no issues with that ROM as long as you flash JK3 modem aswell, your data won't be erased and yes you do have to disable OCLF first."

Thanks a lot for your reply.

Do you know where I can find the JK3 modem?
[Captivate Android Development] peachpuff:
SetiroN will you be switching to the voodoo5 lagfix in the future?
[Captivate Android Development] ReedX50v:
Original post.
[Captivate Android Development] mikewong27:
Thanks a lot.

Mike
[Captivate Android Development] jdbeitz:
1600mhz... wtf?!

This is getting nuts lol
[Captivate Android Development] DAGr8:
god im awefull , it was too obvious 1600 mhz cpu 200 mhz gpu

duh
[Captivate Android Development] mikewong27:
flashing setiron_v1.5.3xt_cwmupdate.zip

HI All,

Just flashed the setiron_v1.5.3xt_cwmupdate.zip file and JK3 modem file using ROM Manager. It went okay. But when I flashed setiron_v1.5.3xt_cwmupdate.zip was it supposed to ask me to setup lag fix?

Mike
[Captivate Android Development] slider2828:
What scheduler are you using?

Damn also now one crash from the OC and my f...ing thing freezes on Media Scan....
[Captivate Android Development] shaolin95:
I always use noop...have not tried others for stability..not sure if that helps
[Captivate Android Development] crazililazn:
I cant even get the 1.5.3 kernel to boot... always crashes shortly after booting.... -_-

And i reset all my UV settings before too...

It even crashes in recovery.... wtfreak... O.o
[Captivate Android Development] DAGr8:
hmm cant get the echo script to work ...

couldnt on 1.52 either ... but worked fine on 1.5 // ??? :confused:
[Captivate Android Development] slider2828:
Yeah I have an issue with it too sometimes... It currently crashes on Media scanning if the screen is locked, but ok if I unlock the screen before it starts scanning hte external card....

My POS phone won't even go over 1288 without crashing... RAWR!!!
[Captivate Android Development] crazililazn:
Even if i unlock it, it still freezes :/ Well, weird, even when i flash back to 1.5, its happening too. Guess its time for a restore.

Just a quick question, i know it may be a bit off-topic, but, which rom is better? Axura or Assonance? looking for some opinions since its not my cup of tea having to restore too often x.x
[Captivate Android Development] slider2828:
I am in the same boat..... I like Assonance, the GPS works much better.... No real text on Axura though...
[Captivate Android Development] shaolin95:
I prefer Assonance but thats a personal choice of course.
[Captivate Android Development] crazililazn:
Hmm, must be a bug in the kernel then :[ I'm sure Setiron will get working on a fix soon enough :]

And haha, i heard the new Axura might come out in like 4 hours, so i will wait and see what it has first. But yeah, it would be nice to have my GPS actually working for once X.X
[Captivate Android Development] rusty815:
i cant get 1.5.3 and 1.5.2 to work, 1.5.2 always causes my rom to freeze and 1.5.3 gives me an error "android.process.acore stopped working" or something like that, i dont know if that is something serious or not.
[Captivate Android Development] mod777:
t-x till meltdown:eek:
[Captivate Android Development] lpsi2000:
Everyone who is having issues with booting this, start fresh by flashing stock then ROM and finally kernel. With changes made with this release, it does not seem boot well for me either if I just flash it over existing ROM.

But I am thinking 1.4 is going to max I can get with my phone. With the latest version I was able to UV it -25 and it ran well until for while. If you push too much and the temperature get > 42 degree Celsius, it will freeze.

So increasing the voltage just so I can decrease only put us right back to where we were before. It is the same as setting it to 0 with the previous version:p
[Captivate Android Development] junktzu:
I didn't have any trouble upgrading directly from 1.5.2 but I didn't have any scaling and UV settings loading on boot either.
[Captivate Android Development] crazililazn:
I upgraded from 1.5 to 1.5.3 without any scaling or UV settings either. I had deleted/reset them, before upgrading. :/
[Captivate Android Development] mikewong27:
Which file to use

I'm wondering what is the difference between "setiron_v1.5.3xt_cwmupdate.zip" and "setiron_v1.5.3_cwmupdate.zip"?
[Captivate Android Development] junktzu:
I believe the xt version has more aggressive voltage settings that aren't quite as battery friendly as the non-xt version.
[Captivate Android Development] mikewong27:
I see... I went ahead flashed the non xt version. By the way, any idea on how to apply the lag fix on this kernel?
[Captivate Android Development] junktzu:
Reboot into recovery, select advanced SpeedMod ULK features, select Lagfix options then select lagfix of choice.
[Captivate Android Development] mikewong27:
Oh... I see... thanks a lot for this info. I really appreciate this...
[Captivate Android Development] slifer315:
or you could even merge the kernel cwm zip with the rom zip, placing files into the correct folders and flashing only one thing like I do.
[Captivate Android Development] lpsi2000:
I flash too many rom and kernels, so I don't want to repackaged them every time something new comes out

I also think something is going on with the latest kernel. It is freezing on me in recovery mode when I went to tweaks menu made changes there, then went to work on my lagfix then it froze. I don't know but I am going to try previous version (1.5.2).
[Captivate Android Development] eSPyeL:
boot issue

I've had some problems booting with 1.5.3. I just rebooted and it got stuck on the boot screen. I was able to get adb to run logcat...

W/AudioSystem( 4205): AudioPolicyService not published, waiting...
I/ServiceManager( 4205): Waiting for sevice media.audio_policy...
I/ServiceManager( 4205): Waiting for sevice media.audio_policy...
I/ServiceManager( 4205): Waiting for sevice media.audio_policy...
I/ServiceManager( 4205): Waiting for sevice media.audio_policy...
I/ServiceManager( 4205): Waiting for sevice media.audio_policy...
W/AudioSystem( 4205): AudioPolicyService not published, waiting...
I/ServiceManager( 4205): Waiting for sevice media.audio_policy...
I/ServiceManager( 4205): Waiting for sevice media.audio_policy...
I/ServiceManager( 4205): Waiting for sevice media.audio_policy...
I/ServiceManager( 4205): Waiting for sevice media.audio_policy...
I/ServiceManager( 4205): Waiting for sevice media.audio_policy...
W/AudioSystem( 4205): AudioPolicyService not published, waiting...
I/ServiceManager( 4205): Waiting for sevice media.audio_policy...
I/ServiceManager( 4205): Waiting for sevice media.audio_policy...
I/ServiceManager( 4205): Waiting for sevice media.audio_policy...

It can't get past this. Pulling the battery now.
[Captivate Android Development] junktzu:
This happened to me too.
[Captivate Android Development] mikewong27:
I also got stuck at recovery mode while applying the lag fix. I downgraded to 1.5.2 and still have same issue while applying the lag fix. Can anyone help? Thanks,

Mike
[Captivate Android Development] bts0uth:
Weird. Im not freezing or anything weird in recovery like you guys are. On normal 1.5.3. O/C'd to 1344 at -25 UV. It froze once playing pocket legends after about 30 mins when it was at -0 UV but its been great since I made it -25. Im loving it. Phones as fast as ever.

Posted from my Captivate
[Captivate Android Development] capita:
I was freezing up in recovery as well during lagfix. Not sure what was up. I ended up downgrading back to 1.4.3
[Captivate Android Development] mikewong27:
For me, it only freeze if I apply any lag fix in recovery mode. I tried 1.5.3 and 1.5.2 and both version froze while inside recovery mode. Really strange. I also tried to use One Click Lag Fix software and it doesn't allow me to apply ext2 lag fix.
[Captivate Android Development] lpsi2000:
When I downgraded, I re-flashed stock before going back 1.5.2. You might want to try that.
[Captivate Android Development] rusty815:
i kept getting the same issue too, what i did is i had it apply the lag fix without backing up or restoring anything, it worked. i lost all my data, but i backed it up with titanium backup so i was fine.
[Captivate Android Development] johan8:
I've just applied 1.5.3,

but my phone just keep freeze or reboot:(

I've just keep /system/etc/init.d/S99_freq_scheduler.sh as default ......0 0 0 0 1 1 1 1 1 1

Very unstable for me.....:(

And Quadrant score is 50-100 lower than 1.4.x
[Captivate Android Development] junktzu:
Finally got 1344 running stable with 0 25 50 50 75 100 100. I hope to push up to 1400 tomorrow.
[Captivate Android Development] xredjokerx:
does anybody actually notice any performance difference between 1200mhz and 1400mhz or even 1600mhz?

I feel like the phone is already pretty snappy at 1200mhz and I'm afraid to fry the chip by running it at 1400 much less 1600. thats a 40% and 60% cpu clock increase. On top of that.. undervolting it? that just seems so risky... am i wrong guys? I don't know much about cell phone cpu's and gpu's but I know I wouldn't do a 60% OC on any of my computer clocks.

On a side note, this may be unrelated, but I've worked a lot with car audio and I've heard that if your amplifier doesnt supply enough watts rms it damages the subwoofer-- would that also apply here? you're giving the cpu less volts when it demands it? But i'm not completely 100% sure about that either.

Please enlighten me, this is merely my own speculation; I mean no offense to anybody.
[Captivate Android Development] gtg465x:
So I wiped data from cwm and for some reason I lost voodoo color. Actually I'm not complaining though because my phone looks way better without it. My display is only slightly cool stock and voodoo color makes it too warm (gives whites and grays an ugly redish tint). On to my point though. I was about to ask if you could provide a version without voodoo color or tell me how to disable it, but then I fell upon this convenient bug. For future reference though, is there a way to disable it easily (other than wiping data)?

Thanks
[Captivate Android Development] johan8:
In 1.4.x, Quadrant score is around 17xx~19xx

But in 1.5.x, score is 15xx~18xx

CPU is running 1.2G.

So anybody know what's wrong ??
[Captivate Android Development] amtrakcn:
Frequent freeze at startup...