Related
OK new to this forum, but please assist if possible - I have an XDAIIs which I have combined with a Bluetooth GPS unit and Bluetooth headset, I am runing the latest ROM from the O2 web site and the following occurs:
with TomTom vs3 the headset will pair but fails to connect, with TomTom vs5 the headset set will pair and connect, but when I terminate a call on the road using the TT vs5 the GPS disconnects at the same time. I have tried TomTom vs 3 with the GPS driver rolled back to vs2.06 which was the concerted opinion of pocketgps.co but that to did not work. I have tried setting the XDA up for a wired conection but that to fails to work - does anyone have a TomTom nav working reliably with this device when it is combined with a Bluetooth headset, any help much appreciated as I am now considering returing the unit as not fit for the purpose it was sold to me - in anticipation many thanks Mike
I have had the same problem with TTN3 and headsets not working. The GPS pairing was not the issue. Removing TTN3 restored the link, but for some reason headsets will no longerconnect automatically.
I have tried soft and hard resets, and updated the bluetooth drivers to build 3900, but still the headsets will not connect automatically, only manually..
I have exchanged a few e-mails with the guru's at TomTom who now thick this may be a bug, but no resolution yet...
OK try this for good measure, I loaded up TomTom vs5 again yesterday, and connected up a wired GPS unit through the serial port (remove cross from check box marked "receive incoming beams" in the Ir port settings tab - in order to use serial GPS) and it works the Bluetooth headset is fine and doesn’t mess up the GPS - However before you rush out and purchase TT5 please read on. Last night I undertook a trip from Blackpool to the centre of Liverpool, approx 55 miles and about one hour in duration. The XDA required soft resetting no less than 16 times on the way there - not easy when driving !! When I got there I needed to use it as a phone and got the no noise in headset problem - note I was not using the bluetooth at this point it was back to a "normal phone" (occurs on my unit at least three times per day) - another soft reset. One other observation with the XDAIIs was its inability to charge up properly when running in the car cradle I set off with 85% in the main battery, a hour later it was down to 35% even though it was showing charging, way too many bugs in this unit for me to consider putting up with it any longer, one month on from purchasing it is going back to the shop and I don't want it repaired, or swapped for another one - I am going to go back to a standard phone that will work, I am sure under the trading standards the unit would be viewed as unable to perform the function for which it was sold - its a shame I like the design of the unit, and the functionality without having to carry around a plethora of kit, chargers, holders etc. but I will return back to my trustworthy ipaq-4700, in twelve months I have never hard reset, the XDA has had over twelve hard resets in the one month of ownership - regards all - Mike
OK appologies for the rant and rave, yesterday I took the unit back to the O2 shop who really did not want to know anything about the problems - "you only have 14 days - take it up with customer support" - which I did, first lesson if you have any problem with a new O2 unit get it back in the 14 day period. Customer support were most helpful and aventually agreed to replace the handset with an identical machine at the local shop, which proved easy (shame about 40 min on the phone but at least I got somewhere) second lesson use the support system it really does work. thirdly the shop assistant manager informed me O2 are no longer selling the XDAIIs with the TomTom package due to neumerous problems - that says something in its self. Loaded the new unit up with TT5 and used it today for navigation (3 hours), no problems with charging, GPS or phone usage all day, if this remains the case I will be a happy customer, perhaps I had indeed been supplied a faulty handset, time will tell - Mike
sinclox, if you need more advice on this one please e-mail me on [email protected]
I am sure you can get it to work - I am most impressed with my unit once the bugs were ironed out - let me know _mike
Mike,
Thanks for the offer, currently I am waiting for TTN5 upgrade to arrive until them I am unable to register TTN3 due to the TT upgrade process and so can't use TTN on the XDA.
I have dumped the O2 active interface in favour of Wisbar 2 and the XDA hasn,t locked up since.
Have you any clues as to how to get the bluetooth connection working automatically again with headsets? :?
Send me an e-mail to address previously posted on this link - Mike
After searching this forum there is no thread on Bluetooth issues connectivity.
For a wile now i been searching the net and different sites for a fix between my phone and my car bluetooth. Before the epic i had a windows phone and the connectivity was fine including all the phonebook would load up and everything the system was build to do. With Android Epic i been having issues. Sometimes I cant connect to the car and other I am able to connect but phonebook wont load.
With all the Geniuses in the website i am sure someone can come up with a fix.
I figured i open this thread hoping we can find a final fix to retire this problem.
If it helps I am running the latest Viper Rom with Genocide kernel at 1.2ghz
However the rom did not change the statues of my issue.
Any help would be appreciated.
Thanks
I also have connectivity issues with bluetooth, in my case the car has A2DP allowing for music to be played over the car's stereo. It cuts out so much that it is completely useless for music. I mostly listen to podcasts but Pandora would be nice. However it cuts out so much that it isn't worth it. So if anyone does have a solution. To me though I've tried so many kernels, and roms to no avail that I'm pretty sure taht the software Samsung has shipped has faulty drivers. By the way it also seems that the cut outs occur when switching towers, however I could be wrong.
I use this in my car: http://us.kensington.com/html/14484.html
It may cut out every 45 seconds or so but it's the only thing I've used. Got it on sale for $20.
I've got a pair of a2dp bluetooth headphones that I use to listen to podcasts via my Epic. I've had zero problems with those (using DK28 atm, for the record). So I don't think there's a hardware problem with the Epic's bluetooth.
If we're going to get some troubleshooting done, we should get a bunch of details from everyone. Like exactly what bluetooth hardware they're using, and what roms they're running.
thezero4 said:
I also have connectivity issues with bluetooth, in my case the car has A2DP allowing for music to be played over the car's stereo. It cuts out so much that it is completely useless for music. I mostly listen to podcasts but Pandora would be nice. However it cuts out so much that it isn't worth it. So if anyone does have a solution. To me though I've tried so many kernels, and roms to no avail that I'm pretty sure taht the software Samsung has shipped has faulty drivers. By the way it also seems that the cut outs occur when switching towers, however I could be wrong.
Click to expand...
Click to collapse
Does everything cut out, or just Pandora? If it's just Pandora and other apps that need data connection, it might not be a bluetooth problem as much as a data connection problem.
I would suggest testing it by trying the car bluetooth with something that requires no data connection at all, like pre-downloaded podcasts.
I am talking about connectivity issues with in stock car bluetooths.
this problem is big many people been having this issue and there is a list of stock bluetooth cars that android wont pair with. I had the touch pro 2 for sprint with windows system and it worked fine in my car bought the epic and there we go. Now looks kind of bad that i would need to get an aftermarket piece to listen to bluetooth calls and load up the phonebook from android to my car.
Windows got it right even though i would never go back to a windows phone so i know there is something that android messed up here
Below i will put some links to show you how there is A LOT of people that been having this issue.
http://code.google.com/p/android/issues/detail?id=3960
http://www.google.com/#q=android+bl...start=0&sa=N&bav=on.1,or.&fp=3f40f95b1b9c7c0d
I have a 2006 Dodge Durango. It has Bluetooth. My old phone, a Samsung flip phone would connect without issue. My new phone, a Samsung Captivate, will connect most of the time, but often times, once it connects, it drops the call.
I understand this is an Epic thread, but I thought I would add my input as I am having similar problems (and this came up on my search).
If I understand you correctly, you connect some of the time and sometimes not.
Regardless, if your phone is rooted you might wanna try this.
I had a lot of issues with my bluetooth after upgrading to froyo and tried a lot of fixes including wipe3x and odin to stock....this is the one that worked for me.
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Ensure that you first
- delete the car from your phone,
- delete the phone from your car,
- disable bluetooth,
- delete the file,
- CHANGE YOUR BLUETOOTH DEVICE name,
- restart,
- reenable bluetooth
- re-pair your phone with the car.
Some of you must own a Chrysler/Dodge/Jeep vehicle with a Uconnect stereo in it, right?
I've been all over the google search, the Dodge Forums, calling Chrysler's Uconnect dept, etc. and no one seems to have any clue what their talking about. I know that XDA is knowledgeable about all things phone. Searching doesn't get my exact questions, here's an unanswered one for the HTC EvoLTE (http://forum.xda-developers.com/showthread.php?t=1667801). The Ford SYNC systems have a similar problem.
I have a 2012 Dodge Durango with a Uconnect 430 RBZ stereo. It announces that my phone (the Sprint SGS3 with 4.1.1 LJ7 stock non-rooted (for now)) is not compatible with the Bluetooth Messaging Access Protocol profile or MAP-profile necessary to announce and control the SMS messages on my phone. There's a service on our phones that runs constantly when the bluetooth is enabled called MAPSamsungService, which after googling/reading/searching, leads me to believe this is the messaging protocol that the Uconnect desires.
My questions are:
1) Why won't this radio identify the MAP process of the SGS3 and connect to it Are there ROMs that do support this? (CM10 reportedly does support this http://forum.xda-developers.com/showthread.php?t=1916902 - but I don't like the CM10 camera....so...yeah)
2) Has anyone had success in getting the SMS messages functionality on their Uconnect
3) Has anyone had luck with getting your contacts to properly sync? All mine are Google Contacts, and it is VERY random which ones show up. (I have just less than 1000 contacts, which is apparently the upper limit for these radios)
[just in case this shows up in google searches, I have learned that USB drives connected to the Uconnect need to be in FAT32 format and you can only move 2048 songs over at a time to the HDD, so load up multiple flash drives for the transfer. must be constant bit rate not VBR, 1000 folders is limit and 20k songs]
as a former u-connect owner and current audi interface owner, let me offer the following:
When sold, the technology in any car is about 2-5 years old. meaning it was designed to interface with phones 2-5 years ago. so if you have an old phone, it will probably work great!!
Chysler never offered a flash or upgrade to the original uconnect system, but that was supposed to change with the RBZ. My brothers at the LX forum have reported that is not really true. There are some systems that allow you to get around this with aftermarket HU but not what you are looking for.
No way to know what ROM's will work or not because of your specific situation. There is a mammoth black hole where all BT protocols go...no one seems interested in making it generic.
We currently own 2 vehicles under the VW/Audi brand and a Ford with a Pioneer HU in it. My EVO LTE phone book will update in the VW, but not the Audi. Same system, right? In the Audi, it will frequently not sync. one vehicle has different software and Audi cannot flash it. no worries on the Pioneer HU though.
TLDR -> Car companies suck, wha, wha, wha
-----
Thanks for the reply and your experiences. Speaking separately for all the tech they put into every aspect of the car...... I would figure that in 2012, these car companies and their stereos would learn their lesson and start to evolve. I guess we need a Uconnect forum on XDA to really get things heated up! If anyone knows of a site for ROMs and such for these systems, please let me know, I'm willing to take the plunge.
I had an aftermarket Kenwood in my 2000 Jeep Grand Cherokee that I traded in. It synced with my phone perfectly, downloaded all my contacts, but didn't have the ability to read SMS messages (it also had a tiny display). Bluetooth worked well, etc. it just became a real piece of **** car that needed to be replaced.
The latest CM10 logs indicate that MAP functionality was fixed on 11/23: http://mobile.cm10log.appspot.com/?device=d2spr
I really wish that the CM10 camera and data connectivity didn't have so many issues, otherwise this would be a non-point and I'd be happy as can be with full functionality. What I find troubling is how many opinions there are about these different car systems and their compatibility. I understand your point about Bluetooth standards being quite a jumble. You should be required to support them all if you are going to use it in your device. I'm going to back to dual booting CM10 to see if I can get the MAP to work with the Uconnect system.
Then there's the confusion of all these systems. I have read links where a Stock Sprint SGS3 running 4.1.1 worked perfectly with MAP in a toyota prius. You ask Samsung and they say that MAP is not supported by the SGS3, their fact sheets would indicate the protocol is missing. But it was supposedly included in Android 4.1.1, but no one can confirm that.
It's just very disappointing when a company touts a technologically advanced car that can do things like read your SMS messages, display album artwork for songs, play songs from USB sticks, has ipod connectivity, etc. Can't seem to A) do any of those things well and B) offer absolutely ZERO tutorials and guidelines for making the above features actually work. You have to sift through forums to find out that a USB drive needs to be FAT32 formatted!
I just added 26.5GB worth of music to my HDD in my Uconnect 430 RBZ. I ensured that the album artwork was correctly linked with the ID3 tags in all of my music, a painstaking venture to say the least that I was meaning to do for a long time, however NO artwork actually shows up. It did finally all sync over and there are some things that it does "well" but far more that just miss the mark for no other reason than laziness and profitability. Just saying you can do these things is more profitable than actually making them work consistently - OR having knowledgeable people that can help you when you call in.
Overall, I guess I should be happy that it does what it does in the least. I understand the product cycles for cars and the tech is most likely 2-5 years old. Like everything else in this world, hopefully they'll improve their cycle time for updates. Then again, out of sight, out of mind. They have your money, who cares if they add any new functionality. Most cars aren't impulse buys like phones tend to be.
You can use any camera it does not have to be the cm camera. You can flash the stock or the 4.2 or even the note2 camera.apk. Also you xan flash your uconnect with a new firmware
Sent from my SGH-T999 using xda premium
Hello everyone,
This is not my first post on this issue. Sorry for the long post, but I am sick of this issue.
I have an Eonon G2110F head unit - RK3188 / MCU: MTCB-KLD2-V2.67 / KitKat 4.4.4.
It is stock (with only simple "factory setting" root). This is the "universal model".
Everything functions correctly. But I have an issue only with part of the GPS function.
I have a confirmed "good" iGO Primo version from a reputable GPS forum (v2.4+). I have installed it with maps/pio, regular voices, and TTS voices on my phone and tables. It work 100% correct, the way it is supposed to (both when installed to internal memory and external memory). What I am specifically testing for is how my phone and table function when I am playing music at the same time that the GPS is running (on both the stock mp3 player or Poweramp player).
When I set iGO Primo to use its regular voices, the music mutes when the GPS announces directions, then the music un-mutes once the announcement finishes. This is 100% correct. When I set iGO Primo to use its TTS Pro voices (using the Android default TTS engine), the music mutes when the GPS announces directions (which now include street names), then the music un-mutes once the announcement finishes. This is 100% correct. So as you can see, my iGO Primo build is a good correct working version.
However, I can not say the same thing when I install the same iGO version on my head unit (on the GPS card slot). Overall the app works. Both the regular voices and the TTS voices work and announce directions correctly. But once I am playing music at the same time, that is when the issue starts (regardless if its the radio / stock mp3 player or Poweramp / iPod / CD - I have tested them all). When I set iGO Primo to use its regular voices, the music mutes when the GPS announces directions, then the music un-mutes once the announcement finishes. This is 100% correct....,
However, when I set iGO Primo to use TTS Pro voices (using the Android default TTS engine), the music does not mute when the GPS announces directions (which now include street names). Instead, both the music and the TTS voice are playing at the same time. The TTS voice is much lower in volume and is hard to hear over the music. This is not correct. I have tried several other iGO Primo versions that are know as good working builds. These all work on my phone and tablet. But they have the same issue on my head unit once TTS voices are used. I have even tried by installing the app to the internal memory or the external SD card slot of the head unit.
I feel there is some kind of disconnect between the app and the MCU audio stream once the TTS voices are used. Remember, when the regular voices are use, the app and the MCU audio stream both work in the correct way. But as soon as I switch to use TTS voices, then the MCU audio stream does not mute when the GPS announces directions.
Over the past year, I have read so much that my eyes are bleeding. I have tried almost everything. I have even worked with senior members at the GPS forums. I am sick of this. When iGO Primo is installed on my head unit it is laughing at me to my face. So now I am ready to go "Ninja Assassin" on it.
Is there any other solution out there to force the music to mute? Is there an Xposed module that can deal with this issue? Is there some kind of modification that need to be made (on either the app or the head unit). Otherwise, I will need a full professional developer to look at this and create a solution (for hire $$). I have seen several, several posts on the internet with similar issues - yet no solution. So I am ready to hire someone and pay to have a solution developed (for the good of the community).
Any help will be greatly appreciated. Again, sorry for the long post.
Thanks,
ggee
Tried using some TTS voices in other languages to see if the issue is related to the voice you're using?
Tried using another music player?
I have the same Eonon G2110F and use iGo Primo (one of the latest versions) with a dedicated Italian TTS voice and have no problem while listening to the radio (not tried iGo and music player together with active navigation).
themissionimpossible said:
Tried using some TTS voices in other languages to see if the issue is related to the voice you're using?
Tried using another music player?
I have the same Eonon G2110F and use iGo Primo (one of the latest versions) with a dedicated Italian TTS voice and have no problem while listening to the radio (not tried iGo and music player together with active navigation).
Click to expand...
Click to collapse
Hello,
My issues happens with any music applications. It will happen with the stock MCU music apps (Radio / iPod / CD / Music ). And it will happen with third party music player (like Poweramp).
I have had people reply before who say they have no problems. But when I ask follow up questions and dig deeper, I discover they either don't use TTS voices, or don't play any music while driving (which is why they don't know of any problems). Or I find that they run the app from their phones/tables and bluetooth the audio/screen to the head unit. There is always something different about how they use it that explains why they do not have an issue. For example, they find out that they don't really have a legitimate iGO Primo version - instead it is some generic GPS app with an iGO skin and very limited features (yes, these do exist).
- Can you please let me know the specs of your head unit (firmware version / MCU version / Custom Rom if any)?
- Do you have any major software modifications on the head unit?
- Are you using the stock Android TTS Engine or a third party TTS Engine (like Vocalizer/Nuance)?
- Can you please let me know what version of iGO Primo you have and where you got it from (check the Settings/About screen in iGO for the exact version)?
- Can you share the TTS voice file, and the sys.txt file with me (this way I can test the setting on my head unit).
-If you can share your whole iGO Primo build with me that would be even better (minus your maps/pio/dem/buildings files)? You can PM if you prefer that way better.
I use a real iGO Primo version in a normal way, on a normal stock head unit. That is why I am asking the above questions. I personally feel there is an issues with the MCU.img that some how causes a disconnect to the android audio stream when using an "outside" TTS voice over the android TTS engine. By "outside" I mean that the GPS card slot is technically a separate memory area on these head units. Since iGO Primo is running from this "outside" memory area, it might be causing an issue, such that the MCU does not see a running TTS voice. Therefore, it does not know to mute the music (but when regular voice files are used, it somehow knows). This is what makes this so strange and freaking annoying.
Thanks again for any help,
ggee
I have the original Eonon MCU and ROM, rooted.
The iGo specific Italian TTS voice has been provided by an Italian iGo user forum, but I don't think the TTS voice matters for your issue.
Obviously no iGo version can be shared...
Anyway, I have never heard of similar problems, at least on the iGo Italian fora.
Maybe it's better to ask on some specific iGo forum, all those fora of course deal with Android head units...
themissionimpossible said:
I have the original Eonon MCU and ROM, rooted.
The iGo specific Italian TTS voice has been provided by an Italian iGo user forum, but I don't think the TTS voice matters for your issue.
Obviously no iGo version can be shared...
Anyway, I have never heard of similar problems, at least on the iGo Italian fora.
Maybe it's better to ask on some specific iGo forum, all those fora of course deal with Android head units...
Click to expand...
Click to collapse
Hello,
Since you "can't" share anything
Can you at least tell me what MCU version you have on your head unit? In this way, I can see if I have the latest MCU version. If your version is newer, I can at least go back to the seller and ask them to send me the same or latest version (and flash my head unit).
For example, this is my version: MCU: MTCB-KLD2-V2.67
What version do you have?
There are many posts on the internet where people mention some type of volume issue with iGO Primo using TTS voices.
Also, can you at least tell me what forum you are referring to. If you have specific forum/post link information that would be better. As I mentioned in my original post, I have read and been to many other forums before. I have tried many things already. This is not me trying to be lazy. But if you have a specific forum, or a specific post - can let me know what it is? That would be of great help.
Thanks,
ggee
gguevara said:
Since you "can't" share anything
Click to expand...
Click to collapse
It looks like that probably you're not completely aware that there are no "legitimate" versions of iGo for private users (maybe except in Israel), so of course I'm not going to share anything...
And for this reason too IMHO this kind of discussion shouldn't be carried on XDA and so I suggested you to better ask on other specialized fora.
That said, the last and final information I can give you on this subject are the current firmware version of my head unit, see the attached images.
themissionimpossible said:
It looks like that probably you're not completely aware that there are no "legitimate" versions of iGo for private users (maybe except in Israel), so of course I'm not going to share anything...
And for this reason too IMHO this kind of discussion shouldn't be carried on XDA and so I suggested you to better ask on other specialized fora.
That said, the last and final information I can give you on this subject are the current firmware version of my head unit, see the attached images.
Click to expand...
Click to collapse
Hi "mission",
Thanks for the reply. I appreciate the info about your MCU version. I have a lesser version, so I will ask the seller to send me the latest official MCU version (not BETA).
I will talk to you soon..., keep your eyes open
Thanks again,
ggee
You can find all the known MCU versions here:
http://forum.xda-developers.com/showthread.php?t=3246386
themissionimpossible said:
You can find all the known MCU versions here:
http://forum.xda-developers.com/showthread.php?t=3246386
Click to expand...
Click to collapse
Hello,
Today I received the same mcu.img version that you have (for my exact KLD2 head unit). I noticed that my stock firmware is newer than yours, but your mcu version was newer than my.
Anyways, I updated the mcu to my head unit successfully. However, this has not resolved my TTS voice issue. It is acting in the same way. The music does not mute when the TTS voice on the GPS speaks. They both play at the same time. When listening to the radio, the TTS voice volume is much lower. When listing to MP3s on the stock MTC Music player, the TTS voice volume is about equal (the same thing when using PowerAmp, except the TTS voice volume is not as low as the radio scenario). Why Does Yours Work and My Does Not???
_____________________________________________________
Anyway,
This goes out to anyone else out there who is willing to actually help me with this (not just empty talk or drop their 2 cents). As I mentioned, I now believe this is an issue with the MTC side of the head unit. Something is affecting the MTC audio stream from acting properly when the TTS voice of the GPS speaks. I have tried everything I can get my hands on. This is so frustrating.
When I use Google Maps on the head unit, it acts 100% correct. Keep in mind that Google Maps exclusively uses the android TTS engine and TTS voices. Additionally, I have installed the same iGO on my phone, and it works 100% correct.
Can someone who is an expert on the MTC function of these head units please help me??? Or can someone point me to the right person(s)???
Do not hesitate to Private Message me if you want to "assist" me.
Anyone else...., Please!!!!!
Thanks,
ggee
There are more than one TTS engine available to try.
Try for ex. latest Vocalizer (Nuance).
Search on the net.
Hi
I think the issue may be that the software for the TTS is run from head unit system and not from the Igo software. The standard voices use the Igo software and Igo mutes the radio or any music. The TTS is actioned by the head unit.
Ok I'm back,
So just to quickly update you on my 2din issue. It is still an issue. Update finished.
Back to my install on my phone, though. As a reminder, I installed the same Igo Primo on my android phone just so that I could test to see if it would have the same TTS Pro voice issue as I am experiencing with my 2din (TTS does not mute music when speaking). I initially reported that my phone installation works 100% correctly when using TTS voices and playing music at the same time. The music mutes when the GPS speaks.
However, I noticed something the other day. When I initially tested with music on my phone, I initially used the default android music play on my Samsung Galaxy phone. This worked fine. But the default music player would also pick up the audio files from the Igo folders and list them within the music library. I do know there is a simple work around in order to stop the default music player from seeing the Igo folder (and not play the GPS audio files).
But instead I started playing music on my phone using the Power Amp player. Anyways, when I play music through Power Amp, the TTS Pro voices do the same thing as my 2din (which is that the music does not mute when the GPS speaks). Yet when I play music using the phone's default android player, this issue does not happen. So now, I have this question and issue to resolve. Maybe this will somehow explain why my 2din also does not mute the music when the GPS speaks (using TTS voices).
Does anyone have an idea on this.?I would think that the audio stream for music would be the same for both mp3 apps. So if I change the audio stream options on the Igo sys.txt file it should affect how it reacts with all apps. Not just one app and not the other. Is this a correct assumption? Does this mean that the default music player uses one audio stream (the same one used by Igo), and that Power Amp used another audio stream?
Any ideas?
Thanks,
ggee
Hello,
I want to pass this along in case there is someone out there with the same issue on their 2din android car head unit. Someone on another forum shot me a private message to try something as a workaround and it seems to have worked for me (I can live with it).
My issue was that when using iGO Primo with TTS voices, the head unit would not mute or lower the volume of music when the navigation voice speaks. It did not matter if I used android's built in Google-TTS engine or another third party engine. However, I did not have this issue when using the normal non-TTS voices (in this case the head unit worked correctly with muting/lowering the music).
So they suggested that I switch back to using the built in Google-TTS engine and the correct language in the android settings of the head unit. Then go into the head units GPS settings and assign the Google-TTS engine as the default GSP application. Doing this will mean that the hard GSP button on the head unit will no longer launch iGO Primo. But that is ok because I can launch it through the iGO icon/shortcut on the screen. Then make sure to go into the iGO Primo sound/volume settings and select the correct TTS voice, with the correct language that matches the language on the Google-TTS engine setting. Then properly exit from the iGO Primo app and reboot the head unit. That's it.
This somehow causes the head unit to function correctly when iGO Primo uses TTS voices. This workaround only works when using iGO Primo with TTS voices. It will not work when using normal non-TTS voices.
If you are using any third party TTS engine (like Nuance or Ivona) and try this workaround, it will not work properly. It will work at first until you shut off iGO Primo or the head unit reboots. When this happens, the settings get lost and you will need to redo the settings each time. But the settings "stick" when using the built in Google-TTS engine.
So far I have not had any issues in over two weeks. I hope this helps anyone else with the same annoying issue I had (look at my first post on this thread for a full description of the issue).
Thanks,
ggee
themissionimpossible said:
It looks like that probably you're not completely aware that there are no "legitimate" versions of iGo for private users
.
Click to expand...
Click to collapse
Not true anymore. IGo is available in the PlayStore.
m00n61 said:
Not true anymore. IGo is available in the PlayStore.
Click to expand...
Click to collapse
Finally!
Thanks for the news!
I am curious if you have gone to the GPS settings in the head unit under settings and modifie the volume setting fade in or out. I put mine to the highest seting and now the volume mute is good. hope this is what you meant and helps.
roscored1000 said:
I am curious if you have gone to the GPS settings in the head unit under settings and modifie the volume setting fade in or out. I put mine to the highest seting and now the volume mute is good. hope this is what you meant and helps.
Click to expand...
Click to collapse
Changing GPS settings didn't help me. Setting gps app to Google TTS only works.
Since the navigation hardware key does not work anymore when GPS app assigned to Google TTS, can the key be assigned to iGO app directly? From Factory Settings menu all keys can be mapped to different functions, but cannot be mapped to android apps. Is there a solution for assigning apps to keys?
yves31 said:
Since the navigation hardware key does not work anymore when GPS app assigned to Google TTS, can the key be assigned to iGO app directly? From Factory Settings menu all keys can be mapped to different functions, but cannot be mapped to android apps. Is there a solution for assigning apps to keys?
Click to expand...
Click to collapse
Use mtc-keys xposed module
I have the same problem with Sygic. TTS voices much lower than the system volume. And no way to higher them up. Sygic i think is only using the default google tts engine.... any idea??
Hi everyone, looking to pick up an octacore headunit from aliexpress, "KANOR" branded.
[can't post link because new member]
But one of the main reasons I want it is to connect with my ECU through a google play app called MDash. It connects via bluetooth. Through my reading over these android head units, I've seen a lot of mentions of the bluetooth functionality only working for music, phone calls, and the obd2 adapters. Does anyone have experience on whether or not the bluetooth is still this limited for the newer Android 8.0 octacore units? And if so, is there a way I can get the functionality I need out of the headunit by rooting it?
Thanks for your time and help!
bump
bump. Any help is greatly appreciated before I spend my money on a headunit.
Yes mate still crap. In fact Id say worse.
I have a new erising octa px5, mtcE, android 8 and bluetooth is minimal. Phone app is rubbish, sounds / looks terrible and it just about works .
Dont no for sure what profiles it has stock but seems everywhere I read now ppl are going the android auto route (which uses 'OK' google everything (surprise surprise)) and always on data. etc.
Lemmings!