A little disclaimer: I'm not entirely sure this is the right place for the post, if it's not any mod feel free to move it I found a bunch of similar posts under this section after a quick search so I decided to post it here; once that said let's move on. After some months of using the HTC 10 and after months of not having any accidents, I finally decided to send it to SAT to fix some scratches the phone has on the back and some light bleeding on the left side of the panel after a drop. Knowing the process could take weeks, I decided to buy a spare phone and I bought a Galaxy S6 which I got for just $275. I've passed the following days synching, installing apps and using the phone while I was ready to send my HTC 10 and in the process I've noticed something I hadn't and I probably wouldn't until you use two phones side by side: the HTC 10 has some is underperformed in most of tasks where in the past it used to excel for its optimization.
First I noticed something as simple as facebook app was a ton smoother on the Galaxy S6 than on the HTC 10, running both the exact same version (103.0.0.20.72) not talking about things opening fast which is not the case most of the time, but losing a lot of frames while doing actions like opening reactions panel which sometimes stutters and looks like "in slow motion" on the 10 at the point I need to close the app from RAM here and there to keep it smooth which is not the case on the Galaxy S6 and other stuff like reactions flickering while playing gifs or videos and not happening again on the S6.
At first I just thought "meh facebook it's a poorly optimized app so must be the isolated case" but then I noticed a HUGE difference in graphics performance as well, when I thought the Adreno 530 was better overall compared to the Mali on the Galaxy S6. These are both screenshots taken on the HTC 10 and the Galaxy S6 running Need for Speed: No Limits on the same car and similar race conditions. This is the HTC 10 ss:
{
"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"
}
And this is the Galaxy S6 counterpart:
There's a loss in definition for both while looking at the screenshots on bigger displays of course, it was less notorious on the devices screen but it was there and still was obvious. Just look at the lines on the back cover of the car. Then I thought it was some specific random failure on the renders, but the same happens over and over, look at this pic of the LaFerrari on the start line, HTC 10:
Now the Galaxy S6 screenshot, same race, same car, same weather condition:
There's a lot of differences: the brake lines, the car's plate, the wheels, the car hoops...
Honestly I didn't even know where to start looking for answers, so here we go: is there any limitation on the graphics card on the HTC 10 stock firmware making it look that inferior? Do I need another factory reset (I've had to a couple times after weekly security patch updates so far), is this improved with custom ROMs? Is my device faulty? I don't know how to feel about this right now, I guess I'm just shocked. Just in case I disabled the screen lowering resolution on the HTC 10 and did reset the device and wait for it to completely cool down before running the game and taking the screenshots
Thanks for your time and any advice you can give to the subject
I would definitely start with a fresh, clean wipe/install (RUU if you can) to compare apples-to-apples.
Rolo42 said:
I would definitely start with a fresh, clean wipe/install (RUU if you can) to compare apples-to-apples.
Click to expand...
Click to collapse
I guess you're right, I need to backup all of my content anyway to send the phone to SAT, I'll check again later on
It looks to me like the game is still running in a lower resolution, based on that screenshot quality. Did you double check afterwards to see if its still disabled in the HTC Boost app? Sometimes things get re-enabled for me when they update.
As far as speed, I came from an S7 Edge and a Note 7. The HTC has way less judder and frame drops in day to day use, especially in Facebook. If yours is doing that I think there may be something wrong. I'd do a factory reset.
kwolf said:
It looks to me like the game is still running in a lower resolution, based on that screenshot quality. Did you double check afterwards to see if its still disabled in the HTC Boost app? Sometimes things get re-enabled for me when they update.
As far as speed, I came from an S7 Edge and a Note 7. The HTC has way less judder and frame drops in day to day use, especially in Facebook. If yours is doing that I think there may be something wrong. I'd do a factory reset.
Click to expand...
Click to collapse
Same here. I mainly use the oblong S7 as a paper weight now. I keep a Note 7 handy in case I run out of matches and need to start a fire.
kwolf said:
It looks to me like the game is still running in a lower resolution, based on that screenshot quality. Did you double check afterwards to see if its still disabled in the HTC Boost app? Sometimes things get re-enabled for me when they update.
As far as speed, I came from an S7 Edge and a Note 7. The HTC has way less judder and frame drops in day to day use, especially in Facebook. If yours is doing that I think there may be something wrong. I'd do a factory reset.
Click to expand...
Click to collapse
comstockload said:
Same here. I mainly use the oblong S7 as a paper weight now. I keep a Note 7 handy in case I run out of matches and need to start a fire.
Click to expand...
Click to collapse
I double and triple checked, the boost app has the check disabled for the game. I guess I'll backup my data, do a factory reset and see what happens after that, I'll be reporting back
well back again, surely took my sweet time long story short? Poor optimization for the phone. The S6 just had a fresh reinstall but after a month of use it began to present the same frame drops on facebook then the 10 had, it's just a facebook app thing. The graphics on the other side didn't improve even after a factory reset on the HTC 10 and the android N update. This is a sample recorded with the same app, same settings on both phones, make sure to load at 720p or 1080p in theater mode to spot the differences easier.
Galaxy S6:
HTC 10 Sample, same race
As you can see, the graphics on the HTC 10 are lower quality, more pixelaton, less details on the ground and surroundings, and so on. So considering hardware wise I don't think Adreno 530 is inferior to Mali T760MP8 I took my sweet time looking for an answer. Looks like the game it's extremely poorly optimized for the HTC 10, but there's a way to mod the game graphics on your own even without root. So after some research and modding the graphics on my own, this is the same race, with the same recording app, same settings, on the HTC 10:
As you can see differences are night and day in terms of texture quality and pixelation. It's just sad some games are that poorly optimized for the HTC 10
Edit: sorry for the bad driving skills, I was more focused on looking at the differences on the graphics than the race itself
Related
The one and only thing that keeps me on Sense now instead of just flashing CM or ICJ is the Sense Camera.
Is it just me or is the AOSP camera just ridiculously horrible? Or is it that I can't use it like it's intended to be used?
All of my pictures get this green tint with the flash on, they are grainy, too sharp.
In every scene (sun, night, light) there seems to be just one problem no matter what I set the settings too.
Also, what's with the interface?
{
"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 know it's all about personal preference, but I really can't stand that, choppy, type of "un-finished" look of it.
What is the whole grey background needed for? Why all that un-used space thrown away? Move the button completely right, make the buttons appear by swiping down or something, and you have a fullscreen camera that actually looks pretty minimal and gorgeous.
I love how simplistic and minimal AOSP can be when you customize it right, but is there a way to customize the stock camera app?
Anyone care to explain to me how to use the AOSP Camera or recommend me any alternative I could use on AOSP?
I really love the Sense Camera and I think it's pretty great, but unfortunately you can't use that on AOSP.
So, conclusion, does this stock AOSP Camera really suck this much as I think it does, or am I looking into it too much?
I have the same thoughts as you on this.
Sent from my HTC One X using xda premium
I saw your ICJ post directing to here Well, my view, I 'love' AOSP + AOKP (especially IceColdJelly) JB ROMs, the speed and look is how I like my OS/phone. Just the deal breaker for me, at moment anyway is the photos with flash mainly, there are improvements in photos taken in day but they aren't "miles ahead" like SENSE camera is with photos taken with flash (in dark).
Having a couple kids that heaps of friends and relatives want to see pics of since we moved not too long ago to be closer to our respective parents, friends and outer family members 'need pics' to see us + the kids, it's made a big difference that as you have said, night photos look 'unpolished' compared to standard cameras and SENSE camera on our phone.
I use like 3 or 4 camera apps when I was/am in Jellybean to get the best day pic/video depending on condition, since for me, I really need photos to be of 'best value' comparing look vs speed of photo (the funny moments when kids do something funny or 'milestone', just moments worth remembering that have a tiny window to catch). I use ProCapture for nice still shots, camera jb+ for photos needed in a quick timely succession of each other, LGcamera for the camcorder side of things, the 'lgcamcorder' for me is hands down best video making app on the phone I have come across.
Yet with SENSE, I only need the 'SENSE camera, at least the HQ mod that removes HTCs stupid artificial compression limits. I chose the phone from the specs which included the camera, why limit it software side, bleh, whole different topic though, HTC are idiots for what they do post sale IMO, probably lost me as a recurring customer, but as said, that's another tale/topic
I literally moved back to SENSE since warmer weather (I'm in Australia) is coming to us, we'll be out and about in the dark more with the kids rather than 'snuggled up' in cold months at night. I have nerve damage related pain so the cold really exacerbates this, so I don't head out 'that much' in cold nights since it means I need extra pain meds and/or the pain gets to me.
So the warmer months means I'm out lots, probably most nights, we used to eat out/party 7 days a week, my wife managed cafes + restaurant type places, so she was shift work, either finished work early (2-3PM, 6am start), or 9pm to midnight finishes, so most of the time we were never home (or her awake) for 'dinner', so most of our circle of friends are people who are best caught up with "out", so I wanted a phone that was part phone, part computer (ssh etc, been a unix admin over 20 years, can't work due to pain but still have home network and friends hosting places/shells that I ssh to a bit), part camera, the less 'things' I need to carry, the better. When we're like going out shopping, eating, catching up with friends more often than not, it makes sense (boom tish) that the less things I have, the less chance of losing something or scratching it from 'full pockets'.
TL;DR, I love JB ROMs for speed and look, but 'need' SENSE camera (and phone isn't CID compatible for JB SENSE just yet) for the night time photos, I took like 25 GB (maybe more?) last month of photos and videos, having kids means we want lots of pics that capture 'that moment', non SENSE and flash just doesn't cut it sadly enough, ,,|, to HTC for the things they do for 'their platform'
*edit*
Oh, it's not AOSP developers being 'crap' for the camera, it's HTC and their locked down 'SENSE stuff' that they can't (fully?) emulate, use for stuff like you mentioned, SENSE - flash is the biggest thing to mind, I haven't looked, but I do hope the JB SENSE ROMs camera(s) do tap into 'SENSE' for taking photos, or else I'll be "stuck" on ICS SENSE again during summer/warmer months until someone gets the non sense camera to be what I get from sense camera for my particular needs.
The Sense app is tweaked specifically to work with the HOX camera sensor. AOSP camera obviously isn't and probably will never be as the libs/binaries for that are probably closed source.
I agree that it also looks horrible, but that's just how it is and there are plenty of other camera apps on Google Play. You could always modify it to how you like and try pushing it upstream to CM10 and even AOSP.
Same thoughts as me. If it wasn't for the Sense camera I'd have jumped on AOSP as soon as I got my One X. I use the phone primarily for taking photos, so the camera is a big factor for me. I just can't stand the AOSP camera layout on screen.
I just got the Note 2 yesterday, upgraded from S3. I'm very happy with the phone, but the resolution is a disappointment.
From an article comparing the two:
The measurement of the display for the Galaxy S3 is a length of 136.6mm, width of 70.6mm, and a depth of 8.6mm. The screen size is measured in 4.8-inches with a pixel resolution of 1,280x720 with a 306 pixels per inch (ppi). The Galaxy Note 2 is measured with a longer length of 151.1mm, 80.5 width, and a depth of 9.4mm. The screen is measured at a larger 5.5 inches, but the same pixel resolution and a lower ppi of 267.
Click to expand...
Click to collapse
Here's what it feels like: I am used to using a 24" monitor, 1080p. I once got to use a 27" monitor that was the same resolution. I quickly became aware that it really wasn't beneficial. I couldn't put more apps on there, things were just bigger.
So, in the case of this phone, I still see the same amount of App Icons on the desktop (4 across, 5 down). I still see the same amount of twitter posts.
Most of you are going to point out the DPI change/fix. Well, I've been there and done that, and have been dissapointed with it. I ran it on the S2 forever. And there were apps that didn't quite work; the market was horrible. After a month I switched it off, cleared the market data, and realized I had many updates that wouldn't get put on with the right dpi. I've seen issues in the DPI thread.
Not much I can do about it, just wanted to put this out there. I think they could of given us better resolution on this phone. Maybe the Note 3.
woodsdog said:
I just got the Note 2 yesterday, upgraded from S3. I'm very happy with the phone, but the resolution is a disappointment.
From an article comparing the two:
Here's what it feels like: I am used to using a 24" monitor, 1080p. I once got to use a 27" monitor that was the same resolution. I quickly became aware that it really wasn't beneficial. I couldn't put more apps on there, things were just bigger.
So, in the case of this phone, I still see the same amount of App Icons on the desktop (4 across, 5 down). I still see the same amount of twitter posts.
Most of you are going to point out the DPI change/fix. Well, I've been there and done that, and have been dissapointed with it. I ran it on the S2 forever. And there were apps that didn't quite work; the market was horrible. After a month I switched it off, cleared the market data, and realized I had many updates that wouldn't get put on with the right dpi. I've seen issues in the DPI thread.
Not much I can do about it, just wanted to put this out there. I think they could of given us better resolution on this phone. Maybe the Note 3.
Click to expand...
Click to collapse
Do this: http://forum.xda-developers.com/showthread.php?t=1993530
you will fall in love all over again
woodsdog said:
Most of you are going to point out the DPI change/fix. Well, I've been there and done that, and have been dissapointed with it.
Click to expand...
Click to collapse
Cevaes_64 said:
Do this: http://forum.xda-developers.com/showthread.php?t=1993530
Click to expand...
Click to collapse
LOL.
Anyway, yes, I agree, the Note 2 should have had at least the same resolution as the Note 1 (not a downgrade!) and higher than the S3. But I'm guessing a pocket 1080 (or whatever) display would make the phone prohibitively expensive. Not to mention you risk people complaining that the text is too small - you can't please everybody. There needs to be a lot more effort put into handling text size on these devices so that various needs can be met. Everything on the Note 2 is ridiculously oversized for me still even with the font set to "Tiny".
I also miss having 5 icons across on the stock launcher from the Note 1, which is sort of a related issue.
But I still think the Note 2 is the best smartphone I've ever used, by a long shot.
that's the power of AMOLED. they always have poor resolution. this is the only real downfall to samsung devices. ):
coming from an S3 I have been happy with the screen, bump up the font size in chrome and on twitter and it's a joy to use, and videos do look amazing!
I'll take the slightly lower resolution with a non-pentile screen. Worth the tradeoff, IMO.
I think resolution is good to me. I plan on messing with dpi anyways though.
Sent from my SPH-L900 using xda premium
i think you are upset at the screen not being wider like the note 1 because the new DNA has 1080p and it still shows the same amount of info a 720p screen does... i think the problem isn't the ppi it seems like u just wanted the screen to do more then show the same info but bigger with a 1080 screen u could have put more info on the screen but how small would u have to make everything to do so is the real question.... but for me i love the note and the screens ppi because its just below the ppi a human eye can see and it still IMO the best phone out period.
Just found this exdialer if you lower dpi and dont like the small stock dialer
https://play.google.com/store/apps/...251bGwsMSwxLDEsImNvbS5tb2Rvb2h1dC5kaWFsZXIiXQ..
I am happy with the phone, let me be clear, it's fantastic.
However, it seems like there can be a sweet spot between icons/fonts too big (how I feel it is now) and too small. I am SURE there are technical limitations to this, but I would expect Samsung could figure it out. They are REALLY good at making screens with different resolutions!
At this point, nothing is changing, but let me throw out a few more things to help clarify my stance and my wish list. That's all this is at this time, a wish list.
On the S3, I was very happy with the icon & font size to screen size ratio (Is this what PPI is?). In my opinion, it is perfect. I think Samsung feels that way too, it's their flagship.
Here's how I think of it. The S3 is 70.6mm across. If each icon takes up let's say 15mm on the S3 (totally made up these numbers) it looks good. Thats 4 icons across plus space in-between them.
So, in my mind I would think that on the Note 2, they would take that same size 15mm icons, and spread it across the 80mm wide screen. That would look very good. Instead, they made the icons 18mm big, and it looks big and awkward.
As a consumer, I think this is a reasonable request. I REALLY hate to say this, but AppIe got this right on the Iphone 5. They added an extra row of icons, keeping the icons all the same size (yeah, they made a really awkward resolution for it, not defending that all. If I cared st all about the Iphone 5, I would have prefered wider & taller, not just taller). I feel they cheapened the experience of the Note 2 with the same resolution as the S3.
I will get used to it just putting my opinion out there. I have been such a Samsung Fanboy lately, but I still feel I need to point out where they could do better.
Cant please everyone. Having upgraded today from an og Evo4g, all I can say is wow.
Sent from my SPH-L900 using Tapatalk 2
There was a touch wiz launcher on here but dont know if it will work with new rom or not ....it was 5 x 6
I have it let me flash and see if it works but it was on here cant find thread now though ..If it works I can put on drop box for you
{
"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"
}
http://db.tt/9ufBpyN8
Sent from my SPH-L900 using Xparent Blue Tapatalk 2
I'm going to talk about a few things in this review:
Battery Life
The Sense UI
The Screen
BoomSound
Camera's
Round-up/overall impression
Battery Life
The battery life is actually pretty good for the 2400mAh it has, I can easily play games all day and it'll have 20-10% when I'm going to bed (wake up at 6:30am and go to bed at 10:00pm) So it's pretty good for me. Sometimes it'll even last up to 28 hours.
{
"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"
}
This image might not be totally representative because I didn't charge my phone last night and the night before, but you get the idea.
The Sense UI
I have never been using HTC before, but I like their Sense UI, it's very smooth and it just "works". I'm actually used to the Sony UI or even the Samsung UI on my Galaxy Tab 10.1 but I like HTC's UI a lot more than both Sony's and Samsung's. The Blinkfeed was something I was afraid of being too "present" but I've actually just got used to it and now I actually use it, it's not some trashy gimmick you wont use and hogs RAM, I'm really impressed.
The Screen
HTC Has put a 5.2 inch, Full HD 1080p screen in this device, and it's lovely. It's bright, I'm watching all kinds of TV shows on them (while relaxing the hottub ofcourse, because it's waterproof!) The looking angles are good aswell, friends can easily watch a youtube video with me without having to struggle. I also have no trouble reading content from my screen in the bright sun.
BoomSound Speakers
The BoomSound Speakers and waterproofing were what originally pushed me over the edge to get it, and it delivered, I'm loving these nice clear tunes they deliver, I'm preferring them over my regular laptop's audio (HP Elitebook with SRS Audio Pro). The bass meight be a bit underdelivering (when outside) but that's not something I really am worried about.
Camera's
The Camera's are lovely, and especially the camera app. They even got Instagram to somehow integrate the frontfacing flash in their app, so if you take a photo from within instagram you can use your flash on both sides! It really makes your photo's better. I'm a bit dissapointed in the night performance of the back camera, but when you turn on HDR and adjust white balance it's all good.
Here's a sample photo I took outside a few days ago:
Round-up/overall impression
So I´ve been using this device since release date because I´ve pre-orderd it, I have the blue non-AT&T version and it rocks, I'm using it in water daily and when it gets dirty, I just put it under the tap and dry it off. Overall, I'm quite impressed by how quick it is, It's Snapdragon 801 is lovely and even on playing heavy games it delivers what you expect from a high-end device. I'm not someone who used to take selfie's but somehow, I started taking selfie's more often because of the lovely camera I got now (well, I come from a 0.3 mp frontcam so that's not really hard to beat). Compared to a S5 I would take this over it any day. Feel free to ask me any questions you have, I'll answer them honestly.
Could you post some more pictures about battery usage, SoT, maybe compare it with some other phone and etc.? The battery life is only thing I am afraid off, thinking about Desire Eye or Sony X Z2, but Sony let me down with XSp, so maybe will try HTC if battery life is ok. Thanks
NestorC said:
Could you post some more pictures about battery usage, SoT, maybe compare it with some other phone and etc.? The battery life is only thing I am afraid off, thinking about Desire Eye or Sony X Z2, but Sony let me down with XSp, so maybe will try HTC if battery life is ok. Thanks
Click to expand...
Click to collapse
I'm not really sure what pic's to do, but I'll post one after tomorrow. I don't really have another phone, my previous ones died.
Just take pic of your battery usage when in goes around 1-5%, how many hours it run, with how many hours screen on time and that with info about sync, brightness and etc.
NestorC said:
Just take pic of your battery usage when in goes around 1-5%, how many hours it run, with how many hours screen on time and that with info about sync, brightness and etc.
Click to expand...
Click to collapse
http://imgur.com/ZlRzc3w,N7xjNdN,wwDUvv8,2mJSHFi#3 Album of some screens, I can't get it down to 5% in a day as it goes up to 28 hours with normal usage (spotify social media a few games here and there). I'm sorry It's at 37% right now.
Thank you, I just need screen on time, if u can get a pic of that, because i guess screen drains most of the battery, i think its on the next page, near battery history all time, usage of screen? Or u can see it if u have Batterystatus app or something like that
NestorC said:
Thank you, I just need screen on time, if u can get a pic of that, because i guess screen drains most of the battery, i think its on the next page, near battery history all time, usage of screen? Or u can see it if u have Batterystatus app or something like that
Click to expand...
Click to collapse
I couldn't find it anywhere, but there are 4 pics in this album, the last one should contain screen on time
sidle said:
I couldn't find it anywhere, but there are 4 pics in this album, the last one should contain screen on time
Click to expand...
Click to collapse
Yes but dont have in hours, cant see if there is 3 or 4h of SoT or how much, but thanks anyway
are you on an international desire eye? care to share a nand backup?
btw, htc's battery software wont display SOT for some reason
robstunner said:
are you on an international desire eye? care to share a nand backup?
btw, htc's battery software wont display SOT for some reason
Click to expand...
Click to collapse
Don't have anything custom on it yet, trying to keep this one, well... not broken. And yes, I have a international blue one.
Thanks for the reply
Sorry for my bad english.
I have noticed in some videos that opening heavy applications , the HTC 10 is very very slow .
link:
https://youtu.be/FB5W2DYrl5o?t=5m54s
https://www.youtube.com/watch?v=x-voDhSxF4U
More than 40 seconds to open Real Racing 3 , it is not normal for me.
Ok , Htc 10 does not use UFS memory , but even P9 (20 seconds ) or a medium- range as Meizu M3 Note ( less than 30 seconds ) . You think it is just a issues of memory , or is a software problem that over time will improve?
Another review confirms how slow it is compared to the S7 Edge. It is worrying because the difference in loading seems huge. I'm wondering as well if its down to slow storage performance.
incredible, I have no words. the gap is too large to just be a memory problem.
https://www.youtube.com/watch?v=l97ZCFAqqjM
It seems to suffer from throttling
Unless the phone has an SD set to adoptable storage set.....
Sent from my SM-T810 using Tapatalk
DjBorna92 said:
incredible, I have no words. the gap is too large to just be a memory problem.
https://www.youtube.com/watch?v=l97ZCFAqqjM
It seems to suffer from throttling
Click to expand...
Click to collapse
Looking at the video...no it doesn't. Quite consistent actually.
Also could people for the love of god stop throwing the throttle word around without actually understading what is happening here..
Of course the first Antutu benchmark number was really high because the phones started off cool as a cucumber.
You know, that unibody is a huge freaking heatsink. It's able to absorb a lot of heat and gives the 10 the competetive edge in this kind of a test.
S7 has over 5% less mass vs 10 and a glass back as well. Inside you'll find a teeny tiny heatpipe which is supposed to spread the heat more evenly but there's no visible thermal interface material to actually help that process of pulling the heat away from the SoC to the heat pipe and then spread that heat to the mid frame.
Read: the S7 "throttles" right out of the gate.
Thermal interface material is used to have a better contact between two surfaces, otherwise there will be air trapped between those surfaces and air is not good at transferring heat.Same goes with the G5, at least it has almost the same mass as the 10 but it's got that silly primer paint and whatnot covering it. LG, you're a genius, of course that's gonna help the heat get away :silly:
And no TIM goop here either, just some sort of thin heatspreader on top of the SoC/UFS NAND and some thermal tape which would then, hopefully, make contact with the metal frame. Problem here is that there's not a lot metal for the heat to transfer to. Also thermal tape < proper paste/goop or thermal pads.
Unfortunately we don't have teardown of the HTC 10 yet, I'm interested in seeing what kind of thermal solution they've got there.
If you take a look at the standard or average deviation of those results, not including test #1 which is the warm up lap, the deviation of HTC 10 scores is just as good or just as bad as the Galaxy S7. G5 being the worst of the bunch and P9 being slooow and consistent at that, doesn't surprise me when looking at the teardown of it..
{
"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"
}
Or the geekbench numbers, this time we don't need to exclude the #1 test because the warm up was already done with Antutu.
No problem with single core, almost as good as the S7. This comes down to kernel and governor differences.
I'm not sure what happened here with the multi core numbers with the 10, if I'd got that kind of results, I would've restarted the whole test all over again. I wouldn't accept that kind of a variation, #1-2 being close to each other and then dropping by over 6% with #3-4 being close to each other again.
Just by having some random background process do "stuff" could have an effect like that, single core didn't have that where as with multicore test all of the cores are used which of course means that even if one of those is doing something else...
The P9 for example does show some signs of performance degradation here, first one being high and the following three drop off and are close to each other.
The G5 then shows a random drop as well at #3, just 2% but still a little odd.
But nevertheless. These kinds of tests are ridiculously stupid.
How about you take a look at proper testing over here.
http://anandtech.com/show/10252/htc-10-battery-storage-results
If you don't know what to look at, I'll help you.
This, is throttling. You just simply cannot have a device as small as a phone keep the GPU performance up for very long.
The Adreno 530 is ridiculously powerful and with 256 ALUS's and 600+ Mhz clockspeed, it's going to guzzle a lot of power and in the process create a lot of heat.
Apple on the other hand is obsessed with the consistency and it shows. PowerVR's architecture is just so much more efficient along with Apple's own optimizations.
But anyway, S7 and 10 show the same amount of performance degradation.
And here's FPS/vs time.
The 10 of course drops off faster as HTC doesn't want to burn your fingers. They have a completely different body on the device which means different skin temp restrictions.
But in the long run, S7 is all over the place while the 10 gives you a more consistent performance.
I have no clue why on earth Samsung would prefer that kind of oscillating performance. What you wanna have is strict temp limits with high enough temperature hysteresis so it doesn't start jumping up and down like that.
As an example would you rather have a GPU in your PC which fan would sound like WEE-UUU-WEE-UUU jumping all over the place like a kid on a trampoline or a gradual and consistent hum? Not the same thing of course, closest analogy I could think off, but that kind of fan behaviour of course affects modern GPU's with their automatic "overclocking" or rather their clockspeed through the TDP and temperature limits.
It's not good for the longevity of CPU/GPU dies and other semiconductors either if there's sudden temperature jumps all the time, it's known as thermal stress.
Also, what a lovely dip on the S7 to the high 20's fps as it ran into the temperature limit road block.
What happened was that it tried to overachieve by keeping the clocks high longer > oops I reached the thermal limit, now I have to throttle waay down to save myself. Then after that it jumps up and down...
Would've been nice to see the battery+CPU/GPU temps in those graphs!
And I would love to get those T-Rex numbers in a spreadsheet and have a closer look at them.
Most of these youtubers are zombie buyers with 0% knowing about software etc.. When htc starts shipping 10's, go in local stores and try device for yourself, i may sound like a htcwhore, but i'm right on this.
Just don't trust too much this stupid reviews(even before official shipping...).
@lagittaja Geekbench is constant, but steadily low. G5 with the same cpu has the highest scores (500 in single core and 1800 in multi). I want to wait for the commercialization of the device before drawing conclusions. I think maybe it was castrated to save battery and not giving a bad impression as G5.
Hello!
So, whatever video I try to run via Youtube app, the maximum quality is always 480p. Is this a ROM/kernel/app issue or is our device limited by hardware?
480p is often good enough, but recently I've been looking into 360° videos and the resolution just doesn't cut it.
I've tried the modded .apk here on XDA and some alternatives, but none of them seem to allow watching of 360° videos.
Is there an easy fix (I've seen people mention editing of build.prop)? Or is there a decent alternative?
xWhiskey said:
Hello!
So, whatever video I try to run via Youtube app, the maximum quality is always 480p. Is this a ROM/kernel/app issue or is our device limited by hardware?
480p is often good enough, but recently I've been looking into 360° videos and the resolution just doesn't cut it.
I've tried the modded .apk here on XDA and some alternatives, but none of them seem to allow watching of 360° videos.
Is there an easy fix (I've seen people mention editing of build.prop)? Or is there a decent alternative?
Click to expand...
Click to collapse
Yeah the problem is with the youtube app itself on boot it detects your phones resolution (in this case 560p by default) and rounds it down to nearest youtube res (in this case 480p). To get around this first make sure youtube is fully closed then install an app called screen shift off the playstore. Use the resolution you want (1080p 30 fps max) and then youtube should detect that when you open it and make that your limit
---------- Post added at 11:30 PM ---------- Previous post was at 11:28 PM ----------
Oh Unrelated we both have the same phone history (xperia x8 --> xperia go --> gs4 mini) #sorelatable
Xmaster24 said:
Yeah the problem is with the youtube app itself on boot it detects your phones resolution (in this case 560p by default) and rounds it down to nearest youtube res (in this case 480p). To get around this first make sure youtube is fully closed then install an app called screen shift off the playstore. Use the resolution you want (1080p 30 fps max) and then youtube should detect that when you open it and make that your limit
---------- Post added at 11:30 PM ---------- Previous post was at 11:28 PM ----------
Oh Unrelated we both have the same phone history (xperia x8 --> xperia go --> gs4 mini) #sorelatable
Click to expand...
Click to collapse
It worked, thanks! But this really goes to show a layer of bad programming - I mean if the phone is capable, is there some valid reasoning behind limiting the resolution?
Ah, yes... the old X8 Can't say I miss it much now. Gotta hand it to it though - survived 5 years with no damage whatsoever save for the battery change. True survivor
xWhiskey said:
It worked, thanks! But this really goes to show a layer of bad programming - I mean if the phone is capable, is there some valid reasoning behind limiting the resolution?
Ah, yes... the old X8 Can't say I miss it much now. Gotta hand it to it though - survived 5 years with no damage whatsoever save for the battery change. True survivor
Click to expand...
Click to collapse
yeah my X8 was perfectly fine just felt alot like a brick thought especially when I got my xperia go at only 10m thickness compared to the 15 on the x8 great first android phone thought.
Yeah the main reason is that many phone are "capable" of higher resolutions but that would be 1 a waste of battery and resources and 2 not all phones can smoothly do those resolutions. If they unlocked the resolutions to whatever the phone was capable rather than its actual resolution loads of people would be complaining about **** battery life and lag of hell. They just took the easy route and avoided that rather than testing each phone independently through a benchmark or such. Dunno why they round down the resolution it would make more sense to round up so the full screenspace is used but I guess its kind of samsungs fault for using such a wonky resolution on this phone
Xmaster24 said:
yeah my X8 was perfectly fine just felt alot like a brick thought especially when I got my xperia go at only 10m thickness compared to the 15 on the x8 great first android phone thought.
Yeah the main reason is that many phone are "capable" of higher resolutions but that would be 1 a waste of battery and resources and 2 not all phones can smoothly do those resolutions. If they unlocked the resolutions to whatever the phone was capable rather than its actual resolution loads of people would be complaining about **** battery life and lag of hell. They just took the easy route and avoided that rather than testing each phone independently through a benchmark or such. Dunno why they round down the resolution it would make more sense to round up so the full screenspace is used but I guess its kind of samsungs fault for using such a wonky resolution on this phone
Click to expand...
Click to collapse
Eh, at least an option to test it would be nice, together with a warning that comes with it. But this trick does work - I've found that if you first stretch the resolution, then run the Youtube app, and put the default resolution back, Youtube still remembers it up to 1080p until you do a reboot. The videos look really great now but you do have a point with the battery :good:
Thanks for the help!
xWhiskey said:
Eh, at least an option to test it would be nice, together with a warning that comes with it. But this trick does work - I've found that if you first stretch the resolution, then run the Youtube app, and put the default resolution back, Youtube still remembers it up to 1080p until you do a reboot. The videos look really great now but you do have a point with the battery :good:
Thanks for the help!
Click to expand...
Click to collapse
Yeah it only checks resolution on app boot up so as long as it stays in the background the resolution should stick. Yeah an option would be nice but effort. 720p and 1080p should look about the same apart from the Antialiasing factor so less jagged edges I guess?!
Download App Settings module from xposed installer
and do following setting to Youtube App
DPI : 180
Font Scale : 85
Screen DP 800x1280
it will allow 720p playback
this setting will do changes in Youtube app only
{
"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"
}