[Q] Heat...? - Nexus 7 Q&A, Help & Troubleshooting

I am beginning to suspect that there may be a simple reason 'some' N7's are having crash issues with custom kernels/ROMs. I have a small temperature & CPO widget, and also use Sense Analog Clock w/system data, and I have been paying attention to - temperature. FULL DISCLOSURE: I use a case that is very solid and enclosing, as I travel a lot and want my N7 protected well, and that may be keeping some additional heat in via insulation.
In any event, I notice that the N7 starts out at about 79.5F, but with even moderate use, is over 85F. I use mine mostly for reading news and books, I don't play games on it, and only review the occasional youtube news video. Could the 'culprit' be simply overheating?
It would be interesting to have some small app that would record CPU, GPU & memory use, temperature, and 'crash' information - we might be able to get to the 'bottom' of the sporadic freezes/crashes that some are experiencing.
Will cross post this in a couple of places. jf

friedsonjm said:
I am beginning to suspect that there may be a simple reason 'some' N7's are having crash issues with custom kernels/ROMs. I have a small temperature & CPO widget, and also use Sense Analog Clock w/system data, and I have been paying attention to - temperature. FULL DISCLOSURE: I use a case that is very solid and enclosing, as I travel a lot and want my N7 protected well, and that may be keeping some additional heat in via insulation.
In any event, I notice that the N7 starts out at about 79.5F, but with even moderate use, is over 85F. I use mine mostly for reading news and books, I don't play games on it, and only review the occasional youtube news video. Could the 'culprit' be simply overheating?
It would be interesting to have some small app that would record CPU, GPU & memory use, temperature, and 'crash' information - we might be able to get to the 'bottom' of the sporadic freezes/crashes that some are experiencing.
Will cross post this in a couple of places. jf
Click to expand...
Click to collapse
Desktop CPUs generally will run up to 85C, which is 185F. I suspect mobile CPUs are not specced nearly that high, but you have nothing to worry about there.
Are there variations, issues, solder problems? Sure, any of that could happen, and be exposed under various thermal stresses. But 85f is nothing to be concerned about.

khaytsus said:
Desktop CPUs generally will run up to 85C, which is 185F. I suspect mobile CPUs are not specced nearly that high, but you have nothing to worry about there.
Are there variations, issues, solder problems? Sure, any of that could happen, and be exposed under various thermal stresses. But 85f is nothing to be concerned about.
Click to expand...
Click to collapse
Agreed... but I'm getting that on light usage - I wonder what the game players are getting.. and if heat is causing a lot of the problems being reported on the N7 on XDA...

Related

3.1 OCed to 1.6 GHz, FCs & Artifacts in Dolphin

Wondering if anyone is experiencing artifacting while overclocking. I'm getting great quadrant scores, and all else is smooth. I've only been running this configuration for a few hours, so I haven't checked out any games yet for the artifacting. I'm not concerned about the FCing (twice so far) because I can just turn down the clock in SETCpu, but the artifacting makes me nervous about doing permanent damage to the video card.
Is my concern valid, or should I relax?
In the Xoom channel, we actually ran alot of test using dolphin and HULU. Alot of people can not get a video to play at 1.6 for a long period of time. Either the browser crashes or the xoom itself crashes. You may want to back down to 1.4 for now.
Psychokitty said:
Wondering if anyone is experiencing artifacting while overclocking. I'm getting great quadrant scores, and all else is smooth. I've only been running this configuration for a few hours, so I haven't checked out any games yet for the artifacting. I'm not concerned about the FCing (twice so far) because I can just turn down the clock in SETCpu, but the artifacting makes me nervous about doing permanent damage to the video card.
Is my concern valid, or should I relax?
Click to expand...
Click to collapse
Relax. No problem. as long as you did not smell any smoke from your xoom or feel it getting extremely hot.
High temperature is the main reason causing hardware permanent damage.
You wont do any permanent damage to your Xoom since pretty much all modern CPUs have built in protection for such scenarios on the hardware or firmware level. The worst that can happen is the Xoom shutting down.
Sent from my PC36100 using Tapatalk
Lol!...."smoke".
alex2792 said:
You wont do any permanent damage to your Xoom since pretty much all modern CPUs have built in protection for such scenarios on the hardware or firmware level.
Click to expand...
Click to collapse
I know it's nearly impossible to kill a CPU because of this reason (besides maybe severely overvolting it by about a misplaced decimal point...), but I didn't know if gpus also had these same built-in failsafes. I figured since the development of mobile hard core gaming machines that they certainly should by now, but last time I paid any attention to the technology was when I was upgrading laptops with the "new" Dothans, and they had cutting edge ATI M9800s in them!
Thanks, everyone.
I have standard xoom us wifi 3.1 and i also have sometimes artifacts. that is a feature!
dolphin browser hd
hdtvpower

[Q] Considering rooting 10.1 but...

I have never rooted any of my Android devices because I've never really had any reason to. That and I was always nervous to do with my Droid Incredible even though I'm a computer guy.
However, I am considering rooting for this device because of some benefits I've read about such as:
1. Overclocking
2. Better battery life
3. Additional apps or functionality (I want to use Google Movies, Netflix, Hulu Plus, etc and I am guessing root might help get some of this sooner based on some of the other threads)
My concern is whether overclocking has any risk to the processor long term in the tab? For some reason, I seem to have something in my head from years back that overclocking computers/devices could cause processors to overheat or something. Maybe this is an old concern from when I was in college that was specific to PC hardware?
Also, aside from sticky threads, is there any thing on the wiki that talks a bit more about some of the apps used to manage ROMs and backups along with what is preferred and why? I read a good rooting guide thread in Android development forum but apps change all the time and I read different things in each thread that it can be hard to follow jumping in now.
If I missed a thread, feel free to point me to it.
Thanks.
Overclock always carries risks to hardware, especially without proper configuration. When overclocking you will use apps such as SetCPU or others, these apps typically have 'profiles' set up. On my LG G2x I have profiles set like:
Default 1.5GHz
Screen Off 400mhz
Battery Tempurate 48c Downclock to 800mhz
These settings will give you great performance, great battery life and a safety net assuming you leave your phone in direct heat. Sometimes if the battery gets too hot you'll damage your hardware, I've had this happen to my old Nexus One where I now have a very dark spot measuring about half an inch around on my display.
In consideration to rooted apps for Galaxy Tab... Hulu works without root by simply installing a modified Adobe Flash Player and adjusting your browser configuration to reflect a desktop user agent (You can easily find all this information using Google). Google Movies probably won't be available to rooted devices due to the agreement that Google signed with production companies, and whether root will allow you to run this application really depends on the way the content is delivered, however, I'm sure someone will figure it out.
Overclocking the Galaxy Tab probably will resemble the performance measures of other Tegra based devices. G2x can acheive 1.5GHz and Xoom 1.7GHz. Stability is really hit or miss as no two cpu's are created equal. I'm on my third Galaxy Tab and my third G2x and have not ran into an issue where I can't overclock to the speeds which kernel developers are building.
Edit: There is really only one overclock kernel available right now for the 10.1 and Pershoot is working hard to make it stable and powerful, the current 'preview' has quite a few stability issues.
So, hopefully this helps you out. Just an FYI though, really try and search. This has been repeated hundreds of times throughout various different forums. The general consensus is that rooting provides far too many benefits to be afraid of hurting your device, and so long as your are able to A. Unroot the phone for manufacture warranty B. Backup and restore using Nandroid, you will not have any issues that can't be resolved.
Heat is bad for electronics, and any time you increase the operating frequency or voltage of a microprocessor, you're going to be generating more heat. Modern hardware has thermal monitoring and throttling capabilities, and as such you're going to be able to simply fry your processor by pushing it too hard. However the additional stress is is accumulative and will shorten the life of your hardware.
That being said, I suspect that the operational life time of the chips in our tablets (and virtually any modern computer) is several orders of magnitude longer than their useful life time. I'm not entirely sure how long these processors last if operated at spec (it may be in a white paper somewhere), but I suspect it is on the order of many decades, if not centuries.
mesasone, true it will generate heat at full load but in all reality my G2x rarely throttles all the way up to 1.5GHz unless I manual set it to for benchmarking.
Thanks wesbalmer and mesasone. I've been reading threads all day for the last 6 hrs before posting but I'll search a bit more next time. This was helpful in reassuring me though.

My nexus 10 getting warm from only web browsing.

My nexus 10 had become really warm around back camera after using chrome apps for a few minutes about 7 minutes or so. Web site I mostly visit are
kotaku.com
theverge.com
batoto.com
This noticeable warmness only occur when I use web browser app. Funny thing that when I watch movie using MX player Hw+, watching anime MKV 8 bit the device never seem to get hot, except when watching in SW for 10 bit anime it get extremely hot.
Youtube app also shows no singe of this warmness.
Do I get the defected device? Please help me with this I really don't want to get the replacement.
Thank you for your time.
benzs129 said:
My nexus 10 had become really warm around back camera after using chrome apps for a few minutes about 7 minutes or so. Web site I mostly visit are
kotaku.com
theverge.com
batoto.com
This noticeable warmness only occur when I use web browser app. Funny thing that when I watch movie using MX player Hw+, watching anime MKV 8 bit the device never seem to get hot, except when watching in SW for 10 bit anime it get extremely hot.
Youtube app also shows no singe of this warmness.
Do I get the defected device? Please help me with this I really don't want to get the replacement.
Thank you for your time.
Click to expand...
Click to collapse
If it's only getting hot with certain apps or content, it's probably those apps or content stressing your device, not the device being defective. This CPU does get a bit hot sometimes. I don't know if all ARM CPUs are like this, or just the ones I have.
I suggest you install the Battery Widget app by Elvison, so that you can see how hot Android says the CPU is getting when you do these things. We can then compare temperatures, if you also note the background temperature in your town when you are testing, so we can compare how much hotter the device gets from the baseline background temperature. I have gotten my HTC One X+ to report a temperature of 60 degrees C when playing a lot of HD video, but while my Nexus 10 gets somewhat hot, it never gets that hot. :fingers-crossed:
benzs129 said:
My nexus 10 had become really warm around back camera after using chrome apps for a few minutes about 7 minutes or so. Web site I mostly visit are
kotaku.com
theverge.com
batoto.com
This noticeable warmness only occur when I use web browser app. Funny thing that when I watch movie using MX player Hw+, watching anime MKV 8 bit the device never seem to get hot, except when watching in SW for 10 bit anime it get extremely hot.
Youtube app also shows no singe of this warmness.
Do I get the defected device? Please help me with this I really don't want to get the replacement.
Thank you for your time.
Click to expand...
Click to collapse
Hi, that is perfectly normal. What a lot of people don't know is that web rendering is one/if not the most CPU intensive ask you'll do on your tablet. So for it to get warm at the back after several minutes stressing the CPU out from web rendering is not bad at all. It's nothing to worry about, every phone/ tablet does this. Hope this helps
Plus the wifi chip dumps out a lot of heat just by itself, even if it isnt even being used very hard.
EniGmA1987 said:
Plus the wifi chip dumps out a lot of heat just by itself, even if it isnt even being used very hard.
Click to expand...
Click to collapse
The wifi combo chips don't draw a lot of power, and usually go into a low-power idle mode for even less draw (already just a few milliwatts max)...
(Giving benefit of doubt because N10 has dual MIMO fancy chip. Might draw a bit more. Still feels wrong, though.)
Are you sure?
Yep I am very sure. If I leave the wifi on when I play a game I will hit thermal throttling WAY faster than with it off, and the tablet feels much warmer overall as well. Turning wifi off and doing the same thing lowers the reported temperatures by around 5-6 degrees Celsius.
believe it or not it probably chrome... i had the same issue with my nexus 4.... try using boat browser or something else lightweight and see if that changes anything
EniGmA1987 said:
Yep I am very sure. If I leave the wifi on when I play a game I will hit thermal throttling WAY faster than with it off, and the tablet feels much warmer overall as well. Turning wifi off and doing the same thing lowers the reported temperatures by around 5-6 degrees Celsius.
Click to expand...
Click to collapse
Right, but the correlation between heat reducing with wifi off doesn't mean the wifi chip itself is the source of the heat. It could just as easily be that having wifi on allows background processes to connect to the network, and their use of the CPU increases load, thus heat.
I'm not saying you're wrong, I'm just saying that assuming cause from correlation is tricky.
Should be easy to resolve for someone with a laser thermometer.
Another thought: Display brightness is directly related to a fair amount of heat output. Maybe you changed that setting.

Nexus 10, is it that bad?

I've been reading for quite awhile because I got myself one (it's still on the way to me, so no hands on yet). I got it mainly because it's a Nexus and I'm done with those 3rd modifications on top of vanilla.
However, I'm getting really mixed comments from all of you guys. Some said it's really nice, some said it's the worst tablet. Although things are always going back to people's own preference but from what I read, 4.2.2 did give lotsa headaches to users mainly because of leaked memory and so.
So users, can you give me your truthful comments from both pros and cons? I can only get the device by next week and after that, it will be my time to list out my very own pros and cons.
Thanks and cheers!
Nexus4 modded with cyanogen.
Yeah, you better cancel your order because some random a holes on the internet did not like something.
Well, the problem is, I can't. Plus, I'm still quite skeptical about the reboots and I have faith that it will be fixed with the update soon.
Are you one of the users?
I'm definitely ok with a bit of problems and it gives me perfect reason to root and tweak it on myself although some do claim that, it should work perfectly fine out of the box.
Nexus4 modded with cyanogen.
I'm running stock and can definitely say that the surfaceflinger memory exists. It becomes obvious when you play multiple videos (streaming or video files). When you do other activities this bug is not readily apparent.
I also from time to time get random WiFi disconnects, which are easily fixed by toggling the WiFi off/on. With that being said I really like my N10 and am using it for more than I expected when I bought it. The display resolution, I/O speed and CPU are all outstanding.
At least the memory leak can be fixed and I read that the surfaceflinger driver developer already has it ready. This gives me hope that Android 4.3 will include the fix. The N10 used as a media consumption device is very good/excellent. I am not disappointed with my purchase.
My laptop at the about same price point (after including N10 accessories) has not been turned on in over three months. All my news reading has move from my desktop PC to the N10. I was surprised at how smooth that transition went.
The only thing that really bothered me about the Nexus 10 is how it could throttle and lower CPU clocks under general usage (general being like playing a game). But then again, the Nexus 4 also does this...
Aside from that though, I find the N10 pretty awesome
The light bleed at the bottom right is the only thing that has bothered me much, but that's because the threads here pointed it out and turned on an OCD switch in me. After almost a month, I had my first two reboots last night, both while watching an hourlong streaming video from a TV network site (using Firefox with Flash). Other than that, couldn't be happier with my N10.
3DSammy said:
I'm running stock and can definitely say that the surfaceflinger memory exists. It becomes obvious when you play multiple videos (streaming or video files). When you do other activities this bug is not readily apparent.
I also from time to time get random WiFi disconnects, which are easily fixed by toggling the WiFi off/on. With that being said I really like my N10 and am using it for more than I expected when I bought it. The display resolution, I/O speed and CPU are all outstanding.
At least the memory leak can be fixed and I read that the surfaceflinger driver developer already has it ready. This gives me hope that Android 4.3 will include the fix. The N10 used as a media consumption device is very good/excellent. I am not disappointed with my purchase.
My laptop at the about same price point (after including N10 accessories) has not been turned on in over three months. All my news reading has move from my desktop PC to the N10. I was surprised at how smooth that transition went.
Click to expand...
Click to collapse
espionage724 said:
The only thing that really bothered me about the Nexus 10 is how it could throttle and lower CPU clocks under general usage (general being like playing a game). But then again, the Nexus 4 also does this...
Aside from that though, I find the N10 pretty awesome
Click to expand...
Click to collapse
JasW said:
The light bleed at the bottom right is the only thing that has bothered me much, but that's because the threads here pointed it out and turned on an OCD switch in me. After almost a month, I had my first two reboots last night, both while watching an hourlong streaming video from a TV network site (using Firefox with Flash). Other than that, couldn't be happier with my N10.
Click to expand...
Click to collapse
Here's the thing that I always talk about. It's a nexus and all problems will be solved for sure by Google itself. With such a good display as well as the A15 architecture proc, it's really a beast and let alone the pure vanilla android.
People are a little bit over exaggerated about the bug, IMO. We receive the newest version and bugs are bearable with me. At least buyers should be aware of the firmware is always the latest which might be a little big buggy. Few positive comments over here are really making my day.
Another thing that bothered me is available RAM. Google states the tablet has 2GB of RAM, which is true (there is 2GB worth of RAM chips installed on the motherboard technically). Before 4.2.2, about 400MB was reserved specifically for the GPU, which is the largest amount of RAM I've seen on any Android device, so that left 1.6GB usable. Not that bad, and it still rounded to 2GB (most other devices though to be fair take like 200-300MB; but the N10 is driving a pretty beefy resolution)
WIth 4.2.2, the RAM reserved for the GPU doubled to 800-some MB (836?). So now the total RAM that the user can use on their own is 1.2GB. No longer nearly close to 2GB.
I guess nothing can really be done about it now, but I don't understand why there just isn't dedicated memory just for the GPU, or why Google doesn't just advertise how much RAM is actually available to use. This isn't an issue at all on most other devices, since the missing memory is usually a small amount, but when almost half of the advertised RAM is missing and not even user-configurable (most computers with IGPs sharing system memory at least let you specify how much you want to dedicated to it)... I find that pretty shady :/
On the other hand, I don't have any out-of-memory problems though (aside from the surfaceflinger thing), so it doesn't seem to be an "actual" issue.
I haven't really noticed anything wrong with my nexus 10 I think its great and fast. Also 4.3 is going to be released soon which should fix any software related issues and make it even smoother . I don't use my tablet as much as others might so maybe that's why I don't notice anything wrong. I generally use it 2-3 hours a day and the only thing I hat is the charging time which feels like forever and that it has a phablet ui rather than tablet look which wastes a little screen space. What they should do is get rid of notification bar and combine it with Nav bar like other tablets
Sent from my Xperia Play (r800x)
abdel12345 said:
... What they should do is get rid of notification bar and combine it with Nav bar like other tablets.
Click to expand...
Click to collapse
Use full!screen and LMT/PIE and get all the screen resolution back (full 2560x1600). full!screen gets rid of both bars and provides a notifications pop-up while LMT/PIE can be configured with all the navigation buttons plus much more. I've been using that combination on rooted stock for months now and would never go back to the waste of space that either bar takes.
I like the clean AOSP browser in fullscreen mode plus thumb controls but it does not always paint properly when used with full!screen (artifacts where the navigation bar used to be). I switched to Ocean browser which is really AOSP with a new UI and that fixed the fullscreen paint issue.
3DSammy said:
Use full!screen and LMT/PIE and get all the screen resolution back (full 2560x1600). full!screen gets rid of both bars and provides a notifications pop-up while LMT/PIE can be configured with all the navigation buttons plus much more. I've been using that combination on rooted stock for months now and would never go back to the waste of space that either bar takes.
I like the clean AOSP browser in fullscreen mode plus thumb controls but it does not always paint properly when used with full!screen (artifacts where the navigation bar used to be). I switched to Ocean browser which is really AOSP with a new UI and that fixed the fullscreen paint issue.
Click to expand...
Click to collapse
Awesome thanks a lot man I'll try that out
Sent from my Xperia Play (r800x)
billy_overheat said:
Here's the thing that I always talk about. It's a nexus and all problems will be solved for sure by Google itself. With such a good display as well as the A15 architecture proc, it's really a beast and let alone the pure vanilla android.
People are a little bit over exaggerated about the bug, IMO. We receive the newest version and bugs are bearable with me. At least buyers should be aware of the firmware is always the latest which might be a little big buggy. Few positive comments over here are really making my day.
Click to expand...
Click to collapse
If you can deal with random reboots don't worry about it. It really is something that depends on use. Watching YouTube via chrome will exacerbate the reboots. The actual app doesn't seem to eat the memory. However for my use I can't have it rebooting in the middle of a meeting or trying to dial into work so it has become something of a paperweight. I know how to consume the memory and how to avoid it but it will still eventually reboot. If your using it for goof off purposes instead of productivity you'll be fine. Also, please don't be an Android/Google apologist. They've had 6 months to fix the issue. And they don't market it as a device with buggy firmware that will reboot. If they called it Nexus 10 developer edition I'd agree with you.
Sent from my Nexus 4 using Tapatalk 4 Beta
billy_overheat said:
So users, can you give me your truthful comments from both pros and cons? I can only get the device by next week and after that, it will be my time to list out my very own pros and cons.
Click to expand...
Click to collapse
Pros:
- Highest resolution tablet on the market, nobody else comes close, even latest iPad has 25% less pixels. I had a Thunderbolt display at work last year and loved working with so much screen real-estate, well, this tablet has even more pixels in 10" than that display had in 27".
- First Android device with beefy Cortex A15 CPU, the Exynos 5 Dual, still the only tablet on the market with A15.
- I actually like the build, fairly thin and I like the sticky material on back.
- For $500 for 32 GB, the one I got, you won't find any device with such high-end specs.
- Android 4.2.2 is usually fairly snappy, sometimes I go back and forth between the home screen and the application drawer just to see the snazzy zoom-in/zoom-out animation and how fast it is.
Each one of these comes with drawbacks however.
Cons:
- You want a high resolution, you have to pay for it with power draw. The display consistently accounts for about 60% of battery usage, even though I keep the brightness at about 30% under light and dial it down to the lowest setting in a dark room. The colors are good but a bit washed out, particularly when compared to an iPad. I wish it had a matte display like my Zenbook, as the glossy display does catch reflections, but I'm not sure that's possible for a tablet.
- The Exynos 5 CPU takes more power than it should and runs somewhat hot. Not as hot as the Tegra 3 in my HOX+, but fairly warm.
- I was surprised how heavy 1.3 lbs felt from the first time I held it. The battery in this thing is huge, 9Ah, compared to 2-3 Ah in most current flagship phones, like the One or S4. It probably had to be so big with that power-sucking display and CPU, but it adds weight.
- The build is a bit creaky and sometimes feels like you have to snap particular pieces back into place, probably to be expected at this cheap price.
- Android still has times when it starts lagging and everything you do takes a second or two to register. These slowdowns often come out of the blue and you're never sure what's going on. This is a mobile OS, so prepare to be frustrated when apps are backgrounded and cached data is lost, particularly if you're expecting something closer to desktop performance because of the specs. The known memory leak in 4.2.2 exacerbates this problem.
I'm happy with my Nexus 10, as I enjoy the high resolution and don't use it anywhere as much as my ultrabook. Now that I know about the memory leak, I may start trying to use it for web reading again, which I had to give up on because it was unusable when Chrome would start reloading every page for no reason. Now I know to reboot when that starts happening, so I at least have a workaround till they fix it.
I love the tablet, for the way I use it - which may be considered light use by most here - it is perfect. The memory issue is real there is no doubt about that. But it is also easily avoided. I reboot my N10 with a tasker profile once during the night and that is that. However I game on it very rarely and use it mostly for streaming movies or just browing the web. One reboot each night seems to be enough to not make these issues appear.
Having said that I have none of the other reported issues, no random reboots or whacky Wifi - I turn Wifi off when the tablet is not in use - but I am also running SentinelRom which seems to be ironing out a lot of the smaller issues. With this ROM scrolling for example has become a silky smooth affair.
Battery life is excellent, much better than the boards make it out to be. I rarely use the N10 with brightness above 25% because it is already so bright on that setting there is no need for it. There may be light bleed - hey it's an LCD after all! - but I never notice any the way I use it. The display is gorgeous in every way, shape and form and I really really like the fact that putting it on lowest brightness makes it really dark. This is perfect for using it in bed at night without getting eye cancer.
With the POGO charger the tablet even has decent charging speed.
Regarding build quality I cannot complain at all. My tablet is not creaky in the least. I had a TF101 which was way worse. I mostly use it with a Poetic smart cover and couldn't be happier. The weight is of course noticeable, but then again this is 10 inches of hardware, it will never feel light as a feather.
Still there are some undeniable software issues still present. The memory leak being one, some issues with scrolling (except when using SentinelRom) being another. But I have yet to see the "perfect" android device which so far does not exist. Google still has a lot of work to do.
rxnelson said:
If you can deal with random reboots don't worry about it.
Click to expand...
Click to collapse
Not getting the random reboots you speak of. Use my tablet 3-4 hours per day, sometimes more, and do not recall having 1 reboot. AOSP browser closures, yes, though with newer versions not as much. Have 2 Nexus 10 tablets, one stock, one sw display itching between SaberMod and Buttered AOKP.
Had both theTF101 and TF700. Went with the ASUS because of it's IPS+ display and SD card slot. 5 weeks after receiving, had to send it in for charging issues..oneof my main problems with the TF101. For the slight amount of money more for the Nexus 10, it is a much better option. Check out Swappa.com-can typically get a slightly used Nexus 10 for a really good price
mpicasso said:
Not getting the random reboots you speak of.
Click to expand...
Click to collapse
You left out my next sentence. It depends on use. I can duplicate the surfaceflinger issue with eventual reboot on stock CM, buttered AOKP, and rasbean. Obviously we use the tablet differently.
Sent from my Nexus 4 using Tapatalk 4 Beta
rxnelson said:
You left out my next sentence. It depends on used. I can duplicate the surfaceflinger issue with eventual reboot on stock CM, buttered AOKP, and rasbean. Obviously we use the tablet differently.
Click to expand...
Click to collapse
I also left out the statement that got me to post originally: "However for my use I can't have it rebooting in the middle of a meeting or trying to dial into work so it mass become something of a paperweight." As the OP was curious about the reliability of this tablet, I wanted to offer a different perspective.
As a tablet for business, I use it for surfing (quote obtained from website, along with any needed client info), note taking, power point and excel, E-mail, along with a few other things. In a given day, I may spend 3-4 hours, while in client homes, using my tablet. So yes, we may use these differently, but for any "business" function I have thrown at it, it works fine. I also do not do many video presentations, which may explain why I do not experience the same issues as you.

Overkill Resolution for high gfx gaming? Samsung got you covered!

Hello all, one of the main reasons why i chose the xperia z1 compact over a galaxy s5 by then was that i knew that z1 compact had much more power to spare for future gaming thanks to the low screen resolution, It was very hard for me to choose this time galaxy s6 over z5 compact for the same reason, but i succumbed to the bigger better oled screen this time around even though i was upset at the senseless screen resolution of 1440 x 2560 which made it clear that the phone would struggle with current high end games to keep 60fps let alone future games...
Well after playing Dead Trigger 2 with all gfx on max surprise surprise, the phone could not keep up with its absurd screen resolution a steady 60fps so i started thinking if there was a proper screen res changer tool this time around as i was a bit familiar with some of them in the past which done a poor job and many times left the phone unusuable thx to the resolution affecting the OS itself aswell.
Well guess what, Samsung woke up and presented galaxy s6 owners (and some other high end galaxy models) with a very nice solution.
Its called Game Tuner, officially made by Samsung and you can find it here:
https://play.google.com/store/apps/details?id=com.samsung.android.gametuner.thin&hl=pt_PT
What it does is exactly what all the games should have in the first place, options to choose resolution for your game without changing the resolution for your OS GUI, on top of that, you have a nice control panel profile system which allows you to setup different settings for different games installed in your phone, this apps benefits you with the following:
1)Lower graphics resolution for any games of your choosing,
2) It allows you to even force 3D games which are running at a lower resolution than your screen to actually run at highest resolution supported by your screen,
3)It also allows you to lock FPS to 30 instead of 60 if you would like to preserve some battery life.
4)Allows you some brightness control per game.
Here are the more confusing settings explained:
High (turns all games to the highest resolution of the phone screen) almost impossible to observe pixelization
Medium (turns all games to a tad lower res (i believe 1920*1080) difficult to observe pixelization
Low (turns all games to an even lower res( i believe 1270*720) pixelization visible but not too ugly
Extreme Low (turns all games to the lowest resolution possible (i believe 840*472) as i see alot of pixelization
Custom (Allows you to select each game with a specific profile (high, medium, low, extreme low).
Now you can fully enjoy that 2k screen without reprecussions!
Give it a try and have fun!
EDIT: If any questions feel free to ask and ill try to help as i can.
Wow, thanks for sharing. Works great. You can even specify the resolution, fps and brightness per game.
Verstuurd vanaf mijn SM-G920F met Tapatalk
NP, glad you like it, updated thread with more information and corrected some grammar issues.
You can already find this in the S6 themes and apps section. No need to post this here
Thanks, this is really cool. I wouldn't have seen it if you hadn't posted it here! I wish it would actually tell you what resolution each of the settings are. I tried taking a screenshot in game after I enabled it and then checking the "details" in gallery but it still said 2560*1440.
Now I'd like to know how I can completely disable it? It seems even after uninstall the settings remain. I'd like to now bypass the 60FPS limit.
lite426 said:
Thanks, this is really cool. I wouldn't have seen it if you hadn't posted it here! I wish it would actually tell you what resolution each of the settings are. I tried taking a screenshot in game after I enabled it and then checking the "details" in gallery but it still said 2560*1440.
Now I'd like to know how I can completely disable it? It seems even after uninstall the settings remain. I'd like to now bypass the 60FPS limit.
Click to expand...
Click to collapse
The settings wont remain after uninstalling, i say this because i tried it myself by setting a game to lowest resolution possible and after uninstalling it rolled back to normal, many people believe that, without modding, all games will run by default on the highest resolution supported by your screen, this is a false assumption, and you can easelly notice that with games such as Asphalt 8 and Real Racing 3.
Indeed it should specify resolution instead of "very low, low, med, high," thats why the thread settings are nothing more but assumptions.
Also setting it to MED is considered the default setting for said game in this app so maybe med is actually the default app resolution.
crzykiller said:
You can already find this in the S6 themes and apps section. No need to post this here
Click to expand...
Click to collapse
Well, i think it doesn't stress anybody, but the opposite: more users will know about it. It seems this app is not that popular, many users have no idea about it (i found it a couple of weeks ago by mistake in playstore).
The app should receive more coverage in media too. This will be a win-win situation for all, and maybe samsung will add a system-wide option for resolution change (yeah, keep dreaming)
I believe beying able to choose fullscreen resolution of your phone shouldve been a thing implemented by default, im Really happy that samsung thinked of this for my S6 as i can play games like dead effect 2 with extreme graphics but reduced resolution (almost imperceptible pixelization) and get a rock steady 60fps, the only strange thing it semms that it is happening is that after a level or two the game starts to loose performance, other users also reported this issue, samsung will hopefully fix it in the next app update.
TheWarKeeper said:
I believe beying able to choose fullscreen resolution of your phone shouldve been a thing implemented by default, im Really happy that samsung thinked of this for my S6 as i can play games like dead effect 2 with extreme graphics but reduced resolution (almost imperceptible pixelization) and get a rock steady 60fps, the only strange thing it semms that it is happening is that after a level or two the game starts to loose performance, other users also reported this issue, samsung will hopefully fix it in the next app update.
Click to expand...
Click to collapse
I think you should also disable DVFS for optimal performance gains.
vnvman said:
I think you should also disable DVFS for optimal performance gains.
Click to expand...
Click to collapse
Yes that would increase performance but its a heavy risk considering you might burn up ur cpu or gpu and void the warranty
TheWarKeeper said:
Yes that would increase performance but its a heavy risk considering you might burn up ur cpu or gpu and void the warranty
Click to expand...
Click to collapse
I may be wrong but I assume unless you game all day long it shouldn't make too much of a difference in terms of lifespan (assuming one swaps phone every 2 years or so), pretty much like OC/OV.
vnvman said:
I may be wrong but I assume unless you game all day long it shouldn't make too much of a difference in terms of lifespan (assuming one swaps phone every 2 years or so), pretty much like OC/OV.
Click to expand...
Click to collapse
Indeed OC reduces lifespan of said component but the problem is more serious than that, if you disable the throttle the GPU or CPU might overheat, it depends on the phone and the chips inside and also the heat dissipation quality which can range from different thermal pastes to different heatsinks and to where is that heat transfered after that, its a risk of hardware damage without knowing its internal chips temps.
But thats just me who knows maybe im wrong.
TheWarKeeper said:
Indeed OC reduces lifespan of said component but the problem is more serious than that, if you disable the throttle the GPU or CPU might overheat, it depends on the phone and the chips inside and also the heat dissipation quality which can range from different thermal pastes to different heatsinks and to where is that heat transfered after that, its a risk of hardware damage without knowing its internal chips temps.
But thats just me who knows maybe im wrong.
Click to expand...
Click to collapse
Well that would totally make sense, but at least as to OC+slight OV it has been tested that the possibility of making some actual damage will most likely be very slim untill around the 5 year mark or so of usage. As to DVFS, by disabling that you don't actually disable throttling completely, which is still managed by the kernel (as it should), but only Samsung's more aggressive throttling which is completely unnecessary because it's always trying to keep the phone "super cool" at the expense of performance, while some people who are into heavy games would use a device hot to the point that it causes mild discomfort (but still safe for the components), rather than a device that is slightly cooler but gets laggy after 2 minutes of actual gameplay.
I guess it's up to the user to decide whether to mess with this or not, maybe for most people it won't be worth even the slight risks but for people like me who happen to enjoy heavy games and swap phones every year and a half or so it's good to have the option.
vnvman said:
Well that would totally make sense, but at least as to OC+slight OV it has been tested that the possibility of making some actual damage will most likely be very slim untill around the 5 year mark or so of usage. As to DVFS, by disabling that you don't actually disable throttling completely, which is still managed by the kernel (as it should), but only Samsung's more aggressive throttling which is completely unnecessary because it's always trying to keep the phone "super cool" at the expense of performance, while some people who are into heavy games would use a device hot to the point that it causes mild discomfort (but still safe for the components), rather than a device that is slightly cooler but gets laggy after 2 minutes of actual gameplay.
I guess it's up to the user to decide whether to mess with this or not, maybe for most people it won't be worth even the slight risks but for people like me who happen to enjoy heavy games and swap phones every year and a half or so it's good to have the option.
Click to expand...
Click to collapse
I tought the DVFS disabled the throttle completely, its good to know it doesnt then and i agree, the samsung throttle is overreacting and prolly did better good with it off than on, thanks for your suggestion.
TheWarKeeper said:
Yes that would increase performance but its a heavy risk considering you might burn up ur cpu or gpu and void the warranty
Click to expand...
Click to collapse
I play with Samsung DVFS always off and I can play dead effect for 2 hours straight without performance degradation... CPU doesn't go over 75-80*C depending on the ambient temperature

Categories

Resources