yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] kroat999:
I flashed 2.2.1 Firmware and than over it Cm7 0318 Inital with this kernel are iam

doing something wrong that iam getting such low scores 1753

?????
[Galaxy S I9000 Android Development] vukandric:
Did you installed voltage control app? You must apply (menu button while in app and then click apply) after you set all the values. I guess you didn't do that right because I had that score without OC.
[Galaxy S I9000 Android Development] Arkanius:
Reports about the Wifi battery drain? :)

Is it better? Worse?

Fixed?
[Galaxy S I9000 Android Development] kroat999:
yes i did install voltage app Set Scheduler to cfq and Limtit clock 1300 and Apply for Now

Quadrant info shows cpu at 1300 but my scores are between 1600 and 1780

should i flash everithing new

i dont get why my scores are low i think i have done all the flashing stuff right.

hvala na pomoci :-)
[Galaxy S I9000 Android Development] vukandric:
You have a grey button in the bottom of the app (states), where you should tick the values you want. Maybe that is the problem, not sure. Click that button again to hide that menu and then click apply again. And be sure to run quadrant 2-3 times.

Nema na cemu :)
[Galaxy S I9000 Android Development] boarder.2k9:
Its fine, you don't need to do flash again. The other day i was testing out and i couldnt get more than 1750. i tried over and over and couldnt. but today i tried and got 2050. i guess a clean boot, leave it for a couple of mins, kill all apps then try might boost a bit. i wouldn't worry, my scores are similar to yours and my phone runs like a dream.
[Galaxy S I9000 Android Development] muleyman:
I am enjoying CM7 quite a bit. Running OC'd at 1.3Ghz, ondemand scaling. Have tried conservative and interactive as well, but this one seems to be working best right now. I had one freeze when I plugged in USB cable. I've noticed that sometimes the dedicated buttons don't respond unless I power the screen off/on and unlock the phone. Happens fairly regularly. I pulled a 2000+ Quadrant score earlier... but what's the scoop on the 3D graphics/fps being so low? I noticed that when I tried to play a video, (web based, not optimized for mobile devices), it was pretty choppy... not nearly the performance I was getting with 2.2 The screen on/off animations are awesome! I haven't gotten used to it though... I keep thinking my phone is rebooting when the screen turns off. Overall I'm very happy with CM7.
[Galaxy S I9000 Android Development] Razer(x):
Has anybody tried undervolting? How's battery life?
[Galaxy S I9000 Android Development] Tk-Glitch:
@ Razer(x)

Variable :D

It's useable on a daily basis, but Samsung roms gives *for now* better battery life, undervolting or not. I'm actually running 1.4GHz with conservative governor and I'm actually at 46% left after 12 hours of use, the screen being responsible for 50% of the drain (I have a moderate-heavy use of the device). 100-200-400-1000 MHz steps are undervolted and the last one (1400 MHz) is using 1.4v.

Same scenario with a Samsung (based) rom and I would get ~46% after about 20 to 25 hours, to give a good comparison.

Bilboa1 kernel should be a bit less power-hungry than mine though (1.3GHz only and more frequency steps).
[Galaxy S I9000 Android Development] Razer(x):
Thanks, what do you use to undervolt? Can you confirm that this kernel is overclocked by default?
[Galaxy S I9000 Android Development] Tk-Glitch:
This kernel is using 1GHz by default, and you need to use Voltage Control app (available on market / i9000 apps section) to overclock and/or undervolt.

It's pretty simple to use and straightforward. Be sure to test your system for stability before saving your settings to be used at boot.
[Galaxy S I9000 Android Development] Razer(x):
I've just installed the latest update, but my touchkeys aren't working, too bad
[Galaxy S I9000 Android Development] Tk-Glitch:
Make sure you download the one specific for your device.
[Galaxy S I9000 Android Development] Razer(x):
Don't know why, but now touchkeys are working again.

I've succesfully undervolted my SGS, i'll play for some time to test it and i will report tomorrow
[Galaxy S I9000 Android Development] charkey:
I believe there's a bug with the touch keys. I've reverted back to the previous revision. The touch keys light upon touching them after the screen is still locked. Often times the keys would become unresponsive while the screen is active.
[Galaxy S I9000 Android Development] Bo$s:
Same behavior on my device.

EDIT: European i9000.
[Galaxy S I9000 Android Development] kenkiller:
What models are u guys using? BLN works great without problems on my i9000. :D
[Galaxy S I9000 Android Development] zoubidou:
- possibly fixed wifi sleeping issues (battery & crashes, feel free to report any change)

Not sure, but it seems to be worse then before.

not only wifi does obviously not go to sleep when screen is off, as set in settings, but it also remains on at the same time then H/3G. Before, i switched off/on data in settings and then it worked, H/3G off Wifi on, or vice and versa.

Now i have to switch data off/on to make it work each time.

ok for the headphone, it seems to be fixed, i don't know yet if receiving a call with headphones on works, i will let you know when someone calls me.

Concerning BLN: I don't use and thus don't care about BLN, but your BLN fix makes things worse concerning the back and the menu keys. both went off and did not work anymore for a while. I don't know what made them work again, because I switched screen off/on and used the home key several times before both keys worked again, but it could also be some delay or ather reasons that made those keys work again, anyhow this is v"ery disturbing.
[Galaxy S I9000 Android Development] zoubidou:
ok, what I think, what you should do (i am expert on system support and debugging, of all kind of systems -from IBM Mainframe down to Company build Bettingstations - and I have 30 Years of experience in this things. So far for my background.

I would suggest that you first of all, fix the outstanding issues, and then add new functions.

Like there was a headphone pb, only fix this issue, have it tested, and when ok, go for next issue.

This way it will prevent from interaction between new functions, old problems, and simple modifications.

This may increase the number of releases, but it will be less frustrating for the users/testers.

It will make problem reporting simpler, because only the concerned users will report problems on known issues.

Like i would really like if you could concentrate on the wifi/3g on off problem. This issue is a long lasting open problem and no kernel writers got it fixed, in fact it looks like no one really understand what's going on, but it is definitively battery draining.

Once you get this fixed i am sure battery life will be much longer for everybody.

However, these are only suggestions, you do whatever you like, and get organized the way you understand it best.

IF SOMETHING WORKS DON'T FIX IT
[Galaxy S I9000 Android Development] kenkiller:
But it works for me now......no wifi/3g switching problems. BLN works fine too.

So there has to be another problem elsewhere.
[Galaxy S I9000 Android Development] ^Sbk79^:
100% agree. :cool:
[Galaxy S I9000 Android Development] kenkiller:
That and the backlight on buttons not timing out. :D
[Galaxy S I9000 Android Development] kenkiller:
Cross posting here as I'm not sure if it's kernel related
[Galaxy S I9000 Android Development] bilboa1:
the touchkey not timing out is a bug also upstream, in case you haven't noticed before xD

the only "issue" atm is that the touchkeys stay enabled while sleeping and can be light'd up by touching them

as for the other issues that are also upstream:

- test with "stock" kernel, report a bug in their bugtracker & hope they'll fix it

- do the same and hope i'll fix it or someone else fix it

- fix it yourself and submit patches

- pay someone to do it oO

Now that said, about the wifi issues:

the fix comes from google, in fact. battery issues are inherently difficult to figure out and most of us have only an hour here and here to work on that stuff, not whole days so it's more like a best effort than guaranteed quick fixes =/

3G switch etc: no idea, since it doesn't annoy me I don't look at it - i prefer fixing the stuff i use first ;)

battery temp: again it doesnt affect me and is from upstream, but if you know precisely where this is set i can bump it up, otherwise you'll have to hope i find time/will to look it up :P its that simple lol

battery not hitting: 100% IT NEVER DID. The counter was just lying to you before, now it doesnt lie anymore. That's all. Get over it. It will almost never display 100 anymore, unless devs get pissed with complains and make it lie again - still wont really hit 100%, will just make you believe so.
[Galaxy S I9000 Android Development] Mercury0660:
I think, and I hope I am not the only one, that the buttons should light off after some seconds. It's very annoying, when i.e. lying in bed and reading with screen filter on for lower intensity and you always have to lock and delock to get these bright shining lights off. So I hope you can fix that. And thanks for your work ;)
[Galaxy S I9000 Android Development] kenkiller:
Ah...maybe this could be a factor.

I'm using Widgetlocker as a lockscreen replacement, meanwhile it has the ability to ignore keypresses and only accept those that u allow.

This could be the reason why I'm don't seem to be able to activate the button backlight when phone is in sleep mode.

However, I tried disabling Widgetlocker and still I'm unable to make the buttons light up by touching them in sleepmode. Is it an easily reproducible occurrence?
[Galaxy S I9000 Android Development] Mercury0660:
for me, with latest kernel, button backlight switches on when touching in sleep mode and off when pressing home button (of course, screen switches on then)

edit: lol, after a reboot, the problem is gone.

I changed the intensity in cyanogen option to zero, saved, then to 255 again, saved and now, backlights don't switch on when in sleep.
[Galaxy S I9000 Android Development] kenkiller:
Relax man...u seem angry. :D

I was just asking if it's kernel related why the phone doesn't resuming charging if it was previously stopped because of the temperature limit? If it stopped at 45 degrees, shouldn't it resume when it has dropped to say maybe 32 degrees?

Or is this only on my set. :)
[Galaxy S I9000 Android Development] melorib:
+1

I didnt bother trying disable...
[Galaxy S I9000 Android Development] kenkiller:
Tsk tsk....we should try to provide info to help those who are experiencing problems, narrow down the cause. :D
[Galaxy S I9000 Android Development] melorib:
I would, but you beat me to it... :rolleyes:
[Galaxy S I9000 Android Development] Flozzo:
I have the same problem, but somehow this occurs (only?) when it is below 15%. could just be me, as I dont charge it with more than 15% remaining ;)

Oh and its on all 3 kernels for me

CM7 FTW @ SGS - Tapatalk
[Galaxy S I9000 Android Development] g00ndu:
bilboa1, just a feedback and not asking for a solution. I tried your kernel and the bln on the latest MIUI beta6 rom and it totally breaks the 2 touch buttons that I need to reflash the rom again. Didn't try the o/c function. Otherwise it is still a great kernel.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] shaolin95:
Sweet I will test LCD Density and report back! :)
[Galaxy S I9000 Android Development] kenkiller:
Mine doesn't just happen at a set percentage. It happens as long as it stops charging due to temperature reasons..... :( I really have to make sure it's still charging before going to sleep. If I somehow make it overheat before bed, I have to wait for it to go down, unplug, replug make sure the charger indicator is shown. :)
[Galaxy S I9000 Android Development] Flozzo:
As I already said, I dont charge above 15% (except for USB charging @ PC) so I cant really tell you that ;). Another bug I've come across is the menu/back buttons sometimes just stop working, lock/unlock solved it twice, but one time I actually had to reboot :/

Oh and I had a crash listening to music, but that could be anything :S
[Galaxy S I9000 Android Development] kenkiller:
Hehehe...my life isn't as fixed, I have to charge as often as I can. If I could wait till 15% I probably wouldn't yaking here. :D
[Galaxy S I9000 Android Development] BlackDino:
Btw, anyone that accidentally hits the touch keys while the device is locked,

you can hit the volume rocker to set the touch keys back to off.

And when receiving a text message your keys will not turn off when hitting the volume rocker so you know for sure it is a notification
[Galaxy S I9000 Android Development] cocchiararo:
How much uv is normally safe?

I enabled 1000, 800, 400, 100 and one more frec I don't remember now.

My battery is running out way to fast, IM trying anything I can think of now
[Galaxy S I9000 Android Development] DROCSID:
My backbutton is not working anymore with the last update (today / 22).

Bleeeegh /out

(but besides that it works great, proper respect for the BLN)
[Galaxy S I9000 Android Development] Razer(x):
I'm actually at 50 50 50 75 100 100 with no crashes.

But my battery is running out fast too
[Galaxy S I9000 Android Development] cocchiararo:
mine was running out really fast before this kernel too.

My phone can't make even 6 hours now :P
[Galaxy S I9000 Android Development] shaolin95:
Aguante Boca!

You can play with UV as much as you like pretty much since you cannot really damage the hardware undervolting. I normally use -100 from 100Mhz to 1000Mhz but each phone is different so it takes trial and error for the most part.

UPDATE:

Tested LCD Density on Captivate and it works great! Thanks

Would you consider adding 1.4Ghz :D
[Galaxy S I9000 Android Development] n0stalgia:
The capacitive softkeys don't turn on after standby sometimes on the Captivate. Possibly a BLN issue? Is there any way to concretely disable it in CWM or something?
[Galaxy S I9000 Android Development] DvTonder:
Same just happened to me on the Bell Vibrant (i9000m = i9000)
[Galaxy S I9000 Android Development] damianarnold:
Boots initially with working softkeys then after the first switch off they don't work again. A reboot repeats the cycle :(
[Galaxy S I9000 Android Development] Corvillus:
BLN support as currently implemented seems to breaking the touch buttons, regardless of whether or not BLN is actually enabled. The reason I say this is that every time I receive a notification in standby, they break. They always start working again after checking the notification bar, then locking and unlocking the phone.
[Galaxy S I9000 Android Development] zacharias.maladroit:
does the following commit look useful:

touchscreen update

I stumbled over it for my research right now,

it's for the galaxytab but the settings mentioned there might be interesting ...
[Galaxy S I9000 Android Development] damianarnold:
Makes sense, thanks for that!
[Galaxy S I9000 Android Development] Razer(x):
How do you test system stability with UV?
[Galaxy S I9000 Android Development] shaolin95:
You should be able to limit the cpu speed to the particular one you are testing under the CM Performance option (I hope that works) like changing it to min 400 max 400 for example.

Not sure if it works with this kernel.
[Galaxy S I9000 Android Development] zacharias.maladroit:
run benchmarks & stuff

basically everything that stresses the undervolted CPU

when it doesn't get enough juice - it'll hang
[Galaxy S I9000 Android Development] Razer(x):
Yeah, but then how do you test it? Games?
[Galaxy S I9000 Android Development] mcord11758:
This its running great on my captivate running miui. Bln works except for google voice, under clocked to 800 with light uv. Battery is holding up well 70% after 6hrs moderate use

MIUI
[Galaxy S I9000 Android Development] DROCSID:
Hahaha damn, why didn't I think of that, that makes sense indeed. Well, it's worth waiting for this bug to be fixed, I missed BLN for such a long time.
[Galaxy S I9000 Android Development] gabby131:
i finaly found the official thread for cm7 kernel!! that was so slow and so dumb of me!

the latest (20110323_22) has OV to 1.3GHz and so smooth..... :)

have not tested stability yet....
[Galaxy S I9000 Android Development] apewall:
I can confirm since BLN was added the softkey buttons stop working randomly on the Captivate, locking and unlocking the device with the power button temporarily fixes this.'

Edit: Happens with BLN turned off or with it on.
[Galaxy S I9000 Android Development] zacharias.maladroit:
what tool are you guys using for OC/UV ?

VoltageControl ?

which specific version ?

I'm only getting a "Unsupported kernel detected" error with my test-kernel
[Galaxy S I9000 Android Development] shaolin95:
Test with games or apps designed to test stability. Check the link in my sig for example.
[Galaxy S I9000 Android Development] redbull320:
this kernel or zacharias.maladroits ?
[Galaxy S I9000 Android Development] omiks3:
+1 touch keys not working properly on the newest kernel.

Went back to 03.23.02
[Galaxy S I9000 Android Development] zacharias.maladroit:
teste doch einfach beide und nimm dann den, der dir zusagt

simply try both and then take the one to your liking
[Galaxy S I9000 Android Development] derrzredeem:
Yes, ver. 3.0.3. And sometimes i get that "BAZINGA" too.

@bilboa1: thanks very much for this, gotta love oc/uv :)

I had a question tho, theoritically, if i reduce the states, let say, from 200-1300. Will it affect the performance or battery life? How?

Cause i observe with system panel that my cpu frequency has never drop to 100 (governor is interactive - as i find that works best for me). So i wonder if it had any positive effect, i could just skip that state.

~drz
[Galaxy S I9000 Android Development] muleyman:
Just switched back myself. It seemed to get worse the longer it went. Not having the issue on 3.23.02

As for battery life... well, I've been running at 1.3GHz on both .02 and .22 - and it's been quite stable - only one freeze so far but I'm getting about 5-1/2 to 6 hours on a charge. Running at default voltages.
[Galaxy S I9000 Android Development] bilboa1:
with interactive it rarely goes to 100Mhz i'd recommend ondemand atm.

smartass could be tweaked to behave more like ondemand (actually its supposed to) - but it doesnt either right now
[Galaxy S I9000 Android Development] bilboa1:
so mmmh in newest kernel i fixed a few things including bln and touchkey handling.. afaik upstream don't want it fixed and like it the way it is :(

anyhow!

please tell me if this breaks on vibrant captivate or sgsb. it should work on sgs, but i can't test the other 3. if you tell me it breaks please be specify how and in what ways. thx
[Galaxy S I9000 Android Development] kenkiller:
My god...you managed to make button backlight stay off when screen is on!! :D
[Galaxy S I9000 Android Development] r3ferrei:
I didn't know if that was a bug or a bug fix. Like you I consider it the latter :)
[Galaxy S I9000 Android Development] DvTonder:
Buttons seems to work the way they should now. Turning off after a short delay and no longer responding when the screen is off.

I am also noticing better battery life with your kernel since last night.

Thank you.
[Galaxy S I9000 Android Development] bilboa1:
the truth is that the handling was buggy, now.. well i don't know it seems obvious to me it should timeout after the push, but hey. i suppose some might like if they would always be off, but making it optional would be a pita.

one can always recompile his own kernel and turn them always off if one likes ^^

i'm happy how it is now, lights only when i push (with screen on).. or for bln
[Galaxy S I9000 Android Development] kenkiller:
Definitely a bug fix...can't think of many people blind enough to need lights to use those 2 buttons. :D And it still lights up, just doesn't stay lighted up, which is useless imho. :D

It behaves exactly how the i9000 used to behave on stock Samsung, just with a shorter cutoff time, which I am even more grateful for. :D
[Galaxy S I9000 Android Development] kenkiller:
Another issue on the CM7 list of bugs that should be struck off....unless they don't intend to incorp it?
[Galaxy S I9000 Android Development] joaoennes:
Thank you for the Touchkeys light fix, that's how it should be i think. :D
[Galaxy S I9000 Android Development] bilboa1:
let me know if you'd prefer a longer timeout, im just curious. i don't really mind myself as long as it does timeout
[Galaxy S I9000 Android Development] apewall:
captivate here, softkeys no longer light up on screen touch.. and they timout after about 1 second which seems rather fast.
[Galaxy S I9000 Android Development] Arkanius:
It's not a bug because it's the intended behaviour. The backlights on the Nexus S are always on until you turn off the screen
[Galaxy S I9000 Android Development] DvTonder:
2 seconds may be a bit better as it currently seems a bit short.
[Galaxy S I9000 Android Development] joaoennes:
Probably a little longer timeout would be better for users used to samsung way, but for me it's fine.

When you press the key you don't need the light active much longer to say where is the key, you already pressed so you know :)

P.S. I'm using the 1.3GHz and no problems so far, none. The battery lasts just little bit less, off course :rolleyes:, but I have no reasons so far to underclock it back to 1GHz.
[Galaxy S I9000 Android Development] zacharias.maladroit:
intended behavior yes,

but there seem to be large differences between the luminosity (or brightness) of the softkeys between Nexus S phones

so of course the current provided behavior by bilboa1 is the preferred one (at least for me) if the soft keys are very bright and disturb the usage of the phone especially in dark environments

@bilboa1:

well done :)
[Galaxy S I9000 Android Development] boarder.2k9:
absolutely loving all the progress bilboa, your kernel is awesome. Regarding your previous post, i wouldn't mind the timeout a little bit longer (but if you can't be bothered to change it by all means don't). Just loving how much you get done, its a surprise every day!
[Galaxy S I9000 Android Development] g00ndu:
Update: I realized that the kernel and BLN app from market does not break my touch buttons, my apologies. Does the test function in the BLN app works for you guys?

Anyone tried Blinky with this or zac's kernel? Seems that I have problems with that.
[Galaxy S I9000 Android Development] gabby131:
@bilboa1

i can tell that the touchkey issue is gone in version 20110325_00. I also notice the quick timeout of the lights but does not bother me as long as the keys are properly working...thanks..... :)

EDIT: apologies, im using a Rogers Cappy....
[Galaxy S I9000 Android Development] bilboa1:
made a tiny update with longer timeout - if you don't care about that you don't need to flash
[Galaxy S I9000 Android Development] apewall:
Touchkey bug remains for captivate - Randomly touchkeys stop working.
[Galaxy S I9000 Android Development] vukandric:
Thanks, this one is great! :)

Edit: Just had 2 random reboots in a couple of minutes.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] jetpackjeff:
Random reboots as well with latest build, 3 in last half hour. Unrelated to wifi...
[Galaxy S I9000 Android Development] Corvillus:
Bug still exists for me as well on my I9000M, however only for the duration of the timeout. I can live with that. :)
[Galaxy S I9000 Android Development] mcord11758:
No issues on my captivate with latest build.

MIUI
[Galaxy S I9000 Android Development] jimmy-bish:
Hey Bilboa. Firstly, great work on porting much-loved features to CM7! :D

I just flashed from 20110323_22 to 20110325_02, and now my capacitive buttons don't work. I've tried rebooting and powering the screen on and off, but no change. The buttons are useless at the moment.

I also noticed a much larger delay when powering the screen back on from standby.

I'm running the nightly CM7 build from the 18th, your latest kernel, JPY modem. As mentioned, everything was pretty sweet until this latest flash.

Any hints or logs you want me to gather?

EDIT: Flashing to old kernel and back again sorted it out. Sweet! :D