yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] yaatzek:
Thanks mialwe for the new kernel, working great for a few minutes now :D on cm9.
[Galaxy S I9000 Android Development] kabalix:
I really like the way our kernel devs respect and help each other :)

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] Andii S.:
140Mb RAM, realy, or just mistyped?

143 habe 340Mb RAM

Tapatalked with Slim_SGS@Midnight
[Galaxy S I9000 Android Development] mialwe:
Uups, sorry. Correcting asap :-/
[Galaxy S I9000 Android Development] Pac-Man:
Thanks for the answer!

Your kernel is the best one I tried ever. I've been waiting this release impatiently!

tapatalked ... !! ®
[Galaxy S I9000 Android Development] mat0122:
there are 372 available RAM with CM9 midnight kernel ;)

everything works great! even night mode works with gamma -25, great job mialwe :)
[Galaxy S I9000 Android Development] Pac-Man:
I can't install app from Play Store. It says me that I don't have enough space to install apps...

190CM9

tapatalked ... !! ®
[Galaxy S I9000 Android Development] extralife:
Not kernel related.

Use forum search.

... using tapatalk
[Galaxy S I9000 Android Development] mialwe:
Low space on /data:

- /data partition on ICS is smaller than it was on Gingerbread

- most probable you are simply running out of space @ /data. There is at least one script you could try to automatically move some parts of installed apps to sdcard (I think): http://xdaforums.com/showthread.php?t=1541942. Never tried it myself but maybe it works for you.

- Another option would be reducing installed apps to free space on /data partition

Forgot one Important information in changelog: /system/etc/init.d and /data/local/userinit.d script filenames have to start with "S" to be executed. You might have to rename script filenames to work with MNICS >= v190.

Edit: Did not forget it, it's already there...
[Galaxy S I9000 Android Development] cabessius:
that would be the smartest move if you don´t want unexpected lags.
[Galaxy S I9000 Android Development] Pac-Man:
Sorry but I have this probem since I installed the 190CM9 version so I don't need to use the forum search, I'm not witting in the wrong place.

I have enough space and I don't have these folders created...

tapatalked ... !! ®
[Galaxy S I9000 Android Development] bhu1:
hmm....does that implies to all scripts? cause aokp rom have some tweak scripts, none is with the S in front of its name.
[Galaxy S I9000 Android Development] cabessius:
Check with Root Explorer if you have enough space at /datadata
[Galaxy S I9000 Android Development] ghul21:
+1

Good question. S30datafix Only in this case has the appropriate permissions to be enforced
[Galaxy S I9000 Android Development] mialwe:
Sorry, I think you have to try another kernel then. Tested with 190CM9, installed two apps, started them, works. Don't know if and how a kernel could prevent apps from beeing downloaded/installed (besides not mounting /data).

@bhu1: Yes, for all scripts in init.d or userinit.d., from changelog:

- initramfs: executes init.d/userinit.d scripts starting with "S" only

If you don't miss something you probably don't need the scripts not named "S...." :-/
[Galaxy S I9000 Android Development] jacobuscuracao:
let's spell it out: /datadata has only 170 Mb. That space is used by e.g. gmail and if you sync a lot of mail, that fills up.

If you install e.g. Google chrome, many people have found that it filled up the space really fast.

finally, you are the only one here today with this problem, while we're all running the latest Midnight kernel without any problem whatsoever.

This should be a hint to you that it is not the kernel that causes the low on space message (aside from the technical proof that is available).
[Galaxy S I9000 Android Development] Bejda:
Hi Mialwe,so init.d is now enabled by default?But log keep saying can't find midnight_options.conf and skip init.d execution.

I came from semaphore and was already trying init.d scripts execution with "S" with this test one that worked:

http://db.tt/h2ihGt0K

He doesn't work anymore.
[Galaxy S I9000 Android Development] mialwe:
Did you enable init.d via CWM (OP quote)?
[Galaxy S I9000 Android Development] Bejda:
Pfff,not my day sorry.
[Galaxy S I9000 Android Development] mialwe:
No problem, nice to see the logfile is actually used sometimes :)
[Galaxy S I9000 Android Development] 2k4ever:
Thanks for the update, mialwe!

one question about the read_ahead tweak:

i'd like to know whats the advantage of 256Kb compared to the old 512Kb and let you know that for me, after updating from v143, it was still set to the old default of 512Kb
[Galaxy S I9000 Android Development] Rootax:
It seems that midnight app doesn't apply some settings at boot. Like cpu speed limit and colours values. When I open the app, the settings are correct, but not applied. I have to reapplied them (by changing them for exemple).

Other than that, very smooth kernel.
[Galaxy S I9000 Android Development] mialwe:
256Kb performed better during some benchmarks (scripted, no apps) for files ~4Mb. The 512Kb you had after updating to mnics190 are the value previously stored as the app settings do not get wiped.

Thanks for reporting - while experimenting with a CM9-only version I completely removed all color settings. Dropped CM9-only idea for now, readded color settings - and forgot to include the "apply-at-boot checkbox". This is fixed in my dev version. Thanks again for reporting.

For the CPU speed limit 800Mhz: Please check what /data/user.log says about setting the limit.
[Galaxy S I9000 Android Development] Bejda:
for me not sure but it seems (on a miui v4) that only cpu speed limit to 800Mhz didn't sticked.

Changes i made in app:

http://dl.dropbox.com/u/25071013/Mnics_cpu_colors_changes

App launch after reboot:

http://dl.dropbox.com/u/25071013/Mnics_cpu_colors_changes_afterboot

User log:

http://dl.dropbox.com/u/25071013/user.log

...don't know why first link is downloadable and not web visible...dropbox mysteries..
[Galaxy S I9000 Android Development] mialwe:
Colors: No, the debug lines about colors are missing as you are not able to tick the "apply-at-boot" checkbox, it's simply not in the menu. Sorry for that.

CPU limit 800Mhz - are you sure you ticked the limit-800Mhz box?:

800Mhz limit deactivated, skipping...

Which ROM are you on? I see a lot of

[[: missing ]]

errors in the user.log which usually appears if your busybox does not properly support some standard test commands ("[[" and "]]"). This is known to be an issue for e.g. ICSSGS and some version of darknight if I remember right.

Edit: Your busybox is from Aug/2011 1.19.0, maybe that's causing your error messages. CM9 currently uses v1.19.4. 17/03/2012. I uploaded a self-compiled CM9-busybox somewhere in this thread, link should be in OP/FAQ. Maybe replacing your busybox (backup first, just in case) helps here just like it did with ICSSGS.
[Galaxy S I9000 Android Development] Bejda:
Limit max. 800Mhz is still ticked in Mnics control after reboot but shows current as 1000.

I'm on a miui v4 port from nexus by Andy Thomson at miui android:

http://miuiandroid.com/community/threads/miui-v4-for-i9000.15461/

..ok,seen your edit thanks,i'll check :)
[Galaxy S I9000 Android Development] mialwe:
APP: IO sched -> sio
APP: limit800 ->
APP: cpugov -> conservative

Strange thing. According to your log there is no value stored for limit800.

Please try to tick/untick the 800Mhz option again, then reboot. As it's just a false/true check this should not be affected by your busybox/"]]" issue. I can't test myself as I'm working on readding the 7 freq oc (removed the 800limit code a few hours ago), sorry, I'll try tomorrow (or today, it's 1am over here).
[Galaxy S I9000 Android Development] Bejda:
Have a good nigh...morning sleep :) I'm already gone into busybox solution,just have to reboot i'll keep you informed.

No apparently same user.log with newer busybox and tried untick/tick+reboot but still not applied (limit max 800 ticked/current as 1000).

http://dl.dropbox.com/u/25071013/Busybox120317_user.log
[Galaxy S I9000 Android Development] benkya:
I can't install app from Play Store. It says me that I don't have enough space to install apps...

190CM9

you should cek your internal usb storage, not internal storage... is there enough space e.g capacity 13 gb and free 0 mb ?
[Galaxy S I9000 Android Development] mialwe:
Thanks for reporting back.

The new busybox completely solved all the "]]" errors, setting governor, read_ahead,... will work fine now. And all other scripts using the "[["/"]]" checks, too.

Regarding the limit800 - as you have ticked/unticked/rebooted I assume a bug in the app, I'll check this. Thank you for testing.
[Galaxy S I9000 Android Development] nmcc89:
The 800 MHz limit is working fine here. Using icssgs 4.2 (with an updated busybox) and 190LR.
[Galaxy S I9000 Android Development] mialwe:
Thanks for reporting.

I just reverted the 7freq-oc and rebuild the app with 800Mhz toggle - rebootet 1min ago, works, too. Bejda, maybe you can wipe MidnightControl data and retry ticking/unticking 800Mhz + reboot?
[Galaxy S I9000 Android Development] Bejda:
...hell no,still 1000Mhz after reboot and same log...well better wait a little to see if i'm alone having this behavior,keep searching on my side,thks.
[Galaxy S I9000 Android Development] mialwe:
Quickfix for 800Mhz not sticking, LR + CM9 version only for now:

- fixed 800Mhz not sticking at boot !? (Just reimplemented the checkbox after removing it for 7-freq-oc experiments, worked)

- readded apply colors at boot checkbox
[Galaxy S I9000 Android Development] scheichuwe:
You don't need sleep, do you?

It's kind of OT, but I need to say "thanks" for this commit

https://github.com/mialwe/samsung-kernel-aries/commit/cc2a8e49b5f0e3d9ccaaf925d3529283549ea1bc

:)
[Galaxy S I9000 Android Development] malcho:
Very good kernel.I like it.

Keep up the good work.

Midnight control app is great.
[Galaxy S I9000 Android Development] barome:
@ mialwe : great kernel. Your conservative is incredibly smooth and fast. Your app is wonderful. I change sd readhead to 256. If you would upload your work on our ftp server, pm me :)
[Galaxy S I9000 Android Development] ivke101:
Can you fix auto brightnest? Tnx
[Galaxy S I9000 Android Development] mialwe:
I'm sorry but without a description what's wrong I cannot fix anything!? What is wrong with autobrightness? I'm using it all the time without an issue.

@barome: Nice, 256kb is my choice, too :)
[Galaxy S I9000 Android Development] gdroos:
Hi, it seems to me that charging is quite slow and during navigating it is even discharging slowly. I did not have such a problem with another kernel. Does any body else have the same experience?
[Galaxy S I9000 Android Development] barome:
Yes that good to say to users that a value like 1024kb is a little faster for large files (and better for benchmark) but 256kb is the optimum value, very very fast for little file (but worse in benchmark lol)
[Galaxy S I9000 Android Development] silitek:
Very good kernel..fastest on WeUI. great job.
[Galaxy S I9000 Android Development] mialwe:
Thanks :)

@gdroos: I never noticed a changed charging behaviour and nothing was changed in the sources regarding charging.

@barome: Yes, made some tests with Midnight-GB a few weeks ago (adjusted a script provided in the Linux source comment regarding read_ahead and used this for benchmarking different read_ahead values and filesizes) -> 256Kb seems to work best for files up to 4-5Mb if I remember right.

But it's not good for benchmarks :)

Midnight-GB uses 256Kb as default sdcard readahead, Midnight-ICS 512Kb - I'm thinking of reducing this to 256Kb again but IO benchmarks will not like it and people comparing benchmarks will not know about the 256Kb...
[Galaxy S I9000 Android Development] Pipperox:
Well at least in my tests I/O benchmarks are grayed out so don't worry too much.. ;)

Although i love your kernel, i've uninstalled it because of a couple of issues:

1.2GHz overclocking is not stable for me. I get freezes / reboots about twice per day. Although my SGS is perfectly stable at 1.2GHz with other kernels

Compass doesn't seem to work, in Z-test. I'm not sure if it's a problem with the ROM though (Slim ICS 2.8) which however used to work fine.
[Galaxy S I9000 Android Development] nikec:
Great kernel - my first choice now. The only thing I am missing is the USB-Host integration. Is this in your future plans for the kernel mialwe?
[Galaxy S I9000 Android Development] mialwe:
Hm, 1.2Ghz use 1350mV arm.volt, maybe that's too much for your device - did you try (careful) undervolting? I don't know the voltages LiveOC uses but they may be lower, just a thought...

Compass: Thanks, I'll check this, never used it since I own my SGS :)
[Galaxy S I9000 Android Development] dark_knight35:
? If you liveOC, the voltages are the same as before and you have to find the right settings by yourself.
[Galaxy S I9000 Android Development] bhu1:
Mialwe, u can set the default as 256kb as now on ics people much people don't care about benchmarking cause its very slow using quadrant app...hehehe.

Btw, u thought of adding lulzactive governer? Also, ur conservative is a pleasure to use.
[Galaxy S I9000 Android Development] mialwe:
Ok, quickly checked with Slim 2.9 + Midnight 0.7.6-15 (dev version) and two compass apps: CompassPro, worked after calibration. SimplestCompass, worked instantly.

@dark_knight35 : Maybe I should ask like this then: Pipperox, did you use lower voltages @1.2Ghz with other kernels?

@BHuvan goyal: Yes, I think 256Kb will be default again, makes me feel better :)

And no, sorry - no more additional governors, schedulers,...

@All: Updated OP, theres a bug with setting max. frequency limit to 800Mhz -> doing this will cause a system freeze/reboot. This will be fixed in next version (running at 800Mhz all day, no issues and 800Mhz are really usable :) )
[Galaxy S I9000 Android Development] Pipperox:
Ok thanks, then i guess i'll have to try to reinstall the ROM first.

Concerning voltage, i use the stock 1.350V @1.2GHz on other kernels (Glitch and Devil)
[Galaxy S I9000 Android Development] mialwe:
1350mV is equal to the voltage Midnight uses for 1.2Ghz. Do you know the int.volt @Glitch/Devil?
[Galaxy S I9000 Android Development] bhu1:
lols,I tried 800mhz as Max and it froze. I thought its too low...hehehe.
[Galaxy S I9000 Android Development] smudgy456:
Hi, enjoying the kernal but ive noticed the 2g toggle doesnt seem to work, can only switch to 2g if you go into mobile network settings.

minor issue but just curious if this toggle is working for other users
[Galaxy S I9000 Android Development] ExAvantz:
flashed onto BLUE LIGHTNING- v1.1.1-BLACKeditioN ...

look smooth & fast

what is the best setting for a battery life ?

when i tick a Toggle night mode, screen become to dark for me...
[Galaxy S I9000 Android Development] nmcc89:
I'm using ICSSGS 4.2 and I noticed that using nstools along with midnightcontrol means that the cpu doesn't use the 100mhz frequency (using cpuspy to check). Uninstalling nstools fixes the issue completely. Anyway it's probably a combination of a different ROM or some sort of conflict between the two apps. Not much of a problem for me anyway since I'm not missing nstools, just thought I'd mention in case anyone else comes across it.

That aside the kernel runs perfectly; no problems at all since I've installed it and if anything the phone is more responsive (even with conservative!). Just like your GB kernel mialwe!
[Galaxy S I9000 Android Development] mialwe:
Not enough.

The 7 frequencies worked fine this time (booted using max. 1Ghz, switched to 1.128/1.2Ghz only if user requested) but it somehow did not feel right, "laggy" because of the two more frequencies on the way up to maxfreq!?...

But I had to try the 7-freq version again as I do not like the idea of not beeing able to solve the issue regarding booting-at-max-1.2Ghz-always I had a few weeks ago. Now it's solved. But I probably won't use it.

Using 5 frequencies + switchable 1/1.128Ghz feels much better here.
[Galaxy S I9000 Android Development] Bejda:
s'okay now on 201lr ,log gently said "found 800Mhz limit,activating..." :)
[Galaxy S I9000 Android Development] jifeng:
Hi mialwe,

Great kernel so far, but you seems forgot to attach midnight.apk to CM9 version:)

I just get it from 201LR, thanks so much.
[Galaxy S I9000 Android Development] Rootax:
I don't know how you do it but your kernel is very smooth. I'm a Devil kernel lover (and it's a great one), but mnics seem smoother, more fluid, even with the same governer/scheduler.

Nice Job.
[Galaxy S I9000 Android Development] firenxe:
Exactly the same feeling after comparing it with semaphore too... + its even more battery friendly here

Hope you keep developing mialwe!! Great job :)
[Galaxy S I9000 Android Development] adytum:
As the above posters said there's something incredibly smooth with this kernel that I don't find in other ones. Almost always makes the roms lagfree, and I change around a LOT.

Sent from the fridge.
[Galaxy S I9000 Android Development] Bonvaz:
thanks for your new works :D midnight is still the best!
[Galaxy S I9000 Android Development] mialwe:
OP updated, v202

202 - 2012/04/30

- app: fixed wrongly displayed default undervolting preset

- app: fixed colors not beeing applied at boot (v190 bug)

- app: fixed 800Mhz CPU limit not beeing applied at boot (v190 bug)

- zip: added missing MidnightControl.apk to CM9 version

If you have a completely functional v201 (201LR should be ok) you will not need this update.
[Galaxy S I9000 Android Development] bexem:
This is an error that I have it since MNICS143LR, now I'm on the 202 (same error on 190)...

Full log: http://cl.ly/24033i1j2t0u1M2m0O37/user.log
[Galaxy S I9000 Android Development] mialwe:
The app settings parsing relies on busybox correct handling "[[" and "]]" test commands (to distinguish between several options like ondemand, conservative, smartassv2).

Some ROMs use busybox versions which don't support those commands,e.g. ICSSGS, an earlier darkNight and a MIUI ROM. This has been discussed in this thread earlier, last time 2 or 3 pages back. There's an entry in OP (FAQ, settings-not-beeing saved) with a linked post containing a self-compiled CM9 busybox. Your busybox binary has to be replaced with a version correctly supporting those commands.

You can either contact your ROM dev or replace the binary yourself.
[Galaxy S I9000 Android Development] bexem:
Oh thanks, now it works... I'm sorry about the mistake (:

However before and now is the best kernel that I tried!
[Galaxy S I9000 Android Development] VexMunja:
I'm using your kernel with Tiramisu Rom and everything works smooth & stable! Excellent kernel! Keep up the good work!

Sent from Tapatalk 4
[Galaxy S I9000 Android Development] powerdams:
It's the best kernel for ICS, i've tried a lot of rom/kernel combinaison.

I obtain the best result with SlimICS rom & MNICS, thanks mialwe :)
[Galaxy S I9000 Android Development] fahad123:
+1 :)
[Galaxy S I9000 Android Development] xmarciN0ox:
Hey your Kernel is amazing. Ive used devil before, but this runs much better and smoother.

The midnight app is very usefull.

Keep Up the good work.
[Galaxy S I9000 Android Development] saszseb:
Auto brightness didn't work here.

Sent from IMM76I.
[Galaxy S I9000 Android Development] mat0122:
it's working great for me
[Galaxy S I9000 Android Development] fahad123:
I am on slim ics 3.5 and it works for me partially.. when I am out in the day light it doesn't change to high brightness and i have to switch the auto brightness on and off to change it to the high level.. other than this kernel is working real smooth and fast..

Thanks a lot!! :)
[Galaxy S I9000 Android Development] cink40:
Works flawlessly, slim 3.5+202lr

Sent from the Outer Space
[Galaxy S I9000 Android Development] mialwe:
This has been adressed in this thread multiple times. In short:

- experienced the same for various kernels (including CM9 stock)

- brightness goes up one time, then does not change anymore unliss ticking AB or screen-off/on once.

- AB does not work unless I use customized levels on e.g. CM9 or Slim, if I do it works fine.

- light sensor does report values

- ICS 4.0.3 -> 4.0.4 "improved" autobrightness (where is source?)

- had no issues with 4.0.3 if I remember right

- compared gp2a sources yesterday without finding related differences

If AB works flawlessly for you do you use the customized levels or any other autobrightness option?
[Galaxy S I9000 Android Development] mat0122:
I dont use customized settings of AB, I have only turn on AB option, thats all ;)
[Galaxy S I9000 Android Development] 2k4ever:
i don't think so

ICSSGS 4.2 has problems with the light sensor an is still 4.0.3

the solution is simply to use CM9, AOKP or SlimICS and activating the lightsensor filter

I think that it is quite an acceptable workaround, especially because ICSSGS has not been updated and therefore most users will use on of the above mentioned roms - and if you don't, try SlimICS, its great and absolutely stable combined with mialwe's kernel
[Galaxy S I9000 Android Development] -Loom-:
I played around with the lightness filter and enhanced brightness settings in AOKP, but honstely: The amout of features were just overwhelming and looked overly complicated.

Anyone who would like to share their settings ?
[Galaxy S I9000 Android Development] cink40:
Yes, customized settings.

Sent from the Outer Space
[Galaxy S I9000 Android Development] xmarciN0ox:
So could you Post your settings please?
[Galaxy S I9000 Android Development] Kocai:
Hey guys, anyone lost the charging animation when charging the phone while it's off?

ROM: cm-9-20120425-NIGHTLY

Kernel: 202CM9
[Galaxy S I9000 Android Development] mialwe:
This sounds like you had it working and now you lost it. But:

http://xdaforums.com/showpost.php?p=24378471&postcount=14899

1) You asked pawitp on Apr 3 about this - even if pawitp edited the FIM-response as "unrelated" you had the issue 4 weeks ago - without MNICS-202CM9, right!?

2) You asked Stratosk when using Semaphore about the same issue (9 Apr): http://xdaforums.com/showpost.php?p=24639277&postcount=2848

Would have been nice mentioning/linking this as I'm spending a lot of time searching for this issue :-/

But I can confirm this behaviour. Don't know if it shows up with CM9 stock kernel, too, anyone tried?
[Galaxy S I9000 Android Development] Kocai:
First of all, I'm very sorry not mentioning/linking my posts on CM9 thread and Semaphore thread. I did not intend to accuse your kernel of something faulty. I was merely reporting an issue. Please accept my sincere apology.

Second, from my experience this behavior didn't happen under the following conditions:

1. Using CM9 stock kernel (apart from that particular build I used on April 3).

2. Using Elite v9.1 with MNICS-143.

So, I'm curious on what causes this issue. On Slim ICS, krarvind removed all of the battery_charging_xx.qmg, chargingwarning.qmg and disconnected.qmg so it's normal if there's no charging animation when we charge while the phone is off. But on CM9, all of those files are on \system\media so I don't understand why using your kernel would cause the charging animation doesn't work.

The weird thing is that I would get notification when the phone is fully charged (phone vibrates and shows 100%).

Forgot to tell you, the charging animation did work before I switch to your kernel (using stock CM9 kernel). Again, not saying that your kernel is bad. I appreciate your work. Used to use your GB kernel because it's the closest one to speedmod kernel.