As a photographer, the most important feature for me in an upgrade now is whether or not a device supports DNG (RAW) capture with it's camera. I also firmly support the buying of used devices to keep them out of landfills (or irresponsible recycling programs) for as long as possible.
I don't need the absolute latest gear. So I'm happy to snap up gently used.
Would those in the know kindly use this thread to begin listing any device which can support the new Camera2 Module in Android 5.x? I just want to know if the device is capable of outputting DNG files.
Thanks in advance!
Never mind ya'll.
It was late when I posted this. I've been digging a bit through Google and found what I needed to know.
Carry on.
I was doing research on android's Biometric authentication .As we know back in android Marshmallow(6.x.x) we got native support for fingerprint recognition/fingerprint authentication.Not too long samsung started giving new way to unlock devices iris scanner in s8/s8+ last year,so it's there own implementation in S/W and so main problem is you cant use their implementation in any custom rom because AOSP upstream does not supports it.Now from Android Pie onwards they deprecated FingerprintManager API and bring us new BiometricPrompt API,means we can use other methods like iris,face recognition and other methods for unlock/authentication.Probably iris or face recognition might come in coming pixel.
So my main point of making this post is to discuss about the existing device with proprietary sensors like in galaxy s8/s8+/s9/9+,note8/9,mi8,poco f1 etc etc! .
Will we able to get those existing sensors work on custom roms?as far source code is concerned ,we got whole device code of POCO f1(i am not sure about IR face reco).
one thing i want mention:-i remember galaxy s5 released with android 4.4.x,which clearly dont have FingerPrintManager Api,but some smart dev xda managed to get that sensor working on android M based custom ROM .Sooooo maybe we will able to get our,s face IR working in next iteration of android pie.
I am learning about the android"s arch(also learning how to develop custom roms from scratch)
So devs on xda who have knowledge ,must share .i am always ready to learn
topics i refer for case study:-
https://source.android.com/security/biometric/
https://www.xda-developers.com/iris-scanners-native-support-android-p/
https://www.xda-developers.com/android-p-new-biometrics-api/
Help me out! I can only REPLY to threads, I can not POST such one!
thetripleS said:
Help me out! I can only REPLY to threads, I can not POST such one!
Click to expand...
Click to collapse
Bro you are new member, so don't have permission to post, go read xda's rules and terms of XDA. And secondly do a Google search for your problems and stop spamming irrelevant replies
Please!
Jaskirat singh said:
Bro you are new member, so don't have permission to post, go read xda's rules and terms of XDA. And secondly do a Google search for your problems and stop spamming irrelevant replies
Please!
Click to expand...
Click to collapse
Sorry for inconvinience, I digged google, i couldnt find anything! Please tell me when can i start posting questions?? Its true that i am a new member and i started XDA today itself.
thetripleS said:
Sorry for inconvinience, I digged google, i couldnt find anything! Please tell me when can i start posting questions?? Its true that i am a new member and i started XDA today itself.
Click to expand...
Click to collapse
Go here you get an idea which sub-forum you need to post
https://forum.xda-developers.com/poco-f1
.
RUPESHBW said:
Who are you to tell him what to do xda is about sharing tech knowledge there is nothing wrong in posting by new member. He giving his knowledge i had question with his argument above i got my answer. If you cant let other not demotivate.
Click to expand...
Click to collapse
If have you anything related to my topic then most welcome.
And who "ARE" you to correct me.
I didn't say anything offensive to him and secondly i told him to read to rules and terms.
And yea i was not demotivating him, its you who judging here.now stop arguing.
Please :- "STICK WITH THE TOPIC!"
Jaskirat singh said:
If have you anything related to my topic then most welcome.
And who "ARE" you to correct me.
I didn't say anything offensive to him and secondly i told him to read to rules and terms.
And yea i was not demotivating him, its you who judging here.now stop arguing.
Please :- "STICK WITH THE TOPIC!"
Click to expand...
Click to collapse
Oh its you posted this thread i forgot sorry didnt see i thought somebody just delete this arguments :laugh:
RUPESHBW said:
Oh its you posted this thread i forgot sorry didnt see i thought somebody just delete this arguments :laugh:
Click to expand...
Click to collapse
Its ok :/
Jaskirat singh said:
Will we able to get those existing sensors work on custom roms?as far source code is concerned ,we got whole device code of POCO f1(i am not sure about IR face reco).
Click to expand...
Click to collapse
Correction: we do not have whole device code. Nobody ever gets whole device code.
We have kernel source, but it is missing something. Mostly audio and wifi stacks. Wifi is easy to fix thanks to CAF, but audio is more difficult.
Making custom ROM's takes time because it is one big experimental process to get AOSP to work with existing blobs (pre-built binaries from vendor for hardware access) because we don't have the source code.
For IR Face recognition, there would have to be a driver in kernel for the camera, definitely. But that doesn't make it a given that custom ROMs can use it. It may also be missing in kernel sources, like wifi and audio is missing.
Ideally, when Poco gets Pie official update, yes - it will use the biometrics API, meaning that custom ROM's should be able to interface with stock blobs to also support it - this is achieved in much the same way as experimenting to get all the other hardware working. But it's impossible to know for sure until actual official Pie comes.
Most of this stuff relies on CAF, probably. If the kernel driver for the IR camera is found, or included in kernel source (don't know if it is but my guess is no), then they will have something to work on.
I think it's a bit early to speculate on such things now, since there is no public announcement from the community of any AOSP release based on Oreo yet, even.
CosmicDan said:
Correction: we do not have whole device code. Nobody ever gets whole device code.
We have kernel source, but it is missing something. Mostly audio and wifi stacks. Wifi is easy to fix thanks to CAF, but audio is more difficult.
For IR Face recognition, there would have to be a driver in kernel for the camera, definitely. But that doesn't make it a given that custom ROMs can use it.
Ideally, when Poco gets Pie official update, yes - it will use the biometrics API, meaning that custom ROM's should be able to interface with stock blobs to also support it. But it's impossible to know for sure until actual official Pie comes.
I think it's a bit early to speculate on such things now, since there is no public announcement from the community of any AOSP release based on Oreo yet, even.
Click to expand...
Click to collapse
i was wandering around and testing some things with this device.
Yes! That ir receiver(sensor) IS behaving as camera (which is not a color sensor only takes IR as input)
For testing i used miui hidden settings app
Go to hardware test(CIT)>52.ir camera.
And voila! You can see output on screen what this sensor sees
NOTE:- you can open this CIT settings if you tap kernel version number times, but you won't get that "ir camera" option, soooo you have to install that app
Btw anyone working or creating device tree for this device?
Well yea xiaomi is notorious for not giving up whole source, that's kinda bytuh thing
CosmicDan said:
Correction: we do not have whole device code. Nobody ever gets whole device code.
We have kernel source, but it is missing something. Mostly audio and wifi stacks. Wifi is easy to fix thanks to CAF, but audio is more difficult.
Making custom ROM's takes time because it is one big experimental process to get AOSP to work with existing blobs (pre-built binaries from vendor for hardware access) because we don't have the source code.
For IR Face recognition, there would have to be a driver in kernel for the camera, definitely. But that doesn't make it a given that custom ROMs can use it. It may also be missing in kernel sources, like wifi and audio is missing.
Ideally, when Poco gets Pie official update, yes - it will use the biometrics API, meaning that custom ROM's should be able to interface with stock blobs to also support it - this is achieved in much the same way as experimenting to get all the other hardware working. But it's impossible to know for sure until actual official Pie comes.
Most of this stuff relies on CAF, probably. If the kernel driver for the IR camera is found, or included in kernel source (don't know if it is but my guess is no), then they will have something to work on.
I think it's a bit early to speculate on such things now, since there is no public announcement from the community of any AOSP release based on Oreo yet, even.
Click to expand...
Click to collapse
Did you perhaps had some time to look in to this ?
If they used this api in the latest pie beta ?
i read something om miui forums that they used the biometrics API in miui 10 pie versions from other phones.
i'm lacking the knowledge to look in to this myself :/
frietketeltje said:
Did you perhaps had some time to look in to this ?
If they used this api in the latest pie beta ?
i read something om miui forums that they used the biometrics API in miui 10 pie versions from other phones.
i'm lacking the knowledge to look in to this myself :/
Click to expand...
Click to collapse
I'm not sure where to look, to be honest. This seems more like a back-end thing that makes development easier, rather than adding new features? At least that's what I remember.
Also note that I have no interest in custom ROM's personally; I'm modding stock MIUI instead.
Create an AR emoji for OnePlus device. Like samsung.
sagidhamzakutty123 said:
Create an AR emoji for OnePlus device. Like samsung.
Click to expand...
Click to collapse
Thread Cleaned of Off Topic Posts.
Please elaborate more on your request. Currently AR Emoji is not available under camera options and OP does not really plan to implement it in the near future. You can use third party camera apps if you need something like that. I hope this thread will have some meaningful discussion from here on.
Feel free to get in touch if you have any concerns.
Im talking about porting samsung camera to other devices. Like google camera. Developer made it happen.
So here is the good news guys Xiaomi has now realised that google has much more developer resources to built better camra apps and alogrithem and that is why it is being said they are offically adding Hal3 and API2 supports from8.11.8 this rom is in close beta now but that means in future updates we can see native gcam support...
Which in other term means just installing or side loading the gcam app will be sufficient for gcam to work...
Here is the source of the news
https://www.gizmochina.com/2018/11/...om-opens-doors-for-google-camera-app-support/
Good to know.
Please. Carefully read the news before posting such thread.
"The MIUI 10 update has extended support for HAL3/Camera2API which is required by Google Camera app to run on any Android device."
Is not :
"We will support native gcam app"
But more like :
"Porting gcam will be simpler"
Good information!!! but before posting some thread this should be on the XIOAMI POCO F1 GUIDES , NEWS , DISCUSSION. Thanks
elpy909 said:
Please. Carefully read the news before posting such thread.
"The MIUI 10 update has extended support for HAL3/Camera2API which is required by Google Camera app to run on any Android device."
Is not :
"We will support native gcam app"
But more like :
"Porting gcam will be simpler"
Click to expand...
Click to collapse
whats the difference? you should read it with open eyes I guess.
Noob question: with this, will Gcam be able to make use of the second camera? Or simply Gcam isn't made with this purpose and only use the main camera (as pixel phones only have one)?
Poco Always had camera api2 enabled, no big news for us
Now we 'only' need 60fps video recording....
bravo2526 said:
whats the difference? you should read it with open eyes I guess.
Click to expand...
Click to collapse
It means you can't install official gcam from playstore. If you install the official version, it won't work. But it will be easier for developer to make it work for Poco.
If it's really natively supported, then some features will be disabled. Do you really think google will give their cam tech freely? They want you to buy their phones. While the ported version will have the features enabled.
For poco it was available out of the box , they enabled cam2api for all xiaomi devices now :good: ✌
So even with Android 9.0 Pie we still don't have RAW compatibility for our phone, and that would help a lot to catch better pictures and use different apps at theyr fullest. Please sign this petition and share it!
https://www.change.org/p/sony-bring...m=Search>SAP>IT>NonBrand-Tier 1>Head Term>BMM
FlorianSSJ said:
So even with Android 9.0 Pie we still don't have RAW compatibility for our phone, and that would help a lot to catch better pictures and use different apps at theyr fullest. Please sign this petition and share it!
https://www.change.org/p/sony-bring...m=Search>SAP>IT>NonBrand-Tier 1>Head Term>BMM
Click to expand...
Click to collapse
done
It should not be that hard to gain RAW since we have legacy HAL3. Its not a hardware limit just software limited. Think i will add this with my next Patch...
Done! Anything to get Sony to pull their head out of their [email protected]! I have an absolute disgust with companies limit their products on purpose via software, when the hardware is completely capable of more and some!
Miustone said:
It should not be that hard to gain RAW since we have legacy HAL3. Its not a hardware limit just software limited. Think i will add this with my next Patch...
Click to expand...
Click to collapse
It's full for me not legacy HAL3 but still doesn't support RAW.
Lazaros_K said:
It's full for me not legacy HAL3 but still doesn't support RAW.
Click to expand...
Click to collapse
Mine too but scroll down it states that it doesnt support raw capturing
Lazaros_K said:
It's full for me not legacy HAL3 but still doesn't support RAW.
Click to expand...
Click to collapse
Oh thanks for letting me know! It should be less hard in this case. Possible that a simple build.prop edit with a added Permission does the job. I will test that once my patch is booting on .306. I think SONY has just not added a little Part to disable this Feature. I just wonder why since it was working fine for Me on AOSP with My Patch and everything else worked too like HDR+ on GCam Port by Arnova... So... Give Me a while and it will be solved
More Infos can be found here: https://source.android.com/devices/camera/versioning
This Part is important:
The supported hardware level of the device, as well as the specific Camera API2 capabilities it supports, are available as the following feature flags to allow Google Play filtering of Camera API2 camera apps.
android.hardware.camera.hardware_level.full
android.hardware.camera.capability.raw
android.hardware.camera.capability.manual_sensor
android.hardware.camera.capability.manual_post_processing
By adding these Permissions should it at least be available as Option in Apps. Additional can it be added to the build.prop. Example Lines:
persist.camera.ae.capture.bound=
persist.camera.ae.instant.bound=
persist.camera.auto.hdr.enable=true
persist.camera.aux.camera=
persist.camera.auxcamera.swap=
persist.camera.aux.picture.size=
persist.camera.aux.preview.size=
persist.camera.batchcount=
persist.camera.CDS=1
persist.camera.continuous.iso=
persist.camera.dc.frame.sync=
persist.camera.dcrf.enable=true
persist.camera.dual.camera=
persist.camera.dual.camera.dump=
persist.camera.dual.camera.mpo=
persist.camera.dual_led_calib=
persist.camera.dumpimg=
persist.camera.dumpmetadata=
persist.camera.exif.rotation=
persist.camera.eztune.enable=1
persist.camera.facedetect=1
persist.camera.fdvideo=1
persist.camera.feature.cac=1
persist.camera.feature.restart=
persist.camera.feature.shutter=1
persist.camera.global.debug=
persist.camera.HAL3.enabled=1
persist.camera.hal3hfr.enable=1
persist.camera.hal3.prv.feature=1
persist.camera.hal.debug=
persist.camera.hdr.outcrop=
persist.camera.imglib.stillmore=
persist.camera.initial.exp.val=
persist.camera.instant.aec=
persist.camera.instant.capture=
persist.camera.is_type=5
persist.camera.jpeg_burst=1
persist.camera.kpi.debug=
persist.camera.led.on.period=
persist.camera.liveshot.size=
persist.camera.longshot.save=
persist.camera.longshot.stages=
persist.camera.ltmforseemore=1
persist.camera.mem.usecache=1
persist.camera.mem.usepool=1
persist.camera.mobicat=
persist.camera.multi_pass=
persist.camera.no-display=
persist.camera.nonzsl.yuv=
persist.camera.offlineraw=
persist.camera.ois.disable=0
persist.camera.ois.video=
persist.camera.opt.livepic=
persist.camera.preview_raw=1
persist.camera.preview.seemore=1
persist.camera.preview.ubwc=1
persist.camera.preview_yuv=1
persist.camera.raw.debug.dump=
persist.camera.raw.dump=
persist.camera.raw.format=
persist.camera.raw_yuv=
persist.camera.rdimodev
persist.camera.rdi.mode=
persist.camera.retro.number=
persist.camera.secure.mode=
persist.camera.set.afd=
persist.camera.snap.format=
persist.camera.snapshot.fd=
persist.camera.snapshot.number=
persist.camera.snapshot_raw=
persist.camera.stats.af.paaf=
persist.camera.stats.debug.mask=
persist.camera.thermal.mode=adjustFPS
persist.camera.time.monotonic=
persist.camera.tintless=1
persist.camera.tn.disable=
persist.camera.tnr.preview=1
persist.camera.tnr.video=1
persist.camera.video.CDS=1
persist.camera.video_raw=1
persist.camera.video.ubwc=1
persist.camera.zsl.backlookcnt=
persist.camera.zsl.interval=
persist.camera.zsl_matching=
persist.camera.zsl.mode=1
persist.camera.zsl.queuedepth=
persist.camera.zsl_raw=
persist.camera.zsl_yuv=
persist.capture.burst.exposures=
persist.debug.set.fixedfps=
persist.debug.sf.showfps=1
persist.denoise.process.plates=2
persist.sys.exif.make=
persist.sys.exif.model=
persist.tnr.process.plates=2
(This are experimental Values)
Thread closed
https://forum.xda-developers.com/xperia-xz/how-to/petition-camera-api2-support-xz-t3869110
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
Click to expand...
Click to collapse
XDA Rules