yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] andip71:
Don't want to nag you, but have the same opinion :)

Would soooo much appreciate a JW5 kernel from you.

I know, Stratosk also needed quite a while to get it stable. But I am sure he will share his findings with you, so could give you a kickstart.

Thanks, I am not giving up hope on that.

Andi
[Galaxy S I9000 Android Development] GoThere123:
Hi Mialwe,

It's fine, just take your time :)

We all here really know your concerns, we'll just wait :)

Thanks a lot for your great work. ;)
[Galaxy S I9000 Android Development] Soyuz 3:
Lots of activity recently according to the GitHub commits... *fingers crossed*
[Galaxy S I9000 Android Development] andip71:
Yeah... but only commits. No new kernel so far :confused:
[Galaxy S I9000 Android Development] andip71:
But now...

... I read in a German board, there is something on the Horizon.

Mialwe is giving it a try again. So cross fingers :)

Andi
[Galaxy S I9000 Android Development] mialwe:
Yes, that's true.

I switched back to GB because I wanted to give it one more chance and I like the feeling not to get caught by a bootloop issue when I'm not at home to flash a recovery kernel. And I like GB somehow.

Actually Midnight-GB for JW5 is ready since end of March but I tested/used it only a few days before switching back to ICS at that time because JW5 was *really* laggy. Don't know what went wrong but after switching back to JW5 yesterday everything is fine this time.

As I only have a small SSD (64Gb) built into my Thinkpad ICS/GB and MNICS/Midnight is a matter of space, too - I can only build kernel and/or recovery for one version, sources for the other one have to be backuped and stored externally or in case something goes wrong here reinitialized from Github (thats for kernal *and* complete e.g. ICS sources to build recovery).

Currently I'm thinking of two things regarding Gingerbread:

1) build Midnight for JW1 *OR* JW5?

The big difference is the Samsung source/ROM update for more RAM. I lost track about Gingerbread during the last weeks but I read about JW1 beeing more stable for every day use - not sure what to use and build Midnight for right now, probably I'll stick with JW5 for a while as I used JW1 for a long time but JW5 only for a short time.

2) for Midnight-JW5 Mahd (betatesting for ages now, thank you Mahd!!) reported one SOD. Not sure if it was kernel related as SODs have been reported for completely stock GB ROMs, too - but I'm thinking of rebuilding Midnight from scratch: Samsung updated sources + basic features, then slowly readd more improvements/changes.

I'd love to have a rock stable Midnight like 0.7.6 was for a long time.
[Galaxy S I9000 Android Development] xtoad:
It is nice to see you back!

Since I went 'back' to GB I tried JW5 and it seemed nice at the beginning...extra RAM, TW4 (which, I confess, I like...) improved camera. But after a few weeks it seemed all wonky. I started getting bootloops out of the blue (using semaphore kernel, which had been fine...). I flashed the stock kernel and was ok for a while, then the same bootloops.

So back to JW1 and Midnight 0.9.0 (which I really missed anyway). For some reason, JW1 seems to me better than JW5. That said, I'm no dev, and it would be nice to see what you can do. :) Maybe all it's missing is Midnight..?

Thanks for your work. I know you mention that you have learned all you have from reading around XDA and such, but as a simple user I have learned a great deal from some of your posts.
[Galaxy S I9000 Android Development] andip71:
Hi Mialwe,

really really good to see you are back on GB now, working on a JW5 kernel.

I cannot more confirm what you say, I like GB because:

- I do not run into boot loops all of a sudden, the system is rock stable

- Everything works as it should

- Battery utilization is much better than on ICS

For me enough reasons to stick to XWJW1 with your kernel most of the time. It is the best and most amazing tradeoff of performance vs. power consumption.

But, if you release a JW5 based kernel I might give this a try again. I liked the JW5 firmware very much in the beginning, but after 2-3 weeks it got really laggy, slow, acting funny somehow.

Thats why I got back to JW1 and since them I am happy again.

Keep up the good work, I will closely monitor this thread still. Although I will not be with the SGS1 very long anymore, will rather pass it on to my wife. SGS3 is waiting for me already :)

Thanks

Andi
[Galaxy S I9000 Android Development] dherre65:
Well, JW5 is the latest but also the last official firmware for I9000. Also it has a lot more ram, and it's stable (at least on my phone). I would love to have a Midnight kernel on my JW5 firmware.
[Galaxy S I9000 Android Development] mialwe:
MNGB-56

Basically like the last Midnight kernel with JW4/5 initramfs and Samsung source update including the RAM config (won't work with Samsung ROMs < JW4/5).

There has been reported 1 SOD with this one so I upload it as "test version" as I don't have the time to work on it, sorry.

This has been developed using the complete new Samsung sources and re-implementing Midnight changes, don't know if I forgot something.
[Galaxy S I9000 Android Development] Rebel2k:
Oh, pretty cool! I'm on JW4 and will probably have a look at that quite soon! :)
[Galaxy S I9000 Android Development] ddd613:
How can i change filesystem? There is no options on midnight app or recovery.

Sent from Galaxy S DMORE 3.3 based JW5, midnight kernel is testing inside
[Galaxy S I9000 Android Development] jocke_lulle:
Use ext4-app from cfroot thread. Btw,I think it is included in DMORE 3.3.

sent from Tapatalk
[Galaxy S I9000 Android Development] extralife:
Not possible with new kernel. Have a look @post#1.

0.7.6 supports file conversion. But don't forget, you can't boot jw5.

or try cf root and flash back the midnight.

... using tapatalk
[Galaxy S I9000 Android Development] Soyuz 3:
@mialwe

Thanks for your work on the MNGB-56 kernel! I was eager to try out this kernel on my 'stock' XWJW5 but after flashing it bootloops. I've tried to flash from several kernels (stock, Semaphore and CF-Root) both with and without lippo's kernel cleaning script but nothing seems to work. Any suggestions?

(ps. I'm on RFS and cleaned out the init.d folder)
[Galaxy S I9000 Android Development] ddd613:
That's the solution

Sent from Galaxy S DMORE 3.3 based JW5, midnight kernel inside
[Galaxy S I9000 Android Development] jocke_lulle:
Oops, I forgot that. Thanks:)
[Galaxy S I9000 Android Development] extralife:
a little help, for somone who can't handle kernel-loops.

---

jw5-stock-kernel

---

extract the archive and flash 'tar' with your preferred flashing-tool.
[Galaxy S I9000 Android Development] Soyuz 3:
Thanks for your reply. I realized that I formulated my question inadequate after a long day and evening of work :-(

I already flashed other kernels, including stock like mentioned in my posting, and my phone works fine. What I meant is the new midnight kernel always bootloops for me.

Verstuurd van mijn GT-I9000 met Tapatalk
[Galaxy S I9000 Android Development] extralife:
with semaphore 2.7.4 you didn't get a b-loop?
[Galaxy S I9000 Android Development] Soyuz 3:
Indeed, currently I'm on Semaphore 2.7.4 and no problems at all. Also with stock XWJW5 and CF-Root XXJW4 I don't experience bootloops.

When I was on XWJW1 I've been using midnight without problems so there must be something with this specific build I guess.

Verstuurd van mijn GT-I9000 met Tapatalk
[Galaxy S I9000 Android Development] extralife:
hmm ... try neldars kernel-flasher
[Galaxy S I9000 Android Development] mialwe:
Strange - I never experienced loops while working on this, does anyone else (from the 15 downloaders :) ) experience issues like this?

- What does "stock" mean?

- What does "cleaned out" init.d mean - did you try deactivating init.d completely?

- Overclocking/undervolting?

- How did you flash the kernel?

I tested this version with a fresh, stock, odexed JW5 - worked fine the few days I used it :(
[Galaxy S I9000 Android Development] Soyuz 3:
@extralife

Will try with neldars kernel-flasher in a few, thanks for the suggestion :-)

@mialwe

Yes it's very strange, and I'm really sorry to bother you with it. I'll try to answer your questions best I can.

-With "stock" I mean just the regular XWJW5 ROM downloaded through CheckFus, not a custom ROM based on XWJW5.

-During testing I made sure there were no active scripts (also made sure all scripts were deleted from the init.d folder, also I've tried when I removed the init.d folder itself).

-No overclocking or undervolting present.

-Till now I've flashed through Odin 1.82 (using the origional tar and a repacked tar.md5) and tried Heimdall 1.3.1 and 1.3.2 and will try neldars kernel flasher in a few.

Update:

Same result using neldars kernel-flasher.
[Galaxy S I9000 Android Development] ZaneZam:
16 downloads!!! :) I've just installed this version with sgs kernel flasher on JW5 stock odex and have no problems so far!! Of course it's too early to say that everthing is working fine.. i will give it some days and report back if something is "happening"! ;)

Thank you very very much for spending your time and making this JW5 compatible version!!

One technical question: Did you find a way to fix that problem with non-applying lmk settings that is present since JW1 rom?
[Galaxy S I9000 Android Development] mialwe:
Glad to hear it works for you, thanks for reporting back.

LMK: I'm not sure as I never saw Samsungs GB sources and I only have read that the LMK properties have been disabled by Samsung just like they are in the stock ICS sources. So unless the sources or the built ROM are patched to re-read the LMK properties that have been set via the initramfs in earlier versions there's nothing we can do about it.

Background: In earlier versions of Samsungs GB the lowmemorykiller values have been defined in the file init.rc in the initramfs. That is the reason we were able to change them in various ways. The values have been read in by Android at boot and set/used accordingly.

In the new sources (ICS that is as I wrote, assuming JW4/5 beeing similar here) those variables do *not* get read by Android which calculates it's own LMK values according to available RAM and sets it's _MEM/_ADJ and Linux lmk values accordingly.

If one compiles Android from source the needed routines can be re-implemented, maybe that's the way some ROMs handle user defined LMK nowadays for ICS, don't know.
[Galaxy S I9000 Android Development] Soyuz 3:
@mialwe

Good news from my end! While I couldn't get MNGB-056 to work on my phone with the XWJW5 firmware (even after flashing a fresh ROM) the kernel works great with the XWJW6! Thanks a lot and sorry for the previous issues, I really don't have any clue what caused it.
[Galaxy S I9000 Android Development] Abyv:
Hi..just flashed ur kernel on my i9000.Very smooth and nice.! Thank you
[Galaxy S I9000 Android Development] xtoad:
Thanks for making the updated kernel mialwe!

Been using it for a week and seems very nice. I had one black screen freeze but I am sure it was app related. The other thing I noticed was that deleting start up/shut down sounds didn't actually do it for me...?

I am guessing that it works for JW6 also... Will give it a go later.

Thanks again!
[Galaxy S I9000 Android Development] Soyuz 3:
For all the MIDNIGHT fans, mialwe is testing a freshly build "basic" mngb kernel. It's great to see that stock gb roms still get some love from our favorite kernel developer :)

[Of course any test version for us to test is welcome ;):p]
[Galaxy S I9000 Android Development] mialwe:
@xdoad: Great to hear it worked for you, thanks for reporting back. I never tested -56 with JW6 but I think it will work, yes. I'll take a look at the bootsounds not beeing deleted, maybe the filenames have changed or something like that, thanks for reporting.

@soyuz3: Now comes the "basic" MNGB part... :)

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

General update:

As I continue running out of time I had to make some decisions about SGS/Midnight kernels. After testing various ROMs (CM9/other/ICS, MIUI-ICS, CM7, MIUI-GB) I finally made the step (back?) to Stock Samsung Gingerbread, currently running JW6 having the great and stable JW1 as a backup on my /sdcard.

- MNICS developement is frozen.

- MNCM7 developement is frozen (never published).

- Midnight developement is frozen including the MNGB-56 test kernel.

A few days ago I started working on MNGB for JW4/5/6 using completely untouched Samsung sources.

Attached is the last dev version. This kernel comes with the basic features like the known Midnight-CWM4 including cleanup options, general options,..., autoroot, VoodooSound, BLN, the Smoove-Governor [default], SIO IO scheduler [default] and undervolting, overclocking (replaces 1Ghz [default] step with 1.128Ghz) in case it's needed.

- I'll avoid too much optimizing, stability > performance.

- All options can be set in CWM just like in earlier Midnight versions, no app.

- No Nexus drivers with gamma/RGB controls, just stock with Speedmod's sharpness adjustments and color temp. like in earlier Midnight versions.

This dev kernel has not been extensively tested but it seems to work fine with JW6 over here. This is the only Midnight/MNGB kernel in developement right now.

EDIT: As I just found out this version will replace your Superuser.apk/su-binary on every boot (forgot to remove some lines in the initramfs), not a big issue but this will be fixed in next version.

EDIT: Reuploaded new version, fixes Superuser/su replacement at every boot, CWM option "delete startup/boot sounds" now correctly deletes PowerOn.ogg, too.
[Galaxy S I9000 Android Development] Soyuz 3:
@mialwe

You just beat me to it :D Any special upgrade instructions for those who are already on MNGB-056?

I've attached an Odin flashable .tar.md5 for those who need it [mialwe please tell me to delete it is needed].
[Galaxy S I9000 Android Development] mialwe:
Not really. Should be working fine, you might want to delete /system/app/MidnightControl.apk as it will not work anymore.

Thanks, that points me to an error with my new buildscript - the TAR attached in my last post was intended to be usable with Odin (and the extracted zImage with Heimdall which I prefer) but my buildscript puts the complete path into the TAR archive,.... thanks :)

EDIT: Reuploaded fixed TAR archive.
[Galaxy S I9000 Android Development] Soyuz 3:
@mialwe

Great work man thanks. Everything works fine (as far can be told within an hour), checked some CWM kernel options and toggling on and off works like intended. The Smoove-Governor is awesome, very good response in apps.

Will report back if I notice something. Once again, thanks for the marvelous work!

Suggestion:

How about replacing ChainsDD's Superuser with the more recent SuperSU by Chainfire? Just a question, I'm not knowledgeable enough to be aware of any technical problems this might cause.
[Galaxy S I9000 Android Development] ddd613:
Mngb 0.5.1 is the newest one :confused:

Sent from Galaxy S DMORE 3.3 based JW5, midnight kernel inside
[Galaxy S I9000 Android Development] Soyuz 3:
@ddd613

That's correct mngb-0.5.1 is the latest version. You choose:

Gingerbread ROMS

up to

JW1: midnight-0.9.0

Gingerbread ROMS

from

JW4: mngb-0.5.1
[Galaxy S I9000 Android Development] mialwe:
Yes, perfectly explained.

for the new mngb kernels I started all over with the latest Samsung sources -> new name (mngb), new versions starting from 0.0.1 -> 0.5.0 and 0.5.1 are the first versions uploaded here. OP will be updated as soon as I find the time for that.
[Galaxy S I9000 Android Development] ddd613:
Bootloop after 0.5.6

Sent from Galaxy S Saurom based JW5, semaphore kernel inside
[Galaxy S I9000 Android Development] Darkwing_X:
Hi Mailwe,

I use the latest mngb since yesterday.

Everything is running smooth and lagfree.

I have only one thing that Tarffic Monitor widged has a FC

when i boot my phone. But after it's running correct.
[Galaxy S I9000 Android Development] mialwe:
Sorry for that, first and only bootloop report. Did you try re-downloading and re-flashing? Additionally some more information about your config would be helpful, e.g. *any* running init.d scripts, overclocking, undervolting,...

btw. as I've written above there's a new version for JW4/5/6 - MNGB-0.5.1 just a few posts above - I'll delete the -56 test kernel download.

Maybe I should clean up the complete OP to match the new versions...

FCs usually are not related to the kernel but to be sure you could post or pm the output of logcat - all FC debug messages are logged there by Android itself.

EDIT: Logcat is enabled as default in MNGB-0.5.1 so just getting the log via app, e.g. aLogcat or ADB ("adb logcat") would be enough.
[Galaxy S I9000 Android Development] Darkwing_X:
HI Mialwe,

thanx I'll try this later on, maybe there are some remains from Semaphore.

And it's only when i start the phone, when it's running there is no FC and the prog

runs very well.

I'll post or PM when i have a result.

Thanx again
[Galaxy S I9000 Android Development] sammyservices:
hi !

just started with yr kernel on jw6 and cannot load Flipboard. Is this kernel related ? As to other points at this moment all is still new for me to comment on but Please would appreciate if you can tell me something about the Flipboard loading problem.

also there is no Midnight Control Icon in the phone . Is this normal ?

Finally, how do I Wipe Data from Recovery ? I can see Wipe Cache but and Factory Reset which I dont need now but cannot find Wipe data reset.

Thanks !

PS: One more thing; what would you recommend ? JW4 or JW6 ? Thanks again !
[Galaxy S I9000 Android Development] mialwe:
0.5.5

0.5.5 uploaded: http://xdaforums.com/showpost.php?p=16255352&postcount=1

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

@sammyservices:

- Flipboard: Never used, app failures usually are not related to the kernel but to be sure you can send me the output of Logcat (e.g. using aLogcat app after enabling Logcat/Logger module in CWM).

- Wipe data == factory reset

- MidnightControl: Removed starting with the new mngb series (0.5.x+), only basic features.

- JW4/JW6: Never used JW4 long enough, sorry. JW6 runs great here.
[Galaxy S I9000 Android Development] ddd613:
Anyone has experience of use 0.5.5? Install from semaphore 2.7.4 going good

Sent from Galaxy S Saurom based JW5, semaphore kernel inside
[Galaxy S I9000 Android Development] ZaneZam:
Jep, now i have experience, but unfortunately a bad one! :(

mialwe I hate to report it but the new version 0.5.5 gives me a bootloop on JW6! The loop begins after powering on the phone a few seconds after the Samsung logo disappears. It feels like at that point when the bootanimation should start! ;) I tried to flash with odin and SGS kernel flasher (so i downloaded the image twice) with the same result. I was able to install your dev build version MNGB-056.tar (which i used on JW5 before) w/o problems and tried to flash from this working base but again with the same result!

It seems the loop begins on a stage before logcat starts so i can't provide any logs! One strange thing i can report in addition is that when i power on the phone and connect the usb/charging cable the bootloop stops and the phone seems to power off :confused: the charging animation doesn't work and i can not power on the phone again with any cable connected! Another strange thing is that CWM is still working! :eek:

Ah, and before you ask : I had semaphore 2.7.4sbf installed, no tweaks active or any scripts in init.d when i started to flash.

sooo sadly no chance for me at the moment! :(
[Galaxy S I9000 Android Development] mialwe:
Wow, that's not a good day today... just recovered my wife's SGS2 from a soft brick (somehow) after 5 hours of experimenting...

Ok, as this is the first report of such strange issues with mngb I'd like to find out what causes this.

- are you on a stock JW6 without modifications?

- stock bootanimation?

- if you flash mngb -> loop -> flash another kernel: do you have access to a /data/user.log file?

- which parts exactly are looping?

For now I don't have an idea what is causing this as mngb is built on the latest Samsung sources with only the Midnight-CWM, some initramfs scripting and the main features like BLN added. Boot/init process is stock and untouched (charging mode, too), the initramfs scripts come from -56 test kernel :(

Anyone else having loops?
[Galaxy S I9000 Android Development] pikachu01:
Could be due to compile options?
[Galaxy S I9000 Android Development] ZaneZam:
Man that's really bad, if YOU gonna need 5 hours then i guess it was REALLY bricked! ;) And now i came up with my strange bootloop in addition...uff sorry, didn't know :o *g*. Some time ago i was playing around with kernel sources (more precisely with semaphore sources) and till i got a working kernel image (with own modifications - yeah! :p) i saw a lot of strange things, but this one is completely new! I really don't know what's going on here. :confused:

Jep as my signature says i am on stock odex JW6. Actually i HAD semaphore/thunderbolt(no binaries!)/custom bootanimation and at last for testing purposes supercharger installed BFORE i flashed mngb 0.5.5

but of course i removed all of that stuff before flashing!! And nep at the moment i have no other mods installed (because i have to make them first *gg*)

So flashing back to sempahore works and as i mentioned previously flashing MNGB-056 works which is btw. running like hell atm without any additional tweaking! best performance/energy proportion for me :eek: :)

However i really want to nail down my problem here and will try again to get the user.log file and get back to you!

Thx mialwe for the midnight GB revive/refresh and for your time/efforts related to it, really appreciate this!
[Galaxy S I9000 Android Development] mialwe:
Well, as I'm (slowly) rebuilding from scratch there aren't custom compile options, no new tweaks, optimizations,debug removal,... just new source + a few old features + CWM from earlier Midnight Versions.

Thanks for trying, as some users are running MNGB-0.5.5 without loops (including myself) there must be something else, we just have to find it :)
[Galaxy S I9000 Android Development] zodiaxe66:
Thanx for updating.might revert to gb.love the ui of ics,but really miss the stabillity of gb
[Galaxy S I9000 Android Development] ZaneZam:
And the problem is: ext4 ! I guess these users are using rfs. ;)

After converting back to rfs 0.5.5 runs now w/o problems!

This explains the strange bootloop in such a early stage (mounting system etc.) and this is also the reason why i couldn't find the user.log file. Any possibilities to debug this (init.rc??) problem? I am ready for further testing (nandroid rulez! *g*) :)
[Galaxy S I9000 Android Development] mialwe:
I'll take a look at the mounting lines in the initramfs, maybe I missed one (initramfs is 100% JW6 with freshly added modifications used in earlier Midnight kernels).

May take some time since I switched to CM7 but I'll try to debug this.

Thank you for reporting back :)
[Galaxy S I9000 Android Development] M_J_Nazari:
thanks

the init.d scripts doesn't works too.