yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] pikachu01:
It's ok if development is not frequent and massive. Small updates every now and then is good to make progress. And your userbase being small or big isn't really a factor. It's the sharing that actually makes the sum of the whole parts better in the long run.

Hence, some might not use your kernel, but having one more head in researching what's best for the i9000 is more than 2 times better than none at all. :P

Hence, why I also try to chip in my support to as many devs as possible :)

Edit: Added you :) PM me if you have questions. It's cool too if you post in my Android Optimization Tips thread, that way all replies will benefit the community. :)
[Galaxy S I9000 Android Development] brk:
Thanks for your hard work with this great kernel. Just installed 0.8.0 and I'm really enjoying it, it is a top class kernel. Thanks again.
[Galaxy S I9000 Android Development] betoNL:
Great

WOW, just noticed your kernel got 6 frequencies !!

And what a great full-featured Built-in CWM :)

If it had a BigMem version it could become my favourite kernel :

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

Nice work ! Congrats ....
[Galaxy S I9000 Android Development] -freedroid-:
Great work! Just updated from 0.7.6. :)
[Galaxy S I9000 Android Development] Тhe Dark Knight:
thank you very much for the kernel. i've used semaphore, talon and other kernels but midnight is the best. Especially battery life.
[Galaxy S I9000 Android Development] mialwe:
0.8.2-4 / 2011-12-08

- sources updated

- initramfs: JVZ-module, new CFS values (testing)

- kernel: Ondemand/SAMPLING_DOWN_FACTOR implemented

- cwm: /mnt/sdcard compatibility

- cwm: handles mount for /sbin/mount to prevent issues when mounting from update/CWM-ZIP

- cwm: support for /dbdata mounts, /datadata completely removed

CAUTION: create new backups, old Nandroid

backups containing datadata...tar won't restore your data partition.
[Galaxy S I9000 Android Development] jimbo77:
Big thanks for the Midnight Updates... Your Kernel is really good my friend! I love it...
[Galaxy S I9000 Android Development] georsh:
i was wondering if it is possible to have a big-mem version

as i love ur kernel so much but i always encounter problems with not having enought memory while running a few applications

appreciate your work, and keep going =]
[Galaxy S I9000 Android Development] pikachu01:
Bigmem will only add 12MB more towards your RAM. A measly 3.5% more memory. I doubt that it'll groundbreakingly solve your memory problems. Try using other LMK settings in Midnight if it solves your memory problem.
[Galaxy S I9000 Android Development] me_ashman:
Hi, nice work. Coming from Damiens kernel this is very good.

Ash

Sent via ET and he phoned it in
[Galaxy S I9000 Android Development] mialwe:
Right now Midnights default LMK settings are 8,16,46,55,60,70Mb (you can see the matching ADJs in post #2). In CWM you can select from some LMK presets or manually setup the Mb value for every single slot. Maybe this can be of any help.

I was asked about a bigmem version a few weeks ago but have to admit that due to my always-limited spare time I will not provide different kernel versions (recompiling and uploading does not take too much time but nevertheless it's too much for me, sorry).

Midnight in some early version included Talon's 141Mb settings which worked fine for me but were taken out at a time that some users on another board reported blackscreen issues (I think it was ~Sept/11) and I tried to get rid of anything that could be related to this problem. As the blackscreen issue for those users seems to be resolved (I do not thinkt it was related to the RAM settings) I could try to include those adjustments again - but if I remember right I had no sound with this on 720p video playback...

EDIT: Testing with 342Mb (as a starting point) now, assume there will be issues, 1280x720 video works for at least 30sec., does anyone have a suggestion for test cases? I remember a post about video decoding somewhere...
[Galaxy S I9000 Android Development] mialwe:
0.8.3 / 2011-12-10

- Bugfix: Removed Ondemand/deep-sleep patch, somehow caused frequency to be 800Mhz > 40% time if connected to AC charger and sleeping.

- Disabled SAMPLING_DOWN_FACTOR again, testing

- 341Mb RAM, testing
[Galaxy S I9000 Android Development] betoNL:
Try your best scripting/tweaking/memory management and then run iGO navigation for 30 minutes

Then try the same settings on a BiGMem kernel and run the same RAM hungry app (iGO) for 30 minutes..

You will notice the difference. The sgs is the High-end Android device with less RAM of all......every bit counts.....

But it was said already.......

---------- Post added at 02:55 AM ---------- Previous post was at 02:51 AM ----------

I hope you saw my last post on stratosk's thread (regarding the "frying")

Cheers
[Galaxy S I9000 Android Development] mialwe:
The "frying" == overclocking post (this one) ? Yes I read it (edited my post there accordingly). As I said I'm sure you did not want to sound negative :)

Regarding those 800Mhz when AC charging/Ondemand - I'm still having no idea what causes this, I'll try to contact Newmail, maybe he has an idea as I'm not sure if it was the patch itself or something with the implementation in Midnight. All I know is the issue is gone as soon as I revert the patch.
[Galaxy S I9000 Android Development] roundbelly:
Hi flashed this kernel and i was wondering how to enable EXT4 and what is the best settings for uV ? Sorry still a noob at ext4 and uV
[Galaxy S I9000 Android Development] mialwe:
Hello,

due to serios issues while developing Midnight currently does not support EXT4-conversion (I'll try again as soon as possible :) ). You can use any other conversion-capable kernel or Midnight 0.7.6 to convert if you *really* need EXT4.

There are no "best settings" for UV. Every SGS likes different values. Somewhere here @XDA there is a good post about finding your values, it's about

- setting freq to fixed (min freq = max freq) using apps like setCPU, VoltageControl,...

- slightly adjust UV value

- test stability with some software decoding music or video

- adjust UV more, test again - if instability occurs revert last UV adjustment

- do this for every single frequency

All the best

M
[Galaxy S I9000 Android Development] Тhe Dark Knight:
Excellent update, thanks man :)
[Galaxy S I9000 Android Development] Hell_chief:
Nice kernel! Good joob! :p
[Galaxy S I9000 Android Development] roundbelly:
I don't really need ext4 just trying to boost up quadrant
[Galaxy S I9000 Android Development] bhu1:
Why did u say that due to some serious issues ext4 is not supported. I flashed your kernel on jvz while i was on ext4 and everything is fine and perfect. Very good kernel, rock solid. Will their be any problems which i may face later because of ext4??
[Galaxy S I9000 Android Development] Vanto:
Same here ;) and it runs smooter than Semaphore 2.1.1 [@ least I feel it that way]

but also wanted to ask you guys about going back to RFS via Midnight kernel?

пратено преку GalaxyS!
[Galaxy S I9000 Android Development] cwc289:
He means the conversion for rfs to ext4 not support yet ,but its doesnt means not support ext4 format.
[Galaxy S I9000 Android Development] mialwe:
Yep, only *conversion* is not supported for now.
[Galaxy S I9000 Android Development] Zhengod:
i need an honest answer Midnight or Talon?
[Galaxy S I9000 Android Development] madfix:
1. Semaphore

2. Midnight

3. Talon

;-)
[Galaxy S I9000 Android Development] Vanto:
s

o the question remain

s

How can we convert ext4 to rfs and reviser via Midnight kernel :confused:

do we use some external progy like application or

we have to change the kernel to some ext4 compatible
[Galaxy S I9000 Android Development] mialwe:
This question was answered a few times before (e.g. 2 pages before) and is answered in post #2 (FAQ/help/info), too.
[Galaxy S I9000 Android Development] Тhe Dark Knight:
Midnight of course :) Talon has memory leaks and battery life is not so good as in Midnight.
[Galaxy S I9000 Android Development] jenablinsky:
good!

Hey, good kernel! I'm using it on my ROM!
[Galaxy S I9000 Android Development] faithhh:
nice kernel keep working plz thank you...
[Galaxy S I9000 Android Development] pikachu01:
Only if you enable ZRAM. Disabling it and reducing swappiness to 0 solves it.
[Galaxy S I9000 Android Development] saszseb:
Data transfer via bluetooth doesn't work.

Is it a kernel related, it isn't?
[Galaxy S I9000 Android Development] jenablinsky:
does it has thunderbolt tweaks?
[Galaxy S I9000 Android Development] mialwe:
As I don't have the hardware to test this - I don't know, maybe another bluetooth user can say something about bluetooth/data transfer with midnight? Bluetooth code was never touched during Midnight developement.

No, Thunderbolt is Pikachu01's project, Midnight does not include Thunderbolt, you would have to install it as described in Pikachu01's thread. Midnight uses 3 values of Thunderbolt (CFS) because I think they are very good ones but I try to optimize the Midnight tweaks myself.

Midnight performs it's tweak actions *before* init.d scripts are executed. This way you can use every init.d script you want to use, it will overwrite Midnights settings. Caution: If you overwrite LMK settings with some script they will probably not match the ADJ-LMK-values, to be sure take a look at /data/user.log, LMK section. If you use Midnights CWM LMK menu (presets or manually/slot) the kernel will ensure Android- and Linux-LMK-values will be the same.

EDIT: Actually latest 0.8.3 uses my own CFS values, Pikachu01's settings will be back with Midnight 0.8.4.

EDIT2: Found the lines in newmails Ondemand/deep-sleep-Patch which caused the CPU 800Mhz>40% usage when AC charging (*not* USB!) with previous Midnight 0.8.2-4 (patch removed with latest version):

#ifdef CONFIG_DVFS_LIMIT
+#if 0
if (g_dvfs_high_lock_token) {
if (index > g_dvfs_high_lock_limit)
index = g_dvfs_high_lock_limit;
}
#endif
+#endif

I'm testing the patch without disabling this high_lock_token and it seems to work fine (now I *have* to use Ondemand, miss my tweaked Conservative :) ), I'll try to cantact Newmail again about this.
[Galaxy S I9000 Android Development] karapoutsoglou:
wow,what is that????

i tested it yesterday and it is really good!!!

and i mean really good...

keep up the good work
[Galaxy S I9000 Android Development] stratosk:
I use newmail's patch with DVFS locks since 1.9.0 and works just fine.

If you want to enable again please note that there is also a part of code disabled in /kernel/power/earlysuspend.c
[Galaxy S I9000 Android Development] mialwe:
Yes, I went through the complte patch to isolate this, maybe the reason is that Midnight uses 6 frequencies instead of 5 - I am still looking for the reason the original patch jumps to 800mhz with Midnight...

Tapatalked
[Galaxy S I9000 Android Development] stratosk:
I think that the problem is not 6 frequencies nor DVFS locks.

Can you please try to change this line in /drivers/cpufreq/cpufreq.c

cur_maxfreq = cpu_policy->max; // save max freq

with

cur_maxfreq = new_policy.max; // save max freq
[Galaxy S I9000 Android Development] krosscheck:
Data transfer with bluetooth works. I still move data between notebook and my sgs.

Stock xwjvz with midnight 0.8.3

tapatraced with GT-I9000
[Galaxy S I9000 Android Development] mialwe:
Thanks for trying to help but this results in a compile error (error: request for member 'max' in something not a structure or union). To be sure I'm checking without the max.freq tracker var for overclocing (stock 1Ghz) but the oc-tracking worked fine during all tests.

EDIT: Maybe you are right and there *is* something wrong with my tracker variable. A first test for only a few minutes with 1Ghz stock max and without cur_maxfreq -> 4% 800Mhz, 94% 100Mhz...

EDIT2: There must be aliens in my Thinkpad or something, now it works as you suggested... compiles now, have to test...
[Galaxy S I9000 Android Development] stratosk:
No problem my friend.

Yes, it was a strange error. I use the source with the line I posted and it compiles fine.
[Galaxy S I9000 Android Development] mialwe:
Thanks again stratosk, really appreciate your help :) After testing this today it seems I can put the deep-sleep-patch back into the next Midnight version.

Now I have to hunt those aliens in my Thinkpad, have stolen my Logcat messages (only app messages)...hrmpf.
[Galaxy S I9000 Android Development] saszseb:
Do you use Windows or Linux? I'm on Linux.
[Galaxy S I9000 Android Development] mialwe:
Ok, new day new challenge:

As I want to continue the developement of a small app for Midnight (basic menu structure works, nothing more for now) I *have* to have working Logcat.

The problem: Somehow Logcat messages from applications only are never written to log. I can see generic log messages about the system and copying/starting applications but Log.[e|d|v|w]() woill never produce any output.

Why I'm writing this here: It seems to be kernel related:

- Midnight: No application logcat

- Stock JVZ: Application logcat fine

- Speedmod (latest): No application logcat.

UPDATE: it's compiling logger as a module oO? If logger is compiled into the kernel everything works fine...

UPDATE2: Ensured. At least for Midnight it's logger compiled as module causing this issue. After messing with .config and initramfs Midnight 0.8.4-7 was rebuilt with original kernelconfig from 0.8.3 except compiling logger into the kernel - Logcat now works fine.
[Galaxy S I9000 Android Development] krosscheck:
I'm on windows.

tapatraced
[Galaxy S I9000 Android Development] saszseb:
Tried on Vista, yes, it works.

(Stock XWJW1 and 0.8.3).
[Galaxy S I9000 Android Development] lazy_ursache:
Fantastic kernel! Fast! Just Love It!

Hope you will keep updating for every new rom!
[Galaxy S I9000 Android Development] hassaan123:
Hey i am on jvz custom rom with cf- root with ext4. Should i flash this kernel directly or i should convert to rfs and then flash?
[Galaxy S I9000 Android Development] krosscheck:
u can flash it directly

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] mialwe:
0.8.4 / 2011-12-17

- Bugfix: Ondemand/deepsleep-patch (thanks Stratosk)

- Bugfix: Logcat incomplete when loaded as module

- CWM: 3 touch sensitivity options back

- Initramfs: shortend /proc/mem output in /data/user.log

- Initramfs: JW1-modules

- Initramfs: Pikachu01's latest CFS values
[Galaxy S I9000 Android Development] krosscheck:
i wanna test it :)

"... und Nachts ist kälter als Draußen!"
[Galaxy S I9000 Android Development] filchi756:
any chance to implement BM(big memory)
[Galaxy S I9000 Android Development] mialwe:
In case someone needs this: For zipaligning feature in CWM i needed zipalign compiled as ARM binary but the Android build system is configured to build zipalign for the host only. Found not much information on this, only knew that the zipalign sources are in the CM source tree (thanks Pikachu01 for this). This is how it finally worked for me:

Base: http://www.ailis.de/~k/archives/19-ARM-cross-compiling-howto.html#zlib

1) Compile zlib with the used kernel toolchain

CC=$HOME/CodeSourcery/Sourcery_G++_Lite/arm-2010q1/bin/arm-none-linux-gnueabi-gcc
./configure --prefix=$HOME/CodeSourcery/Sourcery_G++_Lite/arm-2010q1/
make

2) Copy sources: android/build/tools/zipalign to android/external/myzipalign

3) Edit myzipalign/Android.mk (fast & ugly but works patch):

--- build/tools/zipalign/Android.mk	2011-12-18 01:36:45.994230026 +0100
+++ external/myzipalign/Android.mk	2011-12-18 09:02:02.506036372 +0100
@@ -16,19 +16,15 @@ LOCAL_C_INCLUDES += external/zlib

LOCAL_STATIC_LIBRARIES := \
libutils \
-	libcutils
+	libcutils \
+	libz

ifeq ($(HOST_OS),linux)
LOCAL_LDLIBS += -lrt
endif

-ifneq ($(strip $(USE_MINGW)),)
-LOCAL_STATIC_LIBRARIES += libz
-else
-LOCAL_LDLIBS += -lz
-endif
-
-LOCAL_MODULE := zipalign
+LOCAL_MODULE_TAGS := optional
+LOCAL_MODULE := myzipalign

-include $(BUILD_HOST_EXECUTABLE)
+include $(BUILD_EXECUTABLE)

4) add external/myzipalign to core/main.mk after "external/zlib" directory below "subdirs := \"

5) Copy the compiled zlib.a to the lib or lib32 directory of the android-used toolchain (here: gingerbread/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/lib32)

6) Run "make myzipalign" from android build root directory

7) Copy out/target/product/galaxysmtd/system/bin/myzipalign via adb to device as "zipalign" or whereever you want.

Useful information:

http://www.ailis.de/~k/archives/19-ARM-cross-compiling-howto.html

http://www.lindusembedded.com/blog/2010/12/10/the-android-build-system/

http://mytechjaunt.wordpress.com/2011/03/15/build-process/
[Galaxy S I9000 Android Development] mialwe:
No, sorry. No time for another kernel build. I should put that on the 2. post/faq. [EDIT: Done.]
[Galaxy S I9000 Android Development] Sarutobi:
Hello,

i have a Problem to change the Filesystem from rfs to ext4. When i tried it with Chainfire´s EXT4-Manager it don´t work and the Manager show at /system etc. RFS and 0 MB free when i start the Manager.
[Galaxy S I9000 Android Development] nmcc89:
You don't use cf's ext4 manager to convert with this kernel. Mialwe explained a few pages back and on the first post that although the kernel supports ext4 as a filesystem it doesn't support conversion between rfs and ext4 due to problems that occurred with cwm.

If you want ext4 you need to flash another kernel that supports conversion (i.e cf-root, speedmod, semaphore), convert to ext4, and then reflash midnight after
[Galaxy S I9000 Android Development] extralife:
Flash CF-root - convert - flash midnight

... using tapatalk
[Galaxy S I9000 Android Development] zenosteam:
i love this kernel best battery life
[Galaxy S I9000 Android Development] Sarutobi:
OK now it Works fine :) THANKS !;)
[Galaxy S I9000 Android Development] mialwe:
Or use Midnight 0.7.6 to convert which is the reason I left the download in post #1.
[Galaxy S I9000 Android Development] Sarutobi:
Is it possible to Integrate the Converter back in the next Kernel?

Btw. Nice Work! Keep it on :)
[Galaxy S I9000 Android Development] mialwe:
Yes, I'll try again. If you look at the changelog there's a gap of 2 months between 0.7.6 and 0.8.0. This gap was caused by issues with the switch from CWM2.5 to CWM4 and various attempts to get RFS/EXT4 conversion working (which worked fine for /data, /dbdata and /cache but never for /system).

As soon as 0.8.x seems to be "somewhat-stable" and there is enought spare time I'll try again (but will continue working on a Midnightkernel-app, too). Meanwhile you can use any other kernel or MN 0.7.6 to convert filesystems.

Edit: Read you saying "next kernel": No way. Please don't forget I'm doing this in my spare time besides job and family, mostly at night and without payment.

Implementing filesystem conversion is not "point-and-click" programming, it's real work, real debugging, real learning and experimenting, sorry.
[Galaxy S I9000 Android Development] ikkuh007:
Hello,

I read some good reviews about this kernel. But can I flash this kerlenl with odin? On the front page he said that he doesn't know.

If not, how can I then install the kernel? Thanks!
[Galaxy S I9000 Android Development] mialwe:
From post #1.

- I don't say I don't know if it works, I just say I cannot test it. It *should* work :)

- another option (see quote) would be SGS kernel flasher (assuming you don't use Linux)
[Galaxy S I9000 Android Development] saszseb:
There is no need to write "sudo".
[Galaxy S I9000 Android Development] ikkuh007:
Hello,

Well my question was if somebody allready test it with ODIN?

And SGS kernel flasher? How must I do that? A program or in CWM?
[Galaxy S I9000 Android Development] scheichuwe:
Yes.

SGS kernel flasher
[Galaxy S I9000 Android Development] ikkuh007:
Thank you, goonna try to test it

Edit:

Works good till now. Are there apps for this kernel?
[Galaxy S I9000 Android Development] mirash11:
great thanks for a fantastic kernel, after a few moments a test on my ROM I think it is worth recommending, is stable and brilliant;)
[Galaxy S I9000 Android Development] karapoutsoglou:
Brilliant kernel with so many nice and well executed ideas.

I used to use the systemapp remover app but now with the options in recovery,the kernel does whatever i want in my phone.

so much more than a simple kernel.

keep up the good work.
[Galaxy S I9000 Android Development] mialwe:
@saszseb: Jep, "sudo" might not be needed to install with Heimdall, I'll correct this. Something went wrong with my last Heimdall-update and since this time I have to use sudo.

@ikkuh007: What do you mean with "apps for this kernel"? If you are thinking of an app to control some Midnight-settings - I started working on this about two weeks ago but do not have enough at the moment.

For general kernel settings like OC/UV, governor or IO scheduler you could use tools like VoltageControl or SetCPU.

@karapoutsoglou: Thank you very much, nice to hear this.

If you have any suggestions about some bloat-APKs maybe missing in the list(s) feel free to post them :)
[Galaxy S I9000 Android Development] ikkuh007:
I had one more question.

Must the kernel 'settle' to the phone and rom before you see results? I read some good stories of this kernel in case of battery drain, but till now I didn't see it.

Can you tell some more about that?
[Galaxy S I9000 Android Development] mialwe:
Sorry, I don't think I understand your question?

Midnight is meant to save some battery life mainly by using the (little bit tweaked) Conservative-governor instead of commonly used Ondemand governor. Do you say Midnight drains too much battery for you?

Or do you have battery-drain issues and try to reduce the drain by testing Midnight now?

In general - after using CWM for some time or flashing something the batterystats maybe are a bit off (but honestly I doubt that only a kernel-flash makes a big difference).

As I have written this on another board a few minutes ago - this is my personal opinion about reducing battery consumption (use them only if compatible with your type of smartphone usage, as I'm mostly reading mail/feeds/tweets, little bit of www, lot of Tapatalking this works pretty well):

- stay with Midnight-default Conservative governor

- use 2G if possible, not 3G/HSDPA, switch to 3G only if needed

- use Wifi only if needed

- set Wifi standby to "on diplay off" (display off = Wifi off after some minutes)

- reduce display time (as long as your SGS is usable :) ), short display timeouts

- reduce multitasking, close apps whenever possible

- reduce widget count

- adjust auto-updating apps/widgets to use biggest usable update interval

- maybe try undervolting (test for stability, raise UV values slowly)

- try default RFS, not EXT4 filesystem. EXT4 may feel a little bit faster (especially for large file operations like Nandroid backups) but also seems to drain a little bit more battery (at least that's my experience).

Maybe this helps a little bit?
[Galaxy S I9000 Android Development] ikkuh007:
Hello,

I use RFS and not EXT4. And how can I use 2g and not 3g? Where can I configure that?

Greetz,
[Galaxy S I9000 Android Development] cha-ka-lak:
Issue with USB charging

I'm sorry, if this issue has been addressed before. I could not find this topic in the thread.

I experience the following issue when charging via USB connection to a PC:

The SGS is fully charged. Then charging stops and the battery charge drops continuously to 50% and below. :confused:

After I unplug and replug the cable, charging starts again.

I use stock JVZ and midnight 0.8.4.

Thanks

Edit: I use a Thinkpad T420. It might be related to its hardware. I'll try with another PC first.
[Galaxy S I9000 Android Development] pikachu01:
It's the infamous Gingerbread bug/feature that is meant to ensure your battery doesn't spoil in 6-12 months time.

Your battery drains a lot because some apps are causing wakelocks/network transactions when the phone is sleeping.