yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mcord11758:
Either I missed the known issue part about miui or it was added after I flashed.

Is there any fix?

Can I delete what you have added regarding camera and reboot?
[Captivate Android Development] zacharias.maladroit:
downgrading to Quorra r5

should help

I tested it and it worked for me

(of course the picture quality of the previews is just as bad as before and you still can't take pictures with the Front-facing camera - besides that it should be fine; Gtalk works afaik)

once MIUI includes the changes you'll be able to use Quorra r6 take pictures with back- & front-camera; Gtalk currently doesn't work due to missing support from the library [needs some hacking]
[Captivate Android Development] mcord11758:
Worked thank you
[Captivate Android Development] ls377:
Is anyone else not having their OC settings last through a reboot? UV is fine, but Oc always goes back to 1000.
[Captivate Android Development] zacharias.maladroit:
values don't seem to get saved but in fact they are, I just e.g. set to 1200

and rebooted

then opened up CPU Spy and it displayed 1200 being used

don't know what is lately causing trouble with VoltageControl:

- needs to be launched several times to display the states to select

- doesn't seem to be able to read the voltages (they're oftentimes at 0 - so no over- or undervolting when in fact it seems to be the case due to the init script)
[Captivate Android Development] ls377:
Weird, I tried that with System Panel and it would only show 1000.
[Captivate Android Development] lazymegaman:
I'm having problems with what I THINK is the scaling. Every so often the CPU will lock on a certain frequency. Usually it's 400MHz or 600MHz, but sometimes it'll go as low as 100MHz and just STAY THERE. Regardless of CPU load it refuses to scale back up once it's "stuck". I'm now having to force it to change the minimum clock frequency with SetCPU to 1000MHz or higher whenever the screen is on because if I don't my phone becomes so slow it's close to unusable (which as a delivery driver is essential since it's important that I don't have to look at my phone longer than it takes to place a call while driving). Is this somehow related to the recent changes in the CPU governor? It seemed to be fine back on quorra_r2 I believe. I'm currently running the non-MIUI-compatible quorra_r5_INTERACTIVE.

P.S. It also happens without ever using SetCPU during and after a reboot, so I don't think it's related to the problem. I've only had it active as both a means to force my phone into usability by forcing a higher clock speed AND as a quick method of seeing a readout of the CPU_time_in_state in the "Info" tab. It's indeed locking at a frequency at random times and just sticking to it. The time values for the other clock speeds don't change once it's "stuck". And yes, I have it set to clock the CPU back down when the display is off AND when the battery temperature goes above a certain point, just to be safe.
[Captivate Android Development] zacharias.maladroit:
lazymegaman,

thanks for your report

the interactive governor is known to favor higher frequencies more than lower ones and to stay at higher frequencies for longer times

it's weird that it will go down that much

like you wrote: it's happening while the screen is on - right ?

hm, you tried the kernel with the ondemand governor set while the screen is on ?

(it's basically changing AWAKE_GOVERNOR="interactive" to AWAKE_GOVERNOR="ondemand"

in system/etc/init.d/90screenstate_scaling)

then re-installing the kernel with the modified init-script

there's also pre-set kernel with ondemand - so no need in manually editing the script:

just download & install:

CM7_CAPPY_platypus-kernel_20110505_r0_quorra-r5_toolchain.zip

make sure the kernel matches the current CM7 nightly you're on:

to make the governor react faster - you could try to add following additional change:

# =========

# Ondemand settings [more aggressive power savings]

# =========

# echo "98" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold

echo "300000" > /sys/devices/system/cpu/cpu0/cpufreq/conservative/sampling_rate

that raises the sampling_rate from 35.000 to 300.000

hope that helps
[Captivate Android Development] lazymegaman:
Ah, how embarrassing. I forgot I DID update to the most recent CM7. So obviously none of this applies since the most recent build of your kernel isn't meant for the 05/06/2011 CM7 build. Sorry for wasting your time!
[Captivate Android Development] mcord11758:
Is this kernel dead for the captivate? We no longer appear to be getting the same updates as the sgs
[Captivate Android Development] zacharias.maladroit:
it's not

I'm currently waiting for feedback from the SGS users if the current changes are stable enough

I've already built the kernels now I only need to upload them :)
[Captivate Android Development] mcord11758:
Good to know

Thanks for the response
[Captivate Android Development] Krooked22:
bricking while installing on cm7

I do a fresh installl of cm7 and try to put this on through cwm and t gives me a brick everytime.

What am i doing wrong? Did I misread or miss something?

Thanks for your help
[Captivate Android Development] ls377:
The last version might not be compatible with the latest CM nightly.
[Captivate Android Development] zacharias.maladroit:
indeed

with newer kernel versions I'll include info with which nightly those kernels *match*

so that people don't install the kernels on much newer or much older nightlies

basically this means: if a kernel-version is running very well for you - make sure you keep a backup of the nightly zip-file

to install if anything goes awry
[Captivate Android Development] zacharias.maladroit:
Changelog:

(05/11/2011) Changes for quorra r7 mem-WIP (needs new drivers; Android 2.3.4)]

RAM, stability, functionality & smoothness test release

[316 -> now 330 MB RAM, more later if all works]

[matches with 05062011 and 05092011 update from CM7])

• added tweaked SavagedZen governor [option]

• added tweaked smartass governor [option]

• fixed regression with scheduler - phone is smoother now again

• raised sampling rate of the ondemand governor with the above change - smoother phone

• added 2 [testing] fixes to improve battery runtime

• [safety] added an overvolting cap with 50 mV - thanks to Xan & TheEscapist ! :)

• [upstream] added fix to properly suspend the serial port - thanks to atinm !

• fixed short-term & long-term lags with ondemand governor

• no change with interactive

• conservative + conservative; ondemand + conservative governor

• sampling_rate of ondemand governor at default (35.000)

• [regression] fixed frame drops & jumps (inconsistencies) for graphics-intensive apps (e.g. quadrant & games)

• [regression] fixed stuttering during shooting / SFX with doodle dash

• MOAR MEMORY - now 330 MB available [need feedback]

1) quorra r7 mem-WIP compatible with MIUI (Android 2.3.4; RC8)]

RAM, stability, functionality & smoothness test release

[316 -> now 330 MB RAM, more later if all works]

1st mirror:

link to CAPPY directory

includes:

- conservative [probably most battery efficient]

- interactive [most smoothest operation - perhaps some hickups from time to time; phone gets quite warm with it; prefers higher over lower frequencies]

- ondemand [ondemand governor - compromise between speed & battery efficiency - in a perfect world the best ]

- smartass [further evolution of interactive governor keeps the frequency at 600 MHz while idle (screen on) to ensure smoothest operation (need feedback, stability, etc.)]

2nd mirror:

3rd mirror:

sticking points that need testing:

- Camera, HD video recording, Google Googles

- HD video playback

- everything VIDEO related

- multimedia stuff

- overall stability when using all the mem

minor:

- has smoothness in operation improved ?

- stability ?

after this release I need to take a sort of "break" for the next 2 months for personal affairs & study

since the main part of kernel development is already done (feature-wise)

I'll try to release kernels as close as nightlys appear but it might be delayed

thanks for your understanding

now: enjoy & have fun with the new kernels ! :)
[Captivate Android Development] zacharias.maladroit:
feel free to mirror these kernels & post the mirror links here

I'm currently unfortunately too tired to upload them to several other sources

thanks !
[Captivate Android Development] ls377:
Mirrored:

http://www.megaupload.com/?d=0BE67H3D

Everything seems to be working fine so far. I'll continue testing.
[Captivate Android Development] mcord11758:
Can't get miui to boot post miui boot screen with latest
[Captivate Android Development] dayloooo:
Which latest did you get ?

the 4/26 Platypus kernel is 2.3.3 Android . You need a 2.3.4 Android based kernel to run the latest MIUI .

If you got the latest quorra R7 , then battery pull and restart . Mine is working fine with the latest MIUI and quorra R7 kernel .
[Captivate Android Development] mcord11758:
did that but will try again.
[Captivate Android Development] cropythy:
I love your work with this kernel, I have it undervolted at 1ghz at settings of

-100

-100

-100

-125

-150

-150 and it is rock solid stable giving me great battery on miui, well great compared to old miui anyway.
[Captivate Android Development] zacharias.maladroit:
@bootloop / boot post victims ^^

Hi guys,

could you please try to replace the existing kernel on your MIUI or CM7 nightly CWM-Package with my kernel, modules and its scripts ?

then install that updated package (with the new kernel, modules and scripts)

after that all should work

the bootloops seem to be an issue with bml_over_mtd (broken sectors on the SSD on your phone)

I'll investigate this and see if anything needs to be rewritten and/or updated in that regard

Thanks !
[Captivate Android Development] gabby131:
looks tempting....will try this one....and super updated....
[Captivate Android Development] zacharias.maladroit:
it might be a permissions problem after all - don't know why - it worked in the past and the permissions should be correct after all - anyway:
[Captivate Android Development] zacharias.maladroit:
since the current nightly seems to be an important update in terms of stability (the previous modemctl)

I decided to upload it just in time:

(05/11/2011) Changes for CM7_SGS_platypus-kernel_20110511_r0_quorra-r8 (needs new drivers; Android 2.3.4)]

[matches with 05062011 and 05092011 and 05112011 update from CM7])

Changelog:

• [upstream] TV-out support (does this even work with CM7 ? :p)

• [upstream] ifdef cleanups in mach-aries.c

• [upstream] reverted back to previous samsung_modemctl - this should solve delays with 3G, 2G and/or data acquisition

• fixed network security enhancements (several settings didn't get applied) - now your phone should be even safer; enabled syncookies [no performance hit with transfer rate]

• dropped intersectRaven's bcm4329 / WIFI drivers [older version than the previous used] - ALL WIFI channels should work now again [need feedback]

1) quorra r8 compatible with MIUI (Android 2.3.4; RC8)]

WIFI, stability & security (test) release

[316 -> now 330 MB RAM]

1st mirror:

link to CAPPY directory (thanks to Roland !)

includes:

- conservative [probably most battery efficient]

- interactive [most smoothest operation - perhaps some hickups from time to time; phone gets quite warm with it; prefers higher over lower frequencies]

- ondemand [ondemand governor - compromise between speed & battery efficiency - in a perfect world the best ]

- smartass [further evolution of interactive governor keeps the frequency at 600 MHz while idle (screen on) to ensure smoothest operation (need feedback, stability, etc.)]

md5sum:

a883b9c01a1edf2a1be9edd0489c4e14 CM7_CAPPY_platypus-kernel_20110511_r0_quorra-r8_conservative.zip

md5sum:

2127cc6548d04c2d93a7f2ca685d8a83 CM7_CAPPY_platypus-kernel_20110511_r0_quorra-r8_ondemand.zip

md5sum:

4af955e6e14fe577586796b082b9ec22 CM7_CAPPY_platypus-kernel_20110511_r0_quorra-r8_interactive.zip

md5sum:

ced3f66acae78589955fee0154b0f81b CM7_CAPPY_platypus-kernel_20110511_r0_quorra-r8_smartass.zip

feel free to mirror these kernels & post the mirror links here

thanks !
[Captivate Android Development] bfara83:
Quick question? Why isn't the releases on the main page anymore? Just a suggestion that may make these releases downloaded more. Other than that, everything is working great.
[Captivate Android Development] zacharias.maladroit:
oh - didn't notice that O.o

@ls377:

could you please add the latest kernels & update the thread title ?

thanks :)
[Captivate Android Development] ls377:
Oh yeah...forgot I had to do that :p Will do.
[Captivate Android Development] gabby131:
Seems like using this one is making me lock/unlock screen first before auto-rotate be enabled.

EDIT: *facepalm* lesson for today....read the op in full.....not browse >_<
[Captivate Android Development] gabby131:
Oh....one more question..

The download link in the op (that looks like a repository) is the one being updated right? I mean i can look at the link first for updates?

Thanks.
[Captivate Android Development] zacharias.maladroit:
ls377 maintains & updates this thread

if he finds time - I'm sure it'll get updated for the next releases :)
[Captivate Android Development] zacharias.maladroit:
troubleshooting:

- bootloops

- FCs

- phone acting erratically

---> you're one of those whose phone and/or system can't handle the faster scheduler timings

open the kernel update package (zip-file) and in system/etc/init.d/89system_tweak search for:

the line

"# TWEAKS: improve handling & reactivity of the CFS cpu scheduler (from 90screenstate_scaling)"

below:

# CFS

replace the following 3 lines with the following

then try to re-install the kernel

hopefully it should work now

since these are the more stable CFS (cpu)-scheduler values you won't experience such a smooth UI

that means - you want a similar experience ?

you need to compensate that with a different

governor

(if not already using interactive)

or

overclocking
[Captivate Android Development] gabby131:
i like the feature of ondemand gov kernel. at screen off governor changes to conservative, i dont have to use setcpu for sleep profiles :) and this is one smooth charm.
[Captivate Android Development] hernan078:
does this kernel works as your kernel, i want to try out the debugging off, in your kernel, the debugging is off?
[Captivate Android Development] TheEscapist:
Nope, planned for the next release though, as everything has gotten stable enough for me.
[Captivate Android Development] hernan078:
i know someone that know about this more than i, and he told me that the debugging consume a lot of battery, is that is true, i really would like better battery performance in my phone.
[Captivate Android Development] cumanzor:
Did that earlier and it worked. I don't know, either the file got deleted automatically or I never saved the settings to begin with.

Sent from my SGH-I897
[Captivate Android Development] CasseTrop:
how's battery life now with such a kernel ?
[Captivate Android Development] apewall:
Guide reads as if you have to install the custom cmparts.apk to enable backlight notifications (This is not the case, its enabled by default, just like bilboa's)

Also the same for voltage control, you don't have to remove it unless you are going to oc/uv

And also this kernel suffers the same as the bilboa's(By his choice) from the backlights timing out instead of constantly being on while the touch screen is in use.
[Captivate Android Development] Auridran:
My auto-rotation breaks completely when using Circle Launcher on this kernel.
[Captivate Android Development] Dxtra:
The question is does the auto-rotate consistently work? Having bad luck with every kernel
[Captivate Android Development] RKight:
I felt like this kernel was sucking my battery dry, so I decided to flash back to TheEscapist's kernel via CW recovery. I removed the S_volt_scheduler file via Voltage Control and flashed the kernel. After booting up, my phone would consistently lock up and reboot as soon as I unlocked it. I tried reflashing the kernel but it still locked up. I flashed the most recent CM7 nightly to restore the stock kernel...and my phone ran just fine. I flashed back to TheEscapist's kernel...and, once again, my phone consistently locked up and rebooted itself. When I got home from work this morning, I decided to open up the zip file for this kernel to see what, exactly, it was putting on my phone. I used ADB through CW recovery to remove the init scripts and the six module files that the kernel installed. I then reflashed TheEscapist's kernel in case any of those files were common between the two...and voila. My phone is working great again.
[Captivate Android Development] born_fisherman:
Has anyone tried this kernel with MIUI yet? Should I be the guinea pig?? :)
[Captivate Android Development] Prototype159:
Tried it, went back to kang's. For some reason it was really laggy for me.
[Captivate Android Development] ls377:
So it works without replacing the settings? That's interesting, I'll have to try that later.

Most kernels I've used have the backlight issue. If it bothers you, you can install the Keepthelightson app.

Anyone else been having lag issues with the UI? I'm using ADW EX and it's not as smooth as it was. I'm not blaming the kernel yet, because I've probably screwed up this install of CM7 (I can't get BLN to work anymore on TheEscapist's, and Trident is giving me graphics problems, and I seem to be the only one with those issues).

The odd thing is, this benchmarks fine, while Trident benchmarks horribly but with little UI lag. I'll have to do a fresh install before I form an opinion.
[Captivate Android Development] Grandelama:
I tried it, at intervals it was very smooth.. but I was having a LOT of small slow downs and lags, in particular when turning off and on the screen..and got a couple of reboots in one hour. Tried to reinstall downloading it from another website, same results. I did remove voltage config. and clean dvk cache both of the times.:(

I went back to theescapist's last kernel
[Captivate Android Development] amerikian:
Headphone button bug

When using the headphone button to pause/play music, if you press the play button with the screen off there is a pause then the music plays but very choppy. Then if you try to turn on the phone, it will not power on the display and really starts to flake out.
[Captivate Android Development] Auridran:
Yeah, after switching back to TheEscapist's kernel due to auto-rotation breaking on this one, I definitely notice that it's significantly smoother.
[Captivate Android Development] cumanzor:
Definitely. But I went back to the stock kernel because something is sucking my battery life and I'm not sure what it is. I'll probaky go back to Le Kernel anyways, but thought it would be a good idea to try this first.
[Captivate Android Development] ninjaclipse:
This is identical to what happed to me
[Captivate Android Development] grkmaster:
I will let you know after a full days use. I installed it last night but im just restoring everything all day so i havent really gotten a chance to play with it. Hiccups here and there but not still runs good. Gonna UV later on to see how it affects it
[Captivate Android Development] apewall:
Yes it does seem rather laggy. It is not constant though but in an interval. I also experienced a few reboots with the kernel. I moved back to the escapist kernel for stability, hopefully when he removes debug from the kernel the battery will exponentially increase.

BLN(and the kang BLN) never would work for me until I wiped and flashed the later CM7 initial and updated from there, I suspect their was some bug that stays over from earlier CM7 packages that keeps BLN from working.
[Captivate Android Development] arcardinal:
I am also having the auto rotate bug. It works when I first boot the phone, but will randomly stop working. It is fixed through a reboot, but will eventually stop working again. This is the only issue with this kernel. I have not experienced any lag at all.
[Captivate Android Development] gabby131:
/me *facepalm* i thought ls377 also maintains the kernel, my bad....again read the OP.....:o
[Captivate Android Development] ls377:
It will be. If not, feel free to spam my PMs til I do it ;)

Sent from my Captivate
[Captivate Android Development] Delwyn:
Zach,

Just wanted to say after a 10 hour work shift with moderate usage (texting, Facebook, Wordfeud, Words with Friends, and even 15 mins of Netflix), conservative left me with 40% battery. Great kernel! Best battery life yet.
[Captivate Android Development] gabby131:
awright! this kernel is so awesome! playing online gameloft games give's me smooth results.

thanks zach and ls377, :)
[Captivate Android Development] mcord11758:
for any that are having boot loop issues I have modified the on demanad and smartass versions with the fix Zach posted. Figured it was worth posting. If you want me to pull this please let me know
[Captivate Android Development] ls377:
I added troubleshooting/FAQ to the third post. If anyone thinks something else should be added, let me know.
[Captivate Android Development] kant5t1km3:
what is the differences between the governs? thanks for he info.
[Captivate Android Development] ls377:
Stole this from zacharias a few pages back:

- conservative [probably most battery efficient]

- interactive [most smoothest operation - perhaps some hickups from time to time; phone gets quite warm with it; prefers higher over lower frequencies]

- ondemand [ondemand governor - compromise between speed & battery efficiency [in a perfect world the best ]

- smartass [further evolution of interactive governor keeps the frequency at 600 MHz while idle (screen on) to ensure smoothest operation (need feedback, stability, etc.)]
[Captivate Android Development] kant5t1km3:
thanks ill tr to keep that in mind :D

i use smartass, works fine, might try other ones
[Captivate Android Development] mcord11758:
Looking forward to seeing the updates on the captivate
[Captivate Android Development] zacharias.maladroit:
(05/16/2011) Changes for CM7_SGS_platypus-kernel_20110516_r0_quorra-r9 (needs new drivers; Android 2.3.4)]

[matches with 05062011 and 05092011 and 05112011 and 05152011 update from CM7])

[use this kernel with latest nightly unless you have a good reason to use older ones]

Changelog:

(from quorra r8)

- kernel comes pre-packaged with smartass governor

- [EXPERIMENTAL] - make an nandroid backup before testing & using: for switching to other governor (while screen is on - screen off = conservative) apply additional "screenstate_scaling switcher" script

# see attachments#, # additional scripts# <-- *Link* inside

- added interactiveX cpufreq governor from leanKernel-tbolt/imoseyon (adds sleep & wake code) - (probably) better (less) battery usage than conventional interactive governor [need feedback]

- tweaked interactive governor to scale down to lower frequencies faster (less battery usage & still very smooth)

- fixed & tweaked SavagedZen [*very* laggy - for those battery runtime fetishists ^^] [needs more testing & feedback]

- [upstream] wifi driver now supports channel 12, 13 and 14 again (thanks to atinm !)

- [upstream] added recovery 2e checks for initial update

- [upstream] accurate battery gauge display (thanks to atinm !)

- [upstream] improvements in recovery-handling with the /cache partition (thanks codeworkx !)

- [upstream] some fixes & improvements for recovery (e.g. creating missing devicenodes)

Mirrors

:

#1: quorra-r9/CAPPY

(thanks to Roland !)

#2:

this post

scripts:

this post

Mirror for scripts:

quorra-r9/scripts

(thanks to Roland !)