Database Info

Updated:(3/6/2011) Lets Solve G2x Freezing Issue (Solved:Random Freezing in standby)

I know there are countless threads related to G2x Problems but none of the threads are focusing on isolating the reasons of Freezing Issue. I have recently upgraded my phone from Galaxy S Vibrant to G2x and i have to say i love the hardware and performance. Only Issue for me is random freezing.
After using the phone for 2 weeks and trying 3 roms
1. Stock
2. EB 1.04
3. Dark Sinister 1.1
I have come to a conclusion that kernel and rom is not the solution. At least not for me.
So i will try to solve the problem using hardware testing.
From my past 2 weeks experience.
1. Phone Freezes at night during charging
2. Phone Freezes when ever i turn off/on wifi and bluetooth and gps and Data (4g/3g) (Still have to figure out which of them is the cause. Cause i usually turn all off when i need to save battery).
Test Day 1
For Reason 1
I am using SetCpu and have changed Min from 216 to 312Mhz. I am trying this because i think very low cpu usage in standby for a very long period causes the phone to freeze. Its a Hunch i am not sure.
For Reason 2
I will keep wifi, Bluetooth and GPS off.
I will keep 4g/3g Data On all the time.
To My Surprise its been 16 hours no freeze. It includes charging at night. Lets see how long i can go without a freeze. Upon freezing i will make some changes.
Update 31/5/2011 (Test Day 2)
Ok its been more than 40 hours and not a single crash...
I removed the following possibilities as well....
It wont crash upon excessive usage.
Also Normal Heat up does not cause the crash.
As i have been playing Samurai II Vengeance all day long... Until I ended it. Several times charging along playing. I even played it on TV using HDMI. Not a single crash. I used to have around 3 crashes a day on stock rom when i unboxed my new G2x.
I also started using GPS from today. So lets see how it goes. I will update it every 24 hour.
Update 3/6/2011 (Test Day 5)
Ok i am considering Random Freezing On standby as solved because i havent had a single freeze at night after setting CPU Clock at 312 MHz using SetCPU. There are also other comments that back up my solution. I am considering this the solution of one problem.
2nd Issue of freezing while using cell phone apps is because of certain applications that are either buggy or not compatible with tegra Platform. For that i will start another thread with individual application testing for all apps that can cause the system to freeze or crash.
Please Discuss apps System Bloat-ware/User Apps that cause your G2x to Crash or Freeze in the following thread i created:
http://forum.xda-developers.com/showthread.php?p=14399089
Thanks for all the feedback.

Luckily I dont get that issue, buy I think this is a good test :u

Good point. I have not had these issues but i do have trinity kernel and minimum speed is 300
G2x with CM7 and trinity kernel

All you have to do is be careful what apps you install. I've had the phone for over a month and the one time it rebooted or froze was when I used an app the phone didn't agree with.
I am almost certain that people are experiencing reboots and freezing because of the apps they have on their phone. Hopefully the update will solve the problem because it shouldn't be that way.
Sent from my LG-P999 using XDA App

In my opinion, the shut down has to do with temperature of the phone. As long as I keep the phone cool by not charging and multitask with other things, then my phone is fine.

garrychau said:
In my opinion, the shut down has to do with temperature of the phone. As long as I keep the phone cool by not charging and multitask with other things, then my phone is fine.
Click to expand...
Click to collapse
I used to think the same thing but the problem is my phone gets hot and works fine. I am almost positive it has something to do with an issue in the kernel that's being exposed by certain apps. My Xoom on release had reboots and SOD and it went away with app updates and removals. It also has Tegra 2
Sent from my LG-P999 using XDA App

mobilehavoc said:
I used to think the same thing but the problem is my phone gets hot and works fine. I am almost positive it has something to do with an issue in the kernel that's being exposed by certain apps. My Xoom on release had reboots and SOD and it went away with app updates and removals. It also has Tegra 2
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Do you or @kangxi remember what Apps gave you issues?

it has to be a driver issue, its virtually the only explanation for why devs have not hammered it out yet or even CM7 team for that matter... it has problems on pure AOSP which leaves drivers or overheating (unlikely)... LG has to come up with the fix because they know their drivers and hardware better than everyone else...

Well the obvious problem I see is that they are all based on the stock rom. Try using one build from AOSP or a CM variety.
I didn't stay stock long but I did have reboot using the leaked Gingerbread (which is what EB is built from). I don't follow it but one is based off the stock 2.2.2 rom and the other is based off the leaked 2.3.3 rom.
I had nothing but problems with the stock roms. Thus your problem I think. Move over to Bionic, CM7, Gigglebread, or something.
I tested my phone and I didn't have a reset in like 5 days (which then my battery died overnight because I forgot to plug it in). I usually crackflash the CM nightlies and haven't had any problems with reboots or any issues requiring a reboot (aside from the flashlight killing audio, but just don't use it).

There are definitely two problems - software and the battery. I used to way more problems until I exchanged the battery for a new one and that solved most of my issues. The issues that remain are definitely software based.

tackleberry said:
Good point. I have not had these issues but i do have trinity kernel and minimum speed is 300
G2x with CM7 and trinity kernel
Click to expand...
Click to collapse
Thanks for this information/ Changing the minimum speed didnt affect the battery life but it has survived two nights without crashing. So i am planning to keep it at 312Mhz min.

kangxi said:
All you have to do is be careful what apps you install. I've had the phone for over a month and the one time it rebooted or froze was when I used an app the phone didn't agree with.
I am almost certain that people are experiencing reboots and freezing because of the apps they have on their phone. Hopefully the update will solve the problem because it shouldn't be that way.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I Completely Agree with you. Some Applications do cause system crashes. But I have removed all the t-mobile bloatware and i only have few games and GPS apps. All games are from tegra zone. So I am sure they are supported.
For GPS App i am using Copilot and it didnt crash on me once.

I just installed setcpu and set minimum to 312. I'm keeping everything else the same to see if this change has any difference. Will report back.
Sent from my LG-P999 using XDA App

Looks like you are gaining progress. Sounds like keeping the processor revved up a little more does the trick.
It would be a simple fix for people to try that have reboot issues. I can't get mine to reboot, so unfortunately I cannot help you. My contribution was to resist from flashing for as long as possible to test how long I could get my "uptime" to. I got up to 127 hours when I passed out without charging it.
I'm running 20 hours now because I forgot to charge it again (seems to be my only problem, lol).

Looks like you may have fixed your rebooting issues. It sounds feasible that the clock speed could be causing it. I never had a reboot so I can't help you out but I can tell you that I have a profile under SETCPU that clocks it at 216 min and 216 max when the display is off and I don't have a problem. I wonder why the low clock speeds would only effect certain devices? Maybe it's certain apps that stay running in the background (since there poorly written) that require higher clock speeds than what the G2X gives at idle?

jrwingate6 said:
Looks like you may have fixed your rebooting issues. It sounds feasible that the clock speed could be causing it. I never had a reboot so I can't help you out but I can tell you that I have a profile under SETCPU that clocks it at 216 min and 216 max when the display is off and I don't have a problem. I wonder why the low clock speeds would only effect certain devices? Maybe it's certain apps that stay running in the background (since there poorly written) that require higher clock speeds than what the G2X gives at idle?
Click to expand...
Click to collapse
I've definitely noticed that the G2X wakes up faster and smoother (fade in from screen off) when min is set to 312mhz that's for sure. if this is all it will take to stop the reboots, I'll be super happy because otherwise this phone is just amazing.

mobilehavoc said:
I've definitely noticed that the G2X wakes up faster and smoother (fade in from screen off) when min is set to 312mhz that's for sure. if this is all it will take to stop the reboots, I'll be super happy because otherwise this phone is just amazing.
Click to expand...
Click to collapse
Have you noticed any changes in battery usage? I haven't really played around with SETCPU much but can the clock speed be set lower and if it can, have you tried slightly lower settings than 312mhz?

y are u guys using setcpu? and its def cuz the min is too low faux has his at 400 and no problems morfic also has his a little higher then what is it i think 216?? thats too low thats y setcpu isnt supported yet.....pimp my cpu

Someone asked me a question earlier. Only app I had issues with was fring. Soon as I opened it and started playing around with it, phone rebooted.
I uninstalled and it never happened again.
Sent from my LG-P999 using XDA App

mobilehavoc said:
No clue what you're trying to say but setCPU works fine. At startup for first time I selected Tegra2 and it works great. I have max set to 1000 and min to 312mhz (default was min to 216mhz). I'm running stock ROM but with root. that's all.
Click to expand...
Click to collapse
well thats y it works for u, u cant overclock over a thousand mhz so in ur situation ur ok i guess it only applies for people running a custom kernel then setcpu doesnt work, then u would need pimp my cpu

Anyone else having tons of lag?

Just a quick question for you guys: I recently purchased an Infuse from the marketplace here, and so far I've gotten an absolute TON of lag using the device. I've flashed Infused 1.5 and Bionix with the Infusion kernel, and so far the lag has gotten better, but it's not totally cleared up. I'm definitely not new to Android, but I haven't seen anything like this before. I know that Quadrant isn't a reliable benchmark, but I'm scoring about 1900, OCed to 1.5Ghz.
Just to give an example: I'm using desktop visualizer to add some custom icons to my screen. When I go to select an icon image, it's fine, but it freezes for about 90 seconds when a list of my apps comes up.
Anyone experience this before? And if so, how did you solve it? If this was widespread, I'd imagine there would be complaints all over here.

Which app are you using to set your overclock settings, how many clock speeds do you have enabled, are you under or over volting, and *which governor* are you running?
I have seen some similar problems here when I was using conservative governor with poor choices of clock speed. Right now Infusion 1.5.2 kernel has some issues with not liking the ondemand governor, so I reduced my number of available clock speeds so it would jump to the top more quickly while using the conservative governor.
Also, did you use either the return to stock, or the ultimate unbrick flash before you flashed your ROM? If it was a used Infuse, I would do one of the above before I start looking anywhere else, then reflash your rom/kernel of choice.

I'm using SetCPU with the OnDemand gov (400/1500), no undervolting. I have a profile set to underclock it to 300/700 on conservative when I'm charging, but that's about it.
I think I'm going to use GTG's unbrick/return to stock and root the thing myself, I figured I'd ask before I did anything drastic. My UI is a ***** to set up every time, and I hate wiping because of it.

Just a quick note, I've had some serious lag using the oc kernel... Like real world usage got worse after oc'ing
Sent from my SAMSUNG-SGH-I997 using XDA App

Although it is counter intuitive to the way governors should work I have seen less lag on Infusion 1.5.2 when I use conservative. The ondemand governor seems to be having some issues with the most recent update. If you flash back to 1.0 Infusion you get a max overclock of 1.4, but it is much more stable IMHO. Also FFC is presently broken in 1.5.2 and will hard freeze the phone (battery pull).
I'm debating flashing back to community kernel, but I am going to wait and see how long it takes my battery to drain because I am using some undervolting. You might try using conservative governor and only enable 100, 400, (800 or 1000), (1200 or 1300) and 1500. Honestly the infuse is my first smartphone, but I've tinkered with desktop hardware the last 15 years. It literally amazes me everytime I pull the battery out of this phone and feel how light it is.

I also used the desktop vis app and yes it lagged when chosing apps however it seemed to get better after three or four times but that seems to be the only place it lags for me im using the oc-uv kernal 1.0 clocked to 1.4 seems bulletproof compared to later versions im getting great speed and batt life with this kernal but i had the same lag in the same event as you
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

I'm going to try bringing it back to stock and re-rooting it myself, if only because I trust myself with adb//scripts/rooting, and I'm hesitant to trust someone I don't know. Lag has gotten a lot better since switching to conservative, OCing to 1.6 and undervolting a tad, but it still lags when opening apps or scrolling through long lists. Desktop Vis is of course, still a nightmare.
Oh well, I'll report my findings tomorrow I guess. Hopefully I'll be scoring higher than the 1700 I just pulled in quadrant.

entropism said:
I'm going to try bringing it back to stock and re-rooting it myself, if only because I trust myself with adb//scripts/rooting, and I'm hesitant to trust someone I don't know. Lag has gotten a lot better since switching to conservative, OCing to 1.6 and undervolting a tad, but it still lags when opening apps or scrolling through long lists. Desktop Vis is of course, still a nightmare.
Oh well, I'll report my findings tomorrow I guess. Hopefully I'll be scoring higher than the 1700 I just pulled in quadrant.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using XDA App
Do you use spareparts?

usually yes, but I dont believe I installed it yet on the infuse. Why?

lag on stock also
I'm 100% stock & get lag also. Definitely in the situation you describe, when the app list comes up for adding shortcuts to any homescreen. Takes forever for that list to come up. Secondly, simply from running for a while, i have to kill all the apps using the built in task manager in order to get it to run smoothly again. It's like it never closes an app. I'm new to android, but guessing this is a problem inherit to android. Can't see how samsung or at&t could have screwed this soo badly to cause it to never close an app. Hoping memory management is better in Gingerbread.

Blario, you're new to Android, so you need to read up on how memory management works with Android. It's not SUPPOSED to kill apps, and that's not what's lagging your phone. In your case, I'd think it was more of a case of WHICH apps you were running.

yeah, the longer I have the phone the more it lags it seems
probably going to push me towards the Evo3D

If you're on stock and after a week or two your phone gets slow as hell (mine did), install a Voodoo lagfix kernel. All the current ROMs include it.

superweapons said:
If you're on stock and after a week or two your phone gets slow as hell (mine did), install a Voodoo lagfix kernel. All the current ROMs include it.
Click to expand...
Click to collapse
I did
I still have random slow downs when it gets bogged down with stuff
I'd give a left nut to have this phone with dual core

entropism said:
Blario, you're new to Android, so you need to read up on how memory management works with Android. It's not SUPPOSED to kill apps, and that's not what's lagging your phone. In your case, I'd think it was more of a case of WHICH apps you were running.
Click to expand...
Click to collapse
I don't do much. Twitter, "Web" (some mozilla stock ish), SMS, phone, Android Market app (browsing), and Maps. I've had it lag up using only those. Far less often, I use Yelp... that's about it.
Not supposed to kill apps? When I kill them it fixes the problem. Maybe it *should* be killing apps?? If its supposed to flush their state to disk... it seems to be doing a poor job at it.

I would be suspicious of your microSD card (if you have one). Do you know what class it is? Have you tried removing it and performing the same functions in which you see lag?

hydrogenman said:
I did
I still have random slow downs when it gets bogged down with stuff
I'd give a left nut to have this phone with dual core
Click to expand...
Click to collapse
I'd more readily assume the 512MB RAM is the issue. Looking forward to SGSII

SolusCado said:
I would be suspicious of your microSD card (if you have one). Do you know what class it is? Have you tried removing it and performing the same functions in which you see lag?
Click to expand...
Click to collapse
It's the stock card that came with the phone. Any way to check? The apps are installed to it... so removing it I wouldn't have the apps available anymore.

A little update: I returned back to stock and re-rooted. I installed 3E, then CWM, then threw on Infused 1.5 and Infusion, OCed to 1.6Ghz and slightly undervolted (about 25-100mv along the range) using SetCPU.
As of right now, it still lags on occasion, but not as bad as it did. Quadrant is giving me a whopping 1300 average score, with a low of 800 and a high of 1600. This is just pathetic.

[POLL] ICS battery issues, Default OC, Hardware revision

I opened this thread to help shed some light on the battery issues that keep occurring (and many ppl trying to downgrade end up bricking because of that).
I'm not sure the leak was meant for all revisions, because some have problems running it properly.
This guy made the connection, and i think he might be on to something:
moofree said:
I think there may be two different AT&T MB865's in the wild- the originally release fcc id IHDT56MV1 approved in September 2011 and the IHDT56MV2 that passed through the FCC in January 2012.
This may explain the 1.2ghz clock on your phones, cause mine is definitely still 1.0ghz.
Click to expand...
Click to collapse
You can check it if you remove battery, its on a sticker on the back.
You can check your default clock with setcpu(2.23 avaliable for free on xda), OR search for "cpu" in play store, "antutu cpu master" will show up, its free and reports same values as setcpu.
I'll start: im running V1 /default 1.2clock /no batter issues (I was bootlooping at 1.2 on GB, so i used 1125).
Please vote so we can get an idea whats happening with the clocks and why do people have battery problems !!

Well I am a V1 and 1GZ clock, NEVER over or under clocked the phone before with any of the ROMs... so, I am thinking might have something to do with it... Also no battery issues.

V1 1ghz. And I was overclocked on 2.3.6 to 1.2 battery on ics is great for me
Motorola lied and I'm still locked mb865

V1, 1.2. I was overclocked through Romulus 2.0 which was at 1130 if i'm not mistaken.
And I have AMAZING battery life with ICS. Much better than GB.

I've found something interesting, not sure if the guy is talking hot air though, source:
Actually the 4430 isn't overclocked in the RAZRs, it's running at 1.2GHz "Turbo" mode, an undocumented clock speed for 4430 chips tested at the factory to be stable at 1.2 GHz and run at normal temperatures. These chips are separated from the rest of the production run and sold at a premium with the 1.2 GHz "Turbo" identification.
Click to expand...
Click to collapse
It really isnt documented, this is from ti.com
OMAP4430 operates at up to 1 GHz
Click to expand...
Click to collapse
And the RAZR was 1.2 from day one. Considering its realease date, and the start of sampling of 4430 (ti.com says "currently sampling" as of 28 March 2011) they well had enough "Turbo certified" samples to make a phone using only those.
In short, hes story seems legit.
But why do we have two different clocks and how does the rom determine which setting its going to run on.
I dont think CPUs themselves "know" if they are certified, they are just placed in another box after the tests(being a bit vague here).
Just like some OC edition video cards; fitted with a better cooler, placed in a different retail package(with higher price).
Then again some OC video cards do get a modded bios (but not at the OEM level).
If they had a different firmware/serial numbering like desktop cpus then it would be documented and listed on the ti.com site.
But could it be that they "know" it after all? I'm not even sure these ARM SoC-s have something like a GPU bios register that tells them the voltages per states and clock rates(that they could flash while still on the test line) at all.
The reason this is interesting is that if its burned in on an individual chip level, the hw revision holds no relevance at all.
OR There could be some test after first install and it falls back to 1.0 if you get a reboot... obviously I didnt stumble into this and it wouldn't seem like a professional method from motorola at all.
Anyone running 1.0 carefully watching(and remembering, lol) the process could clear this one up though.

I'm on V1, setcpu is reading 1 ghz, I think my battery on ics seems OK, maybe drains a slight slight bit faster than before, but maybe that's my imagination!
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE

V1 at 1.0. Ran overclocked on 2.3.6 Roms at 1125.
1.2 bootlooped on every rom I flashed .
And I tried them all.
ICS leak is running sweet. Only interesting thing I've seen is uninstalling stock bloat, ATT crap, through Absolute System app (which is step 3 after every flash) is it says it uninstalls but it don't.
Like ATT family map or YouTube.
Says successful uninstall. Google restore is off, so no clue. Of course stopped trying after hard brick scare.
Battery is great, wifi and data fast. Only installed spare parts to set animation and window transition to fast. Originally it popped up on slow setting. That was odd.
Hit my upgrade date last week, but for some reason ATRIX is my choice. I had the original also.
Sent from my MB865 using xda premium

dicksteele said:
V1 at 1.0. Ran overclocked on 2.3.6 Roms at 1125.
1.2 bootlooped on every rom I flashed .
And I tried them all.
ICS leak is running sweet. Only interesting thing I've seen is uninstalling stock bloat, ATT crap, through Absolute System app (which is step 3 after every flash) is it says it uninstalls but it don't.
Like ATT family map or YouTube.
Says successful uninstall. Google restore is off, so no clue. Of course stopped trying after hard brick scare.
Battery is great, wifi and data fast. Only installed spare parts to set animation and window transition to fast. Originally it popped up on slow setting. That was odd.
Hit my upgrade date last week, but for some reason ATRIX is my choice. I had the original also.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
You know with ics, the at&t bloat can just be disabled, which is probably safer than uninstalling!
Sent from my MB865 using Tapatalk

big ach said:
You know with ics, the at&t bloat can just be disabled, which is probably safer than uninstalling!
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
Yeah I agree just get a bloat freezer app, much safer.

I had a v1 and ICS was clocked @1200 for me. I have never been that high - always got unstable around 1175 on gb - but it was smooth as butter on ics.. recovery operations were so damn quick.
Sent from my phone's mind

My phone is V1 and I used to run at 1.335 on GB. I am now clocked at 1.0 ghz by default on ICS.

jimbridgman said:
Yeah I agree just get a bloat freezer app, much safer.
Click to expand...
Click to collapse
No, I was saying that you don't even need a bloat freezer app, by default in stock ics you are able to disable (freeze) any system apps. Its a new feature in ics!
Sent from my MB865 using Tapatalk

big ach said:
No, I was saying that you don't even need a bloat freezer app, by default in stock ics you are able to disable (freeze) any system apps. Its a new feature in ics!
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
So far, I haven't gotten a single app to show me the disable button, just force stop and uninstall.
My battery life is GARBAGE. I used to get 18 hours + on a single charge, but now I barely make it 12 hours.

V1 - 1000 Ghz - Battery Problems
Even though I didn't install the ICS leak, I wanted to chime in because I've been having battery issues for some weeks/months.
When I bought the phone the battery worked well. After the 2.3.6 update the battery lasted even longer than before. So I was happy and everything. Now a few weeks/months ago I get to the end of the night with only 20% or 10%. Sometimes it even dies! I tried everything, even replacing the battery, and nothing, still poor battery.

I think battery life is also subjective. There should be a standard as to what is good or bad. I have used my phone pretty heavily today with wifi on and im at 9 hrs and 30% remaining. This seems okay to me, but I noticed some people getting over 24 hrs on a charge so maybe half a day isn't that great.
My battery life is definitely better on ICS though. And it's also possible some of you are playing with all the fun stuff involving ICS for long periods of time which is making the battery die faster then boring GB where it stays in your pocket the whole day.
Anyway, I have a V1 and i'm at 1 ghz, ICS is noticeably faster. In GB I could run as high as 1.25ghz, and I would overclock using a script, not an overclocked ROM

I'm v1 clocked at 1.2 ics leak. I bootlooped at 1.2 on gb. At first I thought my battery wasn't right. Seemed to charge really slowly. After a couple cycles though I'm pretty happy with it. I have basically the same battery life as before.
Edit
I was using Remus on gd.
I uninstalled all the at&t bloat with no problem.
Sent from my MB865 using Tapatalk 2

[email protected], no battery issues.
Sent from my MB865 using xda app-developers app

has anyone else noticed that no one with a v2 has even voted? are we sure there is a v2? lol

where do i check my a2 versioN?

fromanbr said:
where do i check my a2 versioN?
Click to expand...
Click to collapse
under the battery look at the fcc number and compare to first post.

High Load in cm10 and Roms based on it?

Hello,
I have noticed, that the load* (not the CPU%) under several CM10 (or higher) based roms is very high, i.e. >2.
This is true for PACMAN, JellyBam and the CM10 nightly.
Can someone please have a check by activating the CPU-Stat-Overlay and post the line that looks like 2.7/3.0/2.0?
Is this a known problem? I once had a nightly of CM10 on the Phone, which ran very well. I do not think, that it had this problem...
I do not have this Problem with OptimusRS which is based on the Official ICS. Here, the load is lower by a factor of 10.
*in contrast to the CPU usage (%), the load also captures if the system is blocked by something other than the CPU (I/O, ...)
Greetings,
Hendrik

Mine says 1.15/1.18/2.25
Using PacMan 19.3 rom

svvv said:
Mine says 1.15/1.18/2.25
Using PacMan 19.3 rom
Click to expand...
Click to collapse
Well, that's quite high, still.
Was that after the device was ideling??
When I have not used the phone for 15 min, I get 0.02/0.02/0.02.
Your values show that your phone is really busy (values > 1 means that it is over-loaded).
Are you happy with the responsivenes of the phone?
Greetings,
Hendrik

henfri123 said:
Well, that's quite high, still.
Was that after the device was ideling??
When I have not used the phone for 15 min, I get 0.02/0.02/0.02.
Your values show that your phone is really busy (values > 1 means that it is over-loaded).
Are you happy with the responsivenes of the phone?
Greetings,
Hendrik
Click to expand...
Click to collapse
I kept my device idle for 5 mins then checked all three vr above 1. But my mobile seems to be smooth when runnning single app but while multitasking device becomes very slow.

svvv said:
I kept my device idle for 5 mins then checked all three vr above 1. But my mobile seems to be smooth when runnning single app but while multitasking device becomes very slow.
Click to expand...
Click to collapse
The first value is now, the second 5 minutes ago, the last 15 minutes ago.
So, your device/your Rom seems to have the same problem I experienced.
I am surprised, I am the first to complain?!
Greetings,
Hendrik

henfri123 said:
The first value is now, the second 5 minutes ago, the last 15 minutes ago.
So, your device/your Rom seems to have the same problem I experienced.
I am surprised, I am the first to complain?!
Greetings,
Hendrik
Click to expand...
Click to collapse
I come back to CM-Based rom today...and i noticed that in Jellybam and also Bernie's rom the CPU usage is really high...the cpu stays every time at the higher frequence and the back of the phone is really hot! I noticed this problem also with MIUI rom that are also CM Based, i need to change kernel for trying correctly Bernie rom! With Pesach kernel for CM10.1 the thing seems good..but the phone stucks ever at the minimum frequence...and it never go on deep sleep!
Is really strange! I tried bernie's also when it came out some time ago but it hadn't this problem! I think that is a recent problem!

Install wakelock to see who do that. put wifi to sleep when screen is off. Uninstall the programs that you do not need.
Take a look here
http://forum.xda-developers.com/showthread.php?p=42778421
Sent from my LG-P920 using xda app-developers app

Well, I suspect the obstacle might be the CPU driver - I don't know if LG have ever used Texas Instruments' default values or just made them up by themselves although I suspect it would be the latter since I have used Tegra 2 based phone before (hacked, of course), and it's surprisingly smooth so there may be explanation somewhere in either second-stage BIOS or in the kernel for the 3D phone and no I am not pointing the finger at any developers here as there are variables that have to be checked down.
Sent from my XT907 using xda premium

Dr. Mario said:
Well, I suspect the obstacle might be the CPU driver - I don't know if LG have ever used Texas Instruments' default values or just made them up by themselves although
Click to expand...
Click to collapse
I don't understand, what you are saying...
For me, it is not yet clear, whether this problem exists on every phone, and whether it is on every rom.
When I started using CM10, I did not have this impression. Does someone have an old version on CM10 and could check?
What about the others? What are your LOADs?
There must be more users...
Greetings,
Hendrik

CM10 only load the values which are in the kernel which you can install separately, and some kernels have better CPU values. Not to mention there is 410 MB assigned to CPU.
However in some case, BIOS is what make or break this phone (BIOS boots up first and displays red or silver LG logo depending on whether BIOS is unlocked or not, and is responsible for loading Linux kernel, thus booting Android OS up). So it's hard to say but I might want to try assemble the BIOS on my own and see if problem persists in some OS images (FYI, BIOS development is much harder than Android OS development).
Sent from my XT907 using xda premium

Hello,
I think, it is worth to go back to an older CM10 Version, because I am quite sure, that it was better there.
What really surprises me is, that I am the first and more or less only one to complain. For me, PACMAN and JellyBam were unusable, CM10 was also quite bad.
Greetings,
Hendrik

henfri123 said:
Hello,
I think, it is worth to go back to an older CM10 Version, because I am quite sure, that it was better there.
What really surprises me is, that I am the first and more or less only one to complain. For me, PACMAN and JellyBam were unusable, CM10 was also quite bad.
Greetings,
Hendrik
Click to expand...
Click to collapse
You're not the only one...some days ago i went back to CM-Based roms and i noticed that they never go in deep sleep! And the phone goes hot...the only rom where i hadn't this problems is the Baked Blackbean by kidkoala...also MIUI roms have this problem!

Hello,
is there anything new on this topic?
Can anyone using CM10 or higher confirm, that he does NOT have this problem?
(to check:
Settings-->Developer Settings (very bottom) --> Display CPU Usage (far down)
let the phone rest some Minutes.
An Overlay is shown. The first three lines are of interest
--> Are the values low, around 0.1? --> no Problem, all good.
--> Are the values high, around 1 or higher --> you have the Problem.
Greetings,
Hendrik

Help!! GPU broken

Hello. I have been using s8+ for couple of months
Recently I've found lags in Google map. I was curious so I installed AnTuTu Benchmark, and I think my GPU is broken.
In the first visual tests, the device was heavily lagged and shuttered. One scene to another took 4-6 seconds to load. Wtf? Even my Xiaomi Mi5 still working properly. I read articles about comparison between Mali GPU and Adreno, but i never thought it will be this bad.
I was unable to complete the test since it was too horrible and my phone got lagged and could not be used.
I tried to install CPU-Z and GPU load section always stay at 0% no matter what. Is my GPU broken??

reynaldi3 said:
Hello. I have been using s8+ for couple of months
Recently I've found lags in Google map. I was curious so I installed AnTuTu Benchmark, and I think my GPU is broken.
In the first visual tests, the device was heavily lagged and shuttered. One scene to another took 4-6 seconds to load. Wtf? Even my Xiaomi Mi5 still working properly. I read articles about comparison between Mali GPU and Adreno, but i never thought it will be this bad.
I was unable to complete the test since it was too horrible and my phone got lagged and could not be used.
I tried to install CPU-Z and GPU load section always stay at 0% no matter what. Is my GPU broken??
Click to expand...
Click to collapse
are you rooted or custom rom do you have gpu under clocked or anything
I would imagine a total gpu failure would probably not allow te device to boot or display much of anything correctly

TheMadScientist said:
are you rooted or custom rom do you have gpu under clocked or anything
I would imagine a total gpu failure would probably not allow te device to boot or display much of anything correctly
Click to expand...
Click to collapse
I have stock rom. No root or whatsoever. The only different thing I use is Nova launcher. Other things are stock. Do you have anything in mind what cause this?
Thanks!

reynaldi3 said:
I have stock rom. No root or whatsoever. The only different thing I use is Nova launcher. Other things are stock. Do you have anything in mind what cause this?
Thanks!
Click to expand...
Click to collapse
Anythng messed with in developer options.