yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] rom08:
Hello mialwe just to know if it is normal behavior because in freauencie voltage table in the line for1.2 ghz I see this

1200 mhz the to numbers 1300 and 1325.

Don't know what it is as I don't use any overvolting feature. I thought that default voltage was 1300. But in setcpu the voltage is really 1300 . I come from semaphore wich have 1325 as default for 1.2 ghz maybe it is related . I also try to delete the file and reboot but the file regenerates itself with the sames number ! So what do you think is my cpu at 1300 or 1325 mv ? I believe it is at 1300 because setcpu say so , am I right ?
[Galaxy S I9000 Android Development] mialwe:
- haptic feedback: I converted filesystems multiple times while working on Midnight - just tested - haptic feedback works for me (but still on JVQ) , anyone else with this issue?

- voltage@1200Mhz: 1300mV should be correct, I'll look into the source as soon as possible.

- One user reported CWM settings not beeing saved with JVT, can anyone confirm/test this (dont use JVT yet)? Thanks.
[Galaxy S I9000 Android Development] jimbo77:
I can deny this... I'm using Midnight 7.3 since yesterday over Ramad's JVT Deodexed and it's working really good. I'd step away from your Kernel on JVS becuase my phone was laggy and had memory leaks but after Flashing JVT and 7.3 i can tell you that my phone is flying and YES settings do get saved from CMW...

J!M
[Galaxy S I9000 Android Development] malcho:
Flashed this kernel and play with it few hours.

Man you done outstanding job!

Clockwork options on this kernel is great.Everything works.

I'm gonna watch this thread and i will include review on my thread.

Many regards
[Galaxy S I9000 Android Development] mialwe:
0.7.5 / 2011-10-07

- raised 1.2Ghz voltage from 1300mV to 1310mV (stability)

- removed 1.3Ghz

- updated su/superuser to 3.0.2-efgh

- updated to proprietary JVT modules

[Download TAR 0.7.5], Sources updated.
[Galaxy S I9000 Android Development] nmcc89:
@mialwe I've tried to install root on stock JVT using your latest kernel (0.7.5) and unfortunately root isn't being installed. I downloaded this root checker app from here and these are the detailed outputs (I'd imagine there's a better/more informative way of doing this via terminal?):

Root Checker Advanced Root Access Results

Root Access is not properly configured or was not granted.

Superuser.apk - com.noshufou.android.su - version 3.0.2 is installed!

System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

The adb binary is set to default shell user access as a standard non-root user

Standard su binary location: ls -l /system/bin/su:

/system/bin/su: No such file or directory

Standard su binary location: ls -l /system/xbin/su:
-rwsr-xr-x root root 22140 2011-10-07 17:57 su

Alternate su binary location:
/sbin/su: No such file or directory

Alternate su type binary location:
/system/xbin/sudo: No such file or directory

SU binary not found or not operating properly

Results provided on your GT-I9000 device by Root Checker version 3.7 from joeykrim in the Android Market - [url]http://goo.gl/GgWae[/url]

Root Checker Advanced BusyBox Results

System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

BusyBox binary location: /system/xbin/busybox

Installed BusyBox Version:
BusyBox is not sharing its version information

BusyBox supports the following applets:
BusyBox is not sharing its supported applets

Results provided on your GT-I9000 device by Root Checker version 3.7 from joeykrim in the Android Market - http://goo.gl/GgWae

I flashed semaphore just before this, so to rule that out being a problem I reflashed stock JVT with repartiton and have wiped the internal sd/cache/davlik, but still can't root with 0.7.5.

0.7.3 roots fine so I just rooted with that and just flashed 0.7.5 over as a fix.

Kernel's looking great though :), I finally made a move from speedmod with the SGS development drying up, but I'm glad I stumbled upon this thread. I like the similar approach you have here aiming for stability for the average user, but also how you can switch most of the parameters being in cwm too
[Galaxy S I9000 Android Development] andip71:
Can confirm...

Hi,

I can confirm the issue with not being able to root with 0.7.5.

Also I tried it many times today on a fresh stock JVT, but no success.

Currently running on Semaphore, which was rooting fine.

I even tried to flash Midnight again after Semaphore, but then root was gone again.

Hope for a fixed version soon...

Many thanks

Andi
[Galaxy S I9000 Android Development] nmcc89:
If you want to keep midnight try flashing 0.7.3, rooting in cwm, and then flash 0.7.5 as that worked well for me
[Galaxy S I9000 Android Development] adl:
Tried to flash it on Darky 10.2 but it gets stuck @ the "android" logo. I used the kernel cleaning script before flashing, so there should be no leftovers from any previous kernel (i had galaxian kernel before).

I also tried rebooting, but still stucked @ the android bootlogo.
[Galaxy S I9000 Android Development] pinpong:
You have disable Voodoo Lagfix?
[Galaxy S I9000 Android Development] mialwe:
@rawpunzel: To be sure I just tried -> modem JVQ -> modem JS5 -> modem JVQ using perkas' CWM3 zips. Worked fine.
[Galaxy S I9000 Android Development] mialwe:
@pinpong: No, not actively. I implemented only Voodoo Sound.

@adl09: DOes Darky use a custom bootamination? This may be the reason.
[Galaxy S I9000 Android Development] HM.Carbide:
It's mentioned often that the problem is the bootanimation of darky. Delete it, and it works.
[Galaxy S I9000 Android Development] HM.Carbide:
After one day everything is stable. Battery usage is good for ondemand. I also think that conservative will give better battery life.

Only thing i found is about voodoo. I don't know if it is your kernel, or voodoo problem.

Changing the analog gain in voodoo control app does nothing. It seems not to work.
[Galaxy S I9000 Android Development] adl:
No, should i have done that?

Ok, this might be the reason!

Ok, will give it another try with the upcoming version.

Thanx guys!
[Galaxy S I9000 Android Development] pikachu01:
new JVQ sources are out!
[Galaxy S I9000 Android Development] mialwe:
Are those "GalaxyS_OpenSource_GB_Update2.zip" ? There's no date on the download site... lets see... EDIT: thank you for info, download now at ~48%... :)

@galaxysandstillnofroyo I cant even see this option? Going to look if I have to update VoodooControl...

@all: Testing conservative governor with tweaked settings right now, seems to work for me but maybe some users will complain about slightly reduced smoothness. Maybe I'll set ondemand as default and everybody can switch to tweaked conservative using setCPU or similar apps...
[Galaxy S I9000 Android Development] pikachu01:
Yes, that's the one. GalaxyS_OpenSource_GB_Update2.zip
[Galaxy S I9000 Android Development] krarvind:
where is this file?
[Galaxy S I9000 Android Development] pikachu01:
Samsung opensource release center:

http://opensource.samsung.com/

It's only interesting if you are building kernels.
[Galaxy S I9000 Android Development] HM.Carbide:
Sorry, i was not clear. The option is called headphone amplifier. It controls the analog amplifier.

Had only installed speedmod on gingerbread until now. Under froyo it worked with all kernel supporting voodoo.

Installed your kernel again, installed voodoo app again, still same result.

if i choose the volume key hack, volume goes to max and can't be controlled anymore.

I'll tried this with the fm radio.

Can you reproduce this?

Rom is Stock bojv5 (provider version based on jvo), but i think as there is voodoo driver and voodoo sound involved, it has nothing to do with the rom.

Could it be, that there is some code from hardcores sound optimizations left and interacting with supercurios code?
[Galaxy S I9000 Android Development] mialwe:
Caution: Ext4 conversion via CWM (DATA) does not work, see 1st post for more information.
[Galaxy S I9000 Android Development] HM.Carbide:
My fault! I did convert to ext4 to test, if there is a significant speed difference. I is not.

But, i deleted the backup, as i thought i stored it already on my notebook, but its corrupted.

What am i missing on data, how to restore voodoo functionality?

The data image is the biggest, how come that everything works even 370mb are missing?

How can i restore only data? Will it work with a 14 days old backup?
[Galaxy S I9000 Android Development] mialwe:
More info:

After trying to convert to data/dbdata/cache to ext4 via CWM i ended up with this:

/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata ext4 rw,noatime,commit=20,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/stl11 /cache ext4 rw,noatime,commit=20,barrier=1,nodelalloc,data=writeback 0 0

cache and dbdata worked, data didn't and after booting I saw Touchwiz (use Go launcher) and all installed apps were signed as "on SD" but "not installed".

Reverted back to RFS via CWM and restored the backup made during ext4-conversion (did not use the rfs-conversion backup as /data already was empty at this time) -> everything ok again. No error messages during any conversion in CWM.

Right now I have no idea what the problem might be but I'll try to find a solution.
[Galaxy S I9000 Android Development] mialwe:
To be sure restore the data using the kernel you made it with.

About restoring the voodoo functionality - I'm not sure, I think I did not understand that question.
[Galaxy S I9000 Android Development] HM.Carbide:
Nothing really bad, i have a backup of my sms, kontakts are synchronized with outlook, backup of the Pokemon savepoint of my son :)

So I'll flash back the original kernel, and make the second factory reset since i have the phone. Should anyway make gingerbread faster :)
[Galaxy S I9000 Android Development] mialwe:
Update #1: CWM/ext4/rfs: Somehow unmounting /data and /cache partitions does not work, maybe thats the problem. kmsg and recovery.log don't give any information....:(

Update #2: Cannot find a solution for ext4-problem, I'm thinking of trying another initramfs to see where the problem is. PMed hardcore a few seconds ago, maybe he has an idea.

Latest sources: Compiles fine but refuses to boot past the sgs logo - maybe I need a new LOCALVERSION... not a good day today...hrmpf...

Update #3: Latest sources/seems to be a problem with RFS/SFR/Initramfs somehow... if anyone has a hint I'd be glad to hear about it...
[Galaxy S I9000 Android Development] mialwe:
Update: Midnight 0.2.3 uploaded, switched back to basic recovery3e for now, don't want you to end up with empty /data... was not able to resolve the umount issues with CWM2.5, looking for CWM3.x with RFS support or at least recovery3e now...

My personal workaround for now: If I have to use CWM backup or updating (zip) - don't need those features that often - I'll flash my safety-kernel (latest Speedmod), then switch back. Don't know if this would be an option for you...
[Galaxy S I9000 Android Development] mialwe:
Thanks for reporting this guys, I'll look into this. Only change about rooting was update of su and superuser so I don't understand how this can happen right now...

According to your log:

- superuser is installed ok, right version. Ok.

- busybox is installed but not giving information, thats ok as busybox is basically a symlinked reovery binary (method inherited from Speedmod). Ok.

- error reported about su nor working properly or not beeing installed BUT:

So it's there !?

[ Edit: Just one moment, think I got it... ]

Question: If you run superuser and check the installed su/superuser versions in options menu, what does it say?

Meanwhile going to look into the root install code...

Edit #2: Somehow su is broken, calling it diretly gives me this output:

reloc_library[1312]: 1315 cannot locate '_ZNK7android6Parcel15setDataPositionEj'...
CANNOT LINK EXECUTABLE

Downloaded directly from superuser website yesterday... edit #3_ maybe wrong base system version...
[Galaxy S I9000 Android Development] brk:
TUN module works fine in 0.7.5. Thanks.
[Galaxy S I9000 Android Development] nmcc89:
That's strange, although I'm sorry I can't help with code, I have no idea!

Currently root is working (from flashing 0.7.3, rooting and then flashing 0.7.5). Su did update once I rebooted the phone though. So if I go into superuser app and check the version I have Superuser v3.0.2 (37) and Su binary v3.0.

I'll now "root" using 0.7.5 and tell you what it says

Edit: the superuser app now reports Superuser v3.0.2 (37) and Su binary vnull after rooting with 0.7.5. I guess the su binary being installed by the kernel is broken?
[Galaxy S I9000 Android Development] mialwe:
Dont try, it won't work.

Accidently downloaded wrong zip archive (Donut). 0.7.6 is building right now...
[Galaxy S I9000 Android Development] nmcc89:
Good news!
[Galaxy S I9000 Android Development] mialwe:
0.7.6

Thank you very much, this is exactely what Midnight intends to be. And thanks for the bug report :)

0.7.6 /2011-10-07

- bugfix: su/superuser not working

- slightly lowered conservative thresholds to 55/up)/35(down)

- some text changes in CWM cleanup menu

[Download TAR 0.7.6]
[Galaxy S I9000 Android Development] nmcc89:
Flashed and rooted successfully. More like thank you, you're doing a great job, it's nice to see devs still on the SGS!
[Galaxy S I9000 Android Development] cha-ka-lak:
I think midnight is now the kernel to go for if using sgs.

Thanks for the nightly work.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] rom08:
+ 1 to this
[Galaxy S I9000 Android Development] antz_77:
+1. Best kernel for daily use
[Galaxy S I9000 Android Development] tma200:
I've been tweaking my SGS for a year now and this is by far the best kernel for playing around with. The only thing I can think to improve this for what I need is a bigmem version that sacrifices 720p recording for more free RAM. Then it would literally be the perfect kernel.
[Galaxy S I9000 Android Development] fylim:
Fully agree with you. Further extending my sgs life span.

Oh yes. Big mem please.
[Galaxy S I9000 Android Development] mucinch:
Could you explain how to set governor Min/Max thresholds and sampling rates? I tried to change them via SetCPU but they don't seem to change, is there a better method?
[Galaxy S I9000 Android Development] mialwe:
Thank you all ,glad you like Midnight :)

Thresholds: Never had any problems setting them with setCPU, I'll re-test this. In CWM->advanced options->CPU there are menus for setting the thresholds, too.

@all: I'm working on a CWM4 port for Midnight, sorry for les updates the last few days... and thanks to madrooster for some really useful tips on CWM > 2.5.
[Galaxy S I9000 Android Development] brk:
Nice, I was going to say that the only thing missing in this kernel is support for CWM3 scripts, but CWM4 is very good news. Thanks.
[Galaxy S I9000 Android Development] mucinch:
Thanks for the reply, I changed the thresholds through CWM and it worked fine. But I still cant change the sampling rate.
[Galaxy S I9000 Android Development] mialwe:
hehe, I know some people who say that Midnights' CWM options are too much - maybe I should include a sampling rate option :)

To be honest - I don't know if setCPU allows to change the sampling rate. The SYSFS interface for the governor tunables is untouched by Midnight.

Only exception: I do a lot of experiments with the conservative governor (I like it somehow :) ) - right now conservative governor does *not* use the "step" tunable (you can set it via e.g. setCPU but it won't be used) as Midight uses two lookup tables for up/downscaling the frequencies - one table for moderate CPU load (or the % you set via up_threshold), stepping up frequency per frequency and one table for CPU load > 70% stepping up faster.

This will be changed when I find the time to put conservative \w Midnight modifications into it's own module, leaving the original conservative governor untouched.
[Galaxy S I9000 Android Development] mucinch:
I like the present implementation of the Conservative governor better than the default one. The reason I want to change the sampling rate is to prevent lags while scrolling long lists. A sampling rate of 15000 produces no/negligible lag when scrolling and with sample rate polling taking minimal overhead, it gives me the best UX.

As for the numerous options in CWM, it is a better solution than installing dozens of apps to tweak each parameter. Of course if you can find the time a "Tweaks" app would be awesome.
[Galaxy S I9000 Android Development] hippo_potamus:
"numerous options in CWM", suggest to leave it. My opinion is that it's good to have it this way.
[Galaxy S I9000 Android Development] mialwe:
Yes, I'l l leave them as they are.

Made some progress with CWM4 last night (compiles and boots fine now), right now working at the post-init.sh which applies all those CWM Midnight settings - have an issue I don't find any information on:

- trying to set the uv values

- the settings get applied

- but in /data/user.log I can see this:

echo "$uv1200 $uv1000 $uv800 $uv400 $uv200 $uv100" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
sh: write error: Invalid argument

same if I use e.g. "echo "0 15 50 50 100 125" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table"

But the values are set correctly...!? If I try the same line in adb shell there's no error shown...

[Edit: Got it solved. Voltages have been set correctly every time but original UV error handling caused this issue. For devs: sscanf in "store_UV_mV_table" returns the number of successful conversions, should be enabled_frequencies count, not "1" to remove the error message. Just in case anyone actually sees the error message :)]
[Galaxy S I9000 Android Development] tirlibibi:
Thanks For this kernel, i tried almost all custom kernel, this one is the fastest for me !
[Galaxy S I9000 Android Development] andip71:
Just to let you know I am also back on your kernel now after 0.7.6 got out.

Coming from Semaphore (which is also a great kernel).

But now running on ext4 again, governor switched to ondemand and undervolted.

Works excellent !!!

Pls keep up the good work. What would be the advantages of CWM 4 by the way?

Thanks

Andi
[Galaxy S I9000 Android Development] saszseb:
I've had problem with Midnight.

I've flashed it over Semaphore_1.8.0. After reboot uninstalled superuser, then in CWM ran superuser.

After reboot in CWM I converted all partitions into EXT4. The second Quadrant score shows only 1200. It should be cca. 2800-3200.

What's the problem?

Thanks.
[Galaxy S I9000 Android Development] mialwe:
Did you change CPU governor and frequency to match Semaphores settings?
[Galaxy S I9000 Android Development] saszseb:
No, I didn't change CPU settings.

I'm on Hybrid ROM with stock Semaphore_1.8.0. All filesystems are RFS.

What steps to do?

- flash Midnight via SGS Kernel flasher?

- ??

Thanks.
[Galaxy S I9000 Android Development] mialwe:
?? I thought you you reported the Quadrant scores with EXT4?

- flash Midnight using the method you like most

- Re-ROOT if neccessary (only needed if problems with su/superuser)

- via CWM: change CPU frequency to the freq you used with Semaphore (if other than 1Ghz stock)

- via CWM: change CPU governor to the one you used with Semaphore (if other than conservative, also see post #2 "Low benchmark score" on this one)

Midnight was never optimized for speed, it's an slightly optimized "average-daily-use kernel" with some added features other users and myself were interested in and CPU governor conservative as default setting as stated @ first post. Best Quadrant I got on my SGS with Midnight was ~2600 with 1.2Ghz/ondemand/EXT4. Conservative score matches your value.

If you need hight Quadrant scores you should try much more optimized kernels like Talon (& TalonSH) or use more optimized EXT4.

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

@all

I'm working on a port of all the Midnight-CWM features to CWM4 (therefore not more updates these days, sorry), next public kernel version will be uploaded if

- CWM4 itself compiles and runs fine (done)

- Completely new built initramfs with CWM4 runs fine (done)

- all Midnight CWM options work (done, 1 bug [color mode WARM] fixed)

- conversion RFS/EXT4 works (currently trying to make Midnight compatible to Chainfires EXT4-Tool)

- booting with EXT4 fs works (done, untested)

I hope I will get this one ready within a few days...
[Galaxy S I9000 Android Development] saszseb:
Thanks. I managed to do it.
[Galaxy S I9000 Android Development] zenosteam:
I am testing this kernel it fast no lag and no rebbot after playing with ov
[Galaxy S I9000 Android Development] mialwe:
The gamma tables are hardcoded into the kernel sources (for now :) ) - so at the moment there's nothing you can do about it, sorry. But changing brightness levels is on my todo list for a long time now, I'm going to look at it as soon as the "base" version is running somehow fine.

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

@all again: new version not ready yet. I had some issues with my initramfs and CWM4 in combination with chainfires EXT4-app which I had to solve, ended up with rebuilding the complete initramfs *again* including all Midnight CWM options parsing... the initramfs is now a combination of JVT stock/Semaphore/CF-Root/Midnight initramfs and working.

The initramfs seems to work now, including the option to use Chainfires EXT4-tool for RFS/EXT4 conversion (big thanks to Chainfire for helpful PMing - you created great kernels/apps/methods - now I know why Midnight users were asking for CWM3+ and CF-tools compatibility...!!!).

TODO:

- test all CWM options (I think there are some "stock" CWM options which have to be adjusted for SGS)

- test all CWM Midnight options

- re-test CF-(EXT4-)tools functionality/compatibility after everything is done
[Galaxy S I9000 Android Development] Rootax:
Is it possible to put the max fps to 66 ? All seem smoother with that tweak.
[Galaxy S I9000 Android Development] 2k4ever:
That would be great, especially if the brightness settings would be adjustable in CWM
[Galaxy S I9000 Android Development] zenosteam:
keep the the good work
[Galaxy S I9000 Android Development] mialwe:
I'll try, thanks :)

For now I'm going to fight with CWM4 a few more days, have to test e.g. the nandroid backups (had some issues with mounting/RFS/EXT4 which seem to be solved now) and some other untested "stock" CWM features.

- FPS uncap: I tested this for a short time a few days ago, disabled it again as I don't know if there are any disadvantages, does anybody have some information on this?

- gamma tables/brightness - yes, I thought of something like that. But the gamma table work will be another "big one" like CWM4 now, haven't had the time to do experiments with gamma/brightness/colors until now (wanted to improve Midnight stability and implement CWM4 first) and there's not much documentation (found a good thread from supercurio but nothing more) about this. But I will try :)
[Galaxy S I9000 Android Development] fylim:
If you can pls kindly look into big mem reqeust. Tq. Very useful for the sgs.
[Galaxy S I9000 Android Development] scheichuwe:
Just reporting:

I did a nandroid backup (all) in recovery mode and tried to restore it (with "restore all" option).

But /system is not restoring, it is erasing completely :eek:

Maybe you can take a look at the restoring options?

As I don't have a Custom-ROM on my scdard (execpt CM7 which can't be installed because of getprop-errors) I have to wait until I get back home to get my SGS working again :D

Stock JVT with MIDNIGHT 0.7.6