11–17 of 17 posts
Even better, it loses to iPhone 7. Apple silicon is really far ahead right now.
Earlier quoted context omitted.
Try to use their camera2 api to see what I mean about sloppily put together. I’m with you on iTunes. Thankfully I haven’t had to use it in years.
You mean the same camera2 API that's used by the Google Pixel 2 - the world's best smartphone camera?
Earlier quoted context omitted.
You mean the same camera2 API that's used by the Google Pixel 2 - the world's best smartphone camera?
Let me assure you, this was possible in spite of, not thanks to this API. Words fail to describe how horrible and unusable it is.
Camera API's also need to be performant. Specifically, converting the data from one form to another, compressing or decompressing it, adjusting colorspaces, rotating it, or copying it from one memory to another typically isn't possible to do as part of the abstraction.
Simple things like rotating a 240fps video to be the right way up in real-time really aren't doable, which means those details have to be passed on to the application if the camera hardware is mounted the other way up.
That means the API itself needs to get the application to handle those details if it wants to offer performance.
All those possible hardware details which the API can't hide for performance reasons lead to a huge and complex API. If you want a simple API, you're free to build one on top (and some exist), but beware - performance will be atrocious on some hardware.
As a rule, performance of flagship Android phones lags iPhone by 2 years or so. Been that way as long as I can remember. Worse, floating point perf lags by about a factor of 3. I don’t know why Qualcomm and Samsung keep doing this to themselves. It’s not like they can’t design decent chips. They just choose not to. The situation is further exacerbated by Android being a disorganized, sloppily put together pile of exc…
Funny isn't it how an Android phone with an old Snapdragon 835 from last year can so easily beat an iPhone X. https://www.youtube.com/watch?v=uL99tRQR9W0 The "sloppily put together pile of excrement" iPhone X can't even keep apps in memory as it loses to an Android phone from last year. If a Note 8 can make the iPhone X look that bad just think what this year's S9 will do.
Therefore, I would suggest it's best to use other kinds of real world tests, like for example completing a specific set of tasks, or webpage loading tests, which aren't yet over optimized.
Earlier quoted context omitted.
Let me assure you, this was possible in spite of, not thanks to this API. Words fail to describe how horrible and unusable it is.
When looking at the API, you have to take into account limitations the designers had. Specifically, the API is part of the android layer that Google writes and OEM's can customize. It must, however, support any underlying camera HAL and associated hardware. The software for that is typically written by SoC vendors, and therefore the camera2 API needs to work with existing HAL layers without modification. Camera API's…
Earlier quoted context omitted.
When looking at the API, you have to take into account limitations the designers had. Specifically, the API is part of the android layer that Google writes and OEM's can customize. It must, however, support any underlying camera HAL and associated hardware. The software for that is typically written by SoC vendors, and therefore the camera2 API needs to work with existing HAL layers without modification. Camera API's…
Excuses, excuses. Meanwhile iOS API for the same thing requires 1/10th the amount of code, is easy to use, and has great documentation.
https://www.youtube.com/watch?v=UY4a0IPXotA
While the S9+ seemingly handles everything and anything you throw at it the X has some obvious difficulties every now and then.
PS: I (still) have a (ancient) iPhone 4 right now. No fanboyism here.