Related
I've heard/read that ONLY honeycomb makes use of the dual core.
So what's the advantage of having a dual core phone running gingerbread?
Nvm I found some information.
Sry for makimg a new useless topic
Where did you find the information?
Please post the Link!
All of the information I've read shows that Ice Cream should be the build with this integrated.
It's somewhat baffling that it's taken this long considering that for the average phone user, how smooth the phone is plays a huge part in whether they like it or not.
iOS has had GPU UI acceleration since its inception, how have the Android team members let this slide? Is it simply because the implementation requires a massive structural re-write?
Tossing the 2D UI acceleration over to the GPU should theoretically increase the speed of the OS as well, since it frees up the CPU to focus on its own tasks.
MustWarnothers said:
iOS has had GPU UI acceleration since its inception, how have the Android team members let this slide? Is it simply because the implementation requires a massive structural re-write?
Tossing the 2D UI acceleration over to the GPU should theoretically increase the speed of the OS as well, since it frees up the CPU to focus on its own tasks.
Click to expand...
Click to collapse
Caching is primarily what makes it so smooth on the iPhone, not GPU acceleration; though that helps a fair amount, also. The lack of heavy use of caching everything in the UI for what seems like all Android UIs is what has baffled me about Android UIs. Home screen launcher replacements like LauncherPro use it, and it makes everything nice and silky smooth. I've honestly been thinking that most UI designers for the hardware companies simply do not know what they are doing.
MustWarnothers said:
All of the information I've read shows that Ice Cream should be the build with this integrated.
It's somewhat baffling that it's taken this long considering that for the average phone user, how smooth the phone is plays a huge part in whether they like it or not.
iOS has had GPU UI acceleration since its inception, how have the Android team members let this slide? Is it simply because the implementation requires a massive structural re-write?
Tossing the 2D UI acceleration over to the GPU should theoretically increase the speed of the OS as well, since it frees up the CPU to focus on its own tasks.
Click to expand...
Click to collapse
it's not that simple...ios is missing a lot of features. i read that it doesn't support java and just object-oriented C++.
Since android was started, phone developers have pushed it in directions that Google didn't originally plan for. That's why the nexus s only had single core, and afaik, all the dual core phones have software on top of android to manage the dual core processing, which doesn't really do much for them. yes they're faster, but i think not as fast as they could/should be.
i'm assuming the next nexus will be a dual core, and with android that has support for them. if so, it'd blow all dual cores away to this point, because processor management is more efficient the lower in the stack it's handled.
however, what with the nexus s 4g being recently released, i'm not expecting the next nexus to be around anytime soon as G focus on tablets.
Since the SGS2 is so fast for web browsing and flash content, as well as UI, what type of magic do they do if they aren't altering the basic Android system? Does it involve using dual-core? How specific are the Samsung optimizations and are they low-level enough for Google to say this would be great in Ice Cream and thus steal that optimization from them? Is TouchWiz actually faster than stock Android? Or is that impossible since it is built on top of Android? Will the browser speed translate to other installed browsers, or is it specific to the stock browser? I really don't know how far Samsung or any other manufacturer can customize the software beyond just superficial skins and whether or not deep customizations change the system fundamentally and possibly break certain apps.
I didn't really investigate this issue deeply, but I think it works out like this:
Right now, the android sdk (2.3) provides no means to use more than one CPU core.
Still, multicore CPUs will increase performance because background processes can use CPU time on the core not being used by the running app.
This also applies to garbage collection (GC) which happens periodically (I guess you can trigger it manually too) whilst an app is running. With more than one core, the GC won't block the app which makes it feel "smoother".
I remember reading about Google's plans to improve multicore-support in android 2.4. It will take some time for existing apps to use it though (like it's happened with desktop applications).
Then just imagine the performance of the SGS II device with hardware acceleration support.
MustWarnothers said:
All of the information I've read shows that Ice Cream should be the build with this integrated.
It's somewhat baffling that it's taken this long considering that for the average phone user, how smooth the phone is plays a huge part in whether they like it or not.
iOS has had GPU UI acceleration since its inception, how have the Android team members let this slide? Is it simply because the implementation requires a massive structural re-write?
Click to expand...
Click to collapse
Since Honeycomb utilizes GPU for UI rendering, I guess it will be available on Ice Cream too.
Android is handicapped by the big range of hardware used by manufacturers. Some GPUs are simply too slow or have other issues which will make GPU acceleration fail. This is not an issue for Apple, because there is no hardware choice on iOS.
silverwolf0 said:
Since the SGS2 is so fast for web browsing and flash content, as well as UI, what type of magic do they do if they aren't altering the basic Android system? Does it involve using dual-core? How specific are the Samsung optimizations and are they low-level enough for Google to say this would be great in Ice Cream and thus steal that optimization from them? Is TouchWiz actually faster than stock Android? Or is that impossible since it is built on top of Android? Will the browser speed translate to other installed browsers, or is it specific to the stock browser? I really don't know how far Samsung or any other manufacturer can customize the software beyond just superficial skins and whether or not deep customizations change the system fundamentally and possibly break certain apps.
Click to expand...
Click to collapse
All parts of android (2.3) are open sourced, so Samsung can customize anything they want. They don't have to release the changed version as open source though (except for the GPLed parts, like the kernel) - so we'll probably never know what they've been doing.
german wikipedia says that gingerbread 2.3.3 features dual-core support ...
Link it please, thats odd.
My German is bad as I only read it for a couple of year but here is the Wikipedia page http://de.wikipedia.org/wiki/Android_(Betriebssystem)
At the bottom you have "Dual-Core-Unterstützung" on 2.3.3 which means it support it.
But as always Wikipedia is never 100% correct so who know
I read that they will re-release a gingerbread version (2.4?) that will take advantage of Dual-core apps. So basically, they add dual-core support and it will also still be gingerbread but version 2.4 of android.
Come to think of it, they did the same thing with Eclair (2.0 and 2.1) already.
Hope this helps
I think they have already done that with "Gingerbread 2.3.3", Instead of calling v 2.4 GINGERBREAD as well, they made the changes in "Gingerbread" and gave it versioning 2.3.3.
Thats what it looks like all on Wikipedia pages. Highlights 2.3.3 as a Major release.
Yes, the wiki says that dual-cores are supported from 2.3.3 and it says too that dual-core-apps are supported on single-core smartphones! --> Thats an indication for real dual-core support!
I'm just waiting for when Android decides to implement GPU UI acceleration.
Even if apps are offered dual core support, if both of those cores are still working on UI animations instead of tossing it to the GPU, it seems like 3 steps forward, 2 steps back.
As I understand it, Gingerbread (2.3) offers limited dual-core support. If your phone has a 2nd core available, then it will move the Garbage Collector onto the 2nd core which means there will be a lot less lag in applications and games when the GC fires off to remove unused resources.
http:/ /developer.android.com/sdk/android-2.3-highlights.html
It's under the 'enhancements to games' section I believe.
Honeycomb (3.0) offers full UI hardware acceleration and makes full use of both cores - so wait for Ice Cream to come to phones and it will be fully supported.
I know that wikipedia isnt always right but if i assume that it is right this time it says that what you just wrote Xailter was integrated in 2.3 and real dual-core support in 2.3.3 :
2.3 features:
Linux-Kernel 2.6.35.7
Unterstützung von WebM
Unterstützung von HTML5 Audio [31]
Unterstützung von Google TV
Unterstützung von Near Field Communication
Parallele Garbage Collection für ruckelfreiere Animationen
verbesserte Integration von sozialen Netzwerken
Unterstützung von Gyroskopen (nicht zu verwechseln mit Bewegungssensoren) und anderen Sensoren (u.a. Barometer, Schwerkraftsensor)[32]
Integrierter SIP-Client für VoIP[33]
Integrierter Downloadmanager[33]
Unterstützung des Ext4-Dateisystems[34]
translated something like "parallel garbage collection for smoother animations"
while 2.3.3 features:
Dual-Core-Unterstützung
Unterstützung von Dual-Core-Apps auf Single-Core-Geräten
verbesserte Unterstützung der NFC-Technik
verbesserte Bluetooth-Unterstützung
kleinere Verbesserungen
which means dual-core support
support for dual-core apps on single-core-devices
improved support of nfc
improved support for bluetooth
minor improvements
if we can believe in what wikipedia says ... 2.3.3 features dual-core support
and i think it is true because it would just make sense to support the hardware that is releasing right now
source: de. wikipedia. org/wiki/Android_%28Betriebssystem%29#Versionsverlauf
sry for the spaces .. but i'm not allowed to post outside links
hey all,
first: sorry for my bad english..
i love android for example being open source (and so having the ability for custom roms)... and for much more. but NOT for being not perfect smooth. most android devices do not have fully hardware acceleration/gpu acceleration. when you compare the S2 with an iphone 4 or iphone 4s or lumia 900 you will realize, that the s2 is smooth, but not so butter-smooth as the iphone or new windows phones. the iphone and the new windows phones (e.g. lumia 900) have fully working/fully enabled hardware acceleration/gpu rendering.
now in the new ice cream sandwich build there is an OPTION (only option, not enabled by default) for complete gpu rendering. this option is missing or not enabled in the new android 4.03 leaks of the S2 samsung firmware. i dont get it why google does not force all new firmware to enable this very very nice feature by default. in my option it should be enabled about 1 year ago.. i love android, but from an objective point of view, IOS and the new windows phone software is much smoother.
http://www.youtube.com/watch?v=SKV39MPZw30
watch the video and you will see the difference. i hope it will be the new standard and will be fully enabled in all upcomping android firmwares. will i be satisfied?!
sorry for my bad english!
As devices are made for ICS you'll see better GPU acceleration. Older devices with unofficial ICS builds may never run as smooth due to driver/kernel limitations. Personally I find Android plenty smooth, but I would rather have functionality than aesthetics. I turn off all the app drawer animations, etc since they waste computing power and delay transitions.
Chances are there will always be low end phones that can't handle the graphics that well. When Windows debuted aero many low end systems couldn't run it. In a more closed eco system like iPhone or Windows Phone minimum hardware requirements are established so the experience is nice. Android leaves the minimum requirements up to the manufacturer.
So you mean with better GPU acceleration that GPU or hardware acceleration will be partly or fully enabled? should be fully enabled in the future...
Sent from my HTC Desire using XDA App
Evil_enc said:
hey all,
first: sorry for my bad english..
i love android for example being open source (and so having the ability for custom roms)... and for much more. but NOT for being not perfect smooth. most android devices do not have fully hardware acceleration/gpu acceleration. when you compare the S2 with an iphone 4 or iphone 4s or lumia 900 you will realize, that the s2 is smooth, but not so butter-smooth as the iphone or new windows phones. the iphone and the new windows phones (e.g. lumia 900) have fully working/fully enabled hardware acceleration/gpu rendering.
now in the new ice cream sandwich build there is an OPTION (only option, not enabled by default) for complete gpu rendering. this option is missing or not enabled in the new android 4.03 leaks of the S2 samsung firmware. i dont get it why google does not force all new firmware to enable this very very nice feature by default. in my option it should be enabled about 1 year ago.. i love android, but from an objective point of view, IOS and the new windows phone software is much smoother.
http://www.youtube.com/watch?v=SKV39MPZw30
watch the video and you will see the difference. i hope it will be the new standard and will be fully enabled in all upcomping android firmwares. will i be satisfied?!
sorry for my bad english!
Click to expand...
Click to collapse
Dood its not quite as simple as you think. Just enabling global GPU acceleration is not guaranteed to always give UI speed benefits. Due to complex interaction between soft/hardware components & bottlenecks , in fact on some configs it can definitely slow UI down.
Also on a mobile device you have to consider more issues than just pure UI speed, battery life is definitely more of an issue to consumers.
Battery life is supposed to be better with hardware acceleration/GPU rendering, yeah?
of course lower consumption by hw render because it lowered cpu usage
*********
I've read on several ROM forums that only certain apps utilize or dual cores. go to sys/devices/system/cpu/cpu1 there is a file there. When using one of the above said apps it populated cpu1 with freq folders etc, changes that one file from 0 to 1 enabling it. without one if these apps there is no freq tables for cpu1.
****my question: using Linux and cpu i ran speed tests. Over 70 tests in total. There is zero performance difference in using one app versus another versus cm performance cpu menu. I understand how it looks like two cores are only utilized from certain apps looking at the folders. However it does not change performance at all. Tests show same speed any way to control cpu. Also feels the same. Is there really a difference our is it monkey say????
Also in my tests i found using "VR" versus sio or noob or cfq to be the fastest. I didn't feel a difference however changing i/o setting.
Sent from my SGH-I717 using xda premium
Their are claims that Intel’s internal handset testing has shown multi-core implementations running slower than single core, however they did not cite any particular chip. If you take a look a lot of handsets on the market, when you turn on the second core or having the second core there [on die], the [current] leakage is high enough and their power threshold is low enough because of the size of the case that it isn’t entirely clear you get much of a benefit to turning the second core on. In some of the use cases they cited, having a second core is actually a detriment, because of the way some of the software engineers have not implemented their thread scheduling properly.......
That being said, one could argue the concept that a single core chip, running a slight overclock, would produce a far better result, than a dual core application. But again, thread scheduling detracts from any governor efforts anyway...IMHO....g
Hum. I would have to agree then that in our case and in my tests dual core doesn't help nor hinder performance results but does appear to reduce battery life. Now these are my tests using two different programs to test performance and using combo of setcpu/system pro/Cm10 performance built in/Tasker to control cpu. I have done enough testing to know that on cm10 roms dual core, or so the sys files indicate, is of zero performance upgrade and appears to drain battery faster.
Sent from my SGH-I717 using xda premium
Yes ...I agree with your findings.
I suppose it's safe too say then, when using the AOSP rom source, within it's normal configuration, that unless development is done beyond the current schedules, the stated performance is well ....overstated ??
Of course , CM is in a constant state of change, and I suppose that after they are finished with the functional repairs, they may focus more on the kernel.
I'd be very interested to see your same tests against another kernel, say flappjaxxx latest JB build.
I do know that he, and several other developers have made some great improvements to the source kernels, and although there will likely always be bugs present, after running my own evaluation of them, the governors are functional and do make at least a perceived difference.
But as you stated, albeit at the cost of battery life.
I choose not to overclock, as I feel that the marginal reward , as proven by your testing , and by testing from several reputable sources, is simply not worth the risk ...g
I agree Greg, i will test other kernels... Samsung ROM is probably the only one i won't test... I also don't overclock, i do under clock at work and screen off using Tasker for battery life. That does help greatly. I'll post back after testing different kernels tonight.
Sent from my SGH-I717 using xda premium
troyolson92 said:
I agree Greg, i will test other kernels... Samsung ROM is probably the only one i won't test... I also don't overclock, i do under clock at work and screen off using Tasker for battery life. That does help greatly. I'll post back after testing different kernels tonight.
Sent from my SGH-I717 using xda premium
Click to expand...
Click to collapse
Excellent....
And I suppose, since this is the Premier development site, that it would be of great value to the community if you could perhaps publish your results here ?
These aspects of the android OS have been of great interest to me for some time.
Without doubt, many other users would enjoy this information as well in forming their decision regarding roms, kernels etcetera.
Thanks to you, for your inspiring thread. I look forward to the forthcoming information ....g
Ok with out posting tons of pics i tested all available kernels (new). Results were the same. No real difference in single core versus dual core...
The following pics show how to know whether the second core is online or not and my results and how i tested this time around... I was more through the first time but results the same.
Sent from my SGH-I717 using xda premium
troyolson92 said:
Ok with out posting tons of pics i tested all available kernels (new). Results were the same. No real difference in single core versus dual core...
The following pics show how to know whether the second core is online or not and my results and how i tested this time around... I was more through the first time but results the same.
Sent from my SGH-I717 using xda premium
Click to expand...
Click to collapse
I am posting pictures for first time hope this turns out.
What do you use to disable the second core? Read this with some interest. Would like to try this with ics Rom. With oc'ing fRom 1.56 to 1.72 i see a consistent jump of 300-400 in my antutu scores. Currently on flapjaxx ics b4.
I know it is just a score, but is your score indicative of the cm builds? It just seems really low.
Here is my 'stock 1.56 speed' with ondemand governor. Want to a get a single core sample.to compare with it.
How interesting ....
I can say that both of your posted results lead toward our initial assumptions, that indeed we are seeing a consistent draw against the systems cores with little or no improvement upon activation of the second core.
Some Time ago, shortly after my note arrived, I began some simple tests with low speed dual core activation. My thought process was simply this.
Slow speed dual core operation (both cores running in the 650mhz range ) would ideally produce a faster process response.
My initial results were favorable, as I had a noticeably quicker device during screen transitions, and even in several multitasking functions.
I even went so far as to create a small script to handle this function for me. I'm no developer, and ultimately I didn't possess the programming skills I needed to complete and implement my script into an actual, flash worthy modification. And based on what we are seeing here , the results provided would indicate that my attempt is flawed due to chip current leakage, if the cores are allowed to ramp to high, and perhaps even the use of improper source schedule interference.
I'm so busy these days, I simply haven't time to explore the low speed theory further at this point.
But perhaps with your test bench already set, a simple test using my concept could be carried out??
As we know, CPU [current] thresholds are plagued by voltage bleeding at maximum CPU frequencies, but the thought has just occurred to me that [current ] bleeding is highly controllable when the CPU is driven at lower voltage inputs. And too combine a reduced frequency with reduced voltage over a multiple core platform, could, or should balance the loss and equal the output levels.
Are you up for another test ??
If so ....I suggest the following parameters.
Core "0" at 600/700 MHz
Core "1" at 600/700 MHz
Governor at "interactive "
Voltage at "-24Mv"
Then we'll see if the theory holds water.
P.S. thanks gents, I'm enjoying the heck out of this thread ......g
Mad383max, look at your folders from my pics to tell if two cores are running. Typically on after market roms one core is running until you enable the second from other software like from my pics.
Will test at lunch. I like this lower voltage idea. If i were a betting man i would guess with speeds you proposed and two cores i would guess similar to higher results. Let's see....
Sent from my SGH-I717 using xda premium
troyolson92 said:
Mad383max, look at your folders from my pics to tell if two cores are running. Typically on after market roms one core is running until you enable the second from other software like from my pics.
Will test at lunch. I like this lower voltage idea. If i were a betting man i would guess with speeds you proposed and two cores i would guess similar to higher results. Let's see....
Sent from my SGH-I717 using xda premium
Click to expand...
Click to collapse
Agreed......
I'm excited to see the results....and thank you !!...g
I have to reflash ROM so pics might be a little awhile. I messed up some things and somehow lost my Google account. reflashing gapps and ROM didn't fix it.
Anyway results were 2600 something at 700 both cores underclocked 25... Slightly more than half of normal speed at slightly less than half clock speed... For kicks i tried 1.5 clock speed undervolted 75 (most my phone will go without lockups) and got 5k results. Best yet.
You are on to something. Less voltage = more speed. I now need to try single core undervolted. Give me couple hours for pics etc.. Got to get phone working with Google again and spend time with wife. She hates me on the phone.
Sent from my SAMSUNG-SGH-I717 using xda premium
No worries Troy. ...
Take all the time you need.....
I do appreciate the excellent testing you have undertaken. I know that the results are going to benefit the community.
And i am highly intrigued by your first run under the parameter set you've chosen...
It's leading down the exact path that i suspected. ..
I'll talk with you soon. ...g
A few additional items that I have failed to consider during my testing, could weigh heavily on our testing results and should be considered during testing.
They are, battery power levels, charger connection and type....(wall/PC), and rom power save levels.
I do know that the android OS will adjust itself during varying power levels, much like our setting the CPU to UC/UV settings, only on a much smaller scale.
I feel its important that we are able to control the input levels in the following way...
Battery to full charge, with no charger connection, and if the cable is needed we use a non powered port. Next would be controlling the rom power settings if the rom contains them, as found in most GB and ICS builds.
If these baselines are met, we should be able to greater rely on the mark scores we are seeing. These variables could explain why we continue to see so many peaks and valleys in scores when two users share the same builds, on like devices.....(speculation)..
Additionally, are we able to control the background processes to the extent, they will remain constant for testing?
Sorry for the rant.....Im just concerned about the ability to quantify our findings once testing is complete.
Ive started some tests on my end as well, and certainly do not want to give you the impression that I expect you to do all of the work.
After all, you did ask first....lol and I feel like Im dumping this effort into your lap.
And please forgive my pathetic punctuation in this post, as my keyboard of choice decided to fail tonight....g
Battery does effect performance greatly.... Also noticed none of the apps to test are very repeatable. Fluctuation seemed to be about 100.
Having issues up loading pics from phone, I'm away from laptop for a few days.
In the end i found -12 v single core to provide the best battery and performance that was equal to dual core. I tried over under voting many differences.... over voting did nothing, under voting a little made small preformance improvements. I believe some of fluctuations are related to app, battery, etc.... In the end it's too say dual core has no speed improvement. I would be cool to test an app that it's specifically for dual core. I am better off without the second core speed is same anyway, and battery is much better. There is definitely voltage leakage..
Let me know what y'all find in your tests....
Sent from my SAMSUNG-SGH-I717 using xda premium
Outstanding !!
I appreciate the hard work !!
So it seems we are better off using the note running a single core and about 12mv under volt.
And I'm of the belief that our second core is rather pointless...unless it can be proven that the second core is absolutely needed to perform a function.
And so far, I haven't found anything I use that requires activation of the second core.
I'll continue my tests, but the way it looks now, Intel is right, and Samsung pushed a dual core chip to this device for nothing more than a market share increase. As it is quite clear that the device does "not " need it to function well, and at a Very respectable speed.
Now we have a quad core version, and I highly question the motivation behind that move, beyond marketing as well.
These statements may offend some, and folks will certainly disagree, but if you want a great running device and great battery life, you need a single core chip ...IMHO ....g
Agreed Greg. Someone will get upset when they do thirty own tests and realize what we see, and what you said, good marketing by Samsung. Numbers don't lie and i did tests as controlled as possible. Even my battery shows in the picks... A true second useful core would have easily bested the single core results. Plus undervolting tella the bigger story...
I must say though. It had been very useful.. My battery life is so much better now!!!
For me the only true performance gain had been from v6 supercharger.
Sent from my SAMSUNG-SGH-I717 using xda premium
Fyi: same exact results using cm9 versus cm10. Neither ROM benchmarks faster than the other as of 9/16 cm9 and 9/15 cm10 builds. Dual core zero performance upgrade.
Tried quadrant again and result very up to 20% back to back so that app is useless to me.
Can someone try a Samsung based ROM. I'm curious add to a difference in roms. just use antutu benchmark and set cpu however you wish to whatever you wish just report cpu clock speed, type of test, and results
Sent from my SAMSUNG-SGH-I717 using xda premium
Out of town this week Troy, but i'm gonna bump it for ya...g
How do you all find the new Jellybean update's battery life? Better or worse than ICS? I'm guessing worse because of Google Now, but just wondering...(I don't have phone yet)
seems worse to me i was gettinf better battery life on ICS.. my battery drops from 100% to 50% way to fast..
Battery life on the new JB update is amazing!
Even MeanROM never was this good with battery life!.
After a couple of days and restarts its looking good
Sent from my EVO using xda premium
evo401 said:
seems worse to me i was gettinf better battery life on ICS.. my battery drops from 100% to 50% way to fast..
Click to expand...
Click to collapse
If you were not such a FLASHAHOLIC just sayin
There is actually a logical and technical reason as to why JB have worse battery life than ics.
As many people probably know, JB focuses on project butter which aims to make the android experience smoother.
Unfortunately, Google's philosophy is about brute forcing into the problem by relying on raw cpu and gpu power instead of fixing their shaddy code.
The most noticeable difference on JB is UI becomes smoother but that smoothness came at a price, the cpu and gpu has to work harder to maintain 60fps with added vsync triple buffering on top of it.
I also noticed that HTC has boosted the.default 3d gpu clock of adreno 225 on their latest kernel to compensate for the additional workload to maintain smoothness. Some people that is familiar to overclocking knows that if the clocks are increased, the power consumption also increases. It is also not help by the fact that EVO 4g LTE can't always maintain 60fps so it has to work extra hard.
Probably not a lot of people know this but android has abysmal input lag and Google tried to address the issue(in which imo they horribly failed) by boosting the cpu clocks everytime you touched the screen. Obviously, raising the clocks would have negative impact on battery life so if you type a lot or Swype a lot or scroll alot, the cpu would get raised everytime. You could see it yourself by installing a program called micro cpu monitor.
The most obvious way to see the input lag in action is try playing a music then replicate the beats on apps like real drums. The lumia 900 which has single core or even the iPhone 4 which has single core 800mhz cortex a8 does not suffer from horrible input lag.
I was really disappointed with Google and it seems like they have no plans to really fix the core problems in the near future.
Sent from my EVO using xda premium
bigdaddy619 said:
If you were not such a FLASHAHOLIC just sayin
Click to expand...
Click to collapse
hahahah!! u are so rite!! i do have a problem with flashing
I've been using performance mode since the day I got the phone, so for the last 10 days, but I wanted to know - is it really worth it? I rarely play games, if I play them at all. I don't edit videos, do some photoshop work or whatever. I mainly use M20P for whatsapp facebook insta reddit and browsing.
So do I really need it or should I disable performance mode and get even more battery juice?
Ty
furiouszagreb said:
I've been using performance mode since the day I got the phone, so for the last 10 days, but I wanted to know - is it really worth it? I rarely play games, if I play them at all. I don't edit videos, do some photoshop work or whatever. I mainly use M20P for whatsapp facebook insta reddit and browsing.
So do I really need it or should I disable performance mode and get even more battery juice?
Ty
Click to expand...
Click to collapse
TBH, I've never used that and the mate is the fastest most fluid phone I've ever used. I really don't think it's needed at all.
mike2518 said:
TBH, I've never used that and the mate is the fastest most fluid phone I've ever used. I really don't think it's needed at all.
Click to expand...
Click to collapse
I see. So you would reckon I dont need it enabled?
Not really seen any difference in performance with it, I tested but don't use it at all now.
Sent from my HUAWEI LYA-L09 using XDA Labs
The performance mode increases the GPU performance and doesn't have this much impact on the CPU.
So you will only notice it while playing games or doing some GPU-accelerated video editing - the everyday performance won't improve this much..
I think it changes the cpu's governor to respond faster to any solicitation (for me it unlocks a bit faster for example).
If you don't need extra battery life you can stick to performance mode.
But like others said, it's not a big change, it will still feel smooth and fast without performance mode.
Alright, I'll just do a test and if the battery lifr difference is significant, I'll turn it off. Thank you everyone
I didn't realize we even had a toggle for that. Too bad they treat it the way they do - it should be a list of apps that automatically turn it on when they are running. EMUI 9.1 has something kinda like that, except it is a group of optimized settings that have been pre-made for specific games. There are only about a dozen or so games on the list so far, which kinda makes it pointless. There were reports that Huawei had changed their mind and remove the performance toggle from the Mate 20 Pro at the last moment, because it made the phone heat up and didn't really gain anything. I have a zillion games on my phone but none of them are so GPU intensive that the phone struggles, haven't seen a need for this mode - yet.
I play tekken 6 on PPSSPP emulator, it runs the same with or without it, pretty much perfect.
kaibosh99 said:
I didn't realize we even had a toggle for that. Too bad they treat it the way they do - it should be a list of apps that automatically turn it on when they are running. EMUI 9.1 has something kinda like that, except it is a group of optimized settings that have been pre-made for specific games. There are only about a dozen or so games on the list so far, which kinda makes it pointless. There were reports that Huawei had changed their mind and remove the performance toggle from the Mate 20 Pro at the last moment, because it made the phone heat up and didn't really gain anything. I have a zillion games on my phone but none of them are so GPU intensive that the phone struggles, haven't seen a need for this mode - yet.
Click to expand...
Click to collapse
In other words, what you're saying is basically there's no need to actually run it as the perfomance isn't significantly improved, likely not at all? And I don't even play games, I guess it's even more pointless for me? Lol
kaibosh99 said:
I didn't realize we even had a toggle for that. Too bad they treat it the way they do - it should be a list of apps that automatically turn it on when they are running. EMUI 9.1 has something kinda like that, except it is a group of optimized settings that have been pre-made for specific games. There are only about a dozen or so games on the list so far, which kinda makes it pointless. There were reports that Huawei had changed their mind and remove the performance toggle from the Mate 20 Pro at the last moment, because it made the phone heat up and didn't really gain anything. I have a zillion games on my phone but none of them are so GPU intensive that the phone struggles, haven't seen a need for this mode - yet.
Click to expand...
Click to collapse
Derpling said:
I play tekken 6 on PPSSPP emulator, it runs the same with or without it, pretty much perfect.
Click to expand...
Click to collapse
I see. Could it be Huawei just put that with the EMUI 9 to satisfy those who complained they couldnt get the same or similar antutu or geekbench scores that were advertised?
kaibosh99 said:
I didn't realize we even had a toggle for that. Too bad they treat it the way they do - it should be a list of apps that automatically turn it on when they are running. EMUI 9.1 has something kinda like that, except it is a group of optimized settings that have been pre-made for specific games. There are only about a dozen or so games on the list so far, which kinda makes it pointless. There were reports that Huawei had changed their mind and remove the performance toggle from the Mate 20 Pro at the last moment, because it made the phone heat up and didn't really gain anything. I have a zillion games on my phone but none of them are so GPU intensive that the phone struggles, haven't seen a need for this mode - yet.
Click to expand...
Click to collapse
I think this is what "Game acceleration" mode is for...you select the apps and they will get a performance boost at the expense of battery. Never tried it myself, but I wonder if this is a "Performance mode" limited to those apps...that's how I look at it.
Ipse_Tase said:
I think this is what "Game acceleration" mode is for...you select the apps and they will get a performance boost at the expense of battery. Never tried it myself, but I wonder if this is a "Performance mode" limited to those apps...that's how I look at it.
Click to expand...
Click to collapse
Makes sense. I agree
Ipse_Tase said:
I think this is what "Game acceleration" mode is for...you select the apps and they will get a performance boost at the expense of battery. Never tried it myself, but I wonder if this is a "Performance mode" limited to those apps...that's how I look at it.
Click to expand...
Click to collapse
Game acceleration is the gpu turbo, performance mode is in battery settings,2 different things.
Be that as it may, general consensus seems to be that it is pretty much useless...
The performance mode was meant for a higher score on benchmarks. Huawei and a few other OEMs were accused of detecting popular benchmark apps and purposely tune their software to score higher on benchmarks. The performance mode was a result of public demand.
Koong1 said:
The performance mode was meant for a higher score on benchmarks. Huawei and a few other OEMs were accused of detecting popular benchmark apps and purposely tune their software to score higher on benchmarks. The performance mode was a result of public demand.
Click to expand...
Click to collapse
Yeah, thought it was something amongst those lines. So, useless in day to day usage
furiouszagreb said:
Yeah, thought it was something amongst those lines. So, useless in day to day usage
Click to expand...
Click to collapse
Yes. It is useless. There is no need to keep your CPU running at maximum in everyday usage. The phone can auto detect graphics intensive and CPU hungry apps, it will adjust automatically to the needs of different apps. Use the phone as it is for the best stress free experience.
(Damn, I sound like some Huawei salesperson)
Lmao! But yeah I figured as much. thanks haha
Koong1 said:
The performance mode was meant for a higher score on benchmarks. Huawei and a few other OEMs were accused of detecting popular benchmark apps and purposely tune their software to score higher on benchmarks. The performance mode was a result of public demand.
Click to expand...
Click to collapse
this!
I think people have forgotten about the benchmark cheating controversy.
"optimisation" in benchmark apps (that is detection and different settings for benchmarks vs real world apps) was considered cheating (and rightly so)
so instead, huawei made the optimisations an option for the entire phone. only affects benchmarks afaik. maybe some intensive apps... but which apps right now would be considered power intensive for a phone (not a benchmark, an actual app).