Hi!
Been trying to get aptx working over Bluetooth. I have 2 devices, one that is officially aptx certified, and one that is generic Chinese brand but works with aptx anyway. I tried both the Rayglobe module and the Oreo aptx module in the magisk repo. Neither of them work for me and I can see both in MatLog, and in settings that it's dropping back to SBC every time. Have tried android 7.1.1,android 8.1,and GSIs on my device.
Both of my aptx devices work fine on several other phones including my now sold OnePlus 5
Any ideas what to do?
I'm on a 3 branded phone, but same happens if I use the global image
The Razer phone doesn't have the licensing to use apt-x unfortunately so it won't work on it.
Roxas598 said:
The Razer phone doesn't have the licensing to use apt-x unfortunately so it won't work on it.
Click to expand...
Click to collapse
Neither did oneplus originally but the magisk module worked. Doesn't explain why it won't work on this phone, even when all the files are there unless razer are going out of their way to stop you using it even with the correct files there. Before oneplus was licenced, you could add unofficial support yourself.
Example that worked on my OP and not razer: https://forum.xda-developers.com/apps/magisk/port-aptx-aptxhd-oreo-8-0-update-jan-t3731151
Related
HI Guys,
Looking for some help.
I have an HTC U11 on Oreo. Recently installed a Kenwood 7704S Android Auto HU.
Installed Android Auto app via google play, as well as latest version direct from Google. Phone is just not detected using the original USB C cable BUT the phone is charging, all other functions work via the Android Auto app without being cable connected. Short of instalkling older AA apk versions I am at a loss. I have tested unit with a iphone and Apple Car Play launches fine so it is not a a HU issue as I assumed. I had used this unit with a P10 Plus and it worked but I had intermittent issue with it as well but with the U11 it has just quit launching all together. I have reset phone to factory and tried fresh, no success. I have enabled Developer mode and enable USB debugging and selected MTP Protocol still no luck.
Anyone experience U11 Android auto issues, super frustrating and dont want to run a custom rom just yet. Suggestions welcome cause I am at wits end beside trying other AA versions from earlier dates or rolling back to Nougat, that I have not yet tried. Phone has worked on Oreo and I got it with Oreo but I was experience intermitent connectivity
I know Google dropped Miracast awhile ago, but I really really need it. Chromecast just isn't cutting it. Via build.prop (additions below), I've been able to see the Miracast device but it won't connect. Occasionally I'll even see my homescreen pop up, but it will immediately disconnect. I remember having this problem with an HTC 10 and it had to do with the wifi setting being in battery saver mode. I'm currently unlocked with Magisk on 8.1.0.
Has anyone been successful in getting Miracast to work??
build.prop modifications:
persist.debug.wfd.enable=1
wlan.wfd.hdcp=disable
persist.sys.wfd.virtual=1
I've not heard anyone getting it to work on the Pixel XL 2. Other than I saw this post in the Nitrogen thread here
Just use All Cast. You will need to pay for it, I think it's like $5, but I've been using it for years. Works great and with Chromecast and pretty much anything that allows DLNA. I cast to two TV's, my Nexus Player, XBOX, etc. using it.
gettinwicked said:
Just use All Cast. You will need to pay for it, I think it's like $5, but I've been using it for years. Works great and with Chromecast and pretty much anything that allows DLNA. I cast to two TV's, my Nexus Player, XBOX, etc. using it.
Click to expand...
Click to collapse
Unfortunately I need to it mirror my screen, not just play media. Thanks though!
Hi folk, please I need mirror my Pixel 2 XL on TVs for my job. I've Chromecast ultra but it doesn't work with P2XL (it seems some technical issue made by 8.1.0) in the meanwhile I'm waiting for fix by big G do you know if All cast can do this job?
last_nooby said:
Hi folk, please I need mirror my Pixel 2 XL on TVs for my job. I've Chromecast ultra but it doesn't work with P2XL (it seems some technical issue made by 8.1.0) in the meanwhile I'm waiting for fix by big G do you know if All cast can do this job?
Click to expand...
Click to collapse
This might sound nuts, but is that Chromecast Ultra using a wired network connection? I have no idea the cause but i've had issues with some devices (a samsung tablet for example) connecting to the Chromecast Ultra when it was plugged into the wired connection, often just insta dropping, but it worked flawless when they both were using wireless. Other devices like a Nexus 6p connected perfectly in both network configurations.
Any idea which custom ROMs support Miracast besides Nitrogen OS Oreo? I really need the screen mirroring ability to a windows 10 laptop.
Hi, as the title says, had a question about using GSI's now that treble is available for our phone. I understand that in order to use treble, we must first flash the newest build of Lineage, and then install a GSI. My question is, if Lineage is installed, does it somehow serve as a base that the GSI installs over, or is installing it only pertinent for updating the partition layout? I guess more specifically, if I install the new Lineage, and then flash a GSI over it, will I experience the same bugs in Lineage in any potential GSI installed?
In my case, it's with android auto, since it doesn't seem to work/project over USB with any car I've tested on any of the currently available ROMs. The app works in Lineage, and the phone can connect via Bluetooth to a car, but it doesn't recognize that it's physically connected to a car at all via USB, so it fails to project to the vehicle's display, meaning I need to constantly look down to where it's plugged in at to interact with it instead of through the vehicles built in touch screen, keeps me going back to stock honestly because it's a feature I need access to.
If I install a GSI where auto is properly working, should it work for me as well or no because Lineage doesn't support it currently and that was flashed before the GSI was?
Thanks
davehasninjas said:
Hi, as the title says, had a question about using GSI's now that treble is available for our phone. I understand that in order to use treble, we must first flash the newest build of Lineage, and then install a GSI. My question is, if Lineage is installed, does it somehow serve as a base that the GSI installs over, or is installing it only pertinent for updating the partition layout? I guess more specifically, if I install the new Lineage, and then flash a GSI over it, will I experience the same bugs in Lineage in any potential GSI installed?
In my case, it's with android auto, since it doesn't seem to work/project over USB with any car I've tested on any of the currently available ROMs. The app works in Lineage, and the phone can connect via Bluetooth to a car, but it doesn't recognize that it's physically connected to a car at all via USB, so it fails to project to the vehicle's display, meaning I need to constantly look down to where it's plugged in at to interact with it instead of through the vehicles built in touch screen, keeps me going back to stock honestly because it's a feature I need access to.
If I install a GSI where auto is properly working, should it work for me as well or no because Lineage doesn't support it currently and that was flashed before the GSI was?
Thanks
Click to expand...
Click to collapse
I think that is kernel side as our HDCP goes to the greybus instead of USB-C for the projector mod. I know through wireless it works. Tried it on my friend's 2016 Hyundai Santa Fe.
GSI's will have the same bugs via vendor and boot. Also, unless the GSI supports moto mods, those won't work either.
Uzephi said:
I think that is kernel side as our HDCP goes to the greybus instead of USB-C for the projector mod. I know through wireless it works. Tried it on my friend's 2016 Hyundai Santa Fe.
GSI's will have the same bugs via vendor and boot. Also, unless the GSI supports moto mods, those won't work either.
Click to expand...
Click to collapse
Oh, I didn't think motomods had anything to do with android auto. It doesn't use the pins on the back or anything, just usb, but I can't project via USB, it just brings up the USB select menu (charge, mtp, ptp) and neither of my cars support wireless android auto. I didn't think there were any cars out yet that actually support wireless android auto.
Oh well, guess stock it is for now, thanks for the info.
Edit:
@Uzephi hey, sorry to be a bother, you said you were able to use wireless android auto on a friend's vehicle. I'm assuming that means it's enabled on custom ROMs since it doesn't appear to be on stock. Do you happen to think a mod like this would work?
https://forum.xda-developers.com/ge...droid-3-0-proxy-gateway-android-auto-t3813163
Just curious, because if I could use wireless projection for it that would work just as well to me.
davehasninjas said:
Oh, I didn't think motomods had anything to do with android auto. It doesn't use the pins on the back or anything, just usb, but I can't project via USB, it just brings up the USB select menu (charge, mtp, ptp) and neither of my cars support wireless android auto. I didn't think there were any cars out yet that actually support wireless android auto.
Oh well, guess stock it is for now, thanks for the info.
Edit:
@Uzephi hey, sorry to be a bother, you said you were able to use wireless android auto on a friend's vehicle. I'm assuming that means it's enabled on custom ROMs since it doesn't appear to be on stock. Do you happen to think a mod like this would work?
https://forum.xda-developers.com/ge...droid-3-0-proxy-gateway-android-auto-t3813163
Just curious, because if I could use wireless projection for it that would work just as well to me.
Click to expand...
Click to collapse
Android Auto uses video over USB. Our ancillary video output is rerouted to the greybus for the projector. Only way to get SElinux to work correctly on aosp was to keep that routing and nix USB video.
I honestly don't know. I did it for kicks to see if his Android Auto app on his Santa Fe would Sync with my phone and it did. It wasn't any projection, it was just the two apps talking to each other. Is that how yours is or is your phone running android auto and the radio is taking the phone's screen as a projection? Because I could be wrong. That is the only thing I could think of why yours wouldn't work.
Uzephi said:
Android Auto uses video over USB. Our ancillary video output is rerouted to the greybus for the projector. Only way to get SElinux to work correctly on aosp was to keep that routing and nix USB video.
I honestly don't know. I did it for kicks to see if his Android Auto app on his Santa Fe would Sync with my phone and it did. It wasn't any projection, it was just the two apps talking to each other. Is that how yours is or is your phone running android auto and the radio is taking the phone's screen as a projection? Because I could be wrong. That is the only thing I could think of why yours wouldn't work.
Click to expand...
Click to collapse
Ahh gotcha, that makes more sense now.
I can pair the device to the vehicle over bluetooth and use the android auto app that way to play music and stuff, but yeah, normally it takes the phone's screen as projection, so I can use the car's 7in display for android auto without having to play around with my phone. Understanding that video over USB is disabled makes sense as to why auto isn't working. I'm guessing this means it won't work on custom ROMs without a custom kernel, and that would have to disable SELinux and reroute video to USB, correct?
Thanks for all the info, always good to learn something.
davehasninjas said:
Ahh gotcha, that makes more sense now.
I can pair the device to the vehicle over bluetooth and use the android auto app that way to play music and stuff, but yeah, normally it takes the phone's screen as projection, so I can use the car's 7in display for android auto without having to play around with my phone. Understanding that video over USB is disabled makes sense as to why auto isn't working. I'm guessing this means it won't work on custom ROMs without a custom kernel, and that would have to disable SELinux and reroute video to USB, correct?
Thanks for all the info, always good to learn something.
Click to expand...
Click to collapse
Yes that is correct. The Z2 development crew tried but the workaround would have been messy and not true SElinux enforcing which makes me wonder about stock rom tbh.
Hi all,
Today out of curiosity I tried to use the Cast feature on my Nokia together with the Connect app in Windows 10. The phone manages to find the PC and tries to connect, then the PC sees the request and tries to accept it, however, it ends with an error saying "Something went wrong with the projection." The Connect app on the PC is version 10.0.17134.1 as seen in the picture. My phone is running Android Pie on the October patch. I was wondering if anyone has managed to successfully cast their screen to Win 10 PC and if so which versions of Android and the Connect app do you guys have?
intervall said:
Hi all,
Today out of curiosity I tried to use the Cast feature on my Nokia together with the Connect app in Windows 10. The phone manages to find the PC and tries to connect, then the PC sees the request and tries to accept it, however, it ends with an error saying "Something went wrong with the projection." The Connect app on the PC is version 10.0.17134.1 as seen in the picture. My phone is running Android Pie on the October patch. I was wondering if anyone has managed to successfully cast their screen to Win 10 PC and if so which versions of Android and the Connect app do you guys have?
Click to expand...
Click to collapse
Same here, I've also tried with a Samsung TV (KU6000). The phone finds the TV and tries to connect, then TV says connecting to phone for a few seconds and that's it. Nothing happens.
akhilkalwakurthy said:
Same here, I've also tried with a Samsung TV (KU6000). The phone finds the TV and tries to connect, then TV says connecting to phone for a few seconds and that's it. Nothing happens.
Click to expand...
Click to collapse
Are you also running Android Pie?
intervall said:
Are you also running Android Pie?
Click to expand...
Click to collapse
Yes, I'm running Android Pie. Never tried on Oreo. But, it's not Nokia/HMD global issue though, Google dropped it since Android 6. It's a problem with Nokias, Pixels and other Android one devices. You can check here. You can also Google for Miracast on Android one devices.
akhilkalwakurthy said:
Yes, I'm running Android Pie. Never tried on Oreo. But, it's not Nokia/HMD global issue though, Google dropped it since Android 6. It's a problem with Nokias, Pixels and other Android one devices. You can check here. You can also Google for Miracast on Android one devices.
Click to expand...
Click to collapse
Okay, I didn't expect that. However, if Miracast is dropped, what exactly does the Cast option support then? It does not make sense for the option to be there if it simply does not work.
intervall said:
Okay, I didn't expect that. However, if Miracast is dropped, what exactly does the Cast option support then? It does not make sense for the option to be there if it simply does not work.
Click to expand...
Click to collapse
The cast option is for use with Google's Chromecast, Android TV, or Google Home. It uses a proprietary protocol, so it is only possible to cast to Google products.
intervall said:
Okay, I didn't expect that. However, if Miracast is dropped, what exactly does the Cast option support then? It does not make sense for the option to be there if it simply does not work.
Click to expand...
Click to collapse
Don't know. What's more interesting is that Nokia devices are Miracast certified (see this). But, there's no mention of variants, only like base models are mentioned.
akhilkalwakurthy said:
Don't know. What's more interesting is that Nokia devices are Miracast certified (see this). But, there's no mention of variants, only like base models are mentioned.
Click to expand...
Click to collapse
Actually, I can only see older models in the link you posted. Nokia 6.1 is not listed. :/
Hi,
I received today my phone, I updated to Android Pie, and now I see that I cannot discover my TV which supports miracast. I also tried to switch off Wlan.
Of course I considered downgrading to Android Oreo, but I read it's a bit troublesome (dual sim stops working when downgrading).
By the way I'm asking to xioami forums too (I cannot post external link), but I don't think I can expect a fast fix
Any idea? Thanks.