yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500 Android Development] fserve:
Hmm, ok. I think that it's really not working.

Just changing one minor thing and i think that now it will work.

Please, testers, help me :-)

Is it charging while off and then if you press power button it starts the phone on v18b1?

v18b1 - http://www.multiupload.com/IHTXY4LG74

I really need to have this fixed right now to the next steps :-)

Very thank you! My job ended last month and since then I'm looking for a new one, any donation would certainly be of great help.
[Optimus One, P500 Android Development] Javi22:
I would wanna ask you what are the mayor bugs or the reason why CFS gbs.v18a is not so stable? What are the disadvantages with respect to franco 19.4 CFS?
[Optimus One, P500 Android Development] DaXmax:
So far, its stable on CyanogenMod... Fserve is talking about the froyo... It's has so called 'bugs' while offmode charging... Franco.kernel 19.4 CFS is for performance and Fserve's gbs is powerpack battery life...
[Optimus One, P500 Android Development] masteryx:
Looks like it's up to me to test kernels on Froyo.

@fserve: success with v18b1, good job! The phone charges while off and powers on while still connected to charger.

A personal curiosity: why is v18 so much smaller than v17? And what are the next steps? :D

---------- Post added at 11:15 PM ---------- Previous post was at 10:57 PM ----------

First impressions, after a few minutes of usage and test:

- the Quadrant score looks a bit higher (1310 vs 1255), but this is irrelevant for me;

- the screen flipping on the desktop and the scrolling in any list are no longer smooth, but a lot choppier than on v17. I'll give it time to build cache and stuff, but I don't think it will go away.

Now charging to full and then let it rest overnight. More feedback tomorrow.
[Optimus One, P500 Android Development] dancom96:
It is still calibrating the software which may think the battery is at 10%, when it is actually at 40%
[Optimus One, P500 Android Development] 32bit:
It's strange that some people says that v.18a have a problem with offline charging. I've tested it with my 2.2.0.Froyo and I can confirm it is works as it should to.

But there is one peculiarity that could mess somebody: when the phone been switched off automaticy due to it's battery was discharged, then when you plugged it to charger, the phone DOESN'T boot immediately after the Power button depressed, but only after the battery would charged to some appropriate level.

So, in this case it seems that the phone doesn't react on buttons for a few minutes. But been switched off manually with some enough battery level (10% or more, for example) the phone reacts immediately.
[Optimus One, P500 Android Development] fserve:
32bit, they are reporting a testing version (v18b/v18b1) not v18a...

About this 10% thing, i've heard that this is the normal behaviour of the LG Stock ROM.

Sent from my ASUS Transformer TF101
[Optimus One, P500 Android Development] nd4spdbh:
and where do we make donations to? paypal email?

cus i cant believe how much batt life im getting out of my phone with v110919 its awesome.
[Optimus One, P500 Android Development] krishnandu.sarkar:
Just check the Donate To Me link under his thanks meter and above his profile avtar.
[Optimus One, P500 Android Development] masteryx:
@32bit: My test were conducted with the battery 80% full. But thanks for your input, it may be useful for other users to keep this in mind.
[Optimus One, P500 Android Development] terratrix:
Ok, surface dithering options sticks with v18b now, thanks:)

Also, can you include OndemandX in the next release?
[Optimus One, P500 Android Development] DaXmax:
What is the latest of OndemandX do?

Battery saver?
[Optimus One, P500 Android Development] terratrix:
I think some tweaks and Suspend/Wake profiles, i prefer Ondemand very much..
[Optimus One, P500 Android Development] DaXmax:
Ohk, but i hoping if fserve can get 'lightass' from the italians... It's a battery saver and performance killer...
[Optimus One, P500 Android Development] franciscofranco:
Lightass -> same governor as smartass, he just changed the name and probably changed one or two values in the suspend profiles - that is called placebo effect.
[Optimus One, P500 Android Development] DaXmax:
Thanks! **** i been fooled!
[Optimus One, P500 Android Development] samcad:
Can I use V18b1 for ma cyanogen??? Now I'm using v18a .....! Is there any difference?
[Optimus One, P500 Android Development] 32bit:
Yes, absolutely. But I say about 10% only for example for manual testing. In real life the depleted phone starts after about 4% charge. It's a protective measure.
[Optimus One, P500 Android Development] fserve:
new testing, v18b2.

http://www.multiupload.com/DWLRLBUJID

IT'S TESTING <<<<<<<<<<

Now, test camera flicker.

Radio worked fine here, (i've removed some radio drivers)

Go testers go!

Go donators :D
[Optimus One, P500 Android Development] DaXmax:
Can i use ur kernel for my rom?
[Optimus One, P500 Android Development] fserve:
wait for a NOT testing release :-) or use 18a/goldenleaf :-)

PS. i forgot to mention, test smoothness on the system :-)
[Optimus One, P500 Android Development] DaXmax:
Hmm ok...
[Optimus One, P500 Android Development] samcad:
Gonna download it now :) I'll test for yu ;)
[Optimus One, P500 Android Development] Garuxa:
Thanks fserve :)

Sorry, dumb Tapatalk :(

Enviado desde mi GT-I5500
[Optimus One, P500 Android Development] terratrix:
Hmm, will the tweaks be on goldenleaf on the next release?
[Optimus One, P500 Android Development] orsonbear:
Testing camera on v18b2

Kernel v18b2 testing

Rom Mik CM 7.1 6.5.7, 480/787

Governors without flicker at all:

smartass, smartassV2, ondemand, minmax, scary, conservative

Governor with some flicker:

interactiveX

I haven't tested other features, only the camera in photo/video mode in various light and subject conditions.

Cheers!
[Optimus One, P500 Android Development] DaXmax:
Camera flicker...
[Optimus One, P500 Android Development] Garuxa:
Thanks dax :)

Sorry, post in this device may not display correctly :(. Tapatalk problems :D

Enviado desde mi GT-I5500
[Optimus One, P500 Android Development] Garuxa:
No more camera flicker (tested with Smartass V2) :) It feels smoother when scrolling through menus. Also Radio works fine (using stock app or SpiritFM Radio) Now to test the stability of the system and battery. All this using CM7 6.5.7

fserve Excellent work, thanks! :)

Enviado desde mi LG-P500
[Optimus One, P500 Android Development] gekko69:
v18b2 feels smoother, still not as smooth as Francos .35 kernel on 6.6.1. If a long list has pictures (e. g. market app) the loading of the pictures stalls the scrolling for a short time.

Camera flickering is gone when overclocking. There are still some stripes in video mode, the more I oc the more stripes. But since I only do photos and no video I don't care. If it proves to be stable then this is a great release. Thank you!

Edit: not to forget, logcat enabled again :-)
[Optimus One, P500 Android Development] DnaPolymerase:
fserve, you deserve a golden statue for this hard work. Just saying, keep going strong.

I'll be sure to come back again when the testing is done, can't wait to test this new kernel.
[Optimus One, P500 Android Development] dancom96:
Camera flicker is gone when ocing! :) Great work, and thanks!
[Optimus One, P500 Android Development] fserve:
Yes :-)

Sent from my ASUS Transformer TF101
[Optimus One, P500 Android Development] samcad:
Fserve... I'm using kernel 18b... its too late to charge usin ma adapter charger....!! I guess its problem of yuA new v18b2... m back to 18a.. ;) love yuA kernel ;)
[Optimus One, P500 Android Development] Jaani:
@fserve..hi mate 1st THANK U for making the Franco's kernel more better...using gbs from a month & its awesome no doubts..:)but in v18a & v18b2 cfs(dont know abt earlier versions)I m having this peculiar freezing while recording videos..see the video below & watch carefully at 18-20sec..using stock freq in CM7 stable..happening in both smartass & its v2..everything fresh install but same..is it a real bug or happening only with me..others plzz test..:)

[YOUTUBE][url]http://youtu.be/865TozuYx4I[/YOUTUBE][/URL]

NOTE:This happens in FK v19.4BFS also..:(

&&& battery is goin awesome as u can see no drop in more than 2hrs..:)
[Optimus One, P500 Android Development] shhbz:
it does not freeze but the lining are there

edited: i forgot flickers happen in andy's rom ,mik rom is clean and works charm and lines are there in andy rom even in day time using normal.

confirming:mik rom works flawless
[Optimus One, P500 Android Development] Jaani:
then its only me...anyone else confirm?lines are there bcoz of the monitor..:)
[Optimus One, P500 Android Development] orsonbear:
I can confirm the camera pause effect.

Kernel: new testing, v18b2. Rom Mik CM7.1 6.5.7

The pause in camcording seems to me related at least to governors. Using smartass it's minimized, using smartass2 it's more evident and frequent. The effect seems to be similar to a filled buffer emptied on the SD in synchronous mode, just to give an idea...

The effect seems also minimized taking a photo before the footage.

Uhm...
[Optimus One, P500 Android Development] Turducken:
Thanks fserve for including the camera flicker fix, no more need for the Italian kernels! ;)
[Optimus One, P500 Android Development] 32bit:
v.18a, ROM 2.2.0.Froyo custom, CPU oc@480/729

Strange results on battery life.

Smartass v.2 overnight (6 hours) in plane mode = 6% drain.

InteractiveX overnight (6 hours) in plane mode = 0% drain (yes, I say ZERO)

Tested several times with very same results.
[Optimus One, P500 Android Development] DaXmax:
Thanks fserve! The v18b2 is a sucess to my rom... Very smooth... So may I release it?
[Optimus One, P500 Android Development] franciscofranco:
Smartass2 is a strange governor. I don't think it caps at X speed during sleep time, but it ramps up its speed when the device wakes up.

Been extensively testing governors and frequency speeds and the more I see, the more I realize that the best governor is Minmax.
[Optimus One, P500 Android Development] terratrix:
As in performance and battery life? With what frequencies? It only uses the the min freq and Max freq so... ...
[Optimus One, P500 Android Development] fserve:
@dax, It's your call =)

@32bit WOW, changing to interactivex in 3...2...1...

@orsonbear this bug does not happen in v15/v17?

@samcad what's the problem with chargin v18b2?

@shhbz do you remember if this happen in v19.3?
[Optimus One, P500 Android Development] DaXmax:
Thanks... I'm gonna make 2 rom...

One is an update for my sonygenmod

Two is ur rom... GBS ROM...
[Optimus One, P500 Android Development] Turducken:
I read somewhere that knzo came to the same conclusion. It's either working hard or it's not. We're only bridging a gap of 250-350Mhz. Why bother with freqs in between? These thoughts have been lingering in my head. MinMax seems the logical choice.

If we had a Tegra dual core then I'd want speedstep or the like.
[Optimus One, P500 Android Development] mDroidd:
Great kernel, even better juice!

Greets

mDroid

ROM: void #forever

Kernel: franco gbs cfs
[Optimus One, P500 Android Development] terratrix:
You FAILED! this is for 6.5.7 not 6.6.1!!!
[Optimus One, P500 Android Development] mDroidd:
Whaha, then it's just me xD

Greets

mDroid

ROM: void #forever

Kernel: franco gbs cfs
[Optimus One, P500 Android Development] deetailed:
Noticing that^ is exactly why I prefer Smartass to Smartassv2 (and thanks fserve for still including it!). But when looking at the CPU stats it very rarely stays at intermediate frequencies anyway, so the behavior is kind of like Minmax.
[Optimus One, P500 Android Development] ert69:
My lockscreen is getting burned in the LCD with Goldenleaf kernel... anybody else have that problem?
[Optimus One, P500 Android Development] terratrix:
Not here....what rom are you using?
[Optimus One, P500 Android Development] vikasb32:
i am using stock rom 2.3 can i use this kernel plz help me
[Optimus One, P500 Android Development] franciscofranco:
No........
[Optimus One, P500 Android Development] deetailed:
Go and read the first post carefully, especially the Remember: part.
[Optimus One, P500 Android Development] ert69:
Im using miks cm7 6.5.7
[Optimus One, P500 Android Development] fserve:
Test the new v18b2.

Sent from my ASUS Transformer TF101
[Optimus One, P500 Android Development] orsonbear:
Fserve, I don't understand where exactly is the culprit (governor, buffer management, task scheduler or ?). I have changed kernel (gbs 15 17 18 a b...) but the problem persists.

Seems more present in latest 18b2 testing version but in all the other versions is present too, randomly in frequency and duration.

BTW I have flashed the "good old" FK 16.1 CFS and the problem is absent at all (smartass), at this point surely the ROM is not related with the camera lag and the culprit is the kernel.

More testing coming... sooner or later!

ROM by Mik CM7.1 6.5.7, Kernel... dependent by wind, rain and monsoon, highly GBS influenced :eek:
[Optimus One, P500 Android Development] fserve:
Test the newest goldenleaf, please :-)

Sent from my ASUS Transformer TF101
[Optimus One, P500 Android Development] orsonbear:
Test camera's random lag under Goldenleaf 100919

Camera works without lags (smartass). It shows strong flicker under InteractiveX, some faint flicker with other governors but SmartassV2 that don't shows any flicker at all.

With governors smartass minmax and other (except smartassV2, flickerless) it shows some faint flicker depending on the camera subject, if it's a white area then the flicker appears suddenly and suddenly go away if the camera is moved to a slight darker area...

Cheers!

ROM by Mik CM7.1 6.5.7, Kernel... dependent by wind, rain and monsoon, highly GBS influenced :eek:

P.S. For flicker I mean a faint effect of black horizontal stripes (with the phone in horizontal or 16/9 wise position) moving from top to bottom. This stripes are not related with 50 or 60 Hz electric current lights and are unaffected by the apposite camera settings.

P.P.S. Post updated, see some posts forward
[Optimus One, P500 Android Development] samcad:
Using v18b2 its charge very slowly ;(
[Optimus One, P500 Android Development] DaXmax:
It's fine to me...

TIPS- If u want fast charging, turn off the data,wifi,gps or whatever, turn ur brightness off... Ur charging will go faster in 2 mins instead 5 mins for 2%
[Optimus One, P500 Android Development] mDroidd:
Hi :) I also flashed the testing version, and:

-battery is awesome

-^^ when I use the phone.

-when screen turns off, drain.

I downloaded cpu spy and noticed that my phone can't go in 'deep sleep' anymore.

I am still happy with it, but for now,i am going back to stable..

Greets

mDroid

ROM: mik's 6.5.7

Kernel: franco gbs cfs
[Optimus One, P500 Android Development] franciscofranco:
Increase the minimum frequency to 480 - done.
[Optimus One, P500 Android Development] orsonbear:
Fserve, I don't understand, I don't have consistent results. Tried again now latest Goldenleaf, the flicker (the classic flicker with sudden unstable brightness changes) plus the stripes are presents also with SmartassV2 wich was flickerfree in the previous test session.

I'm baffled...

ROM by Mik CM7.1 6.5.7, Kernel... dependent by wind, rain and monsoon, highly GBS influenced :eek:
[Optimus One, P500 Android Development] mDroidd:
Ehh, already did that..

But back on 18a is good enough for me :)
[Optimus One, P500 Android Development] mDroidd:
Hi,i had the same problem, gps and wifi of didn't help.. Anyway, what did help,is go back to v18a ;)

No that's mean.. I think its just my phone being weird ;p
[Optimus One, P500 Android Development] fserve:
test other governors please.

Interactive and minmax.
[Optimus One, P500 Android Development] orsonbear:
Now I'm working and perhaps cannot test nothing but after done few other tests I suspect the faint moving stripes are generated by a faulty 50/60 Hz light source detection algorithm. I hope to do other tests soon, cheers!
[Optimus One, P500 Android Development] androidmeda:
Any word on the sensor bug? Except for the camera that comes with the ROM, all the rest don't stop using the sensor. I tried Camera360 and lgCamera with the same result.
[Optimus One, P500 Android Development] orsonbear:
I have tested further latest Goldenleaf achieving some results.

The camera's faint moving stripes are related with a light source AC powered as a light bulb or a neon tube or a CRT monitor or a fast LCD. The sync algorithm is messed up by overclock resulting in less precise light peaks detection then creating the faint moving stripes. More, in presence of two light sources with different frequency (a light bulb or neon and a PC monitor) the sync algorithm (or the CPU computational power) cannot lock the clashing light peaks generating always the damned stripes. With a DC powered light bulb or some electronic neon tubes generating a continuos light flow the stripes are absents.

Also, if the min clock frequency is setted too distant from the max clock frequency (e.g. 245/787) the algorithm struggle to sync lock and the stripes appears and disappears randomly. The governor has some influence on how quickly the stripes are neutralized and on the quality of this operation, e.g. minmax is way more fast and effective to get rid of stripes than smartassV2 (245/787).

Btw, (245/787 - 480/787) Smartass is affected by the "classic" camera flicker, minmax is unaffected, interactiveX is strongly affected. All this governors don't shows any camera lag or pause effect.

That's all, cheers!

ROM by Mik CM7.1 6.5.7, Kernel... depends on wind, rain and monsoon, highly GBS influenced :eek:
[Optimus One, P500 Android Development] deniso177:
Do you use a taskiller or or force close apps through the cyanogen long-press back key?

Because as i mentioned earlier in the thread, if you force close any apps that use sensors, eg. Camera, Google Maps, compass, speedx(accelerometer game), the game closes, but the sensor remains on, and that also shows up in your battery usage, even if you used the app for 1 sec and force closed it straight after.
[Optimus One, P500 Android Development] androidmeda:
I don't. It even shows the force close button when I check under Applications so I know I haven't forcefully terminated it. On another note, this one game acts the same way (Nano Panda). I think it has something to do with how the application/s are programmed to close. I'll try a few things later when I get out of work.
[Optimus One, P500 Android Development] mentalityx:
Finally decided to give this kernel a try. So glad that I did. Just have the camera flicker problem but the rest is A-ok. Luving this kernel. Thank you Fserve.

Now Im going to change my sig.
[Optimus One, P500 Android Development] fserve:
test v18b2 and check camera flicker

or set governor to min/max..

Or, remove that overclock :-)
[Optimus One, P500 Android Development] kapitanbasa:
now testing v18b2...minmax governor..480/710... no camera flicker here...though last nyt's bootloop may have been caused by some other thing. will report tom...

you rock fserve!
[Optimus One, P500 Android Development] terratrix:
I never had any flicker with 729 with any governors before the camera fix.
[Optimus One, P500 Android Development] kapitanbasa:
mine was pretty bugged up a month ago...with my stock camera app refusing to work no more.
[Optimus One, P500 Android Development] kapitanbasa:
so far this testing release is simply awesome...
[Optimus One, P500 Android Development] m4dbra1n:
So many thanks to you fserve!

Goldenleaf was a great battery improvement, but with the latest b2 and minmax governor, with only 2g, data, wifi and gps disabled, only 97% after more than 5 hours!

Well, I'm not one of those always-data-on-people, but even in these conditions for me it's a very great improvement from the old lg stock rom ;)

So fserve thanks again and keep on rockin'! :D
[Optimus One, P500 Android Development] fserve:
So, did v18b2 added any bug over v18a/v17?

or it is rock solid stable? =)

Sent from my ASUS Transformer TF101
[Optimus One, P500 Android Development] nd4spdbh:
fserve, again i wanted to say THANK YOU, your kernel is simply amazing.

Running Cyanommatt v1.1, with your GoldenLeaf 110919 kernel... with 480/729 smartass.... yeilds the results in the attached screen shot.

3 DAYS 8 HOURS w/ 11% left.... thats NUTZ.... thats with data enabled the entire time... somewhat light usage (untill the last part where i was browing the web in class... god its such a slow class)
[Optimus One, P500 Android Development] m4dbra1n:
Well fserve, for me seems to be as good as your old kernels, only sometimes I had black screen bug with the latest 18b2 and the old 18b testing: even changing frequencies and governor, it happened 3 times if I remember well. With the 18a and goldenleaf, even latest, I didn't have that. just for info, my cpu was set @ 480-748 MHz :)

@ next recharge I will try smartass governor instead of the smartassv2 that i was using days back; now I'm trying minmax, but when on seems to drain battery faster than smartassv2...

Anyway, your kernels are fantastic! ;)
[Optimus One, P500 Android Development] masteryx:
I couldn't find any bugs. This one is a keeper for me, just as v17 was. I can't perceive any difference between them, actually, except for the size. You still didn't tell me why v18b is slimmer... :)

So I call this stable.
[Optimus One, P500 Android Development] acax456:
Any updates fserve
[Optimus One, P500 Android Development] fserve:
nops =)

In v18 I removed more unused modules, thats why i asked if everything is working perfectly well.

Maybe it's your rom... try to clean cache and dalvik cache too...

blackscreen bug is gone! Minmax is doing good on my phone, but if you have too many apps open, your phone will remains always on "max".

Sent from my ASUS Transformer TF101
[Optimus One, P500 Android Development] Sephirothrx7:
So far so good using 18b2

The battery use is better then franco 19.4, using minmax governor.

LG Stock rom 2.2.2 + gbs 18b2

There is any bugs that needs to be tested on this rom?

Greetings from Brazil.
[Optimus One, P500 Android Development] Paulojrc:
V18b2 works great for me. No problems at all.
[Optimus One, P500 Android Development] Layio:
When I use lgCamera, and exit it with back button (app is closed) it still use sensor and I got no wakelocks, but in battery stats there is 70% lgCamera, and spare parts tell me that lgcamera use sensor everytime. Cm7 6.5.7.

How to fix this?
[Optimus One, P500 Android Development] kapitanbasa:
no noticeable bugs here.

ive noticed also dat lgcamera thing staying at the list stating that its still active...but betterbatterystats is not reporting wakelocks so i dont mind.
[Optimus One, P500 Android Development] deniso177:
If by back button you mean you force close it by holding the back button (enabling force close by long hold of back button in cyanogen), then do not force close any apps.

Force closing any app that uses sensors keeps the sensors running, even if the actual app doesnt run. There should be a pinned topic why force closing and task killers are bad on this devices development thread
[Optimus One, P500 Android Development] luckydog2006:
Hi fserve,

Is there any way to have a brightness manager/setting where when the phone is plugged in via USB, the brightness on the phone is at full brightness, but when it is unplugged (i.e. battery), the brightness is at a different lower level?

---------- Post added at 10:09 PM ---------- Previous post was at 09:57 PM ----------

Ok, forget it. I found the perfect small app that does this called "Full Brightness When Plugged" in Android Market! Finally. This was a pain the ass for me. IMO, this should be a default feature in CM7.
[Optimus One, P500 Android Development] androidmeda:
I think he just backs out of it until he gets to the home screen. Same issue here with any 3rd party camera.