Hello, i was recently made aware that my usb 360 panoramic camera module (Lolly360) does not work in android 10 due to a bug in the source of Android 10 that lacks the proper permissions for devices that use USB video device class (UVC) api's. I'm not 100% how things work, but I think an api in the SDK28 (USBCamera-target-API-28.apk) is bugged but maybe has been fixed in the latest Android 10 source. Unfortunately, im not sure if it exists in OxygenOS 10.3.3.
Is anyone aware of this? And/or does anyone know where i could begin to tackle this issue?
I posted in the OnePlus community forums, but i feel like it may have fallen on deaf eyes
Sources for my information:
https://github.com/saki4510t/UVCPermissionTest/issues/1
https://issuetracker.google.com/issues/139087809
https://developer.android.com/about/versions/10/privacy/changes
https://www.camerafi.com/notice-android-10-devices-do-not-support-usb-camera-connection/
Related
With great respect to all developers that contribute to this forum:
WHEN ARE YOU GOING TO HACK CAMERA DRIVERS IN G TABLET HONEYCOMB ROM SO THAT WE CAN USE SKYPE AND OTHER APPS THAT NEED CAMERA FUNCTION WITHOUT DOWNGRADING ROM??
We want it...
THANK YOU.
Also i would like to say that GtabComb ROM 1.6 (now at 3.3 version) is report by many to have fully functional camera. The latest versions though do not have a working one. So what is it that made it function at that version? I personally use the Flashback 10.0 ROM.
some more remarks
Since no developer has replied i would like to ask some more things in regards to the honeycomb port camera drivers and if still noone answers then let them be....
Why don't use drivers from earlier versions with some kind of fix?
Why don't try to fetch drivers inside already installed systems that have working cameras and then make some kind of fix for g tablet?
Why does the HONEYCOMB PORT GtabComb v1.6 has a WORKING camera?
Why nobody doesn't have the slightest idea on how to make camera work on a honeycomb system?
I am not a developer myself but with all the respect i cannot understand why is it so hard to make a micro camera work at least...
Thank you.
Camera Drivers
I must personally say after trying the "Bottle of Smoke" and "Flashback" ROMs... the developers have done an amazing work. Thanks and congrats to the developers and ROM cooks.
Honeycomb has improved significantly over previous versions of Android and it is heavily comparable to other tablet (i)OSs.
In this particular case I can only miss the Camera and some flash functionality. But I can live without it considering the other improvements.
Now I ask:
Ins't it a matter of maybe getting the camera driver for say Linux and recompiling it for android?... Most manufacturers already make drivers for other OS's like android.
Cant we load the previous driver/module that worked?, the original Tap 'n Tap ROM had a working driver. Which is the filename?
Has anybody opened up the gTab and looked at the camera chip on the board, the brand, and model so we can do some research?...
Im sure we can find a solution for this issue, after all the beauty of this whole ROM thing is the amounts of flexibilty there is
If anybody has any answers to this maybe we can tray and find some solutions.
Hi All,
I have been a long time XDA user, and follow and utilize a number of threads for my android devices!
(
For the first time ever i have not been able to find what I'm looking for and so I send out a plea for help (or lay out a challenge if people prefer them) !!
I have a lenovo yoga 13 and can run a live version of android 4.2 however i do not want to complete a hard drive install due to the lack of support for the wifi and BT.
I was wandering if anyone would be able to create a yoga 13 ROM including the driver for the realtek RTL8723a wifi/bt chip.
This has been working on Ubuntu elsewhere.
My knowledge does not extend passed installing ROMs so the process to learn this is beyond my grasp. I am happy to donate to developers should this help!!
I would love to do this myself but would not even know where to begin.
I have managed to install the relevant version of android and touchscreen etc works brilliantly, i just need the ability to connect to the internet.
I guess there are two options and some advise would be great:
1 - could i use a usb wifi adaptor that would be supported by Android rather than the built in realtex card.
2 - where should i begin to look or research if i wanted to learn how to modify the install in order to include the correct kernal or support for this version (I am assuming using the working ubuntu drivers in some way). Any recommended reference materials to get me started. I appreciate this option may require quite some time to fully understand android development.
Thanks
ussasx said:
I would love to do this myself but would not even know where to begin.
I have managed to install the relevant version of android and touchscreen etc works brilliantly, i just need the ability to connect to the internet.
I guess there are two options and some advise would be great:
1 - could i use a usb wifi adaptor that would be supported by Android rather than the built in realtex card.
2 - where should i begin to look or research if i wanted to learn how to modify the install in order to include the correct kernal or support for this version (I am assuming using the working ubuntu drivers in some way). Any recommended reference materials to get me started. I appreciate this option may require quite some time to fully understand android development.
Thanks
Click to expand...
Click to collapse
I am still really struggling with this and some help would be massively appreciated :/
For those interested
ussasx said:
I am still really struggling with this and some help would be massively appreciated :/
Click to expand...
Click to collapse
For anyone that is interested in android on the Lenovo yoga 13 check out console os
https://www.kickstarter.com/projects/mmv/console-os-dual-boot-android-remastered-for-the-pc
I am a backer and it looks like it will be funded.
Hello Folks,
I seen a rumor that Android may about to support iOS on its wear platform. Think Moto360 with iPhone.. See This
Since Android shipped about 720,000 device in 2014, compared to 4.6 million wearable devices in 2014 by estimates. See Here
I have been working on developing an application for the Android Wear platform that will allow iOS communication, but there is a well known bug in Android that is preventing connecting to an iOS device. This is despite Android Wear supporting Bluetooth LE GATT profile, and will connect with most other bluetooth devices over Bluetooth LE using the GATT profile. You would think it seems like an iOS issue. When you dive into the communication handshake between the devices when attempting a connection between Android Wear and iOS, you get an error.
This has been reported to Android and since then, not fixes. I understand they have bigger fish to fry than allowing their watches to support iOS, but since their devices are not selling well this may push them into fixing the bug.
See This ... It explains how the bug in android is failing connecting to iOS devices due to their bug..
I did some deep diving and reviewed the code for the BluetoothDevice.java file in the Android Development Studio and found that there is the option to select either Normal Bluetooth or LE via a transport parameter with connecting... BUT... When android implemented their specific code, they OMITTED the transport parameter and it SHOULD connect via LE, but doesn't.
Here is my comment on the above thread (Issue 58896):
Reviewing the android code for BluetoothDevice.java I found that connectGatt() function has a hidden int TRANSPORT variable that will allow you to use AUTO or specific LE or BR/EDR only.
For some reason, this is available in the BluetoothDevice.java file in android studio, but not listed in the android code reference. When you attempt to use this, it gives you an error. If someone can explain how we can fix the compiler on android studio to compile our code using the TRANSPORT_LE option instead of TANSPORT_AUTO which I assume is being used.
I see someone with Broadcom has requested that the transport parameter be added in May 2014 on the android GIT page (https://android.googlesource.com/platform/frameworks/base/+/b88fa82^!/) which is almost 7 months ago. If this is such a seemingly prominent problem and so many fixes since then and this hasn't been fixed??
So this has been reported by Broadcom in May 2014..... and no fix as of yet???
I am curious how MohammadAG bypassed this snafu. Any thoughts?
Here is his proof..
hhttps://www.youtube.com/watch?v=DIIYmVSc9Yw
Hello!
I too am working on such a project and during my studies have successfully connected my android to my iPhone with one extra step: since android can only act as the central and connect to a peripheral, the iPhone has to be put into peripheral mode, for which I used LightBlue (look in the app store). After they connected I was able to discover the GATT service, but I'm new to android and this is a huge project so I'm kinda lost after that. Would you mind sharing your code with me so I can collaborate with you on this? I'd love to release something like this to the XDA community, and if you're closer than I, I'd love to help!
I hope this answer helps you, but I may be completely misunderstanding the question.
Thanks!
Zachal
I'm hoping someone may let me know if it's possible to write a Driver to access the Android Cameras' directly rather than the OEM's or the Camera API?
I'm looking to have an app that can access both Front and Back cameras at the same time for devices that have dual video processors and looking to hire a developer to do "this" if it's possible.
I imagine it would most likely be C++ at the Linux Kernal or HAL level?
I'm not sure if there's anything at that level that would prevent an app from using it's own driver either?
Android 9 now allows for Dual/Multi Camera support but at that higher level, the Camera2 API only works for some devices. Have tried on Galaxy S4, S6 and S9 all running Android 9 and only the S4 worked.
Any information would help me to see if it's worth pursuing and greatly appreciated.
Just wanted to renew this question. Hoping someone can let me know if it's possible to do this?
I have a brand new OP7 from China, with AA international android 10 rom installed.
problem I am having, my employer requires device management through vmware intelligent hub application for device enrollment, and cert installations.
during the setup and enrollment process, I get an error saying failed to create install url, support team has never seen this error before, and I can't find much reference to the issue online.
Any suggestions where to start with this?
Probably compatible issue with android 10.
Try to clean install of 10.0.1. For me at least it solved some apps that didn't worked even in first original android 10 release.
As usual, the solution here is downgrading to android 9, due to providers not being willing to believe there is an issue with their software. I used the rollback package provided for those running Q betas earlier in the year. This put it back to 9.5 and I was able to get the vmware product to work. I will hold off on updating to 10 when they get their head out of their butts.
Note to the vmware developers, your product has been broken on android 10 since the early betas in the spring, but still, you fail to address the problem. Your support is a joke.