How is it? - Nexus 10 General
So... worth it? Better than the iPad? Surface? What do y'all think?
Different. For some better, for some worse. It all comes down to your own preferences.
C-Lang said:
So... worth it? Better than the iPad? Surface? What do y'all think?
Click to expand...
Click to collapse
Cant say, haven't used the Surface and only little iPad 2 so hard to tell.
Sent from my Nexus 10 using xda app-developers app
how about those that have/had the note 10.1? worth switchin to nexus 10? or is screen the only factor..over all the features note 10.1 has especially with its upcoming jb update
tuffballa said:
how about those that have/had the note 10.1? worth switchin to nexus 10? or is screen the only factor..over all the features note 10.1 has especially with its upcoming jb update
Click to expand...
Click to collapse
Nexus 10 will receive future updates first (before any 3rd-party vendor/non-nexus device), has a clean Android experience (no Touchwiz, may or may not be a plus), and can easily be unlocked and modded (not sure what the Note 10.1's stance is on such matters)
What will yo be using it for mostly ? And gave you owned a tablet be for and what tablet? Once we know this we can give you a better answer.
I came from an I pad and it took me two weeks to settle into the nexus 10, first week will be poor battery life and frustrating with the back button but after that its great.
Don't use chrome use dolphin browser and the YouTube app is good but getting to subs is a little annoying at times.
Ill also say I've found lagg on some games like osmosis HD but others work great.
The feel of the tablet is great the soft warm rubberized finish is really comfy.
Also the tablet gets warm near the camera when being used nothing to be conserned about.
You should also keep in mind that you will get great support from Google with updates but even more support from us with custom rooms, however Samsung is a consern with giving out source for the exynos processors but I'm sure since it is a Google tablet this will not be an issue.
Also if you side load flash I personly found it to be useless and laggy.
Another thing is with such a high Res screen some site images will look pixalated but text and vector images are clear as a magazine.
We are also finding that support for some video codecs is not great but Mx player seems to do well to help this but it uses software to decode if I'm correct.
Sound quality is amazing with true around sound coming from left and right speakers.
And you will find some screen have light bleed but you will not notice this unless looking at a blank black image so not worth worrying over.
The screen is bright and crisp and hope full more apps will be updated to the Res in the future.
This still is more a Dev device rather then a consumer device so we do get some random reboots but it generally takes 30seconds to reboot so take that into consideration.
Also no mirracast support from what I hear so you cannot mirror movies onto your TV without a HDMI cable.
Also charging takes a long time 8 hours from empty to full. Their will be a pogo charger but who knows when that will be available and how long it will take to come out. Same with the smart covers and magnetic keyboards.
Hope this helps .
I live my nexus 10 and am happy i sold my I pad 2 I like the customization and freedom to do what I want with it also the comfort of use.
Sent from my GT-I9300 using xda premium
its amazing hands down if you love google you will cum
Its an awesome tablet; beautiful screen, front speakers, good battery life, really fast processor speed(boots up in 15 seconds), crazy multitasking with 2 GB ram and android 4.2 for only $400. Can't get a better deal than this in the market.
Sent from my Nexus 4 using XDA Premium HD app
I LOVE this thing, however, I must say that compared to my nexus 4, this thing is quite laggy. I of course rooted it and overclocked it and kept the minimum processor speeds to about 1 GHz to prevent lag as much as possible, but if you do any sort of "stressful" multitasking or game playing, then this thing will overheat and reboot fairly annoying, but it will surely be fixed in the future However, I LOVE the beautiful screen, stock experiecne, and the light form factor :highfive:
Just go to a Best Buy or equivalent and check them all out. People will have different opinions which may or may differ from your own.
ImARaptor said:
I LOVE this thing, however, I must say that compared to my nexus 4, this thing is quite laggy. I of course rooted it and overclocked it and kept the minimum processor speeds to about 1 GHz to prevent lag as much as possible, but if you do any sort of "stressful" multitasking or game playing, then this thing will overheat and reboot fairly annoying, but it will surely be fixed in the future However, I LOVE the beautiful screen, stock experiecne, and the light form factor :highfive:
Click to expand...
Click to collapse
This is one anecdotal experience and involved a complete wipe but I found that my N10 was much more responsive after flashing the stock image than it was out of the box.
ImARaptor said:
I LOVE this thing, however, I must say that compared to my nexus 4, this thing is quite laggy. I of course rooted it and overclocked it and kept the minimum processor speeds to about 1 GHz to prevent lag as much as possible, but if you do any sort of "stressful" multitasking or game playing, then this thing will overheat and reboot fairly annoying, but it will surely be fixed in the future However, I LOVE the beautiful screen, stock experiecne, and the light form factor :highfive:
Click to expand...
Click to collapse
Hmm... I've never, not once, had mine overheat and reboot. Mines also been as smooth as butter in every definition of the phrase. That's just me! Running on all stock.
Returned my ASUS Infinity TF700T for the Nexus 10, and I absolutely love it.
beamed from a Nexus 10 far, far away
jonstrong said:
Returned my ASUS Infinity TF700T for the Nexus 10, and I absolutely love it.
beamed from a Nexus 10 far, far away
Click to expand...
Click to collapse
I also returned my Infinity for the N10....not that the Infinity was awful. Gaming is better, the screen is awesome, 2GB is nice. The only down side is the charger IMHO.
ImARaptor said:
I LOVE this thing, however, I must say that compared to my nexus 4, this thing is quite laggy. I of course rooted it and overclocked it and kept the minimum processor speeds to about 1 GHz to prevent lag as much as possible, but if you do any sort of "stressful" multitasking or game playing, then this thing will overheat and reboot fairly annoying, but it will surely be fixed in the future However, I LOVE the beautiful screen, stock experiecne, and the light form factor :highfive:
Click to expand...
Click to collapse
I had only one reboot since I bout it, and too when I was not rooted, the only problem I have is that this thing does ridiculous amount of thermal throttling and can start lagging after playing high end games for a long time. Just a matter of time before the developers fix that
Sent from my Nexus 4 using XDA Premium HD app
johno86 said:
Just go to a Best Buy or equivalent and check them all out. People will have different opinions which may or may differ from your own.
Click to expand...
Click to collapse
Best Buy doesn't sell the Nexus 7 or 10, much to my chagrin!
Surface although it has that desktop mode you can't do much except office and browser. The app catalog is not as big as android or iOS and its a new platform hasn't been tested much in everyday use.
IPad is good at hardware not so good software wise (tired of the same old UI). I hear there are more apps for tablet on iOS.
Nexus 10 is android and has none of the bloatware of other android tablets faster upgrade cycle. Apps for tablet are limted . hardware is really good very good response times. Only problem is the light bleed which for my tablet is not noticeable in regular conditions unless you want to look for it. Contrast could have been better but its $100 cheaper than the competition. Not many Accessories yet.
Sent from my Nexus 10 using xda premium
If you consider yourself a power user and are used to Android, you'll sometimes find it incredibly difficult to do what you would consider even basic tasks with an iPad (tweaking settings is extremely limited as is personalisation for example). You'll find yourself regularly going to forums and searching for ways round the many limitations of the apple ecosystem, only to find if you want to do it you can't-unless you jailbreak it.
I do however tend to recommend ipads to my friends who are either not great with technology or who want it for a specific purpose that it performs particularly well at (as long as they have deep pockets obviously)!
It most certainly does have more optimised apps, you find many apps tend to appear first on ios and in the past have been higher quality.
You'll also find however that you'll almost certainly have to spend more money on apps with an ipad.
The android tablet apps will catch up soon enough though I'm sure as this christmas, tablets are selling in huge amounts and developers are all going to want a slice of the cake.
Sent from my XT910 using xda premium
So far, IMHO, the best droid tab on the market!!!
So you don't think that my opinion is frivolous, I have been a big part of the PDA/XDA revolution. My career is in mobile tech and my first smartphone was the "Amigo". Any of you remember that one?
Okay, so I did quite a bit of research on my next tablet. My first was the Galaxy 8.9 (by far my favorite form factor), then the Galaxy 10.1 V2, and finally the Prime TF700. Well, I didn' own the Asus for very long due to the ridiculously under developed I/O.
Unfortunately, my experience with Samsung's Cust SVC was like pulling teeth. My 8.9 developed horrible screen issues and had to be sent back to Samsung three separate times. After three months of playing ping pong with the under trained Samsung staff, finally, my money was refunded. So, needless to say, when I heard that Samsung was chosen to make the n10...I was displeased.
With that said, I can't begin to tell you how much of an improvement the n10 is to the Android sector. This tablet is by far the finest yet and should be given the top ranking spot...and not just because of the specs. Overall, 4.2.1 is extremely fluent and intuitive. Switching between programs and the home screen has absolutely no lag. The chrome browser is fast and seems to handle the lack of flash fairly well.
I, for one, really like the rubberized backing. Although I think that Asus' design is flashier and has a more "high-end" look, I always felt like the bare tablet was slippery and risked a drop. The n10 does not feel this way at all! Holding the tablet in one hand or two seems to make no difference on the grip. I believe this to be an extremely important factor in making the decision on which tablet to buy. A tablet has to be comfortable to use in all conditions.
One gripe...I know, I know....the lack of the SD card is a bummer. I did get the 32GB model, however, my movie collection alone is approaching 100GB. When I bought the TF, I sat down and spent hours transferring all of the videos to SD cards...now...anyone want three 32GB SD cards? I guess I'll be floating with the clouds.
Anyways, overall I give the n10 a 9.8 rating on my scale and truly believe that this is the tablet that has that potential to overtake the aging iPad and its iOS. Really shows what Google and its droid OS are capable of....can't wait to see what's next!
C-Lang said:
So... worth it?
Click to expand...
Click to collapse
For a few days i thought 100% yes - positive. Now im not so sure.
Screen was the main selling point for me. But now im disappointed.
After comparing with macbook retina screen (same image,on the same brightness) the difference is obvious: light bleed not only makes black glowing, but also makes colors much less saturated.
Both panels made by samsung, but they look completely different. PLS technology is supposed to be superrior than S-IPS, and it is, in retina display. But in nexus 10, it actually looks worse than S-IPS desktop monitor.
Nexus display still better than TFT.
DX11 class GPU ARM® Mali™-T604 GPU: APIs supported include OpenVG™ 1.1, OpenGL® ES 1.1, OpenGL ES 2.0, OpenGL ES 3.0*, DirectX® 11 and OpenCL™ 1.1.
GPU is great, but there could be a problem with tablet design. Playing modern games results in thermal Throttling in a few minutes.
I got to #2 in NFS: Most Wanted, but it was a torture, not fun. Usually, if you start with cold device, you can finish 2 races before slideshow starts.
You would not believe how bad it is.
Here is an example:
I slowed down and undervolted CPU to 600MHz/825mV to this test. Visually this reduced FPS (and supposedly GPU load) to about a half. But look at dmesg:
Code:
<3>[ 6121.923434] wm8994-codec wm8994-codec: FIFO error
<3>[ 6136.684382] wm8994-codec wm8994-codec: FIFO error
<6>[ 6162.047312] battery: l=77 v=3977 c=-873 temp=33.5 h=1 st=1 ct=2139 type=usb
<6>[ 6222.078644] battery: l=77 v=3991 c=-1122 temp=33.5 h=1 st=1 ct=2199 type=usb
<6>[ 6282.105733] battery: l=77 v=3982 c=-1177 temp=33.3 h=1 st=1 ct=2259 type=usb
<6>[ 6342.134913] battery: l=76 v=3986 c=-931 temp=33.3 h=1 st=1 ct=2319 type=usb
<6>[ 6402.164581] battery: l=76 v=3977 c=-1044 temp=33.3 h=1 st=1 ct=2379 type=usb
<6>[ 6462.191748] battery: l=76 v=3977 c=-1572 temp=33.5 h=1 st=1 ct=2439 type=usb
<6>[ 6522.217670] battery: l=76 v=3982 c=-1077 temp=33.5 h=1 st=1 ct=2499 type=usb
<6>[ 6582.243999] battery: l=75 v=3957 c=-1740 temp=33.5 h=1 st=1 ct=2559 type=usb
<6>[ 6642.273164] battery: l=75 v=3957 c=-1556 temp=33.6 h=1 st=1 ct=2619 type=usb
<6>[ 6702.300569] battery: l=75 v=3967 c=-1009 temp=33.6 h=1 st=1 ct=2679 type=usb
<6>[ 6740.053235] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 6744.060087] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 6745.065074] exynos_thermal_unthrottle: not throttling
<6>[ 6762.326856] battery: l=75 v=3952 c=-1452 temp=33.6 h=1 st=1 ct=2739 type=usb
<6>[ 6799.431233] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 6809.440076] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 6810.445067] exynos_thermal_unthrottle: not throttling
<6>[ 6822.353315] battery: l=75 v=3952 c=-1246 temp=33.8 h=1 st=1 ct=2799 type=usb
<6>[ 6882.380353] battery: l=74 v=3957 c=-1253 temp=33.8 h=1 st=1 ct=2859 type=usb
<6>[ 6898.923374] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 6906.925088] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 6907.930062] exynos_thermal_unthrottle: not throttling
<6>[ 6942.406760] battery: l=74 v=3962 c=-1170 temp=33.8 h=1 st=1 ct=2919 type=usb
<6>[ 6961.641239] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 6965.645090] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 6966.650084] exynos_thermal_unthrottle: not throttling
<6>[ 7002.435304] battery: l=74 v=3952 c=-1121 temp=34.0 h=1 st=1 ct=2979 type=usb
<6>[ 7056.386004] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 7061.390081] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 7062.395063] exynos_thermal_unthrottle: not throttling
<6>[ 7062.460871] battery: l=73 v=3947 c=-1320 temp=34.1 h=1 st=1 ct=3039 type=usb
<6>[ 7116.360405] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 7122.487602] battery: l=73 v=3928 c=-1728 temp=34.1 h=1 st=1 ct=3099 type=usb
<6>[ 7135.366751] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 7136.380068] exynos_thermal_unthrottle: not throttling
<6>[ 7137.473113] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 7157.487309] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 7158.495067] exynos_thermal_unthrottle: not throttling
<6>[ 7161.072825] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 7180.086782] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 7181.090064] exynos_thermal_unthrottle: not throttling
<6>[ 7181.762092] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 7182.515823] battery: l=73 v=3928 c=-1058 temp=34.1 h=1 st=1 ct=3159 type=usb
<6>[ 7201.783180] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 7202.785083] exynos_thermal_unthrottle: not throttling
<6>[ 7204.425444] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 7224.436955] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 7225.445074] exynos_thermal_unthrottle: not throttling
<6>[ 7226.939704] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 7242.544022] battery: l=73 v=3923 c=-1736 temp=34.3 h=1 st=1 ct=3219 type=usb
Game started at ~6162s, ~500sec later it started to throttle. Throttling, among other things, change memory speed and increases memory refresh rate 2x ( which slows down memory even further). Memory bandwidth is crucial to 3D graphics in 2560x1600.
This could be totally software issue, increasing temperature threshold, undervolt/underclock GPU and memory controller could solve the problem.
But if you want to enjoy this toy right now, you are out of luck.
P.S second issue seems to be solved, undervolting GPU -100mV and increasing throttling point to 85 C did the trick
Related
[Q] What benefits does UC\UV give you?
If someone would teach me that would be great! Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Better battery life. But be careful with undervolting. It can cause phone to be unstable. Under clocking is more forgiving. If you are going to do either I would suggest only making small changes and then use phone for several hours to settle in. If all good then try next step lower and test until you find the limit of your phone. Then bump it back up to last stable setting.
There are no noticeable benefits.
jimmer411 said: There are no noticeable benefits. Click to expand... Click to collapse I agree, its mostly the placebo effect regarding lag, a variable effect regarding battery life, due to user apps, and downright dangerous regarding overheating. But many people whine when its not available for a kernel. I don't have a very high opinion of its necessity.
Battery life in our phones is dominated by the screen and radio (cell and wifi) but I find that undervolting at least reduces the heat when I'm doing something intensive like SNES emulation. Lag in our phones is also primarily a software issue (I have other Android devices with the same hardware running at the same MHz and it's a smoother experience). Not that my Note got hot, it's just less warm.
ZacksBuilds said: If someone would teach me that would be great! Sent from my SAMSUNG-SGH-I717 using xda app-developers app Click to expand... Click to collapse There's no reason not to under volt. UC=Under clock UV=Under volt OC=Over clock OV=Over volt. Newer generations of chips have tremendous tolerances. If you were to look at the S3, a Qualcomm built SoC that was a bit long-in-the-tooth by the time the Note was released, you'd see that in many cases, there were phones that featured the chip, but were clocked lower... I.E at 1,000 MHz. Most chips are designed to run faster than they do, at least for short periods of time. Modern chips use temperature and load to designate the running frequency. When Qualcomm releases a chip, they need to be sure that 99% of the units they produce, can run with a near-flawless level of stability. Because of this, they often run chips slower, and at a higher voltage than is actually needed. The result is, that Qualcomm or Samsung might design a chip rated for 2ghz, and release their first device with the chip running at 1.5ghz. This is common. Each piece of silicon is slightly different due to manufacturing differences. Chips are made on giant discs, with hundreds of chips on a single disc. The chips in the center are generally considered to be of a slightly higher quality, requiring less voltage, or capable of running at a higher frequency, sometimes both. Because of this, each device is capable of slightly more, or slightly less. The challenge is for Qualcomm to set the speed and power usage for every chip-- the challenge for us, is to see if we can run the chip at a higher frequency, while drawing less power....because power =heat, and power= battery life. There are two different ways to approach customizing frequency and voltage to your needs. One: If you could run your Note at 1,900mhz, instead of 1500mhz, and draw the same amount of power, that'd be considered a success case. Your device would be faster, without a hit in battery life. Two: Or, if you could run the device at the same speed, and lower the voltage (saving battery life), this would also be considered a success. Sometimes, but rarely in the mobile space, you'll get lucky and receive a prime piece of silicon, and you'll be able to over clock, WHILE undervolting...resulting in a faster phone that uses battery life. Ranger was correct...clock speed changes on the order of +/-20 percent are hardly noticeable. However, power requirements grow exponentially at higher frequencies, and on a mobile device, they're noticeable. While a device might require 1.2 volts at 1.5 GHz, and 1.3 at 1.6ghz, it might also only require 1.05, or 1.0 volts at 1.4ghz. These numbers are theoretical, and shouldn't be used-they arent even close to correct. They're used merely to illustrate that to over clock, chips often require more power than over clocking is worth, in heat (and heat past a certain point will instantly fry your device, or will reduce the lifespan of the chip). These are general ideas on over clocking. If you want to know something specific, ask away. When over clocking/underclocking, the governor used (a set of conditions that tells the CPU when to change from, say 300mhz (when the screen is off, and the device isn't being used), to 1.5ghz, when both cores are being used, and fully loaded. If you want to save battery life, a combination of build.prop radio tweaks, modem tweaks, under clocking profiles, and using a custom governor can significantly increase standby time, and noticeably, but not too significantly increase usage time. Its important to know though, that the screen is the hungriest part of our device, and brightness is the the quickest setting to adjust to gain battery life. The same is true for performance. Kernel, OC profiles, build.prop and launcher tweaks, GOU over clocking, etc. All in combination can have a noticeable effect, because performance is the net sum of dozens of moving parts. Sent from my SGH-I717 using XDA Premium HD app
Jamesyboy said: There's no reason not to under volt. UC=Under clock UV=Under volt OC=Over clock OV=Over volt. Newer generations of chips have tremendous tolerances. If you were to look at the S3, a Qualcomm built SoC that was a bit long-in-the-tooth by the time the Note was released, you'd see that in many cases, there were phones that featured the chip, but were clocked lower... I.E at 1,000 MHz. Most chips are designed to run faster than they do, at least for short periods of time. Modern chips use temperature and load to designate the running frequency. When Qualcomm releases a chip, they need to be sure that 99% of the units they produce, can run with a near-flawless level of stability. Because of this, they often run chips slower, and at a higher voltage than is actually needed. The result is, that Qualcomm or Samsung might design a chip rated for 2ghz, and release their first device with the chip running at 1.5ghz. This is common. Each piece of silicon is slightly different due to manufacturing differences. Chips are made on giant discs, with hundreds of chips on a single disc. The chips in the center are generally considered to be of a slightly higher quality, requiring less voltage, or capable of running at a higher frequency, sometimes both. Because of this, each device is capable of slightly more, or slightly less. The challenge is for Qualcomm to set the speed and power usage for every chip-- the challenge for us, is to see if we can run the chip at a higher frequency, while drawing less power....because power =heat, and power= battery life. There are two different ways to approach customizing frequency and voltage to your needs. One: If you could run your Note at 1,900mhz, instead of 1500mhz, and draw the same amount of power, that'd be considered a success case. Your device would be faster, without a hit in battery life. Two: Or, if you could run the device at the same speed, and lower the voltage (saving battery life), this would also be considered a success. Sometimes, but rarely in the mobile space, you'll get lucky and receive a prime piece of silicon, and you'll be able to over clock, WHILE undervolting...resulting in a faster phone that uses battery life. Ranger was correct...clock speed changes on the order of +/-20 percent are hardly noticeable. However, power requirements grow exponentially at higher frequencies, and on a mobile device, they're noticeable. While a device might require 1.2 volts at 1.5 GHz, and 1.3 at 1.6ghz, it might also only require 1.05, or 1.0 volts at 1.4ghz. These numbers are theoretical, and shouldn't be used-they arent even close to correct. They're used merely to illustrate that to over clock, chips often require more power than over clocking is worth, in heat (and heat past a certain point will instantly fry your device, or will reduce the lifespan of the chip). These are general ideas on over clocking. If you want to know something specific, ask away. When over clocking/underclocking, the governor used (a set of conditions that tells the CPU when to change from, say 300mhz (when the screen is off, and the device isn't being used), to 1.5ghz, when both cores are being used, and fully loaded. If you want to save battery life, a combination of build.prop radio tweaks, modem tweaks, under clocking profiles, and using a custom governor can significantly increase standby time, and noticeably, but not too significantly increase usage time. Its important to know though, that the screen is the hungriest part of our device, and brightness is the the quickest setting to adjust to gain battery life. The same is true for performance. Kernel, OC profiles, build.prop and launcher tweaks, GOU over clocking, etc. All in combination can have a noticeable effect, because performance is the net sum of dozens of moving parts. Sent from my SGH-I717 using XDA Premium HD app Click to expand... Click to collapse So what I understood is this: instead of having let's say, your note running at 1.2ghz consuming 15% battery per hour you can have it at 1.5ghz consuming the same battery life? Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Is my Z5c throttling?
Hello guys, I bought this phone about two days after release and was pretty happy with it. It felt like the Snapdragon 810 didn't overheat at all and the performance was far better than on my "old" Z3. Reason enough for me to try PPSSPP and emulate some good old games. For example MHP3rd ran at 100% speed in every area in-game with no frameskip activated. But after some time (I'd say 20-30 mins) the cpu throttled a lot. The game speed was only at 50% even though the device didn't feel THAT hot (I've seen/felt hotter ones). I tried the same thing again with the app "CPU Temp", and it seems like the CPU temperature never exceeded about 58°C. I'm not sure about smartphone CPUs but as far as I know, most chips can take up to 80-90°C until they start throttling. My Z5c runs at 52-58°C perfectly fine, but suddenly starts throttling for some reason. Is it the CPU governor that tries to save battery life? I'd probably need to root the phone to "fix" this, but there are no roots available yet. Or is it something else? Is the max. cpu temperature set too low? Could it be the S810 has no real temperature sensor and CPU Temp shows me something completely different? Thanks in advance! Greets, Uftherr
I think that Sony it's throttling the CPU more to be below 58°C than to save battery life. Try with the latest firmware (released today at PC Companion) it seems to be a little more snappier (maybe its a placebo). I don't know why because the kernel is from the same date. I consider that they should let the phone gain 65°C to increase the performance (at heat cost). Sent from my E5823
Is it possible to fake SoC temps readings?
Hi everyone, i recently bought a TV Box running the Amlogic S905X and android 6.0. The box idle at 70 °C with only one of the cores running on really low freq, and it can spike up to 90 °C when i use it heavily. i think those reading are not correct, since the heatsink on the chip (I've replaced the original compound with some good quality thermal paste from noctua) is not that really hot. So I wanted to know if it is possible to set an offset to those temperatures, like a -20 °C one, so it will idle at 50 and have spare headroom to boost the clocks when i actually use it. If it is needed i've got the system .img of the firmware, provided by the manufacturer. Let me know if something can be done about this.
Overall speed
Would you say that the Sony Xperia X Compact is "fast" in day-to-day use? A higher rating indicates that you think the Sony Xperia X Compact exhibits fantastic performance. Like, is it as fast as your tears when you watch The Titanic? Then, drop a comment if you have anything to add!
X Compact has really surprised me with its responsiveness. I was expecting a slower phone due to its slower processor but I have been blown away with its responsiveness which surpassed my higher end phone. It must be a combination of its less demanding screen processing with a smaller screen and its updated android version on 7.1.1
I am blown away too. A 7.1.1 update made this a true beast. Coming from Moto Z all I can say I am impressed.
I'd say that overall speed is okay. I'm not blown away by the 30MB/s hardware R/W limitation of the SD card controller. I and a few others with this device have cards that reach well in excess of those speeds (see photo - yes, it's on Windows but tested 3x with different .iso images; on separate media, and never read/written to either device before), and having external storage is certainly a must have in this day and age. I won't really blame the controller speed, it's just an ongoing problem with Android -- where to fix its speed and efficiency (perpetual bloat), you just throw faster hardware at it without really fixing anything (optimization). What really gets me is that Battery Care turns "on" when I tell it to, but it causes more performance issues than it saves battery. It appears to use the same amount of battery whether it's enabled or disabled whether low/moderate/high - so it's detrimental to performance with no real gain in battery (a day's charge is a day's charge). Sony did a pretty good job of optimizing the stock ROM for performance/battery without the middle management (using International/Chinese).
stock CPU GPU throttling performance and modification
Hello Axon 7 users, I just picked up one a couple of days ago. After finally figuring out the bootloader, bootstack and general stock experience I tested a little bit of gaming. I found that a basic game like Clash Royale heats the battery up to around 42°C already with low brightness and slow charging. A more intensive game like the new Knives Out runs only slightly hotter but it becomes apparent that CPU gets throttled soon after loading to 1036MHz across all cores causing lag. It's disappointing so I tried to find how to modify the throttling. Using ZTE's Power Manager setting on performance or balanced doesn't seem to have a noticeable difference.I tried the only stock custom kernel AX7 but it's outdated on B32 and I find it randomly reboots regularly. The stock kernel itself allows some configuration, but the thermal settings in Kernel Adiutor don't reflect any charge. A quick Google search brings up how LG V20 Snapdragon 820 users edit /system/etc/thermal-engine.conf to tweak the throttling levels. Their config is quite different but they mod big to 1824Mhz and let little scale itself. I couldn't get thermal-engine.conf to use the thermal-engine-8996-perf.conf values by copying the values to it as it suggests inside. I tried renaming it with the -zte.conf ending as it suggests as well but that didn't work. After just renaming both the normal and perf conf files with a .bak ending, I've found better throttling performance. Big now throttles to 1632Mhz and little to 1324Mhz. As far as I can understand the files don't have charging rates inside, just GPU and CPU throttling. However as expected the device heats up a few degrees more now. This now puts my battery up to 47°C in Knives Out under the same conditions. Charging is stopped at 45°C by the system so as previously mentioned it's unmodified. I just wanted to check since I couldn't find it mentioned. Is everyone ok with gaming performance limited to 1036Mhz with the normal throttle? Also are my temperatures normal? I guess CPU doesn't seem that high reaching around 65°C, it's just that the battery has less than 20°C difference in intensive performance. I suppose it's a quirk of the heat pipe to battery as heatsink design. I just expected more from a metal unibody chassis and at least normal CPU gaming performance. I thought my Sony Z3 Compact design was bad for battery thermals, with the battery stacked behind the CPU board, sandwiched in insulating glass. But I didn't expect to see a phone to route a heatpipe directly to it's battery. Anyway it is what it is. Follow this information if you want some better gaming performance at the cost of your battery cycle life. In my case I bought the Axon7 just as a separate media consumption device rather than a phone so I can live with the tradeoff. If battery gets bad enough before 2 years I'll consider using warranty at the loss of receiving their refurbished replacement. Manufacturer warranty's in fact cover batteries for 80% depletion. I recommend the app DevCheck Pro for being able to monitor CPU, GPU, temperatures and other things overlayed. I think some others may do similar but they may not be updated for Big Little and are more instrusively overlayed.
Infy_AsiX said: A quick Google search brings up how LG V20 Snapdragon 820 users edit /system/etc/thermal-engine.conf to tweak the throttling levels. Their config is quite different but they mod big to 1824Mhz and let little scale itself. I couldn't get thermal-engine.conf to use the thermal-engine-8996-perf.conf values by copying the values to it as it suggests inside. I tried renaming it with the -zte.conf ending as it suggests as well but that didn't work. After just renaming both the normal and perf conf files with a .bak ending, I've found better throttling performance. Big now throttles to 1632Mhz and little to 1324Mhz. As far as I can understand the files don't have charging rates inside, just GPU and CPU throttling. Click to expand... Click to collapse I read half of that to be honest, but just one thing: To make things harder, ZTE added added a write protection on the system. To disable it you have to use a computer and connect your phone with ADB, then issue "adb reboot disemmcwp" (like DISable EMMC Write Protection). Otherwise all the changes that you made get undone after a reboot, and obviously you'd have to reboot after modifying that file On LOS you can use BeastMode (even if your phone isn't an A2017U) which for me is the best friggin kernel I've used in performance terms. There you can change thermal limits
Infy_AsiX said: Hello Axon 7 users, I just picked up one a couple of days ago. After finally figuring out the bootloader, bootstack and general stock experience I tested a little bit of gaming. I found that a basic game like Clash Royale heats the battery up to around 42°C already with low brightness and slow charging. A more intensive game like the new Knives Out runs only slightly hotter but it becomes apparent that CPU gets throttled soon after loading to 1036MHz across all cores causing lag. It's disappointing so I tried to find how to modify the throttling. Using ZTE's Power Manager setting on performance or balanced doesn't seem to have a noticeable difference.I tried the only stock custom kernel AX7 but it's outdated on B32 and I find it randomly reboots regularly. The stock kernel itself allows some configuration, but the thermal settings in Kernel Adiutor don't reflect any charge. A quick Google search brings up how LG V20 Snapdragon 820 users edit /system/etc/thermal-engine.conf to tweak the throttling levels. Their config is quite different but they mod big to 1824Mhz and let little scale itself. I couldn't get thermal-engine.conf to use the thermal-engine-8996-perf.conf values by copying the values to it as it suggests inside. I tried renaming it with the -zte.conf ending as it suggests as well but that didn't work. After just renaming both the normal and perf conf files with a .bak ending, I've found better throttling performance. Big now throttles to 1632Mhz and little to 1324Mhz. As far as I can understand the files don't have charging rates inside, just GPU and CPU throttling. However as expected the device heats up a few degrees more now. This now puts my battery up to 47°C in Knives Out under the same conditions. Charging is stopped at 45°C by the system so as previously mentioned it's unmodified. I just wanted to check since I couldn't find it mentioned. Is everyone ok with gaming performance limited to 1036Mhz with the normal throttle? Also are my temperatures normal? I guess CPU doesn't seem that high reaching around 65°C, it's just that the battery has less than 20°C difference in intensive performance. I suppose it's a quirk of the heat pipe to battery as heatsink design. I just expected more from a metal unibody chassis and at least normal CPU gaming performance. I thought my Sony Z3 Compact design was bad for battery thermals, with the battery stacked behind the CPU board, sandwiched in insulating glass. But I didn't expect to see a phone to route a heatpipe directly to it's battery. Anyway it is what it is. Follow this information if you want some better gaming performance at the cost of your battery cycle life. In my case I bought the Axon7 just as a separate media consumption device rather than a phone so I can live with the tradeoff. If battery gets bad enough before 2 years I'll consider using warranty at the loss of receiving their refurbished replacement. Manufacturer warranty's in fact cover batteries for 80% depletion. I recommend the app DevCheck Pro for being able to monitor CPU, GPU, temperatures and other things overlayed. I think some others may do similar but they may not be updated for Big Little and are more instrusively overlayed. Click to expand... Click to collapse I have noticed the same performance many months ago. I tried changing the thermal values with both ways through the conf file or a custom kernel but all implementations seem to be faulty as nothing changed. In the end I gave up because I couldn't find a solution for this. But I figured because my games clash of clans, ppsspp, gba emulators don't lag I din't care much. If you find a solution let me/us know. Or post the modded confs you're using as well if you can. That's all from me.
I just renamed both the thermal-engine files with a .bak extension. I've also got ZTE's Power Manager frozen as the performance profiles there don't seem to do anything and I don't use it's other features. There's some kind of CPU GPU throttle still in place but it's much higher as previously mentioned,. After searching further I saw your discussion about /vendor/bin related throttle, maybe that's the fallback it's now on. The device does get uncomfortably hot with a new demanding game at maximum settings. I wouldn't recommend doing this if you want to maintain your battery. However if you're interested I discovered the Ax7 allows defining a lower maximum battery voltage in another TL/DR post https://forum.xda-developers.com/showpost.php?p=74746734&postcount=1353. To explain simply, it's possible to limit the voltage low for health and safety while keeping the device almost primarily powered by mains. Effectively the battery is at an optimum low voltage, practically idle but very hot. A little complicated sure, but worth it. Getting a Daydream V1 tomorrow to play with, this stuff will help with heat and performance a lot. If anyone wants my long winded explanation, give me a shout. The CPU temp does jump around higher than 70. I'm tending to think that current powerful mobile processors aren't efficient enough for the physical body constraints of phones. Let alone poorly designed ones. The 820 is meant to be an improvement over the 810, wouldn't believe it by the throttle required and performance lost. The 835 is efficient enough apparently. From experience though I have my doubts on reviews and benchmarks to reflect real usage stress. edit: Oh and disable VDD restriction in your kernel setting if you've set it to auto enable. That seems to be a switch for the aggressive throttle still available after mod. Sent from my ZTE Axon 7 using XDA Labs
Infy_AsiX said: I just renamed both the thermal-engine files with a .bak extension. I've also got ZTE's Power Manager frozen as the performance profiles there don't seem to do anything and I don't use it's other features. There's some kind of CPU GPU throttle still in place but it's much higher as previously mentioned,. After searching further I saw your discussion about /vendor/bin related throttle, maybe that's the fallback it's now on. The device does get uncomfortably hot with a new demanding game at maximum settings. I wouldn't recommend doing this if you want to maintain your battery. However if you're interested I discovered the Ax7 allows defining a lower maximum battery voltage in another TL/DR post https://forum.xda-developers.com/showpost.php?p=74746734&postcount=1353. To explain simply, it's possible to limit the voltage low for health and safety while keeping the device almost primarily powered by mains. Effectively the battery is at an optimum low voltage, practically idle but very hot. A little complicated sure, but worth it. Getting a Daydream V1 tomorrow to play with, this stuff will help with heat and performance a lot. If anyone wants my long winded explanation, give me a shout. The CPU temp does jump around higher than 70. I'm tending to think that current powerful mobile processors aren't efficient enough for the physical body constraints of phones. Let alone poorly designed ones. The 820 is meant to be an improvement over the 810, wouldn't believe it by the throttle required and performance lost. The 835 is efficient enough apparently. From experience though I have my doubts on reviews and benchmarks to reflect real usage stress. edit: Oh and disable VDD restriction in your kernel setting if you've set it to auto enable. That seems to be a switch for the aggressive throttle still available after mod. Click to expand... Click to collapse That's weird... what are the ambient temps where you live? Here it's anything between 20 and 30 degrees and mine never gets that hot, and it barely throttles. Of course you shouldn't game while charging, that WILL throttle the phone. I have a big old CPU heatsink without a fan, and when I charge the phone at night I just put it upon the heatsink. It keeps the battery around the ambient temp, which I guess helps with battery degradation. A nice app for monitoring the CPU is Trepn profiler, you can program it to show you anything like frequencies and temps on 2 separate graphs for example