yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] logpc:
I had the same problem, it seems ok with this test version (1200 mhz, ondemand). Thanks
[Galaxy S I9000 Android Development] jocke_lulle:
Hmm. I just had another freeze and reboot with the test version. I used oc1200 and -25mv on 1200mhz (the same settings as i used for a long time with 1.8.2). When the screen froze the colors looked washed out(if you understand). Right now im testing latest simplicity and earlier this week i tested the 1.9beta together with innovation v13 rom. I have had the same problem with both configurations. For me it isnt a must to oc but I share this to let you know.

Now im back to no oc and no uv so let's see how it works:)

Edit. I just noticed that since the last froze and reboot i lost my sms. I then looked in lost.dir and found five files, probably from the freezes I have had during yestetday and today.
[Galaxy S I9000 Android Development] stratosk:
So, I guess the problem is not in the transition latency that reduced in 1.9.0...

Thank you for testing this
[Galaxy S I9000 Android Development] darckengel:
For those which have problems with 1.9.0.

Can you get back to 1.8.2 for a day and tell if the problems disapear?

It's strange that only few people seems to have new problems.
[Galaxy S I9000 Android Development] betoNL:
Safe move

Sooo....since I am not having any issues at all, I decided to try to make my phone even more responsive and get even more juice...

So I did more testings and decided to revive my thread - fast guide on how to overclock/undervolt a tough to OC/UV sgs:

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

OC/UV App: Tegrak Overclock Ultimate

Kernel Semaphore 1.9.0 BigMem

Scheduler: deadline

Governor: smartassV2

[B]
Frequency Core Voltage Internal Voltage

L1 1144 MHz 1285 mV 1105 mV

L2 800 MHz 1150 mV 1100 mV

L3 400 MHz 1050 mV 1100 mV

L4 200 MHz 850 mV 1000 mV

L5 100 MHz 825 mV 950 mV
[/B]

Tested the whole day, some heavy games and run Neocore for 10 minutes

Smooth, stable and safe.....:cool:

What was great (Semaphore 1.9.0 + GalaxyROMv11) got even better ! :)

Follow the guide over there ,,,you guys wont regret it:

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

My 2 cents

« »
[Galaxy S I9000 Android Development] a g bell:
Bootloop detection is becoming a pain in the ass when using cwm is there a way to disable this feature?
[Galaxy S I9000 Android Development] mancukya:
whit Semaphore 1.8 and 1.9 Virtual/ cache to 50 mb activated market not works.
[Galaxy S I9000 Android Development] McDown:
Works for me with both. You can always use the old market.
[Galaxy S I9000 Android Development] stoske:
I am now on stock JVT and with 1.8.2 I had a little issues with restating Launcher Pro in some cases.

The 1.9.0 version is the best so far, actually the best kernel I used. No restarting LP, all fluid, no problems at all far.

Beamed from Dark Side
[Galaxy S I9000 Android Development] burakgon:
Stucked on boot again after flashing a rom. I think the detection did it.

Now fresh installed and rebooted after OC. But there is no problem normally booted up.

It sometimes reboots after when I change some settings on semphore app.

Usually on touchscreen sensivity.

Just for feedback all issues. %100 fast + smooth gaming. But bootdetection is a really pain.
[Galaxy S I9000 Android Development] HM.Carbide:
Reboot should not be. There must be a tiny thing wrong on your current rom installation.

A force close on semaphore app is possible, if you have old and new touchscreen scripts in Semaphore folder on sdcard.

Delete the whole folder. At least the touchscreen scripts. The new kernel has already the most recent scripts.
[Galaxy S I9000 Android Development] darckengel:
For the x time, remove the extra busybox (with semaphore app in 1.9.0 or manually deleting those on /system/bin and /system/xbin).

People should search before asking always the same questions.
[Galaxy S I9000 Android Development] betoNL:
Should you not be more worried about what is possibly causing boot loop?

.
[Galaxy S I9000 Android Development] GreenSGS:
The symptom: freeze, color washed for 2-4 sec (looks like phone has sudden heavy load)and then reboot,is exactly what I have had. I am also not using OC,smartass v2 and sio anymore. Getting no clues whats wrong.

Stratosk: Thank you for paying attention,to it.
[Galaxy S I9000 Android Development] darckengel:
Can you get back to 1.8.2 for a while and see if you still have this?
[Galaxy S I9000 Android Development] GreenSGS:
Thanks,thats what I thought too, to check.I.ll do a clean install too.lets see.What is your config at the moment?
[Galaxy S I9000 Android Development] habylab:
This just isn't working, will just go back to 1.2.2 cannot see why you would disable conservative as default.
[Galaxy S I9000 Android Development] cink40:
existz managed to fix auto brightness in 0.3.2 JVQ version (which is in Continuum 6.1 ROM)
[Galaxy S I9000 Android Development] :
i can make an update.zip for you later when i'm back home if you want.
[Galaxy S I9000 Android Development] stratosk:
I'm sorry you are facing problems with this kernel.

First of all please make sure that you are using JVQ_1.3.0 and not JVP_1.3.0a

Actually, the JVP version does not contain the /res/scrips folder.

cid85 explained in detail the actions you should follow in order to load the konservative module.

If you want to use the JVQ version you may copy the script from res/scripts to /system/etc/init.d

if you want to use the JVP version you have to create the script in /system/etc/init.d

In both cases after the module loading, you may enable the conservative governor from chainfire's tweak application.

Please also note the conservative governor is not the default one. Both stock's and Semaphore's kernel default is ondemand.

Please let me know if you still have problem with this.
[Galaxy S I9000 Android Development] sahidmiah:
hello mate i am on ginger real 7.0.1 JVQ.with your kernel 1.3.0JVQ .everything works excellent accept BT.is there any solution? thanks
[Galaxy S I9000 Android Development] stratosk:
BT issue is supposed to be related with CF's initramfs and I think I found a solution which works in stock rom. I have to say that is difficult for me to test this kernel and reproduce the problem in different custom roms as I have only on device and very limited time. There is a workaround for this, posted in this and some others threads.

But anyway, I will try to find a solution.

About the auto brightness, I will also try to resolve in the next version.
[Galaxy S I9000 Android Development] :
not sure but i think its working, at least it's some more often changing brightness with the library of this thread:

http://xdaforums.com/showpost.php?p=15189970&postcount=1

I replaced the file sensors.default.so with the one in his attachment, but left a backup (sensors.default.so.bak) left in case of problems upcoming.

the only BT problem i had was today in my car, a restart of the radio (car) resolved the prob.
[Galaxy S I9000 Android Development] stratosk:
I just tried this library. I think it's better now. I will try it for a couple of days :)

Thanks
[Galaxy S I9000 Android Development] habylab:
R

Will the jvq version work on jvp or not? And how would I fix the auto brightness with the sensors listed as a .zip file in the post a couple above.

I did not know ondemand was default!

Thanks once again!

Edit : it does work on jvp! Is undervolting disabled too, or do I need to copy over a script?
[Galaxy S I9000 Android Development] seeraj15:
How do you enable ext4 on this kernel?
[Galaxy S I9000 Android Development] :
I made a update.zip file if anyone wants to use it. It makes a backup file (sensors.default.so.bak) in /system/lib/hw and copies the file of the thread mentioned above/before into /system/lib/hw folder.

I've tested the file on my phone just right now, was working,

but please only use it if you know what you do!

UPDATE: Removed the file, use redmaners (next post) cwm file :)

The manual step would be:

Using file explorer with root enabled, e.g. Root Explorer and going into directory: /system/lib/hw. Renaming sensors.default.so to sensors.default.so.bak (and/or copying onto sdcard on a secure place). Copying sensors.default.so from the attached zip file (see the linked thread from my last post) into /system/lib/hw.

Reboot the phone due to a reload of the library.

On the undervolting part: i use tegrak oc app, loads additional modules (tegrak_overclock or so) and works like a charm :)

use ext4 apk from chainfire

http://xdaforums.com/showpost.php?p=12651371&postcount=7

as this kernel is based on CF-Root you can use the tools supplied with CF-Root.

edit2: lol redmaner, i got stuck on the update file and although i forgot the permissions so i deleted the file in my post :)

your file will do fine i think. doh, its just too late today hehe
[Galaxy S I9000 Android Development] redmaner:
POST ABOVE ME IS BETTER

Auto-Brigtness fix for JVP and JVQ

This will work on every stock/custom rom based on JVP/JVQ

This will work with every kernel

Using sensors.default.so from JVO

Flash this in CWM >> http://www.multiupload.com/039QER144H
[Galaxy S I9000 Android Development] stratosk:
If you are on JVP it's better to use JVP_1.3.0a version.

For overclocking, undervolting you may use Voltage control like applications if you are not familiar with scripts. You don't need to load additional modules for OC/UV. The functionality is embedded in the main kernel.
[Galaxy S I9000 Android Development] exkalibur68:
my feedback :)

Rom Sconcau Ext6 JVP based

Modem JVP

Kernel Semaphore 1.3.0 JVQ stable

BLN good for every events

Fix Gps abou 10/15 seconds

Wifi and BT good

quadrant whit 1.2OC between 2500/2600 (a couple of time 2850!)

for me is one of the best sgs kernel :)

thanks a lot :)
[Galaxy S I9000 Android Development] kubilayk:
thanks for JVQ kernel. nice work...
[Galaxy S I9000 Android Development] cink40:
huh stratosk, one issue : after i flash semaphore 1.3.0 app Droidwall stop working, app says something that iptables 1.4.10 could not be found and that the kernel need upgrading?

Then i installed DC 2.8 JVQ and DroidWall start to work again. I am on Continuum JVQ ROM. Oh yeah and on rfs.
[Galaxy S I9000 Android Development] stratosk:
I was worried! Too much silence in this thread...:)

Anyway, about your issue: you have to load the netfilter modules with the enable_netfilter script.

Copy it from /res/scripts to /system/etc/init.d/ and reboot
[Galaxy S I9000 Android Development] cink40:
Thanks, i shoul read the first post... sorry for bodering you
[Galaxy S I9000 Android Development] stratosk:
No problem! As I said I need feedback :)
[Galaxy S I9000 Android Development] Rebel2k:
I find this kernel quite good, even if I still face Bluetooth activation problem (using GingerReal 7 ROM). An issue with wifi too: from time to time, wifi is still connected to my router, but DNS are lost and since then, it is impossible to resolve any domain name... Have not found anything else than rebooting to have DNS back. Never had this issue with other kernels.
[Galaxy S I9000 Android Development] darckengel:
I'm on odexed JVS rom, OC at 1.3Ghz, On Demand/SIO, Semaphore 1.9.0bm.

And I had no freeze/reboots (except when i tried to UC a little too much 1.3Ghz) with any of lasts versions (i used tes 1.8.2 patched version, 1.9.0 beta , final and bm).
[Galaxy S I9000 Android Development] jocke_lulle:
Ive been on 1.8.2 for the last 6hours,oc to 1200 and uv-25. So far no problems. I'll keep testing it.
[Galaxy S I9000 Android Development] logpc:
For me, the test version 1.9.0 give this results (JVT, 1.2 GHz) :

ondemand/Noop : Ok

ondemand/SIO : reboot
[Galaxy S I9000 Android Development] darckengel:
For those who have problems with 1.9.0 can you try this one too:

View attachment Semaphore_kernel_JVT_1.8.2d.tar

But if you want to test with OC, you will need to set max freq in a screenstate scaling script (you can found it on pikachu01 thunderbolt thread).

(or you can try this one i edited, didn't had tested it but it should works: View attachment S98screenstate_scaling.txt , don't forget to set permissions at 777)
[Galaxy S I9000 Android Development] pikachu01:
Your 800MHz UV is too low. Try upping it.
[Galaxy S I9000 Android Development] gsw5700:
thanks for that, using your apk to simply remove journals on system and cache file systems. I have compared io performance using androbench as a rough guide. I found that many different ext4 options don't make any noticeable difference. So using your apk to remove journals (less writes, less wear, less cpu).

Ps. I found that rfs random writes are still twice as fast as ext4, but SQL lite updates are much, much slower when using rfs!

Sent using TCP/IP
[Galaxy S I9000 Android Development] jocke_lulle:
Trying right now. Thanks
[Galaxy S I9000 Android Development] andip71:
Cool. Good to know it is of any use :)

I have made another version now, that more or less 99% uses the same mount option speedmod kernel uses. Not yet uploaded, but working fine since yesterday morning.

EDIT: No, too unsafe. I reverted back to my original script again.

Cheers

Andi
[Galaxy S I9000 Android Development] Ashtrix:
@stratosk: Any news on ICS port & CM7 support :rolleyes: ?
[Galaxy S I9000 Android Development] darckengel:
People don't have enough to flood the ICS thread, they need to flood others threads ...

ICS port is still in very early stage of investigation ...

You should wait a little bit
[Galaxy S I9000 Android Development] s3icc0:
Yesterday I flashed the 1.9.0. And today I got a standard lock screen rotated by 270° clockwise and it takes some time to unlock it. Other info from lockscreen was just normal. Just a single occurrence. Never had this before.
[Galaxy S I9000 Android Development] gsw5700:
Hi Andi,

Thanks dude, could you let me know the mount options please, this could be good! I've always thought there should be a app to offer 2 or 3 ext4 mount options, say fast/most risk, medium speed/ risk, slowest/ safest etc

Would be great to see the options in semaphore script manager

Sent using TCP/IP
[Galaxy S I9000 Android Development] jocke_lulle:
@darckengel

I flashed 1.8.2d as you posted and I copied the screenstatescaling script to init.d and gave it permissions (rwxrwxrwx) and then rebooted. Then I chose oc1200 in semaphore app and uv-25mv with voltage control. But if I close voltage control, leave the phone for some minutes and then open the app again it has set the maximum freq to 800Mhz? How come? Btw, why do I need the screenstatescaling script when I want to oc with this kernel version?

Thanks
[Galaxy S I9000 Android Development] andip71:
Oh cool, my 100th post :-)

Hi,

this is how speedmod mounts the volumes:

/dev/block/stl9 /system ext4 ro,noatime,commit=15,barrier=1,nodelalloc,data=writeback 0 0

/dev/block/mmcblk0p2 /data ext4 rw,noatime,commit=15,barrier=1,nodelalloc,data=ordered 0 0

/dev/block/stl10 /dbdata ext4 rw,noatime,commit=15,barrier=1,nodelalloc,data=ordered 0 0

/dev/block/stl11 /cache ext4 rw,noatime,commit=15,barrier=1,nodelalloc,data=writeback 0 0

However, I just reverted back as I had a data loss issue with these settings.

Which is strange, as with Speedmod this does not happen. As soon as I use commit somewhere it leads to issues sooner or later. Don't know, maybe hardcore has implemented something else to make it work with Speedmod. With Semaphore I definitely cannot recommend it (anymore). Sorry.

BR

Andi
[Galaxy S I9000 Android Development] Michel38280:
On the French Galaxy forum, some people are complaining about battery fast burning ... :confused:
[Galaxy S I9000 Android Development] darckengel:
The kernel sets max freq while screen off at 800Mhz and while screen on at 1Ghz.

That's why i suggest you to use the screestate scaling script to force it to 1.2Ghz.

It's strange that it stays at 800Mhz while screen on, it should be 1Ghz or 1.2Ghz.

Maybe some error from the app...

I will check my script to so see if it works.

Edit: My bad, editing with wordpad was a bad idea,

Try this one:
[Galaxy S I9000 Android Development] manjee:
I experienced this a few months ago with another kernel. It happened to be caused by file system corruption. My advice is not to bother much and do a clean install of a Rom. Preferably you can flash a stock Rom then semaphore then factory reset then flash your Rom of choice.

FYI I found simplicity is the best one around.

Hope that helps.
[Galaxy S I9000 Android Development] betoNL:
Anyone? Never mind...

I kept on testing and realized that the combination DEADLINE/SMARTASSv2 adds more responsiveness but compromises stability....

Therefore I am changing the scheduler to NOOP

and the governor to ON DEMAND

A little bit less responsivness , but it solves the stability issue on my TOUGH to OC/UV sgs

For those not overclocking/undervolting, I would suggest the combo DEADLINE / SMARTASSv2

At the moment I am testing this:

[B]
Frequency Core Voltage Internal Voltage

L1 1200 MHz 1325 mV 1105 mV

L2 800 MHz 1180 mV 1100 mV

L3 400 MHz 1050 mV 1100 mV

L4 200 MHz 850 mV 1000 mV

L5 100 MHz 825 mV 950 mV
[/B]

So far so good.........pretty good ........very good.... and what a juice :cool:
[Galaxy S I9000 Android Development] jocke_lulle:
Still the phone reverts to 800mhz!? Maybe I should try a clean install from stock and so on just like manjee said. Anyway, thx for your help. I will hit thanks when i get to my pc:)
[Galaxy S I9000 Android Development] Millionas:
I got much better batterie with 1.9.0.

I charge my phone during the night, pull it out at 0700 and it shows 98%.

Usually at 1600-1700 i have 50% left. Now the time is 2020 and I have 64%.

Normal usage, no gaming, some mp3/web radio/radio/calling/txting/surfing.

Dont know what he has done with the 1.9.0 but i get much better battery than the one before.

Setting is: 1000, Ondemand, Simpe I/O, VM Dirtyness, 64MB(Bigmem), 256kb-64kb, Sensitive.
[Galaxy S I9000 Android Development] Michel38280:
Thanks for your answer ... but it does not solve the problem of some users :rolleyes:
[Galaxy S I9000 Android Development] stratosk:
Nobody can help you when post a statement like that.

There are too many factors that affect battery life.

Please be more specific when you post about a problem, if you want someone to be able to help you.
[Galaxy S I9000 Android Development] Michel38280:
What can I say more ? I did not change anything from 1.8.2 to 1.9.0 and the battery is burning faster, that's only an observation :rolleyes:
[Galaxy S I9000 Android Development] betoNL:
Still...makes no sense....

Your usage changes, you will find newer apps, you move on

what's the point to have a smartphone if you wont try new things with it?

Anyway, battery performance here is good, even before i started undervolting.....

No probs here
[Galaxy S I9000 Android Development] Michel38280:
I will try with the same options as yours ... feedback tomorrow :)

---------- Post added at 10:04 PM ---------- Previous post was at 10:00 PM ----------

My usage remains an average use as the days before, some market updates as usual.

I will try it again with the options given in a previous message :)
[Galaxy S I9000 Android Development] HM.Carbide:
Since one week i have email polling enabled (2 accounts every half hour), 1.9.0, jvt, battery lasts 1 day 17 hours, 4 hours 30 minutes display time. I am happy :)

If you use “normal“ tweaks, fast battery drain comes mainly from an app, poor 3g reception or poor wlan reception.
[Galaxy S I9000 Android Development] darckengel:
It should revert to 800Mhz when screen is off (changed by kernel) and at 1.2Ghz when screen is on (by script).

---------- Post added at 11:28 PM ---------- Previous post was at 11:17 PM ----------

Your phone usage is every day different, it's hard to compare one to another and just say, it uses more or less battery, to be sure of that you say, you must make tests that compare exactly the same use of your phone and compare, compare the usage of displaying the same film, playing the same music for the same time, playing the same game for the same time, let it iddle at the same place for the same amount of time.

When you flash a new kernel, generally you tend to test it more than a kernel you have since 1 month, so obviously, you will drain your phone faster.
[Galaxy S I9000 Android Development] jocke_lulle:
I understand but it seems to stay at 800mhz...
[Galaxy S I9000 Android Development] darckengel:
Can you check it with another app than voltage control? (CPU Spy, or antutu cpu master free).
[Galaxy S I9000 Android Development] Ashtrix:
Hmm, well..!

;)
[Galaxy S I9000 Android Development] jna9000:
I understand that I have to check netfilter for tethering. But what is the rationale to disable this by default? (not only netfilter but other options as well)
[Galaxy S I9000 Android Development] darckengel:
Less memory print!
[Galaxy S I9000 Android Development] jocke_lulle:
I just tried those apps but it is the same result. As soon as the screen goes off and I turn it on (after some seconds) the max freq has changed to 800mhz and it seems to stay there.
[Galaxy S I9000 Android Development] darckengel:
You enabled OC on semaphore app?

It works on my phone.
[Galaxy S I9000 Android Development] jocke_lulle:
Yes i did. But im going to start all over now from stock jvt and see if it helps:)
[Galaxy S I9000 Android Development] Michel38280:
After a full load during the night and a wipe battery statistics ... it seems better ... sorry for the noise ;)
[Galaxy S I9000 Android Development] betoNL:
pick one oc/uv app and uninstall the others

furthermore, voltage control app is one of the buggyest oc/uv apps I ever tried (at least some versions)

Anyway, work always with one oc/uv app and uninstall the others

my guide is still working for me (on mine sign)

EDIT: The guide is just updated:

http://xdaforums.com/showthread.php?t=1250442&page=2
[Galaxy S I9000 Android Development] cherenco:
after instaling your kernel, my screen got really weird it is so dark and it,s hard to read the text, any idia how to fix this?
[Galaxy S I9000 Android Development] gsw5700:
Use voodoo control to change colors, you can also try different settings using semaphore app

Sent using TCP/IP
[Galaxy S I9000 Android Development] disclaimernotice:
Will you please make a version without voodoo colour? Voodoo colour is really really bad for dark images.

---------- Post added at 10:08 PM ---------- Previous post was at 10:07 PM ----------

And using voodoo settings doesn't change the colours back to stock.
[Galaxy S I9000 Android Development] HM.Carbide:
Try in Semaphore app:

Miscellaneous - Voodoo Color Settings - Stock Color

Is it the color schema you expected?

If not, what is different to stock?
[Galaxy S I9000 Android Development] disclaimernotice:
I've tried the semaphore app, and even then, I cannot get back the stock colours. The main problem with voodoo colours for me is that in images and videos that have dark colours, the colours look horrible.
[Galaxy S I9000 Android Development] HM.Carbide:
Do you have a link with an example video or image?

I'll try to compare stock kernel and stock settings.
[Galaxy S I9000 Android Development] cherenco:
I've done it too, but did not solve anything. the image is really bad compared to the stock kernel, going back to the CF-kernel ROOT...
[Galaxy S I9000 Android Development] jocke_lulle:
@darckengel

I did a clean install but still got freezes at oc1.2 with both 0 and -25mv uv. About your 1200screenstate scalingscript, should I delete the .txt in order to use it?(sry for hte dumb question:) ) I have sent you a pm.

@betoNL

I havent tried your oc/uv yet. What is the internal voltage? Can it only be set with tegrak ultimate? The core voltage I can change with for example voltage control?

Edit. I deleted the .txt in the end of the script and rebooted. Now it works:)
[Galaxy S I9000 Android Development] hackeron:
You want pictures that looks crap with nexus s framebuffer and good with stock? here is 3..

http://imgur.com/1p8Vk,mGX4r,4lUe1#0

But this is a dilema, voodoo color if you set it up correctly looks better in almost all cases.. but in for example these 3 pics.. it still looks crap no matter how much you callibrate or adjust..
[Galaxy S I9000 Android Development] sbnaul:
Open vodoo app and reset gamma hack to default...