yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] speshow:
Wow, I did not know and spent like 2 hours on it last night.
[Captivate Android Development] shaolin95:
Ha! Welcome to the club :D
[Captivate Android Development] PAulyhoffman:
Your item left the United States from ISC CHICAGO IL (USPS) at 10:36 pm on December 14, 2010. Information, if available, is updated periodically throughout the day.

hopefully i wont be too long in customs...
[Captivate Android Development] Nickel Dime Bay:
same thing happened to me, i did not know about using odin. If you could zip up 1.4.6 1200 id appreciate it.
[Captivate Android Development] PAulyhoffman:
this should work for you. PM me if with your results
[Captivate Android Development] Nickel Dime Bay:
Thank you!, i will flash this in a bit. I am using 1.4.3 1280 right now, do i just flash this over in cwm?
[Captivate Android Development] aleadam:
You're the man! Not only the phone, but all the track info in real time :)
[Captivate Android Development] PAulyhoffman:
yes 10char
[Captivate Android Development] johan8:
Depends on which file you have downloaded.

If you've downloaded odin tar file, of coz you need to flash into your phone.

If you've downloaded cwmupdate zipfile, of coz you can only update it in recovery mode.
[Captivate Android Development] Doug8796:
SetiroN : Please make a GPU OC kernal . I would like a .9-1.2 ghz kernal with a much higher gpu clock !
[Captivate Android Development] Yuna:
This won't do too much: we have too slow CPU for such POWERFULL GPU, or you didn't noticed that while overclocking CPU we have also about the same % increase in GPU perfomance, at least quadrant 3d tests?
[Captivate Android Development] bugity:
Im trying to adjust the clock but i have tried every kernel on this page and every 2.2 froyo captivate rom but i dont seem to have the files

/sys/devices/system/cpu/cpu/cpufreq/states_enabled_table

/sys/devices/system/cpu/cpu0/cpufreq/update_states

therefore im unable to edit files i do not have ps im using root explorer to browse my files. thanks
[Captivate Android Development] Doug8796:
well these are for tests of the Dreamcast emulator. GPU is slowing down speeds. No games on android market really demand the gpu. It will help, trust me :P
[Captivate Android Development] shaolin95:
So the emulator is really using our GPU that much unlike the psx4droid one? I wish that is true but somehow I doubt it.
[Captivate Android Development] ryude:
He's telling the truth, however I truly doubt an OC on the GPU would provide any tangible improvement in emulation.
[Captivate Android Development] aleadam:
what kernel are you using?
[Captivate Android Development] SetiroN:
Would anybody be available for beta testing? I need someone who has issues with v1.5, possibly with a phone able to run at 1450/1460MHz and is willing to waste a little time. Drop me your email address in PM if you're interested.
[Captivate Android Development] johan8:
I like to be a tester, PM is sent.
[Captivate Android Development] aleadam:
Why not?

10 char
[Captivate Android Development] mgfjd:
I am new dont know if this can be done...

Can the in call volume be increased? Driving and trying to have a phone conversation is really hard.. The default volume for the captivate seems to be on the low side.. if there is a kernel that helps to increase the volume, it would be appreciated.

Thanks.
[Captivate Android Development] bugity:
Currently the xt 1350
[Captivate Android Development] ColonyDude:
I believe others have done this but I decided to run some of my own tests with the 1.4.6. Normally I don't do well going past 1280. I was was surprised how well I did overall.

I averaged my scores. All the test were done with RFS and no under volting.

1400 had problems with quadrant. Quadrant would freeze somewhere while walking through the rooms. I could use linpack and stability test with no real problems. I tried under volting 1400 but that did not help. I felt like I could use this if I did not do anything that was too intense on the graphics.

I am going to use 1280 because I am afraid 1400 would freeze during games.

speed linpack quadrant

1200 16.5 1206

1280 17.4 1234

1300 17.7 1233

1350 13.7 1104

1400 18.9 1255 1209

1450 17.4 1161

1460 Freezes on boot

Hope this helps someone.
[Captivate Android Development] thardie:
VPN (tun.ko)

I'm running this kernel - Any chance you can build tun.ko for it? If not, can you post the config file you used to build this, any patches, and I'll build the whole thing from scratch (although, it'd be much better if you could just build tun.ko) :)

Thanks!
[Captivate Android Development] ngochuy:
what is the difference between xt and non xt version ?

thanks
[Captivate Android Development] grkmaster:
so i may have downloaded the wrong setiron kernel as i was applying to my captivate over a stock jpu rom and my screen went black ... ive tried every method to get it back on but nothing.. no power to it what so ever. (was odin flashing 1.4.6 1480mhz)

ive tried my jig .. which works at times and doesnt cause it came apart... ive put a hair dryer with the battery off and then put it back in to see if that would trigger dl mode.. nothing ... ive tested with a differnt battery nothing... it seems no sort of life to it ...

what is my last resort?? or is there any other than hopefully go return and get a new one?
[Captivate Android Development] xan:
Reconstruct your jig!
[Captivate Android Development] grkmaster:
let me ask ... even if i used the 1480mhz kernel, i assume my phone isnt able to handle it, but technically i should be able to get into download mode no matter what to reflash back to stock?
[Captivate Android Development] xan:
Yes you should!

Moreover you should be able to get into recovery.

Kernel has no influence on sbl [secondary boot loader], which is responsible for Download Mode.

If jig worked for you before it should work this time too.
[Captivate Android Development] grkmaster:
I just read what setiron wrote... his phone bricked.. same issue as me where nothing is working.... that will suck! ... im gonna try new resistors tomorrow since i left them there.. if not then there goes my files on my phone that i backed up too .. ugh

also how possible is it that it can be in download mode with the screen being black the whole time?
[Captivate Android Development] bames:
easy solution

use Root Explorer to mount system r/w

then save the boot settings. Worked for me.
[Captivate Android Development] SetiroN:
v1.4.7

- fixed boot animation issues

- fixed init.d script execution

- fixed CIFS support

Additional frequencies to follow.
[Captivate Android Development] shaolin95:
Thanks...it is looking nice!
[Captivate Android Development] SetiroN:
Here they are.

I still welcome anybody else willing to beta test new things out. :)
[Captivate Android Development] DAGr8:
GREAT ill be waiting for higher freqs .

Edit they are out .. testing now !

for some reason the best linpack I ever got were on 1.43 @ 1.450 GHZ XT ... tho unstable (crash in gallery everytime) successfull linpack would give me at least 22 sometimes 23.5 //

since then 1.54XT (although it drains like mad)

I can run at 1.464 GHZ -25 no problem whatsoever , but linpack stays at 19.8 - 20.2 same thing if I go to 1.504 GHZ tho not stable (random crash in gallery so more stable then 1.43 @ 1.45GHZ ) linpack barely go up , actually the average result pretty much the same from 1.400 GHZ to 1.504 GHZ...

cant boot 1.55 at all here or if it boots it doesnt last ..

I suppose you know my next question ...

were the linpack fubared on 1.43 or what changed ? sorry I read the thread a few times cant seem to find the answer ..
[Captivate Android Development] SetiroN:
RAM and other internal compoments run on the same clock used for the GPU. It only makes a tangible difference in Linpack, real world performance is much more CPU bound.
[Captivate Android Development] DAGr8:
agreed

cant get passed scanning media @ 1552 XT

1488 just rebooted on me on linpack , it freeze on every boot now

goin back to 1.54xt

Edit 3 : obviosly didn tdelete anythnig ssice I coudnt boot in between , now bunch of FC on boot goin back to 1.54 time to master clear and try again ..
[Captivate Android Development] momulah:
Tried flashing through clockwork by switching zimage from 1.4.7 1288 to 1.4.3 1200 cwm version and when I try to flash it states E: blah blah blah error...Any ideas?
[Captivate Android Development] DAGr8:
probly zip got corrupted ... try putting newone in there

happens often to me lately for some reason ( too many odin one click me guess )
[Captivate Android Development] alkam:
From Russia with love, Setiron. Its a vremennie (russian) troubles, kirpitch (brick-russian). Everything ll be OK.

Thanks, excellent work.

1.4.6.1200, KILLER23D_XXJPU_Doc_V4.0, JL3.

next 1.4.7.1200, KILLER23D_XXJPU_Doc_V4.0, Jk4.

Old 7.6.2 JPA killer23d, 1.4.3. 1200.

1580 voodoo, 1300 no lagfix
[Captivate Android Development] johan8:
This is the grestest kernel so far!:)

Is it also JPU supported ?
[Captivate Android Development] shaolin95:
I tested it with Darky 5.5 JPU and it worked great for me.
[Captivate Android Development] SetiroN:
Yup, it is.
[Captivate Android Development] shaolin95:
So Setiron how do 1.5 and 1.4 series differ...if its possible to explain so that even I can understand it that is aside from one having a single set speed? LOL
[Captivate Android Development] johan8:
That's great!

On the other hand, do you guys have any idea why 1.5.x won't work in my i897 ?:(

I'm using stock i9000 rom, that's it..... not any cook rom.
[Captivate Android Development] johan8:
1.4 is single speed OC.

1.5 is multi-speed OC, you can switch from 100Mhz to 1.6Ghz anytime.
[Captivate Android Development] shaolin95:
Ok so just as I thought that is the only thing. Cool
[Captivate Android Development] DAGr8:
I beg to differ none of these boot for me while I boot no problem with 1.54 XT set at 1504 ...
[Captivate Android Development] johan8:
Even 1.4.7 1200 also not work for you ?

I can't use 1.5.x, it just freeze after media scan.
[Captivate Android Development] DAGr8:
Im sorry I should have specified , of course I meant @1.4ghz ..
[Captivate Android Development] beerbaronstatic:
This was asked a few pages back but nobody answered it. Whats the difference between the normal and the XT variants, and why would you run one over the other?
[Captivate Android Development] geokhentix:
The XT variant was compiled under different conditions with different flags and parameters. It runs a little bit faster, but is also more unstable and battery intensive. If you can roll with XT, do it. The battery drain difference is very negligible.

I've been running 1.5.4 1600mhz XT variant for the past week now, my and my battery is decent.
[Captivate Android Development] aleadam:
That has been asked and answered many times. Just not in the last few pages. Before posting such a message, I would strongly suggest you to use the search button.

It is my understanding that XT variants have different compilation optimizations. They are mainly for testing purposes and may give you a slightly increased speed at the expense of more battery consumption and less stability. Others seem to have better results with them than with the non-xt versions. YMMV.
[Captivate Android Development] shaolin95:
I think Setiron should put that in the OP with big bold letters. :D
[Captivate Android Development] beerbaronstatic:
That was the first place i looked, then I did a basic quick search
[Captivate Android Development] JPxM0Dz:
I'd love to see some screenshots of that including a couple of benches ;)
[Captivate Android Development] M1nur:
ok im having issue flashing this latest kernal on my axura rom. any ideas? the file says bad when flashing using rom manager.

also the extension says .7z so its not even recognized until i change it to .zip
[Captivate Android Development] existz:
You have to flash with Odin...just open Odin, put the phone in download mode, and flash
[Captivate Android Development] M1nur:
I only have the odin for stock rom reload

link please?

And flashing this will keep my rom, right?
[Captivate Android Development] existz:
Yes you will keep your Rom,all this does is change the kernel....as for a link to Odin, you will have to search to find it, I dont have time atm to look for it, but it is here on XDA
[Captivate Android Development] M1nur:
Cool thanks bro
[Captivate Android Development] slider2828:
Hey guys,

1.4.7 IS SECKSI!!! It works a LOT better than 1.4.6. I was able to get 1288 on my phone which 1.4.6 couldn't for some reason....

Anyways, does anyone have any problem with Xan's VC? Mine is FCing everytime I try opening it.....
[Captivate Android Development] MikeyMike01:
No CWM version? It's such a pain to use Odin.

Sent from my Captivate.
[Captivate Android Development] slider2828:
Yeah not CWM version. hahaha....

Hey Mikey the battery drain was because of JL3 with your ROM.... Tell peeps not to use it..... It drains like a MOFO
[Captivate Android Development] aleadam:
Among all, you?!! :D

I agree that odin is kind of annoying, but how long does it take to grab an old cwm zip and replace the zimage file?

On the other side, I was having some bad flashes using cwm. Odin 1.7 was always flawless for me...
[Captivate Android Development] krazyphire:
Off-topic: Using JL3 with no issues and battery is great with full bars. Feel like I've already mentioned this too you but you may be the only one with your battery issues.

On Topic: Is anyone else having fcs with 1.4.7 and xan's voltage app?
[Captivate Android Development] slider2828:
Yup FCing all over the place.... Tried uninstall reinstall RC4 and same thing.... Dunno why.... But if you read the JL3 thread, I am not the only one reporting it....

Yeah I have no idea why its draining either.... it didn't happen before....
[Captivate Android Development] existz:
Same here, FCs with Voltage app...

Also using JL3 and so far battery has been great over last few days ..about the same as JK3
[Captivate Android Development] krazyphire:
Yeah sorry didn't want to sound like a know it all lol its just when mine works great I wonder why others have issues
[Captivate Android Development] DAGr8:
I m not running it anymore .. but I did experience it ..

all I did was uninstall reinstall VOILA it worked

dont forget to thank me

lol
[Captivate Android Development] MikeyMike01:
The one he's referring to is JK3. Not JL3.

Damn Samsung ROM names. :rolleyes:
[Captivate Android Development] xan:
About VoltageControl issues -> please report in my thread, there is also a 'troubleshooting' guide there.

BTW, new version is due in few minutes, includes interaction with "states_enabled_table"
[Captivate Android Development] slider2828:
Yeah I got it fixed. I deleted ALL the scripts that were there such as 99volt, 99freq, and freq. Then uninstalled and reinstalled and it worked fine, except it doesn't detect 1288MHZ custom volts. Xan's 3.0 will fix that I think ....

If you can't uninstall through apps, then you have to use TIBU to uninstall....
[Captivate Android Development] MikeyMike01:
I have JL3, 1.4.7, and voltage control 3.0 rc 3 and it works fine.

On Assonance 5.1 of course. ;)

Sent from my Captivate.
[Captivate Android Development] xan:
Those scripts you refering to were not created by VoltageControl. Only script being created and removed is 'S_volt_scheduler'.

About 1288 voltage: unless there is information available by 'frequency_voltage_table' only information I got is *stock* table. This is for security reasons: since kernel makers apply different voltages on custom frequencies hardcoded values might mislead them about the real voltage applied.
[Captivate Android Development] peachpuff:
Anyone getting fc's on barcode scanner and google goggles with 1.4.7? No fc's with 1.4.6.
[Captivate Android Development] DAGr8:
well I tried both I have exact sae battery drain ..

as I said dotn forget to thank me , only reinstalling after upating kernel fixed the problem , but yea xan's 3.0 works
[Captivate Android Development] shaolin95:
I am trying to boot at higher speeds with 1.4.7 like 1.6Ghz but I know I need to lower the voltage to get some stability at least yet I cannot do so because it needs to boot at full voltage before I can apply this.

I believe there is way to push a modified voltage file from ADB or something like that right?
[Captivate Android Development] slider2828:
Yeah the wifi drains battery... I switched to JK4 and when I sleep and turn off wifi and it seems to have worked.... try that.
[Captivate Android Development] neffarious:
I had Xans crashing issues as well, i reinstalled the 1.46 kernel and the reflashed 1.47 and it worked again. This is probably moot as he has released a 3.0
[Captivate Android Development] DAGr8:
setiron can we please get a JPX kernel ?

EDIT : flashed 1.45 JPU on top of doc's JPX rom and its workin .
[Captivate Android Development] johan8:
Probably you need to DHL/UPS a i897 to him....
[Captivate Android Development] DAGr8:
lol that ahs already been done read the first post and dont forget to thank the donor ..
[Captivate Android Development] johan8:
I know, seems that it will delivery soon.

So if you are in harry maybe you can send another by UPS, it will deliver in the next day.

And I've already thks to donor, you can find my post in previous pages.

Btw you can use 1.4.7
[Captivate Android Development] gin032:
CIFS

Is there a cifs kernel module for 1.4.7?
[Captivate Android Development] johan8:
Yes, it is build-in !

Just boot to recovery, enable it in CWM.

Then you don't need to "insmod" the modules anymore,

and simply use "mount -t cifs ...." to mount your win-network(or samba) share.

And you can use cifsmanager(also in Market) to mount your share.

Of course you can disable "Load cifs module" in the settings, because module is already in kernel.
[Captivate Android Development] gin032:
I've loaded 1.4.7, but CIFS still doesn't work for me. Was this compiled into the kernel, or should there be a kernel module for it?
[Captivate Android Development] gin032:
posted while I was typing my question...excellent info. I've never "enabled it in cwm"...editing post as I found the option after a little looking:

Enter recovery mode (hold power button while running until power options menu, select recovery)

select advanced speedMod ULK Features

select TWEAK options

select enable CIFS

Can anyone provide technical level info on what CWM is changing here to enable CIFS?
[Captivate Android Development] johan8:
If you see CIFS enable, then it cifs module will load during bootup.

What else you want to know ?

You want to know how CWM trigger the ON/OFF switch ?

If you look into the bootup script, you will know what's going on.
[Captivate Android Development] thecellx:
1.4.7 kills battery. I tested 1.4.3 and 1.4.7 with the same rom,settings and use and the difference is incredible. On 1.4.3 i did 30 hours, on 1.4.7 i just did 7 hours.
[Captivate Android Development] shaolin95:
In case anyone is wondering I am using 1.4.7 with a JPX Rom and all looks good so far! :)
[Captivate Android Development] aleadam:
Is it enabled in cwm recovery?

advanced SpeedMod ULK features -> TWEAK options -> Enable CIFS support

As an optional tweak, in some kernels it's not enabled by default

Never mind, replied before finished reading the thread...
[Captivate Android Development] aleadam:
Say whaa??? What about rc2?? Giving up? ; )
[Captivate Android Development] SetiroN:
That's really strange and unexpected... could you monitor CPU frequency while idle?

Anyone else having such issues?

v1.5.6

- fixed boot-up and CWM instability

- updated modules from JPX kernel

- full compatibility with Voltage Control 3 alpha3 (alpha3 bugs: lowering frequency and leaving it open seems to cause freezes, please report in Xan's thread)

- removed update_frequency, making changes to the freq table immediately applies them

- new frequency table

1600MHz CPU	200MHz GPU	1400mV
1552MHz CPU	194MHz GPU	1375mV
1488MHz CPU	186MHz GPU	1350mV
1440MHz CPU	205MHz GPU	1325mV
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

RESET ALL UV SETTINGS (DELETE INIT.D SCRIPTS) BEFORE UPGRADING TO HIGHER VERSIONS

Voltage Control 3 supports enabling higher frequencies from the freq table, but doesn't yet let you disable selective ones.

To disable a certain frequency its corresponding value in /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table has to be set to '0'.

Changing update_states is no longer necessary. That file can either be manually edited or modified through an 'echo' command, which is much more convenient if you're in front of a PC and able to use ADB.

It's a volatile RAM file, which means changes made to it won't stick through reboots; I've included a script that reapplyies settings on boot in the CWM package (also attached to this post).

Let's say you wish to overclock to 1400MHz and disable 1288-1344:

1344MHz corresponds to the 6th value, 1288MHz to the 7th:

#!/system/bin/sh
#SET OC - below are GHz decimals (i.e. 1.60GHz, 1.55GHz, 1.50GHz and so on)
#60 55 48 44 40 34 28 20 00 .8 .4 .2 .1
[color=red]#[/color]echo 0 0 0 0 1 [color=blue]0[/color] [color=blue]0[/color] 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table

REMEMBER TO REMOVE # FROM THE LAST LINE
[Captivate Android Development] realawill:
Thanks for all your hard work SetiroN!
[Captivate Android Development] slifer315:
I am not having similar battery issues. did your battery completely die in that 7 hours or did it just get low? if it didn't actually die yet, you might just need to recalibrate the battery. but I guess it could also be that your phone was idling at too high of a frequency...potentially because of an app staying open in the background?
[Captivate Android Development] thecellx:
Completely dead. I did not make phone calls, data was fully disabled, battery was calibrated, and no applications running on background.
[Captivate Android Development] Cezar`:
What ROM were you using?
[Captivate Android Development] shaolin95:
haha of course not, it worked fine on JPX too and left it charging all night and came back to life in the morning without issues :)
[Captivate Android Development] johan8:
First of all nothing is dead and nothing is broken!

Leave your phone in idle when poweron (don't run any programs and don't touch it)

after 10min check your battery temperture,

if it is still over 30°C, and you feel your handset is a bit warm,

means that battery drain is happening.

Then you should delete any files in init.d, reboot your phone.

It should be ok now.
[Captivate Android Development] mgfjd:
1.47 is great I don't have any problems..
[Captivate Android Development] sublimaze:
*oh snap*

lol

sent from my captivate with di11igaf b3.0
[Captivate Android Development] slider2828:
Mikey's still hoarding 5.1!! hahaha just kidding... LOVE YAH
[Captivate Android Development] thecellx:
Well.... i notice that during weekend.... and happens after a few minutes.. youre right. Phone is unusually warm. Im going to apply your recommendation.

Thank you.
[Captivate Android Development] thecellx:
Cronus 1.53
[Captivate Android Development] xpamiceftk:
1.4.7 is the best kernel I have used. It is so great.

Thank you for bringing us so good one.

GOOD WORK
[Captivate Android Development] slider2828:
You don't delete EVERYTHING.... you just delete anything dealing with Volt and Freq.... and then reapply voltage with Xan's VC.
[Captivate Android Development] MikeyMike01:
I don't think I've ever been running the version you people get. :cool:

To be honest, I'm waiting for my phone to become different enough to warrant a release. Other than a new kernel, modem, keyboard with vibrate, and Voltage Control it's still 5.0.
[Captivate Android Development] joedon3:
Doh! 1400 kernel keeps crashing. I've run 1400 for weeks before. oh well, guess its back to 1200 :(
[Captivate Android Development] joedon3:
I may have figured out why. the Voltage Control app didn't reset my boot settings before I flashed. I manually had to set them back to 0.
[Captivate Android Development] neffarious:
Edit- found my answer