Hey guys, recently got an Android head unit for my 2008 GTI, and while it was working well enough for the first couple days, today the bluetooth suddenly stopped seeing any device. Nothing shows up in the bluetooth menu and it just searches endlessly. I did a factory reset, and surprisingly it not only fixed the bluetooth issue, some other stuff started working like the car info app. But the fix was short lived as later in the day the bluetooth issue came back, not able to detect anything.
I have done as much searching as I could, but it is difficult with how fragmented these Chinese units are, and how they are so similar but slightly different. I have read that it may be possible to flash different MCU versions but would like confirmation before i try anything. Here is all the info I can get about mine, first this is the one I bought:
https://www.amazon.com/gp/product/B06XY2C1WC/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1
Model: px3 (1024x600)
Android Version 7.1.2
Kernel version: 3.0.101+
MCU Version: MTCD_ZYC_v2.55_1 June 23 2017
CPU Arm Cortex A9
Any help would be appreciated, I got Android Auto working and its awesome, but not having bluetooth for calls is a deal breaker for me...
I messed with the stereo tonight and got the bluetooth working again by simply pressing the small reset button that seemed to actually power cycle the device. I also decided to disable the backup camera mode as I dont plan on installing the camera any time soon, so I cut the wire labeled backup and that seemed to do the trick as now when it is put in reverse, it doesnt load up that blank screen. Strangely enough though, when using Android Auto through Headunit Reloaded, it still went blank when put into reverse, like it can still tell. And when the video comes back it had artifacts all over the screen, but only in that program.
jay-red said:
I messed with the stereo tonight and got the bluetooth working again by simply pressing the small reset button that seemed to actually power cycle the device. I also decided to disable the backup camera mode as I dont plan on installing the camera any time soon, so I cut the wire labeled backup and that seemed to do the trick as now when it is put in reverse, it doesnt load up that blank screen. Strangely enough though, when using Android Auto through Headunit Reloaded, it still went blank when put into reverse, like it can still tell. And when the video comes back it had artifacts all over the screen, but only in that program.
Click to expand...
Click to collapse
You only had to go to factory settings and set no reverse camera without cutting anything
Enviado desde mi SM-G950F mediante Tapatalk
ikerg said:
You only had to go to factory settings and set no reverse camera without cutting anything
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
I looked through the factory settings and could not find anything related to the backup camera
Related
I need some help. A while ago I was having issues with the mic on my LG G Watch so I decided to send it to them and see if they could fix it. I just got it back now and they said they replaced a chipset in the watch or something and now the mic seems to be working. The issue now is when I got it back from them, the watch has seemed a bit buggy. And I keep coming across this hidden menu of debug type tests and things. So I went into the about device section of the watch and something didn't seem right.
It said:
Software version:
KKWT
Build number:
platina-userdebug KKWT
OPENMASTER
eng.yjyj.kim.20140818.1125
39 test-keys
This doesn't seem like what I though it should say normally. So I tried factory resetting the watch and after I got it set up again, I went into the settings and nothing was different.
Any ideas on how I can revert this back to the correct version of android wear or something?
My Moto360 has started not displaying a card notification when receiving a message via WhatsApp. All other notifications are vibrating and switching on the display with card, but WhatsApp it just vibrates.
I have tried uninstalling and re-installting whatsapp, tried re-syncing the apps, but WhatsApp continues not to switch the screen on ... any ideas?
You haven't blocked whatsapp from showing notifications on your 360? Its easily done by accident. You might have swiped then clicked on block this app. If you go into your wear settings, then blocked apps, check to see whatsapp isnt there.
Sent from my SM-G920F using Tapatalk
Nope, checked that .. nothing in the Blocked Apps. The phone vibrates, so it is getting the notification, but unlike all the other apps which vibrate and switch the screen on, this just vibrates. When I wake the screen, the notification is shown
Yeh, sorry, when I re-read your post I realised you couldn't have whatsapp in the blocked list if you are getting the vibration. #facepalm ?.
I had a similar issue with not receiving cards for my outlook work emails on a different device to my 360 a while back, it turned out to be an app I had used to set a custom vibration pattern for my outlook notifications. Im guessing that if you had a similar app installed you would have checked that.. also Im sure you would have tried a restart of your 360..
I think the problem is with your 360 as your phone is clearly pushing the notification to your 360 if you are getting the vibration. I know an app resync usually fixes most issues but as you've tried that what about a factory reset of your moto 360? I know its a bit drastic but I don't know what else to suggest.
Sent from my SM-G920F using Tapatalk
Tried a reset as well ... the funny (annoying part), is that the screen on notification did work for a while, and then just suddenly stopped, withouth me installing anything, so not so sure it is an issue with the Moto 360, as all other notifications pop up ..... WhatsApp is the only one that does not
Yeh thats really odd. Maybe someone else will have a suggestion that can fix it. What version of the 360 do you have? Ive got the smaller mens 2015 version. I'm at the end of my tether with it tbh for other reasons. The lag on the the device is so bad for me its virtually unusable by the end of my working day. Im gonna sell it and get the watch urbane instead.
Sent from my SM-G920F using Tapatalk
I have the 1st Gen, and to be honest I am more than happy with it, even with the outdated processor in there, don't really get that much lag with it .... and taking it off charge at 7 in the morning, and putting back on around 10pm ... still gettng about 40%+ battery left.
Surprised the 2nd gen (2015) version that you are having lags with it, have heard it was supposed to be rock solid
What other issues you having?
I get "android wear has stopped working" at least twice a day. Which means it can crash without me knowing so i miss notifications and calls throughout the day. Thats my biggest gripe at the moment. Then the lag progressively gets worse throughout the day, the only way i can fix it is to do a reboot but at its worst it can take 2-3 minutes for me to get into settings then another few minutes for each option in settings to load before i can choose restart device. I tried a factory restore last night but its already crashed 3 times today..
When i compare it to my other smart watch my 360 doesn't have that 60fps smoothness when navigating the interface. I did read that if you disable ambient then the lag isnt so bad but i like having ambient on.
I'm planning on making a YouTube video of how bad it is over weekend.
Sent from my SM-G920F using Tapatalk
I initially had the android wear stopping issue with mine, what I tried was a reset of the watch, removed all pairing with the phone, and then installed an older version of Android Wear .. think it was 1.1 (do a search on google, you will find a load of links). Then reset my watch up to the phone .... but .... tried running on Android Wear 1.1 for a few days, and it was stable. I then upgraded the Android Wear 1.4 through the Play Store (make sure to disable auto update, whilst testing, otherwise off it will go), and mine has been rock solid
albie999 said:
I initially had the android wear stopping issue with mine, what I tried was a reset of the watch, removed all pairing with the phone, and then installed an older version of Android Wear .. think it was 1.1 (do a search on google, you will find a load of links). Then reset my watch up to the phone .... but .... tried running on Android Wear 1.1 for a few days, and it was stable. I then upgraded the Android Wear 1.4 through the Play Store (make sure to disable auto update, whilst testing, otherwise off it will go), and mine has been rock solid
Click to expand...
Click to collapse
Thanks for the reply. I think I'll try out your suggestion now. Need my watch working, I've come to really rely on my watch for notifications as I can't have my phone on during working hours. It got so bad today with the lag and crashes I had to use my Razer Nabu instead of my Moto360.
Fingers crossed, I'll let you know how it goes [emoji106]
Sent from my SM-G920F using Tapatalk
The 2nd Gen really should not be that bad, as said, I have the 1st Gen and to be honest, hardly any lag, so hope this workaround works for you
albie999 said:
The 2nd Gen really should not be that bad, as said, I have the 1st Gen and to be honest, hardly any lag, so hope this workaround works for you
Click to expand...
Click to collapse
As the moto 360 2015 doesn't have a cable, its wireless charging only, how would you reflash a previous version of wear? Im kinda stumped lol
Last night I did another factory reset and i uninstalled a lot of apps that i didn't want running on my moto. Some apps seem to have a companion wear app for their mobile equivalent that automatically install.. Well ive taken a lot of crap off and i have seemed to have fixed the stability issue. Also i can use my device albeit with a small amount of lag. This i can live with for now, it seems that moto knows about "always on" causing lag on some devices. I'll hold out for an update to fix it [emoji106] [emoji3]
Sent from my SM-G920F using Tapatalk
Ah, should have said .. it is not Android Wear on the watch, but the companion android wear on the phone that I installed an older version. Don't believe you can actually change the version on the actual watch
I have ambient mode off, wifi off (dont really see the point) and tilt to wake off ... as it kept coming on when I changed gear in the car lol
install quick for wear
i know it's an old thread, but i still have the problem in android wear 2.0.
whatsapp notifications are extremely unreliable. it's like the developers do every single thing their own way.
i set my watch to show notifications until i swipe it away or down, the very few times whatsapp actually shows the notification it goes away after a few seconds.
the notifications do work, as i can manually swipe to the notifications and they're there. they just refuse to show automatically.
i'm not a heavy user, so i get few notifications of which most of them are from whatsapp. so my watch functions more like a normal watch.
Whattsapp issues wear 2.0
I too get a buzz but no card till I manually swipe up anyone managed to fix this whattsapp support are useless auto gen email each time
Recently picked up the 6P (still stock on lastest FW) and have only one issue with it.
When I am steaming audio over bluetooth in my car (usually using Play Music), if I wakeup/unlock the device, the audio stutters/lags for a good 5-10 seconds before going back to normal. Once awake, dragging down the notifications menu can cause a similar effect though less pronounced. If I turn the screen back off, it goes back to normal instantly.
I don't have any other BT devices to test this on, but I've not had this issue with any other androids in my car. I also don't see any "lag" issues anywhere else. Before I unlock and root this thing, any ideas on how to fix it on the stock rom, or is a custom rom not likely to fix this either?
Appreciate it.
codeman05 said:
Recently picked up the 6P (still stock on lastest FW) and have only one issue with it.
When I am steaming audio over bluetooth in my car (usually using Play Music), if I wakeup/unlock the device, the audio stutters/lags for a good 5-10 seconds before going back to normal. Once awake, dragging down the notifications menu can cause a similar effect though less pronounced. If I turn the screen back off, it goes back to normal instantly.
I don't have any other BT devices to test this on, but I've not had this issue with any other androids in my car. I also don't see any "lag" issues anywhere else. Before I unlock and root this thing, any ideas on how to fix it on the stock rom, or is a custom rom not likely to fix this either?
Appreciate it.
Click to expand...
Click to collapse
It's a problem at the source code. It's says it's been fixed on Developer N preview 3. So when N is released publicly it should be fixed. Or you can join the beta program. I have preview 3 running now and it's pretty solid. I don't use bluetooth audio though, so I can't say if it is indeed fixed. If you do try it be sure to enable OEM unlocking in Android dev settings just to be sure you can save your device should anything happen. Also check the list of supported apps so if any app you rely isn't supported you can decide from there.
Sent from my Nexus 6P using XDA-Developers mobile app
Gizmoe said:
It's a problem at the source code. It's says it's been fixed on Developer N preview 3. So when N is released publicly it should be fixed. Or you can join the beta program. I have preview 3 running now and it's pretty solid. I don't use bluetooth audio though, so I can't say if it is indeed fixed. If you do try it be sure to enable OEM unlocking in Android dev settings just to be sure you can save your device should anything happen. Also check the list of supported apps so if any app you rely isn't supported you can decide from there.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Gotcha, that's what I was afraid of. Will checkout the N Preview, thanks!
codeman05 said:
Recently picked up the 6P (still stock on lastest FW) and have only one issue with it.
When I am steaming audio over bluetooth in my car (usually using Play Music), if I wakeup/unlock the device, the audio stutters/lags for a good 5-10 seconds before going back to normal. Once awake, dragging down the notifications menu can cause a similar effect though less pronounced. If I turn the screen back off, it goes back to normal instantly.
I don't have any other BT devices to test this on, but I've not had this issue with any other androids in my car. I also don't see any "lag" issues anywhere else. Before I unlock and root this thing, any ideas on how to fix it on the stock rom, or is a custom rom not likely to fix this either?
Appreciate it.
Click to expand...
Click to collapse
Hey! I just found this post. I have had the same issue on my 6P since receiving it in November. I was stock until just a few days ago, now just running 6.0.1 and xposed. The issue fixed itself right after I wiped and rooted, but is now back. This is odd because booting my phone into safe mode didn't fix the issue, so I'm thinking it's not caused by a specific app, although I'm yet to try it.
Since you mentioned you don't use other bluetooth devices, this problem ONLY exists for me in my car audio, a 2015 Chevy Cruze.
If you don't mind me asking, what car are you driving?
Shocknoble said:
Hey! I just found this post. I have had the same issue on my 6P since receiving it in November. I was stock until just a few days ago, now just running 6.0.1 and xposed. The issue fixed itself right after I wiped and rooted, but is now back. This is odd because booting my phone into safe mode didn't fix the issue, so I'm thinking it's not caused by a specific app, although I'm yet to try it.
Since you mentioned you don't use other bluetooth devices, this problem ONLY exists for me in my car audio, a 2015 Chevy Cruze.
If you don't mind me asking, what car are you driving?
Click to expand...
Click to collapse
I have the exact same problem with my 2015 Chevy Volt nav / stereo system. I never noticed this issue until I updated to the Android N release a few days ago. It always happens when I turn on the screen. I rooted and went back to Android M, but the issue is still there. I'm guessing that's because my phone now has the latest baseband and radios instead of the older ones that did not have this Bluetooth problem. If you guys come up with a fix let me know. I'm thinking of flashing the Android M radios to see if that's the problem since I'm now running a custom Android M based ROM anyway. I tested the phone with my wife's 2016 Mazda CX5 and it has none of this screen on stuttering garbage.
UPDATE: I went ahead rooted, installed Pure Nexus ROM (6.0.1-20160821), installed ElementalX-N6P-1.21 kernel, flashed bootloader-angler-angler-03.54.img and radio-angler-angler-03.61.img from angler-mtc20f-factory-d62de11e.tgz, and after all that the issue is still there! What a complete waste of time. What I'm guessing might be the problem is I switched to Sprint on July 2016. Before that I was on T-Mobile and I never had this screen on stuttering issue. It seems there might be some type of interference here and it's possible it is a hardware design flaw since Google has not been able to fix the issue for quite some time. As of now I've switched to my LG G5 phone which has no Bluetooth issues with my Chevy Volt. If I don't find a fix soon I'll probably sell the Nexus 6P and wait for the newer Nexus devices.
FWIW, I have the same issue with my 2014 Chevy Cruze and my HTC 10. Ran across this thread while hunting down a solution (unsuccessfully, this far).
macmanui said:
FWIW, I have the same issue with my 2014 Chevy Cruze and my HTC 10. Ran across this thread while hunting down a solution (unsuccessfully, this far).
Click to expand...
Click to collapse
I figured out that if I uncheck Message Access for my Chevy Volt under my phone's Bluetooth settings, the screen on stuttering is fixed!! Everything works flawlessly with my wife's Mazda CX5 so it must be a Bluetooth compatibility issue. Check it out and see if that resolves your HTC 10 issue with your Chevy. Good luck!
I have found a somewhat reliable fix - PLEASE tell me it works for you all as well.
Hopefully we are all familiar with the problem: A Nexus 6P ( Or whatever is the issue for you) is paired with my 2015 Chevy Cruze that I use to stream audio while commuting. The audio is more or less fine until the screen turns off/I lock the phone. Once I unlock the phone or a notification wakes the screen up, the audio stutters over my car speakers until I turn the screen back off, or 6-8 seconds has passed. This doesn't happen with any other device I own when paired to my car, and my phone doesn't have the same issue when paired with any other bluetooth receiver. I am on a rooted but otherwise stock 6P running 7.0.
I do not use my car for messages, only music/podcasts and phonecalls. I went into the bluetooth settings while driving ( I do not recommend you do this while your car is in motion) and noticed the stuttering was consistent the entire time I had the menu open. This prompted me to assume it must have something to do with the phone making other bluetooth actions while connected to my car, that my car didn't like.
I clicked on the gear for settings next to my car in the bluetooth paired devices list, which pops up the menu that lets you change the name of the device, and what it is used for. My options are: 'Phone Audio', 'Media Audio', 'Contact Sharing', and 'Message Access'. I denied message access to my car the last time it prompted me, but the last two on the list were still checked. I unchecked both of them, reset my phone, and crossed my fingers.
It works. It freaking works. It's not 100% and if I flip the screen on and off over and over again it'll still get a little wonky, but I no longer cringe when I have to unlock my car in the phone.
Will the rest of you give this a shot and let me know if you have similar luck? Best wishes!
Josh
---------- Post added at 01:50 PM ---------- Previous post was at 01:46 PM ----------
mhajii210 said:
I figured out that if I uncheck Message Access for my Chevy Volt under my phone's Bluetooth settings, the screen on stuttering is fixed!! Everything works flawlessly with my wife's Mazda CX5 so it must be a Bluetooth compatibility issue. Check it out and see if that resolves your HTC 10 issue with your Chevy. Good luck!
Click to expand...
Click to collapse
You're totally right. I discovered this on my own right about the same time you did apparently and I wanted to make sure it lasted before I made a post here. You deserve all the credit, I'm just so happy it's fixed. Now, I am curious if it'll still stutter a bit if you turn your screen on and off really quickly a few times?
---------- Post added at 01:50 PM ---------- Previous post was at 01:50 PM ----------
mhajii210 said:
I figured out that if I uncheck Message Access for my Chevy Volt under my phone's Bluetooth settings, the screen on stuttering is fixed!! Everything works flawlessly with my wife's Mazda CX5 so it must be a Bluetooth compatibility issue. Check it out and see if that resolves your HTC 10 issue with your Chevy. Good luck!
Click to expand...
Click to collapse
You're totally right. I discovered this on my own right about the same time you did apparently and I wanted to make sure it lasted before I made a post here. You deserve all the credit, I'm just so happy it's fixed. Now, I am curious if it'll still stutter a bit if you turn your screen on and off really quickly a few times?
Seems that GM vehicles are a common denominator too! I have the stuttering with my 6P int my Holden Cruze. Didn't have the issue with my old Nexus 6 and don't have the issue with the 6P when making calls over BT. I haven't listened to as great deal of music from the 6P over BT except in the car so can't really compare there.
It's interesting to read a comment that it was going to be fixed in M preview 3 but even now in Marshmallow release the issue is still there.
Hi, been suffering with a stutter in my Mercedes every 20mins with a 5X on 7.0. Again, seems a common problem with Mercs. I tried EVERYTHING to fix this for months, including full phone wipes and flashes.
I just fixed my issue entirely, not sure if it will work for you guys, but I believe it is an issue with the BT bandwidth that the car is able to cope with. I turned off Phone Book and SMS Message Access services and my issue is gone. I think the phone is maxing the bandwidth with A2DP and as soon as a sync is requested for phone book or message = the problem arises.
Pica_Man said:
Hi, been suffering with a stutter in my Mercedes every 20mins with a 5X on 7.0. Again, seems a common problem with Mercs. I tried EVERYTHING to fix this for months, including full phone wipes and flashes.
I just fixed my issue entirely, not sure if it will work for you guys, but I believe it is an issue with the BT bandwidth that the car is able to cope with. I turned off Phone Book and SMS Message Access services and my issue is gone. I think the phone is maxing the bandwidth with A2DP and as soon as a sync is requested for phone book or message = the problem arises.
Click to expand...
Click to collapse
Interesting. It certainly does feel like a bandwidth issue. I have a Moto360 and has tried turning that off but hadn't thought of turning phone functions off. I don't really want to do that either but will try it to confirm.
I turned off phonebook and SMS but it made no difference to me at all.
I have noticed a Terrible shutter from my device when paired to a portable BT speaker. at times the only fix is to turn the speaker off then back on. it is horrid.
[SOLVED]
Hi All,
i have read the other posts about similar problems and although they are probably one and the same problems,
i'm slightly new to terminologies and was hoping for a slightly tailored discussion.
That being said i'm going to jump straight in with the story from the beginning,
Around 2 Months ago i bought this Head unit for my car.
Seicane - 9 Inch OEM Android 9.0 Radio 2004-2011 Ford FOCUS EXI MT 2 3 Mk2/Mk3 Manual air condition GPS Navigation system Bluetooth Touch Screen TPMS DVR OBD II Rear camera AUX 3G WiFi HD 1080P Video
I have recently received this and installed it just yesterday.
Now the problems i'm having is that when ever i use anything internet based via a WiFi dongle or hot spot on my phone then the whole system crashes out on me and i have to turn off the ignition.
Also Google is unable to grab my information, It recognizes me and goes through the 2 step verification but gets stuck after accepting agreement, the Gathering Information shows up on screen and then it just loads indefinitely until either the system or the app crashes.
now i'm not sure if these are one and the same issue but do seem very similar, Like once it has an internet connection it is trying to do a background connection to google to pull data but its getting stuck and crashing out again.
So the only way i'm able to use the system is to put it in airplane mode otherwise it crashes and makes the stereo unusable altogether.
So i have contacted Seicane in regards to this issue and awaiting a reply but figure i may have more luck talking with a community of people that know what they are on about.
So i'm going to say i probably need some kind of system update from google and firmware for the system, but cant log into google without the firmware update.
The problem i'm having is i don't know what stereo it is as such..... if someone could help me with this then i may have more luck
I assume its a MTCD board, but is it a PX6 -5 -4 or 104? i have no idea. i don't know if its even a PX...?
any help on that would be GREAT as i may then be able to download the right updates for it and maybe solve this issue that i'm having.
That being said if anyone can take some time to try and help me i would greatly appreciate it.
I look forward to hearing from you.
MANY many thanks,
Frederus
My initial thought on this is that it is probably caused by a hardware fault in the unit, rather than being a software fault. My reason for saying this is that Seicane are a reasonably popular (ie used by many people) brand, and connecting to the internet is a fundamental function of these head units. If it were a software fault, I would expect to see many more users reporting this issue since the software is in fairly widespread use. Since this seems to be (on the surface at least) only happening to your unit, I suspect it is a hardware fault. It would be interesting to see what the manufacturer has to say when they get back to you. Good Luck!
Update
So i have an update for everyone with some Progress.
So after talking with Seicane they sent me a firmware update it was about six months out of date.
After installing this it seems to have helped with the continues crashing issue i was having.
that being said i then lost a few apps like
Netflix, Spotify and my DAB+ app
They also sent me some APK's for Google services and login services, [This didn't make any difference to my login hanging issue]
So i got back to Seicane and informed them of what had transpired along with a short video of what was happening so that they could see this first hand
They got back to me by the morning and sent me the link for the DAB+ apk so i could reinstall and also forward me another set of apk's
Google Services
Login Services
Google Play Store.
i have given these a go this morning,
DAB+ is back and working
Google Services - No difference
Login Services - No difference
Google Play Store. - No difference
I have just sent them another email saying that this hasn't made any difference and await there reply.
After doing some searching i noticed a lot of people have this issue of google getting stuck on "gathering Info" on there smart phones
which is usually a Cache issue, so i will try this once i'm in my car again.
I would attach the link to the firmware update that they sent me for others who may have the same issue, but i am unable to at this moment in time due to forum limitations for new users.
Ill keep everyone informed as and when i have more information.
Update [Solved]
So its been a week or so,
Quick update after going backwards and forwards with tech support at Seicane it turns out it was a combination of the outdated APK and the fact that google was stuck due to an error with the cache, from what i can tell at least,
So in the end i removed all of the google services from the head unit and deleted the caches as well. then forced it to restart and reinstalled Google login services.
This seems to have worked and i'm not having this issue any longer.
That being said i do have an issue where it doesn't want to turn on very occasionally, but this is on a very rare basis and isn't really a problem usually just have to power down the car and reset ignition. except once where i had to hit the reset button, but 99% of the time it is now working fine.
I hope this helps someone who has the same or similar issue.
Fred.
Apologies if this is the wrong forum - newbie.
I have an Xtrons PX30 based unit and the reversing camera has become intermittent - works about 1 time 10. After spending days checking the wiring and even buying a new camera I noticed that the behaviour is consistent and therefore likely to be a software issue. The symptoms are: with the camera not working - switch the head unit off and the camera now works. Switch the unit back on again and the camera still works and will remain working for quite a while but will eventually stop working again.
I've tried factory reset and updated the MCU and the system to the latest versions I can find here:
Yandex
Finds everything
disk.yandex.com
But makes no difference (The interface is nicer though). It's liveable with but irritating.