yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] fcck:
Im wondering if "JVS_1.8.0beta1" is stil in a BETA stadium? As i run GingerReal 2 JVS and flashed the JVS_1.7.5 at first.

However now I flashed to JVS_1.8.0beta1 (which i had to download from www.semaphore.gr/downloads instead of in the attachments in the opening post??)to try it out, bet this cant really harm though? As you didnt put this JVS1.8 version available here on XDA?
[Galaxy S I9000 Android Development] stratosk:
The latest version is JVT_1.8.0. Although 1.8.0beta1 is well tested and not going to harm your device I suggest you to use the latest version. Don't bother that it's built for JVT. This means that is compiled with JVT initramfs but since there are no significant changes from JVS to JVT there will be no problem.
[Galaxy S I9000 Android Development] seghier:
thank you

fast with game . but i have problem with compass and north direction
[Galaxy S I9000 Android Development] stratosk:
Try to calibrate magnetic sensor. Use *#0*# in dialer and in sensors section you may calibrate it.
[Galaxy S I9000 Android Development] liderzre:
what is the difference between 1.80 and 1.80bm?

thanks
[Galaxy S I9000 Android Development] :
The available memory? (bm=bigmemory)

tapatalked...
[Galaxy S I9000 Android Development] stiwipl:
When I use stock JVT with Semaphore 1.8.0 OC 1.2 and your UV settings then I am getting reboots. That's strange because on Simplicity I had much more aggressive UV (-75; -50; -100; -100; -150) with no reboots. Why is that?
[Galaxy S I9000 Android Development] seghier:
Thank you i see black circle and text : need for calibrate

how i can calibrate it ?
[Galaxy S I9000 Android Development] stratosk:
Turn the phone upside down. Repeat this movement few times until you feel the vibration signal.
[Galaxy S I9000 Android Development] stratosk:
Every cpu behaves in a different way to oc/uv. Keep your settings if it stable for you.
[Galaxy S I9000 Android Development] mar90:
i enable the virtual cache to 50mb but i still got error insufficient space on the device. app is 41mb on the market. hmm
[Galaxy S I9000 Android Development] danieldmm:
I fixed that im my custom firmware by removing all busybox related instalation... After that script work like a charme...

Cheers
[Galaxy S I9000 Android Development] mar90:
sorry.i dont know how is that.:confused:
[Galaxy S I9000 Android Development] danieldmm:
So, assuming you have a ROM in format CWM, you open whit WinRAR and search for word busybox, and delete that,normaly its located in system/xbin then you go in updater-script located in META-INF\com\google\android and delete line containing run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin"); if you have...

Cheers
[Galaxy S I9000 Android Development] mar90:
does that means i will have to reflash the rom after i modified the cwm file?
[Galaxy S I9000 Android Development] danieldmm:
Yes, but you can try with root explorer or similary, delete all busybox files and reboot to recovery, wipe cache and dalvik-cache, if that dont work then flash again CWM Rom modified with the steps i tell...

Cheers
[Galaxy S I9000 Android Development] mar90:
yes! finally.solved it. i just moved the busybox file to someplace else using root explorer.wipe all cache.enable the virtual cache.reboot.and it worked! thanks to you :D
[Galaxy S I9000 Android Development] danieldmm:
:) , but you can deleted cause semaphore kernel is blunded with busybox...

Cheers
[Galaxy S I9000 Android Development] job:
Also have the problem with the compass, did what you suggested but nothing happens :c
[Galaxy S I9000 Android Development] seghier:
always the same problem with compass
[Galaxy S I9000 Android Development] stratosk:
Please retry. The other method is to wave the phone in a figure 8 pattern ( this is the way that is proposed by the Compass application from the market).
[Galaxy S I9000 Android Development] extralife:
Compass works

A bit tricky to calibrate, but it works.

Hint :

In LCD test menu first you go to "magnetic" - test - then switch into "sensor" section.

Now move your phone as long as all 3 axes are calibrated - will see a "3" in the circle.

All done, leave the menu :D

... using tapatalk
[Galaxy S I9000 Android Development] seghier:
hello . i see number 3 in circle but compass don t work
[Galaxy S I9000 Android Development] petsasj:
Strato,

I've moved on to an SGS II, however i poped up to see how things are over here and just saw.

My deepest condolences about your father. I wish you all the best.
[Galaxy S I9000 Android Development] scorpie67:
Hi,

I know this is about the 1.8 kernel, but I would like to know if one of this older kernels are good for UV

Semaphore_kernel_JVR_1.6.0.tar

Semaphore_kernel_JVR_1.6.0bm.tar

Thanks a lot

scorpie
[Galaxy S I9000 Android Development] stratosk:
Hi,

All versions since 1.6.0 use the same logic for OC/UV. So, yes you may use UV in the same way as the last one.

But i can't say If the kernel is "good" for undervolting. :)
[Galaxy S I9000 Android Development] adamslast:
Hi Stratosk,

A modest thank for your great work from TR.

6VB87966WD336635C

Enjoy.
[Galaxy S I9000 Android Development] stratosk:
It's not modest at all. It's great and thank you very much for it! Much appreciated!
[Galaxy S I9000 Android Development] stratosk:
New version JVT_1.8.1

- added smartassV2 governor (as module)

- added Simple I/O scheduler (as module)

- updated Superuser v3.0.6

- updated su v3.0.3

- back to HZ=256

- added IPv6 privacy addon script

- dropped Hard to Kill addon script

You may enable smartassV2 and/or SIO scheduler from Semaphore Script Manager application.
[Galaxy S I9000 Android Development] Rebel2k:
Cool! A new version! Like it and will test it soon! Thanks!
[Galaxy S I9000 Android Development] mehrzad1363:
plz one version without voodoo color :(
[Galaxy S I9000 Android Development] MasterJam882:
@Stratosk

Whats the difference between noop and simple scheduler?

And what would say about smartass? U think it's better than ondemand governor?

Greetz
[Galaxy S I9000 Android Development] stratosk:
Noop is the more simple scheduler (that's why still default in Semaphore :)). It handles the requests in a FIFO buffer.

SIO (quote from the author Miguel Boton):

SIO is based on the deadline scheduler but it's more like a mix

between no-op and deadline.

In other words, SIO is like a lighter version of deadline but it

doesn't do any kind of sorting, so it's aimed mainly for random-access

devices (like SSD hard disks) where request sorting is no needed (as

any sector can be accesed in a constant time, regardless of its

physical location).

I believe that noop is faster but there are reports that SIO is more responsive. So, you may try it and decide if it's more suitable for you.

About governors. Ondemand is my favorite and remains the default one.

I'm still testing the combination smartassV2 and SIO. I think that the phone is slightly smoother. But I don't know about the battery consumption of smartassV2. Still testing.
[Galaxy S I9000 Android Development] :
I have no idea on how much the ondemand governor is tweaked or if he is tweaked, but I had very good impressions from ondemandb governor, a more powersaving ondemand-governor.

I think this was on Insanity-CM.
[Galaxy S I9000 Android Development] sarbe:
Just flashed 1.8.1 via kernel flasher and rebooted, phone was stuck at Galaxy S logo. I was running JVT Odexed, Simplicity 1.5.1 and semaphore 1.8.0. All Ext 4. I had to reflash JVT.
[Galaxy S I9000 Android Development] midikarma:
i guess u better reflash the new kernel via odin m8... i've experienced the same before, after had some bootloop' i reboot the phone in download mode then reflash the kernel via odin... then problem solved :)
[Galaxy S I9000 Android Development] shashank.aviator:
JVT wifi bug

Anyone experiencing frequent wifi disconnection on JVT? Any fix for it?
[Galaxy S I9000 Android Development] pikachu01:
Remove the address reservation setting (based on MAC addresses to IP) and set lease time to something that is not forever (like 1 or 2 days) and/or set static IP address on your phone.
[Galaxy S I9000 Android Development] LordVetinari:
Still no BSOD! Now to figure out which is better... Phone that lags like a drunken cow, or a phone that I have to force reboot 2 - 3 times a day?

Any ideas how to fix the issue?

Thanks,

LV.
[Galaxy S I9000 Android Development] pikachu01:
It's probably a misbehaving app that is triggering kswapd. I once dug up until I found the XDA app being the culprit. Installed tapatalk and I never looked back since.
[Galaxy S I9000 Android Development] LordVetinari:
Intresting. I've trawled logs a few times but I've never found what caused the BSOD. Do you have any pointers for what I should look for? I'm converting back to ext4 now. Do you think XDA App migth be the cuprit in my case as well?

Thanks,

LV.
[Galaxy S I9000 Android Development] gsw5700:
Does smartass mean I don't need profiles in setcpu?

Sent using TCP/IP
[Galaxy S I9000 Android Development] pikachu01:
I saw that XDA app was using up more cycles than the time my display was on. It was doing something in the background, which I postulated lead up to kswapd misbehaving.
[Galaxy S I9000 Android Development] syamsoul:
Use tapatalk, its free in samsung app
[Galaxy S I9000 Android Development] dherre65:
Hi stratosk,

what's the reason to drop the hard to kill launcher option? And i like the smartassv2 governor, it really is blazing fast and responsive, but from what i experienced the battery use blazed too...

Tapatalked
[Galaxy S I9000 Android Development] Greenpeace22:
I have tried the smartass governor. It seems it doesn't go any lower than 200mhz. The phone spent over 55% in that state, so I went back to ondemand governor.
[Galaxy S I9000 Android Development] andip71:
+1

Would like to know that as well. Any reason why this has been dropped?

Not required?

Side effects?

Thanks

Andi
[Galaxy S I9000 Android Development] sarbe:
Thanks mate
[Galaxy S I9000 Android Development] midikarma:
is there any option that i can get the GPU OC in your kernel o mr.stratosk? n how to OC the GPU?

thx :D
[Galaxy S I9000 Android Development] DANIEL TAN:
Sorry but what's the previous HZ value?
[Galaxy S I9000 Android Development] ZaneZam:
It was 300 hz ;-)
[Galaxy S I9000 Android Development] HM.Carbide:
One problem is the name, zeppelinrox is using it in his supercharger.

And it did not make the launcher any harder to kill, it only changed lmk adjustment (My fault).

Secondly, I got on my 2.3.3 (I9000BOJV8) the "Android OS" bug after 4 to 5 days without reboot. I don't know, if it has something to do with it. So anyway I asked stratosk to delete the script, and he was so kind :) .
[Galaxy S I9000 Android Development] andip71:
Thanks, all clear now :-)

Cheers

Andi
[Galaxy S I9000 Android Development] stratosk:
I think that according to erasmux (author of smartass2) the answer is no.

No, you can't overclock GPU with Semaphore. I think existz had released a version with GPU oc but there were no actual gain in performance and dropped it.
[Galaxy S I9000 Android Development] andip71:
BM version?

Stratosk,

1.8.1 version is running fine since today in the morning.

I wonder when you will have time to compile a big mem version too?

Don't want to push... ah, just a little bit :-)

Thanks

Andi
[Galaxy S I9000 Android Development] stratosk:
Hi Andi,

I'm glad that 1.8.1 had no issues (so far :)). Hopefully, I will release bigmem version tonight. As I mentioned in the past it's not time consuming to build the bigmem but I use to check that everything is OK with normal version and then proceed with the bigmem one.
[Galaxy S I9000 Android Development] andip71:
Yes, thats why I gave you my first feedback. Stable so far, although i have to admit I am not (yet) using the new features like smartass and simple IO. But will soon test that as well.

Thanks

Andi
[Galaxy S I9000 Android Development] malcho:
I also didn't had any problems butt it's to early to say.Being on smartass v2 all day.

Will see.
[Galaxy S I9000 Android Development] andip71:
Malcho,

being on smartass v2 all the day - did you notice any big difference in battery usage?

I was not (yet) trying it cause I wanted to see first feedback first.

So, would appreciate your inputs. Of course also on your experience with smartass v2 in terms of smoothness etc.

Thanks

Andi
[Galaxy S I9000 Android Development] malcho:
I flashed gingereal tonight and then early this morning semaphore 1.8.1.

Didn't notice very much battery drain butt it's early to say.

Smartass works ok.Maybe little smoother,phone and contacts opening little faster.

Will see in few days.My current config is not reference to review it.
[Galaxy S I9000 Android Development] darckengel:
Nice to see a new version :)

Thx Stratosk to continue your kernel devs.

Any chance to have a test version including ondemand tweaks of this thread:

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

(But with awake min freq = 100Mhz)
[Galaxy S I9000 Android Development] oserx:
good job stratosk ... i'm testing now your new version ... SIO and smartass ... indeed it seems smoother user experience, quadrant scores are about 400-500points lower than with my other settings ... I'll check battery life and also deadline & smartass ... in my opinion deadline with ondemand should be the best option ... but who knows...

LE: As I wrote in my thread ... I tested today some modified values for kernel and it really gives super performance, games are smooth, but user experience in touchwiz is not very good .. sometimes lags :( So I think users should concern more about smoothness and battery life than brute power and high scores !

LE2: it really seems smoother, but the transition animations take just a little little more time. Just my opinion ..
[Galaxy S I9000 Android Development] jornbjorn:
Testing smartass now. Seemsca little faster yes
[Galaxy S I9000 Android Development] stratosk:
Thank you to continue follow this thread. :)

My main problem with this patch is that I cannot isolate (at least easily) the code to make a second on demand governor as a module and leave the default one untouched. So, i cannot include this in the kernel.

But if you want i can build a test version for you.
[Galaxy S I9000 Android Development] stratosk:
Thank you oserx. Please let me know about your test results.

I can't see any problem with transition animations. But since I don't use them I'm not the right person to check this. :)
[Galaxy S I9000 Android Development] gsw5700:
Loving the 1.8.0 bm kernel, solid, fast, no need for OC with journaling off on system and cache, wicked, can't wait to try 1.8.1 bm.

Keep up the excellent work Stratosk

Sent using TCP/IP
[Galaxy S I9000 Android Development] oserx:
Stratosk you're the man... It's super.. i am now on the phone. as soon as I get back home... i'll write more
[Galaxy S I9000 Android Development] stratosk:
Thanks mate. Bigmem is nice (thanks to existz).

Last week I was trying to make 10MB more available memory on bigmem version and about 20Mb on normal version. But no luck. :) But having 365MB available memory was a temptation, with no recording at all...
[Galaxy S I9000 Android Development] gsw5700:
Your a star dude!

Sent using TCP/IP
[Galaxy S I9000 Android Development] darckengel:
It would be a pleasure to test that :)
[Galaxy S I9000 Android Development] malcho:
Also some lags on touchwiz version 3.

Quadrant 300 point bigger with smartass v2.
[Galaxy S I9000 Android Development] jornbjorn:
smartassV2 still going strong... does not seem to eat any more battery as far as i can tell, but will know more in a couple of days.

i was wondering if it was possible to add fps uncap to the script app?
[Galaxy S I9000 Android Development] Jamirobe:
IT WORKS. well done ;)
[Galaxy S I9000 Android Development] darckengel:
Fps uncap is very unstable (tested on all kernels which tried to implement that), you will be often caped at 49 fps which is worse than the standard 56...
[Galaxy S I9000 Android Development] stratosk:
Bigmem version JVT_1.8.1bm

- 352 MB available RAM (it breaks 720 video recording)
[Galaxy S I9000 Android Development] bassie1995:
Why did you get rid of the HTK script?

That's the one reason I'm holding off on 1.8.1bm right now... :)

How you doin'? Greetings from my GT-I9000!
[Galaxy S I9000 Android Development] stratosk:
This is the answer: http://xdaforums.com/showpost.php?p=18924554&postcount=4111

But if you want this script so much you may use it in 1.8.1.

Just copy it as addon script in /sdcard/SemaphoreScripts/
[Galaxy S I9000 Android Development] midikarma:
thanks for the info sir :) i'm just wondering if it could...

downloading 1.8.1bm...
[Galaxy S I9000 Android Development] darckengel:
I have big issues with 1.8.1bm.

smartassgovernor is stuck at 1.3Ghz with a load of 6%.

Cpu states are not always write (cpu spy don't show anything sometimes).

It's not seem to happen with regular 1.8.1

Edit: I also have that with 1.8.1.
[Galaxy S I9000 Android Development] ivofsousa:
Unable to convert to ext4 - Stock JVT

Hi guys,

plz help: when im trying to apply lag fix over the stock JVT all i get is errors, and then when the phone reboots, and i go again to ext4 manager a message "A CF-Root Kernel was not detected. ext4 manager may not function properly". but i have semaphore installed, as i can see in the kernel version.

the steps where:

Was with custom rom, and turned off lagifx - OK

Installed stock JVT - OK

Installed semaphore 1.8.1 - OK

install ext4 apk and pressed convert - NOK (erros saying not enough space on "system" and unable to restore backup, and then the message that i posted above.

thanks in advance
[Galaxy S I9000 Android Development] midikarma:
pls make sure there're enough space in ur system rom (must be free>2.5mb) which are needed for u to convert from RFS fs to EXT4 fs... u can delete some unuse system apps like allshare, aldiko, days, etc.
[Galaxy S I9000 Android Development] stratosk:
Does this happen only with smartass governor?

Edit:

I confirm this. I reproduced this enabling smartassv2 and reboot the phone. Sometimes cpu statistics does not work.

Please use smartassv2 governor for testing purposes only.
[Galaxy S I9000 Android Development] clawwulf:
Can I install the kernel semaphore JVT_1.8.1 on the Rome Goatrip 4.0 JVR?
[Galaxy S I9000 Android Development] stratosk:
Since it's based on JVR, yes you can.
[Galaxy S I9000 Android Development] midikarma:
currently using Sio + SmartassV2 + UV (-25,-50,-0,-75,-125) +1GHz

performance seems better, but idk if it will consume more on battery or not... compare to previous setting (noop,ondemand, same UV,1GHz)...

btw, i wonder why i cannot UV the 400MHz freq at all.. i've tried all UV n it will result an fc~ any idea?
[Galaxy S I9000 Android Development] clawwulf:
But the kernel is based on JVT and Goa 4.0 is based on JVR! Does it still
[Galaxy S I9000 Android Development] arsalanaly:
1200 ghz not sable on stock rom itz reboot itself randomly
[Galaxy S I9000 Android Development] mickeko:
That argument wasn't about the feature itself. He gave a reason as to how it would be safe that just doesn't apply at all. If someone says something is safe, I expect there to be a somewhat reasonable explanation why. Custom kernels are safe because they don't tinker with things like chargingcurrents. Doing so is a leap of faith, it may or may not work, claiming it is safe without good reason is just crap.

Some devs do extreme experimental stuff all the time, and they say it is experimental, they don't say it is perfectly safe.

Some devs never admit being wrong in any way, and a lot of people wants to believe they never are.

Anyway, after having occasional weird quirks with galaxian, I'm on semaphore now. Galaxian is slightly faster in some ways, but I got sick of occational force closes and reboots.

I've had no issues with semaphore yet. As such, I'm likely to keep it. It is definetely a job well done.
[Galaxy S I9000 Android Development] 3d_jc:
Very nice kernel, as usual with semaphore. Great job and tanks

jc

stock jvt + semaphore 1.8.1 + status bar mods
[Galaxy S I9000 Android Development] demonstone:
I totally agree. I didn't accuse Lukiqq about it. I was saying that so many people are disappointed with that feature and were blaming him of can cause some kind of damage to the phone. Well with other words... ^^

Sent from nobody knows where
[Galaxy S I9000 Android Development] darckengel:
When smartass gets stuck at 1.3Ghz, changing to ondemand keeps the bug. It not always appens, maybe some kind of endless boot somewhere in the code which prevents from changing frequency...
[Galaxy S I9000 Android Development] ZaneZam:
Hi stratosk,

Thx for the new version ! I just want to report that i can't reproduce the cpu stat problems with smartassv2 + 1Ghz! I also can switch to 1.2Ghz, (but not to 1,3Ghz!) in test section w/o problems. But if i reboot with oc enabled then the problem appears. When i switch back to 1Ghz right after that reboot cpu stats start working again.
[Galaxy S I9000 Android Development] rom08:
Is it only with 1.3 ghz or also with other frequencies because I have no problem with smartass and sio for more than 24 hours now.

Edit : I have my answer now.
[Galaxy S I9000 Android Development] ZaneZam:
Strange, i just had a battery drop from 47% to 9% after setting from conservative to smartassv2 on 1.2ghz and a reboot. And in the time of writing this text it increased to 11% (!?) I think switching around a lot isnt so good, hmm :-)
[Galaxy S I9000 Android Development] malcho:
Are you shure that your battery is calibrated?Flashed new rom?
[Galaxy S I9000 Android Development] stratosk:
About the smartassv2 issue:

The problem with the cpu frequency statistics appears only when enable the smartassv2 governor and mostly if the phone boots with this script on. It happens sometimes.

If after reboot (or after enabling smartassv2 on the fly) cpu freq statistics work OK then no problem appears on the device. At least for me. I was testing smartassv2 for a couple of days with no issues.

Please also note that if you want to disable smartassv2 to avoid this issue, you must reboot the device since the module still remains loaded.

I'm thinking to not release a new version without the smartassv2 because we can avoid this issue simply with not enabling this governor and also we will have the possibility to test it.

But I need your opinion on this.
[Galaxy S I9000 Android Development] marck1991:
sry, but how do i enable oc @ 1100 mhz?

thanks for your answers...
[Galaxy S I9000 Android Development] stratosk:
OC at 1100Mhz is not supported in 1.8.0 and 1.8.1 because it caused instabilities. Maybe in a future version.
[Galaxy S I9000 Android Development] davor175:
Hey guys,

I'm using 1.7.5 version and for some reason my phone always freezes with 1.2 OC when I use task manager and sometimes when I open up 3D gallery, after a few seconds phone reboots. I downloaded voltage control and I'm using the 1200mhz profile with 1.325V voltage, what can be wrong?

I want the OC to work because it makes quite a big difference and its most welcome.
[Galaxy S I9000 Android Development] gsw5700:
1.8.1 bm is flying and rock solid, using ondemand as it seems to stay on lower cpu frequencies. Testing sio now against noop, very impressed. Battery life also looks to be very good

Sent using TCP/IP
[Galaxy S I9000 Android Development] ZaneZam:
Yes i am sure that my battery is (was!) calibrated as i am allways doing this after flashing new rom. ;-) Last flash to JVT was a few weeks ago and before switching around settings to test this new semaphore kernel today i never had problems with bat stats. However i think the frequent rebooting was the problem, not any setting in particular.

Recalibrated battery, all is good now, with 1ghz + smartassv2 + SIO

Btw stratosk this setting runs stable for me since you released 1.8.1 and i also think we don't need a new version without smartassv2, but what i need personally is a commit on your git repo :-):-) thx
[Galaxy S I9000 Android Development] stratosk:
Hi,

Can you please try to undervolt 1200 by -25mV (1300mV)?