Hello, i havent found a similiar thread so...
We bought an Opel Adam Rocks (2014) in which there is the really nice Intellilink System. Its said it will connect with all newer Android phones that installed Android Auto, but when i plug it via USB (tried different cables already) it says "Unknown/unsupported device detected".
My phone: Oppo Find 7 is ROOTED, on latest OmniROM which is of course Android 6.XXX + Android Auto App
My question: is it GENERALLY impossible to connect rooted/Custom ROM phones to it? is there anyone that was successful?
Its not a disaster since we didn't see it as important but it surely would be nice!
Thanks.
majo334 said:
Hello, i havent found a similiar thread so...
We bought an Opel Adam Rocks (2014) in which there is the really nice Intellilink System. Its said it will connect with all newer Android phones that installed Android Auto, but when i plug it via USB (tried different cables already) it says "Unknown/unsupported device detected".
My phone: Oppo Find 7 is ROOTED, on latest OmniROM which is of course Android 6.XXX + Android Auto App
My question: is it GENERALLY impossible to connect rooted/Custom ROM phones to it? is there anyone that was successful?
Its not a disaster since we didn't see it as important but it surely would be nice!
Thanks.
Click to expand...
Click to collapse
I have similar problem at the moment with Huawei Mate 9 and intellilink R4.0 (both new). I am waiting for new firmware and will contact Opel dealer for update.
I have read different forums that different firmware on phone acts different as well as software on head unit sometimes makes problems.
Generally I have read that also some custom roms work and some don´t.
Also there have been several updates for the intellilink systems since 2014. This will cost some € at Opel Dealer. It is not for sure this helps! Maybe it is waste of money.
In this case it is google bringing the disaster... The app brings no information what is going wrong...
i'm thinking about an update for the Intellilink, indeed... and... at least its good to hear that custom ROMs CAN work, so there is still chance. thanks for the info!
Related
I have a stock, unrooted Galaxy Nexus GSM purchased new from Google currently running 4.3.
I have a FitBit Flex which will only sync with phones that have Bluetooth Low Energy support.
I can not find any information on any of the KitKat ROMs out there for Galaxy Nexus to see if I install it, will Bluetooth LE work?
If it does then work, my next concern would be if the FitBit app would recognize that the Bluetooth LE works and it would then be able to sync, or if it simply would still see it as a Galaxy Nexus which they do not list as a supported device: http://www.fitbit.com/devices
If anyone can offer me some advice here, I'd greatly apprecaite it!
Thanks.
(btw, sorry if this is in the wrong froum. please move it if it is)
adamwsh said:
I have a stock, unrooted Galaxy Nexus GSM purchased new from Google currently running 4.3.
I have a FitBit Flex which will only sync with phones that have Bluetooth Low Energy support.
I can not find any information on any of the KitKat ROMs out there for Galaxy Nexus to see if I install it, will Bluetooth LE work?
If it does then work, my next concern would be if the FitBit app would recognize that the Bluetooth LE works and it would then be able to sync, or if it simply would still see it as a Galaxy Nexus which they do not list as a supported device: http://www.fitbit.com/devices
If anyone can offer me some advice here, I'd greatly apprecaite it!
Thanks.
(btw, sorry if this is in the wrong froum. please move it if it is)
Click to expand...
Click to collapse
See here.
http://forum.xda-developers.com/showthread.php?t=2492436
With any kitkat rom I install only the modified apk from that thread and everything is ok!
Il you wanna stay with 4.3 you must install btle libraries as mentioned in the thread.
Gnex supports BLE with almost every KK rom.
(try BLE Checker on play store: on my Vanir says Supported!)
yes, and wrong place to ask this
caluz78 said:
See here.
http://forum.xda-developers.com/showthread.php?t=2492436
With any kitkat rom I install only the modified apk from that thread and everything is ok!
Il you wanna stay with 4.3 you must install btle libraries as mentioned in the thread.
Click to expand...
Click to collapse
THANK YOU, THANK YOU, THANK YOU!
I used The Nexus Root Toolkit (by WugFresh) to Unolock and Root my GNex. Then I used the link you gave me to get the BTLE files and the FitBit apk. I installed everything and it freakin' works!!! I'm so happy!
I'm so annoyed at Google for letting support of this device go after only 18 months. I bought it because they praised it as being thee flagship, unaltered, always up-to-date phone to have. I figured I'd be on the latest version of Android with this phone for many years. I wanted to keep it stock, but they've forced me to now go rooted. I suppose I could now flash a KK ROM, but I'm not sure what that would benefit me at this point.
Thank you again SO much for your help and fast reply! (Even if I did post this in the wrong place!)
Love XDA!
Ok, so I have to update what happened. Everything seemed to be working fine until I got into my car. My GPS has a bluetooth connection. It would connected, but then almost immediately the Bluetooth service would crash on my phone. Happened over and over again. Even after a reboot. Then when I got home, I tried it with my bluetooth speaker. Same exact thing. I figure the bluetooth binaries that I installed screwed up my connections that used to work. I even tried re-pairing them. Didn't help.
I gave up and decided to wipe everything and flash KK. I used CM11 nightly. Now everything, so far, is working as expected. GPS, speaker & fitbit. CM KK takes some getting used to over stock JB. I don't know what changes are KK and which are CM.
Hi everyone, first time poster, please be gentle...
I have recently brought a chinese smartphone, mainly as a bit of a folly to see what they are like. I have brought the Star C1000 also known as the Sesonn C1000, Kingelon C1000, HDC White Walker, Vifocal C1000, Lenteen C1000, Goophone M3 and many other names. It is 5.5 inch with fingerprint scanner.
I want to flash the rom and put either a fresh android 4.4 on there or another trusted mod e.g. cyangenmod but i'm having some trouble as I can't seem to find the necessary ROM for this phone in order to do this. Add to this non of the apps that automate some or all of this i.e. Rom Manager won't recognise the device in order to provide rom's and back up facility and when I tried the automated cyangenmod auto installation, again would recognise the phone and continue with the installation...
So could anyone give me some guidance and advice on this,
P.s. Phone is already rooted as its loaded with their custom rom which says the version is android 5.5, so unless this phone is from the future...
Thanks
Matt
Hello,
First, i dont think that there is any CM Rom for your device.
Second, check every other device with the same Hardware as your device, for one with 4.4 Android.
If you find something, a little Modifikation of the update binary should do the job
Sent from my HTC One using XDA Free mobile app
Thanks for your reply, that sounds a little too technical for me I think,
Now the reason I want to do this is because it has come with its own rom installed claiming its android 5.5 and that its a sony m880 when it obviously isnt....does anybody know anything about this...
Heve you found any ROM for the C1000?
I recently loaded CM12 on my LG G3 D850 (only variant without Android 6 )
Everything went well until I tried pairing my SW3 via NFC via Wear, not only does it not recognize it, it makes the harp noise of nfc contact but does nothing and then stays on a very bright stock firmware that never goes off...very silly ..so I have to shut it off everytime
Already frustrated that Android 6 wasnt available at the end of three frustrating days of my first attempt at a ROM, now I am ready to switch back to (yucccckkk!!) stock if no solution is available.
I also upgraded my gApps to stock from mini (and that wiped out a whole buncha stuff but thats another story) and tried software update (but CM has its own updater which said nothing to update)
Would appreciate any ideas from the experts here, thanks in advance !
The NFC on the SW3 currently only transmits a URL to the "Android Wear" app. in PlayStore.
ranf said:
The NFC on the SW3 currently only transmits a URL to the "Android Wear" app. in PlayStore.
Click to expand...
Click to collapse
I didnt get you; even with that functionality in NFC, the SW3 connects without an issue with stock firmware but not with CyanogenMod - any reason for this ?
Did you factory-reset the watch after flashing CM on the phone? You need to (AFAIK).
It works for me CM11 + SW3
Working here too with cm 12.1
rojaxda said:
I recently loaded CM12 on my LG G3 D850 (only variant without Android 6 )
Everything went well until I tried pairing my SW3 via NFC via Wear, not only does it not recognize it, it makes the harp noise of nfc contact but does nothing and then stays on a very bright stock firmware that never goes off...very silly ..so I have to shut it off everytime
Already frustrated that Android 6 wasnt available at the end of three frustrating days of my first attempt at a ROM, now I am ready to switch back to (yucccckkk!!) stock if no solution is available.
I also upgraded my gApps to stock from mini (and that wiped out a whole buncha stuff but thats another story) and tried software update (but CM has its own updater which said nothing to update)
Would appreciate any ideas from the experts here, thanks in advance !
Click to expand...
Click to collapse
I'm not entirely sure what you mean: NFC doesn't do much, definitely can't use it to pair the device; which device has a "very bright stock firmware?"
Did you factory reset the watch and set it back up with the new phone rom?
gtriamy said:
I'm not entirely sure what you mean: NFC doesn't do much, definitely can't use it to pair the device; which device has a "very bright stock firmware?"
Did you factory reset the watch and set it back up with the new phone rom?
Click to expand...
Click to collapse
Haah...that was a tongue of the slip..what I meant to say was the stock firmware on the watch was very bright and annoying
Anyway I switched to a nightly CM12 and all was well. Thanks for responding ! Now just waiting for CM13 for the D850
rojaxda said:
Haah...that was a tongue of the slip..what I meant to say was the stock firmware on the watch was very bright and annoying
Anyway I switched to a nightly CM12 and all was well. Thanks for responding ! Now just waiting for CM13 for the D850
Click to expand...
Click to collapse
OP
Are you waiting on Official CM13? There are much better alternatives to be had for the D850, and if your insistent on CM, Unofficial CM13 has been out for sometime.
oogsaggie said:
OP
Are you waiting on Official CM13? There are much better alternatives to be had for the D850, and if your insistent on CM, Unofficial CM13 has been out for sometime.
Click to expand...
Click to collapse
not at all...so what are the alternatives ??
http://forum.xda-developers.com/att...ficial-d850-resurrection-remix-5-0-1-t2978808
http://forum.xda-developers.com/att-lg-g3/development/rom-orionlp-rom-lg-g3-d850-t3173254
Never used Orion, but used the RRemix MM Rom up until today on my D851. I assume it would be as reliable on the 850. I suspect you are only looking in "Original Development" instead of simply "Android Development" in the ATT G3 forums. Enjoy friend.
cm11 + sw3
QBANIN said:
It works for me CM11 + SW3
Click to expand...
Click to collapse
hi there,
can u tell me how
cause my phone is already have CM11 but can't sync with my SW3 :crying:
or did i must rooting my SW3 too?
pulpen said:
hi there,
can u tell me how
cause my phone is already have CM11 but can't sync with my SW3 :crying:
or did i must rooting my SW3 too?
Click to expand...
Click to collapse
Nothing special. Just installed Android Wear app and factory reset SW3.
Hello, I bought a Winca S170 head unit and I would like to know if there are custom ROMS or at least any updates for this device. My HU is already rooted.
D4rk_Seraph said:
Hello, I bought a Winca S170 head unit and I would like to know if there are custom ROMS or at least any updates for this device. My HU is already rooted.
Click to expand...
Click to collapse
You should look for it on a roadnav.com forums.
Kotix builds custom ROMs and UI for winca devices.
Tux2609 said:
You should look for it on a roadnav.com forums.
Kotix builds custom ROMs and UI for winca devices.
Click to expand...
Click to collapse
Hi ,I have the same issue. unfortunately roadnav.com only supports RN units that is made by them and Winca roms can not be found there.
We do not know how we can find original and updated roms for our units.
could any one help us?
It is really annoying!:crying:
arian141 said:
Hi ,I have the same issue. unfortunately roadnav.com only supports RN units that is made by them and Winca roms can not be found there.
We do not know how we can find original and updated roms for our units.
could any one help us?
It is really annoying!:crying:
Click to expand...
Click to collapse
I had winca s100 HU before and I always used firmware from roadnav. S series devices have compatible ROMs with the ones on roadnav forums. I might be wrong regarding new versions but I doubt it.
You should ask someone there, either Leigh or Kotix should know much more than I do.
Tux2609 said:
I had winca s100 HU before and I always used firmware from roadnav. S series devices have compatible ROMs with the ones on roadnav forums. I might be wrong regarding new versions but I doubt it.
You should ask someone there, either Leigh or Kotix should know much more than I do.
Click to expand...
Click to collapse
I Asked both of them today and unfortunately they do not have any experience about winca s170!
Tux2609 said:
You should look for it on a roadnav.com forums.
Kotix builds custom ROMs and UI for winca devices.
Click to expand...
Click to collapse
Unfortunately Roadnav forums do not have ROMS for S170 at the moment, only S160 and earlier. I need to reflash my S170 cause the digital TV shows no image, only audio, and this problem started after an debrick made by an technician and I dont have time (nor patience) to go back to him to correct the problem.
I'm wondering here if GTX ROM could be compatible with S170, cause it uses Intel Sofia 3gr like Joying HUs and I'm using the Joying Extra Tools app with no problem.
Has anyone managed to get Android Auto to connect to their vehicle on their whyred?
I bought a new car last week and have been unable to get it to connect. Meanwhile my friends Blackberry KeyOne and iPhone both activated AA/Carplay immediately like they were supposed to.
I'm running Lineage 17.1 latest build, but I did see folks were having trouble with it a couple years ago. I was just hoping the situation had improved since then. I just updated the fw files from the Xiaomi firmware project and will try it again, but sadly I'm not hopeful.
If it does work for some of you, what rom are you using?
Thanks!
mik101 said:
Has anyone managed to get Android Auto to connect to their vehicle on their whyred?
I bought a new car last week and have been unable to get it to connect. Meanwhile my friends Blackberry KeyOne and iPhone both activated AA/Carplay immediately like they were supposed to.
I'm running Lineage 17.1 latest build, but I did see folks were having trouble with it a couple years ago. I was just hoping the situation had improved since then. I just updated the fw files from the Xiaomi firmware project and will try it again, but sadly I'm not hopeful.
If it does work for some of you, what rom are you using?
Thanks!
Click to expand...
Click to collapse
Problems with GAPPS I guess. Update both, car HUR and phone (gapps, Androidauto, play store,etc).
It's suppose to work normaly.. you can test it with MIUI ROM. You will need to delete LOS anyway if you wanna update FW the correct way (latest Fastboot MIUI ROM using PC).
Good luck and stay safe.
P.S.: I don't use gapps, to much troubles, and not privacy friendly and battery/data eater.
drnightshadow said:
Problems with GAPPS I guess. Update both, car HUR and phone (gapps, Androidauto, play store,etc).
It's suppose to work normaly.. you can test it with MIUI ROM. You will need to delete LOS anyway if you wanna update FW the correct way (latest Fastboot MIUI ROM using PC).
Good luck and stay safe.
P.S.: I don't use gapps, to much troubles, and not privacy friendly and battery/data eater.
Click to expand...
Click to collapse
What is the vendor security date of your device? (Unless its newer than Nov 1 2018 I'm already running the newest available vendor update and firmware.) The xiaomi firmware project updates the exact same files that the MIUI builds would.
Latest open gapps, android auto, etc are all installed. Headunit is updated to the latest version of Entune 3.0. The problem isn't the head unit. It's the phone. Old reports on here suggest it never worked with MIUI either. I was just curious if anyone has tried recently to see if the situation changed. I have zero desire to run that mess that is MIUI. It was bad enough using it long enough to get my bootloader unlock key. When you plug in the device you're presented with a menu on LOS that doesn't exist on other devices. (File Transfer, PTP, MIDI, Do Nothing). None of them do anything, so it appears that the MTP built into lineage doesn't know what to do with the connection.
mik101 said:
What is the vendor security date of your device? (Unless its newer than Nov 1 2018 I'm already running the newest available vendor update and firmware.) The xiaomi firmware project updates the exact same files that the MIUI builds would.
Latest open gapps, android auto, etc are all installed. Headunit is updated to the latest version of Entune 3.0. The problem isn't the head unit. It's the phone. Old reports on here suggest it never worked with MIUI either. I was just curious if anyone has tried recently to see if the situation changed. I have zero desire to run that mess that is MIUI. It was bad enough using it long enough to get my bootloader unlock key. When you plug in the device you're presented with a menu on LOS that doesn't exist on other devices. (File Transfer, PTP, MIDI, Do Nothing). None of them do anything, so it appears that the MTP built into lineage doesn't know what to do with the connection.
Click to expand...
Click to collapse
It's not LOS fault, it's car HUR or GAPPS(androidauto,..) fault.
Something is wrong in communication. I have 2nd device with LOS + GAPPS and all is working in my car HUR.
God luck and stay safe!
drnightshadow said:
It's not LOS fault, it's car HUR or GAPPS(androidauto,..) fault.
Something is wrong in communication. I have 2nd device with LOS + GAPPS and all is working in my car HUR.
God luck and stay safe!
Click to expand...
Click to collapse
You're leaving out a lot of necessary information, like your build of gapps and what your second device actually is. I have no doubt LOS works fine with Android auto on other devices, but I have yet to see any proof of it working on any whyred anywhere. You're just making assumptions and jumping to defend LOS without any proof whatsoever. You're ignoring the part where every post regarding AA on whyred posted on this forum in the past refers to it not working. It may not be LOS' fault in particular but it very well could be the device firmware never working with AA at all.
mik101 said:
You're leaving out a lot of necessary information, like your build of gapps and what your second device actually is. I have no doubt LOS works fine with Android auto on other devices, but I have yet to see any proof of it working on any whyred anywhere. You're just making assumptions and jumping to defend LOS without any proof whatsoever. You're ignoring the part where every post regarding AA on whyred posted on this forum in the past refers to it not working. It may not be LOS' fault in particular but it very well could be the device firmware never working with AA at all.
Click to expand...
Click to collapse
Ok ok I have 2 whyred devices(2nd has smashed screen, i leave it connected in car)...hope that makes sense now
Let me simplified this... whyred and android auto is working! Yeah you need to hasel a bit but its working, at least in my Nissan OEM HUR from 2019. You just need to find right GAPPS version. I think its from feb. 2020, anythig newer breaks androidauto. Than just freeze all google stuff or it will update and breaks again. I cant remember all details couse it's too long ago I did it. Sorry, but you'll need to experiment by yourself.
Ahh almost forget...my FW is 10.0.3 I think. Not the latest.
Good luck and stay safe.
It's a big gapps problem and not about the devices. I am on redmi note 4x and have the same problem. My whyred have too. All original devices work. And my mido work before too. Its all about gapps.
I am very much thankful for all developers here but please don't talk its fixed. Its not especially on android 11 builds. There is non fully working gapps out just betas talk work but not. I have many devices. I flash and hundreds of others cellphones.
For all people search. Help to develop or wait for a right gapps build and report to all.