yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Tepes4:
stratosk,

i tried using the autorightness restore fix but still no joy...

It stays full on and i had to disable it all together cause it was sucking up my battery...
[Galaxy S I9000 Android Development] stratosk:
Did you restore the sensors.default.so library? Someone posted it in this thread few days ago.
[Galaxy S I9000 Android Development] Tepes4:
I used a cwm script that supposedly did that. It was named "Auto Bightness Restore Fix JVR.zip"

I seriously am at a loss...
[Galaxy S I9000 Android Development] stratosk:
Are you in the latest kernel version (1.5.0)? Do you use Juwe's rom? I don't know if Juwe uses additional fixes for the autobrighness.
[Galaxy S I9000 Android Development] Tepes4:
I am on 1.5.0v and i use Juwe's ROM. I do not know if juwe uses something else... but i think this is something to do with the sensors, therefore the kernel software wise...
[Galaxy S I9000 Android Development] stratosk:
Sorry, I didn't understand. Do you mean it's a hardware problem or kernel's problem?
[Galaxy S I9000 Android Development] Tepes4:
Since the drivers for the sensors are linked with the kernel, i guess it is more of a kernel fault, rather than a rom fault.
[Galaxy S I9000 Android Development] stratosk:
Kernel is working fine with stock JVR and with stock sensors.default.so library.

Other users also reported that the latest source changes for auto brightness work fine. So, I believe that something is wrong in your phone. If you installed a fix for the auto brightness, you have to revert back the changed to work ok with the latest kernel version.
[Galaxy S I9000 Android Development] Tepes4:
Androsensors gives me a correct reading...As soon as i cover the top of the phone it goes from 5000 lux to 5 and if i let a little light in it goes to 1000 within one second.

When I go into the settings/display/brightness and i click auto brightness it takes the phone 3-5 seconds to react to the change in lighting conditions.

Any help would be appreciated...
[Galaxy S I9000 Android Development] stratosk:
This is not a problem. It's is the default behavior. I thought you said that the auto brightness does not work at all.
[Galaxy S I9000 Android Development] Tepes4:
Now it doesn't do it at all.

I will try flashing rom again to check...
[Galaxy S I9000 Android Development] didicola:
re filaraki tepes dont do your life difficult;)

flash the simplicity 0.31 use stratos kernel and auto brithness works like a charme
[Galaxy S I9000 Android Development] are-red:
Usb tether also broken on this kernel..hmmmmm...wonder what make it getting error..
[Galaxy S I9000 Android Development] stratosk:
Please read the first post. You have to use the enable_netfilter script.

What else is "also broken" on this kernel?
[Galaxy S I9000 Android Development] dewa5227:
nope. its working fine
[Galaxy S I9000 Android Development] are-red:
Thx all.. Working now..need to move script to init.d folder... Best kernel so far.. With voodoo color and sound.. Thx
[Galaxy S I9000 Android Development] daut:
Ou.. ic.. thanks.

Do you oc ur phone?

yeah, it's the best. ;)
[Galaxy S I9000 Android Development] stratosk:
Yes, I use OC/UV since I released the first version of this kernel.
[Galaxy S I9000 Android Development] ryuzaki_eru:
What this modules do?

- enable_cifs (load cifs module)

- enable_netfilter (load netfilter modules for firewall or WiFi tethering)

- enable_tun (load tun module)

- enable_deadline (load the deadline I/O scheduler module)

- enable_binfmt_misc
[Galaxy S I9000 Android Development] are-red:
Could be enable some tweaking feature..
[Galaxy S I9000 Android Development] ryuzaki_eru:
I know, but what this features do?
[Galaxy S I9000 Android Development] M_J_Nazari:
hi, in newest version, the BLN is supported but not works? anyone has this problem?
[Galaxy S I9000 Android Development] ryuzaki_eru:
There is any BusyBox in this kernel? Titanium Backup tell me that it is not.
[Galaxy S I9000 Android Development] ryuzaki_eru:
I dont' find ant init.d folder...how is that possible? I have a JVR stock ROM.
[Galaxy S I9000 Android Development] daut:
Can u share ur setting?

is it okey?

no, everything fine and great. :)
[Galaxy S I9000 Android Development] stratosk:
Yes, busybox version 1.16.2androidminimal. No problem with Titanium backup here.
[Galaxy S I9000 Android Development] stratosk:
Kernel does not create one. Just create it with a root explorer application.
[Galaxy S I9000 Android Development] stratosk:
I use these settings with absolutely no problem on my phone:

1200 0

1000 -25

800 -25

400 -50

200 -50

100 -75

So, I use this line in enable_ocuv script (of course you may use an application for this):

echo "0 25 25 50 50 75" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mv_table
[Galaxy S I9000 Android Development] stratosk:
Please read this post
[Galaxy S I9000 Android Development] adl:
Where can i download the scripts?
[Galaxy S I9000 Android Development] stratosk:
You can find them in your phone.:)

Check the /res/scripts directory
[Galaxy S I9000 Android Development] Rebel2k:
Why such an old version? (just for my information ^^)
[Galaxy S I9000 Android Development] stratosk:
This version has half size compared to 1.18 version. I guess that's the reason that chainfire use this. And it works fine. :)
[Galaxy S I9000 Android Development] Rebel2k:
Ok, thanks for the fast and clear answer mate! :)
[Galaxy S I9000 Android Development] ghosty7:
Stratosk, i want to overclock to 1.2, but i am a little confused.

Your script is like this:

#!/system/bin/sh

echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

# values in mV, from 1.2GHz - 100 MHz

#echo "25 50 50 75 75 100" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

what changes do i need to make to overclock to 1.2 ? thanks
[Galaxy S I9000 Android Development] kennethkc:
just copy the script to /system/etc/init.d and reboot will enable oc

if you need uv, you can remove # before the second echo
[Galaxy S I9000 Android Development] ghosty7:
Thanks, however i know how to enable, what i do not understand is why is the first line disabled with an "#" ? or is it not relevant ?
[Galaxy S I9000 Android Development] sirbrian:
BLN works fine on my side, what is your probem in details? Maybe I can help...
[Galaxy S I9000 Android Development] stratosk:
Actually, the '#' in first line is not a remark. In unix scripts with the '#!' you specify the 'shell' you will use to execute the script.
[Galaxy S I9000 Android Development] ghosty7:
Katalava :) Thanks
[Galaxy S I9000 Android Development] stratosk:
Παρακαλώ :) ότι χρεαστείς εδώ είμαι...
[Galaxy S I9000 Android Development] vd69:
Συγχαρητηρια!Next thing u must make better is bayttery consuption and gps .Other than this is perfect.ΧΡΟΝΙΑ ΠΟΛΛΑ.
[Galaxy S I9000 Android Development] addicted2088:
Not sure if this is known, but USB tethering gives error everytime I try to activate it. Stock JVR with JVR Semaphore..
[Galaxy S I9000 Android Development] HM.Carbide:
Did you copy the enable netfilter script?
[Galaxy S I9000 Android Development] stratosk:
Ευχαριστώ! Χρόνια πολλά!

Do you have problems with GPS? Because I didn't change anything related to this.
[Galaxy S I9000 Android Development] ryuzaki_eru:
Thanks. But i don't understand what this module do:

What's "load the deadline I/O scheduler module" means?
[Galaxy S I9000 Android Development] stratosk:
Please read this:

http://en.m.wikipedia.org/wiki/Deadline_scheduler

And also this:

http://en.m.wikipedia.org/wiki/I/O_scheduling

The default scheduler in this kernel is the noop. If you want to change this to deadline then you have to load this module and check the respective option in chainfire's tweak application.
[Galaxy S I9000 Android Development] ryuzaki_eru:
Thanks, i will read it. So this tweak improve the phone's performance?
[Galaxy S I9000 Android Development] stratosk:
Not exactly. I believe that noop scheduler I use as default has better performance on solid state storage devices.

Optionally you may use the deadline if it is more suitable for you.
[Galaxy S I9000 Android Development] ryuzaki_eru:
Thanks :) Last question: Chainfire's EXT4 tools tell me that is not enough space for restore the backup of /system when i try to convert /system to EXT4. How come? I have a JVR stock ROM, this is the first time that this happen.
[Galaxy S I9000 Android Development] vd69:
No problem.! Only with battery and I have calibrated it .για το gps σε πείραζα!
[Galaxy S I9000 Android Development] stratosk:
Please try to make some space in /system. Remove some ringtones for example.
[Galaxy S I9000 Android Development] HM.Carbide:
I have testet battery life since 3 days now, i think it is ok.

the kernel is fast (no lags) and that even this kernel has less aggressiv configured governor than the other kernels.

In all other kernels google navigation and gba emulator runs on 1000mhz, with this kernel they use mainly 800mhz which seems to be enough, as i can see no diffetence.

So with my kind of usage i'll get a display time of 5h (with speedmod 4,5h)

Display time is the best battery measurement for me. If the battery holds 1, 2 or 3 days depends on how much i use the phone, but the display time is nearby constant.

The best values i got was about 6h on vacation with speedmod (guess would have been also with this kernel) conservative governor and max freq limit to 800.

Edit: maybe it is possible to make a “very battery efficient tweeked conservativ module“

Edit2: conservative from module uses very high frequencies, deleted script, ondemand on this kernel is the better choice.

Edit3: 1day 10h battery is empty, 5h 7min display time
[Galaxy S I9000 Android Development] stratosk:
Of course battery efficiency and speed are the 'holy grail' of the devs building custom kernels.

So, I can't tell you if it is possible to make such governor.

I strongly believe that the standard linux kernel governors (ondemand and conservative) are very well tested on millions systems and making something better than this, is at least very difficult. But of course if I'll find something good I will implement it in this kernel.

By the way, did you try undervolting? If yes, did this help for better battery life?
[Galaxy S I9000 Android Development] vd69:
Is undervolting dangerous for the phone?
[Galaxy S I9000 Android Development] stratosk:
I don't think so. Using overclocking or overvolting maybe because of heating problems. But with undervolting the cpu works with less voltage and this can not harm your phone.

The usual problem with undervolting is stability. You have to find the ideal values of uv for each frequency for your phone.
[Galaxy S I9000 Android Development] stratosk:
I'm thinking to include a standard version of ondemand governor (no tweaks) as a module in the next version for people who want better battery efficiency.
[Galaxy S I9000 Android Development] Rebel2k:
Is that normal that flashing Semaphore 1.5.0 on a stock JVR odexed ROM doesn't give SuperUser access to apps? I tried and even if the SU app is there, none of my apps can't get root access...

What have I forgotten?
[Galaxy S I9000 Android Development] HM.Carbide:
I guess it was too little test time.

First battery cycle was without undervolting, cause i wanted to see the difference to speedmod. I got about 4h 50mins display time.

The last turn was with undervolting 5h 7mins

Uv setting: 25 50 75 75 100 100.

The 15 minutes difference could also be due to different usage. But the feeling says some minutes are due to the undervolting.
[Galaxy S I9000 Android Development] stratosk:
Did you flash on a clean rom? Maybe leftovers from other kernels or roms?

Anyway, try to delete the cfroot directory in /system the reboot. This will reinstall all kernel stuff. Also check if there is enough space on /system partition.

Please let me know if this works.
[Galaxy S I9000 Android Development] HM.Carbide:
Would be really great!

Normally it is not a problem to charge when ever it is needed, but on vacation i got a real problem with battery life.

The second problem is, that the phone gets really hot when it uses 1000mhz for one hour, and the battery is empty after that (my problem with google navigator and speedmod on vacation)

With your kernel googe navigation mostly uses 800mhz. On my next trip i'll try how long i can navigate with your kernel.

I didn't mention it:

A really great kernel!
[Galaxy S I9000 Android Development] s3icc0:
5hrs of display time??? in average i get 2h 50mins .....
[Galaxy S I9000 Android Development] HM.Carbide:
I have disabled all automatic syncronized services (market, email, google backup,...)

Wifi standby on display off.

So only view battery usage in standby.

The display time also depends on your personally usage. Thats why i wrote: with my usage i'll get ...

I'll also use only 1000mhz.

I use rfs, but that should not make a difference.

Display brightness is always on lowest, if needed, i'll higher it manually on the top task bar.

That is all i can do.

The rest is done by cpu governor and probably by undervolting.
[Galaxy S I9000 Android Development] Rebel2k:
Thanks for your fast answer, as usual! Indeed, I think it was space related (maybe not enough space on /system) but maybe related to TW4 I'm trying to include in my base rom too... Don't know yet... Anyway, with a real stock rom and the kernel, that's working good. Thank you!
[Galaxy S I9000 Android Development] HM.Carbide:
Is it necessary to tweek ondemand governor in source, or would it be possible to tweek it per script?

I guess upscaling threshold 95 will reduce speed a bit, but save a lot battery. Maybe performance will keep ok if the downscaling faktor is increased.

What downscaling faktor are you using? Default is 1 i think, maybe with 10 there is less freq swapping and it will be still fast.
[Galaxy S I9000 Android Development] danchitu86:
I have 1.4.2 version, can I flash with Odin to 1.5 without any loss of data?

10x!
[Galaxy S I9000 Android Development] andip71:
yes you can. by only flashing a kernel you will not loose data.
[Galaxy S I9000 Android Development] hickup:
Yep. I've done that a lot of times with kernel flasher while being out without using odin.
[Galaxy S I9000 Android Development] rom08:
Can this bug be also in semaphore? Don't know if your oc is based on exist one
[Galaxy S I9000 Android Development] stratosk:
No. Everything is OK. You can check this with the way existz explained in his post.

And yes, I use existz's OC/UV as it is mentioned in first post.
[Galaxy S I9000 Android Development] stratosk:
Up threshold to 85 is the only tweak I use to the ondemand governor.

I have to check if it is possible to change this using script.
[Galaxy S I9000 Android Development] adams.alex:
Hi all! I search the subject in this forum and i found some raports about it but, with your permission i will bring to discussion again. Today i tested latest BLN app, Pro and Free, with stock 2.3.4 GB (JVR) and DarkyRom (v10.2) bots with semaphore kernel and on the sms the led's do not work, on call's is ok. If you have an advice...

Thanks
[Galaxy S I9000 Android Development] stratosk:
Hi,

BLN doesn't work on stock sms application. At least never worked for me.
[Galaxy S I9000 Android Development] adams.alex:
In froyo works with stock; in Gb...that is another story, i tried all important kernels from this forum (GB) and for sms...a big NOPE :). Thanks anyway, maybe, someday, somebody will find a solution for this.
[Galaxy S I9000 Android Development] jkruijff:
I started using the Handcent sms app. With this bln does work. (for me, that is).
[Galaxy S I9000 Android Development] stratosk:
A friend just send me a solution for this. He claims that this works on stock sms (for JVR)

Please flash it with your own risk. I didn't test it.

Thanks to mukuro for this.
[Galaxy S I9000 Android Development] Rebel2k:
Oh, great, thank you! I should try to flash it on my new JVR odex! :)
[Galaxy S I9000 Android Development] stratosk:
Thanks @mukuro. Just make a backup just in case.
[Galaxy S I9000 Android Development] ssdd48:
I use this one and it works on stock sms, I know it says its for JVP but I'm on JVR and it works for me. Don't know if it works for odex roms as I'm on deodex.

Also as stratosk says do a backup before you try it ;)
[Galaxy S I9000 Android Development] hickup:
Otherwise switch to e.g. Go sms app. Replacement for stock sms. Notification works fine here.
[Galaxy S I9000 Android Development] krige:
Hello,

I compared side by side the color scheme which comes with the standard rom and the voodoo color fix which comes with the Semaphore kernel and I must say the voodoo scheme is way better!

You can see the difference yourself on the following picture:

http://imageshack.us/photo/my-images/684/img2469m.jpg/

It shows two Galaxy S i9000 with white fullscreen in full brightness. Left is standard, right is voodoo. I did the white balance before taking the photo.
[Galaxy S I9000 Android Development] Tilgi:
Hi, do you have choosen any special settings in Go SMS App to get BLN to work?

I just don't get it... because of the fact that bln dosn't work on the stock app i switched over to go sms (besides that really an improvement :) ) but bln doesn't work again... just missed calls are working.

Any hints for me?

Thanks in advance... :)
[Galaxy S I9000 Android Development] pikachu01:
Make sure Blink-LED is on or wipe the data from GoSMS to go back to defaults (your SMS won't be wiped, don't worry.. you could back it up first if you are worried).
[Galaxy S I9000 Android Development] Tilgi:
Hey, thanks for your hint :)

Now it works, but after setting GoSMS back to default I had to turn off "Screen on when receiving a sms" to get BLN to work.

If I set it so the screen turns on for a short time BLN won't blink.

Thats a bit sad because I want the screen to turn on, but on the other side working bln is more important to me :)
[Galaxy S I9000 Android Development] adams.alex:
Hi! Thanks for support, i do not flash this because something goes mad with the phone, now if i receive a sms and i want to open from notification it's not working, is not tell me anything just no work, tap on the message, it goes to message service and in a second of "thinking" back to "desktop". Stock JVR, semaphore kernel, nothing special, not even restore from a back-up. The ROM in fresh installed yesterday, applied all de clean-up.
[Galaxy S I9000 Android Development] BlueKnight83:
Hi to all. I have a simple problem...

I install semaphore kernel and activate the overclocking module. Whit Voltage Control i set the range of frequency to 100 by 800.. and in advanced i disable 1000 and 1200 frequency. I save profile and save it as a boot setting... but when i turn off and then on the phone.. i found whit voltage control that the max frequency is always set to 1200.

Anibody have the same problem?

Thank.
[Galaxy S I9000 Android Development] pikachu01:
Remove the oc_uv script from init.d?
[Galaxy S I9000 Android Development] BlueKnight83:
Hehe.. you are a genius! :D
[Galaxy S I9000 Android Development] mukuro:
Thank you stratosk, it's a pleasure

but, 34 download and 0 feedback ?
[Galaxy S I9000 Android Development] HM.Carbide:
Tested a lot of governor configs, here my results:

Ondemand:

Up_threshold 85 is the optimum. Very snappy and battery efficient.

With 87 there are already noticable lags in 3d games

With 80 it uses noticable more often 1000mhz/1200mhz if enablef.

Changing powersave_bias leads even on 1 overall to lags.

changing Sample_rate slightly doesn't change anything.

So this config is hard to beat. In my opinion a ondemand module with default up_threshold is not necessary.

Conservative:

As the ondemand is really good, i tried to configure a conservative governor that uses significant lower frequencies, but overall speed is still good.

Up_threshold 90

Down_threshold 70

Freq_step 20

@stratosk if you want, you can try these values in your conservative governor modul.

It should be snappier than the default settings due to faster up scaling by using more the lower frequencies due to early down scaling.
[Galaxy S I9000 Android Development] stratosk:
Thanks for testing and your investigation. I will try the values you proposed. But maybe the point of conservative is to be more... conservative:) Anyway, I will try although I don't use conservative in my own phone.

One more point speaking about governors. I strongly believe and I have already mentioned that there no magical solutions. Linux kernel is very powerful and very well tested in millions of system. These governors (exactly the same code) made by experienced developers and run for years in critical 24/7 servers. In my opinion, just a couple of tweaking is necessary to fit to our phones and that's it.
[Galaxy S I9000 Android Development] stratosk:
Welcome to the thread mukuro.

Don't worry about the feedback. This thread is a little bit quiet last days. Anyway, if something was wrong I guess we would have feedback. No news good news...
[Galaxy S I9000 Android Development] mukuro:
all right :D
[Galaxy S I9000 Android Development] PatcheZ:
bln for sms work now, thanks.

Juwe's 5.2 (JVQ)
[Galaxy S I9000 Android Development] HM.Carbide:
Agree, but i've testet the default conservative module, performance is ok, but it is not as battery efficient as your ondemand governor.

Your ondemand governor cannot optimized anymore, so i am trying to optimize the conservative governor for best battery life, to have an alternative with different goal.

I have optimized it a bit more, it now uses very low frequencies, and is still not laggy.

Up_threshold 90

Down_threshold 75

Freq_step 10
[Galaxy S I9000 Android Development] sherpa25:
I'm currently in JVQ Darky Rom 10.2EE w/ Semaphore Kernel JVQ 1.3.3. Can I install Semaphore JVR 1.5 over my current setup, and just flash no-wipe? Or do I have to go to JVR base first? Thanks.

Where do you get the voodoo color fix? Is it an app or an option in one app installed? Or is it only in JVR1.5?
[Galaxy S I9000 Android Development] stratosk:
You can install the latest version 1.5.0v with no-wipe and also get the voodoo color.

Then you can fix the colors with the voodoo control application.
[Galaxy S I9000 Android Development] sherpa25:
I see, so that means I can mix-match diff ROM versions (i.e. JVQ) w/ Kernel versions (i.e. JVR)? All the while I thought they had to have the same base (i.e. purely JVQ or JVR only for ROM/Kernel). In that case, what's the diff between the bases, or how can one know which is better to use? Thanks.
[Galaxy S I9000 Android Development] stratosk:
Actually, the JVQ, JVR in the version name indicates the version of stock initramfs which used with the kernel. There are small changes between them so there are no incompatibility issues. If you are in JVQ, JVR I suggest you to use the latest version (1.5.0 or 1.5.0v).
[Galaxy S I9000 Android Development] sherpa25:
Thanks a lot! ...not that I understand what initramfs is :D ...but I'm sure a google search would address this :)
[Galaxy S I9000 Android Development] stratosk:
It is the initial filesystem that it's embedded in the kernel image. Kernel use this filesystem to properly initialize the system. It also contains all the modules that the kernel uses. The main difference between versions is the precompiled drivers (modules) from Samsung.
[Galaxy S I9000 Android Development] hackeron:
Stratosk: Lukiqq posted some info about cpu steps.. That it might cause instability to have more steps even if you dont use them.. So will u make a version with non-oc default steps ? I would like this.. Cause now I run 1000mhz anyway and have disabled 1200 step. Which might lead to problems-lags.
[Galaxy S I9000 Android Development] darckengel:
Semaphore is much more stable than galaxian without Lukiqq "fixes" ...

I never had any problem with Semaphore Steps, so what's the need of changing that? :)

I have nothing against Galaxian, but there is a fix twice a day ...

So you couldn't really rely on it's stability ...
[Galaxy S I9000 Android Development] s3icc0:
Agree ... but ... non-OC version with default steps would be fine ... I will definitely try ...
[Galaxy S I9000 Android Development] stratosk:
I'm trying some things about this and I have some plans for the next version. Maybe in the next release when I can find some time. :)