I had noticed some slow performance from my Galaxy Nexus recently, (while playing games) and decided to do a little investigation of my own. I realized that my device was spending almost all of it's time at the idle 350 MHz.(using CPU Spy) Even though the games were lagging, the device was never clocking up, an always staying at 350 MHz. After a 5 minute text run, the device spent 3 minutes 26 seconds at 350 MHz, 1 minute, 13 seconds at 700 MHz, 4 seconds at 920 MHz, and measly 15 seconds at 1.2 GHz.
You can see the change in gameplay too. The test run was Super Mario 64 on N64oid, and the game was somewhat laggy, with occasional ten second or so bursts of smooth gameplay.
I've seen this game played on a Galaxy S played perfectly smoothly, and although the resolution is increased, the bumped up RAM, CPU, and GPU speeds should be able to accommodate that. As a note, even when played without stretch, and with the menu brought down, (which results in the smallest possible screen) the device still lags similarly to full screen mode; leading me to believe this to be CPU rather than GPU limited.
One last thing to add here is that during a 5 minute idle control test, (sitting on home screen, screen set to 10 minutes till auto off) the device performed as you would expect, with all but about 3% of the time at 350 MHz.
Not sure why you are seeing this, I have no problems playing n64oid. I noticed a stuttering effect like you described when running the first overclock/uv boot.img when it was posted, but I have since not had any problems.. perhaps a new boot.img is in order?
I'm running completely stock, have there been any known issues with N64oid on stock?
Related
I've heard that having your screen off setting to 128mhz that it drains more battery than 284mhz and does not let the evo perform correctly. Is this true?
I have mine to 128mhz atm and dont seem to notice qany diffrence in battery loss to when it was at 284. I have only had it this way about 24 hours but so far not a big diffrence one way or the other
Haven't noticed any extra power drawn, only thing I noticed and hate is that when you wake up it can lag bad, until the profile changes to a higher clock
Sent from my PC36100 using XDA App
Im interested in this also. I saw some people say 128 drains more battery but nothing to actually show it. I am running some tests of my own currently. Im sure it will be hard to see a difference unless there is something crazy going on.
It must have been me who posted about the 128Mhz bug first.
I'm running latest ota stock rooted, latest ota radio/wimax with Netarchy's 3.0 or 3.7.3c kernel.
I noticed that when I had 128-998 set on boot, the phone wouldn't sleep properly, and the battery drain in standby mode was ~3x what it normally was.
The normal battery drain for my configuration is about 1% an hour in standby.
If you are running a different rom/kernel, I suppose, it's entirely possible not to see this problem. Test it yourself and find out.
I have had my Evo clocked at 128 for Min and Max for about a day. I initially thought the reports of uneven performance were wrong, but a few runs of Pandora during "Screen Off" did cause some long pauses and some FCs on a couple of occasions. I suspect this is why many recommend increasing the clock to 245, especially when you have process heavy apps running.
I personally don't think the difference in such low clocks will have a significant impact on battery life, but for those of you who get the warm and fuzzies from the absolute lowest setting, I have been playing with my Min @ 128 and Max increased to 245 for a couple of hours. It's jumping out of the low clock much smoother (I can immediately drag the lock bar down) and I haven't gotten any FCs while using Pandora with the screen off. I have ran Pandora with the Screen Off and the "adb shell powertop -d" from my terminal. It is reporting that my Evo is staying in the 128 clock, but, like I said, it's transitioning to higher clocks without a hitch when I turn it on.
Hope that helps.
I've also found that 128 is just too low for things to work properly. It stutters a lot when the screen comes on and things like music also stutter.
Having tested this for a little over 24 hours in response to the increased battery drain, I could not tell any additional battery drain still after 24 hours. On the flip side i could not tell of any additional battery saving either. At the end of the day i was in my normal range.
I do not use the Stock rom but do use Netarchy's latest kernel. So ti may just be a stock rom thing. I will agree that the screen comes on sluggishly and music will skip if you have it playing with the screen off. Since i was unable to tell any significant benefit from lowering it i will be stick to 284.
I prefer screen off profile to scale down to 285mhz as opposed to 128mhz. I know the clock differences are minute, but the phone feels more responsive and ready for action when woken up at 285mhz. You can feel the 128mhz drag.
Due to some of the instability I've gotten, I've decided to bump up the Min to 245. It runs much smoother and I cannot see a difference in battery life. I think the occasional lag and FCs that 128 might cause will hurt your battery life before the increase in clock will. I'm now with the "128 is not an option" camp.
scriptx said:
I prefer screen off profile to scale down to 285mhz as opposed to 128mhz. I know the clock differences are minute, but the phone feels more responsive and ready for action when woken up at 285mhz. You can feel the 128mhz drag.
Click to expand...
Click to collapse
What is your screen off profile, min/max? Obviously 285 is min, but what is your max? What about when the screen is on?
I have my screen off setting for 245 min & max. I get no stuttering pandora and it doesn't **** itself when I turn the screen on. The transition to normal is smooth.
I am getting over 40 hours on battery....
with the set-up in my signature below.......
I have Set CPU set to 245/128 with screen off. I get almost no drain with phone resting. Went to be last night and when I picked up my phone this AM, it was still on the same %. This has been consistent for the last 3 nights.
If you go to the baked snack rom thread, towards the last two pages as of today....I discuss my set up. Others are experiencing the same kind of battery results.
I get no hiccups from resting to on. Pandora plays fine. If it needs the 245 for Pandora or such, it's there. If not, it goes down to 125 and uses almost no battery over an extended period of time.
I just tried setting 128 as min and 245 as max for screen off and my phone got stuck in a boot loop. After sitting idle for a few minutes it started rebooting on its own.
I had to remove the battery and was then able to get into the OS. I have since set my phone back to 245 . I will update if I find out this was happening for another reason or if I try 120 again.
does anyone else is nexus get really hot when surfing the internet or doing anything else. I've only been using the phone for 15 minutes and it's already dropped 10 percent. idk its up to about 118 degrees
is this pretty common with this phone?
Clock speed
Usage
Screen brightness
Those affect how your gets.
Are u an aggressive user and clocked it up high and always have high brightness.
No only 15% brightness no over clock. New phone just got it today just seems to heat up asap...and gets over 110 degrees easily. The of course causes major battery drain. Prob normal for this phone just never experienced heat like this before
Isn't the processor on the Gnex designed to do a panic restart when it reaches 110 C's ? :/ yes its a big issue i've noticed that the phone doesn't get that hot when using stock Rom weird...
I don't get over 110 and I'm OCed to 1.3gHz, auto brightness on.
Sent from my Galaxy Nexus using Tapatalk 2
The only time mine gets abnormally hot is during a phone call. Im even underclocked and it still does.
getting hot in a smart phone this powerful is normal. I had the S3 for week, that sucker gets hot!
I agree with OP. Mine gets noticeably warm when scrolling through large non-mobile web sites. It cool when scrolling through apps like tapatalk, market, reader apps. It must be something to do with browser engine
Mine gets quite warm as well. Especially with games like gta 3 and Final Fantasy 3.
Sent from my Galaxy Nexus
please don't forget that you're holding a device with a dual core CPU, clocked at 1200 MHz, without fan, water-cooling or anything. ever tried touching a computer-cpu?
(don't do that, lol)
Mine can easily get to 110 degrees. It definitely has a heat issue. My Razr Maxx can get warm too, but not hot like this GNex. It hurts to palm sometimes !
LTE / Camera / Data stuff . / Charging all contributes to this.
Thank god it has removable battery, since battery life will be significantly dampened by heat.
Mine gets hot since Jelly Bean... Maybe "project butter" is intended to melt our phones like butter
remember, battery temp and cpu temp are two completely different things. cpu temp will get lowered automagically in the gnex when it reaches a certain point(heat throttling is enabled in the gnex, unless you disable it), and it will shut down the cpu when you reach 110C, not 110F, that is a safety feature. 110C is 230F btw.
Hi Everyone,
Just wondering how your Nexus 7 runs under the new OS? I notice my device getting higher temperature than before, especially when playing some games. For example, with CPUTEMP and Smash Hit, CPU's temp was around 50-55C on Kitkat but now it is 65-75 on Lollipop.
Would be great if someone can run the same test and see if you get high temperature on this game.
Thanks
I can attest to this myself. I use the same app (on a N5 and N7) and I've noticed that the feel in the hand, while doing normal stuff with the same usage pattern, seemed hotter than normal. So I launch the CPUTEMP app and run the overlay, put the N7 to sleep for 15 minutes to idle. Temp starts around 36 C when first turning on the screen, then it ramps up to 44 - 50. Then while actually using the device, (e.g. surfing the web, email, basic stuff) the temps will go up to the 50s and 60s easily. If I leave it at rest on the homescreen after using the tablet, it idles around the low to mid 40s. While video chatting online with someone (hangouts / skype / etc) it will ramp up to 70s, then 80s, and finally cap out at 95 C. (5 degrees before S4Pro SoC maximum?) A video chat will last 2 - 2.5 hours on a fully charged battery, and the heavy SoC throttling affects the frame rate / responsiveness of both my front / back camera preview during vid chat and the entire OS. Downloading an app or two brings the temp 55 - 61, and then installing them (due to AoT compile) from 61 to 72.
The same goes for my N5 also on Lollipop, to a lesser degree, but nonetheless, it runs higher average temps than I noticed while running KitKat. Both devices appear to drain battery quicker on Lollipop, especially during use. That's not even considering LTE / mobile data use, since these days I'm here at home using WiFi all the time.
lpachuong said:
Hi Everyone,
Just wondering how your Nexus 7 runs under the new OS? I notice my device getting higher temperature than before, especially when playing some games. For example, with CPUTEMP and Smash Hit, CPU's temp was around 50-55C on Kitkat but now it is 65-75 on Lollipop.
Would be great if someone can run the same test and see if you get high temperature on this game.
Thanks
Click to expand...
Click to collapse
Yes. You are correct. Even i face the same issue. The device gets heated even on playing candy crush / angry birds which was not the case with kitkat 4.4.4.
Hi there! I have a Galaxy Tab S4, as you can imagine. I use it as my gaming device. The only game I play is Rues Of Survival. And well, Among us, but I don't even take it into consideration as a demanding game.
The tablet is not rooted but I debloated it with adb as far as I could. Android 10 on board.
Probably this crappy game became so poorly optimized that the performance degraded over time.
Now I am at a point where it's pretty unplayable even if I lower the resolution.
Let's see what I have tried so far.
I have checked the usage of CPU, GPU, temp and FPS with the game launcher plug-in. I have an average of 60 FPS with an average CPU usage of 8% and an average GPU usage of 80%. The problem occurs during crowded scenes. The FPS drop to 30, making the whole thing sutter really hard, the CPU usage stays the same and the GPU usage drops to 60%. WHY THE HECK?!
I have tried a couple of different resolutions (the game does not specifically states to how many pixels correspond each d*mn option) with close to no improvements. The graphics got really ugly, obviously.
Should I try to root and disable DVFS? Should I root and lower the resolution of the whole tablet to a normal fullHD with terminal? Should I stop complaining? Should I quit playing? Should I get a new tablet?
It seems pretty absurd that a game that I was able to play on my Galaxy S6, now got so demanding. Or that a 500 euros tablet aged so badly in two years.
Are those 2 free GB of ram out of 4 not enough to handle the game?
I can play it quite flawlessly on my OnePlus Nord. But this is NOT an option. The hardware specs of the two devices should be comparable. What mostly changes are the screen resolution (lower on the OP Nord) and the ram size (double on the OP Nord).
I doesn't try that game, but I played others (pubg (highers settings), stardew valley, this war of mine... etc), and I have not had problems at all. I'm stock. Have you try game booster?
So I have found an odd and repeatable glitch that is a good glitch but I can't explain it. I play one primary game from the dragon quest series on my fold 4. The system app game tracker says I get on average 35 to 40 fps which is fine but one day I saw the game running super smooth and felt way faster. Sure enough it was running at 70fps the entire time. Cpu usage was up and gpu usage went from about 15% before to about 35%. No big deal for how beautiful the game looked and played. A few months went by and I never could repeat how I did this. Then this week I did it again and experimented to try to repeat. My game had to be in the foreground and I turned off the screen. You have to have the side button fingerprint reader set to read fingerprint without pushing the button. Once I did this and instantly turned on the screen and went to game then boom 70 fps speed and glory. The only downside is massive battery drain and if you do anything and I mean anything else but play the game it reverts back to 35 to 40 fps. You pull down the notification tray the fps drop. You have to stay in game don't adjust volume don't adjust brightness. If the frame rate drops from an incoming call then repeat screen off and finger print used again. So here come my questions... The device can clearly handle this 70 fps and I played 2 hours once without it getting too warm... I think I saw 105 degrees at most. I am guessing the fingerprint to unlock with screen off is happening so fast it doesn't give time for Samsungs system files to limit fps... Why do they do this crap? Why can't I choose max power or battery savings. Can anyone replicate what I see? Is there something else I can do to keep my 70 fps and still use my phone for other stuff? I want absolute max performance but not thru a weird glitch. I hope to hear from others.
I'm subscribing to this as I am curious also