yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] stanbel:
Yes 3 mentioned scripts was turned on

For now i am, still with this sctipts, and now is 3rd day without reboots,

uptime is 48hours, so on monday i will complete long test (with scripts)

Task manager says 303/343 MB of RAM

After that i will disable init.d and reboot, and will use phone as usual

If I can provide any information about phone, feel free to ask me

Memory Screen from SetCPU:

2 params was not fit to screen :)

VmallocUsed 69640 KB

VmallocChunk 174892 KB
[Galaxy S I9000 Android Development] mialwe:
Thank you very much for testing this and providing useful information. As I'm taking a break from working on Midnight I'll try to get a longer uptime, too. Currently pure Midnight@stock (slightly themed) JW1, 2d,13h, 277/343Mb RAM, no lags.
[Galaxy S I9000 Android Development] ArctiX:
Hey guys, i've used the search tool to find if it was asked before, but it didn't find anything. So can i use the Chainfire's ext4 tool to convert from rfs to ext4? I'm on the newest midnight kernel and JVU stock rom.
[Galaxy S I9000 Android Development] karapoutsoglou:
I did exactly that and had no problem at all.

Do it:)
[Galaxy S I9000 Android Development] mialwe:
Did not try since this post (Nov 11) if I remember right:

To be on the safe side use another kernel or Midnight 0.7.6 (download -> OP) to convert filesystems if you really need it.
[Galaxy S I9000 Android Development] RooceeD:
mialwe,

If I try to run MidnightControlapp, it's always force closed =(
[Galaxy S I9000 Android Development] apsoogos4ever:
which version of midnight for jw1?
[Galaxy S I9000 Android Development] mialwe:
@apsoogos4ever: as stated in first post Midnight runs on all Gingerbread firmwares.

@RooceeD: Strange. Was autorooting successful? You could test this using other root-apps or looking into upper half of /data/user.log (from "install.sh" onwards or just pm me the user.log or attach it here), maybe this is an issue with MidnightControls root detection (sorry, it's my first app).

Edit: No, after thinking about this autorooting should not be an issue as su/Superuser had enough space in /system if MidnightControl has been copied after them successfully. Must be something else. Do you have ADB installed or any other way to send me a debug log (logcat) - in this case I'd build a CWM-zip to activate logcat (just have to copy /sbin/logger.ko to /data/local)...

Edit: Attached cwm-zip to activate logcat - edit #2: removed, did not work.
[Galaxy S I9000 Android Development] RooceeD:
Here is my logcat once again
[Galaxy S I9000 Android Development] mialwe:
Great, thanks. I'll look into this as soon as possible.

Edit: Second one works and the provided lines are perfect, checking the app now, thank you again.
[Galaxy S I9000 Android Development] mialwe:
@stanbel: 3d 9h uptime - no lags, stock JW1, stock Midnight - and no SODs which leads me to the next question:

On another discussion forum some users reported SODs with 0.8.7 (and 0.8.4 as I know now). Here at XDA no SODs were reported since 0.7.6.

As there have been a lot of changes since MN0.7.6 (no SODs) I tried to track things down a liitle bit and need your help here:

Did you experience SODs? If yes, did you use stock Midnight? No init.d-Scripts? Ondemand/Conservative? SIO/NOOP(/VR)? UV/OC?

Data collected about the SODs collected since yesterday (have to count, ~5-6 users reported this I think, maybe this occurs only in rare occasions but I'd like to figure this out):

- with SIO, not with NOOP, VR <-------- SIO ???

- with 0.8.4 and 0.8.7

- with 1Ghz and 1.2Ghz

- with and without undervolting

- with Ondemand and Conservative

I'll try to reset some settings/tweaks back to 0.7.6 versions and I'm not sure about SIO - but for now it's the only factor consistent in all SOD reports.
[Galaxy S I9000 Android Development] stanbel:
mialwe, what is SOD?

---------- Post added at 05:48 PM ---------- Previous post was at 05:42 PM ----------

Two hours ago i have a reboot

I working with google maps, and phone become laggy and din't respond to hardware keys

And after that make a reboot (without warning), but it was very short rebot (short in time), after that it's loaded (works about 10 secs), but then short reboot again, and again.

During this short reboot I used Power menu and make normal reboot (takes ~2 times longer), and all good for now

SIO

0.8.7

LMK MIDNIGHT

1GHz

undervolt(0,0,10,20,50,75)

ondemand

+3 Prev mentioned scripts from Thunderbolt
[Galaxy S I9000 Android Development] mialwe:
SOD means SleepOfDeath = completely black screen but SGS working (you can hear notification sounds, ringtone,...).

I'm not sure about those SODs and Midnight as there are not many reports compared to the download count but maybe not all users report them and simply switch kernel :) But if this IS an issue with this new Midnight version I'd like to find it. That's why I asked for reports here at XDA (no SODs reported since 0.7.6).

About your reboot - sounds like an UV issue to me (reboot = typical "symptom" - edit: hotreboot (short) - never had this caused by uv, only "normal" reboots) but the continuous reboots are strange as your uv values aren't THAT aggressive. Maybe just try without undervolting and if this works slowly increase uv values.

I'm still trying to reproduce the lag issue you reported (first time my uptime is > 3 days for months :), no flashes, no experiments ) - no lags. RAM is 284/343. gMaps opening fast as usual.
[Galaxy S I9000 Android Development] hippo_potamus:
Installed since 0.8.7 was released, no SOD so far. I don't do UV.
[Galaxy S I9000 Android Development] mialwe:
That's good to hear. And before I forget again - big, big thank you for your donation. Thank you.

Currently I'm thinking of reverting some of the optimizations/code changes in 0.8.7 and changing the CFS to be a little bit less aggressive (latest values were used in 0.8.4 and 0.8.7) because of the issues reported on the other discussion forum but I'm not sure - no reports of SODs or other issues here at XDA after ~1400 downloads until now, so maybe I'll wait a little bit longer.

Update on the MidnightControl FC RooceeD reported: We found out (thanks for your help RooceeD) that his ROM does not provide "/system/bin/cat" which is used by the app. MidnightControl will be updated for this in next release.
[Galaxy S I9000 Android Development] karapoutsoglou:
No sod here too, and believe me i had so many sod's before...

i have overloaded the phone,downloaded all the sd files for gameloft,some games of gameloft crash with this kernel like asphalt 6 but i think that these games are just bad written....

generally the kernel is super stable,it even loads spb shell 3d and when the phone crashes,the bootis normal and no fancy things like eternal bootloops and losing cwm.

edit................

and one last thing.

your option in recovery to boot just once with nothing loaded in the app is pure GENIUS.

you cant imagine how this saves people...!!!!
[Galaxy S I9000 Android Development] cha-ka-lak:
Just noticed the midnight apps. Nice work!

Bought you a beer. I really appreciate your work - thanks

Sent from my GT-I9000
[Galaxy S I9000 Android Development] mialwe:
@cha-ka-lak: Thank you very much, really appreciate it.

@gabriel_4000: Do you have enough free space on your /system partition? The app will be copied to /system/app during boot process but this would fail if there is not enough free space. Btw - at OP are three *screenshots*, it's only one app, don't expect too much :)

About: 1.2Ghz - I don't use setCPU for a few months now, tested with VoltageControl a few seconds ago and VC correctly shows 1.2Ghz.

About front cam: Well, I was waiting for JVU/front cam reports (even wrote it to the changelog -> 343Mb RAM) but you are first :)

As I do not use JVU (JW1 stock odexed, front cam working fine) does the front cam completely refuse to work?
[Galaxy S I9000 Android Development] karapoutsoglou:
just bought you a beer man.

i switched from the heavy spb shell 3d to mx home and all gameloft games run like hell.

not a single problem with this kernel.
[Galaxy S I9000 Android Development] mialwe:
Would you mind posting or pm'ing the /data/user.log? Or only the relevant lines (starting from "install.sh" output), here is a example from a working install:

START '20_install.sh'
remounting /system readwrite...
/system/xbin found, skipping mkdir...
/system/etc/init.d found, skipping mkdir...
cleaning su installations except /system/xbin/su if any...
/system/xbin/su found, skipping...
/system/app/Superuser.apk found, skipping...
installing /system/app/MidnightControl.apk
checking /data/local/logger.ko (Logcat)...
remounting /system readonly...
EXIT '20_install.sh' (0)

Frontcam: Ok, that's the same behaviour I had on JW1 after lowering certain memory constants too much (for 345Mb free RAM) - I raised it again for Midnight 0.8.7 just to fit JW1 front cam needs and ended up with 343Mb free RAM. Seems JVU needs more memory for just the front cam, too - not only for taking pictures while recording movies.
[Galaxy S I9000 Android Development] stanbel:
mialwe, I have got a reboot again (uptime was about 30 hours), so i disabled all Thunderbolts scripts and watching again.
[Galaxy S I9000 Android Development] pikachu01:
When you got the sudden reboot, what were you doing?
[Galaxy S I9000 Android Development] stanbel:
mialwe, nothing

Phone was on the table, and when I took it, "please enter PIN" was displayed, thus my conclusion - reboot

BTW, several people in russian-spoken forum also says that last version is more unstable, then 0.8.4
[Galaxy S I9000 Android Development] mialwe:
Thank you for reporting this. I think this are enough instability reports for this version - it is not a really high count of similar reports but they are definately there so I will revert some of the changes made for 0.8.7 and release the next version ASAP.

Edit: testing the "reverted" version now for a few hours... and unsure again about leaving 1.2Ghz activated...maybe I'll finally drop it as CONFIG_KALLSYMS_ALL is activated again now and everyone wanting to overclock can use Tegrak app again...

@gabriel_4000: I don't know Astro but using RootExplorer I can simply navigate to /data and work with user.log.
[Galaxy S I9000 Android Development] mialwe:
Should be right there (no issues reported with this for months), it's created every time you boot with Midnight kernel:
[Galaxy S I9000 Android Development] mialwe:
Sorry, forgot something: I don't think it's one of Thunderbolt's scripts causing instabilities, I really think it's one (or more) of the kernel source changes since 0.7.4.
[Galaxy S I9000 Android Development] karapoutsoglou:
i am no programmer mialwe but be carefull not to make an unstable new version.

it had happened in numerous other kernel devs...

this version is rock solid.
[Galaxy S I9000 Android Development] saszseb:
I don't understand it. Pls. explain it.

Thanks.

Sent from ICS_TH_Build15, stock kernel
[Galaxy S I9000 Android Development] mialwe:
@karapoutsoglou: no, I don't think reverting changed code since 0.8.4 would cause *more* instability (as part the sources are reverted to 0.8.4 state). But if any of the newer 0.8.7 changes caused those reported instabilities there might be a slight chance to fix this with reverting suspicious commits and maybe enable it in coming releases again step by step. As long as users are reporting instability we cannot say it's "rock solid".

I've done some reverts today and everything seems stable (but I did not have any issues before, too). I'm testing some new CFS values, too, which may be a little bit less aggressive. Don't get this wrong, reverting some of the new changes does not make the kernel completely different, it's source will just be more similar to 0.8.4. RGB/brightness options and MidnightControl will be unchanged.

For anyone interested: I'm using

echo 3000000 > /proc/sys/kernel/sched_latency_ns
echo 500000 > /proc/sys/kernel/sched_wakeup_granularity_ns
echo 500000 > /proc/sys/kernel/sched_min_granularity_ns

for testing since yesterday - no issues yet. Those values are somehow *between* 0.8.4/7 and stock settings.

@saszseb: Midnight CWM has an option right in the main menu to trigger an "app settings block" for exactely one boot process - if users have set an option in MidnightControl which leads to bootloops (e.g. too aggressive UV, phone does not like 1.2Ghz,...) they can just reboot to CWM, enable "block app setings once", reboot with default settings (as app settings will not be set during this one boot process), correct their settings in MidnightControl and that's it.
[Galaxy S I9000 Android Development] mialwe:
Nice it finally worked (user.log, too?).

Besides overclocking to 1.2Ghz and the option to switch from Conservative CPU governor (default) to Ondemand (more performance, less battery, default for most other kernels) MidnightControl does not contain any options to further increase performance or RAM. You can load additional modules (only) if you need them, enable Android Logcat if you need it, enable init.d script execution if you need it and choose your preferred IO scheduler, lowmemorykiller preset etc.

Basic infomation about the options is in the help menu (menu button), for more information just look into many XDA posts about schedulers, governors, overclocking, undervolting,...

Front cam: You are on JVU, are you? Front cam works until JW1, JVU needs more reserved memory for this to work (why??) and I cannot evaluate correct min. reserved memory needed as I'm on JW1 for now.
[Galaxy S I9000 Android Development] mialwe:
0.8.8 / 2012-02-07

- app: fix for users not having /system/bin/cat

- app: fixed Midnight kernel version display

- kernel: reverted some optimizations after instability reports

--> side effect: 342Mb RAM

--> side effect: apps using KALLSYMS_ALL should work again

- kernel: raised 1.2Ghz arm.voltage 1310mV -> 1325mV

- initramfs: changed CFS values, testing...

[download]

With this version I reverted some changes which could be the cause of the instabilities reported on other boards (reports kept coming in until today so I *had* to upload this version - Midnight aims for stability so all those issues are a no-go).
[Galaxy S I9000 Android Development] malcho:
Nice to see this kernel is in development.

Keep up the good work
[Galaxy S I9000 Android Development] ChunLi:
I will always use midnight kernel on my roms! (GamerzRom)
[Galaxy S I9000 Android Development] Soyuz 3:
@mialwe

Thanks a lot for the new version 0.8.8! For me it works as solid as 0.8.7 but that's probably because I don't use apps who use the 'KALLSYMS_ALL'. Also the adjustments to less aggressive settings didn't change the great overall responsiveness (in terms of user experience) of the kernel.

Once again, thanks for the hard work!
[Galaxy S I9000 Android Development] Тhe Dark Knight:
Colors in 0.8.4 were much better. Now it's like voodoo colors :(
[Galaxy S I9000 Android Development] karapoutsoglou:
rock solid! keep em coming
[Galaxy S I9000 Android Development] Soyuz 3:
@mialwe

I'm sorry to report but over night I suffered my first SOD with midnight kernel ever. My phone was in airplane mode on charger. If I can assist in any way to trace back the problem please let me know.

My phone is running stock XWJW1 with Boeffla-Mod 2.0, I slightly UV (0, 10, 15, 50, 75, 100) witch never caused problems before (=>0.8.7).
[Galaxy S I9000 Android Development] pikachu01:
Try not UVing and see if the SOD occurs or not. Kernel changes can also affect how much you can UV sometimes.
[Galaxy S I9000 Android Development] Soyuz 3:
@pikachu01

Thanks, I'll lower the UV of the 100Mhz to -75mV instead of -100mV and see how it goes.
[Galaxy S I9000 Android Development] pikachu01:
Best is to use my guide for UVing:

- MX Video Player with software decoding with these files:

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

- Limit frequency to the one you're testing (min/max to that frequency)

- UV until the file plays for 10minutes without hangs

- Move on to the next frequency.
[Galaxy S I9000 Android Development] mialwe:
Just to be sure as you left it on charger - if it was a SceenOfDeath - battery was ok?
[Galaxy S I9000 Android Development] Soyuz 3:
@mialwe

It was a SleepOfDeath, the phone would not wake up. The battery was ok, the temperature was normal and after holding the on/off button for 10 seconds the phone rebooted and worked as usual.
[Galaxy S I9000 Android Development] stanbel:
Unfortunately, got 2 reboots

first - phone become very laggy and I reboot it (see memory status on picture)

and second - again phone freeze in Goggle maps (when I start Locator and phone connecting to servers to get information about my position and my friends. This was via cell network and usually takes up to 30 secs and almost every time phone is laggy at this time)
[Galaxy S I9000 Android Development] mialwe:
Sorry I cannot reproduce (or even try to reproduce) your issues as I am testing ICS for a few days now - no Gingerbread phone available. Are you sure this is a kernel issue? Do you use any undervolting or 1.2Ghz? Stock ROM? Midnight default LMK preset (starts killing unused processes @65Mb)?...
[Galaxy S I9000 Android Development] saszseb:
Eventually making a kernel for ICS?

Sent from CNA_1.3.3, Semaphore 0.8.1
[Galaxy S I9000 Android Development] stanbel:
mialwe, what do you think: i should try other kernel or another version of Google Maps?
[Galaxy S I9000 Android Development] mialwe:
Not "officially" yet. I'm doing some experiments, have to get used to ICS first... as I'm quite satisfied with ICS (and I had to remove some sources I need for Gingerbread-CWM to free some space on my small 64Gb SSD) Midnight-ICS is the only option for me right now. But this will take some time. CWM+slightly modified test kernel works. Maybe I'll post test versions once Midnight base functionality + MidnightControl are working.

@stanbel: Depends on your setup:

- all stock -> switch kernel and test

- using overclocking/undervolting -> stock freq. and volt and test

- using custom tweaks/init.d scripts -> disable and test

- using custom gMaps -> disable and test
[Galaxy S I9000 Android Development] hippo_potamus:
Mialwe,

Could you advice which ICS rom you're using. I'm going to try one and would appreciate your recommendation.
[Galaxy S I9000 Android Development] krosscheck:
Look for Slim_ICS...

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

Gesendet von meinem GT-I9000 mit CM9 ALPHA
[Galaxy S I9000 Android Development] jocke_lulle:
I can't believe in didn't find this kernel earlier!? Everything works perfect, fast and smooth. The midnight app is great and the colors look beautiful! For sure I'm gonna stick to it until i switch to ics.

And then I'm gonna look for midnight-ics kernel:-)

Thanks
[Galaxy S I9000 Android Development] syamsoul:
Thanks for great kernel but i cant take picture using front camera
[Galaxy S I9000 Android Development] Jose_Paramore:
Nice kernel! I'm running it at 1200mhz, it is the only thing I changed. Conservative Governor, SIO scheduler, stock voodoo color, stock brightness levels... all is working flawessy, also I noticed a better 2D and 3D performance (only a bit, but hey, it's nice ;) )

I'm running it with GamerzROM 6.2, will report back in a couple of days if it is stable and so on (I believe yes :) )

GREAT WORK!

PS: I also love how led backlight works on this rom... :cool:
[Galaxy S I9000 Android Development] mialwe:
I'm currently using Slim-ICS as krosscheck said (thanks krosscheck, I'm quite busy these days). I cannot give any advice because Slim-ICS is the only ICS I tried - I'm quite satisfied for a few days now, still testing (but I *think* I'll use this for some more days:) ).

@syamsoul: That's because I used JW1 firmware on my SGS. JVU (I guess you use JVU?) needs more reserved memory to save pictures via front cam. As I could not test with JVU the reserved memory config was adjusted to

- not stop picture saving @ JW1

- give as much free RAM as possible.
[Galaxy S I9000 Android Development] mialwe:
Glad you like Midnight :)

I wonder if you are talking (quote) about that tiny modification that gets overwritten all the time via some service/app I haven't found yet after booting up if I try to adjust it @ICS...

Edit: Sorry, you were talking about the ROM. So that's something different. What does GamerzRom do to the led backlight?
[Galaxy S I9000 Android Development] Jose_Paramore:
Because of that you have 342mb of ram instead of 337.

---------- Post added at 08:00 PM ---------- Previous post was at 07:55 PM ----------

In fact, I was talking about Semaphore kernel. It is the kernel used in GamerzROM. With this kernel (or Samsung stock one, for example) when you touch leds and then you touch the screen leds keep on... with your kernel, leds switch off after a second, it doesn't matter if you're touching the screen or not. I love this! :p
[Galaxy S I9000 Android Development] mialwe:
+1 :) Glad you like it. Midnight uses a small timeout of 0.5sec as I found the default timeout by far too long - especially at night.
[Galaxy S I9000 Android Development] syamsoul:
ohh yeah..almost forgot about that...anyway thanks mialwe...willing to makw one for JVU? :-)

Thanks jose... +1 jose for the touchkey timeout. :-) so annoying when it stay on especially in dark..
[Galaxy S I9000 Android Development] saszseb:
The LEDs switch off on Semaphore,too.

Sent from CodeNameAndroid_1.3.3
[Galaxy S I9000 Android Development] jocke_lulle:
I have been running 0.8.7 since Monday and i have had 2 black screens (the phone was off). I'm running odemand, sio, ext4, midnight lmk, thunderbolt 2.5.1 (main script only), surface jw1 rom.

I have flashed 0.8.8 now. I hope it will fix the issue because this kernel is the best I have tried.
[Galaxy S I9000 Android Development] mialwe:
@saszseb: Yes, but I reduced the timeout in Midnight so they switch off after 0.5 sec. Never understood why the leds have to be lit for such a long (stock) time.

@jocke_lulle: Thanks for reporting, I should remove 0.8.7 from downloads. No issues reported for 0.8.8 until now, reverting some of the tweaks seems to have fixed the issue.

I'm still experimenting with ICS (Slim-ICS) and some Midnight changes ported to Teamhacksungs kernel + ICS-ported MidnightControl which both seem to work fine. But I'm not sure if I'll continue using ICS or switch back to 2.3.6. Tending to ICS...
[Galaxy S I9000 Android Development] saszseb:
We are now on 4.0.3. Android 5.0 of Google is coming on summer.

Sent from CNA_1.3.3
[Galaxy S I9000 Android Development] mialwe:
=> continue using ICS I assume :)
[Galaxy S I9000 Android Development] saszseb:
Good decision.

Sent from CNA_1.3.3
[Galaxy S I9000 Android Development] stanbel:
mialwe, I am testing last version, previously i have told about reboots and freeze with Google Locator. With version 6.3, it's good, and no reboot :)

Only wish - can you add new setting in your control application

One new LMK value, something between stock 48Mb and Midnight 65?
[Galaxy S I9000 Android Development] robo116:
strange thing

Hello

Yesterday after a phone call i pressed end call nothing happend.

The screen stays the same no response at all.

Had to pull the battery so far so good try to start te phone it came so far as

the galaxy screen and the screen keeps blinking with intervals about one second per interval.

Have wiped the cache and dalvik etc etc no luck.

Flashed the kernel again no luck flashed another kernel no luck.

At the end i had to start up odin flash the stock again and version 6 again.

So i have now a clean phone.

But i hope this one a one time glitch.

Regards
[Galaxy S I9000 Android Development] mialwe:
Thank you for reporting this, to investigate this I would need more information,

- are you sure it's kernel related?

- did you use a stock ROM?

- which kernel version?

- any custom themes, modifications?

- any init.d scripts active?

- UV, OC, governor?

First thought is some kind of filesystem corruption...