So I learned that there is something called Camera2 API, which as far as I understand, allows third party apps to take full advantage of camera on your android phone.
There are 4 levels, the higher the level, the more features and more support you have.
Sadly, Xperia Z2 has no support for Camera2 API, when I install Camera2 API Probe App, it tells me that Hardware support level is "Legacy" which means no support for Camera2 API.
I was wondering, is this set in stone or can it be changed ?
Maybe by rooting or something, not sure.
Hence why I am asking here, do you know ?
So seems like Xperia Z2 simply has no Camera2 Api support and that's the end of that.
That's OK, next time when I go out to buy a new phone I will look for one that has this
As well as unlocked bootloader and sim.
Cheers
Related
As most of you following the KitKat developing scene for lower end devices probably know, Android 4.4 introduced the low_ram property. On 4.4 ROM's, transparent statusbar is disabled for example for devices with this property set to true.
Now, the situation is:
I'm running CM10 (4.1), because it's one of the most stable custom ROM's for my device. A few days ago I put the following line to build.prop:
Code:
ro.config.low_ram=true
hoping to notice better optimized RAM management. It's hard to claim an effect knowing that it could very well be placebo, so I was hoping someone understanding this better could explain the effects to me.
Added a new ActivityManager.isLowRamDevice() to allow applications to detect when running on low memory devices and choose to disable large-RAM features.
(...)
We are introducing a new API called ActivityManager.isLowRamDevice() for applications to determine if they should turn off specific memory-intensive features that work poorly on low-memory devices.
For 512MB devices, this API is expected to return: "true" It can be enabled by the following system property in the device makefile. PRODUCT_PROPERTY_OVERRIDES += ro.config.low_ram=true
Click to expand...
Click to collapse
http://source.android.com/devices/low-ram.html
I too noted that it says API, so that means that it's dependent on the OS version. Is there any way it can have an effect on memory mangement if not runnign 4.4?
Same goes for disabling JIT(see a bit lower on the source page), which needs to be set in the 'product makefile'
Bump
good queries always go unanswered
I asked it in a Reddit thread too and someone said it won't work, but I don't think that guy has more knowledge about it than you or me. However, since they say it's an API, and API's are bound to the Android version I don't have much hope for this to work...
For the time I've tried it, I didn't notice any difference anyway, if there is, tweaks like zRam will benefit you much more anyway.
On CM11 it disabled some effects and gave a lotof free ram. The effect depends on rom and implementation.
so we may as well just add it to the build.prop anyway, if it works then its a bonus if not no harm done.
i think it's only for KitKat
https://android.googlesource.com/platform/frameworks/base/+/b4e12494935697fa4ede006b37e6be889ef27109
https://android.googlesource.com/platform/frameworks/base/+/9fc5bae^!/
It was only added in kitkat.
Previously (only going as down as 4.2 though) if any you had isHighEndGfx and isLargeRAM (which at least on vanilla android were automatically detected at runtime, thus not user-settable)
Hi everyone,
Is there a way to use Camera2 API only for certain apps? For example, Cinema-FV5 works way better in low-light when Camera2 API is disabled, but then I can't use Google Camera port so my photos which are taken with stock app look worse. Would be really cool to use both of these apps to their max potential without rebooting phone everytime
I just know it but usually google camera and miui stock camera can still run as usual
Have you tried to add Cinema-FV5 to the list of apps that use Camera API 1?
Edit build.prop and search for:
Code:
camera.hal1.packagelist=
Add the package name of the app to that list, and it should use the old API
alresave said:
Have you tried to add Cinema-FV5 to the list of apps that use Camera API 1?
Edit build.prop and search for:
Code:
camera.hal1.packagelist=
Add the package name of the app to that list, and it should use the old API
Click to expand...
Click to collapse
I didn't believe it would work, thanks! Now Cinema-FV5 seems to be even less buggy than it used to be haha
Please tell me in detail so that my stock camera can work easily and i can able to do volte video calls. Because after enabling the camera 2 api stock camera gives error of camera cant connect in hdr and video calls stopped working. Please help.
Hello guys, after of 6-7 months of using XZ1 today I sent an Email to Sony regarding the Raw Support of our Xperia and asking about the Gesture Navigation which was not included in the Pie Update.
Here is what I got as an answer:
Thank you for contacting Xperia Support by Sony.
We would like to inform you that our company’s primary purpose is to provide ever improving services and always acts in our customers’ best interest. We would like to thank you for your remarks and inform you that your email has already been forwarded to the appropriate department.
With regards to your inquiry, we would like to inform you that Android 5.0, 5.1, 6.0, 7.0, 7.1, 8.0 and 9.0 support camera features via android.hardware.camera2, and Google defines three modes for the new camera features:
-Legacy mode (no support RAW capture)
-Limited mode (optional capability for RAW capture)
-Full mode (optional capability for RAW capture).
Currently, Xperia devices support the Legacy mode, which incorporates features and functionality in addition to our already renowned camera experience. We are always monitoring our customers' expectations, and as for taking photos in RAW format we will consider this for the future.
We currently have not included gesture navigation in Android Pie, and cannot comment on future plans to add it. However, we will continue to listen to customer feedback and endeavor to evolve Xperia smartphones based on their needs.
We would also like to thank you for being interested in Xperia products and to inform you that we are always at your disposal for any further assistance.
"We will continue to listen" and they never do. LOL.
Tux111 said:
"We will continue to listen" and they never do. LOL.
Click to expand...
Click to collapse
what an ironic answer is that difficult to import a raw support?
kcannonball said:
what an ironic answer is that difficult to import a raw support?
Click to expand...
Click to collapse
They just dont care about user feedback. Easy.
Employees just follows the guideline from the CIO. That's the problem.
lets sign a petition to add RAW support to xperia devices hopefully then we will get Google Cam to work
Gesture navigation works!!!!
Guys it has been achieved through ADB
https://forum.xda-developers.com/cr.../pie-xperia-10-10-plus-launcher-t3905699/amp/
But you have to use the XPERIA 10 launcher port or else the stock launcher will crash if you try going to recents menu.
john_david9000 said:
Guys it has been achieved through ADB
https://forum.xda-developers.com/cr.../pie-xperia-10-10-plus-launcher-t3905699/amp/
But you have to use the XPERIA 10 launcher port or else the stock launcher will crash if you try going to recents menu.
Click to expand...
Click to collapse
this is a great share Thank youu I wish raw support comes too
I am looking into developing an app using the live video feed of a device's IR camera for a particular use case. My research was not very fruitful so far.
Question: Is there any device on the market letting me access the IR camera, stock or rooted? Are there custom ROMs or open drivers allowing this?
I know there is a Lineage OS (v.16) ROM for the Poco F1 with IR face unlock support. Is this a possible starting point, or is access to the IR camera also locked? If the latter, how is the access prevented? Via encryption of the video feed? Via a security subsystem, be it hard- or software? Or just via obfuscating how to interact with the device?
EDIT: The app I am planning does not have to run on many different devices. At the current project state it is only about creating a demonstrator, a proof of concept. And it is not about spying on people, in case anyone wonders about my cryptic first sentence. I am looking into alternative authentication options.
https://forum.xda-developers.com/poco-f1/themes/ir-camera-pocophone-t3886516
Hello together,
does anyone know why the ToF sensor on the 1 III isnt supported by the ARCore Depth API (see [1]) and if there will be a fix in the near future?
Are there any 3D scanner apps that can utilize the ToF sensor without relying on ARCore or is there an alternative ROM with ToF support?
Best regards,
some XDA greenhorn
[1] https://github.com/google-ar/arcore-android-sdk/issues/1327
Your github link already has the answer. It isn't supported because Sony did not implement the Depth API to use their TOF sensor. Simple as they didn't do it. This is the drawback of an "open" operating system. It is up to the OEM/Vendor/Manufacturer to implement features that are not "mandatory" by the OS creator, Google.
Why they didnt do it we will never know. It might be a way to reduce development costs. Maybe Sony thinks that their target market will only use the TOF for photography and not for anything else.
So there are no other apps that can take advantage of something that to the apps knowledge does not exist. Only Sony apps can "see" the TOF sensor, it is not exposed outside of that. No other apps will be able to see it unless they know how to access whatever API Sony maybe using. Or maybe Sony just access the TOF sensor directly in the camera app only, there is no API involved.
Maybe a third party rom can expose it if they can figure out how to access it, either via drivers released by Sony, or by their own trial and error, reverse engineering, etc.