yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G2x] mansa_noob:
Now running for longer than 6 hours with slight undervolting at the higher end of OC without any issues... to get a faster verification of stability, at this time I have changed the low frequency from 216 to 1015. Let's see if it breaks.

I would have a $500 brick if it weren't for nvflash. Thanks Nvidia!
[T-Mobile LG G2x] Darkknight512:
No, just saying that a stable system should stay stable. Restarting it periodically should not be needed, and if it is needed it should be looked at and fixed if possible.
[T-Mobile LG G2x] EEngineer:
That's true, in theory. In reality people have SOD and other problems.

Hey, if we wanted stability we'd have stayed with stock, right??? We are here because we're not satisfied with what everyone else has. When we go custom Android, we accept risk and a bit of instability. To deal with that risk involves improvising.

To be honest, people that make excuses as to why they should never turn off their phone for only five minutes just twice a week - think about it.

The real question is, ask yourself, can you, right now, turn off your phone for no reason at all for 30 minutes? For no other reason at all but to prove to yourself that you can do it? :confused:
[T-Mobile LG G2x] mansa_noob:
OK, report time:

1. Running as stated above is a surefire recipe for SOD. Woke up to a phone that died around 2:30 a.m. and was hot to the touch (not extremely, but more than warm). Note that stay awake while charging is NOT checked.

2. Running with undervolting as described in the previous post worked fine until I turned on the GPS. The phone was exposed to sunlight in the dash mount and died after about 1/2 hour of operation. This time it was hot... when I rebooted it the temperature was around 50C.

I think the experiments need to continue to see the boundary of stable range, so I will continue. I have a theory about the latest failure... high temperature increased IR drop and resulted in lower than stable voltage at the transistor level which resulted in a lockup.

Can anyone shed some light on how the original list of voltages was determined?

Also, are the IO voltages set to stock values? How can I change those?

I would have a $500 brick if it weren't for nvflash. Thanks Nvidia!
[T-Mobile LG G2x] redmonke255:
Are you trying to undervolt to gain stability? Undervolting will only cause instability, all the chips are slightly overvolted to prevent lockups. You might be able to cut down a bit of heat output, but it's not worth it imo.

Aldo Eengineer, stock for this phone isn't stable at all. That's why we're here.
[T-Mobile LG G2x] hairycheapo:
+1.

The wife's G2x is (and always has been) non-rooted stock. She's constantly frustrated by the misbehavior of her phone. As soon as I started running CM Nightlies with Trinity kernel my phone started acting more stable than her's. I now only get SODs when I overclock, undervolt, or get the phone too hot (more than 105 F). Even though her's is stock - she seems to need a battery pull at least once a week.

Yet - she still doesn't want to root :confused:
[T-Mobile LG G2x] n30wav3:
Getting to 50c hot when exposed to a bit of heat and SOD is normal for G2X ..... especially when overclocked.....

As far as voltage is concerned... I think they determined from the stock kernels though I could be wrong...

By the way.... is anybody else except mansa getting SOD on the newest experimental? Its the end of third day of my test.... and I know my device pretty well as far as my usage is concerned.... I should have got an SOD by now ... that's not a placebo .... m not getting any....

So if anybody else using the latest experimental getting SOD please post here along with ur log if possible
[T-Mobile LG G2x] capncybo:
Stable so far

I am also finding the newest experimental build VERY stable. :D

My G2X has also been running for Over 3 Days Now. (Perhaps I should Knock on wood)

Anyways here's the proof.

I'm Running slightly under-clocked @ Min:216MHz & Max:816MHz

Plus I'm even under-volting @ -25mV across every frequency.

I'm seeing awesome battery life & the phone is still SNAPPY & QUICK!!!

I'd show you my battery life snap shot but my phones battery is fully charged & from my understanding the battery information gets wiped at >90%.

Anyways thanks Mazout I was starting to think my phone would never be this stable or have this kind of battery run-time.
[T-Mobile LG G2x] n30wav3:
Wait a sec.... why the radio has no signal? Why ur cpu1 is off? The sleeptime as compared to the boot time shows it was awake more than about 1 day in last 3 days.... its good u didn't had any SOD and by the look of it , it seems u r following the undervolting guide + morfic's xlp clocking 800 something MHz... hence great battery.... but I would still like to know why these things are off

Edit: my bad more than 3 day awake time ... I didn't see the up-time field... still did u use the phone in this state? For this long time?

And yes another thing....battery usage info is lost at 100% not on >90 .... and I dun believe ur battery didn't lose 1% in last 4 days... come on man be realistic
[T-Mobile LG G2x] Pain-N-Panic:
This lol
[T-Mobile LG G2x] pmorrsn:
Does SOD refer to when your phone simply crashes and is only fixed by a battery pull? Also, is there something that causes a phone to sporadically rapidly drain the battery (noticed overnight). None of these require being on a charger (In fact, only noted off the charger) and maybe more frequently on wifi.

If this/these are distinct from SOD, please define for me.

Thanks..
[T-Mobile LG G2x] n30wav3:
Yes that's what SOD is when u need a battery pull to fix it. And as for rapid battery drain overnight, that use to happen with me on faux when phone used to get SOD overnight causing it to become hot and drain battery when u wake up
[T-Mobile LG G2x] pmorrsn:
Thanks, I appreciate the quick response. I am back on Faux. I have been waiting for this new kernel to stabilize and then I'll run it again. I like the haptic feedback with my bottom icon/buttons.
[T-Mobile LG G2x] capncybo:
Ok stay calm, Let me attempt to explain... or eliminate your doubt.

1- Why the radio has no signal? I work in the basement of a very large hospital with a mechanical floor between every patient floor... Hence no signal. (This is When I captured the snapshot)

2- Why ur cpu1 is off? It's OFF because it's not needed. It turns off when not needed, as it should... especially when in deep sleep.

3- I know my phone was in deep sleep for about 2 days with CPU1: OFFLINE that's when the screen was off & it was in my pocket or sitting on a table in the bar... but it was AWAKE for more than a day, from certain moments when being used.

4- And yes another thing....battery usage info is lost at 100% not on >90 .... and I dun believe ur battery didn't lose 1% in last 4 days... come on man be realistic.

I Don't need or appreciate the attitude... but as you can see by the Full lenth RED battery bar @ the top of the screenshot. My Phone was plugged in & at 100% when I took the screenshot.

Hence, I can't provide you with the battery info as it has been RESET!!!

Forgive me if I read somewhere else in XDA that it occured at >90% perhaps it does this at 100% instead.

+ WOW buddy: I never said I didn't loose 1% in the last 4 days.

I was easily getting over 17hrs, 19hrs with moderate typical use... I just forgot to take a snapshot to prove it.

And this was before I started testing under-volting.
[T-Mobile LG G2x] mansa_noob:
I am not trying to undervolt to gain stability. Heck, based on everything I know it is not even for sure that it is undervolting. It is, however, reducing the voltage from current set based on a hypothesis which I described in the previous post.

There is a cliff on both sides of the voltage curve. On one side the setup time is wrong and on the other the hold time is wrong. So the system would lockup if you are outside of this safe range.

Stock is stock. Nobody knows how it came about (except mighty LG & Nvidia of course). It would be fair to assume that stability was tested by very capable developers for overclocking. I simply observed that the frequency vs. voltage curve is not a functional form (does it have to be, not really but I would expect it to follow some form of a curve).

I can run without SOD or lockup with the voltage list I posted, except when the GPS is turned on. Heat, then, initiates the process resulting in a lockup.

Hmmmm. Maybe we can dynamically scale the voltages based on core temperature. That should do the trick. If only I knew how to :D.

---------- Post added at 06:31 PM ---------- Previous post was at 06:24 PM ----------

Hi guys,

I think it may help to answer the following questions (don't start responding with answers until we all agree).

1. Is Stay Awake checked?

2. Type of SOD observed before the experimental builds (BSOD while charging / BSOD while not charging / Lockup).

3. System up time.

4. # of charging cycles and maximum battery percentage in each.

5. WiFi use average state

6. Data use average state

7. GPS used for how long.

8. Is behavior in #2 still present?

There may be others, so feel free to respond with other questions, just not answers until we agree to avoid posting multiple times.
[T-Mobile LG G2x] n30wav3:
Oh boy.... I need to check myself for attitude .... this is the second time in the day someone has sort of complained.... sorry about that I wasn't trying to be an ass ... but seems I made it like that... let me read the whole thing again to add to tthis post then

EdIt: oh ok ... so very less radio usage then ...even when it was awake it was in the basement...coupled with ur UV/UC yup..... that's how u got the timing..... makes sense now...

when u said the >90 thing that it gets erased ...thats where I mixed up thinking the battery is on somewhat above 90 still after all this time..... didn't see the slim battery bar there :p... one last thing... cpu1 turns off automatically when the phone is in deep sleep.

Have u made any other profile to keep it off even when its awake?

And u know what the way u have modified the settings could make it a recipe for SOD.... if its working still thats a very hard proof that this kernel really is the stable most now
[T-Mobile LG G2x] capncybo:
-No additional profiles have been made. I used to use SetCPU with various profiles... such as 216MHz with screen off & while charging.

However JustJackyl suggested that SetCPU did not play nice with the G2X (Hence I started looking for alternatives).

Someone suggested CPUtweaker while I attempted to gain a better understanding of why & when my phone would ocassionaly SOD...

CPUtweaker's layout & functionality really grew on me.

I also know that under-volting could be asking for a SOD but the thing is...

When I tested the regular non OC version I noticed my phone was not actually running at specific different frequencies.

ex) 216MHz, 512MHz even though I set Min: 216MHz & Max: 816MHz

So... I tried the newest OC version and... It Behaved properly with those settings.

Better yet it was stable for over 3 days.

So...

I said hmmmmm maybe I should try undervolting too

and that's where I'm at right now.

Over 3 days UPTIME

& COUNTING...
[T-Mobile LG G2x] mansa_noob:
Is your undervolting profile -25mV across the board?

I would have a $500 brick if it weren't for nvflash. Thanks Nvidia!
[T-Mobile LG G2x] capncybo:
under-volting

Yes sir (for now)... I don't wan't to be to gready. I understand that operating beyond design specs is kind of asking for trouble.

EDIT: Oh & hey you asked earlier about my CPU1 sleeping or being OFFLINE.

From my observations... CPU1 will typically go OFFLINE shortly after being plugged into USB or CHARGER (within a couple seconds to within 15)

I would guess or assume this might be done to prevent the phone from overheating while charging.
[T-Mobile LG G2x] EEngineer:
Can you tell me, were you getting SOD with SetCPU, and now you are not getting SOD with CPU Tweaker?

And does CPU Tweaker allow for profiles? The developer's website is down so I can't reference the Help docs.
[T-Mobile LG G2x] capncybo:
Unfortunately no additional profiles & I can NOT say DEFINATIVLY that SetCPU would cause me an SOD.

Because Mazout has made so many changes to his Kernel.

But what I can say from my personal use is sometimes I would notice SetCPU would stop changing frequencies.

The phone/program would just stay stuck at one particular frequency.

So I took JustJacklys advise & tried something else... after uninstalling SetCPU (of course).

However with the help of BetterBattery stats & some XDA reading I learned...

That in my case... GoogleTalk was really bad for resulting in a partial wake-lock

Thereby preventing my phone from entering DEEP SLEEP.

After I tweaked my Google Talk settings.

My phone started sleeping

ALOT

which is Ideal... as long as it doesn't result in an SOD
[T-Mobile LG G2x] mansa_noob:
Thanks. And regarding CPU 1, I did not ask. I know that even though the governor is called performance it is more like on demand and one CPU will sleep when not needed.

I know what you mean by being greedy :D. I am currently testing very aggressive undervolting... my initial attempt resulted in lockups so I added 25mV to the high frequency portion. So far so good, but haven't tried with GPS yet. Later today hopefully when I go out.

I would have a $500 brick if it weren't for nvflash. Thanks Nvidia!
[T-Mobile LG G2x] pmorrsn:
Sorry no log, but I had an sod overnight with the stock voltage no ds 427 experimental build, while on Wi-Fi.

It also occurred while on the charger yesterday, so I then set it to stay awake. I installed this kernel yesterday, so maybe it needs a little more time.
[T-Mobile LG G2x] capncybo:
4.5 days

My running UPTIME with that build also just came to an end :crying:

But it was OVER 4.5 days with OVER 2 days in DEEP SLEEP plus mine wasn't actually a SOD :D.

I was testing the newest Kii Keyboard with GESTURE SWIPE enabled which used to make the keyboad crash & dissapear as soon as you typed a single letter after swiping. However now it seems to be working almost perfectly both with SWIPE & REGULAR typing, UNTIL...

it hangs for some (unknown) reason. Then the Kii keyboard stays displayed & in this case it completely hung my phone. I tried for several minutes to get the phone to work again... but eventually it forced a REBOOT.
[T-Mobile LG G2x] EEngineer:
Interesting, with Mazkrnl_0323GBOCnoDS I switched to the DEADLINE scheduler and I had two Screen of Death (SOD) incidents in two days.

I'm now on the ROW scheduler, my G2X is fast and snappy and no SOD.
[T-Mobile LG G2x] hairycheapo:
Just for clarification - How did you have your phone configured at the time of each SOD?

-Were you charging the phone during both SOD's?

-Were you charging using your normal charger?

-Was "Stay awake" checked during either SOD?

-What's your setting for Wi-Fi settings > Advanced > Wi-Fi sleep policy?

If you are using the No DS kernel I don't know if the last question has any effect... Also, before I set "Stay awake" on my phone I think I got more SOD's when alternating between USB/car charging and AC charging. My AC charger puts out 1 amp, but my USB and car chargers put out 500 milliamps.
[T-Mobile LG G2x] pmorrsn:
-Were you charging the phone during both SOD's?

Only the first time was charging and since then, I went into apps/keep screen on while charging...The second time was overnight and a notable drop in remaining battery (~30% occurred, but not to depletion)

-Were you charging using your normal charger?

Wall plug charger.

-Was "Stay awake" checked during either SOD?

That is what I checked after the first charger incident...But not relevant to second..

-What's your setting for Wi-Fi settings > Advanced > Wi-Fi sleep policy?

Never sleep.

I am using the Stock kernel, not the NoDS version. During the week, I rarely use USB charging, but do over the weekend some of the time. I rarely use car charger.
[T-Mobile LG G2x] Mazout360:
Thanks! I never actually took some time to doublecheck the voltage values...They indeed seem to be a little overestimated in the higher end but that's probably to keep it as stable as possible when overclocking. I'll try lowering the 1,1GHz and 1,2GHz values to a more accurate theoretical value.

Oh do not switch schedulers right now...They are still based on linux 2.6.32 and I rebased the I/O to linux 2.6.35 so I don't know if they're still compatible. I'll update them for the next release.
[T-Mobile LG G2x] mansa_noob:
Thanks Maz. I am afraid the values I started with result in lockups when temperature rises. Is there any way to dynamically change the voltage as a function of temperature?

BTW I am having sporadic BSOD when charging using default voltage set... I will do a dirty flash tomorrow and if it still happens will do a fresh install to rule out other variables. If still present will try to capture a log.

-- The noob says:

A new android has larger battery, larger display, more CPU cores, more memory, more storage, etc. resulting in identical battery life as your old phone... Go figure!
[T-Mobile LG G2x] n30wav3:
Mansa.... did u had the hot sudden no reason SOD when u first mentioned it on the new one? I think I have experienced it twice till now. Although the frequency is too low that's why m still not able to confirm whether it was kernel or me...
[T-Mobile LG G2x] mansa_noob:
I just woke up from an SOD... lol, although it is no laughing matter as my phone was cooking. All voltages were default as per kernel and stay awake was NOT checked. I need to get through the night so am checking the start awake box.

Not sure what you mean by first so not sure how to answer. When I was playing with voltages I was getting lockups especially with GPS on, but occasional BSOD too. I am not playing with voltages anymore but am getting BSOD (funny I charge the phone during the day too but BSOD tends to happen at night :D).

Please state your question again my rant at 3 a.m. did not result in an answer :angel:.

-- The noob says:

For a dead guy the g2x sure kicks a lot!
[T-Mobile LG G2x] n30wav3:
Uhh... sleepy... what I meant though u were getting hot SODs too right on the latest experimental initially when u didn't tweak anything?
[T-Mobile LG G2x] mansa_noob:
Awake now. Yes, I am getting those. Will stress test the default values later today.

-- The noob says:

For a dead guy the g2x sure kicks a lot!
[T-Mobile LG G2x] iLovPieNCake:
Maz, do you have quickcharge enabled? I find that my phone no longer SODs with your 0327GBnoDS but the phone gets incredibly hot when charging via USB to computer. Hotter than me playing two hours worth of Nova with cpu max at 1480. Doesn't seem to get as hot when charging from wall using a very old LG charger.
[T-Mobile LG G2x] EEngineer:
O.K., last night on Mazkrnl_0323GBOCnoDS I picked up my phone and it was a hot, hot, HOT SOD.

Pulled, the battery, etc. checked my stats. Last log was:

7:22PM 86% battery 22.9degC

After pull, new stats:

9:02PM 7% 37.1degC

Went from 86% battery to 7% in less than two hours while my battery was burning up.

Today (Wednesday) is a crucial day for me so last night I installed Trinity T15 kernel. Using my test video, Trinity video performance is definitely inferior to Maz, but I can't take the chance of having to pull my battery in a meeting or on the subway today.
[T-Mobile LG G2x] pmorrsn:
Were you on wifi at the time? It seems, though I'm not certain, to only happen when I'm on wifi.
[T-Mobile LG G2x] EEngineer:
Yes, I was on Wifi when it burned up on the SOD.
[T-Mobile LG G2x] Pain-N-Panic:
Engineer, do you have the stay awake option selected while charging?
[T-Mobile LG G2x] EEngineer:
No, and I wasn't charging when it SOD.
[T-Mobile LG G2x] pmorrsn:
I still get Wi-Fi sods when off the charger, and this is not only for this kernel. I've not found one that does not cause sods, but only test so much. Anyway,I just got a nexus 4 and am waiting for the SIM.I guess this will remain an emergency back up.
[T-Mobile LG G2x] Pain-N-Panic:
What's your wifi sleep policy look like, if any?
[T-Mobile LG G2x] pmorrsn:
Mine is set to "Never". I never liked having it go offline, so changed this setting quite a while back. It still seems to sporadically go offline(with different kernels), but I hope it is less frequent.
[T-Mobile LG G2x] mansa_noob:
LOL. G2x is an emergency in itself... definitely not a backup. IMHO though.

-- The noob says:

For a dead guy the g2x sure kicks a lot!
[T-Mobile LG G2x] saijaiantonio:
Its not a backup its a last resort lol!
[T-Mobile LG G2x] towelboy:
Nah its a backup for the last resort!!
[T-Mobile LG G2x] mansa_noob:
I have a Moto Milestone as a backup phone. Dog slow but never fails. GPS locks instantaneously.

Take that g2x!

-- The noob says:

Believe you me... Apple suggested LG for Nexus 4
[T-Mobile LG G2x] towelboy:
Can't compare to my Nokia e71.. nothing has ever stopped it ;)
[T-Mobile LG G2x] n30wav3:
Umm.... where is mazo?
[T-Mobile LG G2x] TheCoutures:
Probably busy with his personal life like most.
[T-Mobile LG G2x] n30wav3:
Know that :D .... Just wanted to break the flow :P
[T-Mobile LG G2x] mansa_noob:
Something to report.

I tried the stock voltage version of the 4/27 experimental build and noticed a few things. First, Fmax seems to be showing 1.48G but kernel does not go over 1. So this is no big deal and I can live with that. Second, battery life is actually worse with most consumption by Wi-Fi. This is in comparison with the OC version which is odd. Finally I get SOD on this one too but the phone does not catch fire like in the OC case. Makes me think that when SOD happens the phone gets stuck in Fmax state.

I have also noticed (but hard to quantify) that the phone is more prone to SOD after it gets one. I know this sounds strange but that is what I noticed. Maybe I am going senile in old age :D.

-- The noob says:

Believe you me... Apple suggested LG for Nexus 4
[T-Mobile LG G2x] Pain-N-Panic:
Eh, i made sure to remove Gps on my phone. I don't like Google knowing where i am lol
[T-Mobile LG G2x] EEngineer:
Mazout's kernels still play my test video the best, and also have nicer overclock frequencies.

Can anyone tell me what's the last stable version of Mazout for the G2X, is it 205GBOC?
[T-Mobile LG G2x] towelboy:
My phone is similar to eengineer's where it sods overnight without be charged, with wifi on.

A remedy that I have been using is flashing the same rom every weekend and fixing permissions. Someone else come up with a better fix?
[T-Mobile LG G2x] EEngineer:
O.K., I've been taking a closer look at different G2X kernels. Right now I'm looking at how different kernels allocate memory between Android and the GPU. Mazout's kernels are the only kernels that play my heavy test video properly.

For the Mazout kernels, can any of you please tell me the amount of available memory? Go into Terminal and type

cat /proc/meminfo

I need the first number, Memtotal, along with the kernel version you are using. Trinity kernels have this as a high number (414656 KB) because they take memory away from the GPU and give it to the Android system.
[T-Mobile LG G2x] mansa_noob:
381788.

-- The noob says:

Believe you me... Apple suggested LG for Nexus 4
[T-Mobile LG G2x] iLovPieNCake:
I was suspecting something like this was happening because regardless what I set my F max to in 0323 & 0427 noOC noDS, my quadrant score stayed the same. Also probably why I have been running 1480 wil 100% stability.

My Memtotal is: 381788 kB, from what I remember O2Xs have kernels that do this, they modify the amount of GPU memory to 64mb I think. That helps because you have extra total memory but probably has some 2D & 3D performance effect.
[T-Mobile LG G2x] EEngineer:
What kernel and version are you using?
[T-Mobile LG G2x] mansa_noob:
Maz 4/27 experimental build without OC.

-- The noob says:

Believe you me... Apple suggested LG for Nexus 4