yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] flolep:
:-) I am on it since two days. I just want to have very good tests and I will do a full report tomorrow I think :p but I can already say it is good... I just reserve more of my thoughts for my report tomorrow :p

And, by the way, just wanted to say that I am using your version of talon with neutral colors, thanks for that :p

Sent from my GT-I9000
[Galaxy S I9000 Android Development] jrafael:
@ existz

I have been using the Talondev 0.4.3 340MB 1200MHZ with a custom gingerbread port on my vibrant and runs almost perfect (gps is broken) everything else works ok, (screen orientation, softkeys, hardkeys, bluetoot, wifi, internal/external sd cards, etc)

By looking at the init.rc of a native vibrant kernel I notice a difference on the gps services.

Galaxy S.

# create data/gps for GPS demon
mkdir /data/gps 771 gps system
chown gps system /data/gps
chown gps root /sys/class/sec/gps/GPS_PWR_EN/value
chmod 660 /sys/class/sec/gps/GPS_PWR_EN/value

service gpsd /system/vendor/bin/launch_gps.sh
socket gps seqpacket 0660 gps system
user gps
group system inet

T-Mobile Vibrant.

# create data/gps for GPS demon
chown root system /dev/s3c2410_serial1
chmod 660 /dev/s3c2410_serial1
mkdir /data/gps 771 system system
chown system system /data/gps
chown root system /sys/class/gpio/gpio121/value
chmod 664 /sys/class/gpio/gpio121/value
chown root system /sys/class/gpio/gpio120/value
chmod 664 /sys/class/gpio/gpio120/value

service glgps /system/bin/gpsd/glgps_samsungJupiter -c /system/etc/jupiter.xml
user system
group system inet log

#added for STE GPS
service agpsd /system/bin/agpsd
user system
group system inet
oneshot

I don't know anything about how a kernel works, so let me ask this naive questions, is it hard to make those changes on an existing kernel to make it compatible or there is more work to it than just swapping some lines at init.rc ( again please pardon my ignorance ).
[Galaxy S I9000 Android Development] Szighy:
i know this is not the right thread but it's good to post here: the Talondev kernel with the ported CM7 scripts of Zach is excellent...it's working much much better imo (i don't mean it's faster, but you can see the difference in Titanium Backup for example, till now when you ran a batch restore, you always had to push the install button for each app, now you don't :P)
[Galaxy S I9000 Android Development] pikachu01:
I'm not sure if the script will change Titanium Backup centric stuff. I'm leaning more towards that as a Titanium Backup feature, no?
[Galaxy S I9000 Android Development] Szighy:
i am :P right before i installed the scripts i'm 100% sure it wasn't working this way...also...i'm sure because on miui titanium was working how it's working right now on my phone...
[Galaxy S I9000 Android Development] pikachu01:
Ok. Glad that it made a visible difference for you :)

Probably due to one of the setprop settings that made it so.

On another note, I moved the scripts to my new thread here:

[REF] Android Optimizations Tips on XXJVS (and other ROMs) + Zach's Platypus Scripts
[Galaxy S I9000 Android Development] XblackdemonX:
slow updates makes me want to change kernel...
[Galaxy S I9000 Android Development] pikachu01:
What kind of updates are you looking for? XXJVS initramfs changes got released only days ago. :) Isn't that an update?
[Galaxy S I9000 Android Development] jeebspawnshop:
Then change kernel and go post your misanthropic comments on some other poor dev's thread.
[Galaxy S I9000 Android Development] betoNL:
What do you need updated? Which issues you still need to solve?

Most of problems are more user-error related than anything...

Over the head updates and roms and kernels with nice slogans are there mostly to satisfy the general OCFD

(and collect donations :eek:)

«»
[Galaxy S I9000 Android Development] XblackdemonX:
well then why is it still version 0.5.1.1 and not Version 1 ?
[Galaxy S I9000 Android Development] simone201:
Hi betoNL!

I have finally fully fixed CWM for Talon SH....;);)

Glad to hear that eh? :D
[Galaxy S I9000 Android Development] Szighy:
why do you need update if everything is working excellent...
[Galaxy S I9000 Android Development] betoNL:
Yeppers...

That was one thing that needed an update ;):D

Let's roll

Edit- I mean, let me test it...
[Galaxy S I9000 Android Development] simone201:
Oh okok

The new build is T5s, still JVR initramfs to be sure that it is compatible with my ROM....;)

Sending u a pm with the download link + infos...
[Galaxy S I9000 Android Development] existz:
Because its still a development kernel, theres still some stuff that needs to be done before its a v1 'stable' release...such as oc module, fully fixed memory leak, theres some stuff kodos is working on..etc..etc.. Me and kodos96 are both currently without SGS so things are slow...

I dont want to sound like a ****, but i might come off as one.... but if your looking for updates and updates and updates, then this is not the kernel for you.. we dont release a kernel and mark it as a stable release, then turn around and release 15 updates in 2 days with bug fixes like some that are done around here.. even though its still a 0.5.1 release, its prolly more stable than most other kernels that claim its stable, but its still a DEV kernel and not a full v1.0.. And even when it does hit v1.0, then your going to see less updates, if theres nothing that needs to be fixed, then theres nothing i can do.. If you have issues then id advise reporting them, otherwise they will not get fixed...if you dont have any issues, then whats the problem? Just because theres no new release, that doesnt mean stuff isnt being done. I dont release every test on XDA, i have private testers for that, but if i think its stable enough for everyday use, then ill post it here for you guys... I just posted a release a few days ago for JVS and a few fixes, hell theres alot of kernels that are not even updated to that yet...so if you want to move on to another kernel, by all means be my guest.. I also suggest if you want more updates then learn how to hack a kernel and help out, we are always looking for more devs to work on Talon.
[Galaxy S I9000 Android Development] rlorange:
@Existz you asked about lock screen in relation to my query about music app staying at 800mhz. In simply honey I usually use asop lock screen but I did test every possible one including no lock screen and it's still fixed at 800...

Also screen scaling script with max set at 400 didn't change this. Check the captivate talon thread as there was some informative feedback from our knowledge script man lol! maybe a kernel setting you could try to save battery playing music to set it at 400.

willing to test a build if you wish to compile one... The music battery drain really affects me.

**Simply Honey 5.0 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Galaxy S I9000 Android Development] Tatsuya79:
Just name it as Google does with chrome: Talon 51.1.
[Galaxy S I9000 Android Development] pikachu01:
What rlorange mean is that the DVFS frequency for music has been set to 800MHz by default. Semaphore tweaked this to be 400MHz. Could we implement this in Talon?
[Galaxy S I9000 Android Development] rlorange:
Thanks for clarifying picachu. DVFS is new jargon for me.

**Simply Honey 5.0 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Galaxy S I9000 Android Development] rlorange:
@pikachu I just tested with the new modded MIUI music app in simply honey 5 and the screen state scaling script is def keeping below 400 mhz. In fact miui music was running at 100mhz no glitches. Last time I tried miui music was slow and stuttered but Simone seems to found an improved version.

So thanks for all your wisdom. I'll use miui music for a while to see if it can replace stock music. Done might call me crazy but no third party app has performed as well as Samsung stock for me.

**Simply Honey 5.0 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Galaxy S I9000 Android Development] existz:
Ill look into it, there's no DVFS setting just for music, or any other app, system process ..etc, only for kernel drivers such as cpufreq, USB ..etc. so ill have to see exactly what it was that changed and what (if any) other effects it has..like i said, there's no certain settings for just certain apps, tasks..etc, so I'm sure it's going to effect other things as well
[Galaxy S I9000 Android Development] Tatsuya79:
Funny you're talking about this, I was just having my music skipping on screen off with Zach's script.

Changing the off screen governor back to OnDemand seems to solve this.

I'm using mortplayer.
[Galaxy S I9000 Android Development] existz:
Well, i actually started working on a vibrant port and had a few good test versions but then ran into some corruption issues, but i think it was due to some of the infuse wifi port that we done (has now been fixed).. theres a little more to it than just editing init.rc for gps.., the Vibrant uses the screen orientation of galaxys but uses sound of the captivate...so in order to build Talon for vibrant you would have to edit the source to have it build specifically for vibrant where screen orientation is the same as galaxys and then sound the same as captivate..then edit init.rc for gps to work.. I might start working on it again, but right now im without my SGS so things are slow..ive got a few things that needs done once i get my SGS back, then i might look into it again...or if you know any Vibrant kernel devs that would want to work with us and maintain the vibrant version, send them my way
[Galaxy S I9000 Android Development] simone201:
This is the mod that is included into semaphore (and also in Talon SH): https://github.com/simone201/Talon-SH-Kernel/commit/bbb16a6e2dd451be6619c641d365cf24e72a58b2

For me it works fine, is always used 400Mhz with stock player, but i dunno for other users sincerely...

DVFS settings aren't easy to find, if someone knows where they can be just pm me or existz!! XD
[Galaxy S I9000 Android Development] simone201:
If u need a vibrant version of Talon (Talon SH in my case) this is my repo with all my mods + proper mods for vibrant (already tested and working fine, only gps seems broken) and also cwm 3.0 compiled for vibrant

https://github.com/simone201/Talon-SH-Vibrant

It has got all the updates from Talon original, + my mods + fully support vibrant mods!
[Galaxy S I9000 Android Development] stratosk:
Absolutely no problem with 400Mhz. No one reported problems regarding this.
[Galaxy S I9000 Android Development] rlorange:
Ok so it seems stock music app is immune from Zachary script but not third party ones.

Try editing the scale up threshold etc near the end of the script under the sleep tweaks section to fix the music stuttering.

**Simply Honey 5.0 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Galaxy S I9000 Android Development] rlorange:
I really wonder why I run at 800. It has been like this over many rom and kernel versions and survived through clean installs too I remember stock music app used to run well below 100mhz with the screen off and use very little juice once upon a time....

**Simply Honey 5.0 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Galaxy S I9000 Android Development] simone201:
I dunno...but for now use MIUI Music...:o
[Galaxy S I9000 Android Development] existz:
Thanks, ive already got a patch for original Talon for vibrant i made awhile back, I had 2-3 test builds out for a few vibrant devs and all was fine, then ran into a corruption issue, which i believe was from parts of infuse wifi port but thats since been fixed.. It also had working GPS, but ive got a little to much going on at the moment to maintain another release, so im hoping to get someone with an actual vibrant to join camp and maintain it...but thats easier said than done
[Galaxy S I9000 Android Development] existz:
Thanks, ill include it in next version
[Galaxy S I9000 Android Development] simone201:
Well, i am already maintaining the Vibrant porting of Talon SH (as my github says), but seems the GPS is broken, also with the GPS patch (agps) into init.rc....

It took about 1hr to completely mod the kernel to support Vibrant mods, but the users are really happy of the speed and smoothness of Talon! ;)
[Galaxy S I9000 Android Development] Guto ViP:
Existz, i have a question... I'm using Control Freak for OC/UV and with Talon for JVS i can see only 1200, 800, 400, 200, 100 clocks... no more 1000, this is because some version of Talon (i'm using a version ported for I9000B by Rotten)?
[Galaxy S I9000 Android Development] stratosk:
I just want to share my opinion.

You are the best dev here! You and your team! And your work absolutely amazing and inspiring to all of us.
[Galaxy S I9000 Android Development] simone201:
Completely agree with you stratosk!!

Talon Dev Crew is surely the best team ever seen, and in particular existz is the best dev for his professional work!! ;);)

That's why i have choosen Talon Kernel to create my own mod! :):)

I hope in the next month i will be able to port Talon to SGS2 too!
[Galaxy S I9000 Android Development] existz:
Thank you my friend :), and same to you! the work on the OC module is great and will def be added to Talon once i have my SGS back and am able to test a few things...

To others, i didnt mean to come off as an ass..my point to the original poster who said he was leaving to another kernel because theres no updates, is that Talon has TONS of stuff done to it, and probably has more fixes/features than any other kernel..theres the full kernel base update to 2.6.35.13 plus tons of other fixes from 2.6.36 and up...then oc/uv, bigmem version (both first to be done on gingerbread), custom LMK settings with its own app, swap/ZRAM support (only SGS based kernel with swap support), the list goes on and on.. what else do you want done? If theres bug fixes then please post them and they will get fixed, and not just "this does not work", post how to reproduce it, when it happens, what causes it, any changes, if it happens on multiple kernels..etc..etc.. if you took your car to a mechanic you wouldnt just say "my car doesnt work", explain it to me how you would want it explained to you... Unlike other kernels that put out tons of releases a week just with a few small sysfs files tweaked, that can be adjusted from userspace anyways, everything in Talon has already been tweaked, tested..etc.. if something is not in Talon, its for a very important reason. I personally dont know of any other features to add besides the ones on our todo list (which cannot be done until i get my SGS back), other than that, its already been done in Talon.. With some kernels out there that release 10 versions a week with only small sysfs file tweaks, I dont see a point in doing that, its best to fully test everything, and test every possible way before releasing...its best to release 1 solid/good version than 10 .. So my point is, Talon is throughly tested each and everytime before release, we have probably 50+ private testers and we test every possible scenario before releasing to ensure its the best release, unlike others that do no test and have to keep putting build after build after build out tweaking the same thing over and over.. Im not ****ting on their work, but alot of people do not test enough before releasing, just because it works on theirs doesnt mean its 100% solid, every device is different. So just because other kernels put out 100s of releases doesnt mean they are the best...Its about quality, not quantity

Anyways, lol,sorry... /end of rant
[Galaxy S I9000 Android Development] existz:
This is normal, Talon only uses 5 frequency steps, so with 1.2ghz version the 1ghz step is removed. This is done to ensure all the DVFS settings are set correctly in the source and certain drivers are running at the speed they are suppose to ... in the source theres certain settings for certain drivers..for example there may be a setting for USB set at L2 (with 5 freqs thats 400mhz, if you add 1ghz and 1.2ghz both, having 6 freqs, then L2 becomes 800mhz), theres alot of these DVFS settings through out the source and i do not know where they are all at, so to make sure stuff isnt running at double the speed it was ment to be, we removed the 1ghz step. Also with gingerbread, and the way talon is tweaked, using the ondemand governor, its different than how the cpu scaled on froyo/conservative. It uses mainly min and max steps, just skipping through the rest for a split second from time to time. So having the extra step can/will slow things down when the cpu is trying to scale up. Unlike conservative governor, ondemand does not scale through all the frequencies or just scale to a certain frequency based upon the load. The whole logic behind the way the cpu scales and the way other stuff is done with 2.6.35/gingerbread source is different, conservative governor does not work as well as it did on 2.6.32/froyo. With ondemand it scales to max clock faster, making things smoother, and will scale down to min clock faster (going from max to min in one shot instead of having to scale through each step, working its way down) and is good on battery. So basically its a 2 fold reason why theres no 1ghz step, with original Talon I offer both 1ghz and 1.2ghz version, if your on a variant of Talon i cannot support it and advise msg'ing the dev to release both versions if your wanting 1ghz...but if your just wondering why, ^^this is why
[Galaxy S I9000 Android Development] Guto ViP:
Tnx dude! I will stay with 1.2 if is better. :)
[Galaxy S I9000 Android Development] flolep:
Ok. I have to test one or two days more but since two days, I didn't reboot one time and my phone is still smooth but I think there might still be some memory leakage... :-( but for sure I will report later with more details when I will be 100% sure of that last sentence...

Sent from my GT-I9000
[Galaxy S I9000 Android Development] pikachu01:
You can't avoid memory leak. You can only reduce its occurrence. With Zach's scripts, it will make the memory leak appear even more (with the aggressive VM settings) as I offered a way to clear the memory leak (sync + drop caches)
[Galaxy S I9000 Android Development] flolep:
Are you sure we are talking about the same "memory leak"?

When I am talking about it, I mean when a part of all the free memory we have after boot is lost after some hours / days of use somewhere in the limbs and we cannot retrieve it anymore without rebooting. For example, 130 mb free after boot and one hour of use and after killing all "user tasks" becoming 80 mb free after several hours of use and killing the same tasks. There is in both cases the same system applications in memory but there is 50 mb lost. That is what I call the famous memory leak of talon :-)

So I don't understand when you say that memory leak "appears" even more because there is a clear cache... It doesn't make sense with my definition of "memory leak"

Sent from my GT-I9000
[Galaxy S I9000 Android Development] fishcake13:
i think i can speak on behave of most of the noobs (me) who are Addicted to flashing... we thank you all (devs) for the work you do and for sticking around even when you have other phones. we would like to kindly to ignore any retards (not noobs, just retards). they are always the ones asking for updates and reporting all the useless bugs that been fixed 2 post up.

looks like ppl are too scared to post... so there.. i did it.. i said Thank You! XD
[Galaxy S I9000 Android Development] cink40:
for you, for me BLN SMS is not working (flash ficeto base with repartition then juwe: tried with semaphore, DC, Talon and not working) period.
[Galaxy S I9000 Android Development] Tatsuya79:
I was trying to get Voodoo color back, found the commit but...

I have to install a Unix distribution and all this stuff? :D

There isn't a "simple tool package" for windows which could help a noob like me with this stuff? :p
[Galaxy S I9000 Android Development] paratox:
lost root after flashing r2 1600 version. is there a simple way to get it back?
[Galaxy S I9000 Android Development] .:Crack:.:
I'd say flash CF-Root or FuguRoot and reflash talon...
[Galaxy S I9000 Android Development] paratox:
sounds good, will try it! thx!

edit: hmmm, does not work. after flashing cf-root via odin no root.

will try to flash talon via odin and convert to rfs and later back to ext4 in recovery.
[Galaxy S I9000 Android Development] .:Crack:.:
@existz

getting reboots after a while when charging. UV -150 or -125. Never had it before. And when not charging, so being in normal idle 100mhz, I don't get reboots....

Any idea?
[Galaxy S I9000 Android Development] Parkuu:
What's the best OC/UV Set up?
[Galaxy S I9000 Android Development] paratox:
there is no "best". not every cpu can handle the same. try to start with this and go down in little steps per clock.

1200MHz to 100Mhz: -25 -50 -50 -50 -75 -100

for 1200Mhz be careful, less then -25 will be unstable for most devices. some devices maybe can`t handle -25 on 1200 so you have to stick with 1275mV.
[Galaxy S I9000 Android Development] Cy4n1d3:
Current mV for 1200 is 1300 I guess. 1275 was not stable while battery was running low for me with 0.2.1.

Wifi works for me, running 1440 mhz with no uv.
[Galaxy S I9000 Android Development] Ernest05:
I wait for update with working wifi
[Galaxy S I9000 Android Development] mr_at_sgs:
With your kernel I got 3200 points in Quadrant@1.4 GHz. Lagfix on and JVP.
[Galaxy S I9000 Android Development] betoNL:
What you mean? Wifi is working flawlessly here.

Rom: CriskeloGinger v.73

File System : RFS

Kernel Talon 0.2.2 No OCed/UVed

«»
[Galaxy S I9000 Android Development] betoNL:
Request:

Many sgs devices cannot be overclocked....some can be overclocked up to 1125Mhz max.

It would be nice to have 1125Mhz scaling added to the next version!

Thanks

«»
[Galaxy S I9000 Android Development] st4rk:
Maybe they could put that step in the 1.2 max version.

Tbh though I've never got above 1.2 before but this kernel allows me to do 1.3 and amazingly 1.5 (stable so far), but weirdly 1.4 and 1.44 give me reboots so I'm not sure if that is a voltage thing or what.. 1.6 causes obvious graphical problems so I know that one is a no go..
[Galaxy S I9000 Android Development] fylim:
Anyone can advise to how mount cifs? i am using cifs manager and cant seem to work. Do i need to load any specific modules or mount to specific paths?
[Galaxy S I9000 Android Development] tomeks:
One thing

I was listening music for 2h, nothing in bacground (defualt music player for stock JVP) and cpu state was 800mhz for all the time

with stock hacked by supercurio it is 100mhz all the time

sent from my GalaxyS@JVP/talon
[Galaxy S I9000 Android Development] betoNL:
Is you sgs overclocked?
[Galaxy S I9000 Android Development] zs0mby:
does version 0.2.2R2 have BLN...
[Galaxy S I9000 Android Development] jaiiscool:
This is the best thing that has ever happened to my sgs. I get cm7 speeds with all the stock rom goodies. Life does not get better that this. I am using 1.5ghz oc and the fone is flying, almost equivalent to sgs2. never gonna look back now. I love talon........

PS: my sign is not updated yet.
[Galaxy S I9000 Android Development] Ernest05:
hmm... I've a stock xxjvp and wifi has a problem with connect.
[Galaxy S I9000 Android Development] pikachu01:
Yes, drop caches is meant to drop the cached memory (not the /cache), but the physically memory data cached into RAM used as Virtual Memory.

The problem with you not being able to clear more RAM than what's being used is that RAM is used for caching physical data. What you do when you do a drop cache is that you commit the data into the physical disk thus freeing up RAM at the same time.
[Galaxy S I9000 Android Development] flolep:
Yes. Ok. Thanks. I think I already understood that with your previous posts about it and your modified zach's scripts and the intervention of existz about sync command. But you included that drop and sync in your modified scripts and they are launched automatically or I missed something?

Sent from my GT-I9000
[Galaxy S I9000 Android Development] pikachu01:
They are not launched automatically. You will have to manually drop caches/sync. You can use cronjobs to do it or use script manager to do a 1click widget.