yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500 Android Development] franciscofranco:
What have you done this time explicitly? (in the config I mean :p)
[Optimus One, P500 Android Development] fserve:
# CONFIG_MSM_ONCRPCROUTER_DEBUG is not set

CONFIG_MSM_CPU_FREQ_MIN=480000

CONFIG_RFKILL_PM=y

# CONFIG_MTD_LAZYECCSTATS is not set

# CONFIG_SND_VERBOSE_PROCFS is not set

# CONFIG_SND_USB is not set
[Optimus One, P500 Android Development] franciscofranco:
Nice finds you've been doing. That DG_timer patch plus some other ****s I've found and that are on my github made my battery life on my hauwei gigantic. With 1,5ghz all the time when screen is on + SmartassV2 yesterday merged by erasmux = 60% left with very intensive use (gaming, wifi, sms, music, bluetooth). It's crazy. Can't wait for the new mainstream update so I can do some more magic with the LG kernel using some of your config findings, very nice :)
[Optimus One, P500 Android Development] fernando1sg:
this guy is doing a great work, well you both.

Flashing latest update!
[Optimus One, P500 Android Development] franciscofranco:
Indeed, fserve's been doing a great research and it's great that he shares what he actually changed ;)
[Optimus One, P500 Android Development] deniso177:
Great job, your d version has awesome standby battery life, just flashed e, so will see how that improves
[Optimus One, P500 Android Development] fserve:
Thanks ppl.

for devs, all my .config are in the first page (or inside the kernel in /proc/config.gz lol i didnt disabled that **** yet <)

Lol, i keep forgeting things.

next release i need remember to remove oprofiling things, not a big deal, so i will wait for more
[Optimus One, P500 Android Development] franciscofranco:
Hmm I didn't know the overhead of oprofile **** was so high to be honest! And it causes interrupts even if interrupts are disabled in parts of the kernel...
[Optimus One, P500 Android Development] makona:
Great work franco and fserve.. battery is awsome man! There still more updates for the battery.. may be one day our phone will last for 3 straight days with heavy usage.. :p
[Optimus One, P500 Android Development] fserve:
removing oprofile/profiling done;

vm event counters too

:-)

To remove profiling was need remove the arch/Kconfig file, cos it was enabling profiling and more options all the time.
[Optimus One, P500 Android Development] deniso177:
Is it f version time lol =p

in the past 3 days i flashed 4 of your kernels =)
[Optimus One, P500 Android Development] franciscofranco:
Hmm... instead of deleting that file try to do this for example:

config HAVE_DMA_ATTRS
[b]default n[/b]
bool

In every config like that add "default n".
[Optimus One, P500 Android Development] fserve:
Another thing, i'm getting too many logcat messages like that:

D/dalvikvm( 2297): GC_CONCURRENT freed 386K, 50% free 3065K/6087K, external 187K/512K, paused 6ms+5ms

D/MediaUploader( 2087): PhoneStateBroadcastReceiver.onReceive: CS is disabled or not initialized - skipping Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000000 (has extras) }

D/WifiService( 1363): ACTION_BATTERY_CHANGED pluggedType: 2

D/dalvikvm( 1470): GC_CONCURRENT freed 431K, 48% free 3322K/6279K, external 0K/512K, paused 5ms+5ms

D/dalvikvm( 1858): GC_EXPLICIT freed 4K, 49% free 3151K/6151K, external 0K/0K, paused 54ms

D/MediaUploader( 2087): PhoneStateBroadcastReceiver.onReceive: CS is disabled or not initialized - skipping Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000000 (has extras) }

D/WifiService( 1363): ACTION_BATTERY_CHANGED pluggedType: 2

D/MediaUploader( 2087): PhoneStateBroadcastReceiver.onReceive: CS is disabled or not initialized - skipping Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000000 (has extras) }

D/WifiService( 1363): ACTION_BATTERY_CHANGED pluggedType: 2

D/dalvikvm( 1928): GC_EXPLICIT freed 147K, 49% free 3391K/6535K, external 0K/0K, paused 85ms

D/MediaUploader( 2087): PhoneStateBroadcastReceiver.onReceive: CS is disabled or not initialized - skipping Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000000 (has extras) }

D/WifiService( 1363): ACTION_BATTERY_CHANGED pluggedType: 2

D/dalvikvm( 1363): GC_CONCURRENT freed 845K, 40% free 5916K/9735K, external 618K/1130K, paused 8ms+10ms

D/MediaUploader( 2087): PhoneStateBroadcastReceiver.onReceive: CS is disabled or not initialized - skipping Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000000 (has extras) }

D/WifiService( 1363): ACTION_BATTERY_CHANGED pluggedType: 2

D/dalvikvm( 1448): GC_CONCURRENT freed 445K, 50% free 3051K/6023K, external 664K/1018K, paused 5ms+4ms

D/dalvikvm( 2360): GC_EXPLICIT freed 5K, 49% free 2894K/5575K, external 0K/0K, paused 48ms

D/MediaUploader( 2087): PhoneStateBroadcastReceiver.onReceive: CS is disabled or not initialized - skipping Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000000 (has extras) }

D/WifiService( 1363): ACTION_BATTERY_CHANGED pluggedType: 2

D/MediaUploader( 2087): PhoneStateBroadcastReceiver.onReceive: CS is disabled or not initialized - skipping Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000000 (has extras) }

D/WifiService( 1363): ACTION_BATTERY_CHANGED pluggedType: 2

D/MediaUploader( 2087): PhoneStateBroadcastReceiver.onReceive: CS is disabled or not initialized - skipping Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000000 (has extras) }

D/WifiService( 1363): ACTION_BATTERY_CHANGED pluggedType: 2

D/dalvikvm( 2297): GC_CONCURRENT freed 386K, 50% free 3065K/6087K, external 187K/512K, paused 7ms+4ms

There is any way to lower the number of ACTION_BATTERY_CHANGED or things like this?

if not, i'm thinking in kill logcat and dmesg in a future version, just for testing :P
[Optimus One, P500 Android Development] franciscofranco:
Let me research.
[Optimus One, P500 Android Development] franciscofranco:
As far as I could read that's a normal behavior since Android Donut, so your only option is to disable logcat. I actually don't know how to do that.
[Optimus One, P500 Android Development] fserve:
I tried this default n and didn't helped :/

Testing new build with:

CONFIG_HAVE_CLK=y - for battery save

#CONFIG_ANDROID_LOGGER - logcat

#CONFIG_IKCONFIG_PROC - /proc/config.gz

#CONFIG_PRINTK - dmesg
[Optimus One, P500 Android Development] franciscofranco:
****.

That proc/config.gz thing is useful sometimes. I tried a different approach when disabling printk on my hauwei kernel. If I disabled printk in the config it would return me an error so I went directly to the file applied some simple code that I've seen in another kernel: https://github.com/franciscofranco/...50ded33735dadaab815ad25e92d4db5326daef#diff-1

See the printk.c diff.
[Optimus One, P500 Android Development] fserve:
no need for editing printk.c for p500 :-)

all they are dead now!

one more version? :D

Testing version

.14f

added:

CONFIG_HAVE_CLK=y - for battery save

removed:

oprofile/profiling

vm event counters

CONFIG_ANDROID_LOGGER (logcat)

CONFIG_IKCONFIG_PROC (/proc/config.gz)

CONFIG_PRINTK (dmesg)

http://www.multiupload.com/HNQL2GSL46
[Optimus One, P500 Android Development] aspee:
As I am using 6.6.1 beta this is not for me!

hey why don't all kernel builder come together and make the one kernel?

the XDA p500 kernel !!!!!!!!!!
[Optimus One, P500 Android Development] InfiniteRisen:
Some people want things enabled and disabled, VSYNC for example.Hard to make something everybody would agree on. But I see your point though.

Swyped from my LG-P509 using XDA App.
[Optimus One, P500 Android Development] fserve:
That's why i'm asking which versions i should do :-)

The cpu spike fix add stutter, this is what i saw on testing versions.
[Optimus One, P500 Android Development] dancom96:
What about a partial cpu spike fix if that makes any sense?

I think the non gaming one should be cfs, vsync on, axis fix off, battery saving aggressive, smooth scrolling

*edit*

Is the battery saving aggressive what lowered 3d performance? If so, battery saving light should be better, as the perf difference is quite noticeable.
[Optimus One, P500 Android Development] fserve:
ok, will disable axis fix on non gaming. :)

Partial fix? hmm, the "fix" was with msleep2, i've tested 1,10,100. And i'm using '1'. Cant lower more :/

Test it, please:

http://www.multiupload.com/GX5PERTB7Y

Is it smooth?
[Optimus One, P500 Android Development] Garuxa:
Let's see...

EDIT: It's fast, but not smooth
[Optimus One, P500 Android Development] fserve:
K, try again.

http://www.multiupload.com/PR91VPGIS0

is it smooth?
[Optimus One, P500 Android Development] nd4spdbh:
trying out the gbs-111124_smooth_scroll_v2 ... figured id give gbs a try after using goldenleaf for so long... GL is awesome for battery, just wondering what all the fuss is for gbs :D

Nandroid backup of my good stable smooth long lasting goldenleaf... check.

Ill report back laters.

BTW, thanks again fserve for your awesome work!
[Optimus One, P500 Android Development] fserve:
Even goldenleaf got a new version. For now, test the latest testing from post above, please?
[Optimus One, P500 Android Development] Garuxa:
Nope, still do not feel smooth (CM7 6.5.8 - InteractiveX 748/480)
[Optimus One, P500 Android Development] fserve:
Tks, try again.

http://www.multiupload.com/JYDWE1G07A
[Optimus One, P500 Android Development] khoa02061986:
I'm can old-fashioned , but the version "gbs.111122 - CFS - vsync off - with workaround axis" of you - well played game. high benchmark. Why not develop it? And why not do it on the BFS?

"gbs.111122 - CFS - vsync off - with axis workaround" include any options? Please let me know.

CFS / BFS

vsync on / vsync off

fix axis on / off axis fix

fix cpu spike on (-smooth) / cpu spike fix off (+ smooth)

aggressive saving battery / battery saving light
[Optimus One, P500 Android Development] Garuxa:
It is soft, but not as much as gbs-111125u_gamefix1 version :( (note that this is just my opinion). Using live wallpapers feel stuck, No live wallpapers feel less

Benchmark is not everything...

I think you should put in place for other users, I mean some look only maximum battery performance (for them this goldenleaf), others seek only high scores on benchmark (like you) and others seek to balance the two things (people like I) so I think fserve throws a lot of test kernels to find the most perfect balance that can have with this phone

It should be:

cfs = balanced

bfs = exclusively for games

If I am wrong, please correct me :)
[Optimus One, P500 Android Development] fserve:
Hmm, so this last one was better? Removed a **** that i never knew what it did...

Ok, lets try one more testing.

Test for smooth => http://www.multiupload.com/XDOQ0CF6BB

is it better? worse? equal? [compared to the http://www.multiupload.com/JYDWE1G07A]
[Optimus One, P500 Android Development] khoa02061986:
I think the benchmark but not all, but it responds to the performance of the kernel, otherwise you will not have the apk benchmark.

I choose the game, so I propose, would fserve will help me and many like me - playing games, a kernel with the highest performance for the game.

There are people like you - choose the balance, but also people like me - Game

I hope my suggestions help fserve complete the kernel version of him (even if not then please ignore)

I also thank you, admiration, and admire the enthusiasm of the fserve.
[Optimus One, P500 Android Development] 32bit:
It's smooth but the performance is slightly lower then yesterday's vsync-off. And there is no touch fix.

Oh, fserve, you're releasing test versions too fast. For me it's occupies not less than 30 minutes to test one kernel - reboot, clear, flash, rebuild Dalvic, get very first impressions. Too fast, it's physically impossible to test a lot on real system full of apps :(

Not saying about I'm not see new versions just in the time of release, there is some lag when I'm not monitor DX. And I'm rarely could test the new version immediately :(
[Optimus One, P500 Android Development] Garuxa:
We are almost equivalent (I'm not sure), but at least it is more smooth than the previous

Thanks for having this great patience to create several test kernels :D

Again, not all benchmark scores, they can often be misleading. The only apps benchmark to which they believe is a Neocore and Antutu. I've never believed in what marks Quadrant (Standart and Advanced) why? For example, the P500 is better than a Samsung Galaxy 5, this phone using Quadrant is not come over 1500. With the Samsung I have come to the 1800 (WTF?) Being that is slower, has less memory, etc..

I insist on my opinion that the best is:

cfs: for those who want to balance

bfs: for those who want to play and play no matter if the phone is overheating or if the battery is not paying them enough

Is just my opinion :)
[Optimus One, P500 Android Development] fserve:
Garuxa said that this one wasn't smooth, so i released another one...

I'm trying to make my phone slower so i can test it too...
[Optimus One, P500 Android Development] khoa02061986:
ok, I wait for a kernel version of the best professional game.

We hope that the next version of the mod kernel-based BFS
[Optimus One, P500 Android Development] fserve:
Now i see the sttuter problem.

(live wallpaper, all animations activated, all image quality on high, go launcher)

when i press the button to see all my apps and go back home it isn't smooth.

goldenleaf-111126 performs very better. (at least, without live wallpaper, this **** kills my phone performance at all)

very weird.
[Optimus One, P500 Android Development] nd4spdbh:
which version of goldenleaf? 111126 from the first post?

btw GBS messed up my widget locker for what ever reason... messed with the sizes of the stuff, rebooted many times. probably would of gone away had i redid my lockscreen widgets.
[Optimus One, P500 Android Development] fserve:
Yes, this one from the first post.

I'm testing here and vsync off kernels seems to be smooth.

Test this, check if it is smooth :-)

http://www.multiupload.com/AQXG8B70TH
[Optimus One, P500 Android Development] 32bit:
Goldenleaf 111126 (as 111122) is not smooth.

Gbs versions 111125U* (smooth, game, hope) and 111126 are much better!
[Optimus One, P500 Android Development] 32bit:
Gbs-111126-gamefix1 with .35 backported driver is smooth acceptable.

And it's definitely The Neocore King! (for my setup at least)

AnTuTu scores are quite similar to other "game" versions.
[Optimus One, P500 Android Development] MaKTaiL:
I just tested the new goldenleaf version and it's very smoothly, I liked it.

Fserve, I think you should change the default governor to smartass while keeping 480/600 overclock.

In my opinion its much better for battery and it's better than interactivex on performance.

This is first thing you should do before testing kernels for smoothness.
[Optimus One, P500 Android Development] vlt96:
Conservative is better, I was amazed how smooth and cool it is... pes12 lag free on 480/729 conservative;)

Sent from my LG-P500
[Optimus One, P500 Android Development] MaKTaiL:
Conservative is not that good on lower overclocks though, at least for me.

This is interesting though. It would be great to hear from other people so that fserve can look into it.
[Optimus One, P500 Android Development] vlt96:
Yes, a 480/600 is the same on any governor, except minmax, peformamce and powersave/wtf is that named...

I can go stable @480/787 interactiveX, but I prefer 480/729, as it is less risky, and I play no angry birds;)and perfect performance on any game;)

Sent from my LG-P500
[Optimus One, P500 Android Development] MaKTaiL:
But what about battery? When I was using InteractiveX on 480/600 my battery was draining really fast even on standbye. For exemple, I would go to sleep with 100% battery and when I woke up the next morning my phone was with 60% battery. I can't imagine how 480/729 would be for battery on InteractiveX.
[Optimus One, P500 Android Development] vlt96:
Conservative on 480/729 has better performance than 480/600 interactivex, and 600 and upper frquencies have same volatage;)

Sent from my LG-P500
[Optimus One, P500 Android Development] MaKTaiL:
Well, let's wait and see what fserve has to say about this.

---------- Post added at 10:22 AM ---------- Previous post was at 10:20 AM ----------

What does SLUB Memory Allocator do on the new Goldenleaf?

I noticed the phone is using less memory than it used too. Is that it?
[Optimus One, P500 Android Development] Jaani:
For me u r right..:)
[Optimus One, P500 Android Development] khoa02061986:
"GBS-111126-gamer" and the benchmark.

Gingercrust v1.5

OC = 480/768

Gonevor = smartassV2

Antutu: 1884

Neocore:

+ No sound, no touch: 66.9 FPS

+ No sound, touch: 61.5 FPS

-> Very good
[Optimus One, P500 Android Development] Lycan:
Hey fserve.

How did you get blood and glory to work ?

Can you tell franco to add these changes to his new kernel/tell us?

Thanks.
[Optimus One, P500 Android Development] khoa02061986:
I've been playing this game, play very smooth. Options:

Gingercrust Rom 1.5 + gbs.111126-gamer

oc: 480/768

gonevor: smartassV2

111122 kernel vsyn off with axi ... do not play this game.
[Optimus One, P500 Android Development] Marius Cristian:
I think that last version of goldenleaf has a bug.Sometimes the buttons(back,home,etc) / except power one,freeze.I can use my phone,touch screen is working perfectly but not the the buttons.The restart seems to fix the problem but is only temporal.If i let it this way,after some time a hear a beep,like the volume does and the buttons are working again,but sometimes they don't.Anyway,after 5 minutes or so,the keyboard blinks and the buttons work again.I think volume has a problem,because when i set the volume that bar remains on the screen,i lock the phone so the bar disappear and after unlock the buttons freeze.Sometimes,the bar doesn't stay on the screen,however the keys get stuck.I assume that is your kernel problem because i have been using CM7 for a few weeks and this problem appeared right after i installed your kernel.I liked this version so much because at 480-729 performance/smartass my phone works great with music,im+,wi-fi and game + background programs.All at one time.With older versions sometimes it restarts itself.Hope you can help me :) Thanks
[Optimus One, P500 Android Development] buzzdr0id:
New GBS is smoother than New Goldenleaf :) Thanks once again !
[Optimus One, P500 Android Development] vlt96:
Wipe /cache

/data

/system

Battery stats

Dalvik

In cwm

Then reflash and enjoy;)

Sent from my LG-P500
[Optimus One, P500 Android Development] sprite00:
Guys...little problem...after i flash goldenleaf .v111126 i restart the phone and that it freezes after the logo...what should i do? please help me !
[Optimus One, P500 Android Development] vlt96:
Wipe dalvik and battery stats and never use it on stock GB and mik 6.6.1;)

I think I flashed like... 20 kernels, and never got bootloops;)

Sent from my LG-P500
[Optimus One, P500 Android Development] Marius Cristian:
I found when the bug appears.After i overclock,if i use volume the other buttons freeze.I wiped cache,davlik-cache and battery stats before install.However,i will do as you said tomorrow,even if i don't wanna spend few hours to bring the phone the way it was ( i mean apps,games,etc)

EDIT:I remember that when i installed CM7 after overclock i couldn't use camera sometimes(the phone restarts) so if this method doesn't work i guess it's some rom instability!
[Optimus One, P500 Android Development] vlt96:
titanium backup;)
[Optimus One, P500 Android Development] Garuxa:
Yes, is smooth :)

Enviado desde mi LG-P500 usando Tapatalk
[Optimus One, P500 Android Development] dancom96:
I have no idea what I'm talking about, but isn't msleep not supposed to be used? As seen in this post:

http://xdaforums.com/showpost.php?p=10909973&postcount=1
[Optimus One, P500 Android Development] zakk87:
Wifi works good with x26, but screen don't wake up after lock, like in last 4 goldeanleaf versions.

Battery after 2.5h is 85% not good.
[Optimus One, P500 Android Development] Vermiglio:
last kernel 111126gamer smooth
[Optimus One, P500 Android Development] fserve:
Remove "screen on" animation.

Sent from my ASUS Transformer TF101
[Optimus One, P500 Android Development] zakk87:
I never use on screen animation. screen not responding after lock. Only buttons light
[Optimus One, P500 Android Development] fserve:
Sorry, i dont know.

I dont have this problem. Try remove any type of modification that you did in CM7 config.
[Optimus One, P500 Android Development] MaKTaiL:
Hey fserve, read page 222 and tell us what you think about changing the default governor.
[Optimus One, P500 Android Development] fserve:
Governors can't do miracles.

InteractiveX works very good for me. :)
[Optimus One, P500 Android Development] 32bit:
Fserve, is gbs-111126-gamer have a less powersaving settings?

Is it have touch fix or not?
[Optimus One, P500 Android Development] dancom96:
Just tested gbs-111126-gamer, stuttery
[Optimus One, P500 Android Development] Marius Cristian:
I did this and now my phone isn't starting...stuck at LG logo.what should i do?maybe reflash 6.5.8?
[Optimus One, P500 Android Development] InfiniteRisen:
When you wipe dalvik it takes a while to rebuild. If it takes longer than 5min then reflash your ROM.
[Optimus One, P500 Android Development] MaKTaiL:
Wow, you were very open minded.....
[Optimus One, P500 Android Development] fserve:
Yes, less powersaving settings, with touch fix.

InteractiveX rocks :-)
[Optimus One, P500 Android Development] MaKTaiL:
Please, ask people here what they think. InteractiveX is draining a lot of battery from the phone, specially when it's on standby. It shouldn't. You should give a chance to Conservative or smartass so you can see the difference. Trust me.
[Optimus One, P500 Android Development] vlt96:
Reflash 6.5.8, w

Wiping system deteletes the rom

Sent from my LG-P500
[Optimus One, P500 Android Development] fserve:
Garuxa tested and told that it's smooth.

I've tested too... it's smooth here.

========>> Try remove and apply again your live wallpaper.

Hmmm, yes. Conservative would be good for goldenleaf kernel. And PERFORMANCE (as default) for gbs-gamer :D

What do you people think? :-)
[Optimus One, P500 Android Development] Garuxa:
Man, if you do not like the governor, just change it and be happy. If it is so fserve is on the recommendation of it, but that does not mean that this forcing you to use it.

:rolleyes:
[Optimus One, P500 Android Development] dancom96:
I don't use a live wallpaper, should I apply one?

I agree with this, it literally takes 5 seconds to change, and it is a matter of preference mostly.
[Optimus One, P500 Android Development] MaKTaiL:
It's not about me changing it, but making the changes for people who have no idea what overclock is or what governors they should use.
[Optimus One, P500 Android Development] Garuxa:
It is the responsibility of each person to investigate and prove to all the governors to see which is the best for you. If a flashing a kernel, is because he knows what he is doing and is at your own risk. :)

Sorry my OT fserve
[Optimus One, P500 Android Development] Marius Cristian:
Well...i reflashed the rom,the kernel and same bug as before.

However,i have this problem only with last version of goldenleaf.Now i flashed previous version and this bug is gone.Is there any method to quickly modify the volume without using the specific buttons?Who knows...maybe this will solve my issue.And just for the record...it's ok to keep the phone at 480-600 mHz with smartass ?
[Optimus One, P500 Android Development] vlt96:
Fserve, I think this no ot, this should go on 1st post!!

Sent from my LG-P500
[Optimus One, P500 Android Development] fserve:
People, you are out of focus. Seriously.

Governor? Very easy to change, smartass was default for a good long time. maybe i do it again.

Our problem now is that sttutery thing.

Latest gbs-gamer release was reported as smooth by Garuxa and not smooth by dancom96. I need more reports of it.

@Marius Cristian, yes it's ok to have the phone with those clocks, could you make a video of your problem?

@dancom96 no, do not apply live wallpaper... i said that cos i've use it to test stuttering.