Touch screen edges stop responding - Android Auto General

Hi
I bought this head unit for my honda jazz 4 month ago.
2016 Newest Android 5.1.1 System Car Radio Recorder For Honda Fit Jazz GPS DVD Stereo WIFI 3G BT Phonebook IPOD OBD DVR 1080P
(Cant put link as new user)
Mtcc kld6 v2.91
Android 5.1.1
600x1024
[email protected] #2
Rk3188 userdebug 22062016
Evrything was ok until one day just the 1.5cm edges stoped responding to touch.
Must say, when i connected usb mouse its work fine with it.
I think i did some firmware update by wifi.
Another thing is that all the middle part of the screen that work have like 2x2mm squers pixels that i didnt remember when it was new.
Dose someone know this problem?
Sorry of its not the right places to open this thread.

Related

Nexus one and car bluetooth

Hi
I have been trying to pair my N1 to my nissan altima 2008 bose bluetooth system but it wouldn't pair. I tried countless number Of times but it won't work.
Does anyone else have this problem?
I think I read in the Google Nexus One forum that there are issues with Nissan/Infiniti cars and the bluetooth of the Nexus one.
hmmm... I have got mine paired with Chinese all in one DVD/SATNAV/DTV unit... it works very well.. It even automatically switches on the unit when It detects a bluetooth signals from my paired Nexus One....
Well, Im guessing its something to do with compatibility with the Nissan Bose Unit. Because I also had a difficulty pairing my Previous G1, But ONLY after updating to Donut 1.6. It eventually connected but after many many tries.
I have beeen doing some googling about this and it seems that many users are having problems pairing with different cars with 1.6 and above.
Weees said:
Well, Im guessing its something to do with compatibility with the Nissan Bose Unit. Because I also had a difficulty pairing my Previous G1, But ONLY after updating to Donut 1.6. It eventually connected but after many many tries.
I have beeen doing some googling about this and it seems that many users are having problems pairing with different cars with 1.6 and above.
Click to expand...
Click to collapse
Well the other option you have is to change your car... and get a car which is compatible with Nexus One...
see here: http://code.google.com/p/android/is...ct&colspec=ID Type Status Owner Summary Stars
this issue is known to carry through android 2.0 and 2.1.
I have the 2010 Mazda 3 sport with the Bose package and it pairs fine.
jeffokada81 said:
I have the 2010 Mazda 3 sport with the Bose package and it pairs fine.
Click to expand...
Click to collapse
Yeah, I have the 2010 Mazda 3i touring and no problems either.
ID have a kenwood deck in my mazda and all works good. is there some kind of factory reset switch on your stereo, that's what I have to do t get new phones working on mine.
I have a Parrot Mki9100 and I have some problems...when I am on the car my Nexus One connect itslef with the Parrot, but it disconnect and try to reconnect many times. At the end it stops trying...
So every time I have to go to Settings->BT->Long press on Parrot device and click connect. After that it works...very annoing...
Hm... I have an '08 Infiniti G37 with the Bose system and it pairs and works just as well as it did with my G1. I would have assumed that Nissan is using the same or a similar unit for the audio system for most of their cars.
Mazda 6 gt-m 2009 here, BT carkit has no probs with the N1
Tried to pair it with the parrot in my gf's car, but same probs as described by other users. Seems it's the Parrot; my iphone had issues with it as well.
Ah well, i'd rather drive my car then hers, so good excuse to use mine
I dont get how they end up making things worse by upgrading rather than making things better !!! I mean according to : http://code.google.com/p/android/is...ct&colspec=ID Type Status Owner Summary Stars
This problem has been known since 1.6 and I can defenitly confirm that since It took me forever to pair my G1 previously. But with my N1 , it just never pairs, so they even made it worse. Such an important option, you would think Google would have fixed it in 2.0 but to drag it to 2.1. This is just messed up.
That is very frustrating.
@OP, someone mentioned changing your car to accommodate your nexus one, that sounds like a great idea, but if you can't get it to work you can always go with a bluetooth add on option.
At Volkswagen there were some phones that were not connecting with the manufacturer add on and customers were pissed because they paid over $400 for the option. Another thing just as bad is purchasing the unit and not being able to use the bluetooth steering wheel controls because of compatibility issues.
My conclusion is that there are too many products out there and sometimes they are just not compatible with each other. In this case it sucks that it was your car...or should I say your phone?
Well, the Nexus connects fine to my VW premium bluetooth (from 2005) but the cars system can not access the phonebook.
Not even the sim contacts which the HTC Hero could do.....
Google support suggested importing the sim contacts into the Nexus.
I wonder if they read the mails before they answer....
I've always found OEM bluetooth to be pretty uncompatible, and yet to see an update for one.
I've got a kenwood unit, which works with my steering controls, connects handsfree and audio when I turn on my ignition, and it syncs the phone book fine, showing the callers name when the phone rings. (it cost £80....) and I updated it (it's a parrot bluetooth unit in there) from my laptop via bletooth.
The N1 works best of all the phones I've had (6 htc's in 3 years) with it.
I never had an issue with my old g1...until I flashed a 2.0 ROM. Everything pairs fine, music player worked, stereo would switch over, but no sound came from speakers on phone calls. Now my nexus is the same way. I've asked Cyanogen if he would be kind enought to look into it and hopefully he will.
My N1 (locked bootloader, not rooted) routes the audio just fine, did it work before you cyanogened it?
ck3100
Wel I tried to connect my N1 to the parrot ck3100. it will see it fine, but the moment I try to link it it says paring failed. Anybody had any better luck with the ck3100 and N1?
mgymnop said:
Yeah, I have the 2010 Mazda 3i touring and no problems either.
Click to expand...
Click to collapse
I've got a 2010 Mazda 3 sport - it pairs/plays fine etc with my Nexus, but the person on the other end of the line always complains that I sound *really* quiet. I never had that problem with my G1. Do you get any complaints?

Kenwood DDX9902S Ordered

I ordered the Kenwood DDX9902S the other day, should arrived on the 28th and I will install on the weekend.
Going to install in my 2014 Mazda CX-5 Touring with Bose system.
I chose the DDX9902S over the DDX9702S because it's only $50 more and has 2 more bands of EQ and 2 years of warranty vs 1, and some other stuff.
I chose it over the Pioneer AVIC-4100NEX because it can do the screen mirroring and control the Phone from the touchscreen. (Though the damn Nexus 6 doesn't support video out damn it).
It is too bad the Kenwood only has 1 USB input though, and the Pioneer has TWO and also has an SD card slot. Does a USB hub work?
I'll have to do some creative wiring so I can swap out cables for card reader/etc if I want to view movies and such. The Kenwood can playback mkv files, didn't look up if the Pioneer can.
Ordered it from Crutchfield, $749 + $79 for the steering wheel control/wiring harness, free antenna and dash kit. Since it's so new, it's the same price elsewhere on the internet.
The Crutchfield Mastersheet is stupid. It only shows you how to take out factory audio unit and speakers, nothing about wiring at all. If buying stuff is cheaper elsewhere, do it.
Going to wire up my factory rear view camera to the Kenwood, from the Mazda forums, someone detailed how to do it. Got the items today and will get it prepared for next weekend to install by myself. I'll report back, I might also do a YouTube video since this unit is so new and no one has it.
What phone are u currently using???
cerobles1 said:
What phone are u currently using???
Click to expand...
Click to collapse
Nexus 6
nxt said:
it can do the screen mirroring and control the Phone from the touchscreen. (Though the damn Nexus 6 doesn't support video out damn it).
It is too bad the Kenwood only has 1 USB input though, and the Pioneer has TWO and also has an SD card slot. Does a USB hub work?
Click to expand...
Click to collapse
So you expect to mirror, instead of running Android Auto ?
Pioneer is limited in what it can do on each port. I think iPhone/iPod goes to port 2 while firmware updates and Android Auto are port 1.
In theory, anywhere a phone works, a phone plugged into a USB hub should work. But don't underestimate the need to get a quality hub and cables for reliable connections.
I have no idea if the Kenwood supports flash or other USB stuff besides a phone, and at the same time a phone is connected.
mikereidis said:
So you expect to mirror, instead of running Android Auto ?
Pioneer is limited in what it can do on each port. I think iPhone/iPod goes to port 2 while firmware updates and Android Auto are port 1.
In theory, anywhere a phone works, a phone plugged into a USB hub should work. But don't underestimate the need to get a quality hub and cables for reliable connections.
I have no idea if the Kenwood supports flash or other USB stuff besides a phone, and at the same time a phone is connected.
Click to expand...
Click to collapse
No, I will use Android Auto but would like to check out the screen mirroring too, for apps that don't support Auto / 'appradio' yet.
I've downloaded the manual and the Kenwood does support movies and music on a USB flash drive, but no mention of hubs or simultaneously connected to phone.
I just installed the DDX9702s over the weekend. It's a pretty good unit, Android Auto works flawlessly with my Sony Z3, and the external GPS makes it super accurate. Kenwood's interface is so freaking ugly though
Android Auto is also incredibly finicky on my wife's OnePlus with CyanogenMod. I flashed to 12.1 nightlies hoping to resolve some of the issues but it's no better.
The iDatalink Maestro was also fun to install, it requires taping some wires on your ODBII port. My tip there is grab a right-angle generic ODBII to Serial cable on Amazon/Ebay for $10 then cut it up and splice it into the iDatalink Meastro harness. That way you can just plug it in rather than t-taping or hard-wiring the maestro cable to your car. You can also re-pin the ODBII port as well, but splicing an extra ODBII cable seemed like the best option if I ever want to go back to stock.
jonowar said:
Android Auto is also incredibly finicky on my wife's OnePlus with CyanogenMod. I flashed to 12.1 nightlies hoping to resolve some of the issues but it's no better.
Click to expand...
Click to collapse
Doesn't start or what ? Sometimes enabling/disabling USB debugging can help with getting a phone connected.
I saw the news about 1+2 not having NFC. It appears NFC is required to trigger Android Auto over Wifi connections, so that could be an issue for the new 1+2.
mikereidis said:
Doesn't start or what ? Sometimes enabling/disabling USB debugging can help with getting a phone connected.
I saw the news about 1+2 not having NFC. It appears NFC is required to trigger Android Auto over Wifi connections, so that could be an issue for the new 1+2.
Click to expand...
Click to collapse
Yea, it won't start unless I "forget all cars" and go through the acceptance dance again then most of the time it freezes or just shows a blank black screen. I can't believe how much difference the Sony Z3 is, it works flawlessly every time.
jonowar said:
Yea, it won't start unless I "forget all cars" and go through the acceptance dance again then most of the time it freezes or just shows a blank black screen. I can't believe how much difference the Sony Z3 is, it works flawlessly every time.
Click to expand...
Click to collapse
It MIGHT be due to bad USB connections; maybe the USB port isn't tight.
Android Auto tends to freak out if USB isn't a perfect connection.
mikereidis said:
It MIGHT be due to bad USB connections; maybe the USB port isn't tight.
Android Auto tends to freak out if USB isn't a perfect connection.
Click to expand...
Click to collapse
I'm using the same cable for my Sony though, which means it's the port on the OPO which is only a few months old
I'll give it a shot with the official OPO cable just to make sure.
I guess it's time for USB C.
jonowar said:
I'm using the same cable for my Sony though, which means it's the port on the OPO which is only a few months old
I'll give it a shot with the official OPO cable just to make sure.
I guess it's time for USB C.
Click to expand...
Click to collapse
I'm not saying that it IS the port, just that it's a possibility.
I have about 15 test devices and I don't think any ports are bad, even after years of use.
I DO have cheap USB cables that are pretty bad though.
Trying other cables is the best idea I have, besides wiggling the cable a bit to see if Android Auto stops.
mikereidis said:
I'm not saying that it IS the port, just that it's a possibility.
I have about 15 test devices and I don't think any ports are bad, even after years of use.
I DO have cheap USB cables that are pretty bad though.
Trying other cables is the best idea I have, besides wiggling the cable a bit to see if Android Auto stops.
Click to expand...
Click to collapse
Hey, you were right! The OPO cable works perfectly! Thanks for the tip.
Have the same unit... Love it, look on the Kenwood website, there is a firmware upgrade for our units
Frankenberrie said:
Have the same unit... Love it, look on the Kenwood website, there is a firmware upgrade for our units
Click to expand...
Click to collapse
Awesome! thanks for the heads up, 100mb.
It says to do a reset after, is that necessary, kenwood has a ton of settings.
nxt, been eagerly waiting for your DDX9902S in depth review. Did I miss it? If so, please point me in the right direction. If not, I'd love to hear your thoughts now that you've been using it for a few months, especially if you've had a chance to compare it to the 4100NEX and from an Android perspective (mirroring vs Auto). Thanks
Frankenberrie said:
Have the same unit... Love it, look on the Kenwood website, there is a firmware upgrade for our units
Click to expand...
Click to collapse
senseimike said:
nxt, been eagerly waiting for your DDX9902S in depth review. Did I miss it? If so, please point me in the right direction. If not, I'd love to hear your thoughts now that you've been using it for a few months, especially if you've had a chance to compare it to the 4100NEX and from an Android perspective (mirroring vs Auto). Thanks
Click to expand...
Click to collapse
I wrote a pretty long review on Crutchfield but ran out of space. I ended up not making a video review because... it's not that great.
Just like any head unit, the regular UI for radio/settings/menus/audio/etc is ugly.
Anyways, here's some info going from the HU itself then Android Auto.
The Kenwood only has 1 USB. It charges your phone very very slowly, but it can charge it to 100% if you keep it connected long enough even while using Android Auto. (I do 6-7hour drives every other weekend).
1 USB, so 1 USB device connected and that's it. The Pioneers have a dedicated SD card slot, you can store music on it and leave it in there forever.
Putting about 64GB of music on a USB 3.0 Flash drive, the Kenwood took a very long time to get complete ID3 tags. So I'm forced to listen to Adele when it starts up, or manually choosing another folder before I can shuffle ALL songs.
The Kenwood supports various file formats, it can even play video files! Too bad all the .MKV files I have, no audio is decoded.
Bluetooth audio. Very little lag, steering wheel control to skip tracks almost instantly changes the tracks. My stock HU there was 2-3 second delay. ID3 tags show up properly. I primarily use Google Play Music app. I mostly use Android Auto mode when using to music though.
Bluetooth Phone. Works fine, I have a 2014 Mazda CX-5, I put the microphone where the stock microphone was. People can hear me perfectly. Android Auto voice commands have no issues hearing me either.
I have a Nexus 6 and when it was on 5.x.x, the Bluetooth Phonebook on the headunit would be SCREWED UP. No names, and just a ton of phone numbers. I installed Android 6.0 that was released a few days ago and Contacts information show up perfectly.
The Kenwood's backup camera input works really well. I can turn on the car and as the Kenwood is still booting up, if I put the car in reverse, the backup camera would be displayed! I'm pretty surprised with this and love it. The Kenwood takes a while to boot up.
The Kenwood, like most high end HUs have a TON of audio settings. I'm no car stereo buff so I mostly leave everything at default since I don't know half of what the settings mean. Each audio input has it's own audio setting which is great. My car has the factory Bose system and it sounds even better with the Kenwood.
The Kenwood has built in iHeartRadio/Pandora/Aupeo! "apps" that's supposed to work with your phone. It's junk, I've given up trying to make that work and just do regular Bluetooth Streaming.
Kenwood also has a SmartPhone control mode where if you can get your phone to video output into the Kenwood's HDMI or AV input, you can load the Kenwood App, and control your phone from the Kenwood's touchscreen, so you can use Waze or other apps directly. The app sucks and doesn't get my touches correctly. Don't rely on it, it's not reliable.
So yeah it has 1 HDMI input you can use with your iPhone using video adapter, or Android or whatever else.
It has DVD slot for movies/audio cds, I've never used it.
HD Radio. The radio interface really sucks, but it works. The way to change an HD station from HD1 to HD2 is really dumb and annoying. it has 3 different "seek" modes when you press the >> or << button. Seek1 auto scans to the next station that it can grab. Seek2 is manual seek. Then there's Auto where it changes to your next Preset.
Then there's the CHup and CHdown buttons. So if you're locked into an HD station and you want to change to HD2 you press the CHup or CHdown button, but that only works if you're in Seek2 (or maybe Seek1, I forgot), if you're not, all it does is the same as >> or <<. It makes no sense because CHup and CHdown acts EXACTLY like the >> and << buttons.
I have a ZuneHD with a special car aux box for it, I use it in AV1, works and sounds fine but when I put it into video mode I get a lot of interference. Not sure if it's the Kenwood or my aux box for it.
The Kenwood's video controls suck too. It's just hard to adjust and get proper color/brightness/etc.
At night, it's too bright, and lowering Brightness and "Blackness" levels, it gets hard to see/read the screen. So to make things clearly readable, screen has to be a little bright. There is a way to set holding Menu button and the screen will turn off until you press screen or a button.
OK Android Auto, I won't talk about Android Auto itself, there's many reviews and videos about it. I'll talk about how well it works with the Kenwood.
When it works it's great, but it's a coin toss if it'll work great on this drive, or the next.
Plug in USB cable to the phone and you're prompted to press OK on a warning screen on the Kenwood. The Apps icon turns into Android Auto.
Again, when it works, it works. Here's when it doesn't:
On my road trips, I would get into car, search the destination, and start navigation.
About 5 minutes later, Android Auto on the Kenwood would shut off and you're taken back to the main menu and the Apps icon return. Phone's Android Auto app is shutdown. There's no way to relaunch Android Auto without unplugging the USB and plugging it back in. On my last road trip, I did this about 4-5 times, then I decided to start Play Music while navigating, then it worked and had no issues. On my drive home, I started music right away with navigation and it still shutdown every few minutes. Unplugging and plugging back a few more times then it worked with no issues. It's completely random.
On my drive to work and back home, I drive through some low cell signal areas. When my phone looses signal and then catches signal back, Android Auto's screen would BLINK. Navigation wouldn't stop, music wouldn't stop, the screen would just BLINK. It's distracting.
Phone calls go through Bluetooth still, but it works well from the Android Auto screen. I'm sort of impressed how it works.
It's possible to listen to another audio source (HD Radio, CD, etc) while in Android Auto navigation, just press menu button, pick your source, then go back to Android Auto.
Android Auto I believe needs a lot of work. It's still in its infancy and the missing features and odd limitations Google has with it frustrates and confuses me.
Kenwood released a firmware update 9/17/2015.
Changelog is: Changed the specification of Volume function. Improved stability.
I hadn't noticed any improved stability.
That's all for now. Ask your questions and I'll try to answer them.
About Mirroring vs. Android Auto.
My Nexus 6 unfortunately does not support video out. I'm pretty pissed. The new Nexus 6P won't either, damn it Google!
So what I did to test was to hook up a Chromecast to the Kenwood's HDMI input.
Then I would set up my phone to be a hotspot, the Chromecast would connect to it, then I was Cast my Phone's screen to the Chromecast. Totally going in a circle LOL. (This will eat up your cell data FYI).
But it does work and my screen shows up on the Kenwood's screen.
The issue is the Kenwood's SmartPhone Control app like I mentioned in the above post.
It does not sync up properly so my touches on the Kenwood's screen, does not touch the right area of my Phone's screen.
I've never used the Pioneer 4100 so unfortunately I can't compare.
I believe that having TWO USB ports on the Pioneer and a dedicated SD card slot is BIG!
It's so annoying swapping out my Phone with a USB Flash drive.
If I were to do it again, I would probably get the Pioneer because of the TWO USB and SD card slot.
I chose the Kenwood because of the higher audio capability (EQ) and the App Mirroring (which sucks now that I've tried it), also it was cheaper than the comparable Pioneer high end model.
Hello, I ordered a DDX9702S and installed it in my '09 Civic Si. I've got a Nexus 6P and have been experiencing odd audio glitches, and I was wondering if you could test something for me.
When I play music, everything is fine until I get an audible notification or use the Voice Search. After that there is an audible buzzing/frying noise in the tweeters of my stereo when a bassy note hits. Once the noise starts, it doesn't stop until I reboot my head unit. Could you see if you have the same problem? I don't know whether it's Android Auto in general, my Kenwood stereo, or what. I've also reproduced the issue with 2 other Nexus 6P's and a Nexus 5, so I know it's not just my phone or model. I know yours is a different model, but it's worth a try to see if it's just me.
Steps to reproduce:
App to use:
Either Google Play Music All Access or Spotify
Song to use:
Rearrange by Vérité - the beginning of the song is quiet with a bassy beat, making it easy to spot the distortion / static.
Steps:
Turn on the head unit and plug in your phone (I used a Nexus 6P and a Nexus 5)
Once Android Auto is running, go to your music app and play Rearrange by Vérité. I find its easier to play the song if you add it to a playlist titled "1" (without the quotes) first, so it's at the top of your playlists.
You'll notice that the beginning of the song is quiet with a bassy beat. After about 10 seconds, hit the microphone in the top right of the screen to activate the Google Now Voice feature. Once it gives an audible beep, hit the microphone button again to cancel.
Hit back on the screen to start the song over. At this point, on my stereo, every bassy beat is accompanied by a static in the tweeters of my stereo. This happens on every song I play, even the radio, but it's much easier to hear on quiet songs like the one I gave as a suggestion to test with.
The static continues even if you disconnect/reconnect the phone. The only think that stops it is restarting the head unit by turning it off and back on. If you use Google Now again or a notification comes in and makes an audible sound, the static will come back. It seems, to me, that any notifications or audio playback from an Android device will cause the head unit to distort the sound until the head unit is rebooted. If nothing happens to cause the distortion, sound quality is stellar.
Hope you're able to test this, and thanks in advance!
DDX9702S
Sent from my Nexus 6P using XDA-Developers mobile app

Thoughts? Erisin 3090A - Single Din, quad core, 4.4, 1024x600

I'm looking to get a single DIN flip screen style head unit. Looks like there are really only 2 quad core options out there:
Eonon GA1312: Seems to be relatively popular Klyde design and shows up under a few other "brand" names. It meets my needs but the basic downsides here being the 800x480 screen and typical lack of an external microphone. From a Youtube walk through it looks like it is a KLD5 MCU.
Erisin 3090A: This looks like an upgraded quad core version of the Erisin 8990A (dual core system). This unit has the upsides of a 1024x600 screen, an external microphone (important given this is going in a loud sports car), options for DAB radio and DVB-T TV (not useful here in the US), and a removable face plate. (I can't post links but the specs are posted at the first google search link for "ES3090A")
Needless to say the Erisin looks like the better on paper, but I'm hesitant to pull the trigger. Anyone have any experience, thoughts, or comments on this unit?
I got both.
Eonon GA1312:
Bluetooth is total crap , no one can hear you in a call .
Missing 3g apn setup
unable to change panel leds color, they are blue and blinding.
no detachable front fascia
front usb and front audio in
Simple to root with a password.
Some apps cannot pass the initial screen due to low Res.
Shutdown timer does not work.
It has configurable reserve camera lines
Erisin 3090A
Bluethooth calling is great plus it has an additional external mic.
Device seems to have 2 Bluetooth devices , one for the phone and other for android
Any color you fancy for the panel leds
detachable front fascia
Can only be rooted via king root ( i was able to replace king root with superuser)
missing multitask button.
No front usb or audio in.
Shutdown timer set a 10 seconds, unable to change so far.
Dos not have configurable reserve camera lines ( most cameras come with lines integrated anyway.)
Both units have the same cpu.
Both units DVR are crap,most of the time they ether crash or fail to start.
The Eonon GA1312 has most setting integrated into the android control panel while the other unit has several other apps to change settings.
Also the Eonon GA1312 seems to have slightly better sound out of the box.
Hope it helps
Erisin a3090 a3090aen 3090aen android quadcore
After extensive reseach ,I also considered a couple of options.
I have a supra mk4 1993. It's double din sits quite low, so opted for a single din with fold out display. So i used the upper part of the space..
Also considered the dvb and TV for posible future uses.
Also there is a reverse camera input with reverse sensor contact as well as the expected dvr with the plug and play USB camera.
I tried a couple of USB cameras and the unit crashed or the app crashed, thought it was a pile of cap,* however I read that it has to be the camera supplied by Erisin. After purchase, the camera has been 100% . Dvr loop, 3 ,5 and 10 mins with option to use specific memory, adjustable up to 500mb.
Not tried the reverse camera as yet.
The Bluetooth works well, I have connected the android phone via Bluetooth for music and the torque unit. They work as expected.
However I did find that on occasions, the phone would knock off when I tired to activate the obd2 Bluetooth adaptor. ( got a converter adaptor on ebay £14)
I got around this by connecting the phone first.
I've not yet tried to connect 3 or more devices as yet.
The 4 really annoying thing are,
1. When on a Bluetooth call, you cannot access the android unit. It seems to lock on to the call screen.
2. Fast processor,* my arse.* More like missing a couple of cores. Slower than my galaxy s5. But fast enough for the pleasures it brings.
3. The Google voice app and other voice apps say error when trying to use. "Mic not working", (something like that).
The mic works normal on the phone and the voice memo apps.
The same happened on another new unit.
4. It seems like there is a limited memory for apps. Can't seem to change where they are stored.
I got about 6 apps totaling around 600mb. And it ran out of storage.
Other things like no AM Radio.
The screen only folds up to 90° angle exactly, so if it's low down on the dash, it may be an issue.
No mic on the dvr they provide,* or the app doesn't support it.
The Satnav could do with having the speed cameras info. But It didn't,* it does have the option to warn for it and others, in the settings though.
The WiFi works well if very close to the antenna otherwise seems to go weak very fast when creating a small distance.
I tested it with a new extended wifi antenna, and actually got a slower speed, but that could be a faulty lead!
I actually was able to test 2 units as I wanted to make sure that my initial unit was working as it should.
And it was. So I returned the second unit after extensive comparisons on data speed and app response times etc.
Despite the problems, I am sure I made the correct decision.
Amazing piece of kit considering I'm updating an old double din of 10 year old with satnav etc.
I use it via a "hotspot" , from my phone. Works really well.
Memory locations and availability work well.
Sound is great.
Ended up costing me £215 after I complained about the mic thing.
I'm sure that another app is blocking the mic from working on the Google thing and other voice apps.
Any or update would be really appreciated to help with my issues above.
I hope I have been of some help.
Contact me at [email protected]
Thanks
Is this a MTCB unit? Can I install Malaysk ROM on it?

mtcb stock/maylay roms 6.0.1 bluetooth error

As soon as my phone updated to 6.0.1 the bluetooth for phone connection connects for a few seconds and then cuts off. It seems to be very repeatable across phones and radios as until a week ago I had 2 mtcb devices both running 4.4. I have not tried the maylay 5.1 for mtcb devices yet, as I would have to set up everything for the wifey again on hers.
This does not happen with the mtcd devices with 5.1.1. It connects fine. I may just have to put 5.1 on hers to make my phone connect.
I have the joying 10.1 universal. If anyone wants to know what I think of this unit because I saw some questions about it, it seems fine. The stock software sucks and is slow. It has no micro usb ports although the rom thinks it does. Guessing they are just not plugged in. The stock microphone is 1000% better than I have seen on any other unit. I have had GS KGL and now a joying. There is no reason for an external. Even google understands me.

Issues with Android Auto

Hey, do you guys get Android Auto to work fine on a car? I tried it recently with VW Passat and Opel Insignia (both 2017 models) It didn't connect to Passat, and was hanging every 2-5 minutes in Insignia. When it hung, it still worked on the phone, but the interface on the car got frozen and unresponsive.
JakubAnderwald said:
Hey, do you guys get Android Auto to work fine on a car? I tried it recently with VW Passat and Opel Insignia (both 2017 models) It didn't connect to Passat, and was hanging every 2-5 minutes in Insignia. When it hung, it still worked on the phone, but the interface on the car got frozen and unresponsive.
Click to expand...
Click to collapse
i recommend to take to service center
cause android auto is limited and it s not easy like phones to flash another firmware and etc
:good:
What do you mean by Android auto being limited? I am talking about the phone piece since it's quite clearly some issue with the phone - the same cars work fine with my girlfriend's Samsung

Categories

Resources