yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] 4hunter:
and whgy not 3.1? or beta2? im on beta2 and everything work like charm
[Galaxy S I9000 Android Development] mark26:
+1 :thumbup:
[Galaxy S I9000 Android Development] jelennn:
In my personal opinion 2.9 is a litlle bit faster than 3.1 and 2.9 have a little bit less battery consumption. Beta2 is only Beta. It not have a lot of functionalities (important for me weather lockscreen and calendar lockscreen for example) It have a stupid lockscreen widgets and it have a lot of bugs (for example we can unlock the phone with any hardware key). Feel that this is just a beta version. On bugs free, full functionallities version We must wait some time. This are my personal feelings.
[Galaxy S I9000 Android Development] Cu8eR:
There wont be calnedar or weather lockscreen... just donwload widget mate! I am on beta2 and there is more features than in v3.1... and the speed with semaphore kernel is amazing! Battery - 2% during night (7,5 hours)

---------- Post added at 02:02 PM ---------- Previous post was at 02:00 PM ----------

OK, what about a new feature in semaphore manager - switching between BLN and CM? I think it would resolve the problem with BLN/CM community :)))
[Galaxy S I9000 Android Development] stratosk:
Hopefully, it will be on Google play later tonight.
[Galaxy S I9000 Android Development] elitevet:
As already mentioned more than trice - you are a MONSTER

OT. Do you keep track of the Seeder / entropy pool discussion? Would you mind sharing your opinion on the matter?

Thanks in advance

sent from CM powered SGS
[Galaxy S I9000 Android Development] Cu8eR:
Amazing!

What about Call volume hack? It has mackay kernel 4.2 and it seems to be working good

and one more question - Battery life extender - does it have any effect?
[Galaxy S I9000 Android Development] s3icc0:
It can only do the same you can do manually .... so it has no effect (at least for me) - and why would I use dark display, no data, no sync etc.....
[Galaxy S I9000 Android Development] chrischa:
yeah id like to see your opinion too :)
[Galaxy S I9000 Android Development] Driv:
Doesn't support loop device ?
[Galaxy S I9000 Android Development] Michel38280:
Big thanks for us :good:
[Galaxy S I9000 Android Development] Nexxusel:
Anyone can tell me if this file is in Semaphore JB 2.9.3 ? / sys/kernel/debug/asoc/smdkc110/wm8994-samsung-codec.4-001a/codec_reg. Which is present at least in the Dec 31 CM10.1 This file is required for the new version of Spirit FM, which according to its developer mikereidis found a way to remove the speaker damage

http://xdaforums.com/showpost.php?p=36434759&postcount=5134

I'm on slim bean 3.1 right now with 2.6.0

if no such file @stratosk please, could you add this file in the future?
[Galaxy S I9000 Android Development] mindphaser2k9:
+1
[Galaxy S I9000 Android Development] stratosk:
I hope the term 'MONSTER' is good. :) (just kidding) Thanks for the compliment.

Yes, I read it.

Little words about it (I'm not aware about the details, though).

In Linux when you want to get random numbers you have to use /dev/random device. This device produces random numbers using an 'entropy pool' of bits.

When somebody reads this device, the pool is consumed. It needs some time to be replenished. If the pool is empty, the function that uses this device MUST wait for new data (it's a blocking call)

There is also another device: /dev/urandom. Reading from this device is a non blocking. But it produces less quality random numbers.

You can also write to /dev/random. Thus, you may feed the 'entropy pool'. This is the idea of writing data from /dev/urandom to /dev/random.

So, you may achieve a larger pool in /dev/random but with less quality data = less security, because random numbers are used in security related functions.

The big question is: How often the android need random numbers? How often the entropy pool is empty and the function that retrieves random numbers from /dev/random blocks and waits for the pool (lags)?

The author of the thread you mentioned accepts that this was an issue in earlier Android versions.

IMHO, I don't think that this will be an issue in normal operation of the phone.

Anyway, someone could test it. I made a little script to cat the available entropy in the device every 100ms. Put the code below in a file, give it exec permission (chmod 777 filename) and run it from an adb shell.

Use your phone, watching the availability of the pool.

#!/system/bin/sh

while true;
do
cat /proc/sys/kernel/random/entropy_avail

busybox sleep 0.2
done

Call volume hack was dropped 3-4 versions ago. I think it gives bad sound quality.

I don't think that battery life extender will save your battery.

Can you please clarify your issue?
[Galaxy S I9000 Android Development] AusMatt:
Please don't encourage the use of non-random data to generate what people will believe to be random data (i.e. one should never seed from /dev/urandom).

Edit: I should say "It's not a good idea to use non-random data..."

There are some real sources of randomness that could be used for seed data.

e.g.:

- User touch screen interaction time data

- Time of receipt of text messages

- Mobile phone network signal strength (and wireless)

- Data transfer meta data

The list goes on.

This is what should be used for seeding.

FreeBSD uses this kind of approach with it's "Yarrow" RNG and is one of the best implementations around (so much so that I think that their /dev/urandom is the same as /dev/random as there was no longer a need for a poor quality device).

FreeBSD also maintains some entropy on disk so as to re-seed after boot so that there is never a time with low data rate RNG (except just after fresh install).

This message should be aimed at upstream CM10.1 maybe.
[Galaxy S I9000 Android Development] Cu8eR:
Does this kernel include bootloop detection? (in GB this feature was... )
[Galaxy S I9000 Android Development] pacc:
ANTUTU v3.0.3 - Semaphore JB 2.9.3s, 1140Mhz, ROW, Bigmem 409MB

SmartassV2 Settings

- awake:912000

- uprate:20000

- down rate: 99000

- max cpu: 65

- min cpu: 20

- ramp up: 200000

- ramp down: 200000

- sleep wakeup: 912000

- sleep ideal: 228000

- sample rate: 2

- smooth ui: on

128KB (read ahead)

1st - 4609 / RAM 636 / CPU 749 & 181 / 2D 412 / 3D 1932 / Database 470 / SD write 107 / SD read 122

2nd - 4736 / RAM 651 / CPU 753 & 180 / 2D 423 / 3D 1985 / Database 500 / SD write 150 / SD read 94

3rd - 4662 / RAM 645 / CPU 743 & 179 / 2D 413 / 3D 1968 / Database 480 / SD write 150 / SD read 84

AVERAGE SCORE: 4669

512KB (read ahead)

1st - 4637 / RAM 633 / CPU 749 & 179 / 2D 377 / 3D 2015 / Database 465 / SD write 100 / SD read 119

2nd - 4078 / RAM 651 / CPU 756 & 178 / 2D 398 / 3D 1344 / Database 490 / SD write 133 / SD read 128

3rd - 4132 / RAM 634 / CPU 753 & 180 / 2D 402 / 3D 1378 / Database 520 / SD write 139 / SD read 126

AVERAGE SCORE: 4282

1024KB (read ahead)

1st - 4265 / RAM 630 / CPU 749 & 178 / 2D 401 / 3D 1592 / Database 480 / SD write 119 / SD read 116

2nd - 4177 / RAM 649 / CPU 753 & 178 / 2D 401 / 3D 1400 / Database 540 / SD write 137 / SD read 119

3rd - 4201 / RAM 639 / CPU 745 & 179 / 2D 419 / 3D 1469 / Database 490 / SD write 134 / SD read 126

AVERAGE SCORE: 4214

3072KB (read ahead)

1st - 4784 / RAM 626 / CPU 747 & 180 / 2D 409 / 3D 2115 / Database 475 / SD write 101 / SD read 131

2nd - 4852 / RAM 644 / CPU 756 & 181 / 2D 412 / 3D 2091 / Database 490 / SD write 148 / SD read 130

3rd - 4629 / RAM 655 / CPU 749 & 180 / 2D 423 / 3D 1843 / Database 515 / SD write 136 / SD read 128

AVERAGE SCORE: 4755

I was trying to figure out which was the best SD read ahead setting for me, which seems to be 3072KB.

But what surprised me was actually the inconsistent 3D performance...
[Galaxy S I9000 Android Development] stratosk:
I didn't say that I encourage it. :)

Thanks for the info.

Yes, it has a bootloop detection. Although, it suffered from bootloops... :)
[Galaxy S I9000 Android Development] KSLevel11:
Yes, I and some users observed this too.. but what is causing problem? I have no idea...
[Galaxy S I9000 Android Development] gardengnome:
Overclocking

Is there a way to overclock more than 20% with this kernel? My device is rock stable with 120% live oc an I feel like there is more to get out of it. Also I would prefer the traditional method of overclocking by raising the maximum clockspeeds and not overclocking the bus.

In all other respects I like this particular kernel very much.
[Galaxy S I9000 Android Development] Cu8eR:
New version of semaphore app is downloaded... BLN is working good! Thank you...

but, I have enabled Bigmem but my memory is only 397MB after reboot (semaphore app shows me that bigmem is activated but in info tab I see 397MB... I think the settings is not saved properly and dismiss after reboot)
[Galaxy S I9000 Android Development] stratosk:
Are you sure that you reboot and not shut down and boot. In the second case bigmem option will not survive after shutdown.
[Galaxy S I9000 Android Development] Turtuga:
stratosk your kernel is perfect and big big thanks for your work ;)

but i have one question... is possible you take a look in gps files (or something) because in pawipt kernel my gps lock fast and works great but in semaphore gps works great but lock is much slow

sorry my bad english
[Galaxy S I9000 Android Development] stratosk:
Thank you my friend. Thanks for all your support.

Although I have no idea what is the difference between 2 kernels at this point, I will check it.
[Galaxy S I9000 Android Development] GreenSGS:
Master,

2.9.4 still compiling :D
[Galaxy S I9000 Android Development] stratosk:
I'm sorry, my friend. I didn't understand. :)
[Galaxy S I9000 Android Development] GreenSGS:
Don't worry :D but in app changelog you wrote 2.9.4.Also in play store. I thought 2.9.4 is cooking.
[Galaxy S I9000 Android Development] Fenvarien:
2.9.4(s), as a test version, is here: http://xdaforums.com/showthread.php?p=36409372

:)
[Galaxy S I9000 Android Development] burakgon:
Another weird question from me :)

Where can I find libs patch for s version.
[Galaxy S I9000 Android Development] franzyroy:
This, it's what you want?
[Galaxy S I9000 Android Development] Rokostar:
Stratosk maybe you put the link for 720 p libs on the first page to your explanation there are again and again people who ask for it

Bla bla from my bla bla bla just to disturb bla bla (sorry for my bad englisch)
[Galaxy S I9000 Android Development] pxrave:
or implement them in the kernel ;) this would be very great
[Galaxy S I9000 Android Development] 99x:
He already said he doesn't want to implement them in the kernel :)
[Galaxy S I9000 Android Development] 4hunter:
use custom roms, like slim beam with libs on board :)

or if u re so pro and use custom roms, u must be so pro to find and use libs :)
[Galaxy S I9000 Android Development] leon105:
Stratosk it's kernel related problem ?

http://xdaforums.com/showpost.php?p=36489773&postcount=1862
[Galaxy S I9000 Android Development] Indian Devil:
Hey stratosk

One query, as soon as I give Superuser/SU permission to Semaphore Manager 720p videos starts giving problem, I mean videos doesn't play properly. Why could that be?

Using Slim bean ROM.

Regards
[Galaxy S I9000 Android Development] 99x:
Disable bigmem in semaphore manager
[Galaxy S I9000 Android Development] Indian Devil:
Thanks mate but It's already disabled...
[Galaxy S I9000 Android Development] stratosk:
Sorry, it will not implemented into the kernel.

I also think the information in OP is sufficient.

I really don't know. Some people complaint for 3D performance, but I did change anything related.

I will try to check it.

Did you reboot after you disable bigmem?
[Galaxy S I9000 Android Development] Indian Devil:
Mate I never enabled it. It was unticked by default and I never touched that.
[Galaxy S I9000 Android Development] stratosk:
OK mate. I'm just trying to get information trying to help.

Please clarify your phrase 'videos doesn't play properly'. Please also provide a logcat.
[Galaxy S I9000 Android Development] Indian Devil:
Thanks mate. I am away from my system as of now will provide logcat as soon as I reach office tomorrow.

And by not playing properly I mean videos keep getting stuck (freezes for a sec or so) every 2-3 seconds but audio is fine.
[Galaxy S I9000 Android Development] rubervalrfl:
Stratosk, I saw that you changed on github for version 2.9.4, when you want to launch?

Congratulations for great job.
[Galaxy S I9000 Android Development] haseoxth:
You can find it on #4664
[Galaxy S I9000 Android Development] rubervalrfl:
Do not you understand? Could you explain?

My question is why already compiled this version and I'm using, but I would post on my site, and he'll wait out of respect to his official post here first.
[Galaxy S I9000 Android Development] ts1506:
Chill dude. 3D is very good in your kernel.

Here is a screenshot from my CyanAOSP 0.3 with semaphore 2.9.3s , 125% OC , row and 397mb ram.

I feel that 2.5k in 3d is more than enough and certainly better than devil and Mackay (no disrespect meant, I respect the Devs quite a lot)
[Galaxy S I9000 Android Development] stratosk:
Thanks, most probably, tonight.
[Galaxy S I9000 Android Development] NDeaz:
Stupid question, but i think semaphore can change Oc 100-120%

How you choose 125%?

Thx. Sorry for my bad English (
[Galaxy S I9000 Android Development] 99x:
I think the low 3D score in antutu may be due to something in CM10.1 as I only get ~1300 points with sem 2.9.3s. Other roms don't seem to have the issue
[Galaxy S I9000 Android Development] ugoms:
Thought of that too cos semaphore can only oc to 1200
[Galaxy S I9000 Android Development] ImSo3K:
One of the I/O's improve the battery? I don't really understand these things
[Galaxy S I9000 Android Development] stratosk:
2.9.4 on OP.

It's identical with test version. If someone flashed it, no need to update.
[Galaxy S I9000 Android Development] mik101:
They're building it themselves from source I'd assume. As far as I know, you can't go higher on Stratosk's provided build. Unless it's possible to manually run the script from terminal to allow it to be set higher (it may just not be implemented in the Semaphore app to keep people from screwing themselves). Many aries (i9000/captivate/etc) won't even operate stable at 120% oc.

That score of 54xx above is amazing. I thought I was doing well with 48xx using a 120% oc and row in CM10.1. :laugh:

I don't think the 3D benchmark swing is anything to do with stratosk's kernel. It might be low for a run or two but it will give the best score of any kernel I've tried if you're willing to run the benchmark a few times. It's hard to say for sure but the system is likely doing stuff in the background on the "low" runs. I'd also hazard a guess that most people will only post their best runs (or worst in the case of complaints), so take it with a grain of salt.

Not really. Noop in theory should have the least overhead as it doesn't do any command reordering or anything, but I've really been liking how the ROW (read over write) scheduler that was recently implemented has been working (only present in Stratosks builds intended for android 4.2). Previously I used CFQ because I found it was more fair than noop when I was multitasking heavily. Generally I say try a couple different ones over a couple days and see what works most smoothly for you, since everyones work load is different. Back on Gingerbread/Froyo many folks used to recommend Deadline as it priorities reads over writes too, but it never seemed to work all that well for me. I believe the ROW scheduler builds on what the Deadline scheduler was trying to accomplish, but perhaps more successfully. Qualcomm implemented ROW in the linux kernel likely with their own Krait architecture and android in mind, but that doesn't necessarily mean it won't work well on other similar ARM architectures too (check out the very nice antutu result above for example). Hope that helps a bit.
[Galaxy S I9000 Android Development] stratosk:
in live_oc.c:

#define MAX_OCVALUE 130

I just put a limit of 120% it in Semaphore Manager for safety reasons. :)
[Galaxy S I9000 Android Development] yahyoh:
WOW i just installed cm 10.1 with Semaphore 2.9.4s i'm really impressed by the smoothness

and its seems faster than 4.1

thank u for ur great work stratosk :cowboy:
[Galaxy S I9000 Android Development] DerRomtester:
If you test antutu score after reboot it is much higher in 3 Dsectin maybe this is the problem i have found out. But GB 3D performance is faster says antutu.
[Galaxy S I9000 Android Development] Rokostar:
Must i change the Values of Smartass in Semaphore App when i overclock ?

Bla bla from my bla bla bla just to disturb bla bla
[Galaxy S I9000 Android Development] DerRomtester:
Yes you can find the new values for oc some sites before
[Galaxy S I9000 Android Development] yahyoh:
for 3d thingy i got about 1350 with devil (1200 oc + 105 live oc ) and cm10 and about 1390 with Sema 2.9.4s and 114 oc and cm10.1 about 1390

is that normal ??
[Galaxy S I9000 Android Development] DerRomtester:
Reboot phone than test devil reboot than test semaphore

Reboot and test Mackay now 3Dscores should be the same.
[Galaxy S I9000 Android Development] KSLevel11:
I got 1350, then 1850, then 1600... very various results...
[Galaxy S I9000 Android Development] yahyoh:
its seems 100% not kernel issue :eek:

http://xdaforums.com/showpost.php?p=36498246&postcount=4751

but why cm roms get worst 3d score :cyclops:

maybe we should ask pawitp

what do u think stratosk ?
[Galaxy S I9000 Android Development] stratosk:
From reports, as you said it's not kernel related.

Honestly, I don't know what happens. :)

It needs investigation.
[Galaxy S I9000 Android Development] yahyoh:
sorry for noob question : is the GPU driver in the rom or in the kernel ?? :rolleyes:

cuz i remember some rom maker on 4.1 day was using Nexus s driver which give better performance:)

edit : we should forget about benchmark if all games run smoothly :p
[Galaxy S I9000 Android Development] DerRomtester:
TS tested nexus driver and its not so good for games. Stratosk optimus 3d has the same GPU right? Is it possible to port this driver to our SGS? Or a 350mhz or a 400 MHz boost also would increase 3D performance.
[Galaxy S I9000 Android Development] stratosk:
The GPU driver is in the kernel. But, I guess that there are also libs in ROM's side.

I'm not aware about optimus 3d.

Google shows that both devices have the same GPU. But It don't think that I will do this because:

1) I'm not an expert on this (and reading the GPU driver code, it's scary :) )

2) I believe that the GPU driver is the same (maybe different version but the same)

3) I feel OK with my graphics
[Galaxy S I9000 Android Development] 99x:
I wonder if the gpu driver updates imagination tech will be releasing will ever reach our phones (opengl es 2.0 enhancements from CES 2013)

Also at one point devil kernel had a gpu only OC, wasn't working though
[Galaxy S I9000 Android Development] ts1506:
Ya. True.

Just use nstools for up to 130%.

Also, nexus s 3d libs perform very bad compared to the original ones.

Also as far as my knowledge goes, drivers don't control clock speed(from my PC knowledge at least)

Like there are Variants of the same graphics card with different clocks, but they all use the same drivers.

It is also possible that our gpu's aren't meant to run at 300mhz so it wouldn't be stable too
[Galaxy S I9000 Android Development] Indian Devil:
Mate I am not getting any error message while playing videos, it's just that it doesn't play properly the videos stuck for a fraction of a second every 2-3 seconds but the audio plays properly. As I am not getting any error I don't think the logcat will be useful still if you want I will provide that.

Please look into it.

Regards
[Galaxy S I9000 Android Development] stratosk:
Maybe you cat try to increase SD read ahead cache. Or please try another IO scheduler.

Do you face this issue with every video?
[Galaxy S I9000 Android Development] Indian Devil:
Every 720p videos.

Not too familiar with either of the things you mentioned but will search for it.

Thanks
[Galaxy S I9000 Android Development] stratosk:
Please use Semaphore Manager app, to change both settings.
[Galaxy S I9000 Android Development] Indian Devil:
Change the settings using Semaphore Manager-

Live OC - 110

Active Governor - Smartass V2

Under Smartass V2 - Everything default just enable Smooth UI

SD Card read ahead set to 512kb

Now Videos are playing fine, thanks a lot :good:

Any other tweak you recommend mate? Not too familiar with it so any advice would be really appreciated.

Kind Regards
[Galaxy S I9000 Android Development] 99x:
Depending what the current Scheduler is set to you may want to change it to achieve better performance, I personally use SIO, but ROW is quite popular these days
[Galaxy S I9000 Android Development] Indian Devil:
Thanks mate selected the SIO only.. Couldn't find that option last time hence nothing was done with that :o
[Galaxy S I9000 Android Development] Taomyn:
Can anyone tell me how I can clear the battery stats? Currently on 2.9.3 will update later, but I could have sworn there used to be an advanced CWM option to wipe the stats.

I know I need to do it because the phone will sit at 1% for hours where as the previous drops were far more rapid. I tried simply draining it until empty then fully charging it, but the same happens. The last time this got sorted for me by wiping the stats through CWM.
[Galaxy S I9000 Android Development] leon105:
With SD-Maid Pro.
[Galaxy S I9000 Android Development] Und3rtaker:
how do i turn led notification off?

have this problem since c-rom bean v2 with semaphore kernel 2.9.3. tried to set cmled to 0 in nstools, but it doesn't help. do i need an app from market or something, and if which?
[Galaxy S I9000 Android Development] stratosk:
Hi, it supposed to have options with all available governors under governor menu.

Please try to copy in /sdcard/SemaphoreScripts all S10enable_gov* scripts and your new performance script.

I think there is a shortcut (key combination) for screenshot, but I can't recall now.

I'm on Slim Bean at the present.
[Galaxy S I9000 Android Development] matesc:
Hey stratosk! I heard from tomassafca, that the usb mounting problem is:

1. Related to the theme manager in cm10

2. Already merged in htc one x

3. coming soon to i9000

So people, if you are facing this problem, set the default theme, reboot and try it again.

For me it worked on cm10 and slim bean.

Greets
[Galaxy S I9000 Android Development] l4m3:
Screenshots are taken by long pressing volume down and power at the same time.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] nevzat74:
Unfortunately it did not help on my situation.

Does it matter which launcher we use? I'm currently on Holo Launcher HD.

By the way, I also tried "ultimate kernel cleaner" script, it did not help either.