yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Fenvarien:
I never flashed with the usb cable plugged in and those bootloop issues quite often. But let's not fill this thread with bootloop stories ;-) There's an extra thread only about this problem.

http://xdaforums.com/showthread.php?p=25496241

... tapatalked
[Galaxy S I9000 Android Development] mialwe:
I give up explaining this. There's a post about 2 pages back which explains why I will not do what you just suggested.

You can open a thread and do this if you want, no problem.

Now I'm getting really angry. I missed a detailed explanation about how Odin works and I can fix it myself this way ???

Before I have to go to work, some Initramfs info as requested (this is copied from our sources):

# CM9 currently uses an init system with two separate initramfs

# images which are packed into the kernel image at compile time.

# During every boot process the needed initramfs image (recovery

# or Android) gets extracted and the boot process continues using

# the freshly extracted initramfs.

We are not sure but we thought packing and extracting separate boot images for recovery/normal boot images at every boot could be the reason, maybe something goes wrong withing this process. So we decided to build an initramfs/init that does *not* have to unpack initramfs images at every boot. I'm not sure about it but until now I did not see new bootloop reports.
[Galaxy S I9000 Android Development] Kocai:
I think you misunderstood Fenvarien post. I believe his post was a response to jacobuscuracao. It was not meant for you....
[Galaxy S I9000 Android Development] Fenvarien:
Mialwe, you completely misunderstood my intention - I tried to support your position! I answered to Jacobuscuracao's posting. Please - read my text again without anger :-)

Grüße aus dem wilden Süden,

Fenvarien

... tapatalked
[Galaxy S I9000 Android Development] malcho:
Status update!

My case.

Flash latest nightly and boot rom.

Power off.Go to download mode,flash midnight via odin.

Everything ok.I didn't loose modules folder.

Thanks mialwe.I guess i done something wrong on previous flash.
[Galaxy S I9000 Android Development] Fenvarien:
I tried flashing midnight on the latest CM9 nightly with Odin too (usually I take Heimdall).

Odin works flawlessly and I encountered no further problems with the modules folder.

... tapatalked
[Galaxy S I9000 Android Development] mialwe:
So sorry Fenvarien, really, really sorry.

Yes, I completely misunderstood your post. That happens if I'm angry anyways and just dont read the text you quoted and then write too fast.

I'm really sorry and apologize for this.

Not a good day today, now I'm waiting for the next bad thing to happen, started this morning, continued at work and now I'm waiting... :(
[Galaxy S I9000 Android Development] adytum:
Kudos for being such a gentleman!

(I'm having one of those days too. One of my main work tools, a really expensive bass guitar, fell over from its stand and its neck cracked. Later I spilled a cup of coffee on my keyboard. Great. So you're not alone!)
[Galaxy S I9000 Android Development] habylab:
Ouch, that's not good!

Sent from my Galaxy S running Slim ICS 3.6 and Semaphore kernel from my XDA Premium app.
[Galaxy S I9000 Android Development] Fenvarien:
No problem Mialwe, you are a great dev and a gentleman! I hope the rest of your day was good, pleasant and without further trouble ;-)

... tapatalked
[Galaxy S I9000 Android Development] mialwe:
Yes, got better. Playing with my kids complete afternoon... no job, no kernel, no nothing... :)
[Galaxy S I9000 Android Development] slaphead20:
Quite right too, don't miss those years, they are more precious than anything, and they pass so damn quick, believe me :)
[Galaxy S I9000 Android Development] Jaggle:
Yep that's so thru.

Verstuurd van mijn GT-I9000 met Tapatalk
[Galaxy S I9000 Android Development] jacobuscuracao:
oh shucks are we in a thread with old geezers here or what?

it's friday afternoon and I know for sure I'll have a couple of beers and then be in bed by 9 anyway or falling asleep in front of the television in the lazy chair .... not like 25 years ago anymore :) but before that I'll certainly spend some time with the kid.

but life is still fun!

and I'll try to find some time to learn about kernels and whatever language you guys write them in (pls I hope it's not Java)
[Galaxy S I9000 Android Development] stratosk:
Fortunately it's pure C
[Galaxy S I9000 Android Development] mialwe:
...and Java isn't *that* bad anymore :D
[Galaxy S I9000 Android Development] H-Body:
Is there only an Odin-version of your newest kernel? Cant find a CWM-flashable one in the OP?! :)

Sent from my SGS using CM9!
[Galaxy S I9000 Android Development] Bejda:
Oops I thanked you involuntary :)

Not in the OP but a few pages back (93/94?) zip packed by users. Read discussions there to know more about this, i didn't follow this matter closely ;)
[Galaxy S I9000 Android Development] TheeWolf:
I'm sorry, I assume this has been answered already, but I have to ask.

There is a CM9 version containing 372 RAM, and the LR version...

If I flash CM9, can I flash the LR version?

As you might have guessed, I want it because... more RAM. Will there be something that will not work? (except for 720p video, I will flash the patch).

Thanks!
[Galaxy S I9000 Android Development] mialwe:
Some users reported sucessfully patching CM9 with F4K's patch. If you want to use the patch there might be issues with sdcard/externel-sdcard mounting but I remember users reporting using LR with a patched CM9 without issues.
[Galaxy S I9000 Android Development] TheeWolf:
Hi,

Here is the reason why I asked that question.

I staying as much updated as I can with everything that goes on around in the ROM area. I understood that CM9 now uses a different memory configuration (am I correct?) and I assume that this is the reason you published a CM9 version (again, am I correct?).

So, the reason I asked is, I was afraid that flashing the LR version on CM9 ROM would pose troubles, far more concerning 720p video (maybe bootloops, reboots, the device suddenly set on fire :) I don't know).

If the only issue here is 720 video then its fine, because from past experience, flashing the patch seems to make it work).

Again, I know that this is clear to you and other users, but I need to be 100% sure I won't do anything that will do any damage.
[Galaxy S I9000 Android Development] H-Body:
Thank you :-)

Sent from my SGS using CM9!
[Galaxy S I9000 Android Development] mialwe:
Hehe, you can't be sure using custom ROMs and kernels :)

- RAM: As long as you use the F4K-patch video *should* work as reported by other users, never tested this myself because I use the CM9 version for CM9.

- other changes: for CM9 a few lines of code in the initramfs must be changed to support the internsl/external sdcard mount switching option of CM9. As CM9 uses internal=/sdcard and external =/mnt/emmc as default setting the LR kernel might work your you but the mentioned CM9 option will not + I havent tested myself (as I use the CM9 version for CM9 :) ).

- EDIT: The CM9 version contains the complete changes Pawitp made for RAM/video including some fixes not included in the LR-patch krarvind introduced to the i9000 community. This maybe prevents video issues on CM9+CM9 mnics but not if used CM9+LR mnics.

Why are 14Mb more RAM that important to you? Memory heavy apps? I had never issues with 372Mb as I think the ICS lowmemorykiller does work really nice (at least for me).

Trying LR on CM9 will most probably not damage anything and you can test what works and what does not. You can change to MNICS-CM9 at any time if something goeas wrong using LR+patched CM9.

As I don't use this combination this is as much information as I can give, sorry.
[Galaxy S I9000 Android Development] TheeWolf:
Hi,

First of all, thanks! Trust me, thats enough information, you could have just written it all in one line but instead chose to elaborate - I really appreciate this.

Why 14Mb more RAM are important? I don't know... I guess I just love seeing as much RAM as possible free. Brings a smile to my face :). Also I try to avoid installing memory heavy apps, and in general install as little apps as possible (so device would be more free, faster, etc...).

So from what I understand, the two advantages of using the CM9 version are:

1. Support of switching the internal and external SD cards - Does it really do anything important, or is it just a matter of switching folders as much as file explorers are concerned? Or does it somehow speed up the phone?

2. Fixes made by Pawitp - this convinced me to use the CM9 version.

Thanks again!
[Galaxy S I9000 Android Development] rtfpessoa:
Java is the best language....is fluffy.

C is much more complicated (low level)

C++ is C more fluffy...hehehe
[Galaxy S I9000 Android Development] jacobuscuracao:
Java needs a virtual machine which makes it inherently less efficient then any other language

I know C is complicated, but that is how you write operating systems. Business applications, no. Operating systems and kernels, yes.

For business applications most stuff is still written in Cobol or RPG, because it's fast and reliable and relatively simple and easy to debug
[Galaxy S I9000 Android Development] rtfpessoa:
Thats the problem of java.

C# is almost java and faster.
[Galaxy S I9000 Android Development] mialwe:
C# is .NET/MS only, is it? Just curious.

@all: Sorry for offtopic but that's interesting, too :)

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

MNICS, next one:

- fast_charge will be back

- I'm currently experimenting with a no-app version containing the important switches in CWM (as I don't play with the settings all the time I prefer to set them once via CWM and then just forget them, currently available toggles: 1.128Ghz, NOOP, Ondemand, touchwake, 512Kb read_ahead and fast_charge) + menus for basic undervolting profiles and vibration intensity levels.

- init.d is still there if one wants to fine tune some option using a script oneliner.

MidnightControl in this version is a nightmode toggle only (no UI, tapping the icon just en/disables nightmode).

This way all important features are accessible via CWM (including basic undervolting profiles), there are no more doubled options for ROM/kernel like for the colors, gamma, CPU,..., for BLN I'm back to BLNControl again.

This approach seems to be more "clean" to me and works just like Midnight-Gingerbread in earlier versions without too many options packed into CWM. Somehow.
[Galaxy S I9000 Android Development] Mr.AFK:
1. best batterylife normally you get with default settings (or 800MHz as max CPU in the next version fixed)

2. night toogle: you can choose your nightprofile first:

if you set the brightnesslvl to 1 you get the MINIMAL Stockbrightnesslvl

if you set the brightnesslvl to 5 you get DARKEST Brightnesslvl, only for dark enviroment without getting blind. :D

i choose for day/night always lvl4. On realy sunny days i toogle off the nightmode via 1klick :cool:
[Galaxy S I9000 Android Development] dark_knight35:
Devil uses int.volt of 1150 and arm voltage of 1350mV for 1.2Ghz
[Galaxy S I9000 Android Development] mialwe:
@mr_afk: Sorry, no color/brightness profiles in Midnight-ICS, thats a Midnight-GB-only feature. Just default-mode and night-mode toglle for Midnight-ICS. I want to keep this as simple as possible.

@exavantz: Nightmode *is* dark, probably unreadable at day/with bright environment. Its purpose is to be used at night without environmental light.

@nmcc89: The 200Mhz/NSTools issue is not kernel related, has been reported a lot of times here at XDA.

@dakr_night35: Thanks, maybe that's the reason. Midnight uses the "stock" 1100mV for int.volt for 1.2Ghz, too. Maybe I should slightly raise this but I'd prefer 1125mV first (used it with Midnight-GB).
[Galaxy S I9000 Android Development] dannyglover:
same as other bugs. you need to toggle off data, wait a while, then you can switch bands. At least I found that is what works for me. Was a common problem back on Miui too. Or try switch out your radio. I'm on JVU and that works using the above method.
[Galaxy S I9000 Android Development] saszseb:
Glitch and a modded Devil kernel use 100 MHz/NSTools.

Sent from MIUI-ICS
[Galaxy S I9000 Android Development] mialwe:
Thank you :)

Just had a little bit of time and looked into this, seems to be this commit: https://github.com/mialwe/samsung-kernel-aries/commit/ed00c113883db367669b0c129aa60b01ca6124ed (4 months ago, stock kernel).

So min_freq will be set to 200 if GPU is active (e.g. while actively swiping screens), min_freq is set to 100Mhz if GPU is not used (screen off or display on without activity like swiping, animations,...). That's the reason why 100Mhz still show up in CPUSpy - it *is* used. As battery life is ok and 100Mhz are still used I will not change this. If you want to be sure try checking the output of sysfs like this while swiping screens or not touching the screen:

# swiping screens
adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
200000
# dont touch
adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
100000
adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
100000
adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
100000
# start swiping screens again
adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
200000
# don't touch
adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
100000

I don't know if the min_freq Mhz displayed by NSTools are refreshed after some time (but if I remember right I read somwhere that it is *not*) but when starting NSTools you touch the screen, GPU is active -> 200Mhz min_freq, displayed by NSTools. If it does not refresh it will continue displaying 200Mhz even after min_freq has been set to 100Mhz again while GPU is inactive.
[Galaxy S I9000 Android Development] saszseb:
Always 100 MHz. is showed up whilst I'm posting in Tapatalk, some apks are open.

Sent from EliteV7.1
[Galaxy S I9000 Android Development] mialwe:
No doubt about that, maybe other devs revert this patch. As midnight correctly uses both 100mhz AND 200mhz I will not revert it for now just because an app does not refresh the displayed value.

tapatalked...
[Galaxy S I9000 Android Development] bhu1:
yeah, true. ur app has everything needed. ;) gonna test for 2 more days then will use it in the rom, :D
[Galaxy S I9000 Android Development] BYRoN_ITA:
Just flashed on SlimICS 2.9. First impression is good : 1) simple as SlimICS ROM without thousands of options :) 2) It seems that this kernel helped the video playback of MP4/MKV files. With SlimICS stock kernel the video playback was a little choppy but now the same files are smooth. So thanks :)
[Galaxy S I9000 Android Development] RooceeD:
Thanks mialwe! =)

This kernel is really fast and per night only 1% left =)
[Galaxy S I9000 Android Development] lucainno:
thanks for new Kernel.

I have tested in miui4 works great
[Galaxy S I9000 Android Development] DerTeufel1980:
Please stop it. Glitch has removed the limit of 200 MHz while gpu is active, and the "modded" kernel is just to old to have this limit.

Sent from my I9000 running Android 4.03
[Galaxy S I9000 Android Development] pxrave:
great kernel ;) put i hope you will develop the official version (gingerbread) too
[Galaxy S I9000 Android Development] GreenSGS:
Thanks Mialwe for update,installing now.
[Galaxy S I9000 Android Development] habylab:
How is the battery life on this considering it doesn't have didle? Thanks, sounds great!
[Galaxy S I9000 Android Development] jocke_lulle:
Batterylife seems good to me so far but it is too early to tell (flashed 0.7.4 yesterday). Didle only benefits you when you are listening to music with screen off, otherwise it doesnt effect the batterylife. But yesterday I listened quite alot to music with this kernel and the batteryuse was fine:)
[Galaxy S I9000 Android Development] mialwe:
0.7.7 -> OP

It's ok for me (Slim-ICS or Elite) but for more information you would have to read the last pages or ROM threads I assume.

0.7.7 is in the first post as is the changelog and some screenshots of the reworked MidnightControl app. All features I need are now implemented (thanks to ezekeel (dev) and derTeufel1980 [devil kernel] again for giving me helpful hints via pm while porting touchwake) so the next versions will be about fine tuning and bugfixing if needed.
[Galaxy S I9000 Android Development] lmulli:
Back to 0.7.4 for me. The new version appears to make my phone freeze in that nothing opens on it. I can scroll around the screens and apps folder but if I select something it highlights and stays highlighted and nothing else happens.
[Galaxy S I9000 Android Development] GreenSGS:
Sir, I think app is better than CWM switches, many times we need to change things quickly for example governor for a game play etc and next thing, list of kernel options may get bigger. Maintenance of app easier than CWM, an app can be patched easily if needed.

And those bootloops reports, makes me avoid CWM as much as possible.

Please keep midnight kernel control app, it already looks very clean.
[Galaxy S I9000 Android Development] Rootax:
I like the apps because there is one global gamma level slider. It doesn't exist on CM9 settings and it is annoying...
[Galaxy S I9000 Android Development] TheeWolf:
Couldn't agree more...

+1
[Galaxy S I9000 Android Development] pu3cyg:
C# is a .net language, but there is Mono which is .net framework running in linux..
[Galaxy S I9000 Android Development] Kocai:
Well I don't know about bootloops but you're right, the midnight control app already looks very clean and it's easier to change the governor. Some games feel like lagging using conservative.

IMO it is too much trouble to boot into recovery just to change the governor.

Please keep the midnight control app.
[Galaxy S I9000 Android Development] salzheld:
I am using Midnight Kernel for 2 month now.

It is a good decision to further reduce the number of options. And since I switched to Cyanogenmod too, a single cm9 version makes sense because development will be easier.

Just one option inside Midnight app seems ridiculous. Why nit drop the app in favour of a 1*1 widget?

Gesendet von meinem GT-I9000
[Galaxy S I9000 Android Development] mialwe:
Ah, yes, totally forgot about Mono - I remember purging it directly after a new Ubuntu install :)

- It already behaves like a widget im my test version - imagine the app icon, you tap it -> nightmode, you tap it again -> default mode. No UI.

- Reducing MNICS to a CM9-only version is what I'm thinking about,too - on the other hand is building MNICS for at last LR patched ROMs a matter of 20 sec. config adjustment and 1 minute of rebuilding. Reducing to CM9-only would give the option to reduce the app menus to only the settings *not* already provided by CM9 (e.g. - colors, - gamma, - governor, - maxfreq, not sure about IO scheduler).

=> after reading the reactions I'm currently thinking of combining the two ideas:

- options in CWM

- MidnightControl app (overrides CWM options if installed)

- MidnightControl separate package to install

=> users not needing the app can use CWM to configure and then just use the phone, everybody else can continue using MidnightControl. If I don't find the time to do this I'll upload the next version with enabled fast_charge + MidnightControl as known before, not sure now.

I'd personally prefer the reduced-as-much-as-possible version (aka CWM options) but I understand everybody saying that MidnightControl is a useful tool, too.
[Galaxy S I9000 Android Development] saszseb:
@mialwe,

I've just tested your "Odin/Heimdall" kernel to get recovery back.

Yesterday i tested Semaphore kernel on Elite ROM. Pls. read my report (post 3975.)!

Some minutes ago I tested the both (Semaphore and yours) on CM9. No success.

My question is as on Semaphore thread:

What do you think CM7 initial kernel knows that Semaphore and yours doesn't?

My test is only info for you.
[Galaxy S I9000 Android Development] yaatzek:
That is why I really like your kernel, because it's slim.

Could you please look at devil kernel about battery, it really makes difference there, especially in sleep. For example on midnight my battery drops by night 6,7 percent (wifi on, 2g), on devil there is 1,2 percent. I am not saying to copy his work, but to only look and maybe do it your way.
[Galaxy S I9000 Android Development] mikiept:
Well, DerTeufel1980 implemented a new type of idle (devil idle). It changes the bus frequency to 100MHz and drops the int voltages 50mv when the screen is off ;)
[Galaxy S I9000 Android Development] 2k4ever:
like i said earlier, i hope you keep up compiling a non-cwm large ram version, especially if you can do it with so little effort

if you reduce the features of the app / cwm to just the ones missing in CM9, that would be OK at least for me

in general, i get you point of reducing the settings to cwm as i don't change the settings as well and because i want to keep the number of background apps and services as low as possible

on the other hand, i would have to run the BLN app instead of your app, so there is no real gain at least for me and I'd prefer to keep midnightcontrol
[Galaxy S I9000 Android Development] mialwe:
Yes, I read your post yesterday and I think you have written the one most important question: Why do Gingerbread (tested Midnight-Gingerbread succesfully, too) kernels solve that bootloop issue.

The new initramfs of Semaphore/MNICS seem to prevent new bootloops but they do not cure previously existing loops every time (there were reports of solved bootloops but unsuccessful attempts, too).

We have to find out either what causes the bootloops or what does solve them \w Gingerbread kernels.

Well, I experienced 1-2% only on a few occasions (2 or 3 times) \w Gingerbread, I'm quite used to loose 5-7%/night. To have a direct comparison we have to know if you di change anything else after Devil->MNICS or vice versa (maxfreq, minfreq, undervolting, apps, sync behaviour, CPU governor, init.d scripts, modem, ROM,...). If it's a 100% identical system with just kernels changed and other users confirm a general 1-2% usage/night with Devil I'd assume it's Devil-idle, too (just a first guess).

EDIT: Maybe it's something else, don't know if those changes will make such a difference for the few wake-up occasions at night.

As I have one rule for myself which is not to copy other i9000 kerneldevs "special" work for the same device I most probably will not implement Devil-idle.

Maybe it's hard to understand but I think if every kerneldev copies the "special" work (that's not general improvements or features used by all/almost all kernels across several devices or ports of other devices/kerneldevs ideas to i9000, it's more like Stratosk's autobrightness driver, derTeufel1980s' Devil-idle, MNICS SmoothConservative to name a few) there would be no reason for different kernels, all of them would be using more or less the same improvements/features/enhancements.

For me this is a question of respect and kernel variability (is this the right word?).

@all: Don't think about CM9-only/no-app/more-CWM-options any longer, next MNICS will come with MidnightControl as before. If one does not want to use MidnightControl it can be removed and except nightmode every option can be set via init.d script => better and cleaner way as re-implementing a lot of CWM switches like in Midnight-Gingerbread.

MNICS will come for at least LR and CM9, not sure about stock-RAM version. Is there any ICS ROM with stock RAM config out there?
[Galaxy S I9000 Android Development] fishears:
Thank you for bringing fast charge back. Could you try to convince Stratosk too? ;)
[Galaxy S I9000 Android Development] extralife:
Nice :D like & need your app.

... using tapatalk
[Galaxy S I9000 Android Development] DerTeufel1980:
You always ca feel free to take this, or other things. No one can always invent everything by himself and from scratch.

For example, we all took your Vibrator intensity ;)

Gesendet von meinem GT-I9000 mit Tapatalk 2