yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] zacharias.maladroit:
ok, I don't own a cappy device

can someone please test out the commits on the cm7_merge_rework_new branch ?

before testing the commits:

- could you please try out the kernel WITHOUT the init scripts included ?

to make sure that the failure of the keys is NOT caused by one of the init scripts

* you either can remove it from the kernel update, delete the files from /system/etc/init.d/

(90screenstate_scaling; 89system_tweak)

* or apply an update for CWM Recovery if that still works:

script removal update

the last good (working) known commits are:

8e42591059c944f9a8bc

mach-aries.c: cleaned up this oled/lcd hell

and

3bf8d333c9121b5e6ba4

complete last commits by reverting max screen frequency to 60

<----- these also need to be tested to make sure they really work

potential candidates to break the keys are:

- 82a770bc3079a94bf3f3 (add sampling down factor to ondemand )

- 453e63a062876da1b2f1 (battery polling, higher timer frequencies )

- 51508bd31ec641122dba (switch to mfloat-abi=hard )

- a5cd5779740e6c51ce83 (net: Add Kineto GAN module )

- 7fa6bbd168ad4746f530 (cpufreq: interactive: Changes to interactive governor )

<-- if one of those breaks it please also try out the commits before and after the offending commit to exactly find out what step caused the issue

Many Thanks in advance for your help !
[Captivate Android Development] TheMathMan:
Wow. I was ever so slightly concerned when it booted up, upside down! Even to the lockscreen.

A lock/unlock seemed to have fixed it.
[Captivate Android Development] BL4zD:
I compiled kernels after manually reverting the changes from commit 453e63a062876da1b2f1 one by one and it looks like

is the culprit.

To confirm, I did git reset --hard origin/cm7_merge_rework_new

then manually reverted those changes from commit 453e63a062876da1b2f1, compiled, and working keys!

how come the kernel packages don't have the scripts in them anymore? should we still use the old ones from past packages?
[Captivate Android Development] BL4zD:
Here's the kernel with the working keys fix

(04/25/2011 release name: "Whatitsname" with arch/arm/Kconfig reverted)
[Captivate Android Development] ls377:
@zacharias-I can confirm this is working, with the init.d scripts (flashed two-face first, then this). Just let me know when you want a version added to the OP.

@BL4zD-Thanks for working this out!
[Captivate Android Development] zacharias.maladroit:
@ls377:

I think I first need to get you guys a working higher timer frequency

reverting it seems to fix it but then you won't get the whole smoothness & more stability, etc. from the new kernel

will see what I can come up with

thanks !

@BL4zD:

thanks a lot - once again for your help ! :)

wait:

so NOT EVERYONE is getting non-working keys ? :confused:
[Captivate Android Development] zacharias.maladroit:
OK,

please test the following kernel if the keys work with it:

CM7_CAPTIVATE_platypus-kernel_20110425_04_whatsitsname.zip

md5sum:

7e63329ab4fa082b517b0121dd72f15c CM7_CAPTIVATE_platypus-kernel_20110425_18_whatsitsname_r2.zip
[Captivate Android Development] ls377:
Still no touckeys.
[Captivate Android Development] BTTNext:
Many thanks for this. Keys work as expected now.
[Captivate Android Development] ls377:
Really? Weird, mine didn't. I'll have to play with it later.
[Captivate Android Development] BL4zD:
He's referring to the one I compiled and tested, which you confirmed as working yesterday. Are you saying that the version I uploaded no longer works for you or are you saying that the newest version from zacharias doesn't work for you?

EDIT: CM7_CAPTIVATE_platypus-kernel_20110425_18_whatsitsname_r2.zip does not work for me
[Captivate Android Development] zacharias.maladroit:
no - my bad - I forgot to add them this time :p

I'll build a kernel with those changes reverted then and add the updated scripts

thanks !

thanks a lot !

@ls377, BL4zD:

how's the speed with that change reverted ?

is the kernel smooth ?
[Captivate Android Development] Theodor911:
@Zach: your rc2 test, still no touchkeys.

Sorry.
[Captivate Android Development] Theodor911:
BL4 version and rc2 are the only two platypus versions to not cause an animation loop at the miui animation.
[Captivate Android Development] zacharias.maladroit:
thanks for your report Theodor911 !

yeah, something smells fishy here

I don't get it why the cappy doesn't like those semi-high timer settings :(

glad to hear that

it's getting more stable :D

I did lots of testing and also did some changes (including one revert) that potentially caused reboots reported by users

thanks !
[Captivate Android Development] BL4zD:
I think the kernel is smooth enough, but then again I used to have it set at 100 months ago so I may not be the best judge of "acceptable" in comparison to users who prioritize speed over battery life :)

When I use conservative there's slight jitter when scrolling through the app drawer. But it's buttery when using ondemand.
[Captivate Android Development] ls377:
Ahhh ok, my bad.
[Captivate Android Development] tjsooley:
did not work for me either
[Captivate Android Development] tjsooley:
Thanks Worked
[Captivate Android Development] zacharias.maladroit:
yet another one:

CM7_CAPTIVATE_platypus-kernel_20110425_21_whatsitsname_r3.zip

please try

hopefully this will work :)

(without scripts atm)
[Captivate Android Development] tjsooley:
No is does not.
[Captivate Android Development] zacharias.maladroit:
dang !

this is really starting to piss me off :p

lol

@BL4zD:

was the HEAD of your git at 7fa6bbd168ad4746f530 ?

(the new interactive givernor)

and you reverted ALL of the changes from 453e63a062876da1b2f1

right ?

sorry all of this additional testing guys,

I simply need to be able to reproduce this and get a working kernel from my part

thanks !
[Captivate Android Development] BL4zD:
yes

I actually built a kernel for every single change (not just each commit o.O) from the beginning to the end of your list of possible broken commits until I found which one broke the keys and then I reset to 7fa6bbd168ad4746f530 and reverted the problematic code.

no, only the three changes to arch/arm/Kconfig

The keys still work when I leave the other changes from 453e63a062876da1b2f1
[Captivate Android Development] zacharias.maladroit:
thanks for the clarification BL4zD !

ok,

in that case the longer battery polling intervall is still in - nice :)

with highres timer of 250 + USER_HZ at 200 it should be somewhat acceptable to use

will try this combination then & build a kernel

hopefully this works this time *crosses fingers* :p
[Captivate Android Development] Killemalll:
This revision works perfectly for me. :confused:

The release gives me significantly improved smoothness. Lag is almost absent , no matter how heavily I use the phone (OC 1.2Ghz). Thanks a lot for posting it!
[Captivate Android Development] Johnston212:
I know you are very busy dealing with the latest revision, but I wanted to mention that the situation I'm having with auto-rotation "wearing off" became worse today. A reset did not work, nor did clearing the caches. I will probably try and re-flash again to see if that works. Does anyone have any ideas as to what may be causing this?

Also, just as a backup, does anyone know if it is possible to 'force' landscape mode?
[Captivate Android Development] tjsooley:
This was the only version that worked for me.

Man thats strange.

if you need a guinea pig I am your man or phone whatever.
[Captivate Android Development] zacharias.maladroit:
it depends on the timer frequencies internally used in the kernel and the governor (probably more factors) but for simplicity's sake:

since we're forced right now to use a lower internal timer the probability is higher that the rotation might get stuck

teamhacksung is working on the sensors and hopefully in the near future this will be solved

thanks !

thanks tjsooley !

it looks somewhat that something in the git repo (a commit or more) breaks the keys for the cappy

so basically the source / kernel is in a semi-broken state

I had these kind of stupid incidences in the past, too with my phone but with auto-rotation breaking

very much at the beginning I didn't had enough git-fu yet so I had to start over from scratch

hopefully I'll be able to troubleshoot this and find out the cause

so I first have to go back with the kernel-state (e.g. at the feature-state of "core" kernel)

thanks !
[Captivate Android Development] zacharias.maladroit:
guys, please test

this is a kernel at the state of "core" but with updated scripts (whatsitsname+) and the 400 + 200 frequencies

if it already breaks here I need to compile a stock kernel with that and see if it's the same:

CM7_CAPTIVATE_platypus-kernel_20110426_18_core+freqs.zip (3.91 MB)

md5sum:

03b3e763f4afd9730ca8915cc3a64318 CM7_CAPTIVATE_platypus-kernel_20110426_18_core+freqs.zip

(edit: removed the attachment to remove storage overhead from XDA servers)
[Captivate Android Development] ls377:
Buttons are good on this one.
[Captivate Android Development] zacharias.maladroit:
thanks for testing ls377 !

ok, next one:

this one's at the state of "core" + gb source merge (from samsung) and should provide better battery runtime + 400/200 kernel timer + scripts

CM7_CAPTIVATE_platypus-kernel_20110426_18_core+gb-merge+freq.zip (3.91 MB)

md5sum:

2e56f3d6a51953fde2ef1a0199c36452 CM7_CAPTIVATE_platypus-kernel_20110426_18_core+gb-merge+freq.zip

(edit: removed the attachment to remove storage overhead from XDA servers)
[Captivate Android Development] ls377:
No buttons on this one.
[Captivate Android Development] zacharias.maladroit:
thanks again ls377 !

ok, looks like I need to build from the teamhacksung repo directly

and troubleshoot this with cmsgsteam

let's first see if it also breaks with the vanilla source + higher timings ...

CM7_CAPTIVATE_teamhacksung-kernel_20110426_19_freqs.zip (4.86 MB)

md5sum:

0d9bf91c23c0a52118e9ae0e2de47f52 CM7_CAPTIVATE_teamhacksung-kernel_20110426_19_freqs.zip

ok, this is using stock config + only change is the higher timings 400/200

please test

thanks !

(edit: removed the attachment to remove storage overhead from XDA servers)
[Captivate Android Development] ls377:
No buttons here.
[Captivate Android Development] zacharias.maladroit:
thanks for your help !

ok, this probably confirms it:

it's a BUG/regression from earlier kernels :(
[Captivate Android Development] insaneturbo13:
Just thought I'd pop in and say thank you to everyone testing this and making it run right for the rest of us. And a big thank you too the original Creator of the kernel zacharius.maladroit Excellent job!
[Captivate Android Development] zacharias.maladroit:
to what exactly are you referring to with "buttons"

the softkey buttons that are lit up, right ?

afaik the cappy has no physical "home" button compared to the SGS ...

ok - more testing:

the hottest candidates are #3 and #4:

#1: added some header files from jvb

#2: correct some regulator voltages

#3: set always_on = 0 on display regs

#4: removed dead code

please see the attachments for download of test-kernels

thanks !
[Captivate Android Development] tjsooley:
They all work.

Which one is the best one to use?
[Captivate Android Development] eccezarathustra:
1 works for me. Auto rotation, buttons are good. Running at 1200 now, going to stability test and test the rest in a few.
[Captivate Android Development] Grandelama:
Ok, I tried them all. Capacitive buttons are working correctly in all the four versions!

(they were broken on CM7_CAPTIVATE_teamhacksung-kernel_20110426_19_freqs version for me too)
[Captivate Android Development] tjsooley:
where did you download the teamhacksung kernel ?
[Captivate Android Development] zacharias.maladroit:
http://xdaforums.com/showpost.php?p=13223900&postcount=238
[Captivate Android Development] zacharias.maladroit:
it's actually a kernel built by me and the only change are the frequencies

so it's not to be mistaken with a kernel by teamhacksung
[Captivate Android Development] zacharias.maladroit:
well, let's see if we could tackle the right commit:

please welcome "alice" kernel release (stable)

minus "mach-aries.c: cleaned up this oled/lcd hell" commit

CM7_CAPTIVATE_platypus-kernel_20110426_23_alice_minus-oled-cleanup.zip (5.23 MB)

md5sum:

f8cb0e84287338da837c69e9193d7e61 CM7_CAPTIVATE_platypus-kernel_20110426_23_alice_minus-oled-cleanup.zip

please test for the following sticking points:

- working keys

- auto-rotation

- overall smoothness & lags

- stability (call drops, spontaneous reboots, etc)
[Captivate Android Development] tjsooley:
Works you rock
[Captivate Android Development] zacharias.maladroit:
thanks ! :)

I'll upload a "final" release with a better tweaked conservative governor later

I'm currently still tweaking it for more smoothness - it still lags too much for my taste ;)

edit:

enjoy Voodoo Sound v8 !

:)
[Captivate Android Development] BL4zD:
so you're using conservative over ondemand?

(and either of those before interactive?)
[Captivate Android Development] zacharias.maladroit:
a tweaked conservative (that's still my preferred one) :)

there's more choice with this release:

- ondemand

- conservative

- interactive

- smartass (aka "min/max")

- savagedzen

- performance

- powersave

it doesn't look however if savagedzen has been built already

seems like I need to update the config-file first :\
[Captivate Android Development] eccezarathustra:
Tried all four kernels, 2-4 all hard reset on me at boot. 1 was laggy even oced. Back to cm7 nightly 21 waiting for new kernel to test.
[Captivate Android Development] tjsooley:
Not to rush you But could we expect this tonight?
[Captivate Android Development] takerfan:
I think it's already up. http://www.ponack.net/zachariasm/stable/alice/CAPTIVATE/

I'm not sure if this is the final/stable release though.
[Captivate Android Development] zacharias.maladroit:
kernel stable (?)-release

Introducing "Alice" release

04/27/2011 (release name: "Alice"

already containing parts of Samsung's GB source (thanks teamhacksung !));

Semi-Testing/Stable (for new integrated code from Samsung) and other exciting new stuff )

kernel:

1st Mirror / Host

: [recommended]

"Alice" (thanks a lot to Roland !)

2nd Mirror

:

this thread (XDA) (attachment)

3rd Mirror

:

CM7_CAPTIVATE_platypus-kernel_20110427_00_alice_minus_led-lcd_cleanup.zip (5.23 MB)

md5sum:

498990f66e1a60636338e490a9bc2094 CM7_CAPTIVATE_platypus-kernel_20110427_00_alice_minus_led-lcd_cleanup.zip

Changelog:

additional optional features:

* bigger Dalvik VM heapsize (64 MB - like on Samsung's Gingerbread)

adb shell setprop dalvik.vm.heapsize 64m

to check if it's enabled:

adb shell getprop dalvik.vm.heapsize

* semi-fix for GSM/UTMS data signal outage (longer intervals):

adb shell setprop ro.ril.enable.dtm 1

to check if it's enabled:

adb shell getprop ro.ril.enable.dtm

Installation steps:

Auto-Rotation related

:

Generally no special steps should be required -

you could also leave out clearing of /cache & Dalvik Cache but this is to be sure - consequence is significantly slower 1st & 2nd (?) boots

following boots should be way faster than before (!)

Troubleshooting:

Please test specifically for the following sticking points:

enjoy ! :)

FYI:

for your convenience the kernel zip-files are also attached to this post

Thank you A LOT for your feedback on previous kernel releases

thanks !
[Captivate Android Development] zacharias.maladroit:
what's wrong with you guys ?

can't you wait until everything's finished ? :(
[Captivate Android Development] Theodor911:
Haha I do.
[Captivate Android Development] tjsooley:
Its hard to wait for the BEST CM7 kernel out there :)
[Captivate Android Development] takerfan:
Hahahaha sorry right when I posted that I refreshed and saw your post. :p

Gonna give it a shot!

Thanks a lot for all your work. :D
[Captivate Android Development] tjsooley:
The release just before I scored 2045 on quad and with this release I score 2054.

The new kernel is a lot smother.

Nice work.
[Captivate Android Development] ls377:
Newest version running great! Added to OP (someone yell at me if there's a bug so I can pull it down :p)
[Captivate Android Development] takerfan:
There seems to be a small bug. If you change the governors from conservative to something else (such as ondemand) and lock/unlock the screen, it goes back to conservative.

Also for some reason I experienced multiple skips while listening to music on poweramp (the screen is locked). Another xda member was experiencing the same thing on TheEscapist's kernel however he was on the smartass setting. I'll experiment some more and let you know. Otherwise it's running great! :)
[Captivate Android Development] tjsooley:
it also goes back to conservative in cmparts to and on reboot.
[Captivate Android Development] ls377:
I think the music skipping is a CM thing, I've had it on every kernel I've tried.
[Captivate Android Development] arcardinal:
it's not a bug. It's due to the scripts that are included with the kernel.
[Captivate Android Development] ClaPik:
Hi, I just want to ask: if i want to, lets say, OC, do i just change the setting in voltage control? is there any tutorial for doing that or I just set whatever I want...?
[Captivate Android Development] takerfan:
Oh ok. Thanks for the heads up. I've only had CM7 on for a little over a day now.
[Captivate Android Development] arcardinal:
You can change the governor by editing the 90screenstate_scaling script in the init.d folder

From

AWAKE_GOVERNOR="conservative"

To

AWAKE_GOVERNOR="ondemand"
[Captivate Android Development] BL4zD:
Likewise, the skipping is probably due to the powersave setting in that same script.

Sent from my CM7 Captivate!
[Captivate Android Development] takerfan:
Thanks guys. I see SLEEP_GOVERNOR="powersave"

I'll try changing that to conservative.

Do you think there will be a significant/noticeable impact on battery life?

Edit: Still seems to be skipping, could it be because min cpu clock is set to 100mhz?

Also I set AWAKE_GOVERNOR="ondemand" but in CPU settings it still shows conservative, even if I try to change it to ondemand.

Edit 2: Looks like all I needed to do was reboot hahaha. Ondemand is now set in CPU settings. I'll let you know how well it goes.
[Captivate Android Development] arcardinal:
I don't think there is really much of a difference in battery life between the different governors, at least I haven't seen a difference.

My battery life gets murdered no matter what settings I have due to extreme usage. I browse the internet and stream a lot of video content. Even on 2.2 Roms I never got more than 12 hours of usage.
[Captivate Android Development] BL4zD:
@Zach,

I didn't have to revert 3bf8d333c9121b5e6ba4 to get working keys.

I still get working keys after reverting 8e42591059c944f9a8bc while leaving .freq = 60.
[Captivate Android Development] takerfan:
Anyone notice that sometimes when you lock the screen the 4 keys at the bottom stay lit up and as soon as you unlock the phone it goes away. And sometimes (these 2 may be related) when you unlock the phone and open an app or so, none of the keys will work until you lock/unlock the phone again.
[Captivate Android Development] Killemalll:
With the latest release I'm randomly getting this behavior:
[Captivate Android Development] zerojay:
Same here.
[Captivate Android Development] ls377:
I've always had that problem...I can't remember if it's kernel specific.

For the keys staying lit, I've noticed that sometimes when the screen is off, when you touch them they light up. Pretty sure that isn't specific to this kernel.
[Captivate Android Development] TheEscapist:
It is, actually. It's a bug in the way kang wrote the led emulation.
[Captivate Android Development] jo7878:
i have the same problem?also i can't charge my battery to 100%.it stay at 95% every night after i charged it. can someone look into it.thank.
[Captivate Android Development] ls377:
Odd, I thought I had it on your kernel. Although I change kernels so often I probably got them mixed up :p
[Captivate Android Development] takerfan:
Getting quite a bit of lag while using GPS and listening to music. Although music doesn't skip the rest of the OS lags, stuff like opening folders in apps organizer, unlocking the screen or opening up the maps app and trying to search something.

Seems to be the same on other kernels too so I'm hoping it's a CM7 issue for our devices while the bugs get ironed out.
[Captivate Android Development] zacharias.maladroit:
I don't know if the following release might help

but I need feedback anyway (test-release):

*crosses fingers* that the keys work

Changelog:

(04/27/2011) Changes for platypus-kernel_20110427_18_quorra_r1:

- based on top of bilboa1's kernel (Voodoo Sound v8, LED notification, etc.)

- fsync performance improvements for CFQ with small files

- CONFIG_PVR_ACTIVE_POWER_LATENCY_MS set to 10

- Nick Piggin's filesystem performance improvements

- toolchain switch to Codesourcery 2010.09

(04/27/2011) Changes for platypus-kernel_20110427_18_quorra_r2:

- mainly config changes [from bilboa1's default config to release "alice" config with changes]

- config_embedded re-activated

- config_aio disabled for now

- optimized for speed than for size

- still SLUB (SLQB not added yet)

- bumped the timer to 512

- tweaked cpufreq conservative governor for responsiveness; while screen is off: now also using conservative governor (different settings from while screen is on)

- config_ksm disabled for now

- CONFIG_UACCESS_WITH_MEMCPY disabled for now

- CONFIG_BINFMT_MISC disabled for enhanced security (new)

- re-enabled FM Radio drivers (needs support in userspace / the CM7 or MIUI system to get Radio working)

- added "Automatic ZipAlign by Wes Garner" v1.1 to the scripts

md5sum:

23e91f292b858a917e7679fd0c17cad5 CM7_CAPTIVATE_platypus-kernel_20110428_01_quorra-r2.zip

md5sum:

3ff64726d486c2bb13f064d50bc0d59a CM7_CAPTIVATE_platypus-kernel_20110428_01_quorra-r2_interactive.zip

[option] new interactive governor kernel <-- need feedback for that - interactive is enabled while the screen is on only, while screen is off: conservative
[Captivate Android Development] zacharias.maladroit:
yeah, in those cases a bigger battery (e.g. Momax ExPower) would be the best bet or an additional battery if you don't like your phone to get thicker

thanks BL4zD !

with the new base I also didn't revert the led/lcd cleanup commit

I bumped the timer to 512

hopefully keys still work (did some extensive troubleshooting with atinm on this yesterday)

thanks again ! :)
[Captivate Android Development] crazililazn:
Loving the kernel, but one thing I have noticed with CM7 is that if I use the same OC/UV settings I used on Froyo, the phone is extremely unstable. Moments into playing a video in Moboplayer/Rockplayer and my phone will just crash. I thought CM7 was suppose to OC/UV better, according to this one thread that I read awhile back.

Also, the quorra-r2 is working fabulously. All sensors seem to be working and there is no visible lag :] Thanks for the hard work!
[Captivate Android Development] zacharias.maladroit:
you can't directly compare the relative overclock/undervolt values (how much you over- or undervolt)

but the absolute ones: e.g. 1200 mV at 1000 MHz

how much was it with Froyo kernels ? how low could you get with that ?

at 100 MHz e.g. it's 825 mV (-125 mV from 950 mV)

is that still less compared to Froyo ?

Quorra kernels are still in development and patches that improve stability (also included in "Alice") will soonish be included - that might allow you guys to undervolt some more

thanks !
[Captivate Android Development] crazililazn:
Yes I understand and that is what I mean. If I set the voltages (final voltage, not the amount that I undervolt) the same as my froyo settings, my phone is much more unstable.
[Captivate Android Development] takerfan:
Just flashed the interactive kernel, deleted the voltage init.d file before flashing. First impression is great but it usually takes a couple of hours of the phone being on to show any problems. BTW are you on IRC? If so what's your nick?

Edit: Just a heads up, the voltage control app doesn't work. Says incompatible kernel.