Hello everyone.
I was using UleFone Power 3 (Android 7.1.1) with my RCD330+ without any problems (on VW Golf Mk6 2011 year).
However, phone became old and started developing issues, so I was forced to buy new one.
A few weeks ago I purchased Realme GT Master Edition which runs Android 11.
However, now I am having problems since day one with the phone and RCD330+.
When using Waze, the display on RCD completely freezes for 30-40 seconds every 3-5 minutes. You can pass a few intersections with Waze still showing you frozen far behind. Everything is frozen - map, speed display, etc.
After ~30-40 seconds, it unfreezes and is displayed all fine again for next 3-5 minutes where it freezes again and all repeats.
Could anyone please help me toubleshoot where the problem is?
Only the phone has changed, no configuration changes were done in RCD330+, USB cable also remained the same.
RCD330+ firmware version 5614
Android Auto version 7.6.621703-release
Waze release 4.82.5.1
Another question - what's the best tool to use to switch off Bluetooth after device is being disconnected from USB?
Thank you
I'm having the same problem and I managed to reduce a little bit the freezing. And don't know if it'd work for you.
Enable developers options and go almost to the bottom, under applications there's an option called "Limite de procesos en segundo plano" which might be something like "Limit backgroud processes" and set it to MAX 4 instead of Standard.
It helped quite a bit. Please let me know if you find something else.
Related
Anyone else with this phone using Android Auto? I've been having issues with my Kenwood DDX9207S head unit where it sometimes doesn't initialize AA properly, is more often than not very laggy, etc. Sometimes it runs smoothly, as I would expect for a phone of this class with these specs, but it's getting pretty frustrating. I've tried clearing Android Auto's data/cache and uninstalling and reinstalling it, but nothing seems to help. I'm not sure if it's an AA issue, phone issue, or possibly the head unit (very doubtful, but the screen sometimes stays stuck on AA after disconnecting the phone). I can sometimes resolve the issue simply by unplugging and replugging the phone in, sometimes I have to kill all app processes, and sometimes I have to flat out reboot the phone.
EDIT:
Did some testing last night and this morning during my commute (I sit in a lot of traffic, don't worry) and found a possible culprit: Settings. I looked at the memory usage for apps, and without fail, everything was using very little memory except Settings, which was eating 100-300mbs. Killing the process instantly made AA responsive again, but within 5-10 minutes, I was seeing lag again, and Settings was building up memory usage. I'm going to perform a factory reset on the phone today to see if that alleviates the issue.
EDIT II:
After factory resetting the phone, I'm not seeing issues, SO FAR, with AA. The settings thing wasn't the right target. I still get high RAM numbers with it regardless, and I see the same thing on my Tab S2, so that's obviously not what was causing the issue. The difference *might* be that I disabled a lot of AT&T bloatware before, and in doing so might have messed something up. I'm leaving everything enabled right now, so we'll see how this goes. I only have one car ride under my belt so far, so it's not a very scientific comparison.
EDIT III:
Ran into the exact same issues earlier this afternoon. Plugged the phone in, got the "Accept" screen on my head unit, and then blank. I looked at my phone and realized that AA didn't actually launch, so I unplugged it and plugged it back in. It launched that time, but the lag was there. I can take up to 10 seconds for AA to register a touch, and Maps freezes up constantly for 10 seconds or so before trying to catch up (it usually doesn't catch all the way up before it freezes again). This makes AA more or less unusable for me. I can't find anyone else out there that has had these issues with AA and this phone, so I'm unsure of what the issue actually is. The only difference between last night and today is that last night I was listening to podcasts through Pocket Casts, and today I used Audible. I'll do a bit more testing with/without Audible to see if that's the culprit; I know AA support is relatively new on Audible (though it was in the beta for a while). Again, I haven't seen anyone complain of poor AA performance while using Audible, so I don't know if that's the issue. I wish I had a Nexus to test this against to see if its the phone...
Having the same issue it does not connect all the time
Workaround that works 100% of the time for those having trouble connecting.
Unlock phone and turn on car or head unit. Note you should have android auto installed already before this will work. Plug in the cable to your phone and you will hear the link sound and the screen on your phone will flash off for just a second. As quickly as possible once the screen goes black on your phone uncable the phone and reconnect it. I know this sounds janky, but it really works. You can tell it is working by the screen on your head unit going black in the background and you will see the android auto icon sI have tried all suggested fixes and this is the only one that works 100% of the time. It also does not take over the telephone's display so you can navigate to other apps and still have android auto running. It is quick and gives you the best of both worlds. I almost returned my 2016 gti due to the frustration from this issue, but now it is no big deal.
Hope this helps guys and gals.
No. For what I read , the only API available for 3rd parties are to send messages and music, and that, using google interface. No other developer can do anything with AA.
I'm not sure if this has to do with recent updates to Android Auto or if it's specific to the make and model of my device (I got the new phone around the same time as the latest AA updates were released), but I'm now experiencing endless frustrations with constant connection failures between my phone and my Jeep's Uconnect 8.4 head unit again. I went through a similar thing, as did many others, around this time last year and the year before. It's infuriating.
Most of the time, when I plug my phone into the vehicle's USB port, the Android auto icon appears on the display of the head unit for a moment or two and then disappears. There's a notification in the shade on my phone that says something like "Connecting to Android Auto" or "Starting Android Auto." But then it never really starts.
Occasionally I try clearing the data, storage and cache from the Android Auto app and sometimes Google Play Services. Sometimes I'll also have to go into the Uconnect settings menu and tell my head unit to "Forget device." Every so often, as long as I then turn off the ignition and then restart the vehicle and then reboot my phone, this will bring me back to the Android auto setup screen and I'll be able to use Android auto for a single drive cycle. as soon as I cut the engine and unplug my phone, it's over. When I get back into the vehicle I'm back where I started: with the head unit seemingly able to recognize that an Android Auto device is connected for a moment and then Android Auto just quits out.
It's insane. Seems like Google can't just get this right. As soon as they release a build that works, they follow up with an update that completely breaks functionality.
Anyone else have a similar experience and, hopefully, have suggestions and how to resolve this nonsense?
Used my iPhone with my 2018 Challenger for a year and it worked perfectly. Switched to a Note 20 Ultra last month and it worked for about 2 weeks. Same issue you're experiencing. I'm going back to iPhone.
I've found that my phone has *the most annoying bug* with Android Auto - AA will work absolutely fine when you connect the phone, but then freezes / stops responding as soon as the phone's screen timeout expires and the phone auto-locks.
AA doesn't freeze, when using the same cable and same car, if I swap the phone to being my OnePlus 8 Pro - which suggests this is definitely a Find X3 Pro issue
(I'm on the 15 firmware, and at the moment can't get it to update, no matter what I do)
@stuclark
I'm on a UK unlocked device and mine won't update either . Still on A15.
That said I tested AA for 2 X 30min trips ( WFH still ) and did NOT have this bug .
I have seen it mentioned in Oppo advert threads on Facebook , they responded each time saying they were aware and working on it . So far I do not put much faith in their updates though.
mgbosshogg said:
@stuclark
I'm on a UK unlocked device and mine won't update either . Still on A15.
That said I tested AA for 2 X 30min trips ( WFH still ) and did NOT have this bug .
I have seen it mentioned in Oppo advert threads on Facebook , they responded each time saying they were aware and working on it . So far I do not put much faith in their updates though.
Click to expand...
Click to collapse
Thanks for the reply - I guess we'll wait to see what the firmware update brings (I've tried uninstalling and re-installing AA, but that doesn't downgrade me to an older version I can use). I'll have a go on facebook and the ColorOS forums
@stuclark . Probably worth opening ticket on chat / Twitter DM with them so they are aware. The more the better.
Not surprisingly, the answer from Oppo is:
It's an Android Auto bug. It will be fixed when they release a new version. Until then, set the screen to stay on whilst the phone is charging (in developer options)
Yup. Welcome to Oppo.
Seems the bug has been present for the year the X2 has been out. So dont hold your breath on a fix.
For me it worked to shut down the always on display function
stuclark said:
I've found that my phone has *the most annoying bug* with Android Auto - AA will work absolutely fine when you connect the phone, but then freezes / stops responding as soon as the phone's screen timeout expires and the phone auto-locks.
AA doesn't freeze, when using the same cable and same car, if I swap the phone to being my OnePlus 8 Pro - which suggests this is definitely a Find X3 Pro issue
(I'm on the 15 firmware, and at the moment can't get it to update, no matter what I do)
Click to expand...
Click to collapse
Try turning off always on display, worked for me.
Good evening I live in France and I test Android auto because some of you have problems with the application and I wanted to know if it was the same with my X3 pro. I use the app for over an hour and don't notice any worries. Good luck to all
P.S: I'm under the latest oppo update with the A17
uzumakinaruto69 said:
Good evening I live in France and I test Android auto because some of you have problems with the application and I wanted to know if it was the same with my X3 pro. I use the app for over an hour and don't notice any worries. Good luck to all
P.S: I'm under the latest oppo update with the A17
Click to expand...
Click to collapse
Thanks for your answer - Android Auto does indeed seem better under A17 than the previous (UK certainly) A15 release.
It also helps to turn off third party navigation apps, such as Sygic or Waze - these seem to exacerbate the Android Auto issues with this phone (but work perfectly on other devices)
Images on the lock screen, crash the Android Auto. It is an OS problem. Here is what to do, till the problem is solved :
-Go to Settings, Security, Smart Lock and and your car a trusted device. That way you have your phone unlocked while driving and fingerprint disappears.
(You can also remove fingerprint from lock screen by going to Settings, Passwords & Biometrics, Fingerprint, Screen-off unlock and select off, but then you have to wake up your phone before being able to use fingerprint)
-Go to Settings, ..Always-On Display, Always-On Display and disable it. (You can also select Always-On Display with battery saver, which turns off image after some seconds, but on those seconds, the Andriod Auto is crashed)
Good day everyone, I'm having a really frustrating problem since I got my phone a month ago. I hope I can get some help here.
From day 1 I've had issues with network on my WiFi. No issues connecting to it, no issues using the internet, let me explain. I first noticed it on MIUI Themes. That was the first thing I went into after setting up my phone. It kept saying "can't connect to network". I figured it was a bug and will be fixed in the 12.5 update (spoiler alert: it didn't). Then I started to notice during setting up of my accounts, discord, reddit, etc. that the login was incredible slow the first time. It would just keep loading when I hit next. Not long after, I downloaded a game and it refused to update saying "can't connect to server". I had to start the process with my data then switch back to WiFi. For clarity, once I'm in the game itself there's no issues, the stability never drops, I never lag, etc.
It became truly evident it wasn't isolated incidents when I would open one of my online shopping apps. It loads the main screen instantly but when I switch the tab to see notifications, the page would load but the notifications would take up to 30 seconds to load. If I clicked on it, the next page would take another 30 seconds to load. Since I've used this app on my previous phone/ipad on the same WiFi I could tell there was something wrong. It should be instant. I opened up MI Community app and I kid you not, it must have taken me 10 - 15 minutes to create an account with all the loading/lag. Every single time I open the app, it takes at least 40 seconds to a minute to load with other pages lagging as well.
I started this long process of trying everything I could find that talks about it which was not much and usually about older phones. I tried everything I could find except factory reset (some have said it doesn't fix it after trying it themselves). I tried all the WiFi adjustments, traffic mode, off private DNS, developer mode options, and obviously reset networks/router/reboot multiple times.
After spending a couple of hours trying to find every mention of this whether it's Youtube, websites or Reddit and trying them (I would switch them back to default after testing the suggestions as they didn't work), my PC started giving WiFi problems. It NEVER gives problems but I figured maybe it was due to the turning on/off router multiple times. I was so frustrated, I was like, screw this I'm done.
I restarted my PC and switched to my PS4 (which runs on the same WiFi with no issues ever in 3 years). As my PS4 booted up, I picked up my phone to check the delivery status on my shopping app and BAAM! For the first time since I downloaded the app, my notifications appeared instantly like it should, the next page loaded immediately. I was like, hold up... I went into MI Community app and BOOM! it loaded immediately, I was shook. One final test, MIUI Themes that has never worked properly since day 1 with its constant "can't connect to network". BLAAM! Every page, instant, clean sweet speed. It felt like a whole new phone, like the new phone that I was supposed to feel all along.
I enjoyed a good 6 hours of bliss, constantly checking my shopping status just as an excuse to enjoy witnessing the speed. He giveth and then he taketh away and as luck would have it, there was a power outage midday. When the power was back on and the WiFi was up, we were back to the suffering. I tried to restart my PC as that was the key trigger and it worked for about a minute and then was the end of it. No amount of shutting down / restarting PC/router fixed it again.
There's something blocking the connection between my router and phone I believe. I figured the initial restart PC fix stopped the connection to the PC and gave the priority to my phone, if you will. That's rubbish I know because my WiFi runs on 4 other devices and never lags.
I'm no tech expert, in fact, I'm the opposite of that, it's embarrassing. I hope y'all can see something I'm unaware of and guide me. I'm certain the phone isn't defective and my WiFi is fine on every other device not to mention it ran flawlessly for 6 hours while other devices were also using the same WiFi.
If you've read this far, thank you very much. I apologize the post is very long, I wanted to get everything in so it paints a clear picture of the issue. I'll add a TLDR just incase.
TLDR: WiFi issues from day 1 in 2/3 of apps mostly with initial connections. 1 month later a chance restart of my PC fixed it. Power outage later that day, problem returned.
T