yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] zacharias.maladroit:
for me the touchscreen has between the just right to somewhat to insensitive

FYI:

Tuning the touchscreen sensitivity

powersave is way to slow:

the GUI and everything would lag significantly (I once had that set and the phone's lagging would annoy the hell out of me)

keep in mind that the 90screenstate_scaling script is running in the background so you only need to change

AWAKE_GOVERNOR="ondemand"

to

AWAKE_GOVERNOR="conservative"

while the screen is off - it's already at powersave (maximum saving at 100 MHz)

1) adb shell

2) su

3) vi /system/etc/init.d/90screenstate_scaling

4) navigate to ondemand

5) press [insert] key

6) change ondemand to conservative

7) [ESC] key

8) :wq!

9) enter

after the next screen turning off and on it should be in effect
[Galaxy S I9000 Android Development] Ferdimage:
i can also confirm that battery temps have risen 9-10% more :O (on idle)
[Galaxy S I9000 Android Development] quadix:
my browser is still crashing when i try to open him, it start happening after i install your 20/03 kernel, i try to get back to the stock kernel and it still crashing, i try to clear cache, dlavik cache and install the cm7 update again and again, and the problem is still there.

help me :(
[Galaxy S I9000 Android Development] zacharias.maladroit:
perhaps my issue with the crashing browser is related to yours :confused:

make a backup and do a factory reset/wipe
[Galaxy S I9000 Android Development] kenkiller:
Browser isn't crashing for me on either wifi or 3g. Bit.ly also works fine.

However the camera seems to be a bit wonky. I start the default camera app, go to FFC, try to revert to back camera without taking a shot, phone reboots. That's ok since the FFC is still buggy.

I then start the camera app, just swing around without taking a photo. Then I exit the default camera app, start another camera related app, camera360. It say initializing camera for around 30secs, then phone reboots.

After that, I start camera360 directly without touching the default camera app, it works fine. Seems that starting the default camera app makes camera access from 3rd party apps slightly problematic. Just fyi.
[Galaxy S I9000 Android Development] Ferdimage:
just a quick question on Voodoo Color Profile setting,

what profile are you guys using original 2.3.3 or voodoo profile?

I cannot notice any difference between them...
[Galaxy S I9000 Android Development] derrzredeem:
I don't think it's working atm.

In zac's nor bilboa's kernel.
[Galaxy S I9000 Android Development] supercurio:
There is not any.

Existing profiles are only for < 2.6.33 drivers, for kernels including 2.3.3 driver, those are ignored (gamma tables are not loaded in kernel because not the right size)
[Galaxy S I9000 Android Development] Ferdimage:
Thanks for clarifying supercurio :)
[Galaxy S I9000 Android Development] zacharias.maladroit:
ok, thanks !

thanks !

haha, yeah,

it would have been weird if the higher battery drain or usage persisted

Netarchy is also using the 1000 Hz on his Nexus S kernel (according to TheEscapist)

I'm currently running a test-kernel with 300 Hz; USER_HZ raised (from 100) to 150 and the default timer at 128 Hz (if that setting even makes a difference)

and so far everything is really smooth

Gun Bros runs awesome, etc. etc.

during the first crash some files got screwed so you need to remove those (perhaps corrupted; most probably temporary/cache files)

factory reset/wipe did it for me

but the browser is still crashing occasionally

I switched to Dolphin HD (also using webkit as rendering engine) and almost the same happened: the browser almost instantly crashed during loading of the site (mostly those are github sites from my cyanogenmod twitter feed) but the phone didn't reboot / crash

so it has to be a (security ?) BUG in Android which probably could be used to crash & reboot the phone - strangely this should be prevented since stuff is supposed to be running in sandboxes in Android to do no harm

reboot / crash is no real harm but it could lead to data loss when you input data or have something running in the background which hasn't been saved yet

I've just switched to Opera Mobile and that one isn't crashing so far

summary:

so - as stated above - it seems to be a BUG in Android that seems to get triggered more easily with this kernel - or if happening with stock kernels by these particular websites and their content

thanks !

yeah, the camera app seems to induce a strange behavior at the system

it however works for me with the new test kernel I'm currently running (switching from back camera -> FFC -> back camera)

the weird thing is that the picture of the FFC is 90° turned clockwise

normally you should be able to see yourself kind of like in a mirror but it's turned 90° XD

I get this with the Cyanogenmod/AOSP camera app and Vignette

so it has to be a driver issue :D

@all:

thanks for your feedback

I'll upload another test kernel (the one I'm currently testing)

with default timer 128 Hz; HIGH_RES_TIMER 300 Hz; USER_HZ 150 Hz

I've also noticed a warm battery with this but only during charging (via usb-connection in this particular case; 43°C - 45°C)
[Galaxy S I9000 Android Development] patrikmuse:
i have a problem with last kernel (21/3)

i use the bt streaming feature and when the screen goes off, the music become laggy.... to solve i have set minimum cpu frequency to 400 and is ok, but before that release i havent this problem....
[Galaxy S I9000 Android Development] g00ndu:
@zac,

Can I use your kernel on the latest MIUI beta5? Cos, I want the debug mode to be off. :D
[Galaxy S I9000 Android Development] freakfingers12:
Yes, it's compatible. Testing out now.
[Galaxy S I9000 Android Development] DvTonder:
Can I make a suggestion:

Since CM7 is still very much pre-beta, I am of the opinion that introducing too many 'bells and whistles' features such as security hardening in these kernels is just complicating things needlesly.

My suggestion would be to focus on the basic functions such as speed optimization, removing debug, battery life tweaks and proven enhancements like Voodoo and BLN etc. until the CM7 base becomes more stable, then start throwing in the kitchen sink.

Just my 0.02c.

I do tip my hat to the OP and others that are contributing to this amazing community and making our mobile experience so much better. Thank you.
[Galaxy S I9000 Android Development] Arkanius:
How is battery life if I do not want to mess with the OC/UC and voltage settings?
[Galaxy S I9000 Android Development] melorib:
+1

The most sensible request I read so far... :)
[Galaxy S I9000 Android Development] zacharias.maladroit:
thanks !

security in 99.9% doesn't hurt since the only one that could lead to adverse effects is the fstack-protector feature which I could easily deactivate at compile-time

the improved ASLR security is somewhat a MUST nowadays

the other features are enabled via sysctl (on the fly) & should do no harm & also are needed

switches that might hurt compatibility and/or apps running (such as breaking compatibility with older apps (e.g. a Launcher)) like in FuguMod are omitted - at least for now

unless of course they become a threat

- basic functions such as speed optimization,

[x] check (I'm kinda constantly experimenting & search for speed improvements)

- removing debug,

[x] check

- battery life tweaks

[x] check (UV/OV will be added once it's more stable and not leading to even more draining of the battery :p ); I've added several to (at least theoretically) prolong battery life

- and proven enhancements like Voodoo

[x] check

- and BLN etc.

[x] check, currently waiting for upstream Neldar's supposed to add fixes today & TheEscapist and/or bilbao1 are currently working on it

so in summary:

I'm following those principles already ;)

thanks !

it should be turned off by default unless you're activating it via VoltageApp / SetCPU or whatever the apps are called

I won't include it unless it's not hurting battery runtime

a already high battery consumption + OC/OV in my opinion is useless and not worth the effort (unless of course you've got a really BIG battery)

luckily it also includes support for UV (undervolting)

hey - I'm already following those

so - I guess you could call this kernel "sensible" ;)

here's the current kernel I'm testing right now - it should be somewhat more stable (a little slower than the previous one 03/21) but using less battery
[Galaxy S I9000 Android Development] Arkanius:
Ah just installed the Kernel

Thank you for the improvements!

And thank you supercurio for restoring my SAMOLED screen back to how it was :)

About the security enhancements: As long it doesn't break anything, we never have too much security
[Galaxy S I9000 Android Development] alerems:
Big tux for the latest release, let's try it abdominal report later.

And if u need a beta-tester u can ask me.)
[Galaxy S I9000 Android Development] melorib:
There must be very large differences between Galaxy S screens, I remember the arguments when Hardcore was trying to please everybody... ;)

My screen looks much better with standard CM7 than with the mods, strange... :confused:
[Galaxy S I9000 Android Development] Arkanius:
There are different screens, from different production times, basically, when Google implemented the new colour table, it only looked right on some screens, the others remained "washed out" and with the gamma way to high and with some yellow-ish tint

That's why everyone reports different results
[Galaxy S I9000 Android Development] supercurio:
Yes that's why you can reset values to the exact default ones in Voodoo Control app.
[Galaxy S I9000 Android Development] melorib:
The function is there, but it doesnt seem to work, I tried it with both alternative kernels, I ended up having to play with the RGB sliders, and could never get identical results... :o
[Galaxy S I9000 Android Development] Arkanius:
I had three random reboots, probably related to this kernel since they did not happen before under the same circumstances:

Adding or removing a Facebook account under Accounts x2

Opening a RSS feed under Google Reader

They seem so random. They could also be Wifi related but just saying.
[Galaxy S I9000 Android Development] bilboa1:
the wifi bug actually should/could crash only when it goes to sleep (usually on screen off)

well, theoretically of course ;) - it can always be something different
[Galaxy S I9000 Android Development] Arkanius:
The screen was on both times.

Actually it seems Wifi is going to sleep correctly. Or atleast never had a reboot due that.
[Galaxy S I9000 Android Development] strickyy:
I flashed 03/17/2011 complete update the last time. What's next? Which CM7, kernel, or update?
[Galaxy S I9000 Android Development] zacharias.maladroit:
thanks

interest in a beta tester ?

lol - I believe I know why it still crashes from time to time

I accidentally left a optimization flag on (-O2) that only should have been there once for a test :eek:

mea maxima culpa :o

so this makes the whole bunch of flags interact even more aggressive and thus unpredictable

thanks for your report Arkanius !

I believe I know what is causing this,

I'll go through the flags again and probably do 2 test builds to get a more stable base

interest in test-driving them ?

yes, it crashed for me pretty reliably when the screen was off

but then I set it to turn never off and it worked ;)

install the 03/18 nightly from sourceforge then install the latest kernel

@all:

interest in becoming a beta tester ?

I'm gonna bake at least 2 kernels in the next time to figure out some more stable flags

thanks !

@all:

sorry for any inconvenience - if you get any crashes

the next kernels should be stable again like earlier builds
[Galaxy S I9000 Android Development] Razer(x):
I can test them if you want, just tell me what you need to test
[Galaxy S I9000 Android Development] lmulli:
Hello,

With your latest Kernel, my Wi-fi no longer connects (stuck on obtaining an ip address). Gone back to an older one and all is well. (also tried bilboa's latest and that work fine)

ta
[Galaxy S I9000 Android Development] Arkanius:
I'll be waiting for them then. I haven't had any more crashes but it would make me at ease knowing I could go to sleep without it crashing in the morning or something
[Galaxy S I9000 Android Development] melorib:
Never happened to me since I changed to CM7, cannot say the same about Samsung ROMs, tweaked or not, no alarm in the morning a few times... ;)
[Galaxy S I9000 Android Development] zacharias.maladroit:
thanks for the report patrikmuse !

you tried the kernel from today ? (03/22)

in that I switched from ondemand to conservative governor

so the change in frequency shouldn't be so abrupt and things going more smoothly

check your PM

thanks !

sure,

please check your PM

thanks !

thanks for the report lmulli !

anything special with your WIFI configuration ?

I'm currently testing a (from what it seems until now) rockstable kernel with less crazy interacting optimizations flags that hopefully should work better

otherwise it could either be an issue with your phone or the WIFI
[Galaxy S I9000 Android Development] cocchiararo:
im downloading the last kernel now, but the previous one cuased phone reboots when trying to use atrackdog XD
[Galaxy S I9000 Android Development] Arkanius:
The browser is making the phone reboot a lot, one more time.

I would go back to the default kernel but I'm quite dependent on Vodoo color and sound :)

Can't wait for the next stable release
[Galaxy S I9000 Android Development] zacharias.maladroit:
yeah,

sorry about that :o

it more and more becomes apparent that this is rather a browser (or even webkit - the rendering engine of the browser) issue than a kernel issue,

the kernel might trigger it to happen more often but it now also happens with the 2nd kernel I'm testing which uses basically the flags from laststufo (the flags in older kernel releases) and his SuperOptimized kernel (minus 2 very very risky flags) which didn't have or had less to no issues (from time to time I got a reboot but not this often like now)

this needs some good testing ;)

there are several ways I'm trying to break it and the 1st one already rebooted with the browser :rolleyes:

I hope the 2nd one is stable enough

or this needs some testing with stock kernel & then filing a bug at google
[Galaxy S I9000 Android Development] Razer(x):
Zacharias check PM

EDIT: Early report, LauncherPro crashed at boot. No problem with the camera and game tests so far. The phone reeboted itself after opening the browser (wifi).
[Galaxy S I9000 Android Development] zacharias.maladroit:
thanks Razer(x),

your feedback is really appreciated

are the crashes with LauncherPro reproducible - happening after every boot

- can it be "recovered" after launching it again ?

was there specific content on that site - bit.ly or github ?
[Galaxy S I9000 Android Development] Razer(x):
Yeah, it crashes after every reboot, and the app works flawlessy the second time. The problem is fixable with a wipe + restore

No specific content, i wasn't able to write anything, the crash was faster than me
[Galaxy S I9000 Android Development] zacharias.maladroit:
did the wipe + restore also fix the browser problem ?

usually this is taken care of after I've factory resetted/wipe'd it and restored a backup from some days back
[Galaxy S I9000 Android Development] kroat999:
Why i have red lines in Camera.

and can this be fixed?
[Galaxy S I9000 Android Development] Razer(x):
No the browser problem isn't fixed unfortunately.

Are these results somewhat strange? Has somebody tried the second kernel?
[Galaxy S I9000 Android Development] zacharias.maladroit:
this was supposed to be a closed testing XD

I'll post it ASAP:

edit:

here it is:

everyone TEST this please for STABILITY

edit2:

@Razer(x):

what base system are you using - the nightly from 03/18 ?

I'm currently using that too for testing purposes to get easier reproducibility

from my testing I haven't seen any crashes, FCs, significant lags or reboots so far with this kernel

you also get this with stock kernel ?

devs are waiting until Samsung releases the source code for their Gingerbread kernel to merge (compare and put together) the differences

this should make fixing it way faster and easier
[Galaxy S I9000 Android Development] Razer(x):
Yes i am using this version. No crashes with the browser? Weird, i'll try to apply the initial update and see what happens

Just a question, have you already found any battery life sucker settings? We gotta improve it as much as we can :)

EDIT: I wiped the phone and applied the initial package, the browser didn't crashed this time (really strange)
[Galaxy S I9000 Android Development] cocchiararo:
does the atrackdog app use webkit in any way ? to show adds ? :P dunno
[Galaxy S I9000 Android Development] kroat999:
I get this red stripes on camera with every kernel for 2.2.3

Only 2.2.1 works perfect
[Galaxy S I9000 Android Development] Steyux:
New kernel with lastufo flags is awesome! No problem with browser and no random reboots :D

It could be a perfect kernel if it will include bln :P
[Galaxy S I9000 Android Development] zacharias.maladroit:
not yet, ah - you mean were you could potentially safe battery ?

yes, I already did some research & found "buttons" but haven't looked at tweaking them yet

real life has been busy,

I'll most probably take a look at it in the weekend, first I gotta find out were those "buttons" are located with the Gingerbread kernel ;) (2.6.29 -> 2.6.32: made it harder; 2.6.32 -> 2.6.35: much more complicated compared to 2.6.29/2.6.32)

glad the browser doesn't crash for you anymore

it probably does

does the crashing or issues still happen with the kernel from 03/22 ?

thanks

like I described in my post or you can read in the main CM7 thread

it's a known issue with the horizontal (or vertical) red lines

since it doesn't appear in the taken picture it's only of aesthetic nature right now

hopefuly it will be fixed once the sources are out (like I explained)

glad you like it :)

thanks for your feedback - finally they're not crashing anymore :D

it will include BLN (I haven't used it with Froyo ROMs yet but I'm looking forward to trying it out - it's quite useful)

but currently it's not available yet

also: real life's busy ...

The following post is taken from the Q&A subforum section as kwantenmechaniker can't post here yet:

Hi kwantenmechaniker,

did this problem with the picture also happen with earlier kernels (from 21st or earlier ?)

the vertical (or horizontal) red lines are a known problem right now

but should only be an aesthetic issue - with the taken picture they're not present anymore

so it's probably an camera overlay or camera driver problem

sorry - I took several pictures and couldn't reproduce your truncated picture

yes, I noticed the 90° (clockwise) rotated picture, too

others get this with bilboa1's kernel also - so it's an upstream problem

you could try one thing:

make a nandroid backup then do a factory reset/wipe and see if that "fixes" it

if not you have a backup to restore

currently I'm out of ideas what might cause this
[Galaxy S I9000 Android Development] Razer(x):
BLN seems to be arrived :rolleyes:
[Galaxy S I9000 Android Development] quadix:
what is the mean of "laststufo" in the latest kernel name?
[Galaxy S I9000 Android Development] zacharias.maladroit:
thanks, I'll take a look at this later

seems like currently it's not working optimally

bilboa1 got a fix for WIFI which might (potentially) improve battery runtime A LOT - kudos to him & Dmitry Shmidt from Google

Google FTW !

it's "laststufo_SO-Kernel-style" to be precise

and if you had read the last few posts you would know that this refers to the optimization flags used in his SO (super optimized) kernel :p
[Galaxy S I9000 Android Development] Alberto96:
why not oc/uv version of kernel?
[Galaxy S I9000 Android Development] zacharias.maladroit:
like I stated before: it will come pretty soon

first stability with current kernel needed to be ensured, then new features can be added

stability -> new functionality -> stability -> new functionality and so forth
[Galaxy S I9000 Android Development] Arkanius:
I had gone to bilboa's kernel since it was stable with the browser/google reader/random internet application

However it is bugged with the headset so I reverted to the latest kernel version from you which seems has fixed the instability of the browser.

I'll keep you updated if it reboots randomly somewhere else
[Galaxy S I9000 Android Development] zacharias.maladroit:
yes, please

report any problems you're encountering - I might run into those problems during testing - but this is not ensured since I've only a limited set of tests to run for a new kernel release

and using it for my daily driver

besides that during the day I'm studying & doing other things

so if you have it running, e.g. with Facebook, beautiful widgets, etc. etc. in the background or exotic apps - you might encounter those earlier (if existant)
[Galaxy S I9000 Android Development] Arkanius:
I use the cellphone heavily and CM7 is my main driver/ROM at the moment

If something shows up, I'll report here, if it isn't kernel related, I'll report to the CMSGS team
[Galaxy S I9000 Android Development] Razer(x):
Didn't notice this post before.

Well done zacharias, keep up the good work :D
[Galaxy S I9000 Android Development] bilboa1:
i heard the cmsgs team was working on these buttons, probably for a future release, but i dont know if thats true

another thing that would be nice is look in 2.6.29 or older .35 what made the touchkey buttons switch off after a few seconds of timeout as its broken atm xD

ill try to find that some time tho, BLN isnt all that nice with that bug imo
[Galaxy S I9000 Android Development] quadix:
the interactive governer is much smoother then the constructive, when i try to change to interactive in the setting is back to the constructive after the screen is off, because your kernel.
[Galaxy S I9000 Android Development] zacharias.maladroit:
sure - I'll look into that as my time permits

thanks !

yeah - it's my kernels fault - NOT :D

I decided to use the conservative governor as default while the screen is on for battery consumptions reasons

as soon as the battery drainage isn't so high anymore I'll set it back to ondemand,

reasons are in bilboa1's and this thread to be found why I won't hard-set "interactive" as default governor [due to ticks and not letting the system really sleep - it's always on the run keeping the cpu alert] (perhaps "smartass" governor in the future if that works well)

so you decided to change to interactive - fine - congratulations:

I've posted an easy guide on how to do it:

I'll repost it here:

source: http://xdaforums.com/showpost.php?p=12276137&postcount=414

hope that helps :)

thanks for using !
[Galaxy S I9000 Android Development] nanu_x2:
is it possible to add divx codec support..??

thanks for your work..:D
[Galaxy S I9000 Android Development] zacharias.maladroit:
that's not a kernel thing

you could try pushing the divx.apk (or what its name is) from a samsung ROM to your /system/app folder

whether that works

thanks for using ! :)
[Galaxy S I9000 Android Development] Razer(x):
Just noticed a reboot while playing around with Runtastic Pro
[Galaxy S I9000 Android Development] kenkiller:
While I do appreciate the battery savings in change of governer, it does make my Feedr reading super jerky.

Is bilboa's kernel on the same governer settings? Because his seems to work much smoother. Yours and his on the latest version at this time.
[Galaxy S I9000 Android Development] zacharias.maladroit:
OK, this one should be easier:

1) set from conservative to ondemand in the update.zip

extract the 90screenstate_scaling

from the zip-file

(/system/etc/init.d/)

then change AWAKE_GOVERNOR="conservative"

to AWAKE_GOVERNOR="conservative"

2) after that delete the existing 90screenstate_scaling in the zip-file (with Winzip, Winrar, 7zip, etc.)

3) and pull in the new one you just modified into the zip file

4) put the modified zip on your phone

5) reboot into CWM Recovery and apply the zip-file

6) now your phone should be more responsive again