yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500 Android Development] orsonbear:
Little infos about Qos

Qos is often used to assign some bandwith for VOIP communications or to other devices or data flows.

For example, if you use the phone to share internet to 2 PCs AND at the same time you want to use the phone's VOIP capabilities without stuttering or crap voice, you must set up Qos correctly to give priority to VOIP data flow over other devices sharing the same internet connection. Some devices may automatically set Qos to obtain priority over the other data flows, if you remove Qos support this cannot be done and, if the device is requesting bandwidth for VOIP, the voice's quality is awful & choppy.
[Optimus One, P500 Android Development] fserve:
Dont forget that qos isnt automatic to start working and has some cpu load overhead.

A non configurated router, a linux or windows box or even any other android around, uses fifo.
[Optimus One, P500 Android Development] kyerie030:
thank you so much for the quick replies to my inquiries guys. hope others could read this to be able to understand what you did to the kernel better. :-)
[Optimus One, P500 Android Development] terratrix:
No, so don't care about it.

Sent from my LG-P500
[Optimus One, P500 Android Development] fernando1sg:
i've been using ungaze since a long time with franco's kernel and this one, i flashed gbv15 and i didn't have such problem..
[Optimus One, P500 Android Development] DaXmax:
Flash it! It will give double the ram and boost! :rolleyes:

Sent from LGE XDA phone
[Optimus One, P500 Android Development] -Arturo-:
Hmm fserve I think your kernel beaks compatibility with Darktremor's a2sd. I just cannot make it work with ext4 partition.
[Optimus One, P500 Android Development] fserve:
No, it's not a need. I dont use it.

zram: generic RAM based compressed R/W block devices

Creates RAM based block devices: /dev/zramX (X = 0, 1, ...).

Pages written to these disks are compressed and stored in memory

itself. These disks allow very fast I/O and compression provides

good amounts of memory savings.

This is enhancement over existing ramzswap driver which creates

virtual block devices (/dev/ramzswapX) which could be used only

as swap disks.

Now, with the ability to handle any kind of I/O request, zram

devices have lot more use cases:

- /tmp storage

- various caches under /var

- swap disks (our case)

- maybe even more! :)

http://lwn.net/Articles/388889/

Just to confirm, are you using ext4?
[Optimus One, P500 Android Development] terratrix:
@fserve

net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960

Are these already in the kernel?
[Optimus One, P500 Android Development] fserve:
ppl, i've made one more testing version..

this one... is very different

i've started from scratch, and added up some franco updates.

plz, test EVERY ****

BATTERY, usb-transfer speed, gps, camera, charging with phone off, and if one bug occurs plz, reset to 600MHz your clock,

only if the bug persists

, report.

oh yeah, to overclock you will need nofrills, or something like that. i'm too noob to know how in the **** that cyanogen overclock works :/

ONLY CFS for now cos i didnt got the bfs code.

http://www.megaupload.com/?d=R7DPR273
[Optimus One, P500 Android Development] killer_jazz:
So zram act like swap and compcache?
[Optimus One, P500 Android Development] DaXmax:
.46 kernel??:rolleyes::rolleyes::rolleyes:
[Optimus One, P500 Android Development] DaXmax:
Ok i tested it... No bugs, SMARTASSV2! :eek: And why the kernel is downgraded? 2.6.32.9??

Sent from LGE XDA phone
[Optimus One, P500 Android Development] terratrix:
I think he used the stock LG froyo 2.2.2 kernel

Sent from my LG-P500
[Optimus One, P500 Android Development] DaXmax:
It must be... But why?

Sent from LGE XDA phone
[Optimus One, P500 Android Development] terratrix:
Maybe its just a testing. Or he doesn't know how to update sources which i don't think so

Sent from my LG-P500
[Optimus One, P500 Android Development] DaXmax:
He did say that he dunt have bfs code right?

Sent from LGE XDA phone
[Optimus One, P500 Android Development] terratrix:
Ya...u didn't read the post

Sent from my LG-P500
[Optimus One, P500 Android Development] orsonbear:
Gotcha! A bug!

Testing the new kernel. The no power off (or permanent power on) on charge bug is gone! But when I plug in the charger and the phone is off, it shows the big battery charging and when the screen go black it's impossible to turn on the phone. Only after removing battery is possible turn on it!

Now I go to sleep, I can test more stuff later or tomorrow. Cheers!

Devoid Froyo Final, clock 480/787 smartass (test executed also at 245/600)
[Optimus One, P500 Android Development] fserve:
Hmmm, ****, it's hard to know that stuff without void or devoid roms. I'm going to void.#forever to test this stuff on my phone.
[Optimus One, P500 Android Development] DaXmax:
No plans to .46??

Edit: Btw, ur gbsv15 is smoother than gbsv16 but maybe cuz im using bfs... I dunno... But btw, great works...

Sent from LGE XDA phone
[Optimus One, P500 Android Development] orsonbear:
to Fserve...

Wait... I have gazillions of ROM and now test this with my mik 6.5.7 backup...

few minutes... I report the results soon below in this post...

Update:

Nope. Sadly the phone won't shut off when charging battery with mik's 6.5.7, it makes a reboot... sorry!
[Optimus One, P500 Android Development] fserve:
I'm trying to fix bugs first. if you want speed, wait for the new franco.Kernel that will be good release.

void.#forever doesnt have that charge while off thing...

going to devoid froyo final :|
[Optimus One, P500 Android Development] DaXmax:
Lol, im stubborn, i will wait for urs...

Sent from LGE XDA phone
[Optimus One, P500 Android Development] orsonbear:
The forced switched ON phone during battery charge happens since FrancoKernel V17, in V16.1 and previous versions the charging phone can be switched off. I have tried this on many roms, CM7 or Froyo, I think someting broken or lost (forever?) moving from V16 to V17... what a pity!

Errata: I have tried FK V16.1 on mik's 6.5.7 and when I charge the phone this turns power ON and cannot be switched OFF. On Froyo (devoid or stock) you can switch off the charging phone (with FK V16.1).
[Optimus One, P500 Android Development] franciscofranco:
I still don't understand what the **** is that bug about to be honest.
[Optimus One, P500 Android Development] fserve:
That **** is a bug in .config i will track it down.

I´m using devoid.#froyo-final (btw, that is a very good rom!) and i've made a kernel that everything works (no usb problem, no charge problem). But it's not optimized yet.

More good news to come soon, i hope ;-)
[Optimus One, P500 Android Development] biggio:
hmm, connecting with USB/AC charger, the stock LG rom will not be on when the battery is below 5%.

I believed the purpose is to get more battery when booting.

In case the charge current (USB) is too small for booting. I got some case that couldn't boot from empty battery when charging with limited USB current.

In other hand, the charge current is enough for booting when connecting with travel charger (AC Mode).
[Optimus One, P500 Android Development] Shofire91:
Well, I got bored this weekend....

So I did a complete wipe and reinstall of everything, and put on Darktremor's apps2SD for the full package. All the specs of my current running setup are in my signature as usual including benchmark scores. Vsync really seems to bring them down, but I'm willing to make the sacrifice.

Once again, solid as a rock. I've got v15 BFS is running like a charm, I was having a few stability issues when I flashed the kernel downloaded from here to my phone with 50 percent battery a few days ago. I just couldn't wait to get home to my laptop to download and charge it before flashing :p.

Will report any major bugs as I find them. So far, zilcho.
[Optimus One, P500 Android Development] fserve:
Another testing release.

That one i've tested for a good time, so i think that it is pretty good.

That release is a special test to make a good kernel with good battery life, overclock support, multitouch fix. I'm starting from the original LG Kernel to make sure that all things works.

news in this testing release:

cyanogen overclock support, thanks Francisco Franco :-)

USB-transfer is pretty damn fast :-)

Recharging with phone off is ok now.

Use this release

ONLY

if you want to help me (to find bugs) OR if you have problems with slow usb transfer/recharing with phone off.

http://www.multiupload.com/B9DCAVC25U

Ps. I know that this kernel is SLOWER than gbs.v15 or francisco.franco v19.4.

At the moment, speed isn't the point here, and it is CFS.
[Optimus One, P500 Android Development] orsonbear:
Latest test Kernel LG-Original-gbs.v16

Devoid Froyo Final, 245/787 480/787 smartass

I can confirm power on when charging bug is gone! I can power on/off the charging phone...

WIFI works, BT exchange data works (I haven't a BT earpiece), camera works in all its features, GPS works. All the most important phone features are working. At least those I have tested :)

CM7.1 6.5.7 by mik_os, Ungaze data2sd, same clock and governor as above

Phone works normally, (WIFI, BT data, camera, GPS...) but it can't be turned off when charging...
[Optimus One, P500 Android Development] harshdoshi25:
wuuhooo !! im a very recent fan of urs ! changes to the best kernel ever to make it even better !?!? woah ! :D and hey have u tried any OOM grouping fixes ? they make great differences ! defeats the use of task killers ! :P lol ! ive tried v6 supercharger and its pretty darn amazing ! :)
[Optimus One, P500 Android Development] signumized:
Thank you for releasing another version (based on LG original).

Apart from the fact that the USB speed / access time has improved, also the file transfer on SD card has improved.

Tested earlier this version versus franco's 19.4, using Total Commander for Android.

When copying a large file (the same one) from one folder of the SD card to another:

- with franco's kernel, very slow transfer speed; the transfer hangs a lot.

- with fserve's kernel (LG original), transfer speed is normal, without hiccups.

Anybody could do this test on their phone, just by transferring a large file (for example mik's rom file - zip - ~90MB) between phone's folders.

Maybe this could help also for future development, as the internally speed is affected by this.
[Optimus One, P500 Android Development] logo_32:
I'm sure all of the devs would be proud to see this :) finally making a kernel of your own :) I'm downloading it now and flash it tomorrow as soon as I'm done reviewing Francos latest release :)

Cheers to another optimus champion :)

Sent from devoid using my own hands :)
[Optimus One, P500 Android Development] fserve:
I think that all cyanogen based roms (for p500) have that thing to auto power-on when charger is connected...

=)

Sooooooo, that kernel is bug free? :-)

I've tested the battery life and i've got 3% down in 6h of sleep..., very, very good!
[Optimus One, P500 Android Development] luckydog2006:
I see people keep mentioning sleep only costs them x% in battery for y-hours etc. What is sleep mode? Is there a setting for sleep profile? Or does it just mean that the phone is powered down? or just in switched off where the screen is powered OFF?
[Optimus One, P500 Android Development] Shofire91:
Okay, so this kernel seems to try to burn the lockscreen image into my LCD!

Happened before a full wipe and reinstall, and it is still happening again after I did it. If I turn off the LCD with my power button and leave it for 10 min it tries to burn the last image it was at when I turned it off. I can clear my LCD by shutting down the phone for a couple minutes. It's gotta be only turning of the backlight LED and leaving the LCD on, I've gone through 20% of battery life in a couple hours, and it was all standby.

14f did not do this, nor did francokernel 19.3. Everything else has been the same except for apps2sd I recently installed, and it did this before apps2SD.
[Optimus One, P500 Android Development] gkarthik16:
Sleep is when the phone's screen is turned off and no background apps running. Idle mode, in other words. In apps like SetCPU, you can set a sleep profile, so that the phone will be clocked at a lower CPU frequency, than the maximum frequency you've set. Suppose you set 748/480 in SetCPU and if you set a sleep profile as 320/122, then the phone will be clocking 320 when in idle mode.

If you use smartass CPU governer, there is no need to set a sleep profile. It by default sleeps at a lower clock.
[Optimus One, P500 Android Development] gkarthik16:
Yup, I read the same thing somewhere. Mik removed the charge-while-off feature AFAIK. It always switches ON. Not sure why does this bother people.

[EDIT]: Using your kernel for a couple of days. Solid as a rock :D Great job.
[Optimus One, P500 Android Development] fserve:
Never had this problem, never seen no one talking about it...

So, i think this it's not a kernel problem. :-)
[Optimus One, P500 Android Development] Shofire91:
I thought it couldn't be your kernel at first either, but I literally have no other explanation for it. Been through my phone 3 times now trying to get rid of it. Nothing seems to get rid of it, cleared battery stats, data, cache, etc. Nothing has gotten rid of the problem. It can't even be any apps doing it, I am sure of it. No CM7 settings yield anything either.

Is v15 bfs got any changes to an LCD timer at all? It's 100% leaving the LCD on after the screen is off. Just keeps burning the image into my LCD. I've only had this issue with v15 bfs.
[Optimus One, P500 Android Development] fserve:
V15 doesnt change nothing with LCD...

Unless more people confirms it, is your phone problem and not kernel.
[Optimus One, P500 Android Development] logo_32:
fserve.kernel.v16 ... TEST RIDE..!!

Im done reviewing v19.4..!! And boy it was one hell of a ride..!! What an amazing kernel.. No wonder franco is a legend kernel developer..!! (And you too will be one in a really short time.. :D)

Ive flashed your v16 and going off to sleep..!! This way the first thing to be tested would be the idle battery usage.. :D Will report soon.. if any bugs found..!!

Cheers to you man..

Good night..!!
[Optimus One, P500 Android Development] masteryx:
I'm going to stick with v15

fserve, as I promised, I'm back with feedback about v15. After all, I am kind of responsible for its creation, since it was your response at my request of bringing back IPv6 support. Which I now see franco also did for his kernel.

The reason for the delay is... well... the excellent battery life of this kernel. I had to let it run dry for a couple of times before reporting and this took longer than I thought :D

As far as I can tell, everything is fine. I didn't test every possible feature - like using my phone as a wireless hotspot, but so far, for daily normal use - it's great.

There's only one minor annoyance that keeps me from being completely happy with my phone. I think it's called "the axis inversion bug" and for me it takes the form of a sudden skip to the end of the page while scrolling. Let me emphasize that this might be not kernel related, because I always experienced it on Froyo but not on mik_os' CyanogenMod. So I'm not pointing this out as a bug for you to solve, rather as a "hey guys, if you use fserve's kernel with Android 2.2.x, this is my experience with it".

Care for some statistics? Well, trying to be as accurate and impartial as I can, here goes: I am now at 9%, after 2 days and 10 hours. In this time frame I had my phone in 3G mode for roughly 6 hours (whenever I left home). In the rest of the time, it was in 2G mode with WiFi enabled. 7% of the battery went in phone calls (~ 1 hour). The longest battery drop occured when I read news for 2 hours straight: 26%. The longest period of time without the battery dropping a single percent: 5 hours! It took 5 hours to go from 20% to 19%. I also watched a couple of YouTube videos and listened to some music using the speaker. All in all, without that news reading marathon, I could have get 3 days of battery life without even breaking a sweat.

I am going to stick with this combination for a while, for sure.

Thank you, franco. Thank you, fserve.
[Optimus One, P500 Android Development] 32bit:
The "Original v.16" seems to bee the bug-free. Sleep-charging bug was gone (oh, yes! You did it!),

momentary-see-the-screen-after-unblock bug was gone too.

So far, so good.

Thank You very much!
[Optimus One, P500 Android Development] Shofire91:
Well shoot, I guess it really is my phone. What in the heck could be causing something like that? Ugh, no matter...

I'm going to KDZ flash it back to OEM spec and start over with the whole process of installing all the mods.

Been hearing good things about franco's 19.4 as well, gonna try his new release out and see if the problem pops back up.

You're kernel's still awesome though :cool:.
[Optimus One, P500 Android Development] kapitanbasa:
Im back to gbsv15bfs...ystday i flashed franco's v19.4...batt was nice, responsiveness superb. But, my sd card seemed to have random unmounts...
[Optimus One, P500 Android Development] terratrix:
The title should be 4 SEPT not SET :P

Sent from my LG-P500
[Optimus One, P500 Android Development] fserve:
Thanks :)
[Optimus One, P500 Android Development] fserve:
Does someone knows any differences between:

g++ code sourcery 4.5.2

android toolchain eabi linaro 4.5

android toolchain eabi linaro 4.6

original gcc

I know that franco got a random bug when using gcc (one or another user got random panics
[Optimus One, P500 Android Development] modifii:
Even I am facing same lock screen burning issue but battery performance is fine on my phone. I closely looked into LCD when in sleep mode, it remains off (LCD & Backlit both off). Using Mik's 6.5.7 with gbs v15-cfs. Never had this issue before in any kernel.
[Optimus One, P500 Android Development] franciscofranco:
g++ code sourcery 4.5.2 -> Better than CM's toolchain, optimized gcc for arm

android toolchain eabi linaro 4.5 -> mostly the same as code sourceries

android toolchain eabi linaro 4.6 -> newer code than code sourceries, might break something. It caused some strange bugs in one kernel that I released

original gcc -> just normal gcc
[Optimus One, P500 Android Development] fserve:
i really didnt understand what this bug is...
[Optimus One, P500 Android Development] Shofire91:
Personally, this is how it happened for me. Screen shuts off and goes into lock mode either by the timer or by hitting the power button. I let my phone sit around for a while. I hear a message notification at some point and unlock my phone, only to find I can still see the lock screen while on my home screen(or any screen for that matter) burned into the LCD. Same thing happens if you leave your computer monitor on for a long time at the same screen. It's a silhouette of whatever the screen displayed when it originally went into lock mode. It sticks around for a while. I usually end up shutting off my phone for 10 min to let the LCD cool down and the burn image dissapear, then start it up again. Only to find though that the LCD burns the lockscreen image into itself again and again.

Not sure either, but I am currently running francokernel v19.4 CFS and the LCD burning issue is nonexistent. Could have been that I cleared everything and started over today when I did the KDZ flash got it out of there. But I doubt it, it only happened when I flashed v15 BFS, I never got it with any other kernel setup I have ever tried, and I've gone through at least 5 since I started flashing my P500h.

Seems to only do it with some phones I guess. I wonder if anyone with v16 of your francokernel is having the same problem?

Anyone with the LCD screen burning problem please speak up for Fserve and help him find the bug!
[Optimus One, P500 Android Development] modifii:
I am now on Testing version v16 and not yet noticed lock screen burning issue. But I can confirm this only by tomorrow morning.
[Optimus One, P500 Android Development] terratrix:
Dunno why but LG stock froyo 2

2.2 kernel gives good battery even without any modifications

Sent from my LG-P500
[Optimus One, P500 Android Development] fserve:
I've made a stock froyo kernel with very few changes. it's the kernel with more battery life that i ever seen. :-) check on the first page my new testing one.
[Optimus One, P500 Android Development] fserve:
Very strange issue. If i had that i could notice.

You had it since the first day using v15?
[Optimus One, P500 Android Development] Shofire91:
Pretty much, it seems to take a couple hours for the problem to start after flashing.
[Optimus One, P500 Android Development] orsonbear:
I'm testing latest v16 on mik's CM7.1 6.5.7, 480/787 smartass, no a2sd or other scripts.

I have noticed the default governor is conservative, I choose smartass instead. Conservative makes longest battery life but a sluggish phone!

Btw, when I awake the phone pressing a key, too often it lags a random time extended till 2-3 seconds before the unlock screen comes on, I have to press a key and suddenly tap on screen to see immediately the unlock screen. Apart this all runs fine, at least seems to me!
[Optimus One, P500 Android Development] kamalnath:
Hi fserve,i found a problem in ur testing release,the blackscreen bug appears only wen i select normal wallpaper,if i select live wallpaper blackscreen bug goes away........:)

edit:it also appers wen u make a call,mainly when proximity sensor is functioning.......:)
[Optimus One, P500 Android Development] lerkin:
Same LCD problem here. Except that no other bugs. Thank you for your work. Finally we have full-speed sd transfer. It's the main advantage over other kernels. And I believe battery life is better to. I think it was great idea to start your kernel project from the scratch. Your new kernel rocks.
[Optimus One, P500 Android Development] terratrix:
Fserve i suggest you put smartass2 as default governor or put scary or ondemandX instead of conservative

Sent from my LG-P500
[Optimus One, P500 Android Development] deetailed:
Tried v16 with CyanogenMMatt v1.1, S2E, smartassv2. All functions seem to be working (phone, data, BT, GPS), except tethering which I didn't try cos I never use. Can't charge while off, still.

Benchmark results:

at 600 MHz: Antutu 1645, Quadrant 1182, Neocore 53.1 fps

at 787 MHz: Antutu 1946, Quadrant 1496, Neocore 60.9 fps

Angry Birds test :D - no lag

I don't feel noticeable difference in performance actually, compared to v15 or fk 19.4

Battery life, we'll see.
[Optimus One, P500 Android Development] ashishv:
Well fserve u forgot to add media button fix in your testing version.
[Optimus One, P500 Android Development] fserve:
What is that?
[Optimus One, P500 Android Development] franciscofranco:
LG's headset **** media button, I had everyone crying at me to fix that for months, I suggest you merge the fix asap to prevent further crying :D
[Optimus One, P500 Android Development] ashishv:
Thanx for the explaination.And i wasnt crying.:confused:
[Optimus One, P500 Android Development] fserve:
wtf? This comes broken in original kernel?

i need 2 phones :/
[Optimus One, P500 Android Development] franciscofranco:
Broken for cm7 yeah.
[Optimus One, P500 Android Development] 32bit:
fserve, I want to say thank You for your work! Your v.16 is perfect with my 2.2.custom.Froyo. All things are working as it should to be. Way faster than original and stable as rock.
[Optimus One, P500 Android Development] fserve:
Thanks, i'm trying to make a new version with the media button fix :-)
[Optimus One, P500 Android Development] holymolys:
i havnt tried the v16 yet, but i just want to comment on the amazing battery life i get out of my phone with v15... still 1/3 left after 2 days of use

I keep my wifi on at all times for gmail/gtalk, and have recently moved my sim card to my backup phone and use google voice exclusively on this one