yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] bhu1:
Mialwe don't stop the project. I was just thinking some days ago to make two versions of my rom , one for those who change or upgrade to new roms in months with midnight kernel and less bloats as those people don't generally touch settings and just want everything working from the go when they flash a rom, basically a liter and battery hero version of the rom for noobs. And the regular semaphore version for power users. But that won't be possible without your support. Pls try to take out some time by ditching some not so important small things and pls keep the kernel up and running and keep making it better.
[Galaxy S I9000 Android Development] mialwe:
Thank you all for your answers, I appreciate it.

-IK-, no, I did not think you were criticising but after thinking about this you definately have a point with the bootlogo - it's already removed in 0.8.6 dev version.

I'm thinking about stopping Midnight developement every few weeks, basically because the spare time I have often changes from 1 or 1,5 hours per day to 10 minutes/day or even no time for some more days - but until now I always continued because of the time already spent, because I enjoy working on Midnight (ok, *most* of the time), the communication here and at another board - and I do not want to disappoint the users actually using the kernel.

With attempts to get 1.3Ghz working (stable), CWM>=3 (this one took me 2 months of work) , Ext4 conversion (never got it to work properly for /system),... developement went from the initial idea more to an user-ideas-driven developement and somehow I lost track in this time.

Probably I won't stop/freeze Midnight but I'll try to give it the right direction again and implement some (2) features I'm personally still misssing. After this I'll keep Midnight updated for new initramfs/firmwares but there will not be "big" new features besides some minor tweaking/optimizing.

To give you an idea about Midnight 0.8.6:

- stock bootlogo (done)

- zipalign via CWM (done)

- 342Mb RAM, testing (/w front cam working (at least JW1)) (done)

- removed some more debug stuff (done)

- big CWM cleanup (done)

- reworked LMK presets (default starts working @65Mb now)

- bugfixed HOME_APP_ADJ (back to "1" again)

- backup/restore /data/app via CWM (restore untested but done)

- Nexus tl2796 driver + brightness/rgb adjustment options based on Supercurios great work (but not 100% voodoo color, fixed gamma, only rgb control for tuning color tint and 6 levels to adjust lower brightness from bright to dark) (done)

- MidnightControl app (95% done)

- completely reworked initramfs scripts for MidnightControl (I want users to be able to overwrite every setting via init.d if needed so app settings have to be applied *before* init.d scripts get executed) (done)

- EDIT: JVU modules (done)

That's what I was working on for the last weeks. With brightness level control (wrote about it a few months ago) and the app (these are the two features I mentioned) Midnight feels somehow "complete" to me.

Before uploading this I have to implement a few still missing options to the app, test it (and maybe clean up some parts as this is my first app and I'm still learning).
[Galaxy S I9000 Android Development] bhu1:
Just 1300mhz and ext4 conversion back and forth, and this kernel will be perfect . ;)
[Galaxy S I9000 Android Development] krosscheck:
Hi mialwe,

if midnight is complete to you, than it is complete for me too.

Do it for you, do your thing, i'm happy if i can continue to use your kernel.

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] Тhe Dark Knight:
Hi Mialwe. When approximately you'll upload new version?

Thanks again for the best kernel ;)

P.S. i like your kernel logo very much.
[Galaxy S I9000 Android Development] mialwe:
I have learned not to write about release dates - everytime something goes wrong.

But I'm thinking of uploading a beta, maybe this week... had to reconstruct complete source yesterday night after experimenting with some kernel debug options so everything is a little bit delayed once again.

Current state:

- features like in last post

- disabled more kernel debug stuff

- minor work/adjustments on Midnight control app

- removed 1.2Ghz step. Back to the roots for Midnight.

Todo:

- implement a few app ideas
[Galaxy S I9000 Android Development] bhu1:
Rfs to ext4 ?? And back to rfs ?? I really wanna use your kernel in my rom just this is the issue as the users of the rom will bug me if this won't work .
[Galaxy S I9000 Android Development] mialwe:
Sorry but no. Not now because of not enough time. I tried implementing a new conversion "engine" for MN0.8.4 for weeks and it just did not work (different issues with initramfs intercepting, graphsh, Samsungs fat.format binary,... lost partitions multiple times). And RFS isn't *that* bad anymore :)

As I have written 3 days ago:

Midnight runs on RFS and EXT4 but you'll have to use another kernel or MN0.7.6 to *convert* if neccessary.
[Galaxy S I9000 Android Development] bhu1:
I know its not at all necessary but its very difficult to make this understand to all noobs . :( they will just look for the famous ext4. :(
[Galaxy S I9000 Android Development] Тhe Dark Knight:
what does this mean?
[Galaxy S I9000 Android Development] krosscheck:
Now u can overclock to 1,2 ghz. With next version not more.

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] Тhe Dark Knight:
So there will be 1.3 instead of 1.2?
[Galaxy S I9000 Android Development] mialwe:
No, sorry. Frequencies will be reduced to the stock ones. I was never happy with OC and did not want to include it in the beginning of Midnight developement, only undervolting.

Edit: I did a lot of experiments with 1.2Ghz, 1.3Ghz, 5 frequencies, 6 frequencies, arm- and internal voltages but was never satisfied and never felt "good" using this.

As I'm trying to bring Midnight back to the originally intended direction OC capability has been consequently removed. I know not all users will like this step but there are good kernels out there supporting OC. Sorry to disappoint you.
[Galaxy S I9000 Android Development] GoThere123:
Hi Mialwe,

Long time not visiting this site, i have just updated my kernel (midnight also) to your latest version 0.8.4 and all works really great.

Thanks a lot for your hard work and keep up the good work :-)

But may i ask why you want to remove 1.2 Ghz in the next version?

I just feels awkward when this runs well and you want to remove it.

But anyway this is just my opinion, just do what you think best :-)
[Galaxy S I9000 Android Development] Sw2rT1:
Hello Mialwe,

Why you removed the "Delete a lot of bloat/software (~52Mb)" option?

As for me, this is a very remarkable feature. Always enjoyed it after I reinstall new rom.

Thx.
[Galaxy S I9000 Android Development] mialwe:
@GoThere123: It's hard to explain and a personal decision about kernel "direction" and/or aims - please read my last post again as I don't have a better explanation, sorry.

@Sw2rT1: You mean this commit? Midnight/CWM got too bloated, did not like this. So I'm currently removing a lot of stuff (from kernel, initramfs and CWM).

The "remove-a-lot-of-bloat (52Mb)" option can be replaced using the other 7 cleanup options. BUT: I'm missing this option myself already :) as it really speeds up the bloat removal after a fresh ROM install, maybe it will come back.
[Galaxy S I9000 Android Development] RooceeD:
Thank you mialwe!

with your kernal I'm able now to play any game without lags. I had Galaxian kernel before, but this kernel is much faster!
[Galaxy S I9000 Android Development] stanbel:
mialwe, which ThunderBolt's scripts you can recommend to your kernel?

I found a small bug: no sound after phone is fully charged

And my launcher (Go launcher) often restarts after usage of other application,

can you give any recommendations?
[Galaxy S I9000 Android Development] -freedroid-:
@mialwe

What do you think about adding interactive governor to your kernel?

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] pikachu01:
Some aspects of ThunderBolt! are already in Midnight, but you can use all the scripts without problems :)

The sound after fully charged was removed quite some time ago (even in stock ROMs).

The launcher restarting is a feature. It's so that your apps in the foreground have the memory it needs.
[Galaxy S I9000 Android Development] mialwe:
@freedroid: No, sorry. For details please see this post (minus the Nexus driver part, experimenting with stock driver again, that's why I'm holding back the beta I intended to upload).

@pikachu01: Thanks for clarifying. HOME_APP_ADJ=1 got lost during some Midnight initramfs update a few weeks ago. BUT as you said - this can be bug *and* feature :) depends on usage. Maybe I should make this one user configurable...

Thunderbolt/any other init.d scripts: Midnight applies its own settings/tweaks *before* init.d scripts get executed to give users the choice to change anything they want via init.d. Just take care the init.d scripts you use don't overwrite Midnight/CWM settings *you* selected to avoid confusion.
[Galaxy S I9000 Android Development] GoThere123:
No Problems.

Your kernel still the best for me hehe..

Thank you :)
[Galaxy S I9000 Android Development] stanbel:
After 3 or 4 days of usage phone often become very laggy, is in possible to determinate what is the reason, may be memory leaks in the kernel?

Built in Task Manager says about RAM status: ~285/341MB
[Galaxy S I9000 Android Development] mialwe:
Is this when the SGS is laggy or is it a 'normal use' value?

Lags after a few days of usage always make me think about lowmemorykiller and/or VM/cache, that's why I ask.

Some more questions:

- are there *any* scripts running (e.g. via init.d)

- how many apps/widgets are running at the same time when lags start?

- if those RAM values are not during lag period can you post them again when you experience the lags?

- which filesystem/ROM are you using?

I'll try to reproduce and look into this (maybe lmk or VM issue, maybe I should readd an older screenstate-scaling script which utilized drop_caches to free some memory) this but I'm not sure if I can - usually I have to reboot/flash countless times/night...:)
[Galaxy S I9000 Android Development] mialwe:
00:00 - midnight...
[Galaxy S I9000 Android Development] hippo_potamus:
Mialwe,

Thanks for the updates to 0.8.7. It's smoother that I can notice and also love the app that is done up.

I'm very happy with your Kernel and it makes my phone run like it should have been from day 1.

My contribution to your hardwork: 9JD04549TH604950C
[Galaxy S I9000 Android Development] stanbel:
It's when phone become laggy, just before reboot

YES

3 scripts from Thunderbolt v2.4

S76Darky_zipalign

S98CFS

S98System_tweak

About 3 or 4 apps and 6 widgets

Yes, but later, I have just made the reboot (new kernel)

Now memory status is 276/343 (according built-in task manager)

ext4/Jetpack v8.2, based on JW1 firmware

I have just update the kernel and make following adjustments in MidnightControl app.

CPU - ondemand

Undervolting - 0 0 10 25 50 75

Scheduler - SIO

LMK - Midnight

inid.d support - ON

I also attach user.log from /Data directory (renamed to user.txt)

View attachment user.txt
[Galaxy S I9000 Android Development] pikachu01:
Just curious, what is Midnight's LMK values?
[Galaxy S I9000 Android Development] stanbel:
Try to look in the atteched user.txt, LMK values was mentioned in it, I don't now what is important for You
[Galaxy S I9000 Android Development] mialwe:
Yep, but this log is from new 0.8.7, right? LMK changed a little bit since 0.8.4 (home_app_adj, perceptible_app_adj, Mb's).

Tapatalked...
[Galaxy S I9000 Android Development] newcastle9:
Thanks for the great kernel love the new app, I flashed from semaphore kernel will it cause conflicts?
[Galaxy S I9000 Android Development] -freedroid-:
Imho the brightness setting when battery is low is much too dark. Can you fix this?

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] stanbel:
mialwe,

Yes, now i have kernel 0.8.7

but the mentioned bellow,

3 scripts from Thunderbolt v2.4

S76Darky_zipalign

S98CFS

S98System_tweak

CPU - ondemand

Undervolting

Scheduler - SIO

LMK - Midnight

inid.d support - ON

and

ext4/Jetpack v8.2, based on JW1 firmware

was the same with prev version 0.8.6

So, I will try such (new kernel) configuration for a 3 or 4 days, and if it become laggy, I can provide as much information as I can
[Galaxy S I9000 Android Development] jontoo:
Good work mialwe, midnight is my favorit kernel and I always love to us it.

BUT unfortunatly I have a problem to load Voodoo driver in app, it says when I stard the voodoo app that everething is OK and when I start to play music the app force close by some reason???

PLease helpp I don't wont to live mIdnight:(

I use stok JVU rom, previos kernel semaphor
[Galaxy S I9000 Android Development] pikachu01:
The LMK is ok from my perspective. 50MB for HIDDEN_APP.

When you're laggy, what apps lag the most? The launcher? How about other apps?
[Galaxy S I9000 Android Development] stanbel:
Launcher, the most, especially when redraw widgets (GO Launcher)

IM+, black screen about 2 seconds, same with Google maps (black screen)
[Galaxy S I9000 Android Development] pikachu01:
Could be that the LMK has no levels in between its 3840 and 12288 LMK? Try ThunderBolt!'s LMK addon and see if you get the same lag?
[Galaxy S I9000 Android Development] hippo_potamus:
Darn, just realize it too ... voodoo don't work anymore.
[Galaxy S I9000 Android Development] mialwe:
Only a few secs of time so just for voodoo - I never had to load a Voodoo module via VoodooControl(-Plus I assume) as VoodooSound10 is compiled into the kernel, I just use VoodooControl to adjust settings if needed.

Not beeing able to load this specific module may be a result of the stripping/deactivating a lot of debug/misc. stuff for less overhead and (slightly) more performance and RAM (kernel option config_kallsyms_all maybe).

Can you try just using VoodooControl + kernel built-in VoodoOSound10 without module? As I said - never had to use the module.
[Galaxy S I9000 Android Development] hippo_potamus:
Mialwe,

Fair enough, it works the way you've described above. So no need the "VoodooControl plus".

Thanks
[Galaxy S I9000 Android Development] jontoo:
ОК my conclusion is to not load driver modul in Voodoo control +:D
[Galaxy S I9000 Android Development] mialwe:
No, no conflicts. Just be sure to activate init.d only if you are sure the contained scripts (if any) don't change Midnight settings you may have selected. If you are using lowmemorykiller-scripts be sure they change both Linux and Dalvik LMK settings nd not only one of them.

I don't think I can distinguish "normal" brightness setting and low-battery-brightness setting from kernel side. The brightness filter Midnight uses works for brightness generally no matter what caused the change. Therefore you could disable the lower brightness on low bat. feature (have to test this myself) if you are already using lower brightness settings via MidnightControl (brightness values > 1, 5 darkest) or set the brightness filter value to a brighter one (1,2, maybe 3).

Yes, ADJ 2 contains perceptible_app and secondary_server_app. I thought about raising the value a bit but decided to keep it lower for now to not loose matching processes (alarm clock/timer as I read somwhere) too early. But that's for MN0.8.7, not 0.8.4 (ADJ0=2048;ADJ1=4096;ADJ2=11776;ADJ7=14080;ADJ14=15360;ADJ15=17920;) which had a similar gap but contained perceptible, secondary_server, heavy_weight AND backup - which might have been too much.

About brightness level adjustment: via MidnightControl users can adjust brightness level using steps from 1 (stock driver brightness) to 5 (lowest). These steps adjust *ALL* brightness levels (0-255), the highest brightness levels only slightly (or not at all at 100% brightness which is untouched), the lower the driver reported brightness gets the more the filter will reduce brightness according to a multiplier (the step you adjust in MidnightControl). This way we can reach really low brightness for dark environment (night, no light) without lowering higher brightness levels too much.

The used formula (you can test for "original" brightness values from 0 to 255):

brightness = brightness - ((255 / brightness) * bmult) + bmult;

My personal settings: level 2 or 3 for daylight/room, level 5 for night/no light.

You can setup 2 color/brightness profiles (e.g. for day/night) and then quickly switch via the checkbox in MidnightControl's main menu as needed.
[Galaxy S I9000 Android Development] karapoutsoglou:
i just LOVE your work.

its a great great kernel and work generally.

keep it coming
[Galaxy S I9000 Android Development] mancukya:
Best Kernel i wait your Kernel for CM9
[Galaxy S I9000 Android Development] Sw2rT1:
Hello!

Again I have a question about wifi.

In new 0.8.7 version, I have the same problems connecting to WiFi.

I'm waiting for the connection for 15-20 seconds. I thought that this problem of my router. But no. On the other kernels, like hardcore@speedmod, stratosk@semaphore this does not happen.

But. If you go into the settings and the connection is instant.

JVT rom, ZSJPG modem.

PS. my router is TP-LINK TL-WR741ND.

Thx.
[Galaxy S I9000 Android Development] mialwe:
To be honest - I thought a lot about switching to ICS the last days but I'm still not sure if it is stable enough for my average daily use. Ok - I *am* sure it is not stable enough. That's why I did not try yet. I don't own a dev phone so I have to use my SGS for daily use AND developement - no room for experiments.

2.3.6/JW1 with Midnight does everything I want, no issues at all and is stable and fast enough for now. Plus I have the chance to use whatever Samsung comes up with as "official" release and continue working on 2.3.6-Midnight (starting all over again for ICS would take a LOT of time which I definately do not have)... I'd love to try the ICS hardware accelerated UI but that's all I'm missing.

Yes I remember you posted this. Last time I tried to reproduce this but ended up with getting a connection after 5-10 seconds depending on signal. This time I compared switching wifi on via pulldown toggle (15sec.) and system menu (wifi to "on", then choose accesspoint) - even counting that manually switching wifi on via system menu takes some sec. until accesspoints are selectable it's really noticably faster this way.

Never noticed this as I think 15-20sec until connection is not a big problem (still think this but it's an interesting issue)

As you say Speedmod and Semaphore connect faster (via pulldown-toggle or when switching SGS on?) I'll look into this - the following versions will be used for bugfixing/improving/optimizing, no new features for now. Thank you for reporting this again.

Step one: As I said a few weeks ago wifi source was never touched. So I'll take a look at the net-security/connection tweaks setup via initramfs first (but I'm not sure how they would be able to cause different connection times for different menus). But I'll try :)

Do you use any other init.d scripts? JVT - stock?
[Galaxy S I9000 Android Development] Sw2rT1:
Сonnection through the pulldown-toggle and settings menu equally quickly connect to an access point.

No. I do not use scripts.

I use JVT rom which made ​​minimal cosmetic work (like battery indicator, SGS2 icons).
[Galaxy S I9000 Android Development] mialwe:
So I'm not reproducing your issue. What's the exact way you detect the different amount of time needed for connection?
[Galaxy S I9000 Android Development] karapoutsoglou:
could not agree more:)

ics is NOT stable...

i can mention countless things happening to my phone with differect ics versions and different kernels...

and i am a heavy user with hundreds of apps.

today,because i am a lawyer,i had a court and i really needed the dropbox FAST to remember a registry number i have forgotten.

And i opened it lighting fast...

in ICS you never know...

Of course if you have a bare bone phone,ics IS STABLE.ok........

anyway,i really think it is the best kernel for me,not even a single reboot,no conflicts,amazing....
[Galaxy S I9000 Android Development] mialwe:
But the devs do some (a lot of) hard and amazing work and they don't say it is stable, nobody should forget that :)

Maybe I *will* switch in a few weeks or months but for now Midnight and myself will stay with Samsung/2.3.6, so if anybody waits for Midnight-ICS please try Semaphore-ICS, Devil or any other ICS kernel and don't waste your time waiting for me.
[Galaxy S I9000 Android Development] Sw2rT1:
Feels like:)

In any case, your kernel connection takes longer than on Speedmon & Semaphore.
[Galaxy S I9000 Android Development] karapoutsoglou:
yes, ICS if not heavily loaded is stable for me at least.

fast,elegant dialer etc.

But if i start loading apps,i f i start downloading gameloft games sd data,if i start pushing the phone,well you can get from lost cw to eternal bootloops...
[Galaxy S I9000 Android Development] mialwe:
Hello stanbel, looking through you log again I noticed that S98CFS sets the same values as Midnight does so you do not really need it (but it does no harm to leave it active). Midnight uses those great CFS values pikachu01 found out as they really, really seem to work fine for a lot of users.

S98system_tweak changes some important values (e.g. Midnight uses other VM/cache settings than Thunderbolt does but you are overwriting Midnights settings with the Thunderbolt variants) to Thunderbolt ones so to clearly determine the lags you experience after 4 days it would be neccessary to turn init.d off for a few days. (Zipalign script does nothing according to your log, everything has been zipaligned/checked before).

@Sw2rT1: It's very difficult for me to reproduce this according to the information you provided, sorry. Anyone else with too long time to connect to wifi (connects fine but you think time to established connection is too long)?
[Galaxy S I9000 Android Development] pikachu01:
It might be due to the LMK settings as well. Hence, also try ThunderBolt!'s LMK and see if it solves your problem :)
[Galaxy S I9000 Android Development] jocke_lulle:
Looks interesting, will try this kernel in due course:)
[Galaxy S I9000 Android Development] mialwe:
Yes, that's true (have written this 2 pages before):

Pikachu01, don't get this wrong, I don't say Thunderbolt is the cause - as you have spent a lot of time optimizing your tweaks I honestly *don't* think they are. So to detect issues with Midnight's tweaks I'd prefere to have information from a "stock" Midnight driven system without additional scripts which would make things much easier.

If users experience lags after 3-4 days I personally would

- ask if this lags appeared while the mentioned scripts were active (this would point to the lowmemorykiller-cause idea as Thunderbolt's cache values were active and I never read about lag issues with Thunderbolt after a few days, stanbel, could you answer this one?)

- check if it's Midnight or something else (-> disable init.d or change kernel to test)

- try a more aggressive lowmemorykiller preset (just a try, according to the info he/she posted there were ~60Mb RAM available).

- look into Midnight's vm/cache settings (maybe they are ok for 3-4 days but cause this afterwards, maybe I need drop_caches,...). As changing those values is not much work I could even provide a test kernel to users experiencing this issue to see if this solves the lags after 3-4 days.
[Galaxy S I9000 Android Development] krosscheck:
I'm waiting for you. CM9 and midnight will be the best of ;)

Gesendet von meinem GT-I9000 mit CM9 ALPHA