yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] doc_2nas:
Thank you Mialwe. On his thred DerTeufel1980 said he used same boot init process as midnight and maybe init.d is executed before sys init, so the setting from init.d is overwritten. Thank you for looking into this issue.
[Galaxy S I9000 Android Development] Bonvaz:
Yeah it would be great a new version with the new changes from pawtip in memory management ..but I know this is only an hobby and you have work and family,so is up TO you :)..
[Galaxy S I9000 Android Development] mialwe:
I completely agree as Pawtips settings maybe are the "safe" version of the initial memory reservation changes. BUT: It only works if ROMs provide the neccesary changes, too (CM9 does).

Most probably I will not provide patched files with MNICS as I don't want to copy files from some thread and do not have the time to recreate my ICS developement environment and compile them myself right now (and I don't know if there are any other files needed than the ones in Pawtip's test ZIP from the CM9 thread).
[Galaxy S I9000 Android Development] Bonvaz:
I understand! thansk for your reply!
[Galaxy S I9000 Android Development] habylab:
I see youve been working hard on your commits in your source, an update this week maybe?

Sent from my Galaxy S running Slim ICS 3.2 with Devils 2.0.67xl Kernel using the XDA Premium app
[Galaxy S I9000 Android Development] mialwe:
Maybe, don't know. Don't expect too much, the dev version basically contains some bugfixes and fast charge mode.

Most of the commits you see come from experimenting with a slimmed down MidnightControl and reduced app interface/settings parsing via initramfs.

As I found that I cannot completely remove the app because of the color controls and nightmode I decided to keep it as it is - providing *all* basic options for CPU, color, IO, options,... so I had to revert my commits in Github.
[Galaxy S I9000 Android Development] rodrigoalumno:
First of all,thank you for this awesome kernel. But there is something I want you to know because maybe its a bug I don't know. The thing is whith the latest version of LR I have problems with the night mod. In the 0.9.2 HR version when I switch on night mode the autobrightness works properly but in this latest version it doesn't work. I hope I'll be useful . Thanks again!
[Galaxy S I9000 Android Development] bennybaz:
Where can I find the dev version?
[Galaxy S I9000 Android Development] mnazim:
For devs obviously... not publicly released...!!!

:rolleyes:
[Galaxy S I9000 Android Development] mialwe:
Autobrightness is supposed to be non functional with nightmode. After the 0.9.x versions I removed some old code from Midnight-Gingerbread which adjusted brightness based on a small formula, maybe that's the reason for autobrightness working with nightmode on this older versions.

Latest versions => nightmode = fixed (minimal) brightness for lowlight environment.

But I still have issues with autobrightness in general on all 4.0.4 ROMs (discussed here some pages earlier, maybe not kernel related, issues persist if I completely remove nightmode which only is active if the app toggle is checked or even completely switch to stock kernels). Maybe I should try an autobrightness driver implementation like Semaphore as suggested by some users here...

@bennybaz: No, the dev version (which is MNICS-161LR right now) is on my phone only as it's the dev version. Some things still need some testing before it's ready for upload.
[Galaxy S I9000 Android Development] 2k4ever:
as mialwe explained, thats the intentional behavior

if you want to enable autobrightness to use very low brightness, just set the Min. brightness in Display to 1

About autobrightness in general: i voted for a specific driver before, but I'm not so sure that its necessary anymore

i have now switched to SlimICS 3.3 which uses the CM implementation of user defined lightsensor levels and that allows all the flexibility and a nice ui to set it up already

(even though its a bit buggy, i have to use the lightsensor filter to get it working at all)

My point is that surely it would be nice to have a driver for the purpose, but it is not really necessary especially as your time is limited
[Galaxy S I9000 Android Development] renedca:
I liked install your kernel , and I want know how have one good installation.

I´m checking the different posts and i have the following configurations:

1.-

a.	In CWM

- Run Install ultimate_kernel_cleaning_script_v4_by_lippol94.zip (Thanks to Lippol94) http://xdaforums.com/show...ghlight=lippol

- Install midnight Kernel

- In advanced option, run Reboot Recovery (NO Reboot system now)

b.	Now we are in the CWM again but on midnight Kernel

- In advanced, run clean NStools settings

- In advanced also, run clean init.d directory

c.	Reboot system now

2.-

a.	In CWM

- Run ultimate_kernel_cleaning_script_v4_by_lippol94.zip

- In advanced, run clean NStools options

- In advanced also, run clean init.d directory

- Install mignight Kernel

b.	Reboot system now

my kernel in this moment is Devil 0.65. with rom elite 10.1

Other question.

I want one kernel with good practice with battery.

what is the best version mnics 143 or 143LR

thanks for you help in advance

regards

renedca
[Galaxy S I9000 Android Development] thearc77:
Mialwe:

I'm running your kernel ported by F4k for SGS 9000B, and he discovery/found this settings with his custom mod (and any other with same mod in Setttings).

With this setup the autobrigtness work flawless with any mod with same menu in Settings. Works with any ICS.

Sorrry for the spanish language in video but you can math the options.

http://www.youtube.com/watch?v=XFFCUgs2x6s
[Galaxy S I9000 Android Development] mat0122:
143 lr VERSION

i have problem with night mode, when i turn it on i have green screen and it's hard to see something
[Galaxy S I9000 Android Development] mnazim:
Decrease the gamma values towards stock values...
[Galaxy S I9000 Android Development] mat0122:
mialwe

is it possible to make a night mode widget? it will be a practical function :)
[Galaxy S I9000 Android Development] mialwe:
- LR makes a difference in available RAM. LR = LargeRAM (386Mb), this enables us to keep more apps/processes in RAM, *maybe* (not sure) this leads to more battery consumption, too (processes aren't killed due to low RAM as before).

- CWM/cleaning: I cannot give a good advice here as I don't use any cleaning scripts, but I can describe how MNICS works and you can dcide yourself: MNICS does not use any init.d scripts, all settings/tweaks are applied on boot *before* init.d scripts are executed. This way users can change almost everything if they know what they do.

MNICS completely cleanes up /system/lib/modules and afterwards copies it's kernel modules to /system/lib/modules like other kernels. MNICS copies the BLN aries-lights.so to /system/lib/hw/ like other kernels.

If you enable Logcat vie CWM MNICS copies logger.ko to /data/local.

Lippols cleaner script cleanes modules if I remember right (not needed for MNICS) and removes /data/local/logger.ko in case the module is from another kernel (not sure if this is needed, foreign logger.ko just won't work I assume).

CWM clean-init.d options depend on what they do and if you use init.d scripts. If you have an empty init.d like me (MNICS tweaks are enough for me) - no need to use it. If you use init.d scripts from another kernel or ROM (jes, they sometimes copy scripts to init.d): Use the CWM option to clean init.d (old kernel or MNICS) to clean it. MNICS completely removes init.d contents (subdirs, too). Don't know about other kernels.

Short: Don't think about /system/lib/modules, remove /data/local/logger.ko if it causes issues or just overwrite it via MNICS CWM activate logact option, make sure init.d is empty if you don't use init.d scripts (CWM, root explorer,...).

Jep, that's what a lot of users mentioned here before - as soon as you use any custom brightness option in your ROM autobrightness seems to work well. Does not work on stock-like ROMs like ICSSGS which do not have such options, that's why I'm thinking of a new driver implementation. I love stock-like ROMs.

That's right. Green color on low brightness is caused by too much gamma adjustment, has been an issue for months starting with Voodoo color back in Gingerbread times. Raise your gamma (I'm personally using -5 or -10, that's enough for me) and the green screen issue will be solved.
[Galaxy S I9000 Android Development] mialwe:
Dont get me wrong but I'll just post this link: http://xdaforums.com/showthread.php?p=24547945&highlight=widget#post24547945

Answered April 7, had to use thread search myself.
[Galaxy S I9000 Android Development] thearc77:
So we must have to wait some days more for Onecosmic and ICSSGS Team next build.

Any way, using 4.0.4 and your's 143LR i'm getting more than 30hs of batery

Thanks :D
[Galaxy S I9000 Android Development] habylab:
Much better battery with your kernel! So good!

Would you recommend sio or noop with your smooth conservative for battery?

Sent from my Galaxy S running Slim ICS 3.2 with Devils 2.0.67xl Kernel using the XDA Premium app
[Galaxy S I9000 Android Development] farid993:
Mialwe, Did you implemented pawitp changes in the 161LR? Thanks
[Galaxy S I9000 Android Development] mialwe:
Not yet, real life is keeping me busy and I'm thinking of trying JW4/5 for a few days. Which one are you interested in?

@habylab: In general (not battery) I use SIO (default in MNICS).
[Galaxy S I9000 Android Development] farid993:
I only saw this post in semaphore topic and i liked to know mnics has not similar problem for pawtip changes in 161LR.

Thanks
[Galaxy S I9000 Android Development] mialwe:
No. This is kernel + ROM related. Pawtip uses new RAM reservation values with the CM9 kernel, the ROM (CM9) properly supports this.

MNICS uses the values/memory reservation krarvind introduced to i9000 which works on all ROMs supporting this or are patched to use this.
[Galaxy S I9000 Android Development] xtoad:
I was pleasantly impressed with Slim and of course, MNICS, but miss some features (camera, reliable FM Radio, and strangely Samsung messaging...)

I gave JW5 a try...The extra RAM is nice and would be even better with your Midnight kernel... :D

ICS will still be here later... ;)
[Galaxy S I9000 Android Development] mialwe:
To be honest - I'm thinking about JW4/5 for a few days now ... :-)

tapatalked...
[Galaxy S I9000 Android Development] ramas123:
Not worth, believe me. It lasted about 2 hours on my phone and I came back to ICS. :)
[Galaxy S I9000 Android Development] Mr.AFK:
I'll be there for you :-). Also on stock :-)
[Galaxy S I9000 Android Development] extralife:
... half the time it would be done :D

anyway - i like your work

- here and there -
[Galaxy S I9000 Android Development] saszseb:
pawitp.
[Galaxy S I9000 Android Development] mialwe:
Jep, I'd like to have that "half the time" :)

Anyways, JW5 is installed since a few hours - not sure how long it will stay. Was GB really *that* slow??? Open app - wait 2-4 sec - work - close app -reopen app - wait again 2-4 sec -... still on stock kernel, no time for Midnight...

Uups, thanks. Sorry pawitp.
[Galaxy S I9000 Android Development] andip71:
Yes Mialwe. Pleeeeease. JW5 could be the last official Sammy FW for our beloved Galaxy.

It would be a perfect closure for all of us - running YOUR great kernel.

Thanks, I count on you (already) :)

Andi
[Galaxy S I9000 Android Development] xtoad:
Awww...it's not so bad.. ;) I didn't find it worse than JW1 or anything... Maybe it would be better with Midnight? :) You know, as a last hurrah to GB?

Keep up the good work where ever you land!

Edit: Yeah Andi, Midnight and your mod is just about as good as stock sammy gets
[Galaxy S I9000 Android Development] Bonvaz:
Imho I would prefer new update for ics kernel,in the free time of mialwe ovviously..this is the best kernel for ics,I want more:D
[Galaxy S I9000 Android Development] mialwe:
Back on ICS. Love Nandroid. Wasted hours.
[Galaxy S I9000 Android Development] WilliamHicks:
Hi there. Thank you for the excellent kernel. A few versions ago, i was able to swipe along the notification bar, and get from full brightness, all the way down to night mode. This was perfect, and eliminates the need for a widget. Can you make this work again?

Using slim rom, on galaxy S I9000
[Galaxy S I9000 Android Development] malcho:
Right choice:)
[Galaxy S I9000 Android Development] krosscheck:
Which rom do you use?

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] mialwe:
If your ROMM supports sliding brightness thi sshould be possible if you lower the min_brightness via MidnightControl (default 20). This will not be possible with nightmode enabled as min_brightness and brightness itself is fixed to 1.

Switching 4.0.4 ROMs.
[Galaxy S I9000 Android Development] WilliamHicks:
Thanks. This made it swipe to a dimmer setting, but still not as dim as night mode. I know it worked before, but if it is no longer possible, i understand.
[Galaxy S I9000 Android Development] mialwe:
If min_brightness is set to 1 this is the definate minimal brightness.

Maybe your ROM limits this to a higher value itself, don't know this.

A few versions back MNICS had a formula calculating even lower brightness than the used ROM allows (e.g. ROM allows min. 10, kernel reduced this to e.g. 1), this has been removed to clean up the code, because it had only minimal effect on the brighness (without nightmode only low have been substracted from brightness level) and was only used to toggle nightmode (= formula substracted high values from brightness which led to min_brightness 1).

Maybe you are missing this formula.
[Galaxy S I9000 Android Development] ramas123:
I told you! :)
[Galaxy S I9000 Android Development] Faith140291:
keep up the good work on this kernel, because i think is the best on all sides, also in performance with heavy games (blood and glory (nr) and shadowgun) they run smoothly :) great!
[Galaxy S I9000 Android Development] Bonvaz:
Today I tried other kernels for I9000.....no way...this kernel is the fastest for ics that I ever seen....please keep on working for us :)
[Galaxy S I9000 Android Development] farid993:
Any new news? we are still waiting for new version :)

good work mialwe, your kernel is lovely.
[Galaxy S I9000 Android Development] d_jaxx:
Stop ask for ETA's...

Everything is fine... isn't it? ;)
[Galaxy S I9000 Android Development] farid993:
I do not ask ETA, i only want to know mialwe work on new version or not
[Galaxy S I9000 Android Development] F4k:
I think he it's working on it, you can check about a few new features, fixes, in second post ;)
[Galaxy S I9000 Android Development] farid993:
Oh, thanks. My bad! I did not see second post till now.
[Galaxy S I9000 Android Development] mialwe:
Hm, maybe I should clean second post and move the changelog to OP.

I'm working on MNICS as often as possible which is not much these days, real life does not allow more, sorry.

Took me some time last night to test an idea about (again) 7 steps oc without forced boot @1200Mhz - it worked but somehow recovery and boot until initramfs ran @100Mhz - not nice.

I was not able to find the bug/reason for this so I reverted everything today. I'll test this version and upload within a few days.

Changes are currently @ post #2, there will probably be 3 versions: 340Mb, 369Mb (CM9 compatible) and 386Mb (LR, krarvind's patch compatible).
[Galaxy S I9000 Android Development] 2k4ever:
Thanks for keeping us in the loop and its good to know that there will still be a "classic" bigmem version for the non-CM9 ROMs out there
[Galaxy S I9000 Android Development] -Loom-:
@Mialwe:

Do you still consider reworking the autobrightness feature?

Today I went geocaching with my phone, and most of the time, the screen was much too dark to read anything. When manually setting the brightness to some value, then re-enabling autobrightness, everything was find again.

It's quite unuseable at this point, at least outdoor. Since Semaphore borrowed your vibration intensity code, maybe you can now get his autobrightness code ?
[Galaxy S I9000 Android Development] mialwe:
Hm, I'd prefer to find out why stock autobrightness stopped working (I think it was working with 4.0.3, stopped with 4.0.4) and why it starts to work somehow if we enable some of the custom autobrightness options from e.g. CM9. Testing this right now, switched to CM9 (which works great btw) for this.

But you are right, I'm thinking of using a new autobrightness driver, too, in case I cannot find the issue. I won't copy Stratosk's code but I surely would have to use the basic structure as I do not have enough experience in creating completely new drivers.

A few days ago Stratosk notified me (thanks again Stratosk, you really are a great developer) that he would help with information on his driver if I have any questions and even told me it would not be a problem using his complete driver - but that's not what I want. It's Semaphore's/Stratosk's driver/work.

As real life continues keeping me busy things will slow down as MNICS users probably have noticed. Sorry for that.
[Galaxy S I9000 Android Development] stratosk:
Of course, you can use the driver anytime you want. And you can PM me for details. I would be happy if I could help you for something.

OK, I made this driver but anyone can use it. This is GPL. And of course I used code from you (thanks, thanks) and almost from any developer here (thanks again).
[Galaxy S I9000 Android Development] test123456789012:
Hi there,

no need for any updates because everything works so smoothly right now. Thanks again, mialwe! :)

I just wanted to report something strange and I don't know why that is. I installed a super clean CM9 nightly – I think from april, 16th. After that your latest kernel LR. I patched the ROM to enable LR support. Everything good until I installed latest semaphore 1.0.1s for testing purposes. I immediately got high Android OS usage (<25%) and my battery drained really fast. I had to revert back by installing anew with a factory reset. Why, oh why is that? I know the article „what the Android OS usage is and what it's not“ but I can't figure this out. Always thought, it was ROM related. Could someone here please enlighten me? :)
[Galaxy S I9000 Android Development] adytum:
Regarding the auto brightness issue; I think people should post whether their light sensor actually works, with z device test or something similar, before concluding that it's a kernel issue. There's a chance it could be rom related.
[Galaxy S I9000 Android Development] adytum:
Perhaps you should post in the semaphore thread, if that kernel was the problem, if I understood you correctly.

Anyway, the android os usage most likely stem from an app or system function using a lot of wakelocks. Check it out with better battery stats, in the partial wakelocks tab. In any case, (I might be wrong here but it's my experience) cm roms tend to drain battery a little bit more than other roms and are a bit prone to high android os battery usage.
[Galaxy S I9000 Android Development] test123456789012:
I think it has been already made clear, that AB /is/ ROM/driver related. See p.42 and further.

Edit: Thanks for the reply. I checked with BBS but can't remember finding anything unusual. I don't think it's kernel related therefor I didn't post in stratosk's thread but rather wanted to give positive feedback with a sidenote. :) So I went OT.

It's just so strange that it happened after changing kernels. It could be that it has something to do with the combination of ROM and kernel.

You can ignore this post, no need to discuss it any further..
[Galaxy S I9000 Android Development] adytum:
I'm sorry if I came over harshly, that wasn't my intention :)

I also find that in periods of much tampering with kernels and settings, android os usage is pretty high regardless of rom and kernel.
[Galaxy S I9000 Android Development] test123456789012:
You didn't. :)
[Galaxy S I9000 Android Development] TheBus:
i try fast_charge with "Fastcharge / Force AC Toggle" but it report that the kernel is not compatibile.

Galaxy S GT-i9000 with CM9 and midnight 143
[Galaxy S I9000 Android Development] nmcc89:
It's coming in the next version - current is 143

@mialwe I've been running this kernel with icssgs and the ram patch for a couple of weeks now. It's rock solid. Your family and life are way more important, nothing needs changing at the moment!
[Galaxy S I9000 Android Development] fahad123:
this kernel works great with the latest slim ics 3.4.. the only problem is that 720p video recording is kinda laggy.. feels like it misses the fps.. i have also tried the simple version but its the same on that and on LR as well.. its not a rom issue coz i have tried it with semaphore kernel and the 720p video recording was smooth.. is there any fix available? really can't leave this kernel because the overall performance is smooth and fast as hell!!
[Galaxy S I9000 Android Development] giokspy:
I try this kernel on slim 3.3 and on working CPU spy .why happent this?
[Galaxy S I9000 Android Development] mialwe:
I'm currently on CM9 and CPUSpy is working fine.

To make CPUSpy work a certain module (cpufreq_stats.ko) is loaded at boot. If something went wrong while flashing the kernel CWM zip your install might use an older, incompatible version of this module. Same if you installed only the boot.img of MNICS (the modules are in the CWM zip and will be copied while flashing the CWM zip). 1st idea: Please try flashing MNICS again vie CWM.

@fahad123: No idea, I'll check this. Anyone else with laggy 720p recording?
[Galaxy S I9000 Android Development] test123456789012:
On latest CM9 nightly (720p patched with MNICS-143LR) 720p recording is as smooth as ever.
[Galaxy S I9000 Android Development] fahad123:
thanks a lot!! .. it feels like the frames are skipping.. after zooming in and zooming out during the video recording fixes it sometimes but not always.. which means the bug is there.. it will be kind of you if you'll check on this..

THANKS A MILLION for this great kernel!! :)
[Galaxy S I9000 Android Development] 2k4ever:
i had the problem too

for me, it was because i was messing around with busybox

not all of my apps worked with the version provided in SlimICS and with the version from the latest busybox installer as well as the CM9 version mialwe provided in this thread, i hat the same error on CPUSpy as you

update to 3.4 or at least apply the OTA patch for 3.3 (if you don't want to upgrade, but if you have messed with the busybox, it could be that the patch is not enough and you will have to upgrade) as krarvind has fixed the busybox problem
[Galaxy S I9000 Android Development] bhu1:
Waiting for your next kernel build. No fast charge in semaphore has left me with ur kernel and devil as only choice. But it seems like the choices left are pretty awesome. ;)
[Galaxy S I9000 Android Development] Pac-Man:
It does not mount CM9 external memory cause I do not see some app I have installed

tapatalked ... !! ®
[Galaxy S I9000 Android Development] mialwe:
v190, 190LR, 190CM9

190 - 2012/04/29

- kernel: sync with CM9 sources (incl. sdcard mountpoints)

- kernel: USB fast_charge by chad0989 (toggle widget available) [default: deactivated]

- kernel: enabled deadline/cfq IO schedulers [default: still SIO]

- kernel: 2 bugfixes (cpufreq), thanks to derTeufel1980 for the hints

- kernel: touchwake sync with Ezekeels source

- app: added fast_charge toggle

- initramfs: 256Kb sdcard read_ahead default

- initramfs: added /data/local/userinit.d execution

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

Download in OP, v190=340Mb RAM, v190LR=386Mb RAM for ROMs with large RAM patch, v190CM9=~170Mb RAM for CM9.
[Galaxy S I9000 Android Development] mialwe:
Just in case you use v143 (v90 uploaded some minutes ago) - mountpoint switching is implemented in v190CM9.
[Galaxy S I9000 Android Development] DerTeufel1980:
First :)

Nice to see, you found the time for the new kernel

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] lippol94:
Congrats! You won an icecream... :D

Thanks a lot mialwe! I consider your kernel the best out there :) Don't know what you've done but it's so good!