yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] existz:
Ill look into the voodoo fm, I might know what's wrong...since we don't actually compile the driver ourselves, we actually just use samsungs precompiled module from jvq, since its newer...but not having it actually set in the source could be causing this, even though voodoo fm tweaks are applied. Also, for the reboots during calls, I also might know what's wrong with it, I had this happen when I tried 2011.03 toolchains, so I dropped down to 2010.09 and they went away (so I thought) .. im not sure if I can solve this with adjusting compiler flags or if we will have to revert back to 2009 toolchains. But the issues are acknowledged and will be fixed

Sent from my SGH-I897
[Galaxy S I9000 Android Development] gonova:
I also have this bug of missing FM Radio option, but.............. I don't have the paid app Voodoo Sound Plus. What can I do without the necessary need of spending money to buy it ........?
[Galaxy S I9000 Android Development] .:Crack:.:
guys just press menu button in voodoo app. press "kernel module options"

click on load driver and set at boot.

fm settings appear then
[Galaxy S I9000 Android Development] Cy4n1d3:
I just tried one of the testbuilds from before the big linux version bump and it doesn't show the rebooting behavior. This one was compiled using 2011.03 toolchain. The current version does reboot - guess I'll trial around a bit more :)
[Galaxy S I9000 Android Development] existz:
Could just be random behavior, I know 100% it happened for me the very first 5min we switched to 2011, thats why we switched to 2010. Which ive had this happen on 2010 also, but it always happened around ~2 battery left, so i chalked it up to low battery since i could never reproduce it with full battery ... This has happened even before we updated to 2.6.35.13. IMO, i don think thats the problem, since with 2010/2011 toolchains we have to actually mess with the samsung modemctl driver to get it to compile with 2010/11 toolchains, so my moneys on it.., but see what happens
[Galaxy S I9000 Android Development] Cy4n1d3:
Yea right :) I have full confidence in you, you're doing some great work here.

The current version 0.4.2 with sourcery '11.03 and w/o overclock does not reboot as well for me. As soon as I compile it with overclock enabled I get reboots however, even without UV and 1000 mhz max. Is the phone app scaling beyond the maximum set frequency - like TW?
[Galaxy S I9000 Android Development] existz:
I dont think so, since going to individual oc builds, ive yet to see it jump to max available clock if max clocks was set lower, for example if set to 1ghz, then it stays at 1ghz... another reason i think the toolchains is causing it, is because with zachs 'snail' kernel, hes getting same issues with it, and im 95% sure it started when he switched to 2010/11 toolchains also.. Which before when i tried 2010 it would always reboot when usb was plugged in, but that was fixed, so now it looks like something with the modemctl driver is causing reboots... ill probably have to end up reverting back to 2009 :(
[Galaxy S I9000 Android Development] Cy4n1d3:
I'll compile the latest build with 09, 10 and 11 toolchain and compare the results... seems to be mainly happening while below ~30% battery for me.
[Galaxy S I9000 Android Development] existz:
Make sure to revert the last 2 commits for modemctl toolchain changes when compiling with 2009, it will give the most accurate results with 2009, that way it doesnt use a precompiled modemctl driver...

https://github.com/existz/linux_gt-i9000-gb/commit/83ae1d3807fe4630727d45321fdd574f725c2b1c

https://github.com/existz/linux_gt-i9000-gb/commit/e4be2e0734c8ac8b3e05ce3887e63d6d8cb9ed91
[Galaxy S I9000 Android Development] Sarutobi:
The same Problem here, i used talon 0.22R2 before without any Problem. I can use SIO + Performance Governor at any OC and my SGS is stable running. Now I use the new talon 0.4.2 and when i use the tegrak overclocking to set OC my SGS reboot. The same Problem is with Voltage Control 4.0.0 :( I've deinstalled tegrak before to use Voltage Control so that i've only one OC-APP installed. I can't use any OC-App to change the the Frequencies.:o
[Galaxy S I9000 Android Development] existz:
Like I said, tegraks app is only temporary ...bare with me and things will go back to normal... actually messing around with a hi-performance version, but don't know when it will get released, I want to mess with a few different setups, but stability comes first...then ill be able to put some time into it. But right now im messing with 200-400-800-1000-1280-1450 (yes it still goes into deep sleep mode, so battery shouldn't be a problem when ideling. )...also, noticed alot of other android devices also only go down to 200mhz. Whenever im happy with it, ill release it as a seperate version, but got a few other things I have to pay attention to first

Sent from my SGH-I897
[Galaxy S I9000 Android Development] zacharias.maladroit:
well, I can't say for sure for the samsung kernel since we're forced to use (samsung) prebuilt proprietary kernel modules and can't rebuild them - thus interactions are not really predictable

but

at least on my cm7 kernel

- 2.6.35.13

- 2011.03

toolchain can be excluded from the "culprit list"

and if the same reboot issue also doesn't occur with hardcore's speedmod kernel (he's using 2011.03 toolchain in a same manner) - it's definitely not the toolchain

but most probably recent changes to the kernel that cause this issue

it's rather difficult to troubleshoot this issue after all these changes

the only way would be to track it down in a "git bisect" manner which takes much time and lots of builds ...
[Galaxy S I9000 Android Development] existz:
Well, I kind of agree, disagree....only reason because when I was using 2009, issue didn't happen, then the only change we made was 2011 toolchains and issue happened within the first 5min of switching to it, no other changes. So I switched to 2010 and issue stopped, atkeast until it gets around 5~ ,then it happens. I had this issue wayy before 2.6.35.13, so I highly doubt thats the issue. But with the only change being toolchains, I get the problem. Ill revert back to 2009 and put a test out just to see if it still happens.

But what really makes me suspect the toolchains is, when we had talon out with 2009, you had snail out with 2011, and the issue started in your release with it. So if it was talon specific, it would have happened with original talon. But then as soon as we switch toolchains, issues happens on talon

Sent from my SGH-I897
[Galaxy S I9000 Android Development] paratox:
when i read this i could remember the same behavior. every reboot / shutdown happened when battery was below 30%.

so now i have my temporary fix - don`t let battery go below 30%!^^
[Galaxy S I9000 Android Development] zacharias.maladroit:
hm, so it's kind of loosely related to the battery state

how about lowering the battery polling intervall and see whether that makes a change - say to at least 10 seconds (afaik that's the stock value) ?
[Galaxy S I9000 Android Development] kicaj222:
When i want to change settings of cpu with control freak there is no problem,

Then i safe as boot settings, after reboot the settings are the same as before. freak does not create file system/etc/init.d/S_volt_scheduler

hel me
[Galaxy S I9000 Android Development] woj999:
For now one reboot. No UV, 1200MHz. I read rss in Justreader - load big rss with photos and phone frees and reboot.
[Galaxy S I9000 Android Development] corgar:
ram managment is not good with latest version. got some lag after some hours of use.
[Galaxy S I9000 Android Development] pedroomnia:
I have no reboots but I can not do oc withTegrak above 1200.

Wonderful kernel. ;)
[Galaxy S I9000 Android Development] existz:
You can try putting a 25-50mV UV on 1200, sometimes if its to much voltage, it can cause instability also... i have to use 75mV on 1200 for it to be 100% stable for me.

Also, note on the reboot, i just need reports of reboots during phone calls, other reboots can be caused by to litte/much UV instability. But the reboots during phone calls seems to be an issue possibly caused by toolchains.
[Galaxy S I9000 Android Development] mawardi:
I don't know what's wrong but the latest version seems to break my back key. Any idea why?
[Galaxy S I9000 Android Development] existz:
Try reflashing... it could be from a bad flash, or might have dloaded the wrong version, make sure -i9000 is at the end of filename. But try reflashing
[Galaxy S I9000 Android Development] betoNL:
Pimp myCpu and control freak apps are behaving weird on the 0.4.2...

Try setCpu app from here:

http://xdaforums.com/showthread.php?t=505419

and for changing the governor use the free No-frills cpu control app....

«»
[Galaxy S I9000 Android Development] jeebspawnshop:
Xan's Voltage Control is working 100% for me on the latest kernel.

Has worked with every ROM I've ever used, actually.
[Galaxy S I9000 Android Development] existz:
Same here... there were some cleanups to initramfs/symlinks, for those with issues with CF..etc.., try uninstalling the app/wiping settings and reinstall then resave boot settings
[Galaxy S I9000 Android Development] mawardi:
Silly me. I downloaded file from Captivate forum. It's identical. All is well now. Thank you.
[Galaxy S I9000 Android Development] rlorange:
@exitz

With 0.4.1.8 no in-call reboots. I did get them every time on two versions of snail kernel. Does this test build have the suspected culprit toolchains? I might stick with this build for now till you create your oc module app.

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] existz:
Well, its using 2010.09 instead of 2011 toolchains. But im suspecting it because of the toolchains, because with 2009q3 i did not have this issue then as soon as i compiled with 2011 it started happening...then with 2010 it went away so i thought, but seems to happen when low on battery. Im running back on 2009q3 right now with no issues, but need to test it more and get it down to low battery. Will probably include 2009q3 in 0.4.3.1 test
[Galaxy S I9000 Android Development] rlorange:
Ok thanks Existz. Your relentless dev work is impressive. Strange I dont usually have many issues to report on test builds like I read here with the official release. I did get call reboots on snail which was really annoying so ill stick with 0.4.1.8 for now

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] Cy4n1d3:
All testing done without undervolting, overclocked frequencies were done with adjusted voltages (higher than stock talon due to crappy cpu :)) which were supposed to be stable.

Max. frequency was set to 1000 mhz, regardless of kernel!

Testing was done with battery charged to ~15% before each run as problems seem to occur faster when low on battery.

Toolchain 2011

1000 mhz version: no reboot (~20min call) - might have been a lucky draw

1200/1300/1400 mhz version: reboot during call (2-3min max.)

Toolchain 2010

1000 mhz version: reboot (~5min call)

1200 mhz version: black screen (no wakeup) & reboot shortly after during call (1-3min max.)

For sourcery 2009 testing I fully reverted the 2 mentioned commits and once more adjusted the toolchain-path.

Toolchain 2009

1000 mhz version: reboot (~14min call)

1300 mhz version: no reboot (battery going low) 17% -> 3%: 21 minutes

Also, just as you already pointed out existz, phone app does not use higher frequencies than max. set with control freak. Checked using cpu spy with reset stats while calling :)

For me 2009 sourcery seemed to be the most stable, especially while overclocking - 2010 + 2011 ended up rebooting within the first 3 minutes each on multiple trys.

Strangely I get reboots much quicker using the OC-kernel although all overclock is disabled - I don't know what's going on?
[Galaxy S I9000 Android Development] existz:
Im back on 2009q3 right now, so far so good, no reboots during phone call... usually it reboots by now, but still need to test it a little further.

Which if it is not caused by the toolchains, then it shouldnt be to hard to figure out. With 0.4.1 there were no reported reports of reboot during phone call, and up until we switched toolchains, i never had this problem... so from 0.4.1 to the time we switched toolchains, it has to be somewhere in between...Which most of the commits were color related, and have no impact on it..so it only leaves like 3-4 commits
[Galaxy S I9000 Android Development] Cy4n1d3:
I'm going to play around with the compiler flags a bit and fall back to sourcery 2009 as it's a lot more stable, just as you pointed out...
[Galaxy S I9000 Android Development] kodos96:
Wow, thanks for the link, I was not aware of this - it looks like I actually have some competition.... an LMK configurator designed by someone who actually understands how android's LMK works, and doesn't just set the kernel minfree values like all the "ram hack" scripts, but actually sets the framework settings as well... and unlike mine, has a nice gui around it. I'll definitely need to look into this some and start comparing notes with the the guys who make it.
[Galaxy S I9000 Android Development] jeebspawnshop:
I just checked that out now, too. Looks very promising and really useful.

Thanks to corgar for bringing it up, and to kodos for maybe implementing some of that magic in to Talon ;)
[Galaxy S I9000 Android Development] jlieu:
Your kernel ROCK my SGS!! Thanks.

Keep up good work!
[Galaxy S I9000 Android Development] zacharias.maladroit:
and 2009q3 toolchain indeed seems to solve it - at least to the few reports in my "snail" thread :)

oh well, if we can't use a newer toolchain there's still the optimization flags ;)

and stability is a MUST ^^
[Galaxy S I9000 Android Development] burakgon:
Nice kernel.. Wifi bt gps all is good. Quadrant is arround 3000 at 1200. I will use tegrak now. Thanks
[Galaxy S I9000 Android Development] samiulislam16:
good kernel, no prob yet in stock freq.:)
[Galaxy S I9000 Android Development] betoNL:
Hello team,

Since many developers are playing with the sgs2, I wonder if we have this feature on the 0.4.2 ?

HDMI via USB (CEC & HPD)

If not, that could be a nice add to the next build, since many users already have an adapter.....

«»
[Galaxy S I9000 Android Development] betoNL:
These reboots...happen only to overclocked devices?

Ext4 or RFS?

Cause I dont have them. Could that be a (mod) rom thing?

I am always on rfs, not overclocked, but undervolted.....very stable , no issues...

But I already posted it before,,,,:o
[Galaxy S I9000 Android Development] rom08:
No reboot for me neither. Oc version on a ficeto jvq base rom. I use tegrak app for a little uv but i don't have any problem even with phone call.
[Galaxy S I9000 Android Development] ngochuy:
this is such a good idea, awesome, hope Existz will add this feature in the next version.
[Galaxy S I9000 Android Development] deezid:
Same here, pretty stable till now :D
[Galaxy S I9000 Android Development] LukeSP:
Will this kernel auto apply lagfix to My phone after flashing? If yes, is there anyway to disable it.
[Galaxy S I9000 Android Development] Lazy Rich:
Funny, looks like this kernel can give me extra battery without beein charged. Take a look at the picture and see what I mean.

At the point where the battery raises (from 18 to 25%) I changed the kernel from the oc one (1200) to the normal one.
[Galaxy S I9000 Android Development] ascariz:
i lost my notification area after flash talon.
[Galaxy S I9000 Android Development] mawardi:
Well, auto brightness seems to change screen to green.
[Galaxy S I9000 Android Development] Rootax:
0.4.2, 1.2ghz version. No reboot, but the memory managment is not that good, I've lags after some times if I don't clear the ram.
[Galaxy S I9000 Android Development] betoNL:
Nope, at least I think so....

But if you want to be sure, just create a Voodoo folder in the internal SD and inside it another folder "disable-lagfix" like this:

/sdcard/Voodoo/disable-lagfix

«»
[Galaxy S I9000 Android Development] zerkai:
I wouldn't be able to test this out on this kernel, could I? Unless I disable the built in memory config?
[Galaxy S I9000 Android Development] zacharias.maladroit:
shouldn't it be familiar to you ? :p

afaik you also observed it with my platypus kernel ^^

2 reasons:

- battery stats generally aren't very accurate on samsung kernels (on cm7 it should be somewhat more accurate since atinm rewrote the algorithm)

- the polling is limited to once every 60 seconds
[Galaxy S I9000 Android Development] existz:
If you reboot with usb plugged in, it can throw battery calibration off...theres been times where mine has went from 60% down to 7% just by rebooting with usb plugged in...then it will actually start to recalibrate itself, climbing back up...sometimes its not as big of a jump, but it does happen....i always recommend to never reboot with usb plugged in, messes up battery calibration
[Galaxy S I9000 Android Development] Mangus_U*RA:
One self reboot today while it was in standby...

Sent from my NES using Duck Hunt
[Galaxy S I9000 Android Development] betoNL:
Originally Posted by kodos96 Wow, thanks for the link, I was not aware of this - it looks like I actually have some competition.... an LMK configurator designed by someone who actually understands how android's LMK works, and doesn't just set the kernel minfree values like all the "ram hack" scripts, but actually sets the framework settings as well... and unlike mine, has a nice gui around it. I'll definitely need to look into this some and start comparing notes with the the guys who make it.

Well I am running it already ....I hope I am not messing things up... am I ?
[Galaxy S I9000 Android Development] zacharias.maladroit:
existz, there's a report from a user in a german forum that there's issue with apps gaining root access

it first occurred with 0.4.2 for him

the apps in question are: TitaniumBackup (paid) & RootExplorer

@all:

anyone else had issues with apps gaining root access ?

at least for me - it has been fine so far ...
[Galaxy S I9000 Android Development] existz:
Its been fine for me also
[Galaxy S I9000 Android Development] jeebspawnshop:
No root issues here either.
[Galaxy S I9000 Android Development] Lazy Rich:
Dammit, you got me ;) I think I have to recalibrate my battery, last time was back in november I think :)

Btw., no problems with root here, TB, Rootexplorer and stuff like this works like a charm.

Sent from my Galaxy S powered by MIUI Rom
[Galaxy S I9000 Android Development] betoNL:
Are you sure that german guy was not confusing TalonDev with the galaxian kernel?

Anyway if that is not happening to you, it means that is probably not kernel related and you dont have to ring any bells...

Some bug reports without any background information, are just waste of thread space imho

«»
[Galaxy S I9000 Android Development] komoornik:
I think there are some root problems with newest RootExplorer.
[Galaxy S I9000 Android Development] corgar:
ok now i'm in a dark room, lowest brightness set to auto and i got a green tint. Can't read nothing on my screen, need to set it to manual and applied lowest brightness manually. All fine now.
[Galaxy S I9000 Android Development] rom08:
No problem here
[Galaxy S I9000 Android Development] Tatsuya79:
I had this problem while installing Juwe's rom 5.1 which included Talon 0.3.1.

I reinstalled the rom again and it was resolved.

I think sometimes CWM fails.
[Galaxy S I9000 Android Development] The Undertakerr:
Yes, I think it's time I report something about this.

In a Dutch SGS forum, many people lose rootaccess when coming from semaphore kernel. They have rootaccess with semaphore, but lose it when flashing to Talon. Regaining root again when flashing back to Semaphore.

Reflashing the Custom Rom(which includes Talon) doesn't help, only al clean build-up from Stock to Custom with Talon helps. This helps everytime.

I believe this is not Talon's fault.

It seems that leftovers from semaphore give the Talon kernel a hard time to get rootaccess.

Just reporting, wanting to help...
[Galaxy S I9000 Android Development] fishcake13:
just switched from Speedmod to Talon.... no issue with root access. no reboot during call...

non OC version.
[Galaxy S I9000 Android Development] kevin2516:
This kernel is awesome, I'm getting a green tint at low brightness when turning off the screen, could you guys fix that like in zac's kernel? other then that, everything is good.
[Galaxy S I9000 Android Development] mohanindia:
good so far

installed the kernel along with Jetpack 1.1

working well...less battery drain

small issue with GPS..but overcame it with the gps aide from market...

no issues noted with wifi...
[Galaxy S I9000 Android Development] mawardi:
Try to restart. It works for me.
[Galaxy S I9000 Android Development] rom08:
I have this green tint when shutting done the screen also. Reboot doesn't change anything. Plus i use fbreder and when i lower the screen brightness to the minimum it becomes green. But no big deal because raising the brightness a bit make the green disappear. The colors are relly good in any other case. Oh and btw i also try to reflash the kernel also. Maybe something related to voodoo colors?
[Galaxy S I9000 Android Development] pikachu01:
Yes, it's related to Voodoo Color. Try increasing the green a bit (along with the others to achieve a balance)
[Galaxy S I9000 Android Development] kevin2516:
nvm about the green tint, i just flashed a CRT animation mod :D and it's all good now hehehe, i wonder how long im going to stay away from cm7, i love the battery life on stock :D
[Galaxy S I9000 Android Development] Mangus_U*RA:
+1

I've reported this problem many times.

But I think it's related to the minimum brightness value set in kernel.

With this value, when you set gamma on voodoo control too low, you get green tint on lower brightness values.
[Galaxy S I9000 Android Development] mab71:
existz and other devs, these are the files in my init.d folder, which do you recommend me to remove? thanks...:)
[Galaxy S I9000 Android Development] jlieu:
How to print screen? and i'm using the voodoo color profile.

what green tint? i didn't noticed that...
[Galaxy S I9000 Android Development] .:Crack:.:
Remove S97sdcardspeedfix.

The rest is OK.
[Galaxy S I9000 Android Development] gonova:
Phone reboots during call

Here is a bad news to report of rebooting during phone call.

Althought I am trying the Snail12_T7, it is still meaningful to share here because the base is Talon with a "fix" that we expect to fix the reboot problem.

Now I am using Snail12_T7 with Continuum6.1.

Today I was using Samsung stock headlphone talking to my gf for 2 min and the phone auto reboot.

Then I wait for a centry-long reboot with all those SD card media scanning, and I call my gf back without any headphone/handfree. I can successfully talk for almost 10 min. After I say "Bye" and pull the phone off from my face, the screen is black and I cannot press the "END" button. After a few seconds, the phone reboot.

Luckily the phone call ended up at a peaceful bye, but unfortunately this smoothest/fastest great Talon-base kernel is still not reliable for daily use.
[Galaxy S I9000 Android Development] zacharias.maladroit:
remove _99ramset

it might interact with the LMK settings from Talon

thanks for the report gonova,

that's clear - that's why I posted that I will upload some more builds (for snail) to test & see whether they stabilize things

maybe meanwhile existz can upload a Talon build with 2009q3 toolchain built only ?
[Galaxy S I9000 Android Development] .:Crack:.:
AFAIK _99ramset is created by Talon so no need to remove! ;)
[Galaxy S I9000 Android Development] zacharias.maladroit:
:eek:

my bad

^^

didn't notice that file so far

sorry kodos :p
[Galaxy S I9000 Android Development] TonyStark R.I.P.:
Hey zach I'm a long time user of Talon on the Cappy side, we've spoken on Talon site. I am trying out Galnet MIUI right now (CyanogenMod based) Do you know if it's copacetic to use this kernel on this set-up?
[Galaxy S I9000 Android Development] mab71:
Thanks...