yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Kagadar:
Two features that I would like to see implemented in this kernel before I consider it viable for day to day use are LiveOC and DeepIdle. If you configure your ROM to use DeepIdle properly (by modifying the framework) then there is a huge difference in battery consumption while listening to music. It probably uses about half as much. You won't notice a difference under any other circumstances.

LiveOC tends to be a hit and miss thing for me. I can use it up to 20% perfectly fine on Semaphore, but it has always EVENTUALLY crashed when its above 100% if I'm using Glitch. That extra 20% makes a really noticeable difference to performance, so it would be nice if you could get it working similarly to Semaphore.

Either way, nice work adding to the variety of ICS kernels available.
[Galaxy S I9000 Android Development] 2k4ever:
I just installed 0.9.0-2-HUGERAM together with the Bigmem Mod on ICSSGS RC4.2

its too early for a real feedback, but i wanted to let you know that my phone was overclocked to 1200Mhz by default

quite strange as the app was reporting 1200Mhz however in the max frequency menu 1000Mhz was selected

changing to max 800Mhz and than back to 1000Mhz fixed it for me

I think the night-mode toggle is a great feature but is there any way to toggle it via Tasker? e.g by changing a config file (where is the app storing its settings?)
[Galaxy S I9000 Android Development] mialwe:
But DIDLE will cause hundreds of didle-does-not-work-why posts which I just don't have the time to deal with. As I don't use DIDLE myself and work on Midnight in my little spare time this will not be implemented in the near future. Written in OP at first MIDNIGHT-ICS upload. DIDLE is interesting but for now I just don't have enough time and motivation for this, need more sleep. If I had to choose between implementing DIDLE and LiveOC I'd choose DIDLE. Maybe sometimes later.

LiveOC: Hit and miss - yes. No issues for me with old-school overclocking, just stable for me - for the same reasons as DIDLE I will not change that. Written in OP at first MIDNIGT-ICS upload.

Other kernels have LiveOC, Midnight has 7 frequencies + modified Smooth-Conservative governor. Just pick what you want.

There are at least 3 good kernels out there which have what you want. Midnight focuses on it's modified conservative governor, old-school-oc, all-in-one app to set your options (so it will work with stock-ROM-ports, too which don't have special menus for BLN, CPU etc, some specials like the nightmode and vibration intensity settings which other kernels don't have for now... and stability as I don't have a dev phone and have to use this 24/7. No more experiments. Only the things I need or find interesting. As ICS is really fast itself I even consider removing the 1.2Ghz step again and have only 1.128Ghz as extra OC step. Not sure yet.

This has been written several times within the last pages: The app option dialogs show the settings you have chosen. The app menus summaries (the text below the option title in menus) show the values currently used. If they differ something else interferes with the settings (ROM option menus, init.d scripts, other apps like NSTools). This has been implemented like this on purpose so users (and myself) can see if anything goes wrong - which worked just like it sould here for you. Something goes wrong and you noticed it.

The settings are stored in the app config file only, initramfs reads them from this file at /data/data/mialwe.midnight.control/... no separate configfile as it's unneeded. Just on single configfile used by all parts of Midnight.
[Galaxy S I9000 Android Development] cink40:
Agree with everything, just leave 1200 please ;)

sent from the Outer Space
[Galaxy S I9000 Android Development] giokspy:
Hugeram working fine on infinitum 1.10 with the pach and 720p ill working. In next version please change the kernel bootlogo :-)
[Galaxy S I9000 Android Development] lerkin:
I think bootlogo is excellent )

Strange, callvibrate fc after flashing that kernel. Behaves normally on slim 3.0 stock
[Galaxy S I9000 Android Development] lerkin:
Delete please
[Galaxy S I9000 Android Development] doc_2nas:
Yes,the boot logo is cool! Simple n Humble... so great
[Galaxy S I9000 Android Development] freaked9:
I just flashed the 720p patch, and the midnight hugemem kernel on WeUI 0.8.7. and i got a bootloop on kernel loading, can't even get to the recovery.. any ideas how get there?
[Galaxy S I9000 Android Development] mialwe:
Reason for FCs alwas is in Logcat, can you provide this?
[Galaxy S I9000 Android Development] lerkin:
Strange, after enabling logcat, everything works
[Galaxy S I9000 Android Development] ghul21:
Hello

Just flash the hudgeram kernel with patch onDark Knight V3, and so far everything works without a problem. Record 720 ok :D
[Galaxy S I9000 Android Development] mialwe:
Nice :)

I don't know "callvibrate" but maybe it relies on Logcat to detect things or something like that? It's rather unusual to rely on optional features like Logcat but I've read about some e.g. security apps which seem to get stuff from Logcat to work properly... anyways, good to hear it works fine for you now.
[Galaxy S I9000 Android Development] 2k4ever:
you are right, not a big problem but i think its a bug of your latest kernel and / or app as i came from RC4.2 (no ROM option) with stock kernel, no OC/UV, never installed NSTools and init.d support is deactivated
[Galaxy S I9000 Android Development] mialwe:
Ok, so could you help me finding it? What I need first is the /data/user.log from the boot that set your max. freq to 1.2Ghz (if you rebooted one time since this it's in /data/user.log.bak).

This would show what frequency is set by Midnight. The app later on changes maxfreq only if you tap the option.

Another option (after having rebooted more than one time in case you still use Midnight) to reproduce this would be:

1) delete MidnightControl data

2) flash stock kernel, boot

3) flash Midnight, boot

4) check value in MidnightControl

5) check/send /data/user.log

Tested on ICSSGS myself so this is strange, hopefully we can find out. Thanks for helping and reporting :)

EDIT: I tested on ICSSGS myself *after* doing some stuff to correct the issues with ICSSGS' busybox version (ICSSGS busybox has issues with some standard busybox commands ("[[", "]]") which are used to parse Midnights settings in the initramfs - maybe that's the problem here, too, I'll check /data/user.logs other ICSSGS users provided some days ago...

EDIT2: I don't have access to a ICSSGS user.log with stock settings, only a userlog sent to me with 1.2Ghz enabled, so you have to help me here pleas, just post the /data /user.log after deleting MidnightCOntrol data and rebooting once. Thank you very much.
[Galaxy S I9000 Android Development] 2k4ever:
of course i want to help you as best as i can, thats why i brought up the problem in the first place

i haven't rebooted since installing the kernel, so attached you will find the initial log

the busybox problem is there allright, but i also noticed that CPU max is set to 1200000

I'm clearing data and rebooting in order to provide you with the second log next

EDIT: max frequency is back to 1200 after the reboot without me even running MidnightCOntrol (checked with CPU Spy)

log attached as user2.txt
[Galaxy S I9000 Android Development] mialwe:
YESS - that's it. Thank you.

The ICSSGS busybox has issues with the standard command "[[", that's the cause of this:

#initialize cpu
uv100=0;uv200=0;uv400=0;uv800=0;uv1000=0;uv1128=0;uv1200=0;cpumax=1000000;
...
...
# set cpu max freq
echo; echo "cpu"
if $BB [[ "$cpumax" -eq 1200000 || "$cpumax" -eq 1128000 || "$cpumax" -eq 1000000 || "$cpumax" -eq 800000 || "$cpumax" -eq 400000 ]];then
echo "CPU: found vaild cpumax: <$cpumax>"
echo $cpumax > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
fi

This works fine on most ROMs' busyboxes and syntax is correct. What ICSSGS busybox does is this:

cpu
[[: missing ]]
/sbin/boot-patch.sh: line 107: 1000000: not found
/sbin/boot-patch.sh: line 107: 1000000: not found
/sbin/boot-patch.sh: line 107: 1000000: not found
/sbin/boot-patch.sh: line 107: 1000000: not found
[[: missing ]]
/sbin/boot-patch.sh: line 113: : Permission denied
/sbin/boot-patch.sh: line 113: : Permission denied
CPU: values after parsing: 0, 0, 0, 0, 0, 0, 0
max : 1200000
gov : conservative

It fails to execute the "/system/xbin/busybox [[" command correctly and sets the wrong maxfreq.

I'll prepare a kernel-zip which replaces the busybox with my self-compiled version from the patch-CM9-for-hugeram compile and upload ASAP (my 2-year old just woke up, may take some time, though).
[Galaxy S I9000 Android Development] 2k4ever:
thanks mialwe

and take your time, its not that big an issue and family comes first anyway
[Galaxy S I9000 Android Development] freaked9:
That could be good for me too, right? If im right, i had the same problem.
[Galaxy S I9000 Android Development] wonsky21:
How about implementing deep idle feature?
[Galaxy S I9000 Android Development] barome:
@ mialwe : have you see my post about init.d error ?

http://xdaforums.com/showpost.php?p=24284854&postcount=291
[Galaxy S I9000 Android Development] flip360:
READ a few pages back as to why not.
[Galaxy S I9000 Android Development] fishears:
0.9.0-2 bigmem working perfectly on Team Kang build 28 with the 720p recording patch :D
[Galaxy S I9000 Android Development] bhu1:
@mialwe silly face effects are crashing with huge ram kernel although video recording and playback is working . Is this is a known bug with HUGE ram kernel.
[Galaxy S I9000 Android Development] cink40:
No, it is a known bug on most (every?) ICS rom's.

sent from the Outer Space
[Galaxy S I9000 Android Development] muff99:
HUGERAM version working great with NRGs latest kan .. err "unofficial" (kangaroo thread http://xdaforums.com/showthread.php?p=24306059)
[Galaxy S I9000 Android Development] doc_2nas:
Hi Mialwe, while screen off + listening to music ( I use mort player) conservative governor use mostly 400MHz but ondemand governor use mostly 200MHz ( no OC/UV), is it intended? Thanks in advance. For now I mostly concern about battery life....
[Galaxy S I9000 Android Development] ramas123:
read a few posts up, will find your answer
[Galaxy S I9000 Android Development] ramas123:
My new favorite kernel with some unique settings. Very very nice work! Thanks!
[Galaxy S I9000 Android Development] saszseb:
aLogcat doesn't work.

http://pastebin.com/nVfCDtk4

Sent from EliteV9.0.
[Galaxy S I9000 Android Development] lerkin:
Try to enable it in midnight app.
[Galaxy S I9000 Android Development] freaked9:
Im having a kernel bootloop again.. it means: no cwm :/

I was just told an idea: flashing a cm7 initial kernel via odin is giving me cwm so i can install a kernel again and dont have to erase the whole phone.

Sadly after trying to install it again, its the same, now i have to start over, but this time i will install the normal version.

Something is really wrong with this hugeram version.
[Galaxy S I9000 Android Development] ramas123:
Well, cm7 and odin don't connect each other.
[Galaxy S I9000 Android Development] nmcc89:
Here's my user.log after putting your busybox in system/xbin. I'm not getting the errors from before so looks like you've fixed it! Is this something worth mentioning to the icssgs guys? Thanks!
[Galaxy S I9000 Android Development] 2k4ever:
thanks mialwe

the log seems fine to me now and your app reports 1000Mhz

however, for a short moment in the beginning the phone uses 1200Mhz nonetheless:

don't know if it was just this first time or whether its normal with your kernel, but i'll keep an eye out for it

EDIT: nmcc89, do you have CPU Spy? if so, please check whether your phone has used 1200Mhz as well, thanks
[Galaxy S I9000 Android Development] scheichuwe:
Here you are.
[Galaxy S I9000 Android Development] saszseb:
I've enabled it, but doesn't work.

Sent from EliteV9.0.
[Galaxy S I9000 Android Development] Trak-X:
Hey mialwe.

I am just trying the new version. For now it seems faster the the old one and i no longer have the wifi flickering issue that i had with 0.7.9.

I just installed the busybox version that you updated and will attach the log after reboot.

LE: it seems that after i updated the busybox version the midnight control app is no longer starting.
[Galaxy S I9000 Android Development] mialwe:
Nothing wrong, you have to flash Midnight via CWM as written in OP. You *could* extract boot.img from the script and flash via Heimdall (don't know about Odin, I do not use Windows) but you will loose e.g. the kernel modules included in the CWM zip.

Indeed, just checked this, Midnight uses 1.2Ghz for a few seconds at the start of the boot and then changes to the default or user defined frequency still at boot time in the initramfs as it should. I'l lsee if I can hardcode max. 1Ghz in the kernel so this does not happen. Great find, thank you for reporting this :)

As its just for a few seconds before initramfs execution this should not be a big issue, though. But I'll look into it.

I'm glad the busybox replacement works, I think team ICSSGS already has been notified.

@scheichuwe: Thanks for building the CWM zip :)
[Galaxy S I9000 Android Development] freaked9:
Read it again..

Finally i was able to start the system without formatting everything (trying out lots of variations).

mialwe: a friend did the same as me, installed the hugeram version and got a bootloop.

At the same time as me.

We both installed Galnet MIUI. Mybe the kernel is not fully compatible with MIUI.

The latest Galnet MIUI from is merged with the latest CM9 sources, maybe that can cause the problem?
[Galaxy S I9000 Android Development] saszseb:
If not, how can you flash a Sammy ROM?

Sent from EliteV9.0.
[Galaxy S I9000 Android Development] mialwe:
Did you reboot after enabling it? What this option does is this: Copy /system/lib/modules/logger.ko to /data/local/logger.ko.

Do you have /data/local/logger.ko *and* have rebooted so the kernel had the chance to load the module?

Edit: Just checked, aLogcat works fine here, logger.ko is loaded. Latest Midnight HUGERAM version.
[Galaxy S I9000 Android Development] mialwe:
Well, Odin connects to download mode, not CM7, 9 or anything else :)

@freaked9 Do you have a link to latest Galnet MIUI? Never used this, I dont know if Midnight is compatible. Do other kernels work? If yes, which kernels?
[Galaxy S I9000 Android Development] ramas123:
Download mode overrides any rom on your device
[Galaxy S I9000 Android Development] Trak-X:
Mialwe, any ideea?
[Galaxy S I9000 Android Development] freaked9:
Here you are: www.galnetmiui.co.uk/content/download/v4_roms/miuiscotland_I9000-2.4.1-V4.zip

changelog:

Updated in line with CM9 latest nightly

Kernel changed to CM9 latest

RIL corrected in line with CM9 latest

Updated to 4.0.4 ICS

Other small tweaks (Slimming rom)

Edit: i did another try with the kernel: its the same:/
[Galaxy S I9000 Android Development] saszseb:
http://pastebin.com/aFQZ6XUE

-yes, rebooted.

-logger.ko is in /data/local

Sent from EliteV9.0.
[Galaxy S I9000 Android Development] mialwe:
What exactely were your updating busybox steps?
[Galaxy S I9000 Android Development] nmcc89:
Yup just checked too and same thing, I opened cpuspy after rebooting and it showed about 20 s on 1.2 GHz (sorry, on tapatalk so uploading screens is a pain). I think it correlates with roughly the same amount of time the boot animation runs. Personally it's not a problem because 1.2 GHz has been rock solid for me and I keep changing between 1 and 1.2.
[Galaxy S I9000 Android Development] 2k4ever:
i agree that it isn't that important

however, at least theoretically it can cause bootloops / freezes if a particular phone can't handle 1.2Ghz - not very likely right now, but if you would implement 1.4Ghz OC or more, it really could become a problem

thanks for checking

this supports my point as 20 sec is rather long

have you set the right permissions for busybox?
[Galaxy S I9000 Android Development] Trak-X:
Thanks. I was able to do it. It seems the first time i updated the file, permissions were not properly saved. I had to do it again.

Now it is fine. Init.d scripts are ok.

Later Edit: Btw .. touchwake is still not working. Same issue with Devil, although on Devil it worked after setting timeout on 0 for touchwake
[Galaxy S I9000 Android Development] ramas123:
Yeah, old school 1,2 OC is tha best, mean, beast :)
[Galaxy S I9000 Android Development] mialwe:
Touchwake works fine here, using it all day. Everyday. Different ROMs. SGS has to sleep once and wake up via button, from then touchwake works fine for me. No other reports about TW not working until now.

@saszseb: Stranke as it's working for me and others and all needed is in initramfs. Can you check the following:

1) again, uncheck Logcat in MidnightControl

2) check if /data/local/logger.ko is gone now

3) check it again

4) make sure /data/local/logger.ko is there (should be the one from Midnight now for sure, important)

5) reboot

=>

6) check "lsmod" output (ADB or terminal if you have one available)

7) check aLogcat

8) check "ENABLED" or "DISABLED" in MidnightControl

I hope we will find out what causes this for you :)
[Galaxy S I9000 Android Development] saszseb:
lsmod:

$ lsmod

logger 1052516 52 [permanent], Live 0xbf000000 (PC)

Sent from EliteV9.0.
[Galaxy S I9000 Android Development] mialwe:
So logger.ko is successfully loaded.
[Galaxy S I9000 Android Development] saszseb:
Yes. and now what to do?

Sent from EliteV9.0.
[Galaxy S I9000 Android Development] mialwe:
The kernel has done it's job.

The aLogcat app still does not show anything? Do you have ADB in your PC? If yes, what does "adb logcat" show?
[Galaxy S I9000 Android Development] saszseb:
No.

I can check it tomorrow evening.

Sent from Slim_ICS_2.8
[Galaxy S I9000 Android Development] baba420:
Is the night mode completely safe to use? Or is it like the app screen filter?

Verstuurd van mijn GT-I9000 met Tapatalk
[Galaxy S I9000 Android Development] s3icc0:
Never had your kernel before on GB or even ICS, but during last few days I give it a go with AOKP and now CM9 and with CM9 use your HUGERAM version ... and I must say this is the best SGS I ever have.

Thanks
[Galaxy S I9000 Android Development] mialwe:
What do you mean writing "safe"? How is the screenfilte app "not safe"?

To answer you question: The night mode

- directly lowers the allowed min brightness to minimum and

- adjusts internal brightness values to reach that new minimum brightness

=> really dark screen, no overlay.

Just to prepare myself for heat and inform you before next version: Next Midnight will come without overclocking (undervolting: yes). I never "felt good" with OC and think about removing this for a few months now (started with Midnight-GB) - now it's done. I know some users will not like this but

1) OC really might be the reason for some bootloops users were experiencing (was able to reproduce them yesterday night)

2) I was not able to limit maxfreq at boot time to 1Ghz (worked fine in GB), tried different approaches in cpufreq drivers and governors, seems the 7 frequencies cause this issue - kernel *always* starts booting with 1.2Ghz for 2-22sec. I was able to limit it to 1Ghz but after this we would not be able to change freqs again - nonsense.

3) Most important: 1Ghz+ICS is fast. Fast enough for me at least. All other custom kernels out there support OC so everybody has the choice.

4) Better battery, better stability, less reboot/instability reports (weren't many).

Please don't hate me :)
[Galaxy S I9000 Android Development] xtoad:
I agree with you. I never use OC either.

But... You are right, the heat will come. ;)
[Galaxy S I9000 Android Development] kryox:
i had reboots with almost every kernel i used oc.. so remove it :)
[Galaxy S I9000 Android Development] doc_2nas:
Hi Mialwe, after upgrade to Slim 3.1 I got 200Mhz most on conservative while listening to music + screen off. So I guess your setting is okay. So sorry for bothering you. Thank you..... :)

Edit: found the culprit, it's the equalizer in mort player...
[Galaxy S I9000 Android Development] 2k4ever:
I'm also in favor of removing OC altogether

there is a reason why hardcore never implemented it: even if you don't OC, the changes necessary to the kernel cause instability

on the same note, I personally would also suggest to remove UV completely
[Galaxy S I9000 Android Development] mucinch:
I don't OC but I under-clock it to 800mHz sometimes when I need the battery. Anyways, thanks for the awesome kernel.
[Galaxy S I9000 Android Development] cink40:
I really do not hate you :D, i will just not use your kernel anymore, it is enough kernels out there (ok yours is the best me thinks :() . Anyway thank you for your work and thank you for sharing your work. Goodbye

(i will check your thread nevertheless, maybe you will come around ;))
[Galaxy S I9000 Android Development] s3icc0:
100% agree with you ... OC is something normal user dont need (and that was what your kernel used to be about) and of course there are better kernels for OC.

Better to have stable kernel. Rather to work on RAM optimizations.

---------- Post added at 04:50 PM ---------- Previous post was at 04:48 PM ----------

and does it help? .. i dont think so ... better to calculate something on higher ffreq for lesser time than heat the phone with 800MHz for an hour.
[Galaxy S I9000 Android Development] mucinch:
I am not technically qualified to refute your statement, but please look at the first post of this thread:

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

also, I am not talking about Deep-idle (2nd graph) or gaming on 800mHz, for average use (calls, messages, twitter) 800mHz is more than enough.

---------- Post added at 08:53 PM ---------- Previous post was at 08:40 PM ----------

I am not saying Mialwe should not remove OC or UV, I was just stating my use-case. Will I still use Midnight kernel without OC/UV? definitely will!
[Galaxy S I9000 Android Development] doc_2nas:
Maybe we should focus more on battery life from now on..... :D

I like it.... :D
[Galaxy S I9000 Android Development] Netmatrix:
+1, and keep undervolt, rock stable...

Sent from my GT-I9000
[Galaxy S I9000 Android Development] saszseb:
- adb logcat didn't work on my Linux.

- I restored my Slim_3.1 and flashed Midnight over stock kernel and aLogcat has been working since enabling logcat.

- it must be a ROM related issue.

Sent from Slim_ICS_2.8
[Galaxy S I9000 Android Development] mialwe:
Thanks saszseb for reporting this back, I'm glad it now works for you.

@all: I'm surprised, did not expect so many users liking the no-more-overclocking-idea :)
[Galaxy S I9000 Android Development] scheichuwe:
I don't like it :)
[Galaxy S I9000 Android Development] yaatzek:
Mialwe, with Your kernel i know for sure that oc is worthless. Everything is so smooth, and i never thought it can be that smooth on conservative. Your kernel is totally complete for me.
[Galaxy S I9000 Android Development] malcho:
I also use this kernel without oc.

Works really great.
[Galaxy S I9000 Android Development] switchgott:
Hi,

Thanks again For this great kernel.But please,Tel US,can we use droidwall with this Kernel?

Thanks

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] mialwe:
Droidwall should work fine.
[Galaxy S I9000 Android Development] switchgott:
Big thanks master .-)
[Galaxy S I9000 Android Development] Mr.AFK:
Hi mialwe,

1 more reason to take a look at ICS :)
[Galaxy S I9000 Android Development] saszseb:
What should it be?

Sent from Slim_ICS_2.9, MIDNIGHT-ICS-0.7.4
[Galaxy S I9000 Android Development] dark_knight35:
This kernel :rolleyes:
[Galaxy S I9000 Android Development] bhu1:
there is a reason why i used to think mialwe was the black horse with midnight gb and now this, seems like u will no longer be the dark horse. ;)
[Galaxy S I9000 Android Development] dark_knight35:
Is it right that we have 4 ics kernels and only one gb kernel more and all the kernel devs work on theire ics kernels? This shows how bad gb is.