-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
a2dp #7
Comments
@GuaiYiHu Thanks u again. Didnt notice that. Btw, how u made camera works. Currently we have a lot of issues such as Nfc, camera, mac adress for bt and wifi. And all of them I can fix (at least I think so), but cant figure out how u made camera for virgo. iirc virgo has imx214 right? |
you can flash virgo's lineage-15.1 to cancro directly to see if camera works on it? They share the same blobs. |
ohhhh thats true |
I shall bring up cm-14.1 with the new kernel source and new blobs for cancro, for easier bringing up for lineage-15.1. |
@GuaiYiHu what do u think about common repo? I mean common-8974-xiaomi or smthng like that. IIRC Virgo = Mi 4 with diff display, right? Even IR blaster is present and IMX 214 sensor too |
Sounds good and I am rewriting the device tree for Virgo. |
we (me and Shivam) will join after fixed camera stuff at cancro. Can u remind me about RIL in virgo? Is that compatible with cancro? Check this maybe I missed smthng Right now I think we have those diffs: |
IR no yes no |
What I am doing is trying to make the commit look cleaner on virgo. XD |
we can remove it in device_check.sh
Pfff I think that we can adjust it too
Yeah I know it, but I think that would be a better use common repo We will try change virgo tree for cancro, dont think that will be hard. |
Just refer to this, this is cleaner than it was before. |
@GuaiYiHu yeah i saw it thanks u |
12-26 17:48:38.491 1115 1115 E a2dp_vendor_aptx_hd_encoder: A2DP_VendorLoadEncoderAptxHd: cannot open aptX-HD encoder library libaptXHD_encoder.so: dlopen failed: library "libaptXHD_encoder.so" not found
rename it too?
cancrodevs/proprietary_vendor_xiaomi@995248f#diff-192a947a2f5c7f30206d1682708c6fc9R499
The text was updated successfully, but these errors were encountered: