yashsingh1/xdaforums huggingface dataset:
[LG Optimus 2x] calav3ra_de:
@Pengus77

I really like the idea of having user-configurable oc of other components. I think pidocchio said one day that he removed it completely because it made problems for some people. This would explain the post not so long ago here where the guy reported he has no OC and UV active, but still got BSODs, but GPU-OC was hardcoded, as you said. So perhaps making it dynamic and don't activating it as default may get rid of all BSOD reports here.

Btw guys, for UV: Since my phone is in 216 MHz mode very often, i focused on UV there first. I went down to 600mV - rocksolid stable :P

I got many states where i went down by ~100-125mV, just saying. Which brings me to another point: Pidocchio limited UV in his kernel internally, so telling an app to go -125mV may still stop somewhere, allowing -50mV at maximum for one state (this is just an example). On the other hand, i receive freezes on some voltages with the 816 MHz mode, so i know UV is working. So i'd recommend you to try out all values.

This kernel is godly :B I only want automatic brightness now to finally work in CM and vibration strength regulator, so i can try if some values work better than others, or save some battery with lower values perhaps (prolly not working, since vibration is already relatively weak, compared to samsung devices like galaxy ace).
[LG Optimus 2x] Ximo F. Verde:
Hi Pengus.. Just trying to understand exactly what are the differences between the 100p1 and the latest nightly. I have read both change logs but would like to verify with you if thats no biggy. I understand that light OC on 2d/3d (and epp/vde which i dont know what they are) has been removed. In order to solve the bsods/sods some users have had, did you raise the OC freqs voltages, and if yes by how much? If i understand correctly, on 100p1 u had UV on OC in order to maintain same battery drain as non-OC. If (all) this is the case, could you (if not done already without me noticing) provide us with a clear freq/V table showing the differences between 100p1, nightly and stock/earlier kernel versions. I just moved to PA a couple of days ago and its been increasingly difficult to follow up all changes/updates in both ROM/Kernel, so bear with me on this. Just on a personal note, I found 100p1 to be v stable (apart from some light graphics glitches - some sort of fps drops in animations and sometimes browser scrolling) but I've seen some really dreadful battery drains while on use - Browsing on 3G I've had a 4% drop in 3mins (!) (with location settings turned off btw)

Thanx for ur time n effort
[LG Optimus 2x] calav3ra_de:
Well yes, i also think that batterydrain increased with 100p1, probably due to GPU-OC? I dont OC the cpu really, just lots of UV going on.

I also agree that it is not very easy to follow all changes right now, but it's ok as i read all posts :)
[LG Optimus 2x] tonyp:
Re: [KERNEL][CM10/CM10.1][100p1 - 2013/02/13] Kowalski Kernel - Now With Nightlies !

UV won't get lower than 750mV iirc.

you can set it lower of course, but pengus introduced some safety ranges so it won't change for real . ;)

With the new kernel the bsods are hopefully dealt with.

None of the guys with early access to the OC kernel had problems with the default UV it included.

Thus we assumed it's safe to use with these default settings, but once again we didn't take LGs build quality into account ;)

So from now on everything is back on stock values.

Of course bsods can still happen if people are trying uv, but they will hopefully realize the cause then.

If there will still be bsod reports with the new nightly it will probably result in two separate kernels - but let's hope there's no need for it.

The newest nightly uses stock freqs for CPU and GPU.

It's definitely recommend to update to it, as the GPU OC of the previous versions could cause pretty much the opposite: a GPU throttling.
[LG Optimus 2x] my_dnl:
@tonyp

Not exactly...

I'm with your latest PA b06 newBL + latest kk_exp_20130215-101 with default settings (no OC, no UV)and today I got 2 BSOD.

last_kmsg attached above (but show no errors)
[LG Optimus 2x] pengus77:
Ok here goes: the new nightly reverted all the uV changes i tested (and that are rock solid on my device) and set them to stock values for the default frequencies and a bit higher for the top-end ones. Of course you can uV them if your device handles it, but i wanted to give a stock system that works on most phones without problems even without uV. About the dynamic OC of 2d/3d, i'm on it and it will find its way in one of the next nightlies for public testing. The main reason i decided to bring out nightlies is to shorten the amount of changes in each release and have a clearer view of what could cause problems... so instead of pushing a 20 lines change log every week, i went for pushing a 2/3 lines one every couple of days. This will surely have a faster bugs discovery process and it'll be much easier for me to record your feedback and revert one or two commits to get back to a stable system.

About battery drain, i can't really say it's higher or lower... for me it's pretty much the same as before. Since yesterday i'm using a "screen-off" profile in CPU Adjuster that sets governor to conservative and max frequency to 600MHz and in 9 hours my phone lost about 12% with wifi and sync always on. I guess this could help all of you ;)

About vibrator control, it's already planned. First stability for all, then features :)

The hardcoded OC of low level hardware is something i won't introduce anymore, while i will focus more on giving you the power to decide if you want to test a higher voltage/frequency for ram, 2d, 3d, system bus, etc. But one thing is really bugging me, i need to know a pretty realistic % of users that are on my kernel without problems compared to those who have problems, otherwise i can't decide how to go on. I know this is unrealistic and pretty much impossible as most users don't have enough posts to comment here, or they're shy, or they just don't do that for whatever reason, but it's really something i need to know. I know for sure that more than 2k people are on 100p1 and/or nightlies by looking at the downloads from my folder, but i need some more consistent figures. Help me out on this, or we will never hit the bottom of the problems :)
[LG Optimus 2x] jabooka:
Max and current CPU speed

Is there sth wrong with my readings regarding cpu speed? In settings-performance-processor there is max CPU freq set to 1200 (default setting with latest nightly kk-exp-20130215-101-oldbl), also same value is displayed in CPU Adjuster. In current CPU speed in both settings and CPU Adjuster app it shows 1000 as max current freq all the time no mather what i do. And in CPU spy it is registering time spent on 1100 and 1200MHz. Glitch in reading of cpu freq or app problem or sth else? Other than that, latest nightly running really smoothly on my 2x :highfive:
[LG Optimus 2x] Ximo F. Verde:
Thanks for the details Pengus. I guess that the best way of finding out would be a poll, wouldnt it? Maybe a bit more elaborrated than '2 options: it crashes or it doesnt' in a way im sure you could think of and present.
[LG Optimus 2x] imayoda81:
I've OCed my phone and my tv set froze.. i can't see any more tv and this makes me angry.. please revert OC :D

Sometimes I belive most lockups are user related.. agressive updating roms without factory reset, changing parameters Vm related, installing backups that may contain even system files from old systems.. i've seen this all among my friends.

What I want to say is that it will be hard to understand who is getting problems becuase of OC and who's not.

Pengus opened Pandora's box :D
[LG Optimus 2x] pengus77:
You see hitting 1k often because it's the speed at which boostpulse operates. You can change it in CPU Adjuster in the interactive governor settings :)

Also, don't use settings -> performance -> cpu. It doesn't work.
[LG Optimus 2x] Ximo F. Verde:
b4 flashing the last nightly i made a screenshot of the fregs (from 1.2GHz to 760MHz - what fitted in the screen). By comparing them to the latest nightly it seems that there a +50mV bump in all frequencies (or at least in the range mentioned). If i want to use the UV values of 100p1, would i just have to go -50mV in all frequencies or are there some that remained unchanged or that had different scaling? Thanx and sry for insisting so much :)
[LG Optimus 2x] jabooka:
Will look into that setting in CPU Adjuster...and I don't use settings -> performance -> cpu, but remembered that there you can also see current cpu speed...or at least I thought it worked...thx for clarification :highfive:
[LG Optimus 2x] lucfig:
Re: [KERNEL][CM10/CM10.1][100p1 - 2013/02/13] Kowalski Kernel - Now With Nightlies !

Using latest PA 06 with both 100p1 and today's nightly kernel (kk-exp-20130215-101-newbl) I had no issues.

I don't undervolt and that is the main reason I installed the nightly, clock always set to 1ghz or 1.2.

Everything rock solid for me.

Enviado de meu LG-P990 usando o Tapatalk 2
[LG Optimus 2x] calav3ra_de:
Default bump is 1.0 GHz ? I have troubles understanding the values about durations, for example default duration of boost seems to be 20000, what is this? milliseconds?
[LG Optimus 2x] pengus77:
Yep exactly, it's in ms and i set it to 200 to give a slightly better feeling of speed. Interactive default is 80ms... anyway in there you can change the speed at which the cpu will boost when you touch the screen. Default is set @1GHz so that people with borked phones won't have freezes due to the boostpulse :)
[LG Optimus 2x] chp2:
Hi pengus,

So far, so good. :good:

I own one of these incredibly good device wich allow me to OC alot without bumping voltages too high an even lower them when on standard frequencies. I think I'll never be able to thank you enough for your incredible job allowing my device to be rock solid since days without any FC / reboots or whatever (except if it was my own fault)

When reading all the posts since you provided the 100series of the kernel, I'm almost sure that we face different versions of our beloved device.

Not all are born with the same components (that's sure) and not all came from the same fab.... more or less I think we face different internal devices under the same reference (P990).

What could be interresting is to differenciate them and for that I think you're able to help us to check.

Can you help us how to catch the right info to differenciate these devices?

Another thing : I'm really impressed by your drain numbers and even if I have a good device I'm far to reach them. perhaps it's ROM related and I'm asking wich ROM are you using to obtain these numbers?
[LG Optimus 2x] tr@p:
One question about CPU adjuster app, maybe it's bit offtopic, but here are a lots of comments about app. I've set 'Default profile' and activated it... and set one 'Screen is off' profile and activated it... will this screen off profile be in use when screen is off, or default one? Do I need convert 'Default profile' to 'Screen is on' then?
[LG Optimus 2x] pengus77:
Nope, the default is sort of "for any other situation aside the ones you created profiles for" :D

So just create the screen-off one and in the default put your standard values :)
[LG Optimus 2x] PirateNL:
Hey Pengus,

Would you suggest updating the kernel to the nightly builds or are they just for testing purposes?
[LG Optimus 2x] pengus77:
Well, yeah, they're not only for testing... i also add features and fixes in there. It's just that i push them more often now, so you can get a faster fix if you're a flash-a-holic or if you find some bugs :D
[LG Optimus 2x] calav3ra_de:
I request feature for setting zram size to userdefinable value. For example, in CM i am forced to three settings, max 26%. I want to try other values, for example many between around 35-70% :) Because i really think, CPU impact with Snappy Compression shouldn't be that high, and more zram means more ram for apps. Or did i overlook the possibility to do this already in an init.d script?

I also ask for information about backlight notification: Is it true that it can theoretically stay on always without draining lots of battery? Also, i'd like to request more slow notification, it is a bit annoying being so fast. I'd like to have custom control over this. I want to know if we can use this app here or wil lit interfere with "kernel settings" ?! https://play.google.com/store/apps/details?id=com.martinborjesson.o2xtouchlednotifications
[LG Optimus 2x] aigaming:
Dear Pengus,poll for testing oc stability on our phones would be good;)

I personally think that the first version was stable for the majority of people(out of box) and only people with "low oc batches" had problems with that version.

I use 1.2mhz oc like i said with slight undervolt and my phone(like yours) is rock solid and i don't notice any more drain then previous versions(in contrary i feel battery lasting longer duo to uv)

Tnx for this wonderfull kernel

I verry much like the fact that our phone can compete with all dual core ones on market couse of your blazing kernel...

This was the first dual core cpu in the world and still working like charm after many yrs;) (this is for all haters that wanted 2 sold and sold o2x duo to bad lg support,slowness,bug's etc) ♥

Do i need to buy new phone(No),do all my friends want 2 buy my o2x after seeing smothness and perfomance(hell Yes) :cool:
[LG Optimus 2x] imayoda81:
too much zram will kill phone performances.. better make a swapfile in sd o swap partition plus the existent cm zram options (they are that way because they know why) :)
[LG Optimus 2x] calav3ra_de:
They are there with traditional zram compression. We have less compression rate but faster one. So i really like to try. I don't think it will be slow with 50%. I ask this because i need just two more apps stay ram that i use daily and they get thrown out soon.

About sd-swap - isn't it horribly slow? I got a speedy sandisk (class 10, ultra), but some random r/w values are not good and moving apps to it on my galaxy ace totally killed performance of those apps. (Also thinking about it: You get max read of 30mb/s, what is when the gallery app is residing in swap, so on the sd, and now it wants to load all pictures - will probably be superslow, no? Internal memory is soo fast, and cpu even faster) That's why i'm not trusting sd-swap. Comparing them would be even better, right?
[LG Optimus 2x] pengus77:
I'd rather add an option to the manager to create a zram block aligned with ram blocks (32/64/96/128) instead of random % values. It's going to be much faster and way less laggy ;)

Anyway i think i just reached a decision and i would like to hear what you think about it:

1) I'll remove OC from the release kernel

2) I'll keep OC and add features on the exp kernel

3) The release kernel will contain stable features cherry picked from the exp branch and unrelated to OC

How's that ? Who wants cool stuff uses the exp (which is btw stable most of the time) and can help out in testing bleeding edge features. This will also assure me that who's on exp also has a superstable phone (because it's not crashing with a slight OC) and testing will be so much easier then, avoiding me to worry less about what caused a problem and focus more on bugfixing.

This also means that the release branch will lag a bit behind in terms of features, but will be rock solid.
[LG Optimus 2x] Diskb0x:
@Pengus77 - Is it worth opening a quick poll in a weeks time? By then most people will have upgraded (hopefully) to the latest version and have used it for a few days. After you have collected the results, delete the poll and re-create again when needed.
[LG Optimus 2x] aigaming:
Totally fine with me,i know i will go for exp version allready;) (better to have 2 options then forced one) :good:
[LG Optimus 2x] pengus77:
I can't delete polls... only mods can do that, that's why i'm a bit skeptic about it. And trolls love to alter the results too...

I'd rather opening up a google docs spreadsheet and ask username and result.
[LG Optimus 2x] Diskb0x:
Sounds like a good approach to me.

Also to help you out going forward, how about adding a small feedback bit to your app, much like CM Mods do. If it's left ticked then the app reports back to you every so often with useful info. Some will untick it but I'd bet many will leave it as default so you get the info you need. Just a thought.....
[LG Optimus 2x] Medizinmann:
How about Antutu CPU master?
[LG Optimus 2x] pengus77:
Not good either. They all set speed for one core only...
[LG Optimus 2x] Rayman96:
Odp: [KERNEL][CM10/CM10.1][100p1 - 2013/02/13] Kowalski Kernel - Now With Nightlies !

what's wrong with OC?

even bad phones love your OC pengus, so it can stay as it is :)

at least 1.2 is fine :)

Sent from LG 2X using Tapatalk 3 Beta
[LG Optimus 2x] DrummerMuppet:
I also agree, pengus. OC isn't that much of a critical feature to have on our 2X since it works perfectly fine without that, so it won't be madly missed by most of us (except hardcore gamers maybe, and benchmark freaks).
[LG Optimus 2x] kaioder:
In my case the exp kernel with OC and stock voltages is working great until now, despite that I would prefer to test it more. With OC+UV I was getting to much bsods. I would like the OC version without UV and decide by myself testing UV.
[LG Optimus 2x] Custom40:
As long as we remain posted on new exp kernels in the same fashion as the "official releases", then yes, its indeed a brilliant idea ;)

Note: You seem to be about right regarding the OC versions being stable at most phones. From both my own experience and from all the feedback, it seems that its a minor party who are having issues with OC versions.
[LG Optimus 2x] FoliathR:
Pengus, do you mean that the exp kernels will come with OC? I think it'll be better if you let those who want to OC to go ahead and do it, but there might be some people with OC-unhappy phones using the exp kernels. Just a little thought.

I'm getting smooth performance even @ 1.0Ghtz, and I think it's better to leave OC to the minority who need the power for gaming and such, who I believe are all more than capable to do it.

Other than that, I think it's fine.

I'm sure those with phones that are not so happy with OC would love to swap their phones with yours, please go contact them. =)
[LG Optimus 2x] pengus77:
I completely agree and, in fact, i want to wait a couple of days and see if the last exp kernel reduces the amount of problems people are having. It has indeed a bit higher voltages than stock by default, so it should be 100% safe to use. If they still will get bsods i'm almost ready to start blaming their apps more than their phones lol

About the exp kernels staying on OC, i do it more for a "public beta" system. I need a wide range of testers on different phones. Recent history demonstrated that sticking with 5 testers in a close circle causes problems. We can't test everything and, fortunately, all our phones are able to OC (a lot, trust me, i pushed mine stably to 1.7). So yeah, i could leave OC also on the releases but i don't actually see the point of doing so...
[LG Optimus 2x] Custom40:
Don't isolate your phone from oxygen too much. 1,7? You're punishing your phone more than I punish the toilet on a bad day ;)
[LG Optimus 2x] pengus77:
LOL

Anyway 100p2 is ready without OC... should i upload it ? :D
[LG Optimus 2x] Garfields 2X:
yeah please :D
[LG Optimus 2x] Miwer:
You could also check out the Llama app. You can achieve the same results, plus a ton of other things.

Sentry will do the job, without much setup, but if you like to do a little more advanced events and actions management, check out this app.
[LG Optimus 2x] peterpao:
Re: [KERNEL][CM10/CM10.1][100p1 - 2013/02/13] Kowalski Kernel - Now With Nightlies !

For me the 100p1 kernel (stable release) is rock solid at 1.2 and -25 uv. Why remove OC? For most people is stable. I'm on cm10 newbl

. By the way, what about hdmi? Thank you for all Pengus77

Sent from my lg 2X
[LG Optimus 2x] jabooka:
Slow charge

Pengus, I still have slow charge on AC charger (stock LG) on latest kernel nightly. Just came home from work and connected phone to ac charger and got only 9% in 40min and that would be over 7h to get full charge. Nothing changed from your default kernel settings. Logcats attached.
[LG Optimus 2x] imayoda81:
1.7GHz sounds goooood :D

seems there are even lucky² phones
[LG Optimus 2x] pengus77:
Well, uhm, thermal throttle kicked in big time and i found my phone topping @816MHz after the benchmark for 10 minutes until it cooled down lol
[LG Optimus 2x] _kankea:
Just wondering if my post seems too harsh... Nah :silly:

This sounds good since the kernel without OC is still lightning fast and without OC there will be less posts about "I OC'd to 1,4GHz and UV everything to 770mV and I cannot boot plz fix Pengus" :laugh:

There's a lot of people who would want to get every bit of power/features out of their phone.

But, my opinion:

Release kernel for all, exp kernel for those who know to logcat. :good:
[LG Optimus 2x] Jishnu Sur™:
Re: [KERNEL][CM10/CM10.1][100p1 - 2013/02/13] Kowalski Kernel - Now With Nightlies !

Once at 1.5Ghz, my phone became very very hot.. Kept it in fridge for half and hour :D :P sorry I'm mad hehehehe

And completed many tests inside the fridge too :D
[LG Optimus 2x] Kamui_:
---sorry wrong thread---
[LG Optimus 2x] imayoda81:
not bad that thermal throttle .. not bad at all 10 mins at that speed and phone still alive :D
[LG Optimus 2x] tonyp:
Today's episode of 10 ways to damage my battery.
[LG Optimus 2x] kaioder:
I was using the phone, locked, and when I tried to unlock, it got a BSOD. I am using the nightly version + max OC (old bl+PA 05). I was unable to get logs this time -.-... mmm I'll keep using whitout the max OC, and increase the cpu if I need to play a game or something.
[LG Optimus 2x] darkcastleking:
Pengus, what temperature does the thermal throttling kick in? Also with that in place, does it mean the chances of frying the chipset or the battery is very low by overclocking too high?

Btw I'm currently running the OC at 1.2GHz and is very smooth with no problems :)
[LG Optimus 2x] rktdi:
bsod

my experience with bsod..

had a lot on cm7 temasek, trying different kernels - the stock kernel always worked the best..

I am now on CM10 latest from 0701, since 0701, had small problems with bsod with the stock kernel - and then tried pengus' kernels - and since 007 I have not had a single BSOD, now using 101 exp - I had 100 OC to 1200 - no problems ever.

then I decided to try PA ver. 2.5 - no tweaks at all, OC 1200 mhz, with pengus 100 kernel - had bsod within 1 hour... Tried raising voltage with 25 mv - same result...

back to cm10, and kowalski 100, 1200 mhz OC - rock stable. Same with the latest exp kernel.

my message is - maybe it is not the kernels fault you get bsod - for me it seems to be triggered by the rom...

Kow@alski kernel rocks - it bought my o2x a lot more lifetime :) thanks pengus!
[LG Optimus 2x] peterpao:
Re: [KERNEL][CM10/CM10.1][100p1 - 2013/02/13] Kowalski Kernel - Now With Nightlies !

I have the same opinion, i experienced that too.

Sent from my lg 2X
[LG Optimus 2x] tonyp:
Just to make something clear:

ALL ParanoidAndroid users should update their kernel to the latest 101 exp one (or the upcoming 100p2).

I won't make new builds only because new kernel updates arrive. Build 05 includes build 100, build 06 a private nightly from yesterday.

So both pre-included kernels are already outdated and aren't considered stable for everyone.
[LG Optimus 2x] tr@p:
Anyone still on 100p1 build? I'd like to know what are default voltages for each frequency. Thanks in advance!

I've installed latest PA, and it has exp build in it. :)
[LG Optimus 2x] wakata:
MHz>mV

1456>1250

1404>1225

1352>1200

1300>1150

1248>1100

1200>1075

1100>1025

1000>950

912>925

816>900

760>875

608>850

456>825

312>800

216>775
[LG Optimus 2x] tr@p:
Thanks!

Cool, I'm on newest exp release with -50mV on all frequencies I'm using (216-1200mHz)... still seems stable. Awesome! :cool: