yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Flynny75:
No such luck with me. Cleared OC/UV in recovery, got gps aids and injected time/LTO/Xtra, and still nothing. Finds 5 sats, gets a lock to within 300ft, then looses it and wont lock again. doesnt see more than 5 sats. Will flash .22 again see what happens.

Edit: WARNING:WARNING:

The link you have for the older versions points to i897 not i9000!

Edit2: Flash .22, Good GPS again. Accurate inside 32ft, can hold a lock for ever. Back on .31 and crappy again. Cant hold a lock aven with 7 sats all over 25 SNR. Hhmmm....
[Galaxy S I9000 Android Development] tzyn:
WPA2-PSK AES/TKIP on channel 1. No other Wlans in my range.
[Galaxy S I9000 Android Development] I9000bramgmail:
"Wired Headset Support"

Hi,,

I'm entirely new to the news of this kernel,, jus saw it as option in Romkitchen... (currently on tegrak kernel)

Can somebody explain me what the "Wired Headset Support" means?

thanks!

cheers
[Galaxy S I9000 Android Development] elcaro:
Wifi ( and everything else for that matter ) works fine for me.

Stock Deodexed JVP + Talon 0.3.1
[Galaxy S I9000 Android Development] betoNL:
No issues except overclocking up to 1400Mhz

Ok , just flashed a couple of hours ago the 0.3.1 version after being testing the Galaxian kernel for a while

Bluetooth and wifi are working flawlessly as always !

GPS is better than ever.

The only thing I cant do is overclock up to 1400 (I mean as long as I dont run heavy apps) ... and overclock up to 1200Mhz is possible as long as I overvolt 1200 a little.

I have one of those sgs's that are difficult to overclock.....at least I thought so; because while running the Galaxian kernel I could overclock up to 1400Mhz with no problems....super stable

I dont think is a good idea excluding some frequencies like it happens with the 1400Mhz version of Talon...

I mean, is that wise if it has to jump jump from 1000Mhz straight to 1400Mhz ( what stability concerns) ?

Anyway, if I want an OC/UV kernel overclocked up tp 1.2Ghz and battery safe I stick to Talon kernel.

But if I want 1400OC, the only kernel that will run on my sgs without stability issues is the Galaxian, but it feels less battery efficient than Talon

The only thing I didnt change yet is the Rom. I am still on v73 of CriskeloGinger.

That's the best way to test various kernels - sticking to one version of the same mod rom for a while....

«»
[Galaxy S I9000 Android Development] Darcia:
Be careful everyone : OC + OV is a really bad mixt that make your CPU warm like hell. And there is no ventilator in a device ^^
[Galaxy S I9000 Android Development] Cy4n1d3:
What voltage does Galaxian apply at 1400 mhz?

Had to bump voltage to 1.325 for 1200 mhz for my device to be stable.
[Galaxy S I9000 Android Development] betoNL:
I didnt undervolt nor overvolt then....

But if you did run all kind of OC/UV apps in the past, I think that the best way to test a new kernel is:

-Flashing the Kernel after a fresh firmware install

- Sticking to one mod rom and to one version of that rom....

«»
[Galaxy S I9000 Android Development] Cy4n1d3:
Not exactly, voltage values are hardcoded inside the kernel and then adjusted using apps. If your phone (for example) needs 1.5v for 1400 mhz: talon supplies only 1.45v @ 1400 mhz, if galaxian supplies 1.5v the difference in stability is to be expected. That's why I'm asking how much voltage galaxian applies, so we can figure out if stability issues arise from voltage or other settings :)

On topic: using max. gpu overclock across the bank, so far no problems! Great ;)
[Galaxy S I9000 Android Development] betoNL:
By the way, which app do you use to overvolt? Cause Voltage Control extreme and tegrak overclock ultimate are way too buggy for my taste.

Btw2 : Galaxian kernel is not ovevolted at 1400Mhz....at least that's what I read when using Pimp my CPU or Control freak apps...

So....what's their trick ??:eek:

«»
[Galaxy S I9000 Android Development] Cy4n1d3:
I'm compiling the kernel myself with some adjusted values, as I need higher voltage for 1200 mhz...

Control Freak is pretty good, so far no major glitches.

I can't believe that galaxian does not apply extra voltage for 1400 mhz.

Must be wrong values in uv-table I guess...
[Galaxy S I9000 Android Development] betoNL:
.

Why you just dont give it a run, for testing purposes ?;)

«»

Edit: Oops...there's a new version now.....looks like 1300 and 1400 are slightly overvolted....not sure anymore and the scheduler is ...deadline....
[Galaxy S I9000 Android Development] Cy4n1d3:
I would need the source of galaxian to tell how much voltage it effectively applies. Or an app which monitors effective voltage by sensor readings, not from files in cpu-folder :\
[Galaxy S I9000 Android Development] Bavaria85:
For me undervolting makes my phone more stable when oc'ing. I can have 1440 stable with -25/50 uv.
[Galaxy S I9000 Android Development] existz:
So I believe the gps issue is caused by the compass issue, gps is locking instantly now for my i9000 testers..which the problem doesn't exists for captivate users so im betting that's what fixed it. So it will be fixed in next release (fingers crossed)

Sent from my SGH-I897
[Galaxy S I9000 Android Development] betoNL:
undervolting the highest frequency doesnt sound logical...does it?

But then again jumping from 1000Mhz straight to 1400Mhz doesnt sound logical either....

«»
[Galaxy S I9000 Android Development] existz:
Y not undervolt highest frequency? I have a new 1300 build im running at 1350mV stock, but 1350 is to much for me, so I have to undervolt it 50mv to stay stable...there's nothing wrong wwith undervolting max clock, some times it makes things more stable.

So for example, if Galaxian kernel really does not raise the voltage for 1.4ghz, and you can run it stable...then with Talon having it at 1400mV, it may be to much..so undervolting it will make it stable for you ..

Also, Ondemand 99% of the time scales from min to max, without scaling through other frequencies..so even if I add a 1200 step in, its only going to be used like 3% of the time...when I ran all in one oc, usually the freqs other than min and max were only used 1-3% of the time, so its not really going to make a difference if its there or not..

Sent from my SGH-I897
[Galaxy S I9000 Android Development] Flynny75:
Good news! Hope this fixes it, this kernel is awesome.

Existz, be sure to check the OP. Your link to older versions points to the Captivate kernels, not i9000
[Galaxy S I9000 Android Development] Darcia:
Uv make your CPU warm less, OC make your CPU warm more. So OC + UV is a good ( I won't OC my CPU to a frequence that I can't UV).

The problem is that more you OC and UV at the same time, less your CPU "detect" the "pulsating" electrique signal. ( Sorry a bad transcription from what my father teach me x) )
[Galaxy S I9000 Android Development] zenosteam:
is it compatbile with the new rom XXJVQ ?
[Galaxy S I9000 Android Development] existz:
Yes should be, a few people on IRC verified it
[Galaxy S I9000 Android Development] existz:
Thanks!..didnt notice that..fixed now
[Galaxy S I9000 Android Development] theos0o:
When will you release the next version mate?

GPS seems a bit off and compass is way off.. :p
[Galaxy S I9000 Android Development] existz:
Yea as i mentioned above, issues are fixed.. will be in next release.. I dont have an ETA, it all just depends,.. Theres technically 4 of use working on Talon (Me, Kodos96, Ytt3r and Zacharias.Maladroit) so just depends on when all of us get work done and are satisfied with the release
[Galaxy S I9000 Android Development] cantIntoCode:
Waiting Patiently :)
[Galaxy S I9000 Android Development] zenosteam:
well ,i can now paly with uv

100mhz 150

200mhz 100

400mhz 100

800mhz 100

1000mhz 50

playing with that settting nova2hd ,shadow guargian hd, with any probleme
[Galaxy S I9000 Android Development] pidz:
This was the first one i tried, didnt really fancy anything faster than 1Ghz, so stuck with no OC.

TalonDEV 0.3.1 340MB No-OC CWM3

Pretty sure this is for i9000.
[Galaxy S I9000 Android Development] Bavaria85:
For me undervolting is the only way to get things stable. If you want to test, just lock your frequency to 1400/1440 or any other frequency you want to test and check your stability. Stability issues for me first kick in by skipping frames or weird frame rates in benchmarks...

I find the right undervolts by using linpack and checking what the best scores give. Certain voltages actually give better/lower scores then others...

Maybe someone now will tell me this cannot be right, but from my experience this works best...
[Galaxy S I9000 Android Development] squealernet:
I'm on 0.3.1 noOC with Juwe5 and navigated today perfectly with navigon. even small short left right turns where announced correctly. Did not check the compass, but bluetooth worked perfectly in the morning accepting pictures from SE K800i

And I never had WiFi issues with this or 0.2.2 version using different WI-FIs (Multiple Home Wifis plus WEP-University WiFi with vpnc. only vpnc disconnects every now and then but would reconnect immidiatly

Only the power consumption is higher compared to gingerbread2.3.3 juwe + fugumod, but now the heavy drains are gone.
[Galaxy S I9000 Android Development] zs0mby:
request

can I ask you to make an 1500 or an 1540 mhz version of the kernel in the next release? thanks in advance....and keep up the good work with this amazing kernel...excellent battery life, 2% in 7 hours, amazing speed and it's very stable to :D
[Galaxy S I9000 Android Development] paratox:
would a bug fix release possible? only 0.3.1 with working compass? something like 0.3.1r2.

i love the talon kernels but sometimes i need the comapss for maps. waiting until next release with no ETA sounds too long for me and maybe others are thinking the same. don`t want to use another kernel only cause the compass problem. maybe you can pm me the fixed test kernel? :)
[Galaxy S I9000 Android Development] johan81:
I would like to see a r2 version or something like that as well when possible.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] astralmind:
Indeed, same here. GPS is critical for me and I'd rather not use a "non TalonDev" kernel :)
[Galaxy S I9000 Android Development] jcvr:
+1 .... "patch" the compass ...
[Galaxy S I9000 Android Development] zacharias.maladroit:
the following kernel is compiled from the official JVP branch

compass is working (just tested)

Enjoy ! :)

edit:

1.2 GHz OC
[Galaxy S I9000 Android Development] jaiiscool:
Wat overclock?
[Galaxy S I9000 Android Development] zacharias.maladroit:
looks like 1.2 GHz
[Galaxy S I9000 Android Development] jaiiscool:
Thanks. Will check it out.
[Galaxy S I9000 Android Development] ktuluz:
Wootz.. Very stable for me on jvq. Bt/wifi/compass/cifs/oc/uv all tested

Phone/gps not tested.

Very smooth at 1200mhz.

Thanks! i really need to learn how to compile this on my macbookpro
[Galaxy S I9000 Android Development] jaiiscool:
My compass is still broken :(

No stock boot animation either
[Galaxy S I9000 Android Development] moophlo:
Hi All,

first of all a big big thanks to existz for it's great job with this kernel.

I'm tring "TalonDEV 0.3.1 340MB 1440MHZ CWM3" and I noticed that if i "Save as boot settings" my preferences of OC/UV on Control Freak the phone boot become really annoying slow and my quadrant score fall down to 2000.

Instead if I use the "Apply for Now" option the user experience is wonderfull and my quadrant score is up to 3000 and more.

Any tips?
[Galaxy S I9000 Android Development] zacharias.maladroit:
bootanimation has been broken for some time (at least for me when adding some optimizations)

don't know why - it hasn't been that fragile with chainfire's initramfs but that in return broken bluetooth :p

try calibrating or waving the phone in an 8-form in the air (like explained, e.g. in the app "compass")

after that it should work

at least for me it points to the correct direction
[Galaxy S I9000 Android Development] hickup:
Thx! just flash via CWM?
[Galaxy S I9000 Android Development] jaiiscool:
I tried all of that.

I just noticed that even if i rotate the phone 180 degrees it still points in the same direction and that becomes the right direction. Like it is not working at all.

Is it some hardware fault?
[Galaxy S I9000 Android Development] zacharias.maladroit:
yes

or you can extract the zImage and flash via Odin/heimdall

could be

or there might be something missing in the source from samsung; changes in JVP, JVQ, ... (source isn't released yet)

did it work before ?
[Galaxy S I9000 Android Development] jaiiscool:
I guess so..... Wats ur current compass working setup?

Also whenever i start the app compass i get the toast that reads "Abnormal magnetometer readings, plz calibrate"

Sorry for troubling you......
[Galaxy S I9000 Android Development] zacharias.maladroit:
FICETO.DEODEXED.XXJVP

Ficeto's JVP Base ROM or how it's called :D
[Galaxy S I9000 Android Development] jaiiscool:
Turns out I was sitting in some magnetic vortex. I moved to another room in my house and bammmm, its working perfectly.

I am so sorry zach....... I feel like such a noob.....
[Galaxy S I9000 Android Development] komoornik:
Would love to try it, but the download is so slow.

Mirror any1?
[Galaxy S I9000 Android Development] betoNL:
Well, GPS is my thing and since I never had any issues (The gps on my sgs kept working fine with all Talon versions, including last one), I would like to ask, how exactly it's getting fixed.

Could you specify?

I hope that what is a "fix" for some will a be "improvement" for others that dont have nothing broken to be fixed.....

I also notice that a new folder (SensorAiding) was added to /data/gps .

Does Talon add this new folder or it is from the new firmware (or mod rom)?

Anyway I dont think I could be usefull as beta tester....Never have issues, except for the stability ones....

Cheers

«»
[Galaxy S I9000 Android Development] existz:
I was using the wrong yas529 sensor position for i9000, so i changed it back to stock value (7), instead of (0), which got left over from the captivate config.

and no, talon does not create that folder

EDIT

I will probably have 0.3.2 released this week, probably by Saturday, I have a new test up, going to see how that goes, if alls good in next day or two, ill release it.. It will just be an incremental release (from 0.3.1 to 0.3.2) nothing drastic .. We added some patches from CKs patchset, been messing with VR io scheduler from Zen kernel, which is very similar to SIO (seems to be mix between deadline and noop).. Plus some fixes pulled from zacharias.maladroit... Also added a 1.3ghz version..not sure if ill replace 1.44 with it or not yet, or just release them all.. there's some cleanups to initramfs,..etc..etc plus fixed sensor position.. Also updated to JVQ initramfs contents, (works with JVP as well) ..
[Galaxy S I9000 Android Development] komoornik:
Any chance for those more aggresive settings in ram config ?
[Galaxy S I9000 Android Development] betoNL:
Ok Thanks.

Dont know nothing about yas529, but that changing of values perhaps can have some influence on accuracy (it now fluctuates between 30 - 10 meters instead of 10 - 5 meters as before)...but there is nothing really broken over here.

How/where can I check those sensor values?

Anyway, I am attaching the SensorAiding folder to this post....Perhaps it can be usefull....(and I still dont know how it appeared at /data/gps folder on my sgs.....

«»
[Galaxy S I9000 Android Development] aladin6:
Me too, i calibrated it and no good results :(

Any idea how to solve this prob?
[Galaxy S I9000 Android Development] Tatsuya79:
Great! thank you! :)
[Galaxy S I9000 Android Development] Cy4n1d3:
Had some random reboots using VR i/o scheduler, can this be related?

Other than that, the current version works flawless on JVQ, thanks :)
[Galaxy S I9000 Android Development] jaiiscool:
Mine started working when i went to another room. You may want to check it in an open space where there is no magnetic interference.

Ps: This was with zach's build. Thanks zach...
[Galaxy S I9000 Android Development] jaiiscool:
Deleted
[Galaxy S I9000 Android Development] hickup:
I'm on 0.3.1 oc1200 cwm for one day now, ROM Juwe 5.0. BT, Wifi, BLN working fine. Absolutely stable, no lags. Great work, thank you very much, Sir!

GPS seems to be a couple of meters off, but I experienced the same with a lot of ROMs/kernels, even with Froyo.

Regards, hickup
[Galaxy S I9000 Android Development] JB-007:
0.3.1 OC 1.2ghz but stay at 1Ghz

Hi all,

I flashed 0.3.1-1.2Ghz over Darkcore v2.6.

On Quadrant information, I see CPU max frequency:1.2Ghz but real CPU freq is never over 1Ghz. What's wrong????

Thk
[Galaxy S I9000 Android Development] komoornik:
Use an app like Control Freak to set it to 1.2 GHz.

Can any1 point me more aggresive settings for ram config ? Or I'll have to use AutoKiller app / Juwe's Script
[Galaxy S I9000 Android Development] betoNL:
Nothing wrong....

Wisely, this kernel is not overclocked by default

If you want to overclock and/or undervolt, you need a 3rd party app to do it. Such as:

Pimp my cpu

Control freak

Voltage Control

SetCpu

And more....

«»
[Galaxy S I9000 Android Development] betoNL:
There is no evidence that , agressive ram config settings are productive what Android OS is concerned...

But you can download the free app.- MinFreeManager from Market and play with some presets or create your own.

Some will say that too agressive MinFree setting are counter-productive within Android, and furthermore, evry usage and every device is different....

«»
[Galaxy S I9000 Android Development] JB-007:
Ok, I forgot to install Control Freak. My sgs works very smooothhhh!!!!

Thanks TalonDev crew.
[Galaxy S I9000 Android Development] Hrithan2020:
Can you share your settings with control freak? (I am using pimp my cpu already .. wondering whether to oc'ing gpu ,also whether uv +ocing gpu + ocing cpu works?)
[Galaxy S I9000 Android Development] st4rk:
As promised a small donation.. 6T299708UD6911331.. (will give a bit more once i've topped up my paypal accnt ;-))

Appreciate your work existx!
[Galaxy S I9000 Android Development] JB-007:
Here's the content of the volt_scheduler generated by control freak

#!/system/bin/sh

LOG_FILE=/data/volt_scheduler.log

rm -Rf $LOG_FILE

echo "Starting Insanity Volt Scheduler $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;

echo "Set UV" | tee -a $LOG_FILE;

echo "0 0 0 0 0 0 0 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo ""

echo "---------------"

echo "Set MAX Scaling Frequency" | tee -a $LOG_FILE;

echo "1400000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo ""

echo "---------------"

echo "Select Enabled States" | tee -a $LOG_FILE;

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

echo ""

echo "---------------"

echo "Set Scheduler for stl, bml and mmc" | tee -a $LOG_FILE;

for i in `ls /sys/block/stl*` /sys/block/bml* /sys/block/mmcblk* ; do

echo "[sio]" > $i/queue/scheduler;

echo "$i/queue/scheduler";

echo "---------------";

done;

echo "Insanity Volt Scheduler finished at $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;

echo "Setting current governor" | tee -a $LOG_FILE;

echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo "Current Governor Set" | tee -a $LOG_FILE;

echo "Setting gpu clock settings" | tee -a $LOG_FILE;

echo "200 400 200 400 200 400 200 200 200 200 100 100 " > /sys/devices/system/cpu/cpu0/cpufreq/gpu_clock_table

echo "GPU Clock Set" | tee -a $LOG_FILE;
[Galaxy S I9000 Android Development] existz:
Much appreciated :) thank you

Sent from my SGH-I897
[Galaxy S I9000 Android Development] asicman:
My understanding is that android 2.3 has no support for GPU acceleration, so GPU OC is kind of pointless. Not many apps make use of GPU @ 200MHz vs. 350MHz it seems. I've done GPU OC testing over the past few days at 350MHz+ and I can comfortably say I see no difference in smoothness in browser or UI. In fact, the difference was so negligible that GPU OC serves no purpose for me. And it is also horrendous on battery life. Its good that the feature is there, but android 2.3 itself does have GPU acceleration for apps of any kind. Smoothness comes from CPU OC and not GPU OC. I'd rather put that extra battery juice to go from 1GHz to 1.4GHz, rather GPU OC.
[Galaxy S I9000 Android Development] Trae32566:
So, GPU OC has hardly any battery loss as far as I've seen (and as far as the other testers). Also, 2.3 does have support for GPU acceleration as far as I know. Also, you kinda contradict yourself saying that it both does, and does not have GPU acceleration...
[Galaxy S I9000 Android Development] Tatsuya79:
I didn't see any GPU oc benefit neither. Pushed it to 300MHz, tried all the usual games I test each time, watched some benchs...

I wondered if it wasn't working or if my tests were only CPU dependant.
[Galaxy S I9000 Android Development] existz:
Plus you have to think that if its clocked at 300, is only a 100mhz OC, your not going to see much difference, even 200mhz shouldnt show alot of differnce, once more is figured out with the gpu, higher oc will be available
[Galaxy S I9000 Android Development] kodos96:
What exactly do you mean by "agressive"? You mean quicker to kill off apps? Killing apps quicker might make your phone feel a bit quicker in single-tasking performance, but then your apps have to reload every time you launch them, instead of staying in memory and just switching back to them instantly.... so it's not like setting your lowmemory thresholds higher will make your phone "faster", it just changes WHERE the slowness kicks in.

If you don't care at all about multitasking and just want the smoothest possible single-tasking performance, then you should probably use one of the presets that disables ZRAM... probably preset #2.... open /etc/ram.conf and change the "PRESET=" line to 2, then reboot.

Whatever you do though, DO NOT use Juwe11's (or any other "ram hack") script on Talon - it will not work as intended, and will degrade performance.

If you'd like I can give you some more advice on cutomizing your ram.conf beyond just choosing a preset, but you'll have to tell me what exactly is the actual problem that you're trying to fix? If it's just that not enough free ram is showing up in task manager, that's not a problem, that's by design - free ram is wasted ram.
[Galaxy S I9000 Android Development] Krieg Noobie:
Existz, pls help. Whenever I switch on wifi, phone reboots. Tried wipe cache n dalvik still the same. Everything else works fine, bt, bln etc. Tried using kernal cleaner n flashed non oc cwm3 0.3.1 but wifi still reboots my phone.

Running criskelo v74 n was using darkcore 2.7.3 with lagfix enabled.

Pls give suggestion, many thanks for your good work.
[Galaxy S I9000 Android Development] existz:
If your enabling it with drop down or power widget, try enabling it in settings/wireless and network

Sent from my SGH-I897
[Galaxy S I9000 Android Development] Krieg Noobie:
Thanks for the reply, enabling wifi from settings gives error 3 out of 5 tries(no reboot). 2 tries successfully connect to wifi.
[Galaxy S I9000 Android Development] asicman:
That was a typo. I meant to say it [2.3] does not have GPU acceleration for apps of any kind.

Have you seen the google I/O section on accelerated rendering? After watching this, a lot people are getting the impression that google thinks that since multi-core CPUs are gaining ground, there is no need for GPU acceleration for smartphones.
[Galaxy S I9000 Android Development] pramathesh:
I'm getting a no baseband error any help?
[Galaxy S I9000 Android Development] jaikat:
@existz

could you make us a "kernel only" zip flashable through CWM please ?!

also, i plan on using this kernel with Darky_10.1, can someone exrtact the zimage and upload it somewhere... i don't want to download the whole 340mb to use this kernel.. :cool:
[Galaxy S I9000 Android Development] Bavaria85:
This is the kernel only. that's why this thread says,[kernel] and not [rom]. The download is 7mb or something... the 340 is the ram.

But please watch out with what you are doing if you don't know this...
[Galaxy S I9000 Android Development] jaikat:
oh, my bad..

thanks, i guess i can be on my "flashing" way now :D

thanks