yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500 Android Development] fserve:
I have a damn f***ing good announce, touchscreen is even better on a new version of my gbs-touchscreen-driver that i'm testing here, franco gave an excelent support to get on this stage.

New version of the driver got some of my improvements made for the latest goldenleaf and merged with the latest improvements that i've made for gbs kernel (yes, i did two drivers with different ways to fix the same thing, and no, i dont have that much free time.).

How it's improved right now: (testing with Cool Tool with 0.5 update interval)

1 finger moving around 15% at the maximum use!

2 fingers normal using: 20% at the maximum use!

2 fingers crossing around very fast to get the maximum cpu use: 55%

But those values are not good!!!!!!!!!!!!!!!!!!!!!

We always talked about the minimum values, now, we can't. Cos this **** got a hell of improvement ;-)

It is stuttering a bit, so i need to work a bit more until it's stable to be tested and released.

The less touchscreen uses cpu, less battery will be wasted;

The less touchscreen uses cpu, more cpu will have power to gaming.

Thank you, donate if you like :-)

oops, sorry, forgot that

know bug, called 'darker screen' it's a bit rare for some. It is a side effect of my blackscreen fix.
[Optimus One, P500 Android Development] viv_jen:
Is it out for testing?

Would like to try it out
[Optimus One, P500 Android Development] sweetnsour:
will these fixes be implemented on all of your kernels (including your .35 goldenleaf)?
[Optimus One, P500 Android Development] franciscofranco:
The fixes can be used in any kernel, either .32 or .35. What I did was described two pages back, me and fserve just discussed those changes and tweaked one or two values until we were satisfied, as far as he can tell me, it looks pretty neat. Sadly I did not try it, I just coded it. Community happy = me happy.
[Optimus One, P500 Android Development] fserve:
Yes, obviously touchscreen driver will be merged for all my kernels, i just need more time to tweak even more.

But for now, I REALLY need I/O Schedulers benchmarks

On any kernel. [just tell me which one was used with the version].

Use Antutu SD card IO to test, please.

Dont forget, benchmark all I/O schedulers at once.
[Optimus One, P500 Android Development] 32bit:
Ooops!

Gbs-v20-cfs-newfix: I have a black screen when unblocking! It was never before!

I still can unblock the screen by blindly swype on, but it is extremely inconvenient.

It could be due to someone crying for noise pattern... :(
[Optimus One, P500 Android Development] hzoner:
both GBS are optimized for performace, BFS for gaming, CFS for multi tasking (for everyday use)

and Goldenleaf is optimized for battery life.... (also fast in games) but if you want pure power use GBS gaming...
[Optimus One, P500 Android Development] sweetnsour:
sorry for the stupid question :p this is pretty exciting news

here are my results for goldenleaf 111205:

noop: 132

anticipatory: 123

deadline: 143

cfq: 113

sio: 129

vr: 145
[Optimus One, P500 Android Development] nd4spdbh:
Fserve. I just updated to your latest goldenleaf... v111205, i was previously on v111108 before you started messing with touch stuffs. And the UI on the latest is much more stuttery, when flicking between pages there is almost a lag of sorts... almost like it waits for you to do the entire flick before the UI actually moves. Also scrolling within menus etc isnt as smooth as before. Gonna give it a day then switch back to 111108 and see if i am truly noticing the difference.

Thanks for all your hard work fserve.

~Nd4
[Optimus One, P500 Android Development] viv_jen:
Jus put v20 gamer on void

Games extra smooth no lag

But scrolling shuttery

Here i did some testing

Noop

Vr

Sio

Deadline

Quadrant scores

Are also high

In short a nice gaming kernel

(Testing with real football 2011)

Better than the previous ones

And m sure ul solve d scrolling problem
[Optimus One, P500 Android Development] server3249:
goldenleaf latest version is terrible, phone goes into reboot loop.
[Optimus One, P500 Android Development] buzzdr0id:
Both GBS have VSYNC OFF ? I feel so. If yes, then please turn it ON.

The gamer version is stuttery ! Waiting for your new test versions :cool:
[Optimus One, P500 Android Development] sweetnsour:
having no issues on my end :confused:
[Optimus One, P500 Android Development] Blueyedevil:
I just installed this morning gbs20 for about an hour or so, and after the goldenleaf 1205 and tested both in Antutu and Neocore. Before this I had gbs18c.

From the start I can tell you this much: Antutu SD card score is NOT set in stone. In 18c I have tested @729 and got some scores, then @748 and got LOWER scores.

Anyway, coming back to the latest versions tested gbs20(CFS non gamer) and got an Antutu total score of 1851 and I/O was around 7Mbps write (sorry but I didnt write it down and cant remember exactly) and 15.1 Mbps read.

Then I installed goldenleaf and tested @729 and @768.

729 => 10.1 write 16.2 read

768 => 10.7 write 14.4 read

768 2nd run => 11.1 write 14.0 read ... :confused:

Edit : forgot to mention - using A-Data 16Gb class 6 micro SD.

How come I get lower read scores at higher freq?

Plus, the goldenleaf seems, to me at least, that is not so smooth as gbs20 (even gbs needs the overclock @729 in order to be really smooth).
[Optimus One, P500 Android Development] xuanduc987:
v20 gamer BFs: benchmark SD IO only

noop: 114

anticipatory: 134

deadline: 117

cfq: 118

bfq: 112

sio: 97

vr: 120
[Optimus One, P500 Android Development] kyerie030:
Here's my result for the I/O:

Testing:

Mik's 6.5.7

gbs v20-gamer

480~710mhz

InteractiveX

sio

MMC: Kingston Class 4 8GB

note: 1881 (ave) score on deadline, 7.9MB/s 17.9MB/s (+ or - 0.3MB/s tested 3 times)

Other tests:

Deadline

Noop

Sio

Vr

Sio has highest write. Other schedulers look the same to me. :P
[Optimus One, P500 Android Development] gekko69:
So true. Run it three times in a row and you can get three very different results (especially with sd speeds) .
[Optimus One, P500 Android Development] hzoner:
Here's a tip.

If you want your phone to be fast, Don't install fancy apps that uses a lot of memory. some app use a lot of background cache. install only what u needed most for your daily use. my phone when idle has about 300+mb of free memory while almost a hundred been used. ;) i use 3 widgets (clock+weather, swiss and music), and some icon shortcut for my desktop. i have almost 200 apps installed most of them are games. got 8gb SD card partitioned, 6.Xgb+1gb for sd-ext2.
[Optimus One, P500 Android Development] kyerie030:
I'm getting + or - 0.5mb/s for the tests using antutu sd tests.
[Optimus One, P500 Android Development] Human_dude_007:
Anyone having wifi issues on goldenleaf 5/12?
[Optimus One, P500 Android Development] kyerie030:
Whoa................ weird!!!!

I just went into misplaced screen bug to black screen bug! (and I think this is because I changed the LCDDensity. :p) running v20-gamer.
[Optimus One, P500 Android Development] fserve:
teste the new one, please. ( goldenleaf-111206 )

blackscreen fix will be reverted in new releases.

should fix that.

EDIT: test it please, v20a got released

blackscreen fix will be reverted in new releases.

should fix that.

EDIT: test it please, v20a got released

Weird, no one had this problem, but, test newest release. goldenleaf-111206
[Optimus One, P500 Android Development] dnle71:
flashing now..cfs
[Optimus One, P500 Android Development] sprite00:
OC:480-748(smart ass)

ROM: Oxygen

Kernel: franco.Kernal-gbs.v20a BFS

Quadrant:1400 points

Neocore:58.9 FPS

Antutu:1744

Pretty good :):p
[Optimus One, P500 Android Development] Human_dude_007:
Flashed already ...seems a bit more smoother..:-)
[Optimus One, P500 Android Development] Human_dude_007:
Flashed franco.20a.cfs

Get a blackscreen for about 2seconds however it dissapears on its own.using dax 's ics themed rom.

(Screen on animation already off)?
[Optimus One, P500 Android Development] sprite00:
Ok...little problem...i can't download from market...it's says your item will be downloaded and after this the little arrow appears on the top bar and disappers...what shoul i do?

//i restarted the phone and now all seems to be fine! :)
[Optimus One, P500 Android Development] skhamsala:
Any specific reason reverting the blackscreen fix ?
[Optimus One, P500 Android Development] buzzdr0id:
Flashing n trying the latest ones now !

EDIT: Blackscreen bug is worse in v20a !!! I cant see anything upon pressing a button to unlock. When i slide then only i see the unlocked screen. Its like sliding blindly lol ! And i don't see the status info like date, gsm bar and battery icon, time after unlocking with black screen. Also, Brightness dims itself. I am goin back to v20 !

Now Goldenleaf is less smoother :( . Again going back to yesterdays version.
[Optimus One, P500 Android Development] Human_dude_007:
I dint have so many issue n feel yu r exaggerating things a bit too much:p.
[Optimus One, P500 Android Development] buzzdr0id:
Nope bro. I am not. I am using Oxygen 1.1 and things are worse in v20a. Now Goldenleaf is less smoother n stuttery . Again going back to yesterdays version.
[Optimus One, P500 Android Development] Raffy 97:
Does it work with BlackBird 1.1 beta 5???????????:D
[Optimus One, P500 Android Development] acax456:
Never x-(
[Optimus One, P500 Android Development] dancom96:
I can confirm that the blackscreen is worsened, with screen on Anim off, you still get it
[Optimus One, P500 Android Development] khoa02061986:
phone: LG P500

Rom: GingerCrust 1.5, android 2.3.7

Kernel: franco.Kernel-gbs.v20-gamer

OC: 480/768 SmartassV2

Benchmark: +Neocore: 66.3 FPS ; +Antutu benchmark: 1903
[Optimus One, P500 Android Development] hzoner:
@fserve why did you revert the black screen fix?

testing new kernel gamer v20a. my phone i f**ked-up. tried screen off animation at its worst than ever had to remove battery.

i noticed than adobe flash 10.2 make the animation slow

neocore score sound on w/touch 51fps

w/out flash installed the score is 59fps. why is that even w/touch same result.?

reboot my phone now im stock @ LG logo. :(

phone is a mess got to full restore...
[Optimus One, P500 Android Development] dnle71:
Yes, blackscreen is showing all the time..
[Optimus One, P500 Android Development] solidv:
Confirm. Gbs20a cfs
[Optimus One, P500 Android Development] vlt96:
Not in goldenleaf 111206:P

Sent from a phone smarter than me, the SmartPhone!
[Optimus One, P500 Android Development] robyguerrini:
The performances have worsened with gbs20a respect gbs20 ..... with all test programs ....
[Optimus One, P500 Android Development] 32bit:
Black screen bug first time was introduced in 111201.v-3 (omg, it's absolutely first time in Froyo!)

The last gbs without this bug is 111201.v-2 (4096 io buffer). Same time it's the most balanced version for me with good game and SD performance, and it's smooth in interface.

===

In my tests "deadline" io scheduler shows the best performance.

===
[Optimus One, P500 Android Development] iGiant:
I had a blackscreen once when an incoming call (GL111206)
[Optimus One, P500 Android Development] 32bit:
English, please.
[Optimus One, P500 Android Development] vlt96:
So that should be the 2010 version?

Sent from a phone smarter than me, the SmartPhone!
[Optimus One, P500 Android Development] viv_jen:
gps not working

it doesnt fix on location

and strange thing is after a minute or 2 i get kernel panic

(only when gps is on):confused:

i fixed it by installing faster fix and manually setting the location
[Optimus One, P500 Android Development] acax456:
Gbs v20a have a blackscreen. And it'll disappeared when i touch screen :|
[Optimus One, P500 Android Development] gkalen:
How did you change schedulers???

By changing from smartass to on demand or interactivex?????
[Optimus One, P500 Android Development] xuanduc987:
Use No-frills CPU control
[Optimus One, P500 Android Development] franciscofranco:
I don't see a single ****ing comment or feedback about the touchscreen responsiveness or cpu load, I only see ****ing blackscreen bug and **** IO schedulers. It took me a good bunch of time to look at the touchscreen code, understand it and fix it, then another bunch of time for fserve to tweak a few values and test his ass off. We can only improve it if we get feedback. No feedback = bye.
[Optimus One, P500 Android Development] vlt96:
Well, I can play pes now with the new touch... I said that;)

Sent from a phone smarter than me, the SmartPhone!
[Optimus One, P500 Android Development] Garuxa:
Maybe later when having more time i testing last kernel.

Sorry franco and fserve :o

Enviado desde mi MB525
[Optimus One, P500 Android Development] acax456:
Yes. I just have blackscreen bug. Touchscreen is awesome :)
[Optimus One, P500 Android Development] DaXmax:
I dunno... Maybe this kernel is only BFS version and dat is why is not working...

Sent from LGE XDA phone wit Matt's v6.5.7(1.1)
[Optimus One, P500 Android Development] terratrix:
Hmm, maybe.

Fserve, is this BFS? mind you create a CFS version?
[Optimus One, P500 Android Development] fserve:
What was the last working version for you?
[Optimus One, P500 Android Development] terratrix:
None...its my first try, btw, is the kernel BFS?
[Optimus One, P500 Android Development] fserve:
Yes, but custom froyo users told me that was working.

Will make a cfs version.
[Optimus One, P500 Android Development] terratrix:
Weird...will wait for your CFS version...thanks
[Optimus One, P500 Android Development] rajathvsm:
Could everyone stop requesting releases for every kernel stream, OS and tweak?

This is a dev thread, which had dev stuff until you all decided to spam here with deodexing, BFS and all. Let him/them concentrate on finding out innovative ways of tweaking (which frankly amazes me, as it is already tweaked like hell!) and then put out different versions of it. Creating different versions takes their invaluable time for doing routine stuff when they could be using it for something else.

All I'm saying is let them do their work now, and once they find that they are ready for releasing a stable, improved kernel worthy of releasing, they will release it. That has been the case so far! Please post only tweaks, feedback and logs here. I hope you understand!
[Optimus One, P500 Android Development] terratrix:
Its not working well with froyo...in the general section people are reporting getting stuck at android boot logo.
[Optimus One, P500 Android Development] fserve:
Thanks for tring make that thread clean :-) But in terratrix's case, i will just make a CFS version and check if solve his problem.
[Optimus One, P500 Android Development] terratrix:
Thank you:)
[Optimus One, P500 Android Development] logo_32:
Thanks for a wonderful kernel...

You've tweaked it pretty awesome...

Did see a notable change in the battery usage... no bugs so far..

Cheers..!!

Sent from my LG-P500 running cyanogenmmatt with franco.kernel-gbs.v14f @ 480/729 minmax
[Optimus One, P500 Android Development] fserve:
Terratrix,

test that one:

http://www.multiupload.com/NH8TF687G8
[Optimus One, P500 Android Development] terratrix:
Thanks, i will try that tomorrow(night time)
[Optimus One, P500 Android Development] fernando1sg:
I'm flashing it.. Non CFS version.
[Optimus One, P500 Android Development] DaXmax:
Cfs also work on ginger right? Can use it? :p

Sent from LGE XDA phone wit Matt's v6.5.7(1.1)
[Optimus One, P500 Android Development] fserve:
If it explode your phone, don't ask me to give another to you!!!

eheheh, test and give me feedback!
[Optimus One, P500 Android Development] DaXmax:
****... Really explode? Dunt make me scare leh... I just bricked my phone few days ago...

Sent from LGE XDA phone wit Matt's v6.5.7(1.1)
[Optimus One, P500 Android Development] 32bit:
No luck with BFS-versions for me. Neither your's, nor franco's BFS since v.13 and upper or something about that, I'm already not remember for now. Infinite loop on boot animation.

CFS-version required.

Thank You.

===

Btw, is the Power button (or any other button) works when the phone is switched off and charging? Can You see the progress of charging or to power-on the phone w/o unplugging the charger?

Hardware buttons does not works with franco's kernel v.17 and upper.

It seems not a big problem as one can say. But all kernel-builders says "wipe the battery stats after installing my kernel" that is automatically presumes that battery calibration cycle is needed. And, haha, how can the cycle could be completed in this case when it is impossible to monitor the progress of charging? :D

I'm even not saying about inconveniences in such cases when the phone was drained-out the battery in real life.
[Optimus One, P500 Android Development] fserve:
v14f CFS Version: http://www.multiupload.com/NH8TF687G8

I Dont know how to fix this issue =)
[Optimus One, P500 Android Development] gkarthik16:
Nothing like CFS is for Froyo/BFS is for GB..you can use CFS on GB too. Your phone won't explode:p
[Optimus One, P500 Android Development] vlt96:
What I've noticed in the new release is that axis inversion is still there, but if 2 fingers are far enought, I can press with the 2nd finger without moving the 1st's axes..

Sent from a phone smarter than me, the SmartPhone!
[Optimus One, P500 Android Development] orsonbear:
Kernel GL 111206, Mik's CM 6.5.8

Smartass 787/480, charging battery

SD 4GB CL6, Link2sd, SD free 695 MB

-------Database I/O--SD Write--SD Read

noop. . . . .175. . . . . . . . 3.6. . . . . 13.9

anticip. . . .180. . . . . . . . 3.7. . . . . 10.8

deadline. . 205. . . . . . . . 3.4. . . . . .9.7

cfq. . . . . . 220. . . . . . . . .7. . . . . . . 8.1

sio. . . . . . 200. . . . . . . . .5.2. . . . . .4.8

vr. . . . . . . 215. . . . . . . . .7.1. . . . .10.8

Later I will test the new GBS. At least I think so! Regards!
[Optimus One, P500 Android Development] 32bit:
Hey, Francisco, you know I love you, but slowdown a bit, you're too aggressive. Watch your words.

CPU and touch responsiveness was discussed since Nov.21 and now there is nothing new, as I see. What one can say? Kernel is stable in this aspect.

But fserve asked us to test all of schedulers. So, we did it.
[Optimus One, P500 Android Development] fserve:
Read the first page, axis inversion workaround is disabled...

@32bit, have you tested all v20a releases and 111206 goldenleaf? have blackscreen bug with all of them?

@people using cyanogen based roms, have you disabled "screen on" animation? (screen off is ok, you can use it)

haha, relax franco, i know it is good, most of people don know how to test it.

And the best reports about that will be of people using the "gamer" version. When trying to play something.

goldenleaf does not have this driver and the cfs version gbs doesn't have the first queue delay, just to be smoothier.

Sent from my ASUS Transformer TF101
[Optimus One, P500 Android Development] 32bit:
No. But I'm home now and I'll do it in the next two hours.

Thank You.
[Optimus One, P500 Android Development] vlt96:
I know it is still there, it actually a bit worse, but I don't see what would it help at:confused:
[Optimus One, P500 Android Development] fserve:
it is worse cos it is disabled.

Sent from my ASUS Transformer TF101
[Optimus One, P500 Android Development] vlt96:
No, they invert now a lot more, but I just don't care, except the axis inversion, any other multitouch bugs are not present, and this is what matters, I use nothing that is affected by that...
[Optimus One, P500 Android Development] fserve:
ok. i will tell it again.

they invert a lot more, like 100% of the times cos the workaround is disabled.

on some releases it used a more "relaxed" way to work, so it worked when you crossed fingers slow.

then i've made some changes and you could cross it very fast without bug the axis.

but what we have earned with it? nothing. actually we lost somethings.

axis was jumping around, and when the workaround was working to swap axis, it make touchscreen even slower.

so, the code now is like lg did, inversion will happen 100% of the times.

Sent from my ASUS Transformer TF101
[Optimus One, P500 Android Development] 32bit:
Goldenleaf-111206 has no black screen bug for me. It perfectly (!) smooth and it's performance is very typical. In exception of touchfix, of course - touchfix is perfect in my opinion.

Great kernel, for a brief look.

(ah, SD writing speed is not best, it was better often a month ago)
[Optimus One, P500 Android Development] fserve:
i didnt changed sd things in goldenleaf, could you tell me which I/O scheduler is the best for you?

Sent from my ASUS Transformer TF101
[Optimus One, P500 Android Development] nd4spdbh:
Tested 111206 and its not AS bad but it doesnt feel as smooth as 111108... went back to my 111108 and flick motions and scrolling seem quite a bit smoother.
[Optimus One, P500 Android Development] Skyline969:
The last Goldenleaf version I tried (early November) continued with randomly crashing my phone while the GBS kernel did not. Here's hoping Goldenleaf doesn't crash me again! If it does though, GBS (CFS, last BFS I tried was quite jerky in menus) works just fine.

Thanks fserve, you've done well.

EDIT: Not 2 minutes into Goldenleaf 111206 I noticed it was very similar to GBS BFS in the sense that it wasn't very smooth. I'll continue to use GBS CFS for the time being. =P

EDIT(2): There seems to be another blackscreen bug on franco.kernel GBSv20a. It takes a good few seconds to display anything once the screen turns on. I'll be reverting to v20.
[Optimus One, P500 Android Development] fserve:
BFS Versions are with gaming focus, side effect is stutter menus :-)

Yes, for now i think that we can't have both.

Smooth menus / cpu lag fix (touch fix, or whatever the name that you know for it)

blackscreen bug does not show nothing, at all...

Sent from my ASUS Transformer TF101
[Optimus One, P500 Android Development] 32bit:
Strange but earlier Goldenleafs always performs better with SD. Now its performance is more typical for franco's kernel.

The best results for me are with "deadline". "Anticipatory" and "bfs" is not bad too.
[Optimus One, P500 Android Development] Skyline969:
I'm aware of that. I'm assuming that this is a new bug though, because it takes so long to display anything at all. It does display, but only after a few seconds.
[Optimus One, P500 Android Development] 32bit:
Just tested gbs-20a cfs version.

It's very smooth but the performance is bad for me, even lower than with Goldenleaf that was never before. Neocore w/o touch 51fps (55 with goldenleaf). Neocore with touch 47fps (50 with goldenleaf).

SD performance is equal now for both versions and more looks like GBS performance, not Goldenleaf one, as I said before.

Ah, I forgot - there is no blackscreen bug in gbs-20a for my Froyo (as it should to be 'cause it's only CM7 bug, hehe).
[Optimus One, P500 Android Development] fserve:
They are different touchscreen drivers, at least ONLY ONE PERSON could give us this feedback, very thank you :-)

Driver used in "-gamer" is even different, will stutter more but it's very cpu lightweight.

About fps drop, i told franco that we got some fps drop with this new driver :-)

You people can check my github.

V20 removed 3 lines from 3 files to add blackscreen fix

V20a reverted it, adding back the 3 lines from 3 files to remove the blackscreen fix

I'm using CM7 and i didnt get any blackscreen bug, with any of the three releases.

Well, i dont get this bug, try cleaning your rom with cache cleaner ng, or something like that. Try gbsv20a same fix is there
[Optimus One, P500 Android Development] 32bit:
I can not point no one, neither v20, nor v20a, nor Goldenleaf. They are almost same now.

Sorry.

Goldenleaf 111107 (may be 08, just not tested) was the last good SD performer. And it was good SD writing speed with some (october?) gbs - I don't remember.

By the way the reading speed is good as it used to be.
[Optimus One, P500 Android Development] fserve:
Ok, very thank you.

-Maybe- and i really dont know how, that TS driver of Goldenleaf made this, i dont know how, we can test with stock lg driver.

EDIT: Goldenleaf 111226+stock lg ts driver: http://www.multiupload.com/8BAO3K1OM9 - DOT NOT USE IF YOU DONT KNOW WHAT IT WILL MAKE TO YOUR PHONE.

@32bit, please test that :-)