yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] BlueFlame4:
This kernel is the most awesome kernel ever :) Thanks a lot! <3 I finally fixed the 720p recording problem :)

-> Much more RAM + HD recording = awesome :) Have a nice day and happy easter! ;)

[x] donated 5 bucks :)
[Galaxy S I9000 Android Development] boarder.2k9:
Thanks for reply, have tested for rogue apps there is none. Normal battery stats says android OS 70% and phone is awake on off constantly (screen is off and wifi is off). Betterbatterystats says partial lock greatest is tasker at 12minutes but kernel lock is 100% with no reference and all the extra info: 1. Cpuspy shows no deepsleep.

This is totally wierd.

Extra info: 143LR, AOKP milestone 4, OC 1138Mhz, no UV, init.d enabled (but no scripts)

I have just disabled init.d in CWM, will see if that has any effect..

Will keep investigating...

---------- Post added at 03:23 PM ---------- Previous post was at 03:17 PM ----------

Phone has started to deep sleep after disabling init.d!

Weird but awesome. working at it should now.

Thanks for your help. Love the kernel
[Galaxy S I9000 Android Development] mialwe:
Naaaah, don't stop here, please! Now what exactely *is* in your init.d? Feel free to post the filenames or file contents. At least /data/user.log, please :)

I'm really interested in what was causing this for you althought I'm glad everything works now.

@craigb244 : Prepared changelog in post #2 for next release...
[Galaxy S I9000 Android Development] boarder.2k9:
I could not attach my user.log but have copied the contents to pastebin:

http://pastebin.com/MZK7KBRB

I have attached the init.d scripts in a zip file.

Hope this is some help.

(I have to admit in no developer so I don't really have a clue about the stuff but if you tell me what you need I will try to help)

Edit: Just to confirm deep sleep is definitely working now. Shall i re-enable init.d in CWM and post user.log?
[Galaxy S I9000 Android Development] mialwe:
No, don't spend too much time in this, thank you for the files. user.log after activating init.d would give you some hints if the scripts are working ok if you are interested. I don't think the screenstate scaling script is required and I suspect this one to be the cause of your issue but I'm not sure after quickly looking over the scripts (+ it changes tweaks already tweaked by Midnight itself).
[Galaxy S I9000 Android Development] rulala:
I have a question

zipalign packages /system/app

zipalign packages /system/framework

zipalign packages /data/app

If I do them all , my rom will be more smooth than I don't do ?

Or this option is not necessary to do ?

Because my inverted app like Talk will disappear by do them

sorry my very bad english:p
[Galaxy S I9000 Android Development] mialwe:
All zipalign options are optional and they maybe slightly increase performance and reduce memory footprint for the zipaligned apps (Google quote):

Some customized packages don't work when zipaligned, I read some thread where the dev informed users to not zipalign his package, sadly I don't remember which thread this was.

The advantage of having these option in CWM is that we can trigger the zipaligning when we want it and don't have to use a script every reboot which does not give any information wether it worked or not.

So when zipaligning be sure to have a backup or the option to reinstall the packages having issues after zipaligning (CWM zip or similar), just to be prepared.

Packages from Play Store usually already are zipaligned as this is a Google requirement as far as I know. I found the downloadable GApps CWM packages to be not zipaligned (and working after zipaligning).

More information:

http://developer.android.com/guide/developing/tools/zipalign.html

http://www.addictivetips.com/mobile/what-is-zipalign-in-android-and-how-it-works-complete-guide/
[Galaxy S I9000 Android Development] Rootax:
No voodoo color with this kernel right ?
[Galaxy S I9000 Android Development] mialwe:
All ICS kernels use the same driver base as Supercurio did with voodoo color. Some calculations are changed but you can adjust RGB and sometimes (?) gamma values.

Midnight:

- adjustable RGB values within a certain range

- adjustable (unified, 1 slider for all RGB-) -gamma within a certain range

This way users can adjust color tints and lower gamma without running into green-screen-issues.
[Galaxy S I9000 Android Development] BlueFlame4:
Battery Life Extender would make this kernel perfect :)

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

Best Regards!
[Galaxy S I9000 Android Development] mialwe:
Hm, not sure about this. Maybe.

Thanks for your donation :) I really appreciate it. Thank you.
[Galaxy S I9000 Android Development] rulala:
thanks very much

I think I know What I should do.:)
[Galaxy S I9000 Android Development] Netmatrix:
Check touchwake timeout, set anything else than 0.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] MortenJ:
I have a very strange problem on my phone, and I think it has something to do with the kernel. Sometimes when I turn the screen on the brightness is very low and I can't change it when I try to use the brightness slider in statusbar. I have to go to MidnightControl and turn night mode on and off before the brightness level is the one displayed in statusbar.

MidnightControl is default settings.
[Galaxy S I9000 Android Development] mialwe:
This has been fixed with latest version, in case you already updated please try to clear dalvik-cache, wipe MidnightControl data and/or reinstall latest MNICS.

tapatalked...
[Galaxy S I9000 Android Development] BlueFlame4:
Is it normal that the CPU won't clock itself below 800 MHz while the screen is on (even if I don't do anything)? Using conservative governor. After a while it should go down to 400 MHz or am I wrong?
[Galaxy S I9000 Android Development] 2k4ever:
it definitely isn't normal

the CPU should clock down to 100MHz if the screen is just on and the GPU isn't used

you say you aren't doing anything, so i suppose you are on the homescreen and if you are using a live wallpaper, thats most likely the thing keeping the CPU working at a high frequency
[Galaxy S I9000 Android Development] sugar 7:
sorry to disturb but where is the link for DL 0.7.9 in OP ?

Thanks
[Galaxy S I9000 Android Development] h O r n:
I got a weird problem after installing the kernel.

Yesterday I installed INFINITUM rom which includes your kernel. Today, I downloaded the last version of your kernel (LR), copied it to the internal storage, restarted into recovery mode and installed it.

Afterward, I chose the 'Reboot phone' option and it showed a screen: "GALAXY S KERNEL LOADING..."

Everything is fine until here. But then, instead of loading the rom, it restarted the phone into this KERNAL LOADING screen again, and now it keeps restarting it self again and again.

I tried removing the battery and put it back, didn't help. Also tried restarting into recovery mode, doesn't work as well. It just loads the KERNEL LOADING screen.

Any suggestions?
[Galaxy S I9000 Android Development] BlueFlame4:
Try wiping davik cache and cache partition and re-flash the kernel.

@2k4ever: Found my problem, some app was running crazy in the background... Thanks for the answer! :)
[Galaxy S I9000 Android Development] karol1981:
look at this

http://xdaforums.com/showthread.php?p=24094311

Flash this file with odin,then you will back cwm,sorry for my english :-)

Wysłano z GT-I9000
[Galaxy S I9000 Android Development] mialwe:
It has been removed as I can only give support for latest kernel version, sorry.

Glad you found the issue and it was not MNICS :)

Cache wiping is not an option as he does not reach recovery:

Bootloops usually appear with overclocking or too aggressive undervolting, in this case you would reach recovery after pressing the 3 keys long enough so I don't think this is your problem (correct me if I'm wrong here).

Another reason for bootloops are misbehaving init.d scripts (you have three of them - downloaded your ROM and took a look - those scripts caused issues for another user a few pages back, no deep sleep if I remember right - deactivating init.d solved the issue) - but you would be able to reach recovery.

As you are *not* able to reach recovery which I read from other users on various kernel threads, too, but first time here - I think something went wrong during the kernel flash itself. So you have some options here:

- flash the recovery fix kernel as posted above (never tried myself)

- use Heimdall (recommended, never failed for me, never used Odin) to flash the boot.img (conatined in all kernel install ZIPs for ICS, it's the kernel itself without modules): Via commandline just use

heimdall flash --kernel boot.img

in donwload mode, usb connected. This will flash the boot.img of the kernel of your choice, you will be able to enter recovery and e.g. clear init.d, deactivate overclocking,...

As soon as you are in recovery remember to flash a full kernel CWM zip first and reboot to recovery again to do the other stuff, otherwise you would try to boot with an incomplete kernel as the other contents of the kernel CWM zip are missing after flashing a boot.img only.

- if you decide to try MNICS again please re-download the ZIP, maybe it was corrupted somehow during download.

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

@all: If the ROM of your choice uses init.d scripts be sure you know *what* those scripts do - some of those ROM init.d scripts caused deep sleep issues or bootloops, at best they just overwrite your desired read_ahead values or already optimized kernel settings without information - I don't know if ROMs including MNICS or older versions have init.d enabled by default but be sure you know what they do or ask your ROM dev.

MNICS is tested on 4.0.4 ROMs without integrated init.d scripts, in fact I never needed any init.d scripts as the kernel (as most (all?) other kernels, too) already includes some useful tweaks which usually get overwritten via init.d scripts. Cant speak for scripts with other purpose than tweaking as I never used them.

I'm thinking about removing init.d support.
[Galaxy S I9000 Android Development] doc_2nas:
Please don't remove init.d support, but maybe you can remove the user interface for init.d from midnight app and set the default to disable init.d. So only experienced users can enable init.d support through terminal. Just a suggestion :)

Sorry OT but can't hold myself to say this: I'm so glad to have a SGS since the devs are very smart, nice, kind, and communicative. Thank you all and especially you Mialwe.... Super job :thumbup:
[Galaxy S I9000 Android Development] mialwe:
But this would enable ROM devs to include everything they want, not notifying users and users would have no option to disable init.d. It already *is* disabled by default :(
[Galaxy S I9000 Android Development] doc_2nas:
What about derteufel's approach by putting a script that remove any scripts in init.d to other folder when flashing the kernel? I guess the problem is gung-ho users who never read before flashing, and blame the dev if anything goes wrong....so sad... :o

But the decision is yours and I will follow whatever path you take :)
[Galaxy S I9000 Android Development] lippol94:
Totally agree man :)

Although I'm positive with using scripts in my roms I never forgot to mention what they would have affected.

Your strong decition is educative and avoid many problems with users:

- Do you have any bug?

- Yes

- Have you enabled init.d support?

- Yes

- Then disable it!

- But...

- NEXT!

:D

I hope in a better ROM quality from now onwards :)
[Galaxy S I9000 Android Development] malcho:
I agree with mialwe.init.d should be disable by default.

Like in linux most of the things are forbidden until you give them access or permissions.

But don't remove init.d let it stay disabled.

Good job let us take control of our phones:)
[Galaxy S I9000 Android Development] mialwe:
No, "NEXT" would not be my answer unless the issue is fixed :)

I cannot test all the init.d scripts out there to give proper advice about them but before calling "NEXT" I prefer to help as much as possible.

Edit: removed a lot of ranting about init.d scripts...,sorry.
[Galaxy S I9000 Android Development] -Loom-:
Very interesting read, again ;)

I like the way you provide some technical background. As for me, I like to know how things work. Long way to go with Linux, but always curious.

---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------

I tried that once and ended up in a stone-aged CWM 2.x

If flashing has to be done with Ordin, better flash Midnight GB kernel, which comes as a .tar package.

From this point, I was always able to flash an ICS kernel.

But in the meantime I had experienced all kinds of bootloops. No beeing able too boot, not beeing able to enter CWM, and a few weeks ago I managed to get a CWM loop. Whatever I did, I wasn't able to boot a ROM. It always reverted back to CWM. In the end I had to flash stock, then cf-root, then ICS.

And I never did overclock nor undervolt. Maybe a little to agressive kernel switching. But it's comforting knowing there's always a way back into CWM and nandroid.

@Mialwe: Mind providing a litle detail about the partition structure in Android? I know there's recovery, boot, modem, system, data, cache ... I mean, during an Nandroid backup, when 'Recovery' and 'Boot' is restored, wouldn't that kick CWM? On which partition does it reside? Or is there some technical documentation avaible? As I said, I like to know what and why I do something ; )
[Galaxy S I9000 Android Development] rulala:
Many people can't use the /datadata/ low storage notification lagless fix - init.d script if you remove init.d support ?

People maybe don't need any tweaks ,

but that script is very important for people who need to install a lots of apps.

It's my thought. thank you very much.

:)
[Galaxy S I9000 Android Development] mialwe:
Thanks for your thoughts - but do we really *need* to install such a large amount of apps? Or do we install them because we can?
[Galaxy S I9000 Android Development] erpurohit:
Post the recent version, I am not able to use wifi tethering.

Any help?

Sent from my GT-I9000
[Galaxy S I9000 Android Development] mialwe:
Im answering your post via wifi hotspot @ Midnight 143LR. Works.

What I did was just enabling wifi hotspot, set new password, reconnect my laptop.

Did you get any error messages? Which ROM?
[Galaxy S I9000 Android Development] erpurohit:
Can you suggest what can be wrong as it was working fine before it?
[Galaxy S I9000 Android Development] mialwe:
Partitions (cat /proc/mtd, unsure what "reservoir" is...):

mtd0: 00780000 00040000 "boot"
mtd1: 00780000 00040000 "recovery"
mtd2: 0fa00000 00040000 "system"
mtd3: 01180000 00040000 "cache"
mtd4: 00c80000 00040000 "efs"
mtd5: 01000000 00040000 "radio"
mtd6: 0ac00000 00040000 "datadata"
mtd7: 00b00000 00040000 "reservoir"

During Nandroid backups CWM saves boot (kernel) and recovery (recovery), too. During restore it tries to restore those. If any of the backup images is corrupted it will fail which might result in loosing recovery, bootloops, lost data,...

BUT: I never experienced this. CWM does a checksum calculation right after backup and validates this checksum again before restoring. If there's something wrong CWM would not restore the backup.

If there are errors on the partitions itself CWM/Nandroid cannot detect this and backup/restore including those errors because the md5 checksum is calculated *after* backing up a faulty partition.
[Galaxy S I9000 Android Development] mialwe:
As I have no idea about your setup, configuration, apps/app updates, init.d scripts (sorry :) ), changes on your PC regarding connectivity,... no, sorry. I can't.

I don't even know *what* goes wrong as you did not answer my question.

One thing: I had a crude password for my AndroidAPN I did not know about - does your password match? Do you get error messages (again)? FC? Which ROM do you use (again)?

+ wifi code was never touched in the kernel sources.
[Galaxy S I9000 Android Development] rulala:
in fact, i don't need to install a lots of apps . I can control myself.:)

but I ever test to install about 70-80 apps and then low storage notification appears. game really needs more space to place.

The /datadata about 172mb is not enough for "most" people

Or , if we use the "script manager" to set the datafix script as root and as boot

It's the same with the init.d support , right ?

sorry my bad English :)
[Galaxy S I9000 Android Development] erpurohit:
Sorry I didn't saw your question earlier.

I am on slim 3.2 and i am not getting any error message. As I enable it, it activate and then immediately deactivate and there is nothing in init.d.

I have kept my androidapn open so anyone can connect it.

Hope I answered all your questions now.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] scheichuwe:
"reservoir" is required by bml_over_mtd tool

https://github.com/teamhacksung/sam...ung-3.0-ics/drivers/mtd/onenand/samsung_gsm.h
[Galaxy S I9000 Android Development] mialwe:
You are right with the games or large-data apps in general - I have to think about users needing those, too. Not sure about how script manager works, never used it. As ICS is not "stock" for SGS I cannot think about keeping the kernel without useful features like init.d, you are right. I'll test another idea I had, init.d will stay.

Did you see this one: http://xdaforums.com/showpost.php?p=24469371&postcount=4023 ?

I'll install Slim3.2 again and test this. Anyways nothing changed about wifi/accesspoint regarding MNICS, never touched those sources.

@scheichuwe: Thanks, never read about that partition :)
[Galaxy S I9000 Android Development] mialwe:
Posting this via Slim3.2 and AndroidAP wireless accesspoint. Works.
[Galaxy S I9000 Android Development] xtoad:
Confirmed. Slim 3.2 with both open and pw protected networks.
[Galaxy S I9000 Android Development] JohnstonF:
@mialwe

Any reason why this kernel has no boot splash?
[Galaxy S I9000 Android Development] mialwe:
It has one. "GalaxyS, kernel loading" :)

Midnight had a boot splash for some versions on Gingerbread which was removed because we don't really need it (visible for only 5 sec.) - I like to keep the boot splash clean and simple.

Maybe I'll replace it with the stock Samsung GalaxyS logo or the simple "Google" line, don't know.

Btw: Had no time to answer your PM, sorry. But there's no link attached?
[Galaxy S I9000 Android Development] Bubble-be:
*Puts up hand*

Can I make a suggestion ?

:p

I would vote for something different than standard, so you can see right away if the kernel updated successfully.
[Galaxy S I9000 Android Development] 2k4ever:
as mialwe stated, the kernle has a boot splash

if you can't see it, it could be that you are still on Froyo Bootloader

I at least couldn't see the boot splashes of ICS kernels in the beginning, when i hadn't updated my bootloader
[Galaxy S I9000 Android Development] mnazim:
Simple and effective... use the Google logo...
[Galaxy S I9000 Android Development] Vipitus:
+1 :D

Maybe the same Google logo as on stock Nexus S?

It will look amazing :)

Galaxy S - Tapatalk
[Galaxy S I9000 Android Development] csapdani:
I like the bootsplash very much, when I first saw it, I thought "Finally, not an overdesigned logo", and the small text is neat also.
[Galaxy S I9000 Android Development] JohnstonF:
http://www.flickr.com/photos/78961671@N06/7067382097/

the color blue seems to look weird though

looked fine on coreldraw.
[Galaxy S I9000 Android Development] kamalmawa:
does midnight ICS kernel runs little bit of UV by default ? I checked the Midnight control app it was already on the first UV setting.

Edit: Never mind figured it out that those values isn't applied until I click the "apply values now"
[Galaxy S I9000 Android Development] Bonvaz:
+1 google logo :D

this kernel is awesome...really,thanks thanks!!!
[Galaxy S I9000 Android Development] BlueFlame4:
Has anyone experienced a high CPU load caused by "surfaceflinger". I got no idea what this system app is for but it kicks my CPU to 100% quite often. Anybody else experiencing this?

Slim 3.2

Edit// Awwwww... Found out that it's the battery bar on top of the navigation bar... Removed it and there we go: 100 MHz in idle.

Thanks in advance!
[Galaxy S I9000 Android Development] mialwe:
Surfaceflinger belongs to your ROM, maybe posting this in the ROM thread would give you more information. Sorry I can't help here.
[Galaxy S I9000 Android Development] malcho:
mialwe,

What do you think about touchkeys on cwm?Very useful since we all flash alot:)

Many regards
[Galaxy S I9000 Android Development] TigerCourage:
I vote for the Google logo also! Looks amazingly simple and awesome!

Now that the JW4 kernel sources are out, do you think you are able to get even more usable RAM in your hugemem kernel? I am using it right now with the F4K patch and everything works perfect!
[Galaxy S I9000 Android Development] kryox:
+1 for google logo :)
[Galaxy S I9000 Android Development] powerdams:
I vote for the "with Google" logo.

@Mialwe:

Do you use high resolution timer hrtick in your great kernel ?
[Galaxy S I9000 Android Development] abalam:
I have flash devil semaphore glitch but must say every time I go back to mnics-143 excellent kernel, verry fast and stable. Tnx for the good work!!!

Print from my GT-I9250® using

CyanogenMod9.0.0-RC0
[Galaxy S I9000 Android Development] farid993:
+1

I hope so too.
[Galaxy S I9000 Android Development] encho:
Little quiet today, I guess noone has any problems. This kernel is rock stable and has everything I need.

OT: @mialwe what will be your next phone so I buy one, my contract expires soon :)
[Galaxy S I9000 Android Development] Spacemonkie4207:
Hay Kernel, Smooth and battery life.

I was playing around with the color settings in the Midnight control app when I clicked "set to default" my screen now gives a very yellow tint. Anyone else experience this?

Sent from my Galaxy S I9000

ROM: Slim ICS 3.3

KERNEL: mnics 143LR

MODEM: KG3
[Galaxy S I9000 Android Development] doc_2nas:
Yes, just lower the red and green setting from midnight app to your desired level, and leave the blue to default.
[Galaxy S I9000 Android Development] Spacemonkie4207:
I used both Galaxy S and midnight Control and looks good. Had too put red and green waaay down.

Sent from my Galaxy S I9000

ROM: Slim ICS 3.3

KERNEL: mnics 143LR

MODEM: KG3
[Galaxy S I9000 Android Development] Bonvaz:
Dev, we could wait a new version with source of jw4 kernel? Thanks,+1 google logo,this kernel is epic
[Galaxy S I9000 Android Development] mialwe:
MidnightControl uses absolute values starting from 4294967294 downwards for R,G and B, if you activate overriding ROM color settings it tries to set your values after the BOOT_COMPLETED trigger (Android boot completed), so MidnightControl Color settings are independant from ROM color settings. If one has a screen with "massive" color tint the colors have to be adjusted more than if one has a screen with slight color tint (e.g. I have to use -100,-250,0 and gamma -5 to get a real white white and nice colors).

Sorry, I don't think I have the time to look over the Gingerbread sources (personal reasons) for the next few weeks, I'd be glad to get ready and upload the current dev version. If ROM devs decide to use the new RAM settings (see CM9/pawtip) I'll adjust the MNICS-LR settings accordingly.

@all: I read in devil's thread that V6 Supercharger maybe does not work with Midnight's init.d implementation. If anyone has issues with this please upload the V6 init.d script, I'll take a look at it. Thank you.
[Galaxy S I9000 Android Development] lippol94:
IMHO it would be a right thing to uniform all kernels to the upstream changes.

https://github.com/teamhacksung/samsung-kernel-aries/commit/164a90a7cd4f7ed363a5b8e74d466186912d05a7

At least I would certainly use it :)
[Galaxy S I9000 Android Development] test123456789012:
I am under latest CM9 nightly. My "values don't match" after a reboot. Thank you for looking into it. Wasn't a biggie because your kernel is /that stable/ :) Here is the script: