yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500 Android Development] Turducken:
I've read dozens of posts about this blackscreen bug. I'm using miks 6.5.8 and have NEVER experienced it with any versions of the gbs kernel (haven't tested gleaf).

Is there something else you guys have in common, maybe a service, script or tweak? It seems to affect some users and not others, strange.
[Optimus One, P500 Android Development] dancom96:
No issues so far with latest testing release, this is asking a lot, but is it possible so that when your fingers get close to crossing axis, they don't squeeze together? They show up closer than they are and sometimes this causes buttons to not work in games

*edit*

Axis inversion doesn't work as well asin 19.2
[Optimus One, P500 Android Development] DaXmax:
I wipe dalvik and cache, downclock to 691, now is working fine.. Weird, im able to use up to 748... :confused::confused:
[Optimus One, P500 Android Development] Xasder:
No tweaks here. Data, wifi, sync was disabled and left the phone to rest overnight. In the morning tried to switch the phone on w/ home key and got blackscreen bug.

Now I reverted to franco's 19.4, just recompiled it with CONFIG_ANDROID_LOGGER, which was the reason I switched to fserve's kernel in the first place.
[Optimus One, P500 Android Development] fserve:
That ANDROID_LOGGER was fixed on the first page release and the newest testing fixed blackscreen bug........
[Optimus One, P500 Android Development] Turducken:
Well guys, I have to admit defeat. I'm pretty sure that Paulo didn't include his Touch fix (CPU spike when touching the screen) in his released sources.

I compiled his sources, no changes made, and the result was the NoTouch kernel. Zacks has been working with Paulos sources for over a month and all of his releases are also NoTouch. If he hasn't found it yet, then it probably doesn't exist.

I looked at his orphans but nothing stood at.

Oh well, IMO the touch fix makes app drawer and browser scrolling stutter so I wasn't a big fan of it anyway.

Sorry for posting this in your thread fserve but I thought you might be interested.
[Optimus One, P500 Android Development] khoa02061986:
I tested GBS 19 (BFS), 1.19 (BFS), 2.19 (BFS) and 19.3 CFS (new to your link).

Comments: franco.Kernel.v19.4 + GBS.v19.1 vsyn off (BFS) is the best version; I also test with pes 2012, 19.1 vsyn off (BFS) is the most smooth. So why not develop the "GBS vsyn off, BFS" for the game.

Also you can benchmark with: atutu benchmark, quadrant advance, neocore -> 19.1 Vsyn off (BFS) is the best.
[Optimus One, P500 Android Development] fserve:
My 19.3 version (newest testing releasing) is using Paolo touchscreen driver.

BUT PEOPLE KEEP NOT GIVING ME FEEDBACK (or money) :/

Benchmark aren't the real deal. Maybe 19.1 was better only because of vsync off. What do you think of 19.3? And if i disable it's vsync would be better than 19.1?
[Optimus One, P500 Android Development] fserve:
deleted =p
[Optimus One, P500 Android Development] khoa02061986:
1. "Version 3.19" is probably the CFS, but the test with pes 2012, it is not smooth compared to "off vsyn v19.1 (BFS)." Maybe that's the difference between CFS and BFS

2. "vsyn off" and "vsyn on": as I know, "vsyn off" smoother than "vsyn on".

-> You can create "off vsyn v19.3 (BFS)" and compare with your current version 3.19

But the combination with Paolo is really great.
[Optimus One, P500 Android Development] Turducken:
If you haven't already please test Paulos Touch kernel. With all other kernels spike is between 30-50% using System Tuner. With Paulos Touch it's about 5-8%.

When I used Paulos touchscreen driver with francos sources, it didn't fix the Touch spike.
[Optimus One, P500 Android Development] blueren:
I'm running 111108 on mik's 6.5.8. Everything is smooth most of the time. However, the sound dies once in awhile and needs a reboot to get it running again. What I mean to say is whenever there is a call or a txt message, the sound doesn't go off. Today infact, my alarm didn't ring. :( When I go to settings > sound > volume, I get a force close.

Is this related to the rom or the kernel?
[Optimus One, P500 Android Development] kyerie030:
Most likely rom related, can you try to reflash? if possible check md5 checksum of the zip you flashed for 6.5.8. Better also if you do a fresh install.
[Optimus One, P500 Android Development] fserve:
I'm testing this right now... updated my arm-toolchain here :-)

Cleaning some code in Paolo driver (a lot of code).

Vsync off.
[Optimus One, P500 Android Development] khoa02061986:
oh, here's how "test lag when touching" was effective

---------- Post added at 05:02 AM ---------- Previous post was at 05:00 AM ----------

I'm anxiously awaiting.:rolleyes::rolleyes:
[Optimus One, P500 Android Development] fserve:
new testing release -> http://www.multiupload.com/390WQZ3GMO

vsync off

backported paolo driver with my very first optimizations based on what i've learned with franco, mik, sippolo, Der_Caveman and waleedq.

55fps, touching the screen.
[Optimus One, P500 Android Development] khoa02061986:
I will test it right now, will report results for you soon.

Thank you, your wonderful and enthusiastic people
[Optimus One, P500 Android Development] GonDr:
very thanks, can u do one with vsync on plz ?

if not, never mind
[Optimus One, P500 Android Development] fserve:
vsync on is a few pages ago...

:-)
[Optimus One, P500 Android Development] GonDr:
i know, but is it with your very first optimizations based on what you've learned with franco, mik, sippolo, Der_Caveman and waleedq ?
[Optimus One, P500 Android Development] fserve:
nop :(

but you could try this vsync off only to give me some feedback if i'm going on the right way :-)
[Optimus One, P500 Android Development] GonDr:
i flashed it, feel its faster and smoother than previous kernel (vsyn on ), in system tuner when touch screen that cpu 99%, will report more soon, thanks
[Optimus One, P500 Android Development] Turducken:
Are you working on the axis inversion fix or CPU spike? I only tested spike and I didn't notice a diff.

One thing I noticed when testing Paulos Touch kernel was a very small CPU spike when I touched the screen but a spike of about ~20% when I removed my finger. This is the exact opposite to how all other kernels react. I hope this helps.
[Optimus One, P500 Android Development] khoa02061986:
here are the results:

GBS 19.1 (vsyn off BFS) / GBS gbs-111121

neocore (no sound)	:	66.1fps	/	66.4

quadrant (1.1.1.2)	:	1469 (cpu:4141)	/	1471(cpu:4156)

antutu	:	1901	/	1877

smoother than pes 2012, I can at least 5-0 goal "in a game," kekeke
[Optimus One, P500 Android Development] linkinparkfan007:
Works great thanks :)
[Optimus One, P500 Android Development] ebe_robert:
Thanks for all your hard work fserve..:)

Eagerly awaiting a Vsync-on cfs version with your Wow optimizations :D
[Optimus One, P500 Android Development] fserve:
Try set your governor for performance and test again with the new vsync off release.

I'm trying to do both things.

WoW optimizations v2 -> 58.3fps touching the screen...
[Optimus One, P500 Android Development] 32bit:
111121 releases both are better than previous GBS in my opinion.

Nothing more to talk because the time is too short.
[Optimus One, P500 Android Development] Turducken:
I forgot to change the gov :o

You are my hero for today!! Yes you are on the right track with the CPU spike fix! CPU impact is cut in half!! Now it's ~20-25%. Please turn vsync off for further tests. I noticed with Paulos Touch kernel that app drawer scrolling is affected by this touch fix. Also app drawer scrolling is affected by vsync off. I'd like to see where the "breaking point" is with just the CPU fix. vsync on would help to remove a variable.

Axis inversion is still weird. The faster/closer I go the more it f*cks up but it's better than Paulos that's for sure.

EDIT: sorry I contradicted myself above, Turn vsync ON. I think Paulo went too far with his touch fix. Scrolling stutter was very noticeable to me even in v6 (which had vsync on)... I hope this makes sense?
[Optimus One, P500 Android Development] fserve:
I'm trying to optimize axis workaround now.

So we can play PES with LESS problems, i don't feel i can solve this, only minimize even more.

Testing with PES2012.

If my idea is right, this should be epic!

but i will need a toggle, like franco is trying with vsync...
[Optimus One, P500 Android Development] sweetnsour:
just out of curiosity, why does this work for performance and not the other governors?
[Optimus One, P500 Android Development] Turducken:
Performance keeps CPU running at max freq. It's for testing only. It helps prove/disprove fix, that's all.
[Optimus One, P500 Android Development] khoa02061986:
gonevor = smartassV2 also very good.
[Optimus One, P500 Android Development] fserve:
My newest driver did - Quadrant/Neocore @ 600MHz - InteractiveX:

Your device score 1107 - Touching the screen

Your device score 1092 - NOT Touching the screen

Neocore 51 FPS Touching the screen

Neocore 46 FPS NOT Touching the screen

EXPLAIN THIS!
[Optimus One, P500 Android Development] Turducken:
1 - Quadrant sucks, I've seen a diff of over 100 without changing anything.

2 - You've gone too far?
[Optimus One, P500 Android Development] fserve:
I'm playing pes2012 @600MHz :)

I'm just thinking how to solve that problem related to virtual buttons not working because of axis workaround...
[Optimus One, P500 Android Development] Turducken:
I have little doubt that you'll work it out. I'm really impressed with what you've accomplished so far. When this monster is released as final everyone will be signing your praise! This is a HUGE fix! :D
[Optimus One, P500 Android Development] fserve:
for now i have a problem.

for gaming we really dont need axis workaround.

for browsing, maybe we need, maybe not.

i'm thinking in remove this ****.
[Optimus One, P500 Android Development] khoa02061986:
It's unbelievable, hope that everyone is going to be a kernel perfect

---------- Post added at 08:33 AM ---------- Previous post was at 08:31 AM ----------

So, do two versions like BFS and CFS
[Optimus One, P500 Android Development] Turducken:
Some games like the hockey game that sweetnsour mentioned are affected but honestly I've never been affected by it.

The CPU spike fix is the big one imo. It helps with gaming and should increase battery life significantly.
[Optimus One, P500 Android Development] fserve:
New testing

with axis workaround: http://www.multiupload.com/CLXC4IDOE9

without axis workaround: http://www.multiupload.com/0YHX636454
[Optimus One, P500 Android Development] Turducken:
Are these vsync on?

EDIT: I'll test tomorrow, it's late here. Thanks again fserve for your great work!!
[Optimus One, P500 Android Development] fserve:
Very late here too... :D

VSYNC ON AND VSYNC OFF kernels on the first page.

Happy testing.

I just need feedback and donations.
[Optimus One, P500 Android Development] khoa02061986:
yeah, this version is great gaming workaround axis,

The remaining version I test it feels like it smooth workaround axis version, but can not play a game with two controls with parallel coordinates

So without axis version has the advantage of what workaround?

Thank.
[Optimus One, P500 Android Development] buzzdr0id:
Thanks but which one is better ? Vsync OFF or ON ? With or Without axis ?
[Optimus One, P500 Android Development] khoa02061986:
I do not know what else to say, your kernel more perfect, it's hard to make error feedback
[Optimus One, P500 Android Development] fserve:
The advantage is in games like pes2012 where virtual buttons are in the same line. Axis inversion workaround will make the button do not work, some times...

Without it, the game runs very good :-)

Try both, vsync off is faster on games.
[Optimus One, P500 Android Development] buzzdr0id:
With or Without axis ?

vsync off is faster overall or just in games ?
[Optimus One, P500 Android Development] fserve:
Just pick one!!!

Try vsync-on-with-axis and be happy!
[Optimus One, P500 Android Development] buzzdr0id:
Thank you LORD OF KERNEL !!
[Optimus One, P500 Android Development] khoa02061986:
Wow, LORD OF KERNEL , is really too gimmicky, but it is true, he has done can not be
[Optimus One, P500 Android Development] MaKTaiL:
Ok, here are my tests. I'm using vsync-on with axis workaround. 480/600 smartass.

Neocore touching the screen: 48.8fps

Neocore without touching the screen: 54.6fps.

Hope I helped in anyway ;)
[Optimus One, P500 Android Development] DaXmax:
Dont care about neocore but care about how smooth and fast this kernel is!
[Optimus One, P500 Android Development] eeee616:
Thanks Fserve kernel test of you the best play pes 12 multitouch very very good :)
[Optimus One, P500 Android Development] vlt96:
With multitouch workaround you have no multitouch bugs in PES???

Sent from my LG-P500
[Optimus One, P500 Android Development] Lycan:
Correct, the 1st thread. You posted 4 cfs version by mistake ! :)
[Optimus One, P500 Android Development] eeee616:
No clip test multitouch + pes 12 multitouch :)

[YOUTUBE]7nR-C9XdnLM[/YOUTUBE]
[Optimus One, P500 Android Development] vlt96:
So this is the new testing with multitouch workaround?

Should I use vsync on or off, what are the one's used in this current non-testing version?

Sent from my LG-P500
[Optimus One, P500 Android Development] eeee616:
I testing gbs.111122-cfs-vsync-on - with axis workaround :)
[Optimus One, P500 Android Development] vlt96:
Of course, but vsync is on or off on 19.2?

Sent from my LG-P500
[Optimus One, P500 Android Development] MaKTaiL:
I'm showing that the touchfix is not perfect yet.

The kernel was already smooth and fast, that's why I'm not caring about it.
[Optimus One, P500 Android Development] Jaani:
With 111122gbs>vsync on>without workaround multitouch

Quadrant

600mhz smartass=1339

652mhz " =1450

I know quadrant sux but still..

WoW fserve great work man..testing report later if got anything...btw i dont got any blackscreen **** in any of yr gbs versions till date..:)

Edit:Just found that scrolling speed in settings & drawer is reduced i guess bcoz of the new driver..
[Optimus One, P500 Android Development] lakerslacoste:
111122 very good , thax u :)
[Optimus One, P500 Android Development] ScripterJR:
I dont really post often but I just wanted to say that this kernel is, in my opinion, probably the best one. Once I get more information, i'd like to contribute and help you out. As of right now, I see that the screen is more responsive. I'm assuming this is caused by the cpu spike fix. I will report back but I'm assuming that battery life will increase as the load on the cpu decreases.

I'm running on 600 mhz using interactiveX. Just tell me what more information you want and I'll be glad to give to you.
[Optimus One, P500 Android Development] vlt96:
The v19.2 has vsync on or off?;)

Sent from my LG-P500
[Optimus One, P500 Android Development] Jaani:
I think ON..;)
[Optimus One, P500 Android Development] viv_jen:
The vsync n axis workaround is only for the cfs version?

I kinda prefer bfs for gaming

Also in cfs vsync off with axis workaround

Should be good for gaming?
[Optimus One, P500 Android Development] ledinhsonhp:
Fserve, why don't you change your "Kernel project" to kernel .35. I think it faster and better than kernel .32. And Mik_os and another developers will port and build their ROM based on kernel .35 in the future.

BTW, thank you very much for all what you do. It's truly great job.
[Optimus One, P500 Android Development] buzzdr0id:
I think vsync ON should be better coz Vsync OFF = laggy/stuttery UI.
[Optimus One, P500 Android Development] Javi22:
Another update wow :D

With 6.5.8 + gbs 19.0 cfs I found the definitely best combination, because I didn't get lags on my games, noticed smooth and fast launcher and the most important, battery is awesome, it can last me for days.

Now I will try 19.2 I hope don't worsen things xD

Ps. People I would not lose time in benchmark, neocore and that things, is not better test yourself how smooth and fast you feel??
[Optimus One, P500 Android Development] fserve:
Javi, go and test mine new testing kernel, this **** is very good! :D

Yes, touchfix is NOT perfect!!! COS "AXIS WORKAROUND" IS A BAD PROGRAMMING THING.

If i make axis workaround better, touchfix will suffer even more.

If i DISABLE axis workaround, touchfix will love me :D That's why i did the version WITHOUT axis inversion workaround.

AND, i've tested in PES2012. The "without axis workaround version" is the best to play. The virtual buttons always work!

Thank you for the good support :-)

About .35 kernel, we have franco.Kernel that are very good, i will send my driver to him make some tests, it's very better than anything available to P500, ever.

Sent from my ASUS Transformer TF101
[Optimus One, P500 Android Development] teddybig:
What exactly is the axis inversion bug? Don't flame me yet, gonna search..... just asking...
[Optimus One, P500 Android Development] fserve:
If you know the bug, you will see the workaround working very good on the "eee616" video

http://www.youtube.com/watch?v=7nR-C9XdnLM&feature=player_embedded

Our phone have a bug when we cross fingers...
[Optimus One, P500 Android Development] vlt96:
The testing versions have anything else, except vsync and axis blablah?

I heard vsync on gets snoother, but does it take more battery from the screen? This phone already has a screen that takes 90% of the battery if not gaming...

Sent from my LG-P500
[Optimus One, P500 Android Development] fserve:
vsync on, on my humble opnion, drain less battery, but i dont have prof for that. It's just my theory about it.

Yes, the news about the testing version are in the first page :-) It's not only this, have some little fixes to work well for everyone.

Just pick the vsync-on with axis workaround fix for everyday use.
[Optimus One, P500 Android Development] vlt96:
How can people have O1 and nor see the miracle in their hands... with cm7 and this kernel you have best phone, really too cheap!

Sent from my LG-P500
[Optimus One, P500 Android Development] yuripg1:
1 vote for "go without axis inversion workaround".

I, personally, don't see any situation where I cross my fingers on the screen (again, in MY usage).

If by removing it your improvements to the touch work best, I have no complains.

It's just a suggestion based on my usage. No pression to choose one or another direction in the development.
[Optimus One, P500 Android Development] vlt96:
It is the same glitch on pes, tried that multitouch test and same ****, so I vote for the best;)
[Optimus One, P500 Android Development] kawaiiDango:
Goldenleaf freezes quite often... can u upgrade it to. 48 kernel? Ppl using the .48 gbs are already seeing performance. Improvements...
[Optimus One, P500 Android Development] kyerie030:
fserve, which is bfs and which is the actual cfs?
[Optimus One, P500 Android Development] linkinparkfan007:
Loving it thanks fserve!
[Milestone XT720 General] mrmako777:
i have tried to install this recovery and i cannot figure out what i am doing wrong. i have followed the instructions to a tee, but cannot get this thing to show me the eclair modding menu. the only new option i see is "console". i have followed both of these posts

http://xdaforums.com/showpost.php?p=10953495&postcount=4

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

as well as the instructions posted on modmymobile without success. please help, im feeling like an idiot over here! :(
[Milestone XT720 General] mchlbenner:
Download it remove regular recommond hide in a folder.

Unzip ardoidiana recovery on main sdcard that's it.

I use it for system tweats on cm 6.
[Milestone XT720 General] Woody:
Make sure you have both open recovery AND Androidiani.zips on the root of your sdcard. Make two folders, one nandroid/openrecovery and openrecovery. Unzip AOR.zip and put contents in /openrecovery. When you back up they go to nandroid/openrecovery and the utilities go to /openrecovery. Reboot and hold volume up at the M
[Milestone XT720 General] mrmako777:
so i should have a zip named openrecovery and a zip named update on the root of the sd card or replace the original openrecovery.zip with a renamed update.zip?
[Milestone XT720 General] mrmako777:
got it working! i had to delete the original openrecovery folder and replace it with the new one! yay! :)
[Milestone XT720 General] Mioze7Ae:
Just FYI I'm pretty sure now that the Androidiani update.zip isn't used at all on XT720 and can be deleted. update.zip comes from the A853 OpenRecovery and the Milestone XT720 version uses OpenRecovery.zip instead.
[HTC EVO 3D] thoughtlesskyle:
First off this project would not be possible without the following users work

NotVeryCreatives keyboard with no smilely key

and ReProd for some of the PNG images

this is the tweaked 3vo keyboard I made for my evo 3d since we share a resolution I figured I would share this here as well

what it is

gingerbread keyboard

-no smiley key

-popups turned off by default (they can be turned on in settings)

-renamed so it can be installed along side and keyboard

-sense green prediction text

-adjusted Dimens files so it scales to the qHD screen better

-named 3vo keyboard

Download here

Classic

Download classic

Bluesy

Download BluesyKeys
[HTC EVO 3D] pstevep:
Nice to see you sir.. Welcome to 3D land.. Great work btw..

_______________________

Now available in 3D
[HTC EVO 3D] thoughtlesskyle:
I do what I can
[HTC EVO 3D] alexnaoumi:
i got the gingerbread donate version, but ill give this a go, ill post what i think of it in a minute.

EDIT: nice keyboard, im definitely using this :D
[HTC EVO 3D] thoughtlesskyle:
This has been my default on my phone since I built it last night I got so used to it on my evo I had to
[HTC EVO 3D] cordell12:
Hey Bro!

We seem to be getting the same phones, lol. Good to see you over here :cool:

Waiting like mad for CM to drop, good FAST rom and easy themes (well easier than sense) ;)
[HTC EVO 3D] METHOD1911:
Man very good to you thoughtless

Rooted 3D shooter in full affect
[HTC EVO 3D] iamdata:
It works in portrait mode. But landscape doesn't work too well. Its very squashed and small. But its such a fast keyboard in portrait. :-) good work. Will be even better with landscape.
[HTC EVO 3D] Rippley05:
Kyle I hope you plan on bringing some classy themes to the 3D! We are seriously lacking in customization ...makes me miss my evo!
[HTC EVO 3D] ch1naski:
Kyle is here. Here we go!

Nandroids are for sissies.

Bang.
[HTC EVO 3D] thoughtlesskyle:
I can fix that
[HTC EVO 3D] thoughtlesskyle:
So hopefully when I get time tomorrow

I will fix the landscape layout , anybody else have any feedback?
[HTC EVO 3D] xyojimbox:
thank you for this its so much easier to type on then the gingerbread keyboards in market
[HTC EVO 3D] k2buckley:
Yea, it's great in portrain mode...100% better than any other GB keyboard I've used. But as stated by the other guy, it's totally squashed in landscape. Great work, thanks. Look forward to it being fixed in landscape, then it'll be perfect.
[HTC EVO 3D] user7618:
This is a great board! As I've already gotten tk's permission, is anyone wanting me to bring my minimal boards to the 3d?

-----

Android: It will make you a sexual tyrannosaurus, just like me.
[HTC EVO 3D] fowenati:
Great work! Although I like the orange from better than green :P maybe upload an orange version?
[HTC EVO 3D] thoughtlesskyle:
okay fixed land scape in the first post

and now put a "classic" version in the first post

same dimensions just stock png's and colors
[HTC EVO 3D] fowenati:
great stuff! would I have permission to integrate this into SupraMOD ?
[HTC EVO 3D] thoughtlesskyle:
Please do
[HTC EVO 3D] fowenati:
thanks! It'll be implemented in the next version !
[HTC EVO 3D] thoughtlesskyle:
i think i might have something else cool for the next supraMod as well let me test it then i will PM you is that cool?

update: PM sent
[HTC EVO 3D] dadoc04:
I like where this is going... :D
[HTC EVO 3D] fowenati:
Its in.supra mod (renamed sensetoaosp) check it out!
[HTC EVO 3D] thoughtlesskyle:
added a blue variation today as well