Database Develop

mail htc driver :/

Good Evening,?
Thank you for your email regarding the video and rendering issues reported with HTC devices that use the Qualcomm MSM7xxx chipsets.?
HTC have released an official statement regarding this issue.?-------------------------
Public Reactive Statement From HTC - Jan. 22, 2008
In response to recent customer complaints about poor video performance on HTC devices based on the latest Qualcomm MSM7xxx chipsets, HTC is providing the following statement.
HTC is committed to delivering a portfolio of devices that offer a wide variety of communication, connectivity and entertainment functionality.? HTC does not offer dedicated or optimized multimedia devices and can confirm that its Qualcomm MSM7xxx-based devices do not use ATI's Imageon video acceleration hardware.
HTC believes the overall value of its devices based on their combination of functionality and connectivity exceeds their ability to play or render high-resolution video. These devices do still provide a rich multimedia experience comparable to that of most smartphones and enable a variety of audio and video file formats.
HTC values its customers and the overall online community of mobile device enthusiasts and fans. HTC plans to include video acceleration hardware in future video-centric devices that will enable high-resolution video support.??
Until another statement is released by HTC regarding this matter, I am afraid that we cannot comment any further on the matter of driver updates for the current range of devices.
As HTC do not sell the devices directly we are unale to offer you a refund, if you are not happy with your purchase please speak to your retailer.

Welcome on board
Regarding your post. Yes that is one of the standard replies folk have been getting. However we have a long running thread on this subject where this has already been shown. There appear to be other responses from HTC that are more hopefull.
I will close this thread and if you wish to read up or post on this issue see here:
http://forum.xda-developers.com/showthread.php?t=359534&page=130
Mike

Flash for ARMv6/v7 devices Q2 2009!?

http://www.adobe.com/aboutadobe/pressroom/pressreleases/200811/111708ARMAdobeFlash.html
For immediate release
Support for Flash Player 10 and Adobe AIR to Bring Rich Internet Applications to ARM Powered Devices
ADOBE MAX 2008, SAN FRANCISCO AND CAMBRIDGE, — Nov. 17, 2008 — Adobe Systems Incorporated (Nasdaq:ADBE) and ARM [(LSE:ARM); (Nasdaq:ARMH)] today announced a technology collaboration to optimize and enable Adobe® Flash® Player 10 and Adobe AIR™ for ARM Powered® devices, ranging from mobile phones to set-top boxes, mobile Internet devices, televisions, automotive platforms, personal media players and other mobile computing devices. The collaboration is expected to accelerate mobile graphics and video capabilities on ARM platforms to bring rich Internet applications and Web services to mobile devices and consumer electronics worldwide.
The joint technology optimization is targeted for the ARMv6 and ARMv7architectures used in the ARM11™ family and the Cortex™-A series of processors and is expected to be available in the second half of 2009. The partnership stems from the Open Screen Project, a broad Adobe sponsored initiative of industry leaders - including ARM - to deliver a consistent runtime environment across multiple devices by taking advantage of Adobe Flash Player and, in the future, Adobe AIR. The initiative is set to address the challenges of Web browsing on a broad range of screens, and remove the barriers to publish content and applications seamlessly across screens. For more information, visit www.openscreenproject.org
More at http://www.adobe.com/aboutadobe/pressroom/pressreleases/200811/111708ARMAdobeFlash.html:cool:

Google Currents

Beautiful, free, favorite publications for your phone and tablet.
Google Currents delivers beautiful magazine-like editions to your tablet and smartphone for high speed and offline reading. Editions are all free and include:
* Publisher editions - Publishers such as Forbes, The Guardian, TechCrunch, PBS, Saveur, and more have produced hundreds of editions including in-depth articles, videos, fine photography, slideshows, live-maps, and social streams.
* Google trending editions - Google Currents uses Google search technology to hourly build a set of editions tracking the five most recent trending stories in categories such as world, entertainment, sports, science, and more. Each story is presented through a fresh edition of articles, videos, and pictures,
* Your favorite blogs and feeds - Instantly, turn your Google Reader subscriptions, or any of your favorite blogs/feeds into a beautiful edition with a magazine feel.
Each edition is available for high speed offline reading, and provides quick-touch sharing. Google Currents self-adapts to differently sized phones and tablets, with your subscriptions synchronized across devices. Google Currents - a reading experience not to be missed.
Named by New York Times, The Next Web, SlashGear and more as a top 10 Android app in 2011.

It's nice but articles aren't marked as read so it's completely useless for me.

Also there is no multilanguage, eg. croatian articles etc.
Sent from SpeedMachine i9023

A question regarding the google’s support

Hello everyone, I just bought the new chromecast with google tv, but then I started to read the google will require new devices on March to have AV1 codec. I was surprised to see that the chromecast doesn’t support it. Now I guess that on my end, there is not a big difference if the device supports AV1 but I was wondering, if it doesn’t support AV 1, will it still get updates from google of future android updates like the android 11? If not I would prefer to wait for their next chromecast so I will have better and longer support
thank you in advance!

This is a much more interesting requirement than just "I want better stuff". AV1 is basically the "royalty free" alternative to HEVC. Its not necessarily BETTER than HEVC, but you don't have to pay royalties to MPEG-LA for its use.
Basically, what is going on is this; Google believes that their media streaming mass is now enough that they can beat down MPEG-LA. Up until now, MPEG-LA has railroaded every silicon vendor into paying them royalties to include AVC and HEVC, and to LEAVE OUT royalty free codecs like Theora, VP9, and AV1. This has, in turn, forced MEDIA VENDORS to use AVC and HEVC encoding for the media that they are distributing, and also paying royalties to MPEG-LA on those -- because they have no alternative since the recipient hardware doesn't support Theora, VP9, or AV1.
But now that Google is making it a requirement, the expectation is that silicon vendors are now going to go back to MPEG-LA and say "Hey screw you, I'll still pay you the royalties for HEVC, but we have to strike out this part of the contract that says we can't also include AV1. We can't sell the chip at all without it, so if you don't like it, suck an egg."
In the short term, which means over the next few YEARS, this will have no impact on you at all, because the media vendors will continue to have to support legacy hardware. But after all of the hardware in use was made AFTER the AV1 requirement came into effect, the media vendors will have the option to drop HEVC and save on the royalties. After the media vendors drop HEVC, then so can the hardware vendors and MPEG-LA can die.
Even if you are a consumer of pirated media, remember that pirates don't pay royalties and operate with the objective of sticking it to "the man". That means that the stuff pirates encode will continue to use AVC and HEVC in order to maximize consumption.
Now as far as gaining future updates goes, Google is saying that they want NEW devices to support it. Legacy hardware will certainly NOT be limited in this manner. Also, Google isn't subject to these requirements -- hypocrisy is legally permissible, although it would likely be bad form.
And don't get caught up in the wait for all the amazing stuff that is coming "next year". There will *always* be something better just around the corner if you wait, so you will end up waiting literally forever.

96carboard said:
This is a much more interesting requirement than just "I want better stuff". AV1 is basically the "royalty free" alternative to HEVC. Its not necessarily BETTER than HEVC, but you don't have to pay royalties to MPEG-LA for its use.
Basically, what is going on is this; Google believes that their media streaming mass is now enough that they can beat down MPEG-LA. Up until now, MPEG-LA has railroaded every silicon vendor into paying them royalties to include AVC and HEVC, and to LEAVE OUT royalty free codecs like Theora, VP9, and AV1. This has, in turn, forced MEDIA VENDORS to use AVC and HEVC encoding for the media that they are distributing, and also paying royalties to MPEG-LA on those -- because they have no alternative since the recipient hardware doesn't support Theora, VP9, or AV1.
But now that Google is making it a requirement, the expectation is that silicon vendors are now going to go back to MPEG-LA and say "Hey screw you, I'll still pay you the royalties for HEVC, but we have to strike out this part of the contract that says we can't also include AV1. We can't sell the chip at all without it, so if you don't like it, suck an egg."
In the short term, which means over the next few YEARS, this will have no impact on you at all, because the media vendors will continue to have to support legacy hardware. But after all of the hardware in use was made AFTER the AV1 requirement came into effect, the media vendors will have the option to drop HEVC and save on the royalties. After the media vendors drop HEVC, then so can the hardware vendors and MPEG-LA can die.
Even if you are a consumer of pirated media, remember that pirates don't pay royalties and operate with the objective of sticking it to "the man". That means that the stuff pirates encode will continue to use AVC and HEVC in order to maximize consumption.
Now as far as gaining future updates goes, Google is saying that they want NEW devices to support it. Legacy hardware will certainly NOT be limited in this manner. Also, Google isn't subject to these requirements -- hypocrisy is legally permissible, although it would likely be bad form.
And don't get caught up in the wait for all the amazing stuff that is coming "next year". There will *always* be something better just around the corner if you wait, so you will end up waiting literally forever.
Click to expand...
Click to collapse
Thank you!! I didn’t know all of that, this whole thing is way more clear to me right now.

Themes / Apps / Mods s21 ultra 108mp raw

hello i'm nosidam although you can refer to me as nosi or idam for short, at any rate it has come to my attention that for over two year's individuals much like myself that are into high resolution photography have been wanting access to the raw resolution of the hundred and eight megapixel (108mp) sensor and countless have tried but unfortunately to the best of my knowledge to no avail, for the past few months i've been working on just that and recently completed the project. the hundred and eight megapixel (108mp) sensor with raw resolution has been unlocked the only dilemma now is making it possible for other's to do it, my method required a very custom language and architecture emulation in order to make it possible and unfortunately the very language and architecture as you could surmise from the necessity for emulation was derived from custom harware and wasn't designed to be utilized in conjunction or substitution for commercial applications or software, additionally unfortunately the language is behind a wall of confidentiality obligation due to what it's used in and for so as you can imagine that means i can't simply distribute it openly although i am working on another project to make it possible utilizing commercially accessible and viable software that can be distributed so that it'll be available for disclosure although until then despite not being able to currently share something distributable i can actually show you the results and comparisons and results of my tests as well as give you some interesting statistics lol.
project C.I.A.R.A. - Google Drive
drive.google.com
that should be a link to a google drive folder that has various comparison photos, i've never posted on here before so i don't know if the attached image's will be fully viewable in their respective resolution or if they'll be compressed or not as of such you should be able to download and view the images without any compression from google drive also i tried drop box but it's uploading was spotty and slow despite having fiber gigabit internet and they only offered two gigabytes, so google drive being much faster and consistent without random pauses for uploading in addition to boasting a free ten gigabytes was a clear winner lol,
the phone's default hundred and eight megapixel (108mp) sensor photo is the file labeled:
"20230516_175804"
it's resolution is twelve thousand by nine thousand (12,000x9,000) with a standard dynamic range and is a jpeg file that has been compressed down from what should have been an absolute minimum of a hundred and eight megabytes (108mb) down to just thirty one point seventy six megabytes (31.76mb) which is a minimum compression in file size of seventy point fifty nine percent (70.59%) so as you can imagine it becomes something similar and or closer to being akin to that of a hot mess so to speak, you'll usually see over sharpening occasionally to help accommodate for a lack of quality to give "perceived quality" and seemingly a lack of dynamic range(potentially from the compression or justcthe onboard post processing) as well as artifacting... which personally i do understand why they would do such a thing, people would run out of memory substantially faster if each photo was over a hundred megabytes minimum but honestly if i'm spending one point four thousand dollars on a phone then i'd like access to everything the camera has to offer therefore even if it's hidden behind advanced settings i think we should at least have the choice, although unfortunately even the twenty one ultra with all of it's very state of the art power and processing especially at release still struggles to handle that amount of information and memory so i have to wait between photo's because the phone gets very hot and also starts to stutter or freeze a bit, utilizing the full potential of the sensor is slightly unstable but still possible and i think they should allow it could to be enabled with a disclosure that it's a potentially unstable and experimental setting but instead it's full potential has remained behind close doors so to speak (os lockdown and software lockouts) well i'm working on making the raw one hundred and eight megapixel(108mp) sensors raw potential commercially available i'm also working on a professional mode in my own functional language which will allow much more fine precision control.
now for the moment of truth, the file named:
"20230516_175938"
is twelve thousand by nine thousand (12,000x9,000) in resolution and has a file size of one hundred and sixty nine point fifty four megabytes(169.54mb) with a seemingly high dynamic range(either that or the standard dynamic range has been impacted by the onboard post processing and compression) so just by the file size differential i'm quite certain that you can ascertain that it's actually going to retain all of it's quality lol it's fifty six point ninty eight percent(56.98%) higher in file size than the bare minimum hundred and eight megabytes(108mb) standard, overall it's file size in comparison to the phone's default version is five hundred and thirty three point eighty two percent(533.82%) higher meaning that the phone's image is only eighteen point seventy three percent(18.73%) the size of the raw file quality one, which is a mind-numbingly substantial difference lol and personally i will always take higher quality and larger file sizes over low quality smaller file sizes, i haven't gotten an s23 ultra yet but if i do you can be sure that i'll endeavor to unlock it's two hundred megapixel(200mp) sensors potential, it's my opinion that if these sensors exist in our phones then we should be allowed to fully utilize they're capabilities and potential lol.
i created some very easy comparison crop out photos from each image that have been cropped(not resized) to the standard 1440x3200(WQHD+) resolution of these screens, the first screen shot is a WQHD+ comparison cropped from the default one hundred and eight megapixel(108mp) photo and is named:
"IMG_20230520_133504"
and is very clearly compressed by the aforementioned percentage whereas the WQHD+ comparison taken from the raw quality version is named:
"20230516_221938"
and is very clearly not compressed and retains all of it's raw quality potential.
on a sidenote i'd like to extend special thanks to M0nK_101 for suggesting a variety of sharing services such as drop box and google drive at my request to share the comparisons lol.
^.^
if you have any questions or concerns feel free to let me know.
with that said i'd like to thank you for potentially taking the time and patience to read this i appreciate it.
^_^

So like any update? Will it work on other devices using samsung sensor?
like Redmi 10 pro using hm2

Inzamam567 said:
So like any update? Will it work on other devices using samsung sensor?
like Redmi 10 pro using hm2
Click to expand...
Click to collapse
affirmative unfortunately thus far i have not yet found an unofficially distributed commercially accessible means to unluck the 108mp sensors raw quality potential outside of my project C.I.A.R.A emulation although rest assured i'm still currently working on it also i'll elaborate compatability details when a publicly distributable prototype is viable lol.
^_^

Is this just an app or an entire OS?

neither it behaves in certain ways like an application although ultimately it's custom hardware software emulation that allows the internal onboard sensor algorithms responsible for compression and file formatting to be sidestepped so to speak.
^_^

I see, very interesting! So I would Hage to hook the camera module up to another board in access it from there? Or will it be possible to use the phone itself?

indeed and negative you could utilize the phone itself.
^_^