yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500 Original Android Development] gekko69:
I had a shutdown 2 days ago at 480/600 conservative. So I would not be so sure it's the OC.

It was the only shutdown since the latest kernel was released.

But I had seldom shutdowns with previous kernels too on 6.6.1

I don't get shutdowns on 6.5.7 with fserves kernels (same applications installed).
[Optimus One, P500 Original Android Development] Turducken:
[FIX][SOURCE] Axis Inversion workaround

Here's what I think I know:

The axis inversion bug is hardware related and can never be completely fixed. Der_Caveman, waleedq and Sippolo came up with this workaround. fserve has added this fix to both gbs and goldenleaf.

Paulos .35 kernel experiences the bug more than either of fserves .32 kernels but far less than your .35 kernel.

I compiled paulos driver with your sources and it worked, bug is greatly reduced. Please take a look and see what you can see, I don't speak C (pun intended) ;)

Copy source to drivers/input/touchscreen

EDIT: Attached source was taken directly from Paulos v6 sources, no changes made.
[Optimus One, P500 Original Android Development] terratrix:
How about the CPU spike bug when touching (lag when playing games), its fixed in paolo's kernel
[Optimus One, P500 Original Android Development] Turducken:
Apparently it is fixed, I didn't test that though.

To be honest I didn't do anything. I simply saw where fserve placed the Sippolo fix in his .32 kernel github, copied paulos same source to francos .35 kernel and compiled. Seriously, copy paste compile. That's all I did.

If fserve fixes the bug in the .32 kernel I'll try the same thing again.
[Optimus One, P500 Original Android Development] sweetnsour:
simple, but definitely ingenious!
[Optimus One, P500 Original Android Development] Lycan:
Please share this with fserve. He seems oblivious to this finding.

And i think franco's dead.
[Optimus One, P500 Original Android Development] sweetnsour:
fserve has a testing release for the cpu spike bug

franco dead? developers have lives outside of xda and android. you must respect that :)
[Optimus One, P500 Original Android Development] Lycan:
I didn't mean no disrespect !

Its just that franco doesn't seem too active these days.

maybe hes working on something else.
[Optimus One, P500 Original Android Development] terratrix:
As you can see franco is very active in xda, he is currently actively updating his kernel for Nexus S. he doesn't have his P500 anymore.
[Optimus One, P500 Original Android Development] metalboy94:
Well as I said I get very rare kernel panics on conservative 729, even if I stress it with games and stuff. Maybe I'll try a stress test next time the phone's refueling. :)
[Optimus One, P500 Original Android Development] DaXmax:
His is the top at here but second in Nexus S (Why?! Cuz Trinity Kernel beats it...)

Ok, another words... Is anyone having glitches when using this kernel? (NOT GAME)
[Optimus One, P500 Original Android Development] franciscofranco:
What the **** are you talking about? I only have my Nexus S for a month, kernel was released exactly one month ago, morfic has his kernel released since April... Why do you people talk about **** you don't know? That pisses me off so much

Glitches? Why should anyone have glitches? This **** is stable, the end.
[Optimus One, P500 Original Android Development] franciscofranco:
That bug is 90% fixed in the .32 kernel for almost a year already.

I can add that changed driver in a future release.
[Optimus One, P500 Original Android Development] Lycan:
Could you add the new driver changes [i.e. touchscreen drain fix] to your .35 kernel ?
[Optimus One, P500 Original Android Development] franciscofranco:
What did I just say?
[Optimus One, P500 Original Android Development] franciscofranco:
Ok I'm planning to release an update later today with that touchscreen driver from paolo (thank you), another vsync toggle on/off interface and a little try to fix the ****ing blackscreen bug. No promises though, we'll see.
[Optimus One, P500 Original Android Development] fserve:
This will be a bomb kernel! :D
[Optimus One, P500 Original Android Development] franciscofranco:
Don't know yet, it's a little hard to test because I don't have my p500 with me so it's a little blind guess.

What I want to try is to setup a wakeup event within the screen on event. In my nexus I can assign RTC_ALARM, RTC_TICK, KEY events that are triggered in certain scenarios depending on the task. I don't know if this is possible with the P500, but it's worth a try.

What would be of value was to have like a manual for this phone chipset.
[Optimus One, P500 Original Android Development] Turducken:
I'm not a dev so what I'm about to say may be nonsense, but Paulos driver had msleep(100) and yours had msleep(10). Maybe the combo of the axis additions plus your sleep settings would be best?
[Optimus One, P500 Original Android Development] franciscofranco:
Yes, I copied the optimized driver by der_caveman/mik_os mechanics and that seemed to produce better results with the stock code.
[Optimus One, P500 Original Android Development] fserve:
I do use msleep 10, but people report that Paolo lagfix is better. (msleep 100) on .32 kernel

Sent from my ASUS Transformer TF101
[Optimus One, P500 Original Android Development] Turducken:
Relying completely on my spider senses, I'm not convinced that this driver is where Paulos lag fix is. It's strange but with Paulos Touch kernel when I touch the screen the CPU barely spikes but when I remove my finger there's a short spike. This is completely different to how all other O1 kernels react.

I was looking at the cpuidle drivers before Vbox took a crap on me.
[Optimus One, P500 Original Android Development] franciscofranco:
We dont use cpuidle for p500, as far as I know this device doesnt support it.
[Optimus One, P500 Original Android Development] oldmanmoz:
I've got a query regarding mcs_6000_ts, comparing the vs740 source, and ours...

The vs740 mcs6000_ts_suspend() checks the return after cancel_delayed_work_sync(&ts->work); and increments irq_sync whereas ours does not, implying there is a scenario where ours becomes out of sync? I know nothing about low level hw drivers but i figured it worth asking.

[p500]

if(ts->irq_sync == 0){

disable_irq(client->irq);

ts->irq_sync--;

}

cancel_delayed_work_sync(&ts->work);

...

[vs740]

if(ts->irq_sync == 0){

disable_irq(client->irq);

ts->irq_sync--;

}

ret = cancel_delayed_work_sync(&ts->work);

if (ret) {

enable_irq(client->irq);

ts->irq_sync++;

}

...
[Optimus One, P500 Original Android Development] Joel Chan:
One word of advice, Dax. Please not talk about other phones when you're on the optimus one forums. Thanks :)
[Optimus One, P500 Original Android Development] RevengeFNF:
Its because of persons like you, saying nonsense things, that devs tend to leave xda.
[Optimus One, P500 Original Android Development] Lycan:
Is the ETA today?

Jusayin
[Optimus One, P500 Original Android Development] fserve:
franco always delay kernel by one month when someone asks ETA :/
[Optimus One, P500 Original Android Development] Garuxa:
Don't Ask ETA's!
[Optimus One, P500 Original Android Development] Lycan:
Oops..sorry!

But when he does, its a bomb ! :D
[Optimus One, P500 Original Android Development] DaXmax:
Yayayayayaya, my fault ok... Fine, im just an idiot, ok **** that... He wont leave xda as his having 2 devices at the same time, he ignored me alright... So can u just stop the offtopic... And his kernel is a bomb here and i was surprised he did the kernel for ics on his nexus s... :(
[Optimus One, P500 Original Android Development] Lycan:
^^Doesn't make sense.

p.s. - You don't even have a p500.
[Optimus One, P500 Original Android Development] franciscofranco:
Vsync toggle isn't possible. Vsync can only change with a recompile sorry. Let's see about the rest...
[Optimus One, P500 Original Android Development] Lycan:
Waiting intently.
[Optimus One, P500 Original Android Development] franciscofranco:
Gogo blackscreen bug fix attempt!!!!!
[Optimus One, P500 Original Android Development] Lycan:
Aaaah !! finally ! :D

Flashing now, will report in a few minutes.

P.S. @franco - U put in the wrong date. Its 22112011 :) jussayin
[Optimus One, P500 Original Android Development] Garuxa:
!!!!!!! Finally! Testing later :D

Enviado desde mi LG-P500
[Optimus One, P500 Original Android Development] Lycan:
EDIT: SORRY MADE A TYPO FRANCO !

Ok. Tested using andys phoenix.

OC 748/480 SMARTASS

old .35 kernel

neocore 63 soundoff

48 soundoff with touch

testing release

neocore 62 soundoff

57 soundoff with touch

Axis inversion workaround is working.

Blackscreen bug still appears.

---------- Post added at 01:38 AM ---------- Previous post was at 01:19 AM ----------

Sorry for double post, but i wanted to add more test results !!

Gaming is **** awesome !

touchscreen lag is never experienced with any game [currently tested gangstar, asphalt 5(using boost), nfs shift, pes11, assassins creed] but pes12 is still laggy. I think that game itself is bugged.

wifi's working,tethering working,gps dunno.

imho, you should lable it as a stable release.
[Optimus One, P500 Original Android Development] vlt96:
I don't know what are you saying about pes12, it is fine for all of gleaf kernel users;)

Sent from my LG-P500
[Optimus One, P500 Original Android Development] Snickers:
Blackscreen bug still appears on Oxygen 2.3.2 :mad:
[Optimus One, P500 Original Android Development] voyager20021:
Confirm on CM7 6.6.1.
[Optimus One, P500 Original Android Development] franciscofranco:
****. I'm running out of ideas. Add debug.sf.hw=1 to build.prop and reboot please.
[Optimus One, P500 Original Android Development] solidv:
It fixes the blackscreen bug.

Edit: you have to be very fast when pressing the power button
[Optimus One, P500 Original Android Development] Bec de Xorbin:
OK! I'll try it very soon.
[Optimus One, P500 Original Android Development] fserve:
Just to let you know.

This .35 kernel, run very good (only with the blackscreen bug) on my MIKS 6.5.8 rom :-)

Thank you, franco. :D
[Optimus One, P500 Original Android Development] Bec de Xorbin:
It's still there. But hey, it's not a big deal and there's easy workaround for that; just touch the screen.

Touchscreen feels weird, don't know if it's a bad or good thing yet ;)

Edit: it's a great thing.
[Optimus One, P500 Original Android Development] Lark987:
.35 kernel on 6.5.8? Are you its working ?... Can you reread your post..
[Optimus One, P500 Original Android Development] fserve:
Yes, it's working :D

not a big deal btw, but it's good to know that the same bug happens on .32 roms.

--maybe, the same fix is needed..........--
[Optimus One, P500 Original Android Development] Turducken:
Very nice, thank you franco, fserve and Paulo! This axis inversion workaround works much better than the Paulo version I posted. :D

Too bad about the blackscreen bug :( Thanks for trying!!
[Optimus One, P500 Original Android Development] terratrix:
How about CPU spike on touch?
[Optimus One, P500 Original Android Development] Turducken:
Go to fserves thread, it's being worked on now. Please test and provide fserve with detailed feedback. That's the only way this works, everyone needs to help test and provide good feedback.
[Optimus One, P500 Original Android Development] terratrix:
Tried the latest testing, axis workaround is great, but the CPU touch spike still remains(PES2012 lags compared to Paolo's v6 Touch)
[Optimus One, P500 Original Android Development] fserve:
When axis bug is fixed will lag more.

Try the without axis workaround fix version :-)
[Optimus One, P500 Original Android Development] terratrix:
Well, using the previous testing release performance is still the same on PES2012:eek:
[Optimus One, P500 Original Android Development] Turducken:
I think we've got our wires crossed here. fserves .32 testing kernels include CPU spike fix. None of francos .35 kernels include it.

Please install a .32 kernel rom, test 19.2 gbs vs the gbs testing releases.
[Optimus One, P500 Original Android Development] terratrix:
Well, i'm on new baseband and on stock gingerbread rom, and i don't have enough bandwidth currently to switch back(have to wait for next year). So, i guess, i have to wait:p
[Optimus One, P500 Original Android Development] franciscofranco:
Hum what? I already changed all the msleep **** from 100 and 120 to 10, and that's how mik fixed most of the CPU lag the first time. Apart from that there's not much more to be done, even with my Nexus S when I touch the screen I notice a few FPS drop, thats with EVERY phone, so I don't know what you guys want more with such low hardware **** as this P500, there are no miracles.
[Optimus One, P500 Original Android Development] Turducken:
Using System Tuner and setting gov to Performance; using Paulos v6 Touch kernel, (the one with his CPU touch spike fix) which includes his rudimentary axis inversion fix, CPU is impacted by ~5-10% when first touched and then backs off to 0% impact.

Using your latest test kernel with improved axis inversion fix and miks CPU spike fix, CPU is impacted when touched by about 35-40% and remains that high until my finger is removed. Compared with your previous stable version this is unchanged.

This is why I assumed it didn't include the fix. I'm guessing this is why terratrix is reporting that the CPU touch spike is still present.

I compiled Paulos v6 sources using the same toolchain he used (git v4.4.3). The result was the NoTouch kernel who's CPU touch spike is also about 35-40%. I can only assume that he didn't include his CPU Touch fix in his released sources. :(
[Optimus One, P500 Original Android Development] Lycan:
Hmm..Well said.

But why isn't this impacted greatly when using neocore ?

When i used neocore, the fps went down to 57 from 62 on touching. So I assume, neocore isn't the best way to measure cpu usage. Trying system tuner atm.

EDIT : Ok just tried system tuner. Cpu usage goes up from 6-15% to 50-55% when touching the screen...OCed to 748/480 smartass. And neocore drops by 5-6fps with continuous 'tap down'
[Optimus One, P500 Original Android Development] franciscofranco:
Ok thanks for explaning, I was unaware of the specific behavior. I'm gonna try for one more time fix blackscreen **** and to improve the touch driver before I mark this kernel stable and stop developing for P500.
[Optimus One, P500 Original Android Development] voyager20021:
Bad news for us. Maybe some other devs will continue your work if anything else can be done with your kernel? Presumming to have your approval off course.
[Optimus One, P500 Original Android Development] tenea:
Hey, Franco! First of all thank you for your great work! Second, with this last testing release, when I scroll a web page or a image it's like having a little wave in the midle of screen. Is anyone experience this or it's just me?!.. Thank you
[Optimus One, P500 Original Android Development] tenea:
Forgot to mention, I'm on 729/480 conservative
[Optimus One, P500 Original Android Development] voyager20021:
Dont see anything like that, except for the waves made by overscrolling at the begining and the end of pages.
[Optimus One, P500 Original Android Development] socialdistortion:
Sorry if this has been mentioned before

I flashed an old CM7 rom which had blackscreen problem. I noticed something very peculiar about the blackscreen bug.

When I click the buttons, I get a black screen which requires lots of tapping around to bring the screen alive. I noticed that the screen turned on instantly if we touched the area where the unlock slider is usually located.

I tried multiple times and the screen came alive with a single touch every time I faced the blackscreen bug. If I touched any other part of the screen, nothing happens.
[Optimus One, P500 Original Android Development] voyager20021:
Its a known workaround blackscreen bug.
[Optimus One, P500 Original Android Development] allsalvati:
I'm getting this behavior too!

The blackscreen bug seems almost solved.

Since yesterday the screen didn't wake only 2 times.

I'm using Mik's 6.6.1 with 600/768Mhz and SmartassV2.
[Optimus One, P500 Original Android Development] lupohirp:
also for me with my aosp rom!!!infact seems that screen goes on when recevice vibration!:)
[Optimus One, P500 Original Android Development] RevengeFNF:
Another workarround for the Blackscreen bug, is to have a Live Wallpaper.
[Optimus One, P500 Original Android Development] voyager20021:
Yap, that seems to make the phone more responsive and less blackscreen bug. A lot more responsive.
[Optimus One, P500 Original Android Development] RevengeFNF:
Probably, the live wallpaper enters in action when we wake up the phone, and the screens reacts.

The same way that the screen reacts if we touch it, and the Blackscreen bug goes off.
[Optimus One, P500 Original Android Development] franciscofranco:
Yes we know that, the problem is that I can't find the portion of code that makes the phone behave like that AND I don't know how mimic that. I know there is a way to remove the blackscreen, but the battery usage increases like 50% and I don't want lame hacks.
[Optimus One, P500 Original Android Development] franciscofranco:
Ups..double post..
[Optimus One, P500 Original Android Development] voyager20021:
Maybe giving the phone a small and fast task to do when triggered. But i think this is exactly what crt animation did, which worsened the situation.

The Live Wallpaper **** does a good job, but eats battery.
[Optimus One, P500 Original Android Development] franciscofranco:
Seems easier said than done. If someone gets me this msm7x27 soc manual I can read about it and implement a few wakeup masks, but without a manual its a no go.
[Optimus One, P500 Original Android Development] JastaPein:
GOOGLE IT !!!! :p Ahahaha.. . Kiddin :D
[Optimus One, P500 Original Android Development] Bec de Xorbin:
This maybe: http://files.persona.cc/zefie/files...SM7627_CHIPSET_TRAINING_-_BASEBAND_TOPICS.pdf

There is one especially for MSM7227 but I can't find it. The only thing I found for MSM7227 is in the attachment.
[Optimus One, P500 Original Android Development] franciscofranco:
Thanks man, will see at home, university now.
[Optimus One, P500 Original Android Development] voyager20021:
Wow, maybe we struck gold!? And i just thought this would be so hard to find. Could there be someone who has access to exactly what we need if that isn`t the one? This is awsome!

Ups! Lots of Korean text out there if you search for those training manuals.
[Optimus One, P500 Original Android Development] Sephirothrx7:
Installed the testing release today. From what I have tested, everything is working fine on aga-rom 2, no black screen bugs (or its just related to cyanogen?). The only problem for me is the battery consumption, as Paolo kernel was using a bit less.
[Optimus One, P500 Original Android Development] Mangala_Dharma:
I get this wave passing through the screen in landscape mode on Phoenix rom, kernel seems a little bit more battery-friendly.

Sent from my LG-P500 using Much Love
[Optimus One, P500 Original Android Development] tenea:
+1 that wave I was talking about too.
[Optimus One, P500 Original Android Development] mastaeit:
F#ck that wave, I'm happy that for 12 hours sleeping the battery is still 100% (2211 kernel).

Enviado desde Swype (dirtyplay)
[Optimus One, P500 Original Android Development] voyager20021:
Really? You calibrated battery?
[Optimus One, P500 Original Android Development] mastaeit:
Just charged to 100% , wipe cache, bat stats, flash the kernel, and when the phone boot I remove the charger and go to bed.
[Optimus One, P500 Original Android Development] socialdistortion:
^^ Get ready for a sudden drop in battery :p;)
[Optimus One, P500 Original Android Development] voyager20021:
Use batt calibration from market or wipe batt status after flashing kernel.
[Optimus One, P500 Original Android Development] terratrix:
Yep, sometimes battery life get lost when battery is taken out, but in some cases it gains. Otherwise it is the graph did not record the battery drain( like making a backup in CWM) hence the sudden drop in graph.
[Optimus One, P500 Original Android Development] acax456:
2 version. Which is better?
[Optimus One, P500 Original Android Development] Sephirothrx7:
In 8 hours of sleep, my battery 8%. What rom are you using?
[Optimus One, P500 Original Android Development] mastaeit:
Everything is in the signiture. (sry OffT)
[Optimus One, P500 Original Android Development] terratrix:
Obviously latest one

CPU frequencies and governor?:)
[Optimus One, P500 Original Android Development] Hanny:
v2-22112011 Report

thanks franco!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! :):):):D:D:D

/cache wiped

/dalvik cache wiped

flashed it and initially tested some critical stuffs, heres what i got!

1. Blackscreen bug

(Maybe widgetlocker does something? idk)

It is 90% solved a very long time ago for me like since october :D so not much difference in this version! :p even i tried my fastest speed to lock screen + press button to wake it up, as before, it only gives me a <0.5second delay and IDFC it lolll

if its after 5 seconds after screen is locked/turned off, at 99% of the time it is an immediate wakeup if i press hardware buttons ;)

2. Axis inversion bug

Yes i understand our phones got **** (really ****....) hardware and it cant be completely solved :o:o but there is a significant improvement in this update!! :)

averagely, out of 3 tries at multitouch test app, 1 of them successfully passed the opposite side of the touch dot (no axis inversion)

therefore, for MY phone, its 33.3% fixed :D its ok!! **** LG :)

(btw i play guerilla bob with the bottom left as touchpad and top right as fire button :p)

3. "Scrolling wave @the middle of the screen" bug

Well users I've tried different ways --- (All with both landscape and portrait)

Dolphin Browser HD - scrolling m.facebook.com (white background)

Dolphin Browser HD - scrolling friendcaster for facebook news feed (white background)

Dolphin Browser HD - scrolling up&down and pinch in&out on xda-developers.com (white background)

CM7 gallery app - scrolling images left&right and pinching in&out in (black background between images)

Settings app - scrolling up&down (black background)

Results: beside CM7 overscroll effect, no such kind of other "waves"

for ur reference, my configurations are on my signiture

ok so other users which are having this "bug", im quite curious, can you please state out ur roms, and... how exactly do you produce that "wave"?

if possible please screenshot with ShootMe or those apps which countsdown :)

4. Performance

As always, it must be supersonic :D, and i dont see much performance changes in the changelog so im lazy to benchmark :p

5. Stability

New bunch of statistics is begun in the link in my signature :) as above, i believe theres not much change though!

6. franco do i love you

Surely yes!!! for your continued support for this very best kernel on the ****test phone and I wish you every success in all your kernels development!!!! :D:D:D:D Best of the luck in building everything!!! ;) I will always be your detailed reporter:cool:
[Optimus One, P500 Original Android Development] :
Hey, can anyone fix the CPU spike bug (CPU shoots up and games lag)?

P.S.: This is only a request.
[Optimus One, P500 Original Android Development] vlt96:
Your using 6.5.8 or 6.6.1, saw you posted on both;)

Sent from my LG-P500
[Optimus One, P500 Original Android Development] franciscofranco:
What do you think we've been doing? I'm sure you know how to read.
[Optimus One, P500 Original Android Development] Sephirothrx7:
Thanks, I installed the CM 7 6.6.1 and latest kernel, lets see how it works.
[Optimus One, P500 Original Android Development] vlt96:
How does this compare to goldenleaf?

Gleaf has awesome performance, and still keeping battery to the max!!

Is this bettee;)

Sent from my LG-P500
[Optimus One, P500 Original Android Development] haxor:
Confuse

what is main difference between both of them in Kernel: Goldenleaf v111108 / franco.kernel.v19.4-gbs.v19 ?:confused:
[Optimus One, P500 Original Android Development] franciscofranco:
What does that question go to do with this thread?
[Optimus One, P500 Original Android Development] Garuxa:
The difference is that you were wrong topic, moron

Enviado desde mi LG-P500