Related
It sems there is a fps cap on our Desire HDs. In games and benchmarks, the limit seems to be around 59-60 fps. Is there any possible way to remove this? And yes, I know our screens are 60hz, but still...
Under ROM development as I understand it is something to do with kernels...
Sounds like v-sync is on. If that is the case and if it were turned off to allow more then 60fps you would get screen tearing and screen tearing looks terrible.
V-sync is a good thing, it keeps frames that are drawn in sync with the refresh rate of the screen.
There is no reason to turn it off, maybe the menus and stuff will be faster but definitely not smoother.
That's not always the case, my friend Generally i'm more interested to see what type of framerates this baby can hit!
Well that's true, in that case it will have to be turned off. In WinMo it was a matter of changing a registry entry but on Android probably more complicated. Like you mentioned, a modified kernel most probably.
I would actually be interested aswell in seeing what this beast can do to.
Hmmm...me ad my friend were experimemting around with our phones, I have a Desire Hd and he has a Galaxy S....generally Galaxy S is more powerful in 3D graphics. However, even though he built a custom gingerbread rom, my cpu was faster (quadrant rated mine 6600 at 998mhz vs his at 1024 mhz giving 5400). Another interesting find was that overclocking q hummingbird decreases gpu performance to speed up cpu operations. I assume the gpu is underclocked to provide more power to the cpu. However, at extremes (1.6ghz) it seems his gpu also overclocks, thus crashing the system. I was thinking if it were possible to overclock the gpu on a desire hd, or at least reroute power from the cpu to the gpu via software codes...
Note: contains theoretical assumptions
Hello,
I have gotten this MHL adapter for my Note 2 about 2 weeks ago and it works decently. The problem I have noticed is that when I play GTA 3 or GTA Vice City is that the framerates seem a bit jerky to me. Im not sure if its just me or if its the mhl or if anyone else has this problem. Is there anything I can do to fix it?
http://www.amazon.com/gp/product/B009MJ58OI/ref=oh_details_o02_s00_i00
Dear X-dude,
Same here...
No problem with videos or other apps but games have less framerates when using mhl... I am not satisfied with the performance of game playing using mhl and sixaxis controller on TV Screen... Couldnt find a solution till now... I had same problem with Note1 also...
Kind regards...
Sent from my Amiga Note
MHL is not 'up to par' when playing video games, the fps just can't keep up. Playing videos though will work excellent! I use my N2 all the time to stream and play videos and music on my HDTV, looks and sounds amazing! Video games...not so good....
its not the MHL that is the problem.
the problem is the fact that the device is running in mirror mode. if you're running the TV at 720p as well as the phone at 720p, that means that the GPU now has to render twice as many pixels (ie. 1843200 pixels instead of 921600 pixels). it only gets worse if you run 1080p as it will have to render a little over three times as many pixels. doing that is far too demanding for our overclocked mali400 GPU, which is one of the reasons why it lags.
basically, the only device available at the moment that would have reasonable framerates in mirror mode based on GPU power alone would be the ipad 4th gen. i personally dont like ipads, but hardware wise, they do have a beefy GPU. the adreno 320 can keep up well enough, but isnt quite as quick as the powervr chip.
the malit604 might be able to do it if samsung can optimise the driver if they use it in the s4 next year, but at the moment, the performance of the mali 604 isnt much faster than the adreno 320.
Souai said:
sigh... its not the MHL that is the problem.
the problem is the fact that the device is running in mirror mode. if you're running the TV at 720p as well as the phone at 720p, that means that the GPU now has to render twice as many pixels (ie. 1843200 pixels instead of 921600 pixels). it only gets worse if you run 1080p as it will have to render a little over three times as many pixels. doing that is far too demanding for our overclocked mali400 GPU, which is one of the reasons why it lags.
basically, the only device available at the moment that would have reasonable framerates in mirror mode based on GPU power alone would be the ipad 4th gen. i personally dont like ipads, but hardware wise, they do have a beefy GPU. the adreno 320 can keep up well enough, but isnt quite as quick as the powervr chip.
the malit604 might be able to do it if samsung can optimise the driver if they use it in the s4 next year, but at the moment, the performance of the mali 604 isnt much faster than the adreno 320.
Click to expand...
Click to collapse
That makes sense. Glad it wasn't just me. Thanks!
Souai said:
its not the MHL that is the problem.
the problem is the fact that the device is running in mirror mode. if you're running the TV at 720p as well as the phone at 720p, that means that the GPU now has to render twice as many pixels (ie. 1843200 pixels instead of 921600 pixels). it only gets worse if you run 1080p as it will have to render a little over three times as many pixels. doing that is far too demanding for our overclocked mali400 GPU, which is one of the reasons why it lags.
basically, the only device available at the moment that would have reasonable framerates in mirror mode based on GPU power alone would be the ipad 4th gen. i personally dont like ipads, but hardware wise, they do have a beefy GPU. the adreno 320 can keep up well enough, but isnt quite as quick as the powervr chip.
the malit604 might be able to do it if samsung can optimise the driver if they use it in the s4 next year, but at the moment, the performance of the mali 604 isnt much faster than the adreno 320.
Click to expand...
Click to collapse
That doesn't make any sense.
Mirroring in that case = Output twice what GPU rendered once. Mirroring isn't involving any extra work to GPU, (not sure about 1080p output, but i guess that all rendered in 1080p instead of 720p then downscales to fit the screen of device, performance-wise its only a tiny amount worse than having 1080p screen on device). But any output (and MHL is included) has latency, when you output videos it is not noticeably because you don't interact with videos, but when playing dynamic game you'll start to notice lag between interaction and game react to it.
It is only applicable to Mirror output, extended screen surely will take part of GPU perfomance, but not half of that - it is depending on what you doing. 3D games is involving much more computing than several layers of 2D in android interface or media player.
Need some technically adequate investigation on FPS drop and MHL latency
mgrviper said:
That doesn't make any sense.
Mirroring in that case = Output twice what GPU rendered once. Mirroring isn't involving any extra work to GPU, (not sure about 1080p output, but i guess that all rendered in 1080p instead of 720p then downscales to fit the screen of device, performance-wise its only a tiny amount worse than having 1080p screen on device). But any output (and MHL is included) has latency, when you output videos it is not noticeably because you don't interact with videos, but when playing dynamic game you'll start to notice lag between interaction and game react to it.
It is only applicable to Mirror output, extended screen surely will take part of GPU perfomance, but not half of that - it is depending on what you doing. 3D games is involving much more computing than several layers of 2D in android interface or media player.
Need some technically adequate investigation on FPS drop and MHL latency
Click to expand...
Click to collapse
Interesting. So there isnt much to do then to increase framerates on games?
Not sure where I read this at, but I was sure to have came across someone saying that the 1080p output is only at 30hz.
xartic12 said:
Not sure where I read this at, but I was sure to have came across someone saying that the 1080p output is only at 30hz.
Click to expand...
Click to collapse
I also heard something about that and does the 30hz cause dropped frames? Also im pretty sure my mhl outputs at 1080i and not 1080p which makes a difference?
1080i is the culprit.
GNoteII
mgrviper said:
That doesn't make any sense.
Mirroring in that case = Output twice what GPU rendeWhenred once. Mirroring isn't involving any extra work to GPU, (not sure about 1080p output, but i guess that all rendered in 1080p instead of 720p then downscales to fit the screen of device, performance-wise its only a tiny amount worse than having 1080p screen on device). But any output (and MHL is included) has latency, when you output videos it is not noticeably because you don't interact with videos, but when playing dynamic game you'll start to notice lag between interaction and game react to it.
It is only applicable to Mirror output, extended screen surely will take part of GPU perfomance, but not half of that - it is depending on what you doing. 3D games is involving much more computing than several layers of 2D in android interface or media player.
Need some technically adequate investigation on FPS drop and MHL latency
Click to expand...
Click to collapse
Souai is right. If you would like a demonstration, do the following. Install the Electopia game/benchmark. When you start the app you will be asked if you want to run it in WVGA resolution or full screen. Try WVGA first. On the next screen choose 'benchmark' mode. Let it run then note what FPS you scored. Next run the benchmark again in full screen mode and note the (lower) FPS. Next, plug your phone into your tv using MHL and run both benchmarks again and note the lower FPS scores.....see? When plugged into a tv via MHL it is having to work much harder.
Ouzo said:
Souai is right. If you would like a demonstration, do the following. Install the Electopia game/benchmark. When you start the app you will be asked if you want to run it in WVGA resolution or full screen. Try WVGA first. On the next screen choose 'benchmark' mode. Let it run then note what FPS you scored. Next run the benchmark again in full screen mode and note the (lower) FPS. Next, plug your phone into your tv using MHL and run both benchmarks again and note the lower FPS scores.....see? When plugged into a tv via MHL it is having to work much harder.
Click to expand...
Click to collapse
Interesting indeed. I will try this soon.
Hey guys!
I just wanted to know if scaling down the screen resolution has any impact on the battery life. All of you who have scaled it down, is there any significant improvement in the battery life?
Sent from my LG-D855 using xda premium
There is an battery improvement but some Apps look horrible with This solution. I am back to 1440p and give a f**k about these 1 or 2 hours.
Der CaRl said:
There is an battery improvement but some Apps look horrible with This solution. I am back to 1440p and give a f**k about these 1 or 2 hours.
Click to expand...
Click to collapse
Is that 1-2 hours of SOT, or just usage?
This would all depend on the way you use your phone.
A. If you're a heavy user, (games & movies n stuff) then lower resolutions would benifit tons.
B. If you're a light user, (texts & emails n stuff) then the higher resolutions are very efficent.
There is a common misconception going around about this screen requiring alot of power.
The screen isn't what is draining the device so bad, it's the gpu powering the immense amount of pixels that is causing the power drain.
Now taking that into consideration, there is 3 things to keep in mind.
1. You're still lighting up 3,686,400 mini lightbulbs (aka pixels) no matter what resolution you run at.
2. Lower resolutions = less power draw from the gpu, mostly when the gpu is under higher loads.
3. The gpu doesn't require much power while under lighter loads
So to sum it up
Higher resolution + Very graphic intensive = Heavy power draw from the gpu
Lower resolution + Very graphic intensive = Medium power draw from the gpu
Higher resolution + Not graphic intensive = Low power draw from the gpu
Lower resolution + Not graphic intensive = Low power draw from the gpu
As you can see, under lighter loads 2560x1440 is extremly efficent and preferable by myself, but under heavier loads (games and stuff) 1920x1080 is far more power efficent on the gpu (if your games will even run), once we get a custom kernel for our phones a slight gpu underclock would be MUCH more effective than lowering your resolution.
All this talk of lowering the resolution to save power is rubbish, it doesn't work. Its just a placebo.
By far the biggest cause of drain on the battery from the screen is the backlight, not the resolution. Changing it to a lower resolution doesnt actually change anything, the GPU isnt even trying even at 1440P, it never scales past the second step (330MHz) in 2D. The only thing stopping the GPU from being able to display 4K or even 8K is the bandwidth, not the GPUs power. 2D is effortless for the GPU.
If you reduce the resolution to 1080P the GPU has to rescale that image to 1440P in order to fill the screen (the actual screen resolution is fixed and cannot be changed). All this does is add an extra layer of processing and costs you processor cycles.
In games this changes somewhat, but the effect isnt as big as some like to think. The GPU is still memory bandwidth limited in 3D even at 1440P, not power limited. To prove the point in Basemark X the G3 scores higher than the N5 and almost as high as the M8 and S5, despite having double the pixels.
I bought it for the resolution.. I'm not turning it down.. Otherwise I would have just bought an S5 Or a freeking iphone lmfao
---------- Post added at 08:32 PM ---------- Previous post was at 08:30 PM ----------
At 47% now 10hr usage 2hr SOT.... ESTIMATED 8HRS LEFT..
Hi there. I have tweaked my phone for extra battery life (custom ROM, kernel, undervolting and multicore power saving) and I would also like to improve performance further more without reducing battery life.
The g3 has a 2560x1440 display or something ridiculously high like that. Its practically the double of 1080p. My PC monitor is 24 inch and has a 1080p resolution. Even though without antialising I can see pixels, its still pretty good. In my opinion, 2560x1440 is way too high for a 5.5 inch screen.
Since 2560x1440 is the double of 1920x1080, reducing the resolution should greatly improve performance. http://www.phonearena.com/news/We-c...and-negligible-battery-life-increases_id65982
However, resolution changer pro and NOMone resolution changer either do not work or cause a bootloot on blisspop 3.6.
Does anyone know of any similar ROMs or alternative apps that will work with blisspop?
Thanks!
Sent from my LG-D855 using XDA Free mobile app
tristan6100 said:
Hi there. I have tweaked my phone for extra battery life (custom ROM, kernel, undervolting and multicore power saving) and I would also like to improve performance further more without reducing battery life.
The g3 has a 2560x1440 display or something ridiculously high like that. Its practically the double of 1080p. My PC monitor is 24 inch and has a 1080p resolution. Even though without antialising I can see pixels, its still pretty good. In my opinion, 2560x1440 is way too high for a 5.5 inch screen.
Since 2560x1440 is the double of 1920x1080, reducing the resolution should greatly improve performance. http://www.phonearena.com/news/We-c...and-negligible-battery-life-increases_id65982
However, resolution changer pro and NOMone resolution changer either do not work or cause a bootloot on blisspop 3.6.
Does anyone know of any similar ROMs or alternative apps that will work with blisspop?
Thanks!
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
Decreasing the resolution will certainly increase performance and is also helping me to get the rid of the heating issues that I have faced on my G3. Resolution Changer Power Menu would help to decrease resolution efficiently. But I am not sure how much it would work with blisspop .
@tristan6100 hi. you can change the resolution manually using terminal:
su
wm size your_size
wm density your_density
if something fails you can try:
su
wm size reset
wm density reset
The settings allow you to lower the resolution. I lowered the resolution to 2340 x 1080 and I don't really notice anything different.... Would this increase battery life? If so, how much?
It will definitely increase battery life.
How much will it increase depends on your usage and your apps installed. It should at max give you 10% increase.
id3alistic said:
Would this increase battery life? If so, how much?
Click to expand...
Click to collapse
It is well and widely known that lowering resolution won't give you increased battery life. At all
Ah thanks. I come from an xperia z3 so been using FHD screens only. I was interested in the XZ1 compact back then and one of the key points from reviewers is that the lower screen resolution(720p) saved a lot more battery vs the XZ1 at 1080p.
id3alistic said:
Ah thanks. I come from an xperia z3 so been using FHD screens only. I was interested in the XZ1 compact back then and one of the key points from reviewers is that the lower screen resolution(720p) saved a lot more battery vs the XZ1 at 1080p.
Click to expand...
Click to collapse
I think the misconception is lowering the screen resolution vs a device that maxes out at a lower resolution. Maybe it makes a difference for OLEDs...but for LCD screens, all if the pixels are still illuminated, so there's not much difference there.
AarSyl said:
I think the misconception is lowering the screen resolution vs a device that maxes out at a lower resolution. Maybe it makes a difference for OLEDs...but for LCD screens, all if the pixels are still illuminated, so there's not much difference there.
Click to expand...
Click to collapse
Sounds convincing and makes sense. I wonder why they'd allow it on this device though?
20degrees said:
Sounds convincing and makes sense. I wonder why they'd allow it on this device though?
Click to expand...
Click to collapse
Because Samsung's can do it.
Nothing but hype for the misinformed and ill-advised.
[Dopey voice]"Bruh...look what my phone can do to save battery life. Can yours?" [/Dopey voice]
Using lower resolutions use less power bc they use less gpu computational power. Youre not saving anything really from the screen itself. Think of it this way does your computer/laptop use more power running resource intensive applications or running idle?
id3alistic said:
Ah thanks. I come from an xperia z3 so been using FHD screens only. I was interested in the XZ1 compact back then and one of the key points from reviewers is that the lower screen resolution(720p) saved a lot more battery vs the XZ1 at 1080p.
Click to expand...
Click to collapse
As one said here it's from misinformed people.
id3alistic said:
XZ1 compact back then and one of the key points from reviewers is that the lower screen resolution(720p) saved.
Click to expand...
Click to collapse
Not that the resolution that saved power. If Sony could put their 3840x2160 resolution display into 4.3" size of XZ1 compact it still would run longer on battery than any 6.5" sized phone from similar battery even with 720p display. Because it's sheer size of screen that saves battery, not the resolution. 4.3" vs 6.5" is hefty difference. One needs more light to make 6.5" display emit light than to make 4.3" one hence one need more power.
Think about it this way, if resolution would matter then XZ Premium and XZ2 Premium would drain their batteries in a matter of minutes with 3840x2160 res displays. Right? But they work almost as long as say Galaxy S9 Plus or Note 8.
---------- Post added at 07:58 PM ---------- Previous post was at 07:52 PM ----------
Nirrik said:
Think of it this way does your computer/laptop use more power running resource intensive applications or running idle?
Click to expand...
Click to collapse
It not works like that. When your phone renders picture in 720p or 1080p it doesn't do it sitting idle. It still consumes power when rendering picture 60 times a sec. And its GPU still runs at 200MHz, maybe it needs like 230 or 250MHz for rendering picture in 1440p but is 250MHz vs 200 MHz a huge difference? I doubt it
It's not like 1440 picture rendering needs full GPU power but 720p or 1080p can be powered by idle GPU. Never was, never will. Ask devs in http://forum.xda-developers.com/android/software-hacking if in doubt
In reality ability to pick your resolution for battery life is a gimmick and doesn't really do anything.
There were no proofs that phones live longer from same charge when it's resolution lowered. Maybe it works for constant gaming, like playing games in 720p on a 1440p screen will bump battery life. But in other cases no
Taking only power consumption from the display alone, there is no different between HD, FHQ, QHD. The different is that if a game or any apps(or even system app itselfs) runs at HD, it will need less graphic computational power than running at QHD (once again, its not about the drainage from the display, its from GPU).
romeokk said:
The different is that if a game or any apps(or even system app itselfs) runs at HD, it will need less graphic computational power than running at QHD (once again, its not about the drainage from the display, its from GPU).
Click to expand...
Click to collapse
in reality, it's bull****. learn how GPU works. Try to ask Google devs if you don't know. They do habitate here, at XDA
It's not like it renders something and then goes to sleep turning cores off as CPU does. Instead GPU renders frame 60 times a sec and uses 203MHz either your resolution is 720p or 1080p. It can't lower frequency to 100MHz magically because it's not designed that way. So it consumes as much power working at 203MHz either rendering 720p frames or rendering 1080p frames.
Hence no battery economy achieved
Billy Madison said:
in reality, it's bull****. learn how GPU works. Try to ask Google devs if you don't know. They do habitate here, at XDA
It's not like it renders something and then goes to sleep turning cores off as CPU does. Instead GPU renders frame 60 times a sec and uses 203MHz either your resolution is 720p or 1080p. It can't lower frequency to 100MHz magically because it's not designed that way. So it consumes as much power working at 203MHz either rendering 720p frames or rendering 1080p frames.
Hence no battery economy achieved
Click to expand...
Click to collapse
See this:
https://www.google.co.th/url?sa=t&s...FjADegQIBRAB&usg=AOvVaw3qEXVbk4h0XmHcDhhRUR1P