yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] mialwe:
Hello scheichuwe, glad to hear you use (used?) Midnight :)

Midnight uses the backup/restore/ext4/rfs-Methods from Speedmod recovery sources and have not been touched by me.

The issue you are reporting hit me back in Froyo times (with Speedmod/JSD if I remember right) - somehow backup sometimes does *not* create a valid backup of /system (I don't say that this is an issue with Speedmod recovery as I don't know if this happens with other Nandroid backup implementations, too) - it never happened to me with Midnight/GB.

Since the day this happened to me with Froyo I *always* check the backup files in /sdcard/clockworkmod/backup for reasonable filesizes - if the filesize is very low I won't try to restore this backup. Example: My current system.img filesize = 236603136 which seems to be ok.

Because of limited time i doubt I'll be able to look for this issue in cwm2.5 sources (IF it's located there), first of all I'll try to get Midnight 8.0 ready including CWM4 and tested Nandroid backup functionality. I hope it will work fine now that the mounting issues for either RFS or EXT4 seem to be solved. I spent too much hours to make CWM4 work to switch back to CWM2.5. Testing everything will take a few days.

Edit: Before testing I'll try to make a flashable-file-based backup as described here, worked in JSD times, maybe with gingerbread, too, maybe someone is interested in this almost forgotten post... :)
[Galaxy S I9000 Android Development] hippo_potamus:
No problem for me, being doing restore ALL / back ALL almost every other day.

Using Stock JVR with midnight.
[Galaxy S I9000 Android Development] Skkip:
Hi mialwe,

Since you add 1200MHZ to the existing cpufreq table, would it be possible to add 600 Mhz too? So we can have 100 - 200 -400 - 600 - 800 - 1000? This would be great for conservative scaling :)

Thx in advance
[Galaxy S I9000 Android Development] scheichuwe:
I still (will) use midnight kernel :)

I _always_ do the same (filesize is 247,05MB) ;)

I don't know what went wrong, but it happens again and again...

(I managed to get my SGS working in the meantime). I converted all partitions to ext4, don't know if this matters.

If you need someone for testing nandroid backup function, I'll help you out.
[Galaxy S I9000 Android Development] badworker:
i have some issues with the cwm nandroid restore. backups can't be restored, it returns me this error:

Erasing boot before restore...
Restoring boot image...
Error while flashing boot image!

so I cant restore any backups, i hope that someone will fix this because i had a problem with a script that doesn't mount my partition (bootloop and no-working cwm) and I had to reflash rom through odin (flash kernel didnt work).

Please, is the only backup i have, 700 contacts that i had to restore (i'm unlucky - google sync didnt sync anything :( )
[Galaxy S I9000 Android Development] mialwe:
1) did you make the backup with Midnight?

2) if yes and your backup files are ok you could try Speedmod as Midnight uses the same Nandroid functions

3) if no: please try to restore with the kernel you made the backup with

Sorry I cannot help any more, just listed my first thoughts on this, maybe someone else has an idea?

4) What script did that??

EDIT: Don't have Midnight 0.7.6 installed right now but after looking into the sources there might be a chance for you to get your contacts back: If you had to reflash your ROM I assume it is working. You then flashed Midnight, ok. In CWM you have the option to flash only the DATA related backup parts ("Restore DATA"), that does not include the boot backup. Did you try this option?
[Galaxy S I9000 Android Development] badworker:
1) yes

2) trying to restore only data (seems working)

thank you so much. I will say you if it worked.

edit: IT WORKED! thank you so much. you really saved my life (and my business :D )
[Galaxy S I9000 Android Development] hippo_potamus:
I just tried (once again) to convert RFS to EXT4 using the CWM option and haptic feedback stops working. Using stock JVR with Midnight Kernel. Out of curiosity, I flashed hardcore's kernel and tried the same thing, no problem at all ... so something's broken in the RFS to EXT4 conversion for midnight on JVR :p
[Galaxy S I9000 Android Development] mialwe:
Thanks for reporting again but I have some problems with this one:

- the conversion code is 100% untouched from what Hardcore mailed me (the initial Midnight recovery code is based on Hardcores CWM2.5 including his conversion routines).

- the Nandroid backup code is 100% untouched.

- nobody else reported this issue until now

- tested myself after converting multiple times and HF worked with JVQ (never tried JVR, JVS)

- I cannot see a relationship between HF and conversion besides a) backup and b) formatting (as the HF code is stored like everything else on a partition which is converted).

I'd love to give a different answer but as I spent a lot of hours in making CWM4 work with Midnight + CF-ext4-tool and my time is very limited atm I won't look into bugs (if it really IS a bug with CWM2.5) with CWM2.5 anymore (if they are not easy to locate). I think I can publish a experimental Midnight 0.8.x with CWM4 within the next two weeks, maybe you want to try Midnight again when this version is uploaded... sorry I cannot help on this one.
[Galaxy S I9000 Android Development] scheichuwe:
Under all circumstances! :)
[Galaxy S I9000 Android Development] hippo_potamus:
It's okay ... I'll try to figure it out myself and report back. Thanks for your great kernel.

[edit] I just tried it again and this time, it works (used terminal to verify it's on ext4). Well it's no longer a problem but still X-files as to why the first two attempts did not work. Oh well.
[Galaxy S I9000 Android Development] saszseb:
Is/are there apps. like Voltage Control to tweak kernel settings?

Thanks.
[Galaxy S I9000 Android Development] mialwe:
You can use VoltageControl or setCPU to control voltages (but using CWM allows 5mV steps), governor, scheduler and some CPU scheduler thresholds. There's no app to set the lowmemorykiller values or the other Midnight options (yet) - use CWM for that.

An app is on my todo list but I have to get Midnight 0.8.0 ready first.
[Galaxy S I9000 Android Development] saszseb:
Thanks.
[Galaxy S I9000 Android Development] jimbo77:
Not ment to push you in anyway but we need a new version to play with ^_^ ...

My phone, so am I, is bored because i can't flash anything new to it hehehe...

Keep up the good work and I hope to see an update soon :)
[Galaxy S I9000 Android Development] saszseb:
Does this kernel work on I9000 Brazil?

Thanks.
[Galaxy S I9000 Android Development] cxyrus:
hi i would like to say thanx for this kernel.

after i flash tihis kernel via odin, i didn't have root access,

enter cwm and install (su.busybox..etc).

reboot...

still dont have root access, superuser installd from market, try to update installing path failed,

how to root it?
[Galaxy S I9000 Android Development] saszseb:
- uninstall superuser!

- go to CWM and install superuser+busybox!
[Galaxy S I9000 Android Development] cxyrus:
already did that twice, still no root.
[Galaxy S I9000 Android Development] mialwe:
You could try CWM->advanced->Cleanup options->Root/Superuser...

This tries to remove all ROOT related binaries/apps.

After this try ROOTing vie CWM again. Maybe this helps.

Update:

Im still having a hard time making CWM4 work with RFS - at this time it seems I have to give up. Cannot count how often I had to compile/reboot/flash/reboot/re-flash backup with Midnight 0.7.6 the last few days due to menu/formatting issues with RFS...:( pretty frustrating as the rest of the rebuilt initramfs and the kernel itself seem to work fine. Anyone knows a source location of CWM3 or 4 with working RFS support?
[Galaxy S I9000 Android Development] nmcc89:
CF-Root has integrated cwm 3 and that works with ext4 and rfs? I don't know where the sources are, you might need to speak to chainfire. Also Semaphore kernel is based on CF-Root and stratosk has posted the sources on his thread if that's any help
[Galaxy S I9000 Android Development] mialwe:
Both of them have not published CWM sources (don't know if they have changed anything in CWM). Strange - there do not seem to be officially published sources of RFS-modded CWMs (>=3.x.x) ... I'll continue searching for my bugs/issues...

EDIT: This may explain why there are no CF-CWM sources available. As far as I know Semaphore just uses the CF-recovery without making changes to the sources.

I'll try to backport Midnight 0.9.x (CWM4 dev version) changes to the CWM2.5 version which seems to work well to give users a small kernel update, need a break from CWM4 now...
[Galaxy S I9000 Android Development] jimbo77:
Any update yet? is development stopped?
[Galaxy S I9000 Android Development] mialwe:
Not stopped, just spent two weeks of work in CWM4 - which did not work out due to an issue with RFS formatting.

Stopped working on the CWM4 version two days ago.

For current plans please see my last post (the post before yours).
[Galaxy S I9000 Android Development] pikachu01:
There's CWM5 out already (not sure if the source is out though). Maybe you'll have better luck with that? :)
[Galaxy S I9000 Android Development] mialwe:
To show a sign of life and becaue I forgot to answer pikachu here's a small update on why there has been no Midnight update for some weeks...

- frustrating attempts to make CWM4 (with CWM5 TAR backups backported, I really like TAR and yes, the source is there) work with RFS as stated above, issues showed for beta testers *after* building a complete CWM4 with Midnight options (Nandroid restore produced filesystem corruption on /system)

- stopped experimenting for a few days

- decided to discontinue Midnight CWM4

- decided to work on it again because I do not like giving up :)

- experimented with CWM4, CWM3, lots of debugging

- found the issue to be the RFS-bug Supercurio described earlier here

- found another issue with Chainfires EXT4-conversion app (stopped conversion somwhere @ /system or /data)

- more experiments, a lot of debugging and searching (web and code)

- finally both issues seem to be solved with CWM3, asked Supercurio for information on the RFS issue (to be sure) and it seems like the bugfixes will work ok. Thanks Supercurio for answering.

- tried to locate a bug which caused the bootanimation to play twice - found and solved after rebuilding the initramfs Midnight scripts one by one.

- testing the initial used and bugfixed CWM4 source now, first Nandroid backup/restore worked fine... :)

Will be testing some more days now (RFS, EXT4, CF-EXT4-tool, Nandroid \w EXT4,... and the Midnight CWM options.) and *really hope* that I'll be able to give you another Midnight kernel. If you still want it.

EDIT #1: Checklist:

- RFS- and mount-bugfixing CWM4: ok

- Port Midnight options to CWM4: ok

- Midnight initscript parsing (uv, oc, lmk, tweaks,...): ok

- custom bootanimations: ok

- nandroid backup RFS: ok

- nandroid restore RFS: ok (4 times, counting...)

- EXT4-tool conversion EXT4: ok 1x, failed 2x

- EXT4-tool conversion RFS: ok 1x, failed 1x

- new plan : implementing RFS/EXT4-conversion via CWM: ongoing

- nandroid backup EXT4: todo

- nandroid restore EXT4: todo

- Midnight CWM options functionality: ongoing
[Galaxy S I9000 Android Development] malcho:
Offcourse we want it
[Galaxy S I9000 Android Development] mialwe:
Hrmpf... trying to implement a pre-init script using "ln -s init.sh init" always results in a bootloop (kernel logo shows up)... don't know why...
[Galaxy S I9000 Android Development] madfix:
Already tried that, same results ;-)

Seems that messing with init or trying to run a lot of init.d scripts always lead to bootloop.

Happy brainy night :-p
[Galaxy S I9000 Android Development] mialwe:
Got it working (system should be initialized to be used :) ). Now I'm trying to get graphsh / graphchoice to work - yellow/distorted screen for now...

Edit: Don't need a framebuffer menu, just outputting information after rebooting into RFS/EXT4-conversion procedure while converting would be fine...
[Galaxy S I9000 Android Development] GoThere123:
Long time not visiting Xda forum, especially this thread.

It looks like your kernel become one of the greatest kernel out there as i thought several weeks ago :)

Want to update my kernel from your previous version 0.5.4 to your latest kernel.

Thank you for your great work and your effort to keep developing this kernel :-)
[Galaxy S I9000 Android Development] mialwe:
Thank you for your words but I don't think Midnight can *ever* be the "greatest kernel out there". No way :) Just look what Existz, Zacharias, Glitch, Stratosk and all the other great developers work on - but I never wanted Midnight to be "the greatest" (and *never* have said or will say/write this).

Just wanted to build a kernel that suits my needs (undervolting, BLN, VoodooSound, mostly stable, fast enough but battery saving because I will use my SGS for at least one year more - that's it.

There are many, many more things that could be done to the kernel/sources/tweakscripts/... but I just don't have the time, the knowledge (actually learning is the best part ov Midnight developement :) ) or the need to do this.

But I'm glad you like it :)

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

Update:

I'm currently working on the init environment in the initramfs where we have to intercept Samsungs "init" binary start to get own scripts executed at this time of boot (for /system EXT4/RFS conversion started via CWM). Works fine now, next step is starting CWM from there for outputting log messages while filesystem conversion...
[Galaxy S I9000 Android Development] laconic5:
Kernel choice is very subjective, depending on your usage. Out of all the other kernels I've tried, this one fits my needs perfectly.
[Galaxy S I9000 Android Development] stratosk:
The greatest is your passion to develop and create something.

The greatest is your honestly.

The greatest is that you keep learning.

The greatest is that you are working for free.

The greatest is that you are helping people (also for free) at your free time.

The greatest is helping other developers doing the same job with you.

The greatest is that you are sharing.

So, yes, your kernel (and you) is (are) the greatest. :)

Keep up the excellent work!
[Galaxy S I9000 Android Development] malcho:
Mialwe,

Nobody can take away your knowledge that is the only thing it's worth.

Keep up the good work.

Anyting i can help i' m here.
[Galaxy S I9000 Android Development] mialwe:
Thanks guys. But this has nothing to do with "greatest". Honestly.

Currently I'm stuck at calling recovery as "fsmenu" to get my filesystem conversion menu shown, (comparing builtin nandroid option with my fsmenu option in code tags here) does anyone have an idea?

$ adb shell /sbin/nandroid
Usage: nandroid backup
Usage: nandroid restore <directory>

$ adb shell /sbin/fsmenu
fsmenu: applet not found

$ adb shell ls -l /sbin/nandroid
lrwxrwxrwx 1 system system 8 Nov 11 23:43 /sbin/nandroid -> recovery
$ adb shell ls -l /sbin/fsmenu
lrwxrwxrwx 1 system system 8 Nov 11 23:43 /sbin/fsmenu -> recovery

in recovery.c:

if (strstr(argv[0], "nandroid"))
return nandroid_main(argc, argv);
if (strstr(argv[0], "fsmenu"))
return fsmenu_main(argc, argv);

Something important I'm missing...
[Galaxy S I9000 Android Development] malcho:
Sorry man i'm not developer.

I can do testing or make some other thing(like semaphore logo).

Many regards
[Galaxy S I9000 Android Development] mrnikt:
Any plans to release JVU compatibile version ? PLEEEEZZZZ :)
[Galaxy S I9000 Android Development] mialwe:
I'm still working on the CWM4 version.

Right now it seems I do not even have the time to do a filesystem conversion and re-check all options with RFS so I'm sorry this will be delayed some more time.

- Is there a JVU zImage linked somewhere so I can look for initramfs differences (if any besides the prebuilt modules)?

- Could you provide the module version string (SGS->options->info->kernel version with stock kernel)?

- Are there issues with JVT version on JVU?
[Galaxy S I9000 Android Development] pikachu01:
I don't have JVU, but I have an XFJVA zImage, which is even newer than JVU. Don't think there was any change regarding the initramfs other than the prebuilt modules.

I9000XFJVA-CL621561

XFJVA zImage:

zImage (5.46 MB)	http://www.multiupload.com/9IW5PTPRR0
[Galaxy S I9000 Android Development] mrnikt:
JVU zimage - here U R

http://www.multiupload.com/ND7CQGD7OL
[Galaxy S I9000 Android Development] mialwe:
Thank you both very much.

I'll look into the differences (assuming not much having changed since JVT) in the initramfs and probably switch to XFJVA as soon as possible. I usually don't do last-minute changes anymore (bad, bad experiences :) ) - but I've just included newmails great ondemand patch as kind of last-minute-change, too (planned for some later release) so a new initramfs (or it's new modules if any) won't probably make things worse :)

Update on MN 0.8.x:

If everything keeps working I'll slightly rearrange CWM menus, update initramfs modules (and whatever has changed since JVT), some final testing and that's it. I hope.

Now that I've written this I'm sure something will break again... :) Need more time...
[Galaxy S I9000 Android Development] hippo_potamus:
Battery full notification sound

Hi,

A bit off topic but I shall asked anyway since I'm using Midnight Kernel now.

How do I enable back the Battery full notification sound?

Thanks
[Galaxy S I9000 Android Development] mialwe:
Im not sure If I can help here, as far as I remember MN does not remove the battery-full sound (don't even know the filename)?
[Galaxy S I9000 Android Development] scheichuwe:
/system/media/audio/ui/TW_Battery_caution.ogg
[Galaxy S I9000 Android Development] mialwe:
Thanks. Definately did not touch this. But a few seconds ago my battery went 100% and I did not hear the notification sound, too. Strange. JVT stock odexed.

EDIT1: The file is there but was not played on battery 100% ...maybe related to having "system volume 0%"...

EDIT2: Don't have the fully charged sound, too (never missed it :) ) - searching for this ends up in millions of "battery drain" search results but found some posts about the notification sound for 100% charged disappeared with 2.3.3 GB - does anybody actually *hear* this sound?
[Galaxy S I9000 Android Development] hippo_potamus:
Checked file "TW_Battery_caution.ogg", it's where it's suppose to be.

Battery low works.

Battery full does not works ... that's what I'm wondering why. Thanks
[Galaxy S I9000 Android Development] mrnikt:
PLease consider adding a little more governor options. Smartass v2 would be a great option .. and maybe interactive.
[Galaxy S I9000 Android Development] mialwe:
Almost midnight. It's time...

- Post #1: Features, changelog and thank-you-s updated

- Post #2: Explanations and FAQ updated

- Sources updated

- uses newmails ondemand/cpufreq patch (with 100Mhz min. freq. and adjusted max. freq. handling for OC), be sure to adjust UV values to be less aggressive if you experience reboots

- Touchscreen-tweak moved to CWM->advanced->misc, has to be re-enabled if needed

Thanks Stratosk (initramfs/help), Supercurio (RFS-bug/help), Mahd + Scheichuwe for betatesting. Thank you all. A lot.

@mrnikt: Sorry for answering late but I've been really busy getting 0.8 ready. For now I do not have plans to include more governors as I'm quite satisfied with the current Conservative/Ondemand setup. After nearly two months of work for 0.8 I need a break.
[Galaxy S I9000 Android Development] malcho:
Hej

It's nice to see you working.

That's impressive changelog.

Keep up the good work.
[Galaxy S I9000 Android Development] antz_77:
Thanks again for your great work!

From a far away galaxy(S)
[Galaxy S I9000 Android Development] mrnikt:
Woooww... Mialwe DUDE ... This release of Midnight is AWESOME :)

Thanks for yor work
[Galaxy S I9000 Android Development] pikachu01:
Wow, github shows lots of changes under the hood.

And I can't seem to generate the .patch file for the latest changes >.<

Anyways, good work man. Keep it up!
[Galaxy S I9000 Android Development] mialwe:
Thanks guys.

pikachu01: Yes, I intended to just update my latest sources (only changes concerning Newmails ondemand/cpufreq-patch), something got messed up. I'm still learning about Github but this huge amount of "commits" was not intended.

[EDIT: Better now. /virt was the problem, still not cleaned completely. But the commit is accessible now.]

If you happen to read this answer - I saw a post of yours about LMK and the only kernels/tweak scripts setting Android/Linux LMK equally beeing Talon, Supercharger and Thunderbolt - Midnight does this since ~0.7.x, too :)

But I think not too many users actually *use* the LMK presets/manual settings...
[Galaxy S I9000 Android Development] pikachu01:
Yup, I didn't know Midnight tweaks the Dalvik/Linux LMK together. I should take that into account next time when recommending LMK :)

Yeah, with git, you can make the commits atomic so that it's easier to manage.

I.e. if you added a bunch of files, you can just do a:

git reset HEAD <file>

To unstage a file so that your commits are atomic.
[Galaxy S I9000 Android Development] mialwe:
Thanks for your help, last night I actually used "git revert HEAD", did the trick. Took me a few attempts to get all commits online but everything should be fine now. Still not sure about /virt...

1) reverted huge commit from before-0.8-upload

2) cleaned git-/virt to match local-/virt

3) commited latest changes (1 change regarding SAMPLING_DOWN_FACTOR for Ondemand will actually be in 0.8.1)

4) finally merged my local git- and developement directories which were separated before. Should make things easier, prevent future commit issues and save time...
[Galaxy S I9000 Android Development] pikachu01:
Time to dig into github's goodness. Thanks mialwe for your hard work :)

Must be tough digging through each of the commits. Your tenacity is something to be admired!
[Galaxy S I9000 Android Development] rom08:
Hi mialwe how do we convert to ext 4 now please ?
[Galaxy S I9000 Android Development] mialwe:
@pikachu01: Wasn't *that* difficult. Just took me some attempts to get it right. But my tenacity is also my problem - seeing Talon, Semaphore and all the other kernels out there Midnight is just a small, tiny, personal project with a small userbase and while working on 0.8 the last few weeks there were many days I thought about dropping Midnight. Too frustrating, too much time consuming. But I actually like working on it and restart again and again :)

Btw _ implemented your latest corrected CFS values again in 0.8.1-dev and they seem to work great, thank *you* for your hard work. Midnight used it's own values for a couple of versions which were satisfying but yours work better.

As I want to learn more about LMK - would it be possible to add me to your PM list for some questions? I don't ask much but need some basic information about ADJ-shifting...

@rom08: You can use any other conversion-capable kernel or Midnight 0.7.6 to convert. Most of the time spent on 0.8 was due to multiple attempts to get the EXT4/RFS-conversion to work but I failed every time getting issues with init-interception in the initramfs, graphchoice.c porting or fat.format itself (anyone knows why it formats /data without any user interaction at boot time if present in /sbin ???). I'l ldefinately try again but first have to sort out some issues experienced for a bugfixed 0.8.1 :)

@all: small update about 0.8.1-dev:

- initramfs: JVX modules (nothing else changed)

- initramfs: Pikachu01′ s latest CFS values

- CWM: Supports /mnt/sdcard for compatibility reasons

- CWM: completely replaced /datadata with /dbdata (CWM-zip mounting issues for /dbdata, won't work with 0.8)

- kernel: Ondemand/SAMPLING_DOWN_FACTOR implemented (performance, stability).

- Midnight-app: first steps done, but worried about this. I think the app will come without backup/restore/install-zip features.