yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] hippo_potamus:
Hi.

Yes, cleaning clearing cache/dalvik-cache is standard for me and it'd done.

Just installed 0.6.7. Will monitor for next 24 hours, thanks a lot.
[Galaxy S I9000 Android Development] djdeeles:
Usb tether not working for long time can u look at this
[Galaxy S I9000 Android Development] mialwe:
Ok!? Nobody reported this, last info on usb tethering was when changing source base to stock + update2 some weeks ago - users reported it's working.

- Can anybody confirm this (I'm not using usb tethering myself)?

- If yes, do you know since which Midnight version tethering stopped working?

Edit: Writing this with quickly enabled tethering and at least MobileAccesspoint seems to work here...but I don't see any new connection /w Linux/network-manager if Tethering is toggled on...hmm.
[Galaxy S I9000 Android Development] samyong76:
if i want to switch to this kernel from Galaxian with SuperSonic RO , what do i have to do? the last time i did it, i lost my root. ):
[Galaxy S I9000 Android Development] djdeeles:
Wifi tether ok but usb not connecting
[Galaxy S I9000 Android Development] mancukya:
usb tethering work fine for me.

i9000 orange ch whit rom revolution v2.
[Galaxy S I9000 Android Development] mialwe:
Good, glad to hear this.

Just compared 0.6.7 souces to original Samsung sources (without update2 changes for /drivers/usb/gadget which were known to cause tethering issues) - absolutely no difference.

@samyong76: Just try to root via Midnight->CWM->advanced kernel options again.
[Galaxy S I9000 Android Development] rom08:
Can you inclued in a future version the stock music player playing at 400 mhz instead of 800 like in semaphore , talon,. It seems since jvq or jvr music player is at 800 mhz . It could really be a battery saver. I copy you the post from talon thread where there is the link for the mod so can look at it.
[Galaxy S I9000 Android Development] nikec:
Wifi working with 0.6.7. and JVS. However I had some random connection drops and reconnections...
[Galaxy S I9000 Android Development] -freedroid-:
...so this means Wifi is not properly working on JVS?
[Galaxy S I9000 Android Development] stratosk:
This is JVS issue. It is not related to kernel.

You may use static IP as a workaround

@mialwe

Check the #define ULP_FREQ line for stock music player at 400Mhz in

arch/arm/mach-s5pv210/include/mach/cpu-freq-v210.h
[Galaxy S I9000 Android Development] mialwe:
Thanks stratosk,

its already

#define ULP_FREQ	(400 * 1000)

since I reworked the OC/max. frequency handling a few versions ago :)
[Galaxy S I9000 Android Development] stratosk:
I'm sorry my friend. I spoke too early. :)
[Galaxy S I9000 Android Development] rom08:
Me too sorry
[Galaxy S I9000 Android Development] djdeeles:
By the way i found my usb tether problem. Changed usb port solve problem :( its working now.
[Galaxy S I9000 Android Development] samyong76:
hey mialwe, awesome kernel! (; made the successful move from galaxian to this kernel on lukiqq's supersonic.

one thing though, after I toggle init.d support in CWM, there isn't any init.d folder present in /system/etc. do I have to create the folder myself?
[Galaxy S I9000 Android Development] mialwe:
Yes, if your ROM does not create init.d you would have to do this manually. Toggeling init.d support via Midnight CWM currently just en/disables the execution of scripts located in /system/etc/init.d - if any.
[Galaxy S I9000 Android Development] simone201:
Hi mialwe!!

Just here to say, keep up the good work! I see that u've done a great work on CWM Recovery, i only hope u will switch to CWM 3.0 (i have compiled my own also for my Talon SH Kernel) that is far better than 2.5 (at least for me)...

I will reply to ur pm later...thx for the infos!
[Galaxy S I9000 Android Development] djdeeles:
I think moving 2.5 to 3 useless. If you plan to move newer version why 3 not 4 ? :D
[Galaxy S I9000 Android Development] simone201:
Because CWM 4 seems have probs with GS1....

CWM 3 is quite similar to 4, only a few things different, like key mapping, but nothing very useful
[Galaxy S I9000 Android Development] mialwe:
Thanks simone201, maybe I'll think about switching CWM when Midnight is ready to be called "kind-of-stable" if this is possible - right now I'm bugfixing, experimenting, adding user requests and things I personally like to see in the kernel and extending CWM2.5 which is fun, too and testing some ideas in non-published builds. But Midnight needs some more time & work to be a "1.0" version...

@all: Is there any information/documentation on the SGS beeing unstable with more than 5 CPU frequencies? I read about this here @XDA (that's the reason Midnight uses 5 frequencies/4 steps now) but would like to test an idea combining 6 or 7 steps (1.3Ghz) and a more optimized conservative governor...
[Galaxy S I9000 Android Development] rabievdm:
Rom suggestions?

I know this is a little OT, but can anyone make any suggestions on a good custom ROM or ROM's? It looks like the my fav has closed it's doors on the Galaxy 1.

Perka has posted his last post and since then the kitchen has closed.

I'm not too much into themes and all, just a nice clean rom with most of the Samsung apps thats relatively fast but not so much that I have to charge the phone every half a day :)

Any thoughts?

R
[Galaxy S I9000 Android Development] betoNL:
I dont think the UOT kitchen ( http://uot.dakra.lt/kitchen/) is closed...

It gets full sometimes, then you have to try later....
[Galaxy S I9000 Android Development] rabievdm:
Thanks for that, but no, I'm not talking about the Ultimate Online Theme kitchen, I am refering to the old Doc's ROM or lately just the 'Rom Kitchen'

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

They seem to now focus more on the SGSII and the SGS area seems to have been taken offline, so I was wondering what roms some of the guys on this forum where running.
[Galaxy S I9000 Android Development] malcho:
Check this post.

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

Hybrid 2.0 lite on semaphore 1.7.0
[Galaxy S I9000 Android Development] mialwe:
Try a stock odexed ROM, remove all bloatware and system apps you don't use or need, add a hosts file and theme-files from XDA as needed - I'm doing this with JVQ and it runs great, no issues, fast and with themed notification bar.

(/OFFTOPIC)

Testing 0.7.1 with 1.3Ghz and 8 frequencies/7 steps again - seems to be stable... anything else you would like to see in 7.x.x?
[Galaxy S I9000 Android Development] mdv53:
Suggestion: When you use your headphone, and someone call you. That the sound/ringtone i can hear in the headphone and not anymore in the speaker(where normaly sounds the ringtone. Do you think that it's possible to make that?
[Galaxy S I9000 Android Development] jontoo:
+1 for that suggestion ;)
[Galaxy S I9000 Android Development] fylim:
switching from H to E with screen off?

Improve Bluetooth A2DP sound quality ?

Call recording on Gb?

Bluetooth PAN?

Pushing my luck hehe
[Galaxy S I9000 Android Development] djdeeles:
1440mhz or 1500mhz option :)

Make higher clocks posible.
[Galaxy S I9000 Android Development] mialwe:
Hehehe, maybe I should no have asked this question :)

Seriously, what I was talking about was little (needed/unneeded) improvements in kernel or CWM, something like "update superuser/su" as I was asked via PM (yes I will), make ROOTing give some feedback if it was succesfull or not in CWM, something like that... since I do not have enough spare time (remember "Midnight" => mostly working on it at night due to job and family) I don't think I'd be able to work on the ideas you mentioned, sorry.

- phone call sound/headphone: sounds interesting, maybe in later releases if possible.

- higher frequencies: thought about that for some days now but I think I'll stop at 1.3Ghz - that's more than enough for average daily use which was the basic optimizing idea for Midnight.

Some ideas from my personal Midnight idea/todo list:

- for next Midnight version:

-- CWM: more undervolting presets (as 1.3Ghz added now)

-- CWM: governor threshold option (done)

-- slightly tuned conservative governor (thresholds + code changes, done)

-- updated su/superuser

- for later Midnight versions

-- experiment with brightness steps/framebuffer/mdnie driver (maybe I should ask Lukiqq - who did a great job with colors/brightness levels in Galaxian - about that but first I'd like to try myself)

-- lower touchkey brightness (if possible)

-- CWM: some more ideas about initial ROM setup

-- CWM: make touchkey timeout configurable

-- app containing all CWM options + frequency usage stats (maybe)

-- TUN, netfilter as optional module (maybe)
[Galaxy S I9000 Android Development] rom08:
I like the idea of an app to too toogle all cwm options ! But I don't know what to think of having 7 different frequencies instead of 5 . It seems that the main point to stay with 4 steps is linked to dvfs values . For exemple if music player is said to work at l2 step it meens that it is 400 mhz with stock values but with 6 steps it means it will run at 1000 mhz. My point is that it will need to tweak each dvfs value and it seems that is really a lot of work to find all of them . Maybe I'm wrong but you can discuss the point with luqqick and exists , I believe they are the ones who find this first.

Also I like your ideas but I would like you to keep the kernel simple. Having too many option can be disturbing . Look at semaphore thread ,there is countless post saying tethering doesn't work even if it explain in the first post on how to enable it ! Just my opinion .
[Galaxy S I9000 Android Development] mialwe:
Hrmpf, almost forgot those &%§$" DVFS locks... thanks for reminding me mate.

I did some searching for the DVFS locks the last few days, what I found until now is this:

# dvfs functions:
./arch/arm/mach-s5pv210/cpu-freq.c:394:void s5pv210_lock_dvfs_high_level(uint nToken, uint perf_level)
./arch/arm/mach-s5pv210/cpu-freq.c:428:void s5pv210_unlock_dvfs_high_level(unsigned int nToken)

Switch:
.config/defconfig: CONFIG_DVFS_LIMIT=y

# how locking (basically) works:
./arch/arm/mach-s5pv210/cpu-freq.c:508:	if (g_dvfs_high_lock_token) {
./arch/arm/mach-s5pv210/cpu-freq.c:509:	if (index > g_dvfs_high_lock_limit)
./arch/arm/mach-s5pv210/cpu-freq.c:510:	index = g_dvfs_high_lock_limit;

# found dvfs locks:
./arch/arm/mach-s5pv210/aries-rfkill.c:282:	s5pv210_lock_dvfs_high_level(DVFS_LOCK_TOKEN_9, L3);
./arch/arm/mach-s5pv210/aries-rfkill.c:286:	s5pv210_lock_dvfs_high_level(DVFS_LOCK_TOKEN_9, L2);
./drivers/media/video/samsung/mfc50/mfc.c:88:	s5pv210_lock_dvfs_high_level(DVFS_LOCK_TOKEN_1, L2);
./drivers/usb/gadget/s3c_udc_otg.c:441: s5pv210_lock_dvfs_high_level(DVFS_LOCK_TOKEN_8, L3); //200Mhz lock
./kernel/power/main.c:300:	s5pv210_lock_dvfs_high_level(DVFS_LOCK_TOKEN_6, dlevel);

Other locks:
./kernel/power/earlysuspend.c:131:	cpufreq_driver_target(policy, ULP_FREQ, DISABLE_FURTHER_CPUFREQ); (the only lock found with cpufreq_driver_target)

Maybe you are right If you point me to the experienced kernel devs here, I think I know what I'll do the next nights...
[Galaxy S I9000 Android Development] mdv53:
Your ideas are great, look Forward for your next release.
[Galaxy S I9000 Android Development] mialwe:
Yes, me too. I'm a bit unsure about the DVFS locks, searched the whole kernel source tree for hours last night, but I was not able to find more lines looking like a dvfs lock (in case any dev reads this searched for "[^a-zA-Z0-9_]L<1-5>[^a-zA-Z0-9_], variations with frequencies and the lock/cpufreq_target functions - thousands of lines but I only found the locks I already posted).

Maybe I have to revert my changes and go back to the 4step/5freqencies version with configurable 1Ghz or 1.2Ghz or 1.3Ghz - but I would like to keep the 7-frequencies version as I like the nice up/downscaling with the slightly tweaked conservative governor a lot - and it seems to work without issues here...
[Galaxy S I9000 Android Development] rom08:
If you have no issues post it as a test version in order to have more feedbacks
[Galaxy S I9000 Android Development] mialwe:
Yes I'll do this. Only things left to do:

- test new su/superuser version install (edit: done 30/09)

- add 3-4 new undervolting presets/test them (edit: done 30/09)

- implement reset of old-version undervolting settings to keep users from getting reboots due to old uv values not working for new high frequencies

My kids just came back home so I have to do those later today/tonight...
[Galaxy S I9000 Android Development] mialwe:
0.7.1 / 2011-09-30

PLEASE ADJUST UV VALUES FOR NEW FREQUENCY STEPS

- switched to 7 freq/5 step version (100/200/400/800/1000/1200/1300Mhz)

- slightly optimized conservative governor

-- up_threshold 60, down_threshold 45, code uses freq. lookup table

- CWM: Added "Unroot" option to cleanup menu

- CWM: load TUN module

- updated su/superuser to 3.0-efgh

Link: TAR 0.7.1

Next few days: only bugfixing as needed, need a break...
[Galaxy S I9000 Android Development] krosscheck:
Do it!!!

New version is top. It will be even better :-)
[Galaxy S I9000 Android Development] pacc:
I'll be testing this one, looks quite promising.
[Galaxy S I9000 Android Development] djdeeles:
Nice features but I think this version a bit slower than before in real fire & quadrant. I get older version @ 1200 higher then 1300 now
[Galaxy S I9000 Android Development] pacc:
Failed 1st flash in Odin, 2nd flash was ok.

Performance seems strangely slow (ex. 1100 in Quadrant) when clocked at 1300Mhz (conservative).

When I change to ondemand, it becomes very unstable.

So probably something needs fixing.
[Galaxy S I9000 Android Development] mialwe:
- did you RESET you undervolting settings (if any)?

- not every SGS is stable @1.3Ghz

- quadrant IS slow with conservative
[Galaxy S I9000 Android Development] simone201:
Well, the 3rd is not fully true....

With my latest Talon SH, @1.2Ghz with Voodoo Lagfix and Conservative i gain about 2800pts...

With InteractiveX (the best for smoothness and battery) i reach over 3200pts
[Galaxy S I9000 Android Development] mialwe:
Ok, conservative is slow with *Midnight* :-)

Ondemand gives better Quadrant scores.

Speed depends on a lot of different factors and Midnight was never optimized for Max speed but for average daily use.

Havent run a single benchmark since I own the sgs ...
[Galaxy S I9000 Android Development] simone201:
hahahaha i didn't say mine is better, nono......:D

i only said that with my kernel, and stock conservative governor, quadrant runs fine.....

Anyway, i think u'd better try to implement InteractiveX as default governor, and tweak it a bit....trust me, is the best ever seen...;)
[Galaxy S I9000 Android Development] pacc:
-Flashed stock JVS (odin repartition, etc...)

-Failed 1st flashing attempt and 2nd was fine.

-Didn't touch UV or OC

-For me 1.3Ghz is slightly unstable.
[Galaxy S I9000 Android Development] djdeeles:
Slow with ondemand 1.3 ghz :(
[Galaxy S I9000 Android Development] mialwe:
Hello, can you give some more information on "slow"? Slow @benchmark(s), slow homescreen sliding,...?

@all: When you have issues please provide the logfile /data/user.log, helped me already a lot finding issues (which mostly weren't kernel related) with previous versions of Midnight.

You can put it in a PM or here in this thread (CODE tags are a good way to not make the posts explode). Thanks. I'll try to figure out your issues/kernel bugs etc...

Via 3 forums there are the following issues reported:

- unstable 1.3Ghz for some user (thats ok, some may need lower/higher undervolting settings)

- less performance (dont know if only governor related), was not able to reproduce this, too.

Kind-of-solved:

- "cannot write config file" error in CWM (one user)

-- worked ok after fresh rom install, before CWM was able to write configfiles only after using conversion via CF-Root based kernel.

- root upgrade did not update "su" (one user)

-- there were multiple instances of su installed

So the main issue seems to be the performance drop. Any information on Mhz/governor/thresholds you used when you noticed the dropped performance?
[Galaxy S I9000 Android Development] mialwe:
Ok, maybe undervolting would be a solution? Midnight uses 1350mV @ 1.3Ghz, maybe that's too much for your device? I'm running 1.3Ghz@-20mV, no instabilities for days now.

Stratosk today wrote in the Semaphore thread why he probably won't implement 1.3Ghz into Semaphore - because of the instability issues introduced with this, seems he's right with this :), maybe I should go back to the 0.6.7 uv/oc setup.

Doing some benchmarks here right now (first time for me :) ), posting them when finshed for comparison...
[Galaxy S I9000 Android Development] stratosk:
Hi Mialwe,

I have never had personal experience, but reading reports from other kernel threads I think it's difficult to have stability for all devices in these frequencies. If I remember correctly Galaxian used in the past 1.4Ghz (and I think 1.6?). Talon also stopped 1.4Ghz.

In the latest Semaphore release I increased slightly voltage of 1.2Ghz to 1325mV because of a couple reports for stability even at 1.2Ghz.

So, I think it's difficult to stabilize this frequency. But again this is my personal feeling and maybe I'm wrong.

Anyway well done for trying this. I hope you will find a solution on this. :)
[Galaxy S I9000 Android Development] mialwe:
EXT4 with journaling,relatime,commit=20,barrier=1,nodelalloc,data=writeback

Stock JVQ, backgrounded apps gMail, gReaderPro, 3GWatchdog, freshly booted up

Quadrant Standard

1300Mhz, noop, ondemand: 2654 (3rd run)

1300Mhz, vr, ondemand: 2652(3nd run)

1300Mhz, noop, conservative: 1334 (3rd run)

1300Mhz, vr, conservative: 1329 (3rd run)

1200Mhz, vr, ondemand: 2452 (2nd run)

1200Mhz, noop, ondemand: 2182 (2nd run)

1200Mhz, noop, conservative: 1416 (2nd run)

1200Mhz, vr, conservative: 1420 (2nd run and 3rd run)

AnTuTU

1300Mhz, noop, ondemand: 3359

1300Mhz, noop, conservative: 2968

1200Mhz, noop, ondemand: 3184

1200Mhz, noop, conservative: 3222

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

@all: can anyone comment on this as I don't have any experience with the scores...

@stratosk: Thanks, read your post about why you won't implement >1.2Ghz today - seems you are 100% right about this :) Looking at my benchmarks above I don't think 1.3Ghz make a big difference to 1.2Ghz, maybe I'll drop it for the next version. What a waste of hours...

@simone201: Do you have some AnTuTu results for conservative @ 1.2/1.3Ghz? Maybe there's an issue with my conservative governor, I'll do some tests tonight. Which mount options does your kernel use (if EXT4 - barriers?, commit?,..)
[Galaxy S I9000 Android Development] krosscheck:
Antutu 3424, conservative, vr, ext4 @1300
[Galaxy S I9000 Android Development] mialwe:
-- wrong post --

Edit: Testing max 1200Mhz version now...
[Galaxy S I9000 Android Development] mialwe:
- Back to 1.2Ghz max frequency again, 1.3Ghz yesterday became unstable for me running AnTuTu@ondemand... 1Ghz step remains for now, if this doesn't work good I'll go back to the "switchable" max frequency 1Ghz/1.2Ghz like in 0.6.7.

- note: please remember "conservative" is the default cpu governor, for higher benchmark values switch to ondemand

- note: if you have issues I'd like to work on them, if possible upload/mail/pm /data/user.log logfile

- added FAQ section @ second post (see signature)

- Please remember to adjust your undervolting/overclocking settings (again).

[Download TAR 0.7.2]
[Galaxy S I9000 Android Development] djdeeles:
Why removed 1.3 its stable for me. for who not stable dont use it. :(
[Galaxy S I9000 Android Development] mialwe:
Your report + various others about not reaching the expected benchmark scores + instability issues for some users (was stable for me, too until used AnTuTu):

Those reports won't stop as long as I have 1.3Ghz enabled. As 1.3Ghz made no big difference in benchmarks I don't think it's neccessary to use it + I'd have to raise voltage/internal voltage to get it stable for more users (if I remember right Glitch uses higher arm.volt + raised internal voltage for high leakage versions).

Midnight aims for stability @ average, daily use and was never optimized for speed, so this is the time to consequently revert the last changes. There were not much reports about 1.3Ghz running fine and after 2 Months of hard work and not very much sleep I try to make Midnight somewhat more stable to get a little break...
[Galaxy S I9000 Android Development] hippo_potamus:
1.3Ghz is bad for me too. 1.2Ghz works okay so far.
[Galaxy S I9000 Android Development] Pfiffle:
Me too!!!

Sent from my GT-I9000
[Galaxy S I9000 Android Development] fylim:
1.3 is stable for me mostly except when playing video using moboplayer.
[Galaxy S I9000 Android Development] mialwe:
Thank you all for feedback and thank you for 2 donations since yesterday, I really appreciate it.

For the next version I implemented a kind of new "hybrid" overclocking variant, experimantal:

- Voltage 1.3Ghz = 1375mV, 1.2Ghz = 1300mv (unchanged), all other stock mV

- Default setting is 100-200-400-800-1000Mhz with max. freq. 1200Mhz deactivated.

- CWM: Enable 1200Mhz OR 1300Mhz

- CWM: manual uv settings for ALL frequencies independently from selected max. freq.

This way we can keep the aditional 1000Mhz step when overclocking, keep the optional 1.3Ghz feature, keep optional 1.2Ghz and set 1000Mhz as default.

Hope this will work for most users.

Download Tar 0.7.3

Edit: First & second post updated, sources updated.
[Galaxy S I9000 Android Development] djdeeles:
Wow thanx :) thats it :)
[Galaxy S I9000 Android Development] mialwe:
Small update on what I'm doing with Midnight...

As 1.3Ghz weren't stable for my SGS I tried different voltage settings - seems that it runs stable now at 1.3Ghz @ 1400mV arm.volt (that's the voltage you can undervolt, too) and slightly raised 1125mV internal volt (default: 1100mV), settings like the ones in Glitch and Fugumod Githubs.

Using default voltages = not stable (reboots e.g. with antutu full benchmark),

using other voltage combinations = not bootable (reboots at SGS logo).

I'll try to implement 1.3Ghz @ 1400mV arm.volt and 1125mV int.volt as an option in CWM in case anyone needs more stability with 1.3Ghz.

@all/devs: Anyone knows why compiling with Linaro toolchain/Ubuntu causes reboots at SGS logo?
[Galaxy S I9000 Android Development] brk:
Hi, I've got a problem. Even if I load TUN module I cannot connect to VPN. With Semaphore kernel, I load TUN module and VPN works fine.

Is there a problem loading VPN module? Thanks.
[Galaxy S I9000 Android Development] mialwe:
Could you PM me the logfile /data/user.log (or the output of "adb shell lsmod" if you happen to have ADB installed on your PC)? I don't use TUN/VPN, just compiled TUN as a module instead of keeping it in the kernel...
[Galaxy S I9000 Android Development] fylim:
Great, bit stable at 1.3 ghz now with no UV. Crashes when playing games. Hopefully the higher volt will help.
[Galaxy S I9000 Android Development] brk:
Sent you a PM. Thanks.
[Galaxy S I9000 Android Development] mialwe:
Thank you, found the bug after looking at the log - I forgot to rebuild tun.ko for last kernel version so the modul version is older and therefore will not be loaded. This will be fixed in the next Midnight version, thanks again.
[Galaxy S I9000 Android Development] Plunky Duck:
@ mialwe :

Best kernel on gingerbread !

You know what , when I saw the Midnight 0.1 , I said : I think it will be the best kernel ! :D

I'm using more the music player than video player and it give me the best sound !

Congratulation !!! :)

(Oh , I forgot : my ROM is coming soon ; can I use your kernel ?)
[Galaxy S I9000 Android Development] mialwe:
Sure you can use Midnight - but for the sound say thanks to supercurio, he's the dev of VoodooSound and did all the amazing work for us :)
[Galaxy S I9000 Android Development] hippo_potamus:
EXT4 x RFS

Hi,

If anyone using XXJVR in this forum could help to verify this ...

RFS convert to EXT4, then back to RFS, after that Haptic Feedback stops working.

If I use nandroid to restore, it's back to normal so I'm sure it's software related. The options for Haptic Feedback is enabled and settings to max.

Thanks