Just an observation I made when installing custom ROMs on my V30 is that anything Android 10 seems to break Android Auto. Seems to work fine on most Android 9 custom ROMs and Stock ROMs, but appears to be broken as of 10. I was wondering if there is anyway to fix it? (I'm talking about the USB tether to car radio). Willing to help in anyway possible!
Which 10 ROM you used and which you preferred? Did you try wireless Android Auto?
I have used Lineage OS 17.1 and Havoc OS 3.2 - I prefer HavocOS. The phone recognises the headunit however nothing appears on the screen. My headunit doesn't support wireless AA.
Related
Hey folks,
I have a couple of questions, if you'd be so kind.
Firstly, upon updating to Android 6.1, will my USB tethering still be available (I am on Three, with 30gb of tetherable data)? I had previously updated my tablet to 6.1, only to find my USB tethering became disabled, and had to revert back -- I even tried all the fixes.
Secondly, will Android stock ROMs work on this device? Specifically the latest one.
Edit: and by stock I mean the Google Android ROMs found on Nexus devices.
Thank yee kindly.
shrooom said:
Hey folks,
I have a couple of questions, if you'd be so kind.
Firstly, upon updating to Android 6.1, will my USB tethering still be available (I am on Three, with 30gb of tetherable data)? I had previously updated my tablet to 6.1, only to find my USB tethering became disabled, and had to revert back -- I even tried all the fixes.
Secondly, will Android stock ROMs work on this device? Specifically the latest one.
Edit: and by stock I mean the Google Android ROMs found on Nexus devices.
Thank yee kindly.
Click to expand...
Click to collapse
What model do you have?
Moto E 4G 2nd Generation.
shrooom said:
Hey folks,
I have a couple of questions, if you'd be so kind.
Firstly, upon updating to Android 6.1, will my USB tethering still be available (I am on Three, with 30gb of tetherable data)? I had previously updated my tablet to 6.1, only to find my USB tethering became disabled, and had to revert back -- I even tried all the fixes.
Secondly, will Android stock ROMs work on this device? Specifically the latest one.
Edit: and by stock I mean the Google Android ROMs found on Nexus devices.
Thank yee kindly.
Click to expand...
Click to collapse
Each device has a it's own ROMs. You cannot flash a ROM of another device. Doing so will brick your device. And therefore you cannot use ROMs of any other device on your moto e 2015.
But you can definitely try other ROMs that give stock experience.
So i've installed this custom os [ROM] [N6F26Q] AOSP Nougat (12 Jan 2017) on my Galaxy s2 plus, and then my DSLR camera connection stopped working (OTG), but the os says it should be compatible with OTG, i'm not sure the DSLR has anything with OTG to do tho?. Now i have googled around and found files neccessary for it to work, installed them and USB Host Controller detected them, still not recognising the camera.
So is there a way to install what's "neccessary" from the original stock firmware into some kind of kernal or "added function" via Custom Recovery or perhaps Odin?
Thanks to anyone that can potentially help to solve this!
This is something you give up when you use aosp. The otg works only if they use the open source version which most do not.
With aosp only the very basic functions will work.
Any custom rom for s2 plus that it works on if you know?
If anyone else have the same issue, it was never a problem with the os, i've tried it on several custom Os aslong as your phone is OTG compatible it works, it seems.
Buy a new OTG Cable and it will work again, or rather say buy the adapter version of it, better then the ****ty cable version that i bought, that broke out of thin air.
Does anybody know if any combination of A11 custom ROM and Gapps work in a way, that Android auto is recognized by cars head unit when you connect the phone?
Last time my phone was recognized as Android auto compatible was on LOS17 and OpenGapps, but I have no luck with any A11 custom ROM and any Gapps (Open, Nick, ...) I try.
primozho said:
Does anybody know if any combination of A11 custom ROM and Gapps work in a way, that Android auto is recognized by cars head unit when you connect the phone?
Last time my phone was recognized as Android auto compatible was on LOS17 and OpenGapps, but I have no luck with any A11 custom ROM and any Gapps (Open, Nick, ...) I try.
Click to expand...
Click to collapse
try Pixel Experience 11/ 11Plus Stable.. Android Auto is preloaded in settings so it should work flawlessly.
Android auto on Fluid OS is working good. Awaken OS also works fine with nikgapps full, previously I've tried with nikgapps basic and it doesn't work.
Hi,
I would like to connect my V30+ to a hearing aid. The current android version of my phone is 9 and therefore seems that my only option of reaching this goal is by an unofficial android 10 ROM.
Is there a ROM offering this goal?
Dear All,
I am using Color OS 13.0 official version and I installed the Android Auto app but when I plugged wire in to my car it said as the pictures and it doesn't work even I choose File Transfer / Android Auto or anything else.
How can I fix it???
There are two solutions.
One is to root your phone and make Android Auto an native app. I don't have the details but you can google and find it.
The other one is to flash Oxygen OS.
thank you @peteve
Finally I came back to Google Pixel ;P