yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Starsream88:
Flashed 65fps test version and the phone feels smoother, no lags on gaming, and animations are faster :good:

However this fps patch causes some issues, boot animation and can't access recovery :(

Hope we will test 60fps, maybe it will be optimal settings for our devices.

Thank you Stratosk, you are the boss :good:
[Galaxy S I9000 Android Development] stratosk:
Actually, I'm not an expert on this.

I change the lcd panel frequency. Default is 60 and gives 56fps. I tested 68 (glitch) and 72 (air kernel) which gives almost 65fps.

Changing this frequency affects the frame buffer driver fps value.

I don't know the exact mechanism, though.
[Galaxy S I9000 Android Development] jugster:
I agree with that. Do you agree that if those issues are somehow solved then it would definitely be included?

I take stability over performance any day, but if I can have both, I'd like that too :)

Signature? Signature!
[Galaxy S I9000 Android Development] kaza:
I had a huawei u8800 that had 45fps lock, with a script we could increase frame rate to 54, one more fps than 54 and the screen would start to show tearing. thats problably the problem of our screen at 65fps in boot, unfortunatly i cant help, i have no knowlege in this matter
[Galaxy S I9000 Android Development] AlexandreT:
Does anybody know if these problems with the 65fps patch also occur in the NexusS roms? If it doesn't then I guess there is a good chance we should also be able to fix it like they did.
[Galaxy S I9000 Android Development] burakgon:
Can we totally disable vsync? This will make this device a gaming monster. ı'm sure.
[Galaxy S I9000 Android Development] prbassplayer:
That is kernel and rom modification
[Galaxy S I9000 Android Development] didhiy:
afaik, it has been removed from official crespo cm10 kernel
[Galaxy S I9000 Android Development] philidor:
I flashed my phone on my train trip. :) I know is not a good idea to flash a experimental kernel on your only phone when you are out of your house for many hours but.... ehi I asked for this mod and now I have to try it.

After a long strange boot animation my phone wake up with new beautiful wings.!

For now all work (except for boot animation). No live oc but I feel better performance

Stratosk thanks for your work
[Galaxy S I9000 Android Development] a g bell:
@stratosk In order to change 65 to 60 does it require much knowledge or can a cut and paste expert like myself do it?

Yes l have read previous post 60 being 56 is it just a case of edit text?Or is more complex:confused::)
[Galaxy S I9000 Android Development] stratosk:
As I said in my previous post, I don't really know.

I tested several values for lcd frequency:

Current value: 60 - 56fps

Values: 60-65 - still 56fps and nothing breaks

Values: 66, 68 and 72 breaks graphics in recovery, boot process. Up to 65fps according to OC value.

It seems that the frame buffer driver depends on this frequency to arrange the fps. But, I need to investigate why it breaks display in boot process (I guess it related that the framework didn't load yet, so maybe it needs changes to ROM also).

Also, because this was asked, the frequency I mentioned, is initialized in early stage, so I don't know if it's possible to change it on the fly.

So, I think I will not invest more time on this.

I was a little mad with Google about the availability of N4. I thought that I would have issues to purchase one in Greece. But I read that it was sold out in minutes in countries that was available in Google Play. Honestly I hate these marketing procedures.

I don't know how, when and IF I will purchase a N4, but something pushed me and I just built my first N4 kernel. :p
[Galaxy S I9000 Android Development] Zatta:
The idiots are not even selling it in the Netherlands. Also a non_play country.

Taptalked u see .. əəs n pəʞlɐʇdɐʇ
[Galaxy S I9000 Android Development] KSLevel11:
@Stratosk

Is 2.5.0 is "up to date" with cm10 stock kernel? I mean, are there (in cm10 stock kernel in today stable release) some changes, that aren't in 2.5.0?
[Galaxy S I9000 Android Development] yahyoh:
FYI N4 is not supported by AOSP :(:(

https://groups.google.com/forum/?fromgroups=#!topic/android-building/-ymcoMuDAbA

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

http://xdaforums.com/showpost.php?p=34072540&postcount=21

https://plus.google.com/u/0/101093310520661581786/posts/ixrAR4Rry6k

:crying:
[Galaxy S I9000 Android Development] stratosk:
There are no changes from cm10 stock kernel, that I would like to include. Latest was about OC/UV code.

I tested Semaphore on latest stable CM10. It's OK here.
[Galaxy S I9000 Android Development] stratosk:
Yes, I read about it. I hope they will, in the near future.

Fortunately, Linux kernel is open source under GPL. ;)
[Galaxy S I9000 Android Development] DeusEx80:
Also here :)
[Galaxy S I9000 Android Development] yahyoh:
kernel source seems already available :D

https://android.googlesource.com/kernel/msm/+/android-msm-mako-3.4-jb-mr1-fr
[Galaxy S I9000 Android Development] fmc000:
So would you mind releasing a new version with those changes and without the 65fps thing? Or are you waiting for something else to add in your next non-test release?
[Galaxy S I9000 Android Development] stratosk:
Thanks. I already have it and I built it.
[Galaxy S I9000 Android Development] elitevet:
Did he come? :p

Sent from a CM10 powered SGS
[Galaxy S I9000 Android Development] yahyoh:
WOW u r so fast :cool:
[Galaxy S I9000 Android Development] KSLevel11:
I flashed 2.5.0 on latest Cm10 stable, after flash, I wiped CACHE and Dalvik-Cache. Then I choosed "reboot system now". Phone gave me 3 bootloops (galaxy s logo > Semaphore logo) and then it booted to semaphore cwm recovery. So I wiped CACHE and Dalvik-Cache again, rebooted, phone booted up properly.

Why it gave me these 3 bootloops?

EDIT: Here is the last_kmsg file: (after this 3 bootloops, wipe cache, dalvik-cache, bootup)
[Galaxy S I9000 Android Development] pxrave:
yeah ur my man dude :)

i know you all hate this question? ;)

but i want to build a custom rom from cm10 final source ;)

do you release the new kernel this week or next? or really no clue?

thanks for answer this
[Galaxy S I9000 Android Development] alexovy:
Did anybody tried to flash back the old kernel directly from Android and if yes, with witch software?
[Galaxy S I9000 Android Development] cezararon:
stratosk can u bring some light on something for me please...i dont know why but i ve been running around 90-100mb free ram (currently on cm10 7/11 with sema 2.5s) for quite some time now,although most people around here are reporting 150-200 ram. i m having 50 apps installed showing in launcher and in running apps i have around 10 apps constantly running,but adding them up should get me around 200-210 free ram
[Galaxy S I9000 Android Development] Helloworld294:
I'm running around 50-70mb ram... I think its normal

Sent from my GT-I9000
[Galaxy S I9000 Android Development] superkoal:
Your operating system might need some space too, but won't admit that ;)
[Galaxy S I9000 Android Development] pikachu01:
It depends on your LowMemoryKiller as well as what kind of apps are in the background (some that requires itself to be in the background thus consuming more memory).
[Galaxy S I9000 Android Development] Kingo64:
False. Humans are very capable of seeing the difference between frame rates.

24fps

48fps

Fluctuations in frame rate such as sudden rises and falls are more noticeable than constant frame rates as you mentioned, but you should always run an interface at the maximum frame rate of the display.

For anybody who can't see the difference, you should see an optometrist or a doctor.
[Galaxy S I9000 Android Development] s3icc0:
I am running 50-120MB max .... mostly around 90MB
[Galaxy S I9000 Android Development] RivalComp:
I've tried this test version. Asphalt 7 runs smoother. But nothing special that would make me say wooow. I think the amount of fps isn't annoying but the hickups while scrolling. When you scroll with your finger and the screen sometimes "freezes" for 0.01 ms. I can't explain it but I hope you know what I mean. :)
[Galaxy S I9000 Android Development] BlueFlame4:
I don't get why people still want free RAM on their devices, even though it was discussed a zillion times that free RAM is wasted RAM. This is a Linux kernel, not a Windows one. Linux keeps "closed" apps in memory as long as possible and just flags that part of the RAM as overwritable.

Sent from my Gameboy Color
[Galaxy S I9000 Android Development] lerkin:
You are not completely right. I have many situations than 'yours' wasted-free ram completely disappeared, than only Nova launcher stays in cached processes, and active processes (whatsapp, dropsync, or something like that) stay to restart again and again. It happens after some uptime. I think this occurs because of memory leaks in Rom (kernel ?) or apps installed. Recently cm plugged another memory leak so I hope those real low-ram situations will occur less frequently.
[Galaxy S I9000 Android Development] 99x:
I notice you are running 2.5S have you flashed the 720p patch to gain some extra ram?
[Galaxy S I9000 Android Development] mindphaser2k9:
Are you kidding? 720p patch doesn't gain any extra ram, it just fixes video playing/recording.
[Galaxy S I9000 Android Development] Kingo64:
I can't seem to enable logcat. Is there any init.d scripts that I should edit in order to enable it? If so, where and how can I do this?
[Galaxy S I9000 Android Development] mindphaser2k9:
There is a switch in Semaphore Manager, you have to reboot then.
[Galaxy S I9000 Android Development] Kingo64:
I have that ticked on, it seemingly does nothing. My logcat still doesn't work/exist at all
[Galaxy S I9000 Android Development] mindphaser2k9:
Have you rebooted? It works fine for me.
[Galaxy S I9000 Android Development] Kingo64:
I found it why it wasn't working. My /system partition was 100% full so there was nowhere for it to write. After formatting /system and reflashing everything it works now due to the free space
[Galaxy S I9000 Android Development] yahyoh:
its cm problem seems there is ram leaking on cm10

with fresh install for cm10 without any apps + sema 2.5s ram goes about 120 :cyclops:

with slim bean 2.9 + sema 2.5s with all my apps after reboot free ram 210 -170 and now after 2 days free ram is 135mb :)

stratosk i have little questions why the ram become lower and seems can't restore what i get after reboot :rolleyes:
[Galaxy S I9000 Android Development] 99x:
Yea sorry, stupid moment there - I'm always encouraging people to use the S version, so I'm not sure what happened lol :eek:
[Galaxy S I9000 Android Development] Grondinm:
Love your kernel. So far it has given me the best battery life out of all i have tried. The only thing i miss is Voodoo color i find it gives a more vibrant color if it is configured properly.. I was wondering if you would consider adding it and if not why?

Also i just want to confirm that the 720p patch is only required if you use the s version of kernel.

Either way thank you keep up the great work.
[Galaxy S I9000 Android Development] cezararon:
yes i ve flashed the patch,but that s not really my issue.i dont think its kernel related...i think its something with cm10 like some other guys pointed out,because some times i have 60ram free sometimes 120 with the same apps running.i m just really curious whats happens... thanks
[Galaxy S I9000 Android Development] superkoal:
You can try slim bean if you want, i didn't notice this kind of memory leak there.
[Galaxy S I9000 Android Development] lerkin:
Just installed slim bean too. Hope that memory management dysfunction does not curse this Rom.
[Galaxy S I9000 Android Development] stratosk:
Your last_kmsg seems normal. You should get it when your phone rebooted in recovery.

Anyway, this is the known and unresolved bootloop issue. I'm sorry but I don't have an answer for this.

I'm sorry, I can't say for sure. Maybe a version with minor fixes this week (like the test 2.5.2 without the 65fps).

I'm sorry my friend but I didn't understand your question. Do you mean that after reboot the free memory remains low?

Thanks for your comments.

I'm sorry, no Voodoo color in Semaphore. I find CM colors OK and I am not good at colors. :)
[Galaxy S I9000 Android Development] yahyoh:
i mean after reboot ram will be about 200 mb after 2 days of using its will become about 135 or a bit more or less and that amount of used ram never restored until i do reboot :)

( maybe some of my apps cuz that problem i will do some more investigation :p )

and thank u for ur help my friend and thank u for amazing fast kernel :highfive:
[Galaxy S I9000 Android Development] KSLevel11:
I understand. So, this is normal right? Is it always 3 x bootloop and then normal, properly boot up?
[Galaxy S I9000 Android Development] pxrave:
thanks for the answer ;)

do u noticed some more speed in the 3.4 kernel?

or is this new version not compatible with our branch ;)

3.4.18

or

3.0.51:highfive:
[Galaxy S I9000 Android Development] stratosk:
I really don't know if it's a memory leak, or a normal behavior (I believe the second).

After a reboot, there are no cached apps. Opening apps, android will cache as many as possible.

There are no reason to have 200MB free RAM, killing cached apps. IMHO, it's more efficient to have 100MB free and 100MB cached apps.

Of course, it's not normal. Bootloop is an issue even if in your case you may recover easily after 3 times.
[Galaxy S I9000 Android Development] stratosk:
3.4.0 kernel in android source is for nexus 4. And of course I didn't test it.

For our device, 3.0.51 is our kernel (unless, someone will merge Samsung stuff to 3.4.0)
[Galaxy S I9000 Android Development] pxrave:
i hope someone will do this :)

it would be great
[Galaxy S I9000 Android Development] lerkin:
Unfortunately after only 3 hours uptime on slim bean free RAM dropped from 150 mb to 50 mb free for cached processes. That means I can only run my Launcher and something else like tapatalk forum app, if I launch Browser, tapatalk will be closed. That means no multitasking.
[Galaxy S I9000 Android Development] prbassplayer:
You do understand that thats how its its meant to work. Specially on our devices with limited ram. Everything keeps needing more ram we can't just swap the ram module like a PC lol.
[Galaxy S I9000 Android Development] matesc:
Hey!

Does anybody have an access to recovery with the test kernel on 65fps? has this been aleady discussed? No time to search. Sorry!!
[Galaxy S I9000 Android Development] yahyoh:
for me after 50 hours uptime i still have about 130mb free ram , i don't use alot if apps that stuck in ram

i have now in ram google services - whatsapp - dsp manager - aosp keyboard - and setting ( which will get cached after exit from running apps )

edit : i suggest for u to analyze which app cuz that ram leaking i've read somewhere that bad apps codes can cuz ram leaking ;) and if u use viber just delete it its freaking ram hogger + did u tried to not restore the apps data from another rom maybe just u can try to restore games data only )
[Galaxy S I9000 Android Development] lerkin:
Yes, I thought about clean installation of apps, Once I will try it.
[Galaxy S I9000 Android Development] chrischa:
imo not: you should flash 2.5.0 with odin i think
[Galaxy S I9000 Android Development] alexovy:
Odin the tar
[Galaxy S I9000 Android Development] _Legend0:
What do u mean by acces to recovery? No three combo button access or what, cuz after installing test kernel my screen is just displaying for eg(it happens all time) at boot process, the Galaxy S (first screen) is displaying properly, but then everything just messed up. The Semaphore logo is showing on all screen. Here is vid : http://db.tt/Svt9of6B (sorry for bad quality, recorded from my brothers Nokia 5130 XM, and for the link. My YT app just ignoring my req to send vid). Is there any way to get it working or my hardware is broken?

//EDIT

I've tested this 65fps version on CM10, Slim Bean and fanzyroy's ROM. AT all of these i had this same issues.

Wysyłane z mojego GT-I9000 za pomocą Tapatalk 2
[Galaxy S I9000 Android Development] makimac:
same happened to me with the 2.5.2 test version and also the 2.5.2s version

i restored my recovery with a devil kernel tar version through odin, all is good now

i flashed with odin 307 from this thread http://xdaforums.com/showthread.php?t=1728605

and the devil kernel tar: http://rootaxbox.no-ip.org/derteufel/jellybean/i9000/181/
[Galaxy S I9000 Android Development] _Legend0:
Nice to know it. I have already restored by odin 2.5.0 version. Everything is now working well. I think we should wait for official relase.

Wysyłane z mojego GT-I9000 za pomocą Tapatalk 2
[Galaxy S I9000 Android Development] pxrave:
i know why the 65 fps version didn't work with our phone

its very simple vsync = hz

our phone had max 59 hz

max vsync = 59 fps

some phones only work with 56 fps but its a very strange issue

best example test on your pc screen => everyone know flat screen = 60 hz (normal)

setup 100hz =>for better smoth (kidding)

and you will see same crazy lines as on our galaxy s

the boot works because its the same as a bios on pc if the hardware isn't corrupt our pc boot into bios

we need a string in a config to setup the vsync rate

this would be great

so you can give us a option on semaphore manager also
[Galaxy S I9000 Android Development] sigarocubano:
But are the problems for the experimental build only in the boot ? and Recovery?
[Galaxy S I9000 Android Development] yahyoh:
i thing s1 screen refresh rate is 56Hz not 60 :rolleyes:
[Galaxy S I9000 Android Development] _Legend0:
Nope, they are for me on all screens.

Wysyłane z mojego GT-I9000 za pomocą Tapatalk 2
[Galaxy S I9000 Android Development] RivalComp:
At the first boot after flashing test version the lock screen was unreadable, just full of scrolling horizontal lines. I could interact with it but I couldn't see anything. Then I pressed power button to go to standby and again to wake up and this made it usable.

Now I'm back to official 2.5.0 with Odin because I haven't seen any remarkable difference between official and test. Games seemed to run smoother because of higher fps but for everyday use the higher fps is not a big deal for me...
[Galaxy S I9000 Android Development] pxrave:
this is what i said

screen 56-59 hz

different screen = year of built

same as the different flash chip

56 hz = 56 fps vsync will work on all galaxy s or their us variants
[Galaxy S I9000 Android Development] stratosk:
If somebody wants to experiment:

http://xdaforums.com/showpost.php?p=34178666&postcount=238
[Galaxy S I9000 Android Development] Solictice:
Destroyed my screen today, so I can't see anything on my phone :\

So I'm wondering if someone can describe the exact steps in CWM to connect to USB, since everything works. I even can hear i'm getting whatsapp messages. Just can't see it. Would be a major relieve if someone can help me out here, so I can save my data!

I'm running Semaphore 2.5.0s (obviously) with CM10
[Galaxy S I9000 Android Development] stratosk:
- 6 times volume down

- home button

- Twice volume up

- home button
[Galaxy S I9000 Android Development] ugoms:
That's a master piece. Works flawlessly
[Galaxy S I9000 Android Development] Jonae:
I have installed semaphore s version. But now when i want to record video i get error gallery has stopt. Help please.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] prbassplayer:
2 things either rom doesn't have hugemem mod. Or you have big mem enabled and trying to record 720.
[Galaxy S I9000 Android Development] Jonae:
I am trying to record 720p. Also playback is laggy.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] Toldo:
If you use bigmem, then 720p playback and record doesn't work properly.
[Galaxy S I9000 Android Development] Michel38280:
+1 to get some battery saving ? :rolleyes:
[Galaxy S I9000 Android Development] stratosk:
LiveOC is less stable to 1200 due to bus overclocking. Please try 1140MHz.

Last update was 4 days ago. :)

No changes regarding this issue.
[Galaxy S I9000 Android Development] beint:
Video files on slim vs. no slim kernel versions

Hi Stratosk

I'm on Elites B9 JB rom. Stock is Sema 2b latest. When installing the 2bs version of Sema, the videofiles I have is deemed as unknown(unplayable, "cannot play this file") by the system. Now when flashing to the 2b version again the videofiles ar OK again, playable and I can record videos.

I also had this problem on B8 from Elite, but then I wasn't aware that flashing the 2b version solved it.

I assume the the GNEXUS port from elite is patched, i.e. can run the s versions of Sema kernel. All other thing ran flawlessly.

This sounds as a bit strange to me. Can you please look into it?

Br

Beint
[Galaxy S I9000 Android Development] gaurav2009:
maybe flashing this can help u

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

and try dice player and bs player ...they are best for video playback...
[Galaxy S I9000 Android Development] beint:
Thanks for the tip, but the issue was rather that the system couldn't recognize the video files. I know that there is problem with 720p recording, however I record in 480p anyway.

Again, tx for the tip :)

EDIT: And I have tried the 3. party players when in this situation. There you can choose between HW and SW decoding. Using HW decoding din't work, but SW decoding did regarding playback. I guess the system allways use HW decoding.
[Galaxy S I9000 Android Development] HiKsFiles:
@Stratosk,

Are you considering an eventual /datadata compliant version of Semaphore at some point in time?

I got one of those slow MoviNAND equipped phones, so Slim Bean & Semaphore JB are a no go for me :(

I'm not expecting this to happen soon, just asking.

In any case, keep up the good work ... as always :)

Thanks
[Galaxy S I9000 Android Development] stratosk:
I don't believe the no /datadata in JB is the issue for the famous lag. I read reports that HellyBean is also facing this issue.

It's not my decision how a ROM needs partition sizes. Anyway, I am not going to release a /datadata version unless pawitp decides the opposite.

In my opinion (maybe I'm wrong) the lag is there because:

1) Jelly Bean is more hardware demanding ROM (more I/O as pawitp said).

2) There is something in ROM and/or kernel that need to be implemented/fixed.

I also have the lag. For me it is more noticeable during browsing in stock browser. UI stops responding for 1-2 seconds. It happens "randomly". You may also see warnings/errors in logcat during the lag ("skipped frames"). I don't think that there is access to /datadata during browsing (or maybe very little access).
[Galaxy S I9000 Android Development] kb909:
Hi Stratosk

Big fan for a while now. Any reason for not a data/data version of your kernel?
[Galaxy S I9000 Android Development] stratosk:
Hi, thanks.:)

Please read the post before yours.
[Galaxy S I9000 Android Development] HiKsFiles:
Thanks for the answer.

I'll most certainly give Slim Bean & Semaphore JB another shot when another more mature release of Slim is made available.

But from personnal "feeling", nothing to do with log analysis or anything more scientific, this very much look like a hardware issue more than anthing else.

Now for some more wine with my girl watching a movie on this rainy saturday night... :cool:
[Galaxy S I9000 Android Development] mdacic:
Hi people. Stratosk thanks for the kernel!

Since installing the newest version everything seams more smooth.

I have enable

smooth ui

1140mhz

CFQ module

But please tell me what is the voltage for 1140?

On gingerbread I used 1300mhz with no problems. Why are we now limited to a lower speed?
[Galaxy S I9000 Android Development] Silentbob999:
Where you in liveOC at 1300mhz? Because with liveOC everything is speed up, including the bus, so it is normal to get lower frequency. However the speed (feeling) should be very very close... (1140/1300, 1200/1400)

Don't expect any changes regarding OC on that kernel (any ICS/JB Semaphore) , liveOC is satisfying for Stratosk and most of his users.

LiveOC is unblocked up to 1300mhz but you are already lucky if you are stable at 1200mhz.

Envoyé depuis mon GT-I9000 avec Tapatalk