yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] mialwe:
Yes, I surely know I can trust you :) (and I accept almost every bug report and start researching, that's one of my problems I think :))

But as a lot of other users read this, too I like to answer with a little bit more information. Now that I know you are using the kernel stock setup I have to say - no, I don't know what's happening for you. Only difference I spot is 3G instead of 2G and I'm sure you know that 3G uses more battery. No issues while actively using the phone for me, until now nothing similar reported here.

Maybe this can be tracked down using some additional apps like CPUSpy for an used-frequency overview and/or betterbatterystats for the wakelocks/processes? OSMonitor or adb top for cpu usage/processes?
[Galaxy S I9000 Android Development] cink40:
mialwe, you did not answer me in wich ROM (and hugeram kernel) you have working compass? Please answer.
[Galaxy S I9000 Android Development] mialwe:
Sorry, I cant right now. Please accept that. I'll explain later as soon as I'm allowed to.

Working compass in the test before (same apps as in answer to your post) was with Slim 3.0 I think. I had to calibrate once, then compass started working ok.
[Galaxy S I9000 Android Development] 2k4ever:
i experience quite a high battery drain while the screen is on and on homescreen because i'm using a live wallpaper and the kernel keeps running on 1Ghz (Conservative governor)

on other apps (mainly FBReader, i'm reading a lot with my phone) battery consumption is rather normal

so if you are running a live wallpaper, lippol94, that could be the problem
[Galaxy S I9000 Android Development] mialwe:
Thanks for the hint, I just tested this with PhaseBeam live wallpaper, swiping left/right several times:

1min 19sec:

1128Mhz - 9%

800Mhz - 8%

400Mhz - 9%

200Mhz - 72%

100Mz - unused (as GPU is active -> 200Mhz min).

No issue here but the scaling triggers have changed slightly in my latest test kernel, maybe theres an issue with earlier versions...
[Galaxy S I9000 Android Development] 2k4ever:
i just retried it:

i'm normally using this lwp: https://play.google.com/store/apps/details?id=com.eightsoft.ICSLiveWallpaper

and just like i said, with that one i get the CPU running on 1GHz constantly

but when trying PhaseBeam, i get CPU usage similar to yours with most of the time on 200MHz!

in the end, its not the kernel to blame, but the badly made lwp

still my point stands, if you are using a lwp, lippol94, that could be the reason for your high battery drain
[Galaxy S I9000 Android Development] mialwe:
- deleted - not relevant.
[Galaxy S I9000 Android Development] 2k4ever:
i agree, but the one i use is so pretty ;)

i think the important thing is to be aware of such things so i / the user can decide to accept the trade-off of higher battery consumption

and i'm quite sure that a lwp doesn't have to be so CPU intense, the problem is that its badly programmed and not making use of the GPU
[Galaxy S I9000 Android Development] Bubble-be:
Is there a way to set e.g. logcat on "externally", I mean without the gui ?

It would really help to debug when first flashing a rom.
[Galaxy S I9000 Android Development] mialwe:
Maybe from ROMs side, kernel can load logger.ko or not. Maybe there would be a possibility to filter messages in the source of logger (did not look for that now) but that would mean a lot of research *what* exactely to filter. So - maybe.
[Galaxy S I9000 Android Development] Bubble-be:
Maybe we have a misunderstanding here. Your reply does seem more complicated than I bargained for. ;)

Can I switch on logcat, either through adb, flashing a zip or - maybe an idea for a future release - through selecting a menu option in recovery ?
[Galaxy S I9000 Android Development] mialwe:
Ahh, yep, misunderstood this, sorry.

No, currently this is not possible. The logger module has to be loaded at a very early stage of the boot process or even has to be compiled directly into the kernel (= no module, always active). I tried loading logger.ko later in times of Midnight-GB wich resulted in Logcat giving only a few system messages but e.g. never app debug messages. Same for ICS now. That's the reason we have to load it this early (via init.rc in initramfs that is).

Forgot: Enabling Logcat via recovery will come back (the Gingerbread CWM recovery contained lots and lots of options including maxfreq, undervolting, LMK, module loading,... everything you find in MidnightControl now). As I'm writing this I'm working on reintegrating some of the options into CWM. As one has to reboot for en/disabling Logcat this option belongs to CWM, freeing some space in MidnightControl.
[Galaxy S I9000 Android Development] Bubble-be:
Nice to hear.

Revisiting the root thing I mentioned earlier : Devil 15.1 gives me full root with adb, while the newer Devil 2.* and Midnight do not.
[Galaxy S I9000 Android Development] mialwe:
Could you tell me what the root thing was?

tapatalked...
[Galaxy S I9000 Android Development] Bubble-be:
Maybe it's something simple.

Using adb shell with Midnight and the newer Devil gives you $, while the older Devil directly drops you at #.

After a flash, I tend to use Android Commander to easily edit files on /system. It will only work as I intended when using Devil 15.1.

Adb remount (not adb shell remount) only works on the older Devil as well.
[Galaxy S I9000 Android Development] scheichuwe:
Try

adb root
[Galaxy S I9000 Android Development] Bubble-be:
uhuh, that just works :o

Thanks!

Wierd that it wasn't needed for the older Devil, but I do feel silly now.
[Galaxy S I9000 Android Development] burakgon:
Transfered to here again. :)
[Galaxy S I9000 Android Development] burakgon:
I want to make a battery hero rom with your kernel.
[Galaxy S I9000 Android Development] edwinlim9310:
Does 0.9.0-2-HUGERAM works on Slim ICS 3.2?
[Galaxy S I9000 Android Development] test123456789012:
Works perfectly.

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] edwinlim9310:
May I ask if you're replying to my post above? If so, does it breaks anything? I heard it breaks 720p recording. But does it breaks playback as well?
[Galaxy S I9000 Android Development] test123456789012:
Yes, I was... Neither recording, nor playback is broken.

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] edwinlim9310:
Thanks! I see from your sig that you wrote on both midnight hugeram and semaphore sbm kernel. May I ask which you preferred for better battery? Or is the default kernel in Slim ICS is good enough?
[Galaxy S I9000 Android Development] test123456789012:
I really did not have the patience for testing both kernels well in this respect :-)

But I'd guess that both kernels provide good battery life. Semaphore can be locked to 100MHz when GPU is inactive (this could save battery, provided that the galaxy runs more efficiently at this frequenzy), on the other hand midnight can be undervolted..

I think your data usage and display brightness will have a greater impact on battery life, second is governor..

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] edwinlim9310:
I see. Thanks for the reply. Since I am not a geek in all these terms and it's functions, I guess I could try the default kernel in Slim ICS first. But I must say I looked into this kernel (midnight) because of it's target functionality.

Really appreciate for all the hard work put in by all the ics developers, whether is it on rom or kernel. Cheers! :D
[Galaxy S I9000 Android Development] Bubble-be:
Ok, as I had it in my adb, I thought it was a general thing. It works after adb root though, so I'm a happy camper.

Thanks for the great support!
[Galaxy S I9000 Android Development] -Loom-:
Yes, why not take whats good and proven ? Semaphores solution works just fine ; )

It would also help conserving battery, since brightness will always be at the correct level, and not jumping up and down for no reason.
[Galaxy S I9000 Android Development] yaatzek:
I totally understand Mialwe, if i were the developer of the kernel i wouldn't copy paste others work if i would not understand it or have enough knowledge what I'm implementing. That is how many custom rom developers do, they cook ROM out of someone work not totally understand what they're putting in.
[Galaxy S I9000 Android Development] -Loom-:
I got your point.

The question is: DOES a rom developer always have to understand every aspect of the code he is putting in? Why start at zero all the time?
[Galaxy S I9000 Android Development] yaatzek:
If he didn't unstandard it, then how will he try to repair something in that case if he doesn't understand it 100%?
[Galaxy S I9000 Android Development] -Loom-:
By teaming up with Semaphore?

There are so many kernels, each has one or more features, that really stands out. Brilliant in their own right. And no kernel which combines it all.

I know it's good to have a choice, but why not create a kernel together? Well, I guess now that's getting off-topic .. ; )
[Galaxy S I9000 Android Development] mialwe:
Only speaking for myself: Because I'm working on Midnight because I enjoy reading, learning and programming stuff. I don't want to provide a hyper-optimized, feature packed kernel to satisfy every single user, I just like what I'm doing - and the learning part is the most important to me (second one would be the communication between all devs/users).

But I fully understand your point about the autobrightness, too, still don't know what exactely is the cause for the autobrightness issues on 4.0.4 ROMs, the 4.0.4 changelog says something about "changes" or "improvements" of autobrightness.

Maybe I'll take a look at the Google kernel sources, especially the brightness related parts. I'd like to have the stock driver implementation working, not necessarily a separate module.
[Galaxy S I9000 Android Development] -Loom-:
Sure, curiousity wins ;)

And it's not like the auto-brightness is completely broken. Just a little jump every while. You get used to it. Gives the phone a little character.
[Galaxy S I9000 Android Development] test123456789012:
Good morning!

I am using the night mode right now and I thought, wouldn't it be great to toggle that with a widget? What do you think? :-)

Besides this minor thing everything runs just superb, using 0.9.0-2-HUGERAM with conservative and slight undervolting.

Have a good one!

Test

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] mialwe:
No, no widgets (at least from my side). I don't like widgets (only use a clock linked to alarms and a week-overview linked to calendar myself, both custom minimaltext widgets).

The nightmode can be toggled via a sysfs file:

echo 1 > /sys/devices/virtual/misc/color_tuning/min_brightness
echo 1 > /sys/devices/virtual/misc/color_tuning/brightness_multiplier

Switching it off means sending 0 to brightness_multiplier and your desired min_brightness (default 25) to min_brightness. If anyone want's to code a widget or script this can be used.
[Galaxy S I9000 Android Development] test123456789012:
Thanks! :-)

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] malcho:
7 days on this kernel and not a single problem.Battery life great.

Thanks mialwe.
[Galaxy S I9000 Android Development] mialwe:
MNICS-139LR - 2012/04/07

- changed name: MNICS-<buildnr>[LR (large RAM for 386Mb)]

- kernel: 5 frequencies, switchable maxfreq 1/1.128Ghz

- kernel: adjusted smooth conserv. triggers, mp3@100Mhz again

- kernel: fixed internal divider bug, thanks to theDevil1980 for the hint

- kernel: removed old recovery backup (-700Kb)

- CWM: added manual zipalign option

- CWM: moved init.d/overclocking/Logcat toggles to CWM

- app: service for missed calls BLN

- app: cleanup

Switched kernel ID to "MNICS" (MidnightICS) + build number + LR (or not for stock RAM). Makes some things easier for me.

Back to stock 5 frequencies, in case you want 1.128Ghz max. this can be switched via CWM which contains a new Midnight menu (as in early versions of Midnight-Gingerbread if somebody remembers :) ).

Moved all options which require a reboot from the app to CWM (init.d toggle, Logcat toggle, 1.128Ghz).

MidnightControl now includes a service monitoring missed calls and switching on the LED in case you really missed a call.

There is only one checkbox to toggle BLN, this toggles BLN itself, the checkbox in settings->display->notificationLED and the LED@missed call. This way you don't have to activate several checkboxes.

MidnightControl supports static LED only, for blinking and scheduled BLN please support Neldar via BLNControl Pro.

Only LR (LargeRAM, 386Mb) for now, stock RAM (340Mb) will follow if needed.

EDIT: $§%&", as I'm writing this I remember that I forgot to update the help file - sorry for misleading info there on maxfreq/overclocking, will be updated in next version.
[Galaxy S I9000 Android Development] -Loom-:
Thank you very much!

Does this BLN monitor service run all the time? I already have BLN Pro installed, and I don't need another service for this.

MNICS ? Hmmm .... I liked Midnight better ;)
[Galaxy S I9000 Android Development] saszseb:
Installed.

I like the bootlog in the menu.

What do these mean in recovery:

zipalign packages in /system/app, /system/framework and /data/app?

Thanks.

Sent from ICS.
[Galaxy S I9000 Android Development] -Loom-:
Should provide a fast startup for the apps. Kinda re-sorting for flash memory.

But doesn't do AOKP this automatically when new apps are installed? Or is this valid only for system apps? I always get the message during boot that some files are been optimized.
[Galaxy S I9000 Android Development] Bonvaz:
Thanks for the new release,but midnight name is better :)..anyway thanks for your work!this kernel is great
[Galaxy S I9000 Android Development] malcho:
Great job.

I like new naming.Looks serious:)

Super that you add zipalign.

Great thank you
[Galaxy S I9000 Android Development] saszseb:
LED notif works only with BLN.apk.

Maybe because of missing "notification LED" in Settings>Display.

I'm on Elite ROM.

Sent from ICS.
[Galaxy S I9000 Android Development] abalam:
Wich 3 options do you use in zipalign what is best?

Sent from my GT-I9250 using

CyanogenMod9.0.0-RC0
[Galaxy S I9000 Android Development] cink40:
On slim, led works without Bln app, (also for calls)

Sent from the Outer Space
[Galaxy S I9000 Android Development] ghul21:
After installation, I lost my opportunity to adjust the brightness. Dark as hell, does not work the system settings the brightness :(
[Galaxy S I9000 Android Development] malcho:
You can use all 3 option.Most if the zipalign scripts do the same.
[Galaxy S I9000 Android Development] cink40:
+1 autobrightness nor custom brightness do not work.

Sent from the Outer Space
[Galaxy S I9000 Android Development] 2k4ever:
thanks for the update, mialwe!

I really like the ability to use LED notification without having to have BLN installed

however, like -Loom-, i would prefer to be able to deactivate the background service for missed calls as i use Missed Calls Reminder (which has a few extra functions)

about the zipalign option: does anybody know whether it can / should be used in combination with an odexed ROM (ICSSGS RC4.2)?

because afaik zipaligning is a substitution for odexing, providing faster start-up times for deodexed roms

had the same problem

toggle night mode once and change the min brightness in Midnight Control and everything works agian!
[Galaxy S I9000 Android Development] cink40:
Edit : toggled night brightness and now works

Sent from the Outer Space
[Galaxy S I9000 Android Development] ramas123:
Actually discovered cool thing about auto brightness in system settings>display>custom bacjlight settings.

Moddified a little bit and I have very pleasant ab values for myself.

Reccomend just do a little bit of work, you will be surprised ;)
[Galaxy S I9000 Android Development] mialwe:
I think I'm actually doing some work :)

This option is not present in *all* ICS ROMs but if it is it's a great one.

----------------------------------

BLN service: Yes, the service must be started at boot-completed state because if it would be started later another service would be needed to monitor if the user toggles the BLN button (or the app has to be running in the background all the time). However the service does nothing except starting the missed calls observer, maybe I can optimize this to work without a service. But it should not drain your battery or something like that.

Low brightness: Yes, as stated a few posts back you have to toggle nightmode once in case this happens to you. The reason is that older app versions used other values for the sysfs files (echo xyz > sys/.../nightmode_file). From now on this file accepts "0" or "not 0" (=enables nightmode). As your app data (=settings) did not change with flashing the new version the old values != 0 have been used -> nightmode on. Toggling nightmode once sets the new values (0 or 1) correctly.

Sorry I forgot that while working on the kernel part related to nightmode, I could have avoided that.

Brightness in general: I had issues with auto- and manual brightness with various 4.0.4 ROMs and kernels (not only Midnight) while testing some things. Autobrightness failed to lower brightness again in dark environment, manual brightness sometimes worked, sometimes not, sometimes after tryying several times. Maybe I have to change something in the kernel for the "improved autobrightness" (Google 4.0.4 changelog). This was discussed here a few pages back.

BLN only works with bln.apk (saszseb): No - BLN works without another app for weeks over here.

Zipalign: I added a zipalign binary (self compiled, used with Midnight-Gingerbread for a long time) to be able to manually decide if I want to zipalign or not as I don't like zipalign scripts running silently via init.d without any information wether they work ok or not.

Zipaligning means aligning app-,system- or even framework-packages (*.apk or *.jar) to certain memory boundaries which results in better performance when actually using/starting those packages.

The three options are for packages in /data/app (your installed apps), /system/app (files mostly coming with your ROM or by CWM zips) and in /system/framework (ROM or theme files). This has nothing to do with odexing as mentioned a few posts back, just optimizing a little bit.

While testing this with a 4.0.4 ROM I found e.g. most GApps to be not zipaligned. /data/app packages mostly are zipaligned as Google made this a requirement for providing apps via the market.

Hope I did not forget something...
[Galaxy S I9000 Android Development] ramas123:
Cool explanaition. Thanks!
[Galaxy S I9000 Android Development] scheichuwe:
NIce work :)
[Galaxy S I9000 Android Development] -Loom-:
My god ;) No one can say you're not devoted to what you do!

So, would it be possible to use BLN Pro, and not using your BLN service at all?

I mean, just like it was in the former kernels ?
[Galaxy S I9000 Android Development] mialwe:
Yes, I'll try to make the service optional via checkbox :)
[Galaxy S I9000 Android Development] muff99:
After flashing MNICS-139LR, my display initally was way darker than before ... changing the brightness in the ICS settings did not have any effect.

After Opening MidnightControl and hitting the "Toggle night mode" twice (so activating and deactivating it again), I got my original brightness back and can now use the settings to change it. I'm not using auto brightness.
[Galaxy S I9000 Android Development] mialwe:
Thanks. The explanation is located 5 posts before yours :)

You did exactely the right thing by toggling nightmode.
[Galaxy S I9000 Android Development] mialwe:
141LR - 2012/04/08

- app: added missed call service toggle (reboot required)

- app: updated help file

- initramfs: fixed issues with some busyboxes/$PATH (SlimICS, grep not found)

BLN + service activated: LED for missed calls + usual notifications (GMail,...)

BLN activated, service disabled: LED only for usual notifications

service activated, BLN disabled: service is running in background but LED will not be enabled.
[Galaxy S I9000 Android Development] -Loom-:
Perfect! Thank you very much!

Get yourself a beer: 8WA96075DU228704J

You really sure keeping that new name ? MNICS ....

What about 'Midnice" ? Best of both worlds ... ; )
[Galaxy S I9000 Android Development] mialwe:
Thank you very much :)

About the name - names change... no, I'm not sure. But for now it will be MNICS, it's still Midnight-ICS but shortened.
[Galaxy S I9000 Android Development] test123456789012:
Thanks so much for all your efforts!

Here's your Almdudler: 36N762838D8572347

Enjoy! :)

Nein, ich schlafe auch nie.. :)
[Galaxy S I9000 Android Development] -Loom-:
Impossible to spell ; ) Sounds like "Nix"

Looks like the kernel is close to perfection, if we're already discussing the name ;)
[Galaxy S I9000 Android Development] mialwe:
Yep. But easier to write in posts, PM, mail... :)

Good night everybody - and thank you, too, test123456789012.
[Galaxy S I9000 Android Development] exjc1986:
Hi first of all thanks a lot for a great kernel, this is the best i've ever used and the bigmem version is the icing on the cake... :)

I'm having a small issue with this kernel, whenever the screen backlight times out, it goes off with green color, the entire screen is green and its really annoying, I used to have this problem with GB kernels and setting the Min brightness value to 20 in Advanced Brightness settings used to fix it.

I can't find similar settings in ICS roms and changing the min brightness from Midnight control does not help!!

I wasn't getting any such issue with version 0.9.0.2.

Sorry if this has been asked already, but can someone please tell me how to fix this.
[Galaxy S I9000 Android Development] mialwe:
What are your gamma, rgb and min_brightness settings in MidnightControl? Green usually is a sign for low gamma + low brighness, that's why I'm asking. The only thing changed (for brightness) is that I have completely removed a formula which was capable to lower brighness depending on a multiplier.

Now its just nightmode=on (brightness=1) or nightmode=off (min_brightness, not lower, rest auto or manual or custom by ROM or...)

What if you reset all defaults (= gamma and RGB all 0)+ set min_brightness to 20, does this still appear?
[Galaxy S I9000 Android Development] exjc1986:
Currently I have

Nightmode: Off

Min Brightness: 20

All other multipliers are set to 0 including Gamma level

Edit: Changed Gamma to -10 and its not happening anymore
[Galaxy S I9000 Android Development] mialwe:
Just tested, no issues with those values. Now there are some options to test:

1) push the "reset to defaults" preference in color settings of MidnightControl, retest.

2) ensure "set at boot" in MidnightControl color settings is *un*checked, reboot, test for the issue without entering MidnightControl.

3) Clear MidnightControl data, reboot and retest.

4) Send me a Logcat containing the messages with the tag MIDNIGHT, they will show if MidnightControl sets other values than the ones you specified (I doubt it, but maybe it helps us to debug this).

To prove there has not been changed anything else, here is the commit. If bmult!=0 (MidnightControl nightmode toggle sets this to 1) nightmode is used, in all other cases normal brightness (even user defined min_brightness is not used, found a bug here :), its using just the brightness as reported without altering it. ).

EDIT: I build another version with the missing check if brightness < min_brightness or brightness > brightness_orig and send you a PM with the link if the other options did not work.
[Galaxy S I9000 Android Development] MagicOnline:
is overclocking gone?? just updated from 0.9.0-2.

edit: found the toggle in cwm. would love to have it back in the app.

bug? other thing is that after a reboot the auto brightness is not working. need to toggle dark mode on and off in midnight app. anyone else?
[Galaxy S I9000 Android Development] mialwe:
Please read changelog if you are installing things, no matter if its a kernel or something else. Overclocking is limited to 1.128Ghz, 1.128Ghz then replace 1Ghz step and the switch has been moved to CWM.

@exjc1986: PM out.