Hi,
I've been searching around for a while, and being somewhat of a audio enthusiast I was looking forward to the rumored support of USB Audio out in ICS. Sadly no such thing has been implemented yet as far as I know.
There is an issue created on code.google's android site:
(I'm not allowed to post links as I'm a new user but this is the link) code.google.com/p/android/issues/detail?id=24614#makechanges
I'm no experienced kernel developer, but maybe some of the wizards we have working on kernels here in the Sensation section could have a go and try to get this working on the custom ROMs?
Might not be a large usergroup out there that would like to use an external DAC with their phones, but I'm one of them and I know there should be more out there.
Anyway, It is a great feature that Android is currently lacking and if there isn't anything you yourself can do about this. Then your wrong, you can voice your opinion and help out by voting on the link above. Just Press the star at almost the bottom of the site above the comment field.
Thank you for reading this far.
/Kultom
Shameless B-U-M-P
Moving from a thread in head-fi (I CANNOT POST THE LINK DUE MY LOW N. OF MESSAGES) i've discover that sadly I cannot use my Fiio E17 DAC with the full power of usb
Reading in the request page of Google Code - Issue 24614 - (I CANNOT POST LINKS DUE MY LOW N. OF MESSAGES) I've discover that some firmware are supporting this feature.
May some of the coder add this possibility in the sensation firmware?
Really appreciated! (sorry for my poor english language...)
Finally!
Android 4.1, Jelly Bean
[...]
USB Audio
USB audio output support allows hardware vendors to build hardware such as audio docks that interface with Android devices. This functionality is also exposed with the Android Open Accessory Development Kit (ADK) to give all developers the chance to create their own hardware.
Thanks Google :good:
Hello, you may say this is the wrong forum to ask this but I've googled all night and the closest thing I found to what I want is the kind of thing XDA developers do to Samsung Galaxy cameras. If you cannot help, could you at least tell me where I can find this kind of help?
Basically, I need to modify a pocket camera firmware, or find someone who could do it for me. There would be a batch of code that I want the camera to skip/ignore/jump over.
To be a little more specific: when I turn my camera on (it's a pocket camera with its own proprietary firmware, NOT an Android camera), there's a zoom error. The error message stays on the screen and I cannot access the camera functions because of it. I want the camera to skip checking the lens assembly altogether.
If there's anything on this forum or any other forum that resembles what I'm thinking, please direct me to it.
Thanks for reading.
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.
Greetings Srs,
I'm the Zero 5 Pro owner which I guess, most of the Zero series owners, we are a little disappointed about the support from the vendor.
For this matter, I'm starting to compile from ASOP with the latest source code for this device.
I found Infinix already removed the stock firmware from the official website, so I can't find the current firmware which the device is currently running x603-h575b-n-190610v136 (if any of you have it back up and don't mind sharing the flashable version please add a link for the binaries, it could be useful).
I'm figuring the device tree, new kernel, and MT6575 documentation (along with the other device's documentation the phone it's built with) so I can customize as much as I can to make a clean build, no blobs, and trash, just to have a feel of the new Android in which I think a phone that could live a couple of years more.
Since the Android Studio AVD is not that customizable as I would like to replicate the phone components I0m looking for a decent emulator where I can specify the devices I know the phone has, and try it there first before going to the hardware itself.
Since I can't post directly in the Infinix Zero 5 Thread, if you please move the post to that thread, do so for me.
Also if you want to share advice, tips or suggestions, tools, etc, please feel free to let your comment below.
If I have news and advances in this process I'll be sharing under this same thread.
Cheers,
crappy OS GREAT HARDWARE...
Phronesis ROM had more useful function than the 05
I have discovered this app called "Koala Phone" at https://forum.xda-developers.com/android/apps-games/app-koala-phone-launcher-simple-phone-t2977253 , it isnt maintained by its developer anymore, its full of bugs especially on newer versions on android, i found the apk for it here: https://apkgoogle.org/apps/koala-phone-launcher-gold-v-1-22-0-apk-paid/ , please at least do these things:
Fix most of the bugs and make it work properly on newer versions of Android
Replace all instances of the phrase "Koala Phone" and their Koala logo with something else (So no copyright infringement)
DONT put certain features behind a paywall or put ads in it (This allows it to be useful to as many elderly people as possible)
Release it to Google Play
Maybe also release the source code to Github/Gitlab
I know the app isnt open source, but someone can decompile it
This looks like a good thing but maybe there wasn't any demand. I think someone should just start a new open source for this kind of stuff where this can be downloaded with ease.
i'm also not sure here is the right audience , I mean for the koala