yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] kodos96:
Yeah, I did away with the whole presets system, since nobody seemed to be using it and it just made everything more complex. Now you just edit the settings by hand if you want to (or uncomment the commented out settings at the bottom of the file if you want the old preset #7 settings).

BTW, for the next version I'm going to be reverting back to default settings pretty similar to preset 7 - the new settings in 0.3.x+ were kind of an experiment I was doing that hasn't panned out and has caused some problems, so I'm going back to more normal-ish settings.
[Galaxy S I9000 Android Development] kodos96:
Hey, could you edit this post and remove the zip? It won't actually harm anything, but it won't accomplish anything either, and will just confuse people. If the script isn't getting autogenerated for you, just delete ram.conf and reboot.
[Galaxy S I9000 Android Development] rlorange:
Ok deleting ram.config is the way to go thanks mate :)

**Simply Honey3.9, Talon 0.4.2 t1 kernel1.3ghz**
[Galaxy S I9000 Android Development] tzyn:
Can anyone upload the latest version (0.4.x)?
[Galaxy S I9000 Android Development] zacharias.maladroit:
could one of you guys test mp3 playback with an "older" ROM such as JVH (I'm currently Base ROM by Ficeto - JVH) but current Talon test kernels ?

it could be that the higher battery consumption during MP3 playback indeed is a regression by the move from 2.3.3 to 2.3.4 (or JVH -> JVP for me)

and not kernel related at all (unless of course it doesn't appear with the stock kernel - in that case we might be missing some needed changes)

thanks !
[Galaxy S I9000 Android Development] darckengel:
It's kernel related, i don't have this issue with Semaphore (Juwe 5.0).

But i have it with talon/snail
[Galaxy S I9000 Android Development] Cy4n1d3:
I've been migrating from JVB till JVQ, keeping my system and user data.

Just had Ubermusic running for 25 minutes on speaker and lost about 2%, frequency used according to cpu spy was 100 mhz. Can't say I'm noticing any massive battery drain...
[Galaxy S I9000 Android Development] zacharias.maladroit:
thanks !

ok, then it must have been one of the commits between 0.2.2 and 0.3.1

that introduced this regression

(currently running a modified 0.2.2 still with CF-initramfs and probably fixed bluetooth)

another thing:

cf-root doesn't seem to work with newer toolchains ("toolchain sorcery")

on the other hand with voodoo initramfs bootanimation seems to be more fragile in terms of optimization flags

anyone know what initramfs hardcore uses for his kernel ?
[Galaxy S I9000 Android Development] darckengel:
Its with stock music app only.
[Galaxy S I9000 Android Development] zacharias.maladroit:
if this is limited to stock music app - so how is this NOT a ROM related regression ? :confused:
[Galaxy S I9000 Android Development] darckengel:
Its the same with criskelo rom.

- Semaphore with 2 differents roms => OK for the 2 tests

- Talon with 2 differents roms => KO fo the 2 tests

=> Kernel issue.

With Talon, the music player stacks at 800Mhz that's the cause of the battery drain.

With Semaphore its 90% at 100Mhz and almost never more than 400Mhz.
[Galaxy S I9000 Android Development] Hrithan2020:
I am having the issue with PowerAmp as well. :(
[Galaxy S I9000 Android Development] darckengel:
I didn't try poweramp, i tried miui and i didn't see the issue.

Poweramp and even miui uses more battery than stock, so i prefer stock :)
[Galaxy S I9000 Android Development] zacharias.maladroit:
ok, one more question

then I'm logged off ^^

how much battery does mp3 / music playback consume with e.g. semaphore kernel

for, say, 2 hours

and how much talon with the frequency at 800 MHz

if you don't want to do it - maybe someone else can

(would be interesting to know if this has been done from several different people on different phones)

many thanks in advance !
[Galaxy S I9000 Android Development] darckengel:
I don't tried long tests semaphore music to see how much battery it uses.

But i hardly believe that at 800Mhz with higher CPU Voltage and more CPU usage you can use less battery than at 100Mhz.

I don't have precise stats of that but my consumption is about 2-3% hour, (-100 UV at 100Mhz) with kernel.

(As i'm at work, i can't test at all ^^ )
[Galaxy S I9000 Android Development] lohho:
Did you have a look on the link i posted ?

800 mhz != 800mhz when using stock player.
[Galaxy S I9000 Android Development] rlorange:
I might try replacing my player from the previous version of simply honey which def ran at 100mhz

**Simply Honey3.9, Talon 0.4.2 t1 kernel1.3ghz**
[Galaxy S I9000 Android Development] darckengel:
Ok, i will make a try tonight, but this theory seems a little strange.

When i reduced max CPU at 400Mhz, the cpu stacks in the logs at 400Mhz, if the theory was exact, it should continue to consider the states as 800Mhz
[Galaxy S I9000 Android Development] rlorange:
Yep still running at 800mhz with a music apk from a different rom

**Simply Honey3.9, Talon 0.4.2 t1 kernel1.3ghz**
[Galaxy S I9000 Android Development] Hrithan2020:
Yes, for me , it uses the max CPU available, except in 1 GHz, where is resets to 800 Mhz sometimes.
[Galaxy S I9000 Android Development] darckengel:
Can someone do this test in talon (i will not have the time today and i will be on hollidays after):

With talon kernel (more reliable results if on airplane mode):

- Charge Full battery

- use 1h stock music player screen off and watch the battery drain

- Charge Full battery

- set CPU at 800Mhz min and max, don't use anything and screen off for 1h and watch the battery drain.

If the results are above the same so the Music player uses really the CPU at 800Mhz and drains battery.
[Galaxy S I9000 Android Development] existz:
So does this happen with non-oc versions and just happens with OC versions or does it happen on all of them?

Also can i get a list of the music players that this happens on, and the ones it does not happen with
[Galaxy S I9000 Android Development] betoNL:
Well....just want to make it clear:

I don't have this issue.

Here, it doesnt hang on 800Mhz while listening to music through the stock music player or any other player

And with both versions: 0.3.1 and 0.4.1

And I can put it on video if anybody doubts it....

But then again, I never had BT / Wifi / Gps issues, with ANY kernel (voodoo or CF initramfs)

And I use these features on a daily basis.

The rom I use is CriskeloGinger ( for months in a row) and I am always on rfs.

And I dumped TW Launcher the same week I bought the sgs ( last year -Eclair times)

I also froze a bunch of Google/Samsung stuff using Titanium Backup app (months ago)...

So, the only thing that still doesnt go on my SGS is.. overclocking... .

But gladly, for the smoothness and responsiveness, I dont really need it....maybe only when I am running iGo navigation software, but I guess what heavy programs like iGo concerns, it is more related to the "insufficient ram issue" which is, imho, still the main "con" of the i9000

Greetz
[Galaxy S I9000 Android Development] tincmulc:
The 800 MHz has to the with DIDLE (aka deepidle) which should allow to the CPU (the ARM-core) to shutdown while still playing music, which so far only works with stock Samsung player.

The definite test, to see if this is Talon related, would be to use a stock rom with a stock kernel and test mp3 playback with cpu time app (play some music, go to app hit restore, than reset and turn the screen off, than wake the phone after a minute, press refresh and see which state was used most, and post your results here)(so far I discovered only MP3s can play in this low power mode).

That is, if the stock kernel writes the time_in_state at all?
[Galaxy S I9000 Android Development] Hrithan2020:
If that were the case, the issue wouldn't have come with PowerAMP which doesn't have access to deep idle state.
[Galaxy S I9000 Android Development] Padillla:
After 10 days of intensive use... heres my 2 cents.

After two clean flashes with Darkys resurrection edition, vodoo lagfix enabled and disabled, the front camera is not working, shows the usual 4 images messed up.

The performance @1.4 GHz with vodoo lagfix is awesome and the battery lasts 10 hours in average. Not a single reboot or bootloop, all works fine and smooth (except the front facing camera)

SetCPU CANNOT be used, it frozes everything (I don't know why i paid for that sh!t)

But Control freak do the job better, and set OC on boot for free!

Played 3D games, THD games with ChainFire3D, no lag, no force closes.

Opened a lot of tabs in Dolphin HD, we have lag, but is probably a DolphinHD issue, it is getting worst every update.

2190 in Quadrant.

Too hot processor using it while charging, usual from SGS, but setting it to 1GHz for 10 minutes will help us to cool it down.

My recommendation... do a clean flash, enable voodoo and buy CF3D to have a great phone, and buy spare battery just in case.

My question: Someone knows if i can do something for the front camera? I really like how this kernel performs and that's the only black dot.

Is probably happening only to me, I didn't find anything in OP about that...
[Galaxy S I9000 Android Development] komoornik:
I don't recall seeing Darky Rom 10.5.

Am I missing something here? :D
[Galaxy S I9000 Android Development] betoNL:
Front camera is a firmware issue, not kernel related, but the with latest versions of Fring and Skype you can use the front camera reasonably well, specially on Landscape position..

And I can't even remember the last time I did a fresh install...every full rom update of Criskelo's is a "non-wipe" and I just flash one upgrade over the other...

«»
[Galaxy S I9000 Android Development] kodos96:
Can you elaborate on what you mean by this?
[Galaxy S I9000 Android Development] zacharias.maladroit:
sure,

"toolchain sorcery" (I'm using this in my CM7/MIUI kernels and hardcore in his speedmod kernel)

you're prebuilding the samsung modem driver with the stock toolchain and stock optimization flags, modify Makefiles; then build the rest of the kernel with the new toolchain (e.g. 2011.03) with more aggressive optimization flags

voodoo initramfs bootanimation more fragile:

bootanimation still works when adding several patches & aggressive optimization flags with CF-initramfs

but the result with voodoo initramfs is a screen that stays black

on the other hand it works with 2011.03 or newer toolchains,

with CF initramfs it would stay at the samsung bootsplash like forever :P

will send you more info via PM later
[Galaxy S I9000 Android Development] flypubec:
I've tried to build talon kernel 4.1 with Sourcery G++ Lite 2011.03-42

and it freezes the first boot flash.

Then I've used the Sourcery 2010.01 and it works fine.

Btw, how do you build only the modem driver and why is it necessary to build it with default flags ?
[Galaxy S I9000 Android Development] tincmulc:
In my experience it doesn't in any other player. Stays at 100 mhz for anything but stock samsung mp3. I already did a post about this a while back, where I did some tests. All this was using TalonDev 0.3.1 1440MHz Oc version.

I find battery life for music playback quite good, and if it were really stuck at 800 and its high voltage, I think it would be noticable...

Someone will have to test. We need to know if this is just a cosmetic upstream issue from samsung(much more likely, since I saw this "bug" on galaxian too) or is is this a bug in the kernel. If noone will I will do it this weekend.
[Galaxy S I9000 Android Development] existz:
Use 2009q3 its the most stable, you don't have to compile modem driver separately, just build and flash...its what I always use with Talon.., 2011 will not work without alot of hacking, 2010 boots but will reboot when usb is plugged in

Sent from my SGH-I897
[Galaxy S I9000 Android Development] flypubec:
Well I don't have any issues with CS 2010.01 and USB

I 've noticed that after the build there is no drivers/misc/fm_si4709/Si4709_driver.ko (I expected it since it is mentioned as target module in the README.txt)

Is this normal ?

The FM radio is working fine though.

So far I only have one issue, which is the greenish (16 colors like) screen under low light.

I am using the sensors.default.so from CM7 build and self tweaked autobrightness values in moded framework-res.apk to achieve my prefered autobrightness settings (at least for my HW)

My tweaked brightness level values are set to [2, 35, 75, 155, 255] and the result with talon kernel is that with the lowest level (values 2) I get the greenish effect.
[Galaxy S I9000 Android Development] Padillla:
LOL you are right! Corrected, is 10.1 ...!
[Galaxy S I9000 Android Development] LowRider150:
Great kernel ;) But is there a chanse to have smartass or interactive governor ?? It will be great
[Galaxy S I9000 Android Development] zacharias.maladroit:
didn't you read existz post some pages back ? :)

the issue is that smartass doesn't scale down and has some issues with high frequencies

interactive doesn't provide a consistent experience overall and tends to have some lags from time to time
[Galaxy S I9000 Android Development] existz:
Actually the FM module is there, I believe its included in the prebuilt modules zip if im not mistaking. The build script copies most compiled modules to the initramfs, then it will extract a prebuilt zip we have of already compiled modules.. (in /usr dir), these are newer modules from JVQ, since all we have is JVB source, these are newer modules then what we can compile.

Sent from my SGH-I897
[Galaxy S I9000 Android Development] flypubec:
Oh I see now that the radio is included in prebuilt modules, although it has a different name there

Btw, in the meantime I managed to get rid of greenish efect on the lowest brightness.

In the /include/linux/tl2796.h I've made the following change:

-	BV_1 = 0x552D,
+	BV_1 = 0xD8722A,

since I figured out that voodoo stuff is doing some gamma offset and for the BV_1 probably falls bellow zero.
[Galaxy S I9000 Android Development] existz:
Awesome, will def try those settings out...I also got some mDNIe settings that I havebt pushed yet.. will get those up afterwhile.. the sharpness is better IMO... also, make sure to build off of the 0.4.x-dev branch for latest changes.. its our experimental branch we test stuff before putting it in talon...but usually 0.4.x-dev becomes main branch...we just put stuff up to test before making it final.

Sent from my SGH-I897
[Galaxy S I9000 Android Development] rlorange:
Aaaargh! Music player stubbornly refuses to run below 800mhz.

No idea if this is rom or kernel related.

**Simply Honey3.9, Talon 0.4.2 t1 kernel1.3ghz**
[Galaxy S I9000 Android Development] rlorange:
**Simply Honey3.9, Talon 0.4.2 t1 kernel1.3ghz**
[Galaxy S I9000 Android Development] tanivula:
Existz: Still having a funny issue with flashing new roms (having to manually mount /system & /data). Must be something to do with the GingerReal ROM. Any idea what to tell the dev/chefs to change?
[Galaxy S I9000 Android Development] existz:
Not sure exactly what needs changed yet, havebt really looked into it much, but I do know its just how the installer script is setup to mount system or data...apparently there's 2 ways in doing this...one of them does not like voodoo initramfs.

Sent from my SGH-I897
[Galaxy S I9000 Android Development] tiwag:
I found out the same. When using MIUI 1.0 music player the CPU is working with 100Mhz frequency all the time (display on or off).

Problem with 800Mhz only occurs with stock-music player while display off.

Using Juwe v5.1 XXJVQ

Btw: CPU never can use deep idle during decoding a mp3 stream. Thats a myth ...

--

sent using recycled bits & bytes
[Galaxy S I9000 Android Development] mariotme:
The 800Mhz bug while using atock player seems like its a jvq bug coz am running continuum v6.1 rom and tegrak kernel and I also have that issue. Just my 2 cents
[Galaxy S I9000 Android Development] darckengel:
No the right test is to compare 800Mhz standart consomption to 800Mhz with music player ...

btw i don't believe much in decoding mp3 in deep iddle state, it's like driving a car without oil ...
[Galaxy S I9000 Android Development] flypubec:
Funny is that at boot animation there is now a "CGA" effect (not the greenish one), but once it boots colors are perfect at all brightness levels.

And yes, I am using the latest code from the branch 0.4.x-dev
[Galaxy S I9000 Android Development] betoNL:
800Mhz bug??

800 Mhz bug?

If it is a bug, somebody explain it to me( pretty please, with sugar on top), why dont I have it?
[Galaxy S I9000 Android Development] Hrithan2020:
If it is not a bug, somebody explain it to me why I don't have this particular issue with any other kernels on my ROM ?

So, it is obviously some combination of ROM or other applications which is causing the kernel to have this issue. Hence, a bug..

And considering the responses, it doesn't seem limited to just one ROM. ( I am on gingerCriskelo v75).
[Galaxy S I9000 Android Development] betoNL:
So, your rom is Criskelo's? Funny, so is mine !

And I have been testing many kernels lately, but not the rom! I am on CriskeloGinger since almost the beginning..

I flash one CriskeloGinger over the other, making full use of the "non-wipe" thing, no fresh installs, never needed to restore a backup...

I still working on a kind of thread with videos (video thread)...

But in the meantime, you can have a look on this video :

http://www.youtube.com/watch?v=HInp0AYRGTM

Since I don't have any of the issues reported on this and many other threads,

the video is a good idea, kinda walking the walk and not just talking the talk

Ususally I dont overclock, but just did it for the video, running the latest versions of talon, criskelo's and voodoo sound plus app, but I was getting same results with the older versions....

On the video (at the end) you can see also front camera in action with Fring app, but it's still a little buggy, and Skype is doing much better

On youtube the video is better viewed on full screen, but if your connection cannot handle it, just use half size....

Cheers
[Galaxy S I9000 Android Development] Hrithan2020:
Yeah, had noticed, which is why I mentioned my version along with the ROM.

So, for flashing to v75(JVP) to v76(JVQ), you didn't have to install the JVQ base?

I am thinking of flashing to stock JVQ (or maybe the next leaked 2.3.4 version) and modify it minimally..But, too lazy to backup and restore..

For me, non-wipe, sometimes causes issues.
[Galaxy S I9000 Android Development] betoNL:
Anywho, I have no issues as you can see on video...

Dont think its kernel related, so if you want to speculate/ask about other factors,

I already started my video thread, hoping I will have time to make some more videos:

http://xdaforums.com/showthread.php?t=1165800
[Galaxy S I9000 Android Development] existz:
Sorry for the delay, been busy is real life and been working on a few new things before releasing... trying to squash a few bugs.. also working with 2011.03 toolchains, thanks to Zach it now works, just need to test it some. Also messing with new mDNIe settings, got the sharpness alittle bit better... So bare with me and ill get it up soon.. but for those that do not want to wait, 0.4.1 is actually uploaded, check the Mirrors link in the OP (only use ones for I9000, others are for Captivate).. I uploaded them but never rreleased it for I9000, waiting on next release. So consider it an unofficial release

Sent from my SGH-I897
[Galaxy S I9000 Android Development] Tatsuya79:
Don't forget this thing hasn't been pushed to 0.4.x yet. :p

Is it something that can change the dark tones gamma?

I've compiled 0.4.x branch and been using it the whole day, I didn't run into issues except this voodoo color stuff.

Is it similar to what we had on Froyo or is it a "dirty hack" using just gamma levels instead of contrast/brightness/saturation before? adjusting for neutrality seems impossible.
[Galaxy S I9000 Android Development] zacharias.maladroit:
already using that fix on my latest cm7 test-kernel and it does help :)
[Galaxy S I9000 Android Development] cantIntoCode:
Wi-Fi finally connects although its causing loads of random reboots when web browsing
[Galaxy S I9000 Android Development] kobik77:
Just flashed latest big-mem release and by funny mysteriouse way my back touch key behaves like the home key. Every time I hit it I get to my home and long pressing it shows me the latest used apps.

Home key is still functioning as it should.

Using continuum ROM.

By the way, what am I compromising on when using big-mem version?

And is there any difference between OC version to normal one when not OCing?

Thnx.

Edit: Silly me, no BIG-MEM for I9000 :(
[Galaxy S I9000 Android Development] s3icc0:
I am using almost 3 days the 0.4.1. with JUWE 5.1 rom and have to say - its really stable.

One possible bug found (don't know if is caused by voodoo sound) but after the call with headset the playback from poweramp resumes but on an incredible volume level for like 1 second.
[Galaxy S I9000 Android Development] B34R_85:
:confused: heeemmmm.. i can't find v0.4.1 :confused:
[Galaxy S I9000 Android Development] kobik77:
Look for the "Download older versions from here" link on the OP.
[Galaxy S I9000 Android Development] bitmappp:
flashed v0.4.1-1200... fantastic kernel, smooth like a butter.. color so so so good! love it.

rom: Ryyuu's EDB v1.2

thank you.
[Galaxy S I9000 Android Development] paratox:
0.4.x kernels are really nice! love them!

but one problem also exist in the actual test kernels like in the old 0.3.1 -> gps is unusable! jumps all over the map on different places. sometimes it stops on one position and will freeze there. this is not rom related, all other kernels have stable gps on ramads deodexed jvq.

i hope this will be fixed on final 0.4.x so i don`t have to flash another kernel every time i`m driving with the car.
[Galaxy S I9000 Android Development] samsontm:
If you flash BIGMEM on i9000 you will get mostly landscape screen when someone call or you like to see settings. Just flash back kernel for i9000 and all ok.
[Galaxy S I9000 Android Development] Hrithan2020:
I think it is a voodoo sound issue. Have had this since v8 ..
[Galaxy S I9000 Android Development] s3icc0:
whats your quadrant score with lagfix active and kernel version 0.4.1. (at 1GHz - no OC) ... I have cca 1950points ... but with older semaphore (1.2.2.) and same rom and ext4 lkagfix i got 2300points.

I know quadrant means nothing, but I'm just concerned ,,,,
[Galaxy S I9000 Android Development] zacharias.maladroit:
Hi existz, kodos,

you guys have an idea how to get memory compaction into the kernel ?

(info: 1.7. Memory compaction)

I saw it in a few cm7 kernels so I thought it's included in Android by default but couldn't find it in our cm7 kernel

might be that the Nexus S kernel/AOSP doesn't include it (don't know why - it's in mainline 2.6.35 and is very useful against memory fragmentation), besides that Samsung's kernel also doesn't since it also bases on the Nexus S kernel
[Galaxy S I9000 Android Development] Tiger33:
hahaha

yep I did the same thing :-(
[Galaxy S I9000 Android Development] betoNL:
I dont know if you saw my video, but seems to be that voodoo sound plus app is not fully functional on the 0.4.1 version, meaning, the FM tweaks are not available as it should be.

Also, on the video I forgot to downclock back to 1000Mhz in order to compare the frequency behaviour while listening to music trough stock music player, but I just did, and indeed with no OC, my sgs is noticeably more stable also on that situation.

But in both scenarios (oc/uc or not) I have no "800Mhz" bug of any other bug.

Anyway I tested all available kernels out there (except for fugu ), always on same conditions (same rom, no lagfix etc. etc.), and for me, this kernel is the smoothest( smoothiest?) of them all, no need for OC nor lagfix AT ALL :)

And with the 0.4.1 , the gps performance (when running programs like iGo, Sygic, Navigon, etc) is better than ever !:)

I keep on saying, but people dont listen:

Talon kernel + CriskeloGinger = winning team !!

«»
[Galaxy S I9000 Android Development] paratox:
that`s strange, my gps was never worser then on talon 0.3.x and 0.4.x

big jumps all over the map, lags and sometimes it freezes on one position.