So according android central's review, the Z3+ has two of the SD810's A57 cores disabled entirely. Only certain apps (literary a select few apps like the camera or antutu) will enable the phone to use all four A57's.
(can't post links, new user:crying
I don't own a Z3+, but I'm interested in getting one. Just curious if the Z3+ still has those A57's disabled under marshmallow, otherwise I might get a Z5.
Would someone on marshmallow test their Z3+ for me? All you need to do is download and use Trepn Profiler from the play store (Qualcomm's app, sorry can't post links).
According android central the A57's are cpu5, cpu6, cpu7 and cpu8.
According to the stats 5,6,8 were running on 0
Sent from my E6533 using XDA-Developers mobile app
Thanks for checking!
Ok so 3 of them were disabled, maybe that's why MM runs cooler?
If possible could you play a game or something, not a benchmark tool, and see how the cpu's behave?
In my case one was showing 0 (if I recall well, cpu7), rest were showing activity during ordinary tasks as browsing, moving through menus etc...
Sent from my Nexus 7 using Tapatalk
After some in depth investigation I can confirm that Z3+ won't use 3 of its A57 when it's gets hot specially during gaming. Only one core would work and that too at very low clock. After that no matter what you do it won't use the A57 cores. The cores would fire up only if you leave the device idele for some time. But as soon as you open Chrome the A57 cores would fire up but a low clock. This is happened in the lady update. Before that on MM even when the device was hot A57 cores would fire up. But after the last update Sony has done heavy change to the governor at the expense of performance. Even my 3 years old note 3 runs the game much faster after 5 mins into heavy gaming.
Sony should provide a performance mode option for people who need high performance during gaming irrespective of the heat. But the phone would never lag in the general applications. The only problem is that high level gaming and video editing impossible on this phone due to the A57 cores becoming inactive.
To be honest I think its actually making the battery last even less time, my z2 goes faster, cooler and much longer. Really really disappointed so far in this device and I dont know if they're going to bother improving on this.
I never used the device with mm because when I got it and added the 2nd user it gone into bootloop, so I had to flash it with the flashtool.
Sent from my E6533 using XDA-Developers mobile app
Just a quick one
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my E6533 using XDA-Developers mobile app
It's how the Big.little has been configured. How I see it though is that it's a 4 core with a boost function. Um sure the 810 Uses HMp
The most powerful use model of big.LITTLE architecture is?*heterogeneous multi-processing?*(HMP), which enables the use of all physical cores at the same time. Threads with high priority or computational intensity can in this case be allocated to the "big" cores while threads with less priority or less computational intensity, such as background tasks, can be performed by the "LITTLE" cores.[10][11] wiki
I also noticed that. 3 cores are dead under pressure of gaming thats creepy.. Im on the latest mm. Hope that they will do something with it because i can feel its getting slower in direct test with Galaxy alpha g850f (with exynos).. Do someone know if this is a feature of marshmallow only or it is included in lollipop
Sent from my E6553 using XDA-Developers mobile app
I just tested some gaming and security software scan, and all cores showed activity more or less..
Related
hi
can someone install droidfish chess app, set on 4 cores and from initial board position will do analysis to see if knps passes 1000...lg g2 failed to pass 600 which is low. interesting to see it that aspect was improved with new chip/memory speed...
Sent from my SM-N900 using XDA Free mobile app
for example, galaxy note 3 result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N900 using XDA Free mobile app
TheBenzinator said:
hi
can someone install droidfish chess app, set on 4 cores and from initial board position will do analysis to see if knps passes 1000...lg g2 failed to pass 600 which is low. interesting to see it that aspect was improved with new chip/memory speed...
Sent from my SM-N900 using XDA Free mobile app
Click to expand...
Click to collapse
It's 602k.
I got 608K, also running HolyAngel's kernel as well, FYI, with CPU at 2.5 and smartassv2 enabled.
thanks to all. I guess need to wait to new Quallcom chip 805 to see if this will be improved..
Sent from my SM-N900 using XDA Free mobile app
TheBenzinator said:
thanks to all. I guess need to wait to new Quallcom chip 805 to see if this will be improved..
Sent from my SM-N900 using XDA Free mobile app
Click to expand...
Click to collapse
No problem, just don't forget the Thanks button.
I do wonder if it's the QHD display that drags down the nps with the G3, compared the Note 3 with similar specs...
JustLok said:
No problem, just don't forget the Thanks button.
I do wonder if it's the QHD display that drags down the nps with the G3, compared the Note 3 with similar specs...
Click to expand...
Click to collapse
My note 3 is with Exynos cpu so it performs much better in this kind of cpu load.... i dont see any relation to QHD display which is handled by gpu part..
Sent from my SM-N900 using XDA Free mobile app
This is L1 cache that matters to chess... not Ghz
Dear all,
Let me contribute to that topic with some more precision.
If you are looking for more Nodes per second, the decisive criteria is the L1 CACHE of the CPU. It plays much more on the outcome compared to the frequency. I am quite sure about that after trying this test on different Snapdragons.
Snapdragons have 16K data + 16K instruction cache. Therefore, even a Galaxy Note IV can barely reach 700K despite 2.65Ghz speed of the Snapdragon 805, while its Exynos brother boosts no less than 1400K.
You may recall the Exynos is octa-core. and SD805 is only 4 cores. If we are supposed to think that's the reason, come explain 730K made with the Exynos 4412 of Galaxy Note 2 which runs @ 1.6 x 4 cores.
Exynos CPU's have 32K+32K L1 cache! That's why they perform surprisingly better. But be careful with all this big.LITTLE thing which is extremely mind confusing. I did not test a note III or a Galaxy Tab with Exynos 4+4 cpu's. They all have low freq set of cores which, if used, could seriously reduce the speed. But i guess engines like Stockfish will force the hi-freq cores. In Note-III case, that means 1.9 Ghz x 4 cores.
The L1-cache effect is obvious on Apple CPU's which have 1.3Ghz x 4 cores but 64K cache. They perform easily around 1300K.
Finally, stay away from Snapdragons if you use Droidfish and check for octa cores, capable of working together at peak speed and insist on 32K+32K L1 cache minimum per core !!!
Alternatively Mediatek octa core CPU's have 8 cores working in parallel at speeds up to 2.0Ghz. They should give 1200 Knps. MTK6592 for example is a concrete low-cost potential. Give it a try if you can. Mediatek will soon release stronger CPU's but they will be big.LITTLE too, unfortunately...
All i say above applies to chess only. Real life usage, internet, movies, games, social media etc is totally a different world and Snapdragon 805 is a monster there! Qualcomm does not and should not focus on delivering the best chess CPU for mobiles., for us, freaks and they are right in what they are doing for mass users market.
Post your benchmarks here, and no "benchmarks are meaningless", we know that already (though some more and some less).
As far as i can tell 3D performance is on point, absolutely zero lag in console-like games like "oddworld" with full graphics, which is great and promising.
Here are some Antutu samples:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It should be great with the lower resolution, everything else would be crazy ?
Skickat från min LG-H815 via Tapatalk
Just did my Z5C
Not bad from a compact with only 2gb ram!
@gadjet can you tell me which firmware (region and customization) do you use)? This is maximum from me right now :crying: And can you place ss from cpuz please; I want to see how fast run s810 at youre device; 1,56 Ghz an mine, and gsmarena write 2ghz?!
edit: strange things happens; now I enter again in cpuz and see tottaly different picture...and shure the better score! (3rd and 4th picture uploaded now)! Any ideas?!
His Proday please find attached, got a 2nd Z5C due to camera blur issue and newv antutu score
Cutting down on processes and uninstalling stuff definitely helps the score.
Just got my Z5C (Central European distribution - namely Czech Republic). Messed around a bit but was not overwhelmed by extraordinary performance. Slight lags here and there, not very impressed.
Ran the Antutu, it gave me quite a poor 53500 score, so I have no idea how you guys squeeze such a high scores from it. Seem like heavily throttled. Do I have an early revision?
Device part number - 1299-1434 Rev1
Customization - 1298-7258
UPDATE: Strange thing, inserted sim card, rebooted, ran again and got 62400, another run 59700.
@OtaruM i think that you have same problem as I. I have flashed firmware for central europe (with flashtool) on mu device and sometimes processor woark on 1.55ghz instead 1.96. Look at my photos higher, install cpu-z and check what happens.
@gadjet really impressive score. Which firmware region do you use?
It's a wolf in sheep's clothing.
Sent from my E5823 using Tapatalk
Omg 66.5k!?...gr8 score man!
Hi,
Today it is the second day I am using my z5 Compact. I noticed some lags, so I ran some Benchmarks. Also I noticed, that my Device is running max 1.5Ghz like someone mentioned before.
Devcheck, CPU-z and CPU Times are reporting a 1.5 GHz CPU.
Sent from my E5823 using Tapatalk
Antutu 5.7.1
z5 compact E5823
64bit mode benchmark: 65203 points
ROM version: 32.0.A.4.11
Devcheck also reporting max 1.55 Ghz, governor interactive, I/O cfq.
Not sure if devcheck might only show the frequency of the 4 A53 cores and not the 2ghz of the 4 A57 cores. Or Sony has done some underclocking to address the battery life and overheating issues of the 810. In any case, the benchmark result is pretty good and battery life as well as heat is satisfying (using it now for one week).
The A57 run at 2.0GHz. A53 run at 1.55GHz.
Source: http://www.anandtech.com/show/8933/snapdragon-810-performance-preview
Did anyone try the new v6 Antutu Benchmark?
In normal use and room temperature I only get around 65000 result, which according to the comparison table is far below the listed Z5. Only if I put the phone in my freezer and Bench it in there I can just match the 74k, that the normal Z5 is listed at.
Not too impressed to be honest.
I work in retail and a customer came into the store this morning with a Z3 on 5.1.1 Lollipop. It actually felt snappier than my Z5 Compact. Don't know how that's possible. Sony need to sort out the software optimisation because having an older phone that feels snappier than the new phone is illogical. I'm guessing Sony's software is not properly optimised for the big.LITTLE architecture of the Snapdragon 810. Marshmallow hopefully will fix this!
Sent from my SM-G925F using Tapatalk
69795 on antutu V6
supercakefish said:
I work in retail and a customer came into the store this morning with a Z3 on 5.1.1 Lollipop. It actually felt snappier than my Z5 Compact. Don't know how that's possible. Sony need to sort out the software optimisation because having an older phone that feels snappier than the new phone is illogical. I'm guessing Sony's software is not properly optimised for the big.LITTLE architecture of the Snapdragon 810. Marshmallow hopefully will fix this!
Sent from my SM-G925F using Tapatalk
Click to expand...
Click to collapse
I have both phones (Z5C and Z3C) and I see little difference in the overall feel regarding speed when using them. A little disappointing considering the money I spent but I'm not sure how much faster these devices can get.
Sent from my XT907 using Tapatalk
Mine is 77430
80441
81476 heuhueheu
Hi,
Been monitoring battery performance and CPU sleep states, and one thing I notice is that on my device the A53's spent a surprising amount of time at 1Ghz+ when the screen is on, and one of the A57 cores is always running a 384 when the device is idle, while the other 3 sleep. Is this Sony's attempt to keep the UI snappy? Having the A57 on all the time (screen on), even at that low frequency is going to use in the region of 100mW+ (which is about 4x that of each A53 core)
Can someone else sanity check my results?
I'm using perfmon, systempanel, and "floating monitors"
Perfmon can be found here: http://forum.xda-developers.com/showthread.php?t=1933284
It's also on the market for the price of a coffee, please consider buying it - great tool!
Yep sounds about right this Greek review:
https://translate.google.co.uk/tran.../2015/10/24/sony-xperia-z5-review/&edit-text=
Found that in most cases only one A57 core runs in the Z5.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pardon my ignorance but...how much worse do you think it is to run only the big cores and throttle them from 2Ghz to 300Mhz without turning ON and switching to the little ones? (In other words...disable the big little technology and just use the best 4 cores).
We're now using the little cores more than the big ones....and that 1.5Ghz cap could be the reason of a lot of stutters.
Changing the topic, now that Google is selling Nexus devices (5X and 6P) with big little. I think they will improve this ARM technology in future Android versions (including the kernel).
Sent from my E5823
thesebastian said:
Pardon my ignorance but...how much worse do you think it is to run only the big cores and throttle them from 2Ghz to 300Mhz without turning ON and switching to the little ones? (In other words...disable the big little technology and just use the best 4 cores).
We're now using the little cores more than the big ones....and that 1.5Ghz cap could be the reason of a lot of stutters.
Changing the topic, now that Google is selling Nexus devices (5X and 6P) with big little. I think they will improve this ARM technology in future Android versions (including the kernel).
Sent from my E5823
Click to expand...
Click to collapse
The little cores will be perfectly fine for most daily mundane tasks, such as checking emails, messaging etc. The stutters you mention probably is because the phone launched just before Marshmallow and Sony are focusing more on that OS, same kind of thing with the camera. The current camera app is just a placeholder for the proper app due for release in a week or two.
thesebastian said:
Pardon my ignorance but...how much worse do you think it is to run only the big cores and throttle them from 2Ghz to 300Mhz without turning ON and switching to the little ones? (In other words...disable the big little technology and just use the best 4 cores).
We're now using the little cores more than the big ones....and that 1.5Ghz cap could be the reason of a lot of stutters.
Changing the topic, now that Google is selling Nexus devices (5X and 6P) with big little. I think they will improve this ARM technology in future Android versions (including the kernel).
Sent from my E5823
Click to expand...
Click to collapse
In short, no. The little cores, whilst relative to the A57's are weak, they are by no means underpowered for running the UI and such. Do consider that the A53 core is faster than the A9 cores that powered previous flagships such as the Galaxy S3. Leaving one of the A57's ticking in the background is probably not such a bad idea having thought about it, as it allows fast handover when the high performance is required; I do however hypothesise that some of the stuttering might be due to threads being handed over to the A57, whilst it is running down at 384, which will be somewhat slower than the high frequency A53 core(s) the process is being passed from. It may be that we see a touch-boost or more aggressive CPU governor brought in to rectify this.
On a related note, there is a good article on the power-aware BIG.little implementation in the Snapdragon 810 here:
http://www.anandtech.com/show/8933/snapdragon-810-performance-preview/4
Definitely for performance.
If they weren't set is this fashion the UI would feel sluggish and sluggish on wake up.
Your findings sound perfectly normal/adequate, resemble a "interactive" CPU governor.
So I ordered 2 Z5's from Amazon (2 different sellers); one green and one white to see which color I'd prefer. Now that I have both, quality is equal (and great!) and I like both colors, so decided to dig deeper.
There are some differences in the 2 devices. They are clearly built for different regions as the white one came in a Spectre 007 package and uses the LTE symbol for LTE and the green one came in a standard Sony package, included a QCH10 charger and shows 4G for LTE speeds. (For reference I know that 4G = LTE). The white one is Rev1 and the green is Rev4.
Here is interesting part. I've setup and configured both phones to be completely identical from brightness to apps to theme, etc. When I run a speed test using the exact same SIM card, I get way different numbers.
Running 2 consecutive tests in each on T-Mobile band 4 with the phone on my desk in the exact same position, the white one (Rev1) gives me 82.38 Down/4.71 Up and 47.55 Down/3.52 Up. The green one (Rev4) gives me 94.83 Down/8.56 Up and 97.10 Down/4.81 Up.
On WiFi, they are consistent.
Running both Antutu and Quadrant on both devices is also interesting. Antutu scores virtually the same on each; the white (Rev1) at 56k and the green (Rev4) at 55k. However, on Quadrant, the white (Rev1) is 29k and the green (Rev4) is 22k.
So what I'm looking for are comments/thoughts from some of you senior folks on the differences to help me decide on which device to keep.
Thanks!!
Since you have gone through all the trouble to set both if them up, I would run a bigger sample size of speed tests, say at least 10. I think you would see things average out and be fairly equal. Only thing is, not sure how your data plan is configured. Running network speed test in bunches chews data.
You actually ordered unboxed and used 2 different devices just because you couldn't pick which color you like before sending back the one you don't want?
I know that you 'can' but...
Sent from my E6653
This post made me rerun Antutu 64-bit today on my black E6653 Rev3 where I got 55,092 only last night, same as OP.
Well, the latest result is 62,511
So, any of you guys notice the phone is faster during the day than at night?
Screenshots of Antutu results, phone uptime is 72 hours so no reboots between runs.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i merely get 50k on black rev4. it shows lte though..
ricodredd said:
This post made me rerun Antutu 64-bit today on my black E6653 Rev3 where I got 55,092 only last night, same as OP.
Well, the latest result is 62,511
So, any of you guys notice the phone is faster during the day than at night?
Screenshots of Antutu results, phone uptime is 72 hours so no reboots between runs.
View attachment 3534281 View attachment 3534282
Click to expand...
Click to collapse
Might depend on signal from carrier and how stable it is. Many apps and system modules launch during different conditions taking a toll on battery and perfomance for a moment. For example changing connectivity from 3G/4G to WiFi will launch several apps that will then be closed down as RAM is needed for other apps that you have launched (these apps might be in standby but do some work from time to time or just when initially launched). This due to them being set by respective app to start when connectivity changes happen. So bench them in airplane mode and with wifi off. Restart before benching.
Mine shows to be slower than the z4 lol
@EQ2000
We all know benches can vary from run to run. My point about 55K vs 62.5K on my Z5 is that OP shouldn't be using benchmark results to choose between two "identical" phones.
ricodredd said:
@EQ2000
We all know benches can vary from run to run. My point about 55K vs 62.5K on my Z5 is that OP shouldn't be using benchmark results to choose between two "identical" phones.
Click to expand...
Click to collapse
Agreed unless this indicates one phone is throttling due to inadequate application of thermal paste and/or contact between SoC and heatsink.
OP (me) isn't using benchmarks to decide. My questions (and title) were around speed variations between the 2 devices and the benchmarks were just a secondary observation.
I was just curious if it could be possible that Rev1 and Rev4 have different radios.
My apologies if the benchmarks became the root of this discussion.
One more observation today. The green Rev4 has a VoLTE button in the Quick Access drop down and the white Rev1 does not.
Could you share with us your test result? Mine
Throttling test : https://play.google.com/store/apps/details?id=skynet.cputhrottlingtest
Mi-Room 9.4.25 + Floppy kernel 22.02.2019 for oreo miui/linaro
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Might do later. In any case, please also write the outside temperature in °C as that has a BIG influence on the speed. Also if you had the phone in a case or not.
No case on the phone. Just a transparent skin on the backside and screen protector. LineageOS 16 + BG345 kernel + no thermal mod applied. Ambient temp maybe 22-23C.
And here's a second one with thermal mod V1
Edit:
Since I saw how consistent your run was with Floppy Kernel I thought of giving it a try myself. So here's the third one with LineageOS 16 + latest Floppy Linaro (2202019). It's alot better but it starts out weird with lower performance and it goes up after a while. Probably some Kernel Adiutor settings I messed up.
Sent from my MI 5s using Tapatalk
Here mine. Complete stock Global firmware with the current version 10.2.2.0(OAGMIXM). Ambient 25°C and running various applications in the background.
xiaomi.eu 9.4.25 + floppy kernel 22022019 + balanced battery setting in floppy managers spectrum section
outside temp around 20 °C and phone is in a TPU case
You're not getting thermal throttle because it seems to me Spectrum profile also limits cpu frequency. Your big cores seem to be limited to 1.82Ghz and not 2.15Ghz as default. Might be wrong but that's how it looks to me. Also your small cores seem also to run under the default frequency. I'm running mine with default 2.15ghz for big cores and 1.6ghz for the small ones. Still average performance seem the same so heck I might limit mine as well. [emoji23]
Sent from my MI 5s using Tapatalk
yeah, floppy manager has 2 underclock settings under the misc tab: balanced and battery. The spectrum profile turned on balanced with 1.82 GHz and 1.59 GHz.
Leni_YO said:
yeah, floppy manager has 2 underclock settings under the misc tab: balanced and battery. The spectrum profile turned on balanced with 1.82 GHz and 1.59 GHz.
Click to expand...
Click to collapse
Do you happen to have the app? Seems it's a modified Kernel Adiutor but I can't seem to be able to download it anywhere.
templeka said:
Do you happen to have the app? Seems it's a modified Kernel Adiutor but I can't seem to be able to download it anywhere.
Click to expand...
Click to collapse
https://github.com/JonasCardoso/Flo...om.jonas.floppymanager-v0.9.10.3-17022019.apk
patoberli said:
Here mine. Complete stock Global firmware with the current version 10.2.2.0(OAGMIXM). Ambient 25°C and running various applications in the background.
Click to expand...
Click to collapse
Looks pretty much like mine. The 4th core just switches off after a while.
Googlemaps becomes unusably slow due to that...
@OJK
I've since switched to a Mi 9T Pro, I can really recommend it.
For the Mi 5s, I think it was the same in the beginning (CPU clocking down), but the newer apps simply require more speed today. I thought about modding mine with a newer/better cooling pad, but discovered that it is really complicated to exchange (it's between the display and mainboard).
patoberli said:
@OJK
I've since switched to a Mi 9T Pro, I can really recommend it.
For the Mi 5s, I think it was the same in the beginning (CPU clocking down), but the newer apps simply require more speed today. I thought about modding mine with a newer/better cooling pad, but discovered that it is really complicated to exchange (it's between the display and mainboard).
Click to expand...
Click to collapse
It's really a shame . I don't want to buy a new phone every two years... The iPhone 7 of my girlfriend still runs Google Maps smoothly, even it hot climates (we're currently in Singapore). The Mi 5S and the iPhone 7 were released at similar time, Mi 5s being top notch then. It seems to be a general problem of android... maybe I will give apple a try and see how I get along.
Sent from my MI 5s using Tapatalk
Apple does have a better working CPU, but hey, it also costs 2-3 times as much as the Xiaomi. So yes, that does make a big difference.
Besides that, google made Maps considerably slower in the last few months. You might want to clear its cache, if you haven't already.