Since our phone has as many subpixels as the 720p display on the Galaxy Nexus, theoretically wouldn't it be possible to make android do same resolution for our phones by using the same amount of sub pixel to pixel ratio?
I Introduce you to this thread.
http://forum.xda-developers.com/showthread.php?t=1363793
Let me introduce you to this post in the same thread...
http://forum.xda-developers.com/showpost.php?p=19726602&postcount=8
This is what I'm asking about. The app idea is great but thats not really changing resolution, its just making everything smaller.
The hardware driver for the screen is not designed to handle less subpixels at a time, and is hardwared for 12 per pixel. Even if we could change that we would have to create the drivers from scratch to handle that. None of the source is available on our drivers. Its just too much to ask.
Thanks for the informative answer
Related
65536 color is a well-known limitation of WinMo.But display hardware's capable more than that.
If the Project Android can break the limitation that would be awesome!
Is it functioning this way now or not yet?
Is it EVEN possible?
Or its based on WinMo,so its IMPOSSIBLE?
Forgive me asking without searching first,cuz i dont think its a silly quz.
BTW.
THANKS ALL DEVS,THIS IS THE BEST THING EVER ON MY PHONE!!!
I don't see why it'd be that much better if it could. Don't think it's necessary either; not like you're photoshopping on Android or anything where you NEED to see EVERY hue of every color.
thats true.
but isnt it good to know ur TP2 has more ability?
BTW. its nice to have sound
I believe on most Windows Mobile devices, including the Rhodium, the display hardware itself is also limited to 65536 colors. Think about it, a manufacturer wouldn't want to spend extra money on a display supporting 24-bit color when the operating system is limited to only 16-bits anyway.
I'm pretty sure that running android on the rhodium ignores the color limitations of windows mobile. Really, the color limitations on winmo are bad. You can see the colors change instead of them blending into one another when you look at pictures. The display on the TP2 does support more colors because they don't make LCD screens 262k- limiting from 1.6m to 262k doesn't save cost- it just makes things instantly obsolete and HTC isn't dumb
Hello there dear Desire Z community!
I am thinking of upgrading my htc desire for a deisre z but i am torn between the DZ and galaxy S..So i went ahead and decided to ask a list of factors before i make my purchase (because i am obviously leaning towards the Z)..
1) and most probably most important.How is the battery life (e.g compared to a desire-n1) ?
2)is the screen viewable under direct sunlight? (desire sucked at this)
3)how is it in terms of GPU graphics compared to these devices? : iphone4 ,galaxy s,desire hd?
4)Does it suffer from the same multitouch bug the deisre/n1 do?And if not it can use true multitouch or dual touch?
5)How is the dev support around here? i know CM is also supporting a rom for DZ/G2 ,but are there are others devs doing nice work on the device?
6)Is there anything u miss from this device ?
36 views and no reply?i only asked because these questions can be answered by only someone that has lived with the phone for a while..
It does have proper multi-touch, but I can't answer your other questions, since this is my first Android phone. And I love it
steviewevie said:
It does have proper multi-touch, but I can't answer your other questions, since this is my first Android phone. And I love it
Click to expand...
Click to collapse
appreciate your feedback sir..enjoy your new handheld!
1) Battery life is amazing, much better than the N1. I can stretch around 18 hours with HEAVY use (mostly texting non-stop )
2) Under direct sunlight the phone does pretty well, just have to crank up the brightness. Remember, this is no S-AMOLED, but still does pretty well.
3) Best GPU I've had so far, Comes pretty close to the Galaxy S.
4) No multi touch problems Tracks 4 fingers independently
5) We have awesome dev support Most notably Enom and Cyanogen himself and the dev support will only increase over time...
6) Coming from a N1, I can say I don't miss anything. The G2 is a proper successor to the N1, better then that crap Samsung Nexus S garbage.
Note: GALAXY S IS COMPLETE GARBAGE. Feels like a cheap plastic toy
I forgot who it was, and what thread. But there is somebody on here that switched from a Galaxy S to the Vision, and he said the Vision was a much better phone. Do some reading on the CPU lag and GPS issues on the Galaxy S to help you decide. Also, being an HTC device, and also since it has the hardware keyboard, the Vision will likely remain a favorite of developers for some time.
In my opinion, the Vision is only the SECOND android phone worth owning. The first being the Dream. N1 wasn't good -- touch screen keyboards are ok for punching in something very SHORT, like a market search term, but anything longer and you're bashing your head against a wall. Faster or not, a lack of a keyboard is DEBILITATING. What can you do with fast if you can't get your data into it. All other keyboard androids suffered from retard issues, like incorrect button alignment and/or being motorola.
Also note that the Vision is the direct successor of the Dream (not the N1). I.e., a vision is kind of like a dream, but more powerful. It has basically the same characteristics of the Dream, but more and faster. The naming is also designed to imply a succession.... Its "vision" as in having a vision of the future, rather than "vision" as in seeing something with your eyes.
Thats great!thanks for the feedback and extra info all of u guys...i guess it turns out the only thing i miss is the better screen part..I think i will enjoy the hw kb!
Im curious, the imagesense found on the One X supossedly makes the shutter speed faster, improves the quality on the pictures and videos taken with the phone but they use propietary drivers, so they're not used on AOSP roms like CM10 or AOKP, is the chip never going to be usable on these roms?
Yeah. I like to know that too
Sent from my HTC One X using xda premium
Interesting... I haven't heard about that one. How much difference does it make just out of interest?
chrisoverson said:
Interesting... I haven't heard about that one. How much difference does it make just out of interest?
Click to expand...
Click to collapse
Difficult to say, since the images and videos are massively over compressed.
Pretty sure that's the Sense camera app and not the chip, though.
If you mean the sense camera then no..it is possible..but too difficult to get it working on aosp based roms..
hello00 said:
If you mean the sense camera then no..it is possible..but too difficult to get it working on aosp based roms..
Click to expand...
Click to collapse
No, no im not refering to sense camera, supossedly the one series phone have a dedicated chip for processing images and videos recording check this:
"HTC was proud to announce that not only are the phones awesome, built extremely well, trimmed down and run fast with HTC Sense, but they’ve also developed a new technology called ImageSense. HTC has actually added a separate processing core for the camera alone. So a dual-core phone will actually have three cores.
The ImageSense chip will not only offload the duties from the regular processor to keep the phone and operating system fast and stable. It will leave the camera completely uninterrupted to take quality, impressive photos. This also allows super-fast shooting possible with a 0.7-second shot time and a 0.2-second autofocus."
http://androidcommunity.com/htc-one-x-photos-show-off-new-imagesense-camera-technology-20120302/
Chad_Petree said:
No, no im not refering to sense camera, supossedly the one series phone have a dedicated chip for processing images and videos recording check this:
"HTC was proud to announce that not only are the phones awesome, built extremely well, trimmed down and run fast with HTC Sense, but they’ve also developed a new technology called ImageSense. HTC has actually added a separate processing core for the camera alone. So a dual-core phone will actually have three cores.
The ImageSense chip will not only offload the duties from the regular processor to keep the phone and operating system fast and stable. It will leave the camera completely uninterrupted to take quality, impressive photos. This also allows super-fast shooting possible with a 0.7-second shot time and a 0.2-second autofocus."
http://androidcommunity.com/htc-one-x-photos-show-off-new-imagesense-camera-technology-20120302/
Click to expand...
Click to collapse
That sounds a bit misguided. The SoC has some space devoted to image processing, it's not another general processing core!
BenPope said:
That sounds a bit misguided. The SoC has some space devoted to image processing, it's not another general processing core!
Click to expand...
Click to collapse
Its not another general processing core but its a dedicated discrete chip for the camera so not part of the SOC, could be image processing parts there as well ofc.
Granted this is about the MSM8960 One X but from what I've read the camera stuff is the same for all One S/X models and in part also for One V.
Source: http://www.anandtech.com/show/5779/htc-one-x-for-att-review/5
"HTC’s ImageChip is responsible for most of the things that would traditionally be done on the SoC ISP. 3A (Autofocus, Auto white balance, and Autoexposure), lens correction (geometric and chromatic correction), noise reduction, best shot selection, continuous auto focus, controlling gains on the CMOS sensor, LED flash level decision, region of interest identification (augmented with face detection) and so on. This is all stuff you can verify yourself by taking apart some of the ISP related files - curiously enough internally ImageChip is actually referred to as “rawchip.” This is also the hardware responsible for enabling HTC’s extremely fast image continuous capture and frame grabbing during video capture (HTC Video Pic). It’s somewhat analogous to what Google and TI did with the OMAP4460 on the Galaxy Nexus, except discrete and with a much more ambitious focus."
More here in the One S review: http://www.anandtech.com/Show/Index...ug=htc-one-s-review-international-and-tmobile
Discrete? That surprises me, and I stand corrected.
Guess HTC aren't ambitious enough to expect sales of these phones to be high enough to work it in as a part of the SoC. That's at least a quid to the cost of the phone right there!
BenPope said:
Discrete? That surprises me, and I stand corrected.
Guess HTC aren't ambitious enough to expect sales of these phones to be high enough to work it in as a part of the SoC. That's at least a quid to the cost of the phone right there!
Click to expand...
Click to collapse
Guess it enables HTC to have a consistently nice camera experience for users across their phones while picking whatever SOC is best/cheapest/comes with the right air interface for a region or carrier. Lol I feel like a PR parrot after typing that... Anyways IF a dev ever gets it working on AOSP for any device it might be easier to port it to other devices. I hear its not impossible, just a massive undertaking and will bring a lot of Sense framework which is not useful for much besides the camera, or maybe documentation will be released sometime. Now I'm just a hardware nerd with zero programming experience so take that with a grain of salt, I'd love to be proven wrong though
I can imagine the camera apk needing sense, but not the chip driver. Reverse engineering that driver and pulling in its dependencies could be a pain, as well of course as creating a new camera app.
If only there were more hours in the day...
The Pixel XL seems to have almost identical hardware: a 1440p screen, a SD 821 (which is just a 820, isnt it?), 4GB Ram...
So why is the 10 not "Daydream" ready? Are there sensors lacking?
Elthy said:
The Pixel XL seems to have almost identical hardware: a 1440p screen, a SD 820, 4GB Ram...
So why is the 10 not "Daydream" ready? Are there sensors lacking?
Click to expand...
Click to collapse
I think it's related to AMOLED and refresh rate or something. I think technically the 10 can perform more less fine for daydream but it wouldn't be as immersive as Google would like associated with it.
https://www.google.com/amp/amp.androidcentral.com/google-reveals-hardware-requirements-daydream-vr
So maybe it's the lack of nougat or because not every hardware revision can handle constant 60 fps. Tianama (or something) locks in at like 58/59 fps.
Is it still compatible? If i dont care for 59fps instead of 60?
Or would the software refuse to run?
I don't have the intimate knowledge of some behind the scene, but my understanding after the stuff launched was that it wasn't a special sensor issue, that was one of the advantages of the google VR stuff over the Samsung (or disadvantages, if you're a Samsung person with all the accessories).
Have we received confirmation that after the nougat update, the 10 will be incompatible? It's quite possible it will be for other reasons, just sharing what my understanding was after looking into some of the Pixel and Daydream things, kind of spitballing/bench racing.
Display response time mainly. OLED response time is practically non-existant and since we don't have an OLED display.. Well there you go.
Elthy said:
The Pixel XL seems to have almost identical hardware: a 1440p screen, a SD 821 (which is just a 820, isnt it?), 4GB Ram...
So why is the 10 not "Daydream" ready? Are there sensors lacking?
Click to expand...
Click to collapse
Let's wait for N and find out. If htc don't include it then it may hit the battery which will mean most who adopt it won't keep it.
The amoled screen means that the black is 0% screen usage or very close to, the htc doesn't have that black due to screen type so might be why.
Would be nice to see a proof of concept but if it hits the battery it won't stay. My friends LG has it and it's quite cool for peeking. Guess we'll find out. Did cm have it??
Just an FYI. I've been using my HTC 10 running an aosp slim build with a daydream vr for a couple of weeks. It does work. No lag but it gets really hot. I think all present phones do, its not an issue with the HTC 10.
Followed these directions. A simple edit to and XML file does the trick.
https://www.reddit.com/r/Android/comments/5hno6u/got_daydream_to_work_on_my_5x_might_work_on_other
Sent from my HTC 10 using XDA-Developers Legacy app
So how's your 11T?
I come from only HTC phones and the 1st difference i noticed is the screen quality in PPI's.
My prev HTC U11 from 5yrs ago is having more ppi's than a 2022 model making look inferior in screen quality and color management.
I understand that for this processor theres not much going on.
Updated to A12 is great all running smooth and sharp.
Anyways its a great phone, found HTC home and instaled as a tribute...
Would be cool to see some dev on this device.
Share your thoughts!
orb3000 said:
So how's your 11T?
I come from only HTC phones and the 1st difference i noticed is the screen quality in PPI's.
My prev HTC U11 from 5yrs ago is having more ppi's than a 2022 model making look inferior in screen quality and color management.
I understand that for this processor theres not much going on.
Updated to A12 is great all running smooth and sharp.
Anyways its a great phone, found HTC home and instaled as a tribute...
Would be cool to see some dev on this device.
Share your thoughts!
Click to expand...
Click to collapse
Devs can't develop for this device cuz mediatek is closed source
Sent from Xiaomi 11T using gboard
Phone is awesome performance wise but this feature called miravision causes shadow detail lose, and detail lose in black areas, adds saturation. It does a mandatory extra post processing on the creator's video. It can't be turned off, that's why I'm considering switching to a new phone. Because even my old LCD phone was better.
Disable hardware overlays, blocks Miravision. But in this way, the charge runs out noticeably faster.
An option to turn this off definitely has to be added. It's unbelievable that they added it by force.
I got screen burn in about a month ago after 14.0.2 update I think it's a good phone, but the mics have too much echo at school. My old S10 didn't do that