yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] mialwe:
No. Midnight does not and will not use separate scripts. Those are old files from other kernels or (maybe other users) self-installed.
[Galaxy S I9000 Android Development] rom08:
Thanks files deleted. But it annoys me because before flashing a kernel i always applie the ultimate kernel cleaning script and some old kernel files are still here. There isn't any way to really clean the phone for a new flash!! Really piss me off.

2 feedback from previous version 0.4.1 :

- first i wasn't able to convert to ext4 correctly via cwm. The conversion was done but due to problems restoring system and data my phone was wipe. Not a big deal i had a backup but really unexpected behavior.

- to let you know i had black screen with oc so now i stick with default values. I think it is not related to your kernel but to my phone as i never succed to oc without bsod or reboot even by triyng all the kernels around

Last point your color adjustement seems god for me but would you consider one day adding voodoo color because once you are accustomed to it it is really difficult to use something else (but no hurry it is just a feature request not a vital one) .

Thanks
[Galaxy S I9000 Android Development] Rawpunzel:
Flashed 0.4.3.....First thing...i like the color. Second.....like ya. Kernel at all
[Galaxy S I9000 Android Development] mialwe:
Thanks guys. Just tested EXT4 conversion, worked without a Problem. Tested converting all partitions - without Backup :-) - typing this from EXT4.
[Galaxy S I9000 Android Development] Rawpunzel:
Oke i find something strange. If i start the goaforumapp there. Was a errormessage 84 Java io inputstreamreader. Never seen before.
[Galaxy S I9000 Android Development] mialwe:
Are you sure this is kernel related? I don't think I changed something concerning Java...
[Galaxy S I9000 Android Development] Rawpunzel:
After tested a bit i have to say i think it isnt Kernel related. It occurs After flashing 4.3 but error stays After flashing back to 4.1.....tomorrow i will Check it it was app related.
[Galaxy S I9000 Android Development] rom08:
Ok i rechecked the ext4 conversion and it worked fine. I had just not enough space in my internal sd card.

Don't you change the screen sensitivity i find it better in 0.4.3 than with 0.4.1. Maybe placebo effect. Anyway 0.4.3 is working great really smooth it really reminds me now of hardcore k13 series big thanks
[Galaxy S I9000 Android Development] DerTeufel1980:
is there a way, to really disable the 1000 mhz step and using 1200 mhz instead?

by disabeling it via voltage control, the value is set to 0 in states_enable_table, but the cpu is still using 1000 mhz.
[Galaxy S I9000 Android Development] mialwe:
I'll check if setCPU disables 1Ghz, maybe this has to do with the OC-code bug existz mentioned two days ago?

@rom08: Yep, have thrown in those:

# touchscreen tweaks
echo "08000" > /sys/class/touch/switch/set_touchscreen
echo "13008" > /sys/class/touch/switch/set_touchscreen
[Galaxy S I9000 Android Development] DerTeufel1980:
using setcpu also doesn't work. the values for the cpu levels are set to: 1 0 1 1 1 1, but this does not prevent the cpu from using 1000 mhz.

One other thing by using setcpu is, that all the files inside /sys/devices/system/cpu/cpu0/cpufreq/ondemand are empty. are these values set in a different way?

edit: are you using 95% as standard value for up_threshold? if I want to make the cpu change earlier, do I simply need to change this value to i.e. 80 or 65? Or are there other things I have to change too?
[Galaxy S I9000 Android Development] mialwe:
Are you sure disabling the frequency (at least with setCPU, don't use VoltageControl right now but took a quick look a minute ago) should disable this frequency? I think that unchecking simply deactivates the UV-settings for this frequency. Setting max. frequency to 1000Mhz at first app screen disables 1.2Ghz for me (does not help you with disabling 1Ghz I must admit).
[Galaxy S I9000 Android Development] DerTeufel1980:
isen't states_enable_table the place where I can see the levels, which the cpu is said to use? did you read my edit? and what about the empty files?

btw: was't existz talking about an undervoltig bug instead of an overclocking one?
[Galaxy S I9000 Android Development] mialwe:
If I remember right setCPU uses an own implementation and does not use tose tables - not sure right now.

Midnight uses (*conservative governor*):

#define DEF_FREQUENCY_UP_THRESHOLD	(80)

#define DEF_FREQUENCY_DOWN_THRESHOLD	(65)

and step: 10

/sys/devices/system/cpu/cpu0/cpufreq/ondemand files are empty if you use conservative governor (which Midnight does per default). Midnight does not change or set settings in cpufreq/ondemand.

If I remember right setCPU uses it's own implementation and does not use tose tables - not sure right now.

/states_enabled_table values are changed as you say but the frequency 1Ghz is used despite of it set to "0" - have to take a look at this if there's enough time (maybe tonight) - don't know if /states_enabled_table is used at all or if it's settings are overridden somehow. Thanks for reporting this.

Edit: Did this work for you with other kernels?

Edit: According to VoltageControl market page: "- enabling/disabling of particular frequencies (on supported kernels!) " so it seems Midnight does not support this (or it's overridden by setCPU). As I said, I'll look for a solution. SOrry this does not work.
[Galaxy S I9000 Android Development] DerTeufel1980:
depending on my selection in voltage control, there is a folder createted named like the govenor. By selecting conservative, there are files inside the conservative folder, which are named up_threshold or down_threshold for example, which are containing the values, you are mentioning above. If I select ondemand, the up_threshold value inside this file is 95. So, does changing this value affect to your kernel?

I´ve just tested with semaphore, which also does not work with this feature, but I´m sure, a previous version of galaxian (< 2.7) did support this.
[Galaxy S I9000 Android Development] mialwe:
Ok, thank you very much for testing.

Maybe Lukiqq has another implementation of uv/oc than myself (using the uv/oc patch provided in existz github) and stratosk. Edit: I'm currently thinking about removing the 1.2Ghz step and leaving the UV capabilities for the lower frequencies...not sure yet...

About the governors: The CPU governors change the frequency scaling behaviour to the users likings, short info can be found e.g. here - so no, ondemand does not change what the kernel does but how the CPU frequencies are scaled up and down.
[Galaxy S I9000 Android Development] DerTeufel1980:
please don't remove 1.2 Ghz. My phone is running very well with this @1300 mV.

I know what the govenor does, but I was't sure, if your kernel is looking for these settings in a different place.
[Galaxy S I9000 Android Development] mialwe:
Bugfix release: 0.4.4 [DOWNLOAD]

- set conservative governor as default (again) instead of ondemand

- removed powersave/performance governor (less overhead)

If you don't want to flash again you can use a tool like setCPU or VoltageControl to set the governor to "conservative".

Sorry guys, used an older defconfig with 0.4.3 so ondemand was set as default governor...fixed now. No spare time at the moment = no new features for now...
[Galaxy S I9000 Android Development] GoThere123:
Hi Mialwe,

Please don't remove 1,2 Ghz step as my device is running smoothly.

Will flash the newest version and report the result.

Thanks for your great work :)
[Galaxy S I9000 Android Development] HM.Carbide:
Funny thing, i tested a lot tweaking ondemand and conservative governor. And i am near on your values :)

Ondemand:

For a fast and quite good battery efficiency up_threshold 85 is very good.

With >=87 there are already noticable lags in 3d games.

With <=80 it uses very often 1000mhz, which is not good for battery life.

Conservative:

The extreme battery config:

up_threshold 90

down_threshold 75

freq_step 10

this is the boundary to get a allround good usable phone (but not for performance freaks) with excellent battery live.

Best allround setting for all day use is in my opinion ondemand with up_threshold 85.
[Galaxy S I9000 Android Development] Gammelgustav:
Hey mialwe,

great Kernel!

I hope this will turn into something big ;)

And: echt gute arbeit mialwe!
[Galaxy S I9000 Android Development] mialwe:
Many thanks to both of you.

I'll take a look at ondemand governor after Midnight is ready to be called "mostly stable" which hopefully is within the next weeks :)

Today I'll upload 0.4.5 with some new, small CWM options and without the touchscreen tweaks which led to screen stuttering for some users.
[Galaxy S I9000 Android Development] mialwe:
Thinking about internal voltages for 1200Mhz right now, found this (Tegrak page) - maybe rising the internal voltage for 1.2Ghz would result in more stability for this frequency? "Default" values are 1300mV and 1100mV (internal), I've seen Glitch uses 1125 vor internal voltage on "high leakage" profile... just thinking...
[Galaxy S I9000 Android Development] rom08:
Just to say to you that nor the uv or oc values works for me and i was using tegrak ultimate. I always encountered bsod or freeze when the cpu was too stressed with the values for 1200 mhz
[Galaxy S I9000 Android Development] mialwe:
Jep, and the reason might be that tekrak uses slightly higher voltages.
[Galaxy S I9000 Android Development] rom08:
I think so! At 1300 mv for 1.2 ghz my phone seems stable .
[Galaxy S I9000 Android Development] mialwe:
Can you help me with this? Which file did you check and which part of the code makes you sure that there is the same bug?
[Galaxy S I9000 Android Development] rom08:
No you don't have this bug. I deleted the file generated by talon and then reboot , a new one has been generated and now the voltage table is ok. The file is in /sys /devices /system /cpu /cpu0 /cpufreq and is name frequencies voltage table.
[Galaxy S I9000 Android Development] mialwe:
Ok, sorry. I thought you did look into the sources :)

Testing 0.4.5 right now...
[Galaxy S I9000 Android Development] rom08:
Far beyond my capacities sorry!
[Galaxy S I9000 Android Development] mialwe:
Update: 0.4.5 :

- disabled touchscreen tweaks (stuttering issues for some users)

- reimplemented missing WARM/COLD mode setting in CWM (advanced options/optional features)

- implemented clean init.d via CWM

- implemented remove all custom bootanimations via CWM

- implemented remove boot/shutdown sounds (for space to root) via CWM

[DOWNLOAD]
[Galaxy S I9000 Android Development] rom08:
Thanks very useful features via cwm and kernel already installed. Just a feature suggestion for you : maybe you should implement an automatic cleaning feature during the installation of the kernel to avoid problems caused by other flash ( something like a script wiping cache and davlikfor example) . Thanks again for all your efforts.
[Galaxy S I9000 Android Development] mialwe:
Yes, i know... I somehow just don't feel good messing with other users files... thats the reason I implemented this in CWM so users can delete themselves if they want to.
[Galaxy S I9000 Android Development] GoThere123:
I think changing the voltage for 1200 is not a good idea.

My device is very stable using 1300 mv for 1200Mhz, i have use this setting for long time even before using midnight and it seems the most stable setting for 1200 Mhz :)

Using midnight 0.4.4 still no issues so far.
[Galaxy S I9000 Android Development] mialwe:
For now I think Midnights further developement will slow down a bit and concentrate on

- bugfixing and

- stabilizing.

All features I was interested in are implemented, maybe I will

- test a few (little) ideas for CWM,

- look into optimizing ondemand cpu governor

- maybe look for more debug stuff not needed

- maybe work with the colors again

- maybe look for useful upstream bugfixes

- read more about the internal cpu voltage :)

Greetings to all

mialwe
[Galaxy S I9000 Android Development] andip71:
Take your time. Your kernel is just great already now.

Andi

(sent via tapatalk)
[Galaxy S I9000 Android Development] blademetal:
it is a great kernel... i use release 0.4.1 with dark rom 10.2 @1200 - 1300mv... and work excellent ... this release is more performant... i try more kernel (and midnight release).. but this have more high score in test
[Galaxy S I9000 Android Development] HM.Carbide:
On my phone with stock 2.3.3 (BOJV8) voodoo sound still does not work.

Voodoo Control shows the right version, but changing any option has no effect.

The sound is like on stock.

Are you able to reproduce that?
[Galaxy S I9000 Android Development] nikec:
Same here... Voodoo sound seems not to work - even if I set the limit to +5 db it goes only to +2db... The sound is different with Speedmod+Voodoo Plus...
[Galaxy S I9000 Android Development] mialwe:
Ok, quickly tried the following with an old (have no other) headset:

- "headphone amplifier", works. max setting 5db according to

- "volume limit" (max 5db, hardware limit)

- "bass boost", worked, most noticable with "small speaker" preset or sliding gain up and down.

- "mono downmix", worked.

Without headset:

"Tune speaker for music" - works, very noticable.

Do you both run 2.3.3 Gingerread?
[Galaxy S I9000 Android Development] HM.Carbide:
Yes running stock tmobile 2.3.3 bojv8

but i thought there is only 1 source of voodoo for gingerbread.

Semaphore for eg works on both.
[Galaxy S I9000 Android Development] mialwe:
Yes, Gingerbread version should not matter, just trying to find a reason why this is not working for you two. If you are using VoodooPlus - is there an option to load the Voodoo module? Did you uncheck it (if there is any)?
[Galaxy S I9000 Android Development] HM.Carbide:
I am not running voodoo plus.

Strange thing.

It seams that somehow the voodoo driver does not get a command from control.

How are they communicating?
[Galaxy S I9000 Android Development] mialwe:
Made a test with Semaphores' Voodoo module built into Midnight - first I had the same "headphone amplifier max db" symptom you described - could not get it higher than +2db, max db was set to +5 (hardware maximum). Now it seems to work, maybe this helps you, too:

- deleted VoodoControl (Free) data from applications menu

- restarted Voodoo Control (= default settings)

- set volume limit max db to max +5db (for testing)

- check if bass boost *gain* has set any value, disable bass boost for testing

- recheck headphone amplifier again - with bas boost gain set to 0 or boost off I was able to set the amplifier to full +5db again. Seems the bass boost gain + "normal" gain must be <= max gain.

Effects, eg. bass boost, downmix,... work with *headphone plugged* in.

Optimizing for phone speaker - works if headset is *unplugged*.

So everything seems to work just as with the "original" Midnight module (except I have activated the FM options in this build :) )...!?
[Galaxy S I9000 Android Development] HM.Carbide:
Didn't recognise this until now.

there is only the option for tune speaker. Doesn't matter if headphones are plugged in or not.

Clearing data did't help.

The problem is, that the headphones aren't detected.

Tried this with original samsung headphones and really good ones.

Do you have an other phone model?

I have a GT I9000.
[Galaxy S I9000 Android Development] HM.Carbide:
Additional info:

The whole part with FM Radio is missing.

So, no Disable voice filter, no Don't filter highs.

Thats probably the problem.

On Semaphore and Talon, it is shown, but there Tune Speaker is not shown.
[Galaxy S I9000 Android Development] mialwe:
The fm options were not enabled, they will be there in next release (see my last post).

But you should see far more options than only speaker tuning wit 0.4.5.

0.4.6+ will be uploaded within the next hours/2days.
[Galaxy S I9000 Android Development] HM.Carbide:
Sorry, i didn't see the fm info. :)

Thats exactly the problem, as i only hear music over fm radio, and this isn't working.

Thanks alot, waiting for the version 4.6.
[Galaxy S I9000 Android Development] mialwe:
0.5.1 / 2011-08-24

- toolchain 2010q1

- VoodooSound FM enabled

- tiny bugfix, disabled more debug stuff

- CWM option: toggle sdcard read_ahead 2048kB tweak

- disabled more debug stuff

- CONFIG_HZ 250hz

- lowmemorykiller values to 48/52Mb for slots 5/6

- moved HOME_APP to slot 0

[DOWNLOAD]
[Galaxy S I9000 Android Development] Rootax:
Have you try to kill voodoo app and started it again?
[Galaxy S I9000 Android Development] rom08:
Thanks for the update. The only curious thing is that your kernel is really great and doesn't have the attention and recognition it diserve.
[Galaxy S I9000 Android Development] rom08:
Oh and i have request. Could you make also an odin version of your kernel along with the cwm? It will prevent us from installing another kernel before yours when we make a clean install.
[Galaxy S I9000 Android Development] mialwe:
As I'm not using Odin (never have :) , using Heimdall with Linux -> direct flashing of zImage file...) - how has an Odin tar to be built up? Just tar the zImage?

Initially I thought that I won't provide multiple file types so I decided to upload only CWM packages - they can be flashed via the Midnight-CWM (no need for another kernel) or SGS kernel flasher (sgs-kernel flasher extracts the zImage from the CWM zip i think), users with Heimdall can extract the zImage and use it directly - so only Odin is missing...
[Galaxy S I9000 Android Development] stratosk:
Yes, just tar the zImage and will work with Odin.
[Galaxy S I9000 Android Development] mialwe:
Thanks stratosk.

Switching from CWM-ZIP to TAR will eliminate CWM-flashing and enable Odin use - I think this idea is not too bad as we can use sgs-kernel-flasher to flash directly on device... so next release will be tar :), maybe I'll upload 0.5.1 as tar archive, too.
[Galaxy S I9000 Android Development] rom08:
No you misunderstound me. I wich to have both. If i install a new rom i need odin version to flash your kernel and have root without going to another kernel. But with cwm version i can use it directly via cwm and so use ultimate kernel flasher first and do some wipe manually ( cache and davlik mostly) . The problem with sgs kernel flasher (wich by th way is a really good app) is that you can't wipe davlik and cache before flashing the kernel. Maybe I'm missing something with this app! Also if something goes wrong and your phone go to bootloop with cwm versions you still can flash via recovery you're not needing the phone to boot.

It is just my opinion but i find that having the 2 version is very convenient depending the situation you are.

Anyway it is your kernel and whatever is your decision i will stick with it as it is the most stable kernel now for me.
[Galaxy S I9000 Android Development] GoThere123:
Once again have flashed the latest version 0.5.1.

Must say this is a very great kernel.

It balance between performance and battery usage !!!

Never have any issues, thank you very much.

One curiousity, is it possible to make this kernel combined with supercharger script?

Just for memory management tweak, i tried to use supercharger script but can't run in this kernel.

If it is possible, kindly explore it :)

If not, this kernel is already more than enough :)

Keep up the great work !!! :)
[Galaxy S I9000 Android Development] mialwe:
Update: Added tar archive @ forst post.

@Gothere123: What was the problem with Supercharger? Maybe I can do something about it... thought it should work.
[Galaxy S I9000 Android Development] PoldyA4:
Supercharger work by my perfekt.
[Galaxy S I9000 Android Development] HM.Carbide:
Just tested the new version.

After toggling 2 times the enable high and low for fm radio is working.

The headphone amplifier, and the bass boost still don't work.

I have no clue, what it could be.
[Galaxy S I9000 Android Development] mialwe:
Sorry to hear that 0.5.1 did not help with your sgs (headphone plugged in for bass boost and amp? max. gain=headphone gain+bass boost gain?, how did you test bass boost?). Strange that FM works for you but other options do not...

Did you ever try with the VoodooPro App? Until now you are the only user reporting this issue so maybe it is *not* kernel related? Anyone else notices similar issues with Midnight?
[Galaxy S I9000 Android Development] rickylcp:
what apps do u recommend for OC/UV?

I tried Control Freak and Voltage Control. Both works but cannot save the settings when rebooted.
[Galaxy S I9000 Android Development] rom08:
I had this pfoblem try to root your phone from cwm even if you have done it before
[Galaxy S I9000 Android Development] rickylcp:
thanks. I will try.
[Galaxy S I9000 Android Development] mialwe:
I cannot recommend a special app but setCPU never caused any problem with my SGS/Midnight 0.0.1-0.5.1...
[Galaxy S I9000 Android Development] rom08:
I had this also before. It was not kernel related. I think it was a busybox one because after i try applying root from cwm it solve the problem. Maybe it can be related also from a bad ext4 conversion. If you are on ext4 try to go back to rfs and reconvert again in ext4
[Galaxy S I9000 Android Development] betoNL:
On Froyo I was an enthousistic Speedmod user myself....

SPECIALLY on Speedmod BIGMEM versions...

What about it? There is a bounty for it , some users are offering 50, 100, euros for a good working bigmem gingerbread kernel

Not counting all the potencial donations:

http://xdaforums.com/showthread.php?t=1233215

Just a thought.....

«»
[Galaxy S I9000 Android Development] mialwe:
Right now I don't have the time to do all the tests required for BIGMEM and changed RAM values - maybe in a few months... but generally Midnight is a kernel optimized for "average daily use" - it will never be optimized to reach top of benchmarks/free RAM...

Donations won't work I think, for Midnight I have not received a single donation until now - but this does not matter as I'm doing this because I like working on the kernel, learning, communicating with users, searching vor bugs/fixes and use the kernel myself - not for making money. Good luck :)
[HTC Sensation] Lennydk87:
Hey all.

I just rootet my Sensation last night, got S-Off, root etc.

Running Revolution HD rom right now, and I've used Leedroid too, but I got a problem, when I take screenshots of my sensation the picture looks like this: https://lh4.googleusercontent.com/-...I/AAAAAAAAAFs/Aai4fJlrAP4/s512/screenshot.jpg

I´ve tried with these two apps: https://market.android.com/details?id=com.geeksoft.screenshot&feature=search_result

https://market.android.com/details?id=com.bw.picme.local&feature=search_result

Anyone know what the problem is?
[HTC Sensation] glhturbo:
The problem is that those 2 apps that you tried don't support the qHD display that we have. They are for WVGA and lower resolution.

What you need is drocap2 which supports qHD.

https://market.android.com/details?id=com.gmail.nagamatu.drocap2&feature=search_result
[HTC Sensation] Darnell_Chat_TN:
Yea it looks like drocap2 works better. But with it there seems to be lines in the capture at times. I took a snap of my home screen which came out great, but when I took a shot of my lock screen which uses the Weather widget the capture had some black lines across it.

The screen shots are attached.

I'm using Perma-Temp Root for root access.
[HTC Sensation] glhturbo:
I just took a screenshot of my lock screen with drocap2 and it worked fine. Perhaps it is because you are using Perma-Temp Root instead of the full S-OFF and Root. :confused:
[HTC Sensation] Darnell_Chat_TN:
Just wondering, did you use the "shake" trigger or the timer? I used the shake trigger.
[HTC Sensation] Scoop24:
I just did it pressing my power+home button no app need

View attachment 675035
[HTC Sensation] glhturbo:
Shake trigger.
[HTC Sensation] Darnell_Chat_TN:
Huh? What? You mean if we press power+home a screen capture is made? Where does the output graphic go?

Maybe I'm not doing it right, I can't make it happen when I try pressing power+home, but maybe I don't know where to look for the graphic :) ...
[HTC Sensation] C0NAN:
Same question.