Should be the same as the S7 prior to them implementing it.
adb shell wm density XXX && adb reboot
I'll give 600 a try and see how it goes.
Did you give it a try? I do not like the stock dpi on the 10 and one reason why I have not bought it.
Should be the same as the S7 prior to them implementing it.
adb shell wm density XXX && adb reboot
I'll give 600 a try and see how it goes.
Did you give it a try? I do not like the stock dpi on the 10 and one reason why I have not bought it.
If I had both phones in front of me, and had to pay for one or the other, I would go with the HTC. The size, processor, etc.I did try it. I couldn't really find a resolution that I liked. There was text cut off in the dialer and other places no matter what I tried. And it basically broke the stock keyboard (but Google Keyboard worked fine). Breaks Android Pay as well. So scaling for sure isn't implemented like in the S7.
But Android N should fix all this (it has system-wide scaling built-in for the previews at least). HTC will need to update their stuff to be compatible. And HTC is promising Android N very quickly for the 10.
Speaking of which, I am going back and forth between this and the Nexus daily. Really tough call. Love the size, feel and the build of the 10. 6P is very awkward at times due to its size. But overall, they are about the same for quality of camera, screen, battery, etc. HTC 10 did seem much smoother, that was until I installed Android N on the Nexus. 6P feel like a new phone since the upgrade..... so fast. And the tall size really makes good use of the multi-windows features in N. Plus being on Project Fi, the Nexus will probably see the first implementations of Allo and Duo, and I am curious to see where those go.
So it will be a tough call. I am not going to keep both with a HTC Nexus down the road. I wish I could. The HTC 10 really is a joy to use. But I just really can't justify the expense of keeping both phones when they are so similar.
If I had both phones in front of me, and had to pay for one or the other, I would go with the HTC. The size, processor, etc.
BUT....if I hadn't been forced to part with my beloved Nexus 6p, I wouldn't be a debate. Keeping the 6p would be that cheaper option (I assume), and we are both waiting for the HTC Nexus.
Now, here is an interesting idea. The HTC 10 might be very similar to the HTC Nexus. It might have a different screen size, as well as other difference....but it might be closer to the HTC 10 then it isn't. If HTC really does role out fast updates (I expect updates for the unlocked version to follow close behind the nexus line, especially with them making the next nexus), and the phones are similar enough, along with HTC's uh oh protection....will it be worth it to move from the 10 to the HTC Nexus? Could be an interesting predicament.
I'm loving the 10. Zero regrets.
Great observations......I would love love to have an HTC 10 like Nexus phone but with a 5.5 display. I just hope they keep the 10 features like camera and battery life. I think we will lose boom sound though.If I had both phones in front of me, and had to pay for one or the other, I would go with the HTC. The size, processor, etc.
BUT....if I hadn't been forced to part with my beloved Nexus 6p, I wouldn't be a debate. Keeping the 6p would be that cheaper option (I assume), and we are both waiting for the HTC Nexus.
Now, here is an interesting idea. The HTC 10 might be very similar to the HTC Nexus. It might have a different screen size, as well as other difference....but it might be closer to the HTC 10 then it isn't. If HTC really does role out fast updates (I expect updates for the unlocked version to follow close behind the nexus line, especially with them making the next nexus), and the phones are similar enough, along with HTC's uh oh protection....will it be worth it to move from the 10 to the HTC Nexus? Could be an interesting predicament.
I'm loving the 10. Zero regrets.
As a side note, for you HTC 10 owners:
My HTC 10 hates the Pixel C charger http://www.androidcentral.com/my-htc-10-hates-pixel-c-charger
So yeah, be careful. People seem to want to blame HTC, which I believe HTC deserves some blame; but so does Qualcomm. USB C is still new enough to have compatibility problems, and proprietary technologies like quick charge appear to have some conflicting protocols or lingering incompatiblies.
I think this will get worse before it gets better. I imagine the first Samsung phone with USB C, possibly the note 6, will use a its own fast charge technology that may conflict.
So essentially until it's all resolved, stick with OEM made chargers, or reputable quick charge brands (and monitor it the first time). I imagine most quick charge chargers will be fine, since the voltage is low enough (amp can be oscillated on demand, voltage is constant). But USB C chargers, such as a MacBook or pixel C charge may be too powerful.
I'm not fully sure what the main problem is. I know a pixel C charge can charge a nexus 6p fine...but it almost fried a HTC 10. I think we have a conflict between the quick charge technology, and the large amount of power some USB C chargers can output.
So just be aware. I have used a quick charge 2.0 wall and car charge from Amazon, as well as a Samsung fast charge plug with the HTC ten without a problem.
Wow T-Mobile is not supporting the HTC 10 in stores very well.
I live in the Chicago western burbs, and I went to the two big local Corporate T-Mobiles stores in Oak Brook, and Glen Ellyn areas, which are high end big stores always packed with people, and typically have the latest phones on display. Well neither store had the 10 on display, and both basically said they don't promote HTC anymore, and that they will never stock or carry the new HTC 10, but can be ordered on T-Mobile's website. But they were very eager to try and sell me a new LG G5
I called a few other local stores, the reps asked which phone ? A new HTC phone ? No we don't have anything like that.
I think more like butt hurt that VZW got the 10 first.....Well probably butt hurt like AT&T that HTC is providing an easy way to get it unlocked, unbranded and unbloated directly from HTC at the same price. Pretty awesome to hear actually.
I called 9 of the nearest T-Mobile stores by me in the Chicago suburbs, not one of them has the HTC 10 in stock, and they all said you could order it online, but no display in stores, and will not stocking the phone.
People don't buy computers and get their machines locked down from their isp eh?
No, but almost worse, people rent cable boxes and modems/routers from ISPs. And probably pay them 10 times over what they are worth during their time renting. And they are locked down. And they hardly ever get upgraded without a fight.
I'm very curious why best buy hasn't taken advantage of this and sell the unlocked unbranded versions and offer a monthly payment option, like the carrier's. They can also offer geek squad protection or include it in the monthly payments like Apple does with Apple care.Dang, as much as I love to hate carriers it is very hard to do well in the us without them because people are so conditioned to buying via carrier
Samsung holds the true power and could probably change the game and make it par for the course for phone software updates to get more efficient and kick the carrier out
T-Mobile is good guy carrier too and has no problem with unlocked devices
Makes my blood boil man!
People don't buy computers and get their machines locked down from their isp eh?
Looks like I have to get a replacement from HTC. Out of no where, the upper left side of the screen stopped registering touch. A factory reset has not helped.
*Correction: It is most of the top of the screen. It can register swipes fine, but not touches. I can't search in the play store, or access the menu in most apps. Unfortunate.....
Well I returned my HTC Friday and already miss it. It was a good phone. I think I'm gonna just go with the Nexus this fall. I imagine it to be a plastic version of the HTC 10 with a SOC bump.
I'm a case man so that doesn't bother me. But will miss the build of the HTC. I liked the phone just couldn't stick around knowing it didn't perform the way I wanted to in low light and didn't have the touch to expose feature I wanted.