Related
Got a 2017 VW and my old Xiaomi Mi Mix worked great with android auto being displayed on the dash.
I'm currently sitting on the 8.8.9 chinese miui 10 beta rom on the Mi Max 3 and I can't seem to get android auto to sync to the car.
Anyone else run into this?
omniphil said:
Got a 2017 VW and my old Xiaomi Mi Mix worked great with android auto being displayed on the dash.
I'm currently sitting on the 8.8.9 chinese miui 10 beta rom on the Mi Max 3 and I can't seem to get android auto to sync to the car.
Anyone else run into this?
Click to expand...
Click to collapse
I'm on miui.eu 10 global 8.8.3 and Android auto works fine.
Andy4Shurr said:
I'm on miui.eu 10 global 8.8.3 and Android auto works fine.
Click to expand...
Click to collapse
Is that the Xiaomi EU rom in the rom section?
And just to double check, Does android auto actually display on your car's screen ok? (I can launch Android auto on the phone fine)
omniphil said:
Is that the Xiaomi EU rom in the rom section?
Click to expand...
Click to collapse
It's an older version as I haven't updated yet... Don't know whether to do so as I'm happy with it as it is and my current version doesn't have anti rollback!
Andy4Shurr said:
It's an older version as I haven't updated yet... Don't know whether to do so as I'm happy with it as it is and my current version doesn't have anti rollback!
Click to expand...
Click to collapse
Does it actually connect to the screen in your car ok, Or are you just running the android auto app on your phone?
omniphil said:
Does it actually connect to the screen in your car ok, Or are you just running the android auto app on your phone?
Click to expand...
Click to collapse
Connects to my head unit display. It's in a 17 plate VW golf.
I always remove Android auto, Google, music apps, Google Maps etc from any battery saving restrictions in the settings and set them to have auto start permissions too.
Andy4Shurr said:
Connects to my head unit display. It's in a 17 plate VW golf.
I always remove Android auto, Google, music apps, Google Maps etc from any battery saving restrictions in the settings and set them to have auto start permissions too.
Click to expand...
Click to collapse
Ok thank you for confirmation, I'll see about moving over to the EU rom and see how that works for me. (Also 2017 Golf)
omniphil said:
Ok thank you for confirmation, I'll see about moving over to the EU rom and see how that works for me. (Also 2017 Golf)
Click to expand...
Click to collapse
No problem! It's one of the main reasons I got this phone over the Honor Note 10 as Huawei phones are notoriously bad for working with Android Auto.
MIUI PRO, No Dice
Andy4Shurr said:
No problem! It's one of the main reasons I got this phone over the Honor Note 10 as Huawei phones are notoriously bad for working with Android Auto.
Click to expand...
Click to collapse
My Android Auto would not work either on my phone. I am running MiUi Pro 8.9.6. It recognizes in the car and when I accept to run, it just doesn't show up. I have given it all the permissions required with no luck.
Damionix said:
My Android Auto would not work either on my phone. I am running MiUi Pro 8.9.6. It recognizes in the car and when I accept to run, it just doesn't show up. I have given it all the permissions required with no luck.
Click to expand...
Click to collapse
I'm guessing Xiaomi.eu must do something different with gapps then as Android pay also works with EU ROMs when it's based on Chinese miui which normally doesn't support that.
All I can tell you is that on this ROM Android Auto is working perfectly. It also did on my old mi mix 2 also running the EU ROM.
Andy4Shurr said:
I'm guessing Xiaomi.eu must do something different with gapps then as Android pay also works with EU ROMs when it's based on Chinese miui which normally doesn't support that.
All I can tell you is that on this ROM Android Auto is working perfectly. It also did on my old mi mix 2 also running the EU ROM.
Click to expand...
Click to collapse
Same here... Android Auto was not working on the Chinese roms, works great on the EU rom tho...
omniphil said:
Same here... Android Auto was not working on the Chinese roms, works great on the EU rom tho...
Click to expand...
Click to collapse
Glad you got it working mate, I couldn't live without Android Auto now I'm used to it!
Xiaomi.eu No Go
I tried the latest Xiaomi.eu ROM yesterday and got the dreaded Error -16 on it.
I just have no luck, and I need Android Auto work . Anyone have any suggestions?
I've got the same issue, really want AA to work again...
//Miui 10 CN stable
Ioniq electric
I can't get it working consistently on any of the EU roms newer than 8.8.9. I have filed a bug report for it in the standard MIUI forum, if it gets fixed there it should then get fixed in EU.
What you guys can do is register for the MIUI bug forum and then you can Confirm my bug report. The more people that Confirm it the more attention it is going to get so it gets fixed..
Here's a link to my bug report. Please Confirm it.
http://en.miui.com/thread-4255414-1-2.html
Done
omniphil said:
I can't get it working consistently on any of the EU roms newer than 8.8.9. I have filed a bug report for it in the standard MIUI forum, if it gets fixed there it should then get fixed in EU.
What you guys can do is register for the MIUI bug forum and then you can Confirm my bug report. The more people that Confirm it the more attention it is going to get so it gets fixed..
Here's a link to my bug report. Please Confirm it.
http://en.miui.com/thread-4255414-1-2.html
Click to expand...
Click to collapse
I have done joined your bug reporting. I hope more people voice their concerns on this topic.
Just to add some info to this... I am on MIUI 9 Global rom 9.6.8.0. I can get Android Auto to work by toggling the USB debugging in Developer settings. It doesn't seem to matter if its on or off, I just have to toggle it and android auto fires right up and connects to the car.
Very weird indeed, there is still some work needed to be done with these roms and Android Auto it seems.
Potential AA solution for Mi Max 3
Hi all - I've just signed up to post this reply, which I hope is helpful to someone at least.
Similar to a number of you, I have struggled to get AA working on the Max 3 (I received my Max 3 last week and it is updated to MIUI 10 Global Stable).
I profess to having no coding/coder/engineering background, but I have solved - with consistency - the lack of compatibility on my Skoda Superb (VAG unit). Where other phones are fine, this wasn't playing nicely.
Essentially, the car would see the phone, but when pressing one of the options on the touch-screen in the car (you choose Android Auto or Mirror Link), it would say that there is an error and to check the device was Mirror Link compatible.
After rebooting/fiddling, I managed to get it to link up once or twice from maybe a dozen tries. What I hadn't done is recorded my process of getting it to work.
Turns out it is pretty simple.
Clearing all apps from the system RAM via the menu button (three lines in MIUI 10, or, swipe up and hold for gestures) makes my Max 3 connect first time to the car without fail. I have read something about apps in the background conflicting with the messages/instructions sent and received, but hey - my layman's solution seems to be doing the trick.
If it works for you, excellent. If not, I apologise and hope a permanent solution comes along! MIUI is a strange beast with some options - some superb (individual data access via 4G and WiFI for example), some really backward (no merging of external SD to internal is criminal!).
jageanke said:
Hi all - I've just signed up to post this reply, which I hope is helpful to someone at least.
Similar to a number of you, I have struggled to get AA working on the Max 3 (I received my Max 3 last week and it is updated to MIUI 10 Global Stable).
I profess to having no coding/coder/engineering background, but I have solved - with consistency - the lack of compatibility on my Skoda Superb (VAG unit). Where other phones are fine, this wasn't playing nicely.
Essentially, the car would see the phone, but when pressing one of the options on the touch-screen in the car (you choose Android Auto or Mirror Link), it would say that there is an error and to check the device was Mirror Link compatible.
After rebooting/fiddling, I managed to get it to link up once or twice from maybe a dozen tries. What I hadn't done is recorded my process of getting it to work.
Turns out it is pretty simple.
Clearing all apps from the system RAM via the menu button (three lines in MIUI 10, or, swipe up and hold for gestures) makes my Max 3 connect first time to the car without fail. I have read something about apps in the background conflicting with the messages/instructions sent and received, but hey - my layman's solution seems to be doing the trick.
If it works for you, excellent. If not, I apologise and hope a permanent solution comes along! MIUI is a strange beast with some options - some superb (individual data access via 4G and WiFI for example), some really backward (no merging of external SD to internal is criminal!).
Click to expand...
Click to collapse
I am glad this thread is getting some attention, hopefully Xiaomi sees it....
I just went out and tried your method and unfortunately it didn't work for me, but I certainly appreciate you adding your workaround to this thread.
The workaround for me is to plug in the USB cable to the phone and then toggle the USB debugging and it connects as soon as I either turn on or off USB debugging. So as usual with these Chinese phones something is running in the background that is looking for Android Auto connections and the task managers on these phones are killing it. (toggling USB debugging must start whatever service is needed and it instantly connects) At least that's my theory anyways
Xiaomi.... Android does not need task killers! Please stop trying to "Optimize Memory", Free ram is totally wasted ram! The ram should be full of cached stuff for optimal performance, LOL
omniphil said:
I am glad this thread is getting some attention, hopefully Xiaomi sees it....
I just went out and tried your method and unfortunately it didn't work for me, but I certainly appreciate you adding your workaround to this thread.
The workaround for me is to plug in the USB cable to the phone and then toggle the USB debugging and it connects as soon as I either turn on or off USB debugging. So as usual with these Chinese phones something is running in the background that is looking for Android Auto connections and the task managers on these phones are killing it. (toggling USB debugging must start whatever service is needed and it instantly connects) At least that's my theory anyways
Xiaomi.... Android does not need task killers! Please stop trying to "Optimize Memory", Free ram is totally wasted ram! The ram should be full of cached stuff for optimal performance, LOL
Click to expand...
Click to collapse
Ah sorry to hear this.
Mine won't stay in USB debug mode anyway, but shame it hasn't sorted for you.
If it's an issue with other applications though, it would be good to figure out which one upsets it being detected right away.
I found a new rom for the XZ1 Compact.
Until now only a few regions are available. Probably the June patch.
SkyHigh76 said:
I found a new rom for the XZ1 Compact.
Until now only a few regions are available. Probably the June patch.
Click to expand...
Click to collapse
Yep. None for Customized DE just yet.
It also comes a little bit late. Am I right?
The xz1c was released on 7.31.17 and I wonder if we will get more security updates after the two years after the release date.
Flash this yesterday using the FTF found here: https://xperiafirmware.com/sony-xperia-xz1-compact/
Can't really see any difference so far, but also no issues with it
Seems to have improved GPS performance on my end. Connection is still a bit weak, but it catches more satellites and doesn't lose tracking suddenly.
The GPS bug is still there and things have gotten even worse. I use a lot of GPS (Waze) and during the weekend I experienced that three times... I just dont get it how Sony cannot resolve that issue (((
mEREHAIGE said:
The GPS bug is still there and things have gotten even worse. I use a lot of GPS (Waze) and during the weekend I experienced that three times... I just dont get it how Sony cannot resolve that issue (((
Click to expand...
Click to collapse
I came across this problem on my XZ1c, but I found a fix.
Go into airplane mode and make sure GPS is disabled.
Settings\Apps & notifications\App info - find Maps
Force stop - Storage - Clear cache - Clear data
Restart phone
Enable GPS, airplane mode off.
If that doesn't work use the following service settings number to go in the gps settings :
on your phone keypad dial *#*#7378423#*#*
Go into service tests, select gps then purge test data
reboot
mEREHAIGE said:
The GPS bug is still there and things have gotten even worse. I use a lot of GPS (Waze) and during the weekend I experienced that three times... I just dont get it how Sony cannot resolve that issue (((
Click to expand...
Click to collapse
what GPS bug is this? I can't say that I've noticed anything off when using Google Maps for directions.
Didgesteve said:
I came across this problem on my XZ1c, but I found a fix.
Go into airplane mode and make sure GPS is disabled.
Settings\Apps & notifications\App info - find Maps
Force stop - Storage - Clear cache - Clear data
Restart phone
Enable GPS, airplane mode off.
If that doesn't work use the following service settings number to go in the gps settings :
on your phone keypad dial *#*#7378423#*#*
Go into service tests, select gps then purge test data
reboot
Click to expand...
Click to collapse
OK, I'll try that and report back in a few days if it helped, thanks!
nakster said:
what GPS bug is this? I can't say that I've noticed anything off when using Google Maps for directions.
Click to expand...
Click to collapse
Usually it happens when I finish using Waze or Google Maps (or any GPS driving app) and after a while I start it again and then it just does not find any satellites. Sometimes after a few minutes its back but sometimes even an hour waiting does not help nor restart nor anything you can think of. And of course it usually happens when you are in hurry It really p....s me off when thing does not work as they should be, especially when you have no time to waist
Well, everything worked fine couple of days and then I started losing GPS again. Seems that purging test data from service menu is the best solution for this bug, sometimes I dont even have to reboot. Still that is very annoying and one more reason not to buy Sony anymore... zero customer support, all this nonsense preventing people to root their phone, bug after bug that dont get fixed etc. They just don't care about anything after you've made your purchase. I've been loyal customer with 3 different phones for 7 years but seems that current XZ1c is the last phone for me that bears the Sony label. Shame on you Sony.
SkyHigh76 said:
I found a new rom for the XZ1 Compact.
Until now only a few regions are available. Probably the June patch.
Click to expand...
Click to collapse
Can you please upload it on mega or drive if possible
Here you are:
https://drive.google.com/file/d/1-sMa_DwDyikHbzJo4zSRgZo3uBulwnX5/view?usp=sharing
Has anyone experienced loosing GPS signal after a 1-2-3 hours of Google Maps ? It may be like the device is overheating. GPS is back usually after resetting.
Anyone having this problem where call doesn't connect with error of 'Call not sent'? This is doesn't happen when connected to Wi-Fi but happens most of the time otherwise and I have to re-try 2 times (sometimes 10 times) to get the call connected. I have tried clearing data for phone app but it didn't help. I am not seeing any reports on it in any beta discussion so I am guessing its not a beta problem? It never happened before the beta update and I installed the beta update from total reset instead of just updating.
Yes. Only happens when I am on Bluetooth connected to my car. I gave to call from the phone app instead of my driver control.
"Call not sent" error on Samsung Note10
I'm having a similar issue with my Note10, just shows "Call not sent.", whether connected or not to Android Auto or any other dock/bluetooth, it doesn't seem to fix the problem.
I have tried several active sim cards from different carriers which work fine in other phones, but in the Note10 I can only access the web and text. When trying to make a call with full signal bars and LTE next to it, it just shows "Call not sent". I've done all the usual restart, full factory reset from the recovery menu, even reflashed it via Odin with the latest firmware (N970U1_UES2BTA1) three times, then factory reset again, but it's doing the same. It seems to be a hardware problem, not a software glitch.
By the way, my phone is unlocked and I have checked the IMEI to make sure it's not blacklisted. I have also examined the charging port for any liquid damage, but it's completely clean and shiny. When I dial the test code *#0011# to compare the network status screen against a Samsung S9's, I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
Also, out of curiosity I have installed a couple of different phone dialers (Google Phone and Simpler Dialer), but the outcome is the same "Call not sent.".
Evidently there's a hardware problem with the Note10 series (some or all), because Samsung's own forum full of similar complaints.:=(
Same problem. Getting call not sent
Was not issue in Android 9. Only Android 10.
Galaxy note 10+ unlocked version on tmobile.
I've also had other random Bluetooth issues.
this issue got so bad, i am not able to make calls, unless i make multiple attempts.
so i just upgraded to the S20 Ultra. Same issue!!
Here are other factors and connected devices.
Connected to a Ford vehicle (Sync; 2017 Explorer)
Connected to Samsung Active2 smartwatch (but issues remained even when watch disconnected).
I've also tried to unpair / re-pair. To no avail...
Help!
Also here:
https://us.community.samsung.com/t5...-Android-Auto-after-upgrading-to/td-p/1077007
I am really glad I blocked updates, I am still running on Pie
billa said:
I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
(
Click to expand...
Click to collapse
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
ultramag69 said:
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
Click to expand...
Click to collapse
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
billa said:
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
Click to expand...
Click to collapse
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
ultramag69 said:
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
Click to expand...
Click to collapse
Right, but usually same bootloader version updates are just maintenance or critical security updates only.
Looks like some major changes have happened in the latest update, which could be causing the no call issue.
Just checked, and it's still the same version available.
Version: N970U1UES2BTA1/N970U1OYM2BTA1/N970U1UES2BTA1/N970U1UES2BTA1
OS: Q(Android 10)
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Chiming in late to the game with a Samsung Galaxy S20. I never had this issue with the new OS on my S10 but it started happening with the S20. It's also intermittent. Sometimes it works. I have tried unpairing and repairing. I have tried deleting the bluetooth device and reconnecting it. All to no avail. At least other folks recognize this issue and hopefully Samsung issue an update soon.
i have regerts (spelled wrong to be funny)
winol said:
I am really glad I blocked updates, I am still running on Pie
Click to expand...
Click to collapse
As nice as this phone is--I am annoyed with myself that I upgraded to Android 10--everything worked so great with 9!!! I wish there was a way to go backwards. I might investigate that, actually. I have a little downtime as of late.
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
i have Android 10 ui 2.1 with infinity rom 6.0 rom N975FD and everything works perfect including goodlock 2020
winol said:
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
Click to expand...
Click to collapse
For me, Android 10, whether UI 2.0 or 2.1
battery.... standby, is exceptional good .!
I am a power user, eg theming etc
so i don't worry or have time to worry,
about SOT ETC....
For me what matters is when , my device is sleeping.....!
/ if anything
is draining my device battery etc.
( Ihave about 200./300 apps.)
Suggestion... factory reset or did you already done that.?
See examples of device overnight
standby etc.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
THIS WAS THE FIX FOR ME! I'll have to research why Android 10 isn't playing nicely with Google Voice, but I'm glad I can hit call and it goes though, instead of hitting "send" over and over and over again!!!
S10+ Exynos, running Android 10 stock - same problem. Annoying as hell!
I can't uninstall GV because I use it for international calls.
Edit: BTW - it definitely seems to be affected by connected BT headset. As soon as I turn the BT headset off I am able to make the call (using MPOW headset, don't remember the exact model).
billa said:
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Click to expand...
Click to collapse
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
dhebi111 said:
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
Click to expand...
Click to collapse
Are you (were you at the time) connected to a BT headseat? It happens to me only when my headset is connected, and not just one - two different types of headseats and also happened once or twice when the phone was BT connected to my car. As soon as I disconnect the BT, all calls can be completed without a problem.
Just checked for ****s and giggles and it was there (SIO).
I've done this update already.
Nothing new at all, just security patch.
FP sensor still not fixed.
kristoff_sz said:
I've done this update already.
Nothing new at all, just security patch.
FP sensor still not fixed.
Click to expand...
Click to collapse
Fixed as in what? The sensor is probably as good as it'll get, the A50S and A51 seem to have different hardware, so it works better. Always readd fingerprints after an update, also add 1 fingerprint with both thumbs, so it's more reliable.
kristoff_sz said:
I've done this update already.
Nothing new at all, just security patch.
FP sensor still not fixed.
Click to expand...
Click to collapse
Are you using a screen protector? To be honest my FP sensor doesn't have a problem since like the August update or so. And I never had to re-register my fingerprints again since then.
I got the update aswell, props to Samsung that was really quick security update..
Polska XEO version, Android System battery drain bug still existing. In other countries is the same thing?
wojtas2max said:
Polska XEO version, Android System battery drain bug still existing. In other countries is the same thing?
Click to expand...
Click to collapse
Confirmed: battery drain and slower system response after ASL6 update. Hope samsung can fix this in next update
A505FN - Czech Republic
After the last update with the security patch date of February 1, after the first reboot, the screen crashed, including a touch response. I eliminated this by restarting the device but I was struggling with the Internet connection. Whether I was connected via wifi or a SIM card, the screen was disconnected from the Internet and either restarting the card or the whole device helped. After several hours of experiments I found out that the culprit is the application "Blokada", after its removal everything works as it should. I do not know if the problem was caused by "tweaking" Samsung update or some art of Google security policy, in any case, until then a great ad blocking application had to unfortunately have gone from the phone .......
janzrokycan said:
A505FN - Czech Republic
After the last update with the security patch date of February 1, after the first reboot, the screen crashed, including a touch response. I eliminated this by restarting the device but I was struggling with the Internet connection. Whether I was connected via wifi or a SIM card, the screen was disconnected from the Internet and either restarting the card or the whole device helped. After several hours of experiments I found out that the culprit is the application "Blokada", after its removal everything works as it should. I do not know if the problem was caused by "tweaking" Samsung update or some art of Google security policy, in any case, until then a great ad blocking application had to unfortunately have gone from the phone .......
Click to expand...
Click to collapse
Use AdGuard it has never failed me on non-rooted phones.
re
k3lcior said:
Use AdGuard it has never failed me on non-rooted phones.
Click to expand...
Click to collapse
Thank you for your answer, of course I installed AdGuard instead of Blokada and everything works. Today I can no longer imagine using a computer or smartphone without blocking ads, there are more and more annoying and spying. However, I was extremely satisfied with Blokada until the February update, unfortunately she had to leave. We will see if the manufacturer of this application responds and will release a new version that will not suffer from this ailment.
Charging issue after ATA1 UPDATE (February)
Is anyone else experiencing this, I swear after the update took it off the charger one last time phone restarted then after that it wouldn't charge anymore. At this point, I'm blaming the forced OTA for the problem meanwhile I've resorted back to my reliable S5. Amazon & Samsung both said that they couldn't RMA the phone because I missed my January 31st window.
haha and you're reporting me and blocking me because of truth.
My phone charges slower after the update. 15w fast charge feels like 10 w, and when I disable fast charge it won't charge and give me prompt something like "use the original samsung adapter or check the cable"
A505GUBS5ATB2 Combination
Hello friends, could anyone tell me if there is a combination rom for this update ? (A505GUBS5ATB2)
Thanks a lot!
Samsung released Firmware Update R825USQU1BTH9/R825UOYN1BTH9 for the Galaxy Watch Active 2 (SM-R825U) (on 9/23/20)
One UI Watch Version 2.0
Tizen Version 5.5.0.1
ECG, etc. !
Build Number : R825USQU1BTH9 Tizen version : Tizen 5.5.0.1 Release Date : 2020-09-23
• Advanced Running Analysis : Giving you the insights you need to improve your running form.
• VO2max : Check the maximum amount of oxygen you utilize during exercise to improve your endurance.
• Added the new Samsung Health Monitor App for ECG Measurements.
(※ Available on Galaxy smartphones with Android 7.0 and later.)
• Detect falls : Watch can send out SOS call and messages to emergency contact when a hard fall is detected.
• Enhanced Notification : Upon receiving a message notification, a chat window appears and can also view images.
• AR Emoji/Bitmoji : Send AR Emoji and Bitmoji through the watch.
• Capture : Supports scroll capture feature that automatically sends the screen-capture image to the phone.
Samsung released Firmware Update R825USQU1ATH1 for the Galaxy Watch Active2 (SM-R825U) on 9/02/20
Change Log Indicates:
· Improved system reliability
Samsung released Firmware Update R825USQU1ATF2 for the Galaxy Watch Active2 (SM-R825U) on 7/24/20
edit: I finally got the ATF2 update on my Unlocked SM-R825U on 9/24/20. After that update, the 9/23/20 R825USQU1BTH9Tizen Update Downloaded.
Samsung Unlocked Version: https://doc.samsungmobile.com/SM-R825U/XAR/doc.html
AT&T Version: https://doc.samsungmobile.com/SM-R825U/ATT/doc.html
· Device stability improvements, bug fixes.
· New and / or enhanced features.
· Further improvements to performance
Samsung's description is lacking
Does anyone have further insight to any of the updates above?
I received this too... very vague. Anyone?
I just updated and now my numbersync doesn't work. It's as if it turned it off but watch says it's on.
Ughh. .
Sent from my AT&T Samsung Note8 [SM-N950U] using Tapatalk
LuvrGirl said:
I just updated and now my numbersync doesn't work. It's as if it turned it off but watch says it's on.
Ughh. .
Click to expand...
Click to collapse
Same here. Watch updated and now numbersync isn't working and when I try to get a numbersync code, it always fails saying "Numbersync is currently unavailable."
Hi, where do you guys live? Where is this update released? Nothing here in Sweden
yeah
Arzo001 said:
Hi, where do you guys live? Where is this update released? Nothing here in Sweden
Click to expand...
Click to collapse
nothin in norway either, we'll probably be getting it a few months after the rest of the world gets it, as always. :good:
that's why I switched to apple.
still love my active 2 though
peace
LuvrGirl said:
I just updated and now my numbersync doesn't work. It's as if it turned it off but watch says it's on.
Ughh. .
Sent from my AT&T Samsung Note8 [SM-N950U] using Tapatalk
Click to expand...
Click to collapse
So last night I tried doing a reset on my active 2 watch to see if that would help. The Numbersync option in the watch no longer showed it was on so I tried turning it on but I would get an error message saying "Mobile network unavailable". Tested it out by calling myself and sending myself a text from another phone and nothing was received on the watch. So watch only worked independently using it's own phone number.
Here's the weird thing now... this morning I wake up and started receiving calls and text messages and they started showing up on my watch! So I go into the watch menu for numbersync and it looks as if it's not turned on but somehow it's synced with my phone?
So currently it's working as if it's synced. So now I'm wondering if I should even go thru the menu option to enable numbersync even though it's working as if it's enabled?
Edit: watch receives calls and messages but because it's connected via bluetooth to my phone. Once disconnected from bluetooth the watch just works independently. Still getting same error message of "Mobile network unavailable" everytime I go into the watch menu and try to get a sync code.
rmcomer said:
Same here. Watch updated and now numbersync isn't working and when I try to get a numbersync code, it always fails saying "Numbersync is currently unavailable."
Click to expand...
Click to collapse
I'm having the same issue. Has anyone found a fix for this yet?
ssnssmom said:
I'm having the same issue. Has anyone found a fix for this yet?
Click to expand...
Click to collapse
No fix that I know of. I did several resets and went thru 2 esim changes all at the AT&T store and nothing worked. The watch has no internet connection after this last update. Phone calls work but no internet. Test it by disconnecting Bluetooth and using it standalone. You should be able to get into the Galaxy Store or update Weather and nothing works because there's no mobile data.
I ended up having to file a warranty claim thru Samsung and my watch is in route right now to Samsung.
Sent from my AT&T Samsung Note8 [SM-N950U] using Tapatalk
Same problem!
rmcomer said:
Same here. Watch updated and now numbersync isn't working and when I try to get a numbersync code, it always fails saying "Numbersync is currently unavailable."
Click to expand...
Click to collapse
I have also experienced extremely long wait times for support, and usually just hang up now. I was told AT&T was aware of the problem and say it has to do with an update from Samsung and a new update from Samsung will be needed to solve the problem. I hope we can learn more!
LuvrGirl said:
No fix that I know of. I did several resets and went thru 2 esim changes all at the AT&T store and nothing worked. The watch has no internet connection after this last update. Phone calls work but no internet. Test it by disconnecting Bluetooth and using it standalone. You should be able to get into the Galaxy Store or update Weather and nothing works because there's no mobile data.
I ended up having to file a warranty claim thru Samsung and my watch is in route right now to Samsung.
Sent from my AT&T Samsung Note8 [SM-N950U] using Tapatalk
Click to expand...
Click to collapse
Update:
So apparently my watch is in route back to me. Samsung repair ticket indicates the solution was "REPLACED PBA".
I don't know what PBA stands for. However, I could have sworn it was due to the recent software update since a lot of other people are having the same issue.
Sent from my AT&T Samsung Note8 [SM-N950U] using Tapatalk
Call from AT&T Tech Support
LuvrGirl said:
Update:
So apparently my watch is in route back to me. Samsung repair ticket indicates the solution was "REPLACED PBA".
I don't know what PBA stands for. However, I could have sworn it was due to the recent software update since a lot of other people are having the same issue.
Sent from my AT&T Samsung Note8 [SM-N950U] using Tapatalk
Click to expand...
Click to collapse
I received a call today and learned that AT&T was working on some "profile problems" in their NumberSync program that many are experiencing (such as those in this thread). The person called to verify my login name. Before the call, I did update the Galaxy Wear App (that I was told earlier should solve the problem), but that made no difference. I was also told that I would receive a return call in 24 to 48 hours when they had fixed the problem and they would help me connect to NumberSync. I am glad they escalated my ticket a few days ago; hopefully that means I am in the queue of known people with problems to have the problem fixed (if that is the problem and there is a fix). There must be hundreds or thousands with the same problem for them to give some attention to it????
LuvrGirl said:
Update:
So apparently my watch is in route back to me. Samsung repair ticket indicates the solution was "REPLACED PBA".
I don't know what PBA stands for. However, I could have sworn it was due to the recent software update since a lot of other people are having the same issue.
Sent from my AT&T Samsung Note8 [SM-N950U] using Tapatalk
Click to expand...
Click to collapse
“PBA” stands for Product Board Assembly.
I’m having the same problem as you. The watch works fine when paired with my phone, but in standalone mode I can’t get any mobile data, and I can’t activate Numbersync.
Do you know if your watch overheated when downloading the update? While the update file was downloading to my watch, it overheated and shut itself off because the file was so large. After I restarted the watch, the update completed and everything was working except mobile data. I’m wondering if this has something to do with it.
Please let us know if everything works after replacing the PBA. I may need to send my watch in to Samsung for a replacement as well.
Zagzagel said:
“PBA” stands for Product Board Assembly.
I’m having the same problem as you. The watch works fine when paired with my phone, but in standalone mode I can’t get any mobile data, and I can’t activate Numbersync.
Do you know if your watch overheated when downloading the update? While the update file was downloading to my watch, it overheated and shut itself off because the file was so large. After I restarted the watch, the update completed and everything was working except mobile data. I’m wondering if this has something to do with it.
Please let us know if everything works after replacing the PBA. I may need to send my watch in to Samsung for a replacement as well.
Click to expand...
Click to collapse
I can't remember exactly if it overheated or not. I know it did reboot but don't remember if I myself turned it back on or if it rebooted by itself after the update...
I"ll come back and update once I get my watch back and can confirm.
LuvrGirl said:
I can't remember exactly if it overheated or not. I know it did reboot but don't remember if I myself turned it back on or if it rebooted by itself after the update...
I"ll come back and update once I get my watch back and can confirm.
Click to expand...
Click to collapse
Thanks! Also, what kind of phone are you using? I am using my Galaxy Watch Active 2 paired with an iPhone 11 Pro Max, or setup independently in standalone mode. You can set the Watch Active 2 up in standalone mode by scrolling down on the watch’s initial setup screen and pressing the “?”. Either way, I am unable to receive mobile data after the update.
The reason I ask about the type of phone you have is when I called AT&T support, they said it was impossible to receive mobile data if the Watch Active 2 is paired with an iPhone or setup in standalone mode, but this doesn’t make sense because it was working fine for me before. I’m wondering if the update disables mobile data unless the Watch is paired to an Android phone.
Zagzagel said:
Thanks! Also, what kind of phone are you using? I am using my Galaxy Watch Active 2 paired with an iPhone 11 Pro Max, or setup independently in standalone mode. You can set the Watch Active 2 up in standalone mode by scrolling down on the watch’s initial setup screen and pressing the “?”. Either way, I am unable to receive mobile data after the update.
The reason I ask about the type of phone you have is when I called AT&T support, they said it was impossible to receive mobile data if the Watch Active 2 is paired with an iPhone or setup in standalone mode, but this doesn’t make sense because it was working fine for me before. I’m wondering if the update disables mobile data unless the Watch is paired to an Android phone.
Click to expand...
Click to collapse
I have a Samsung Galaxy Note 8 and both my watch and Note 8 were purchased directly with AT&T and have had continued service since day 1.
That doesn't make sense at all actually because if it's an LTE watch and it has it's own line, it's supposed to have all the functions available - and that includes phone calls, texts, and internet (data).
My Numbersync issue is resolved
Tumbleweedtoo said:
I received a call today and learned that AT&T was working on some "profile problems" in their NumberSync program that many are experiencing (such as those in this thread). The person called to verify my login name. Before the call, I did update the Galaxy Wear App (that I was told earlier should solve the problem), but that made no difference. I was also told that I would receive a return call in 24 to 48 hours when they had fixed the problem and they would help me connect to NumberSync. I am glad they escalated my ticket a few days ago; hopefully that means I am in the queue of known people with problems to have the problem fixed (if that is the problem and there is a fix). There must be hundreds or thousands with the same problem for them to give some attention to it????
Click to expand...
Click to collapse
Last Friday I called AT&T about my NumberSync issues after my Active2 watch update. They said they'd call back when they researched it. I received a call this afternoon from AT&T about profile issues due to the new watch software and now my NumberSync issue is resolved. I was able to get my Sync Code and sync up my Galaxy s20 Ultra without any problems. A minute or so after syncing, I received tons of text messages that were sent to my phone from last week before the watch update.
rmcomer said:
I also received a call this afternoon from AT&T about profile issues due to the new watch software and now my NumberSync issue is resolved. I was able to get my Sync Code and sync up my Galaxy s20 Ultra without any problems. A minute or so after syncing, I received tons of text messages that were sent to my phone from last week before the watch update.
Click to expand...
Click to collapse
Congratulations and thanks for this helpful information! I have yet to receive a call to finally resolve the issue, and I just tried to get a code and still get the same error message. Perhaps tomorrow I will be fortunate to receive a call too. I will let everyone know. I will also be curious to know if those who sent their watches in for warranty work will have a seamless syncing with their new or refurbished watches. At least I now know where the problem lies and that AT&T has found a solution at least for some! Thanks again! BTW: I was thinking of upgrading to the s20, but did not want to do so if this problem continued..
guys can u tell me in R825U unlocked which csc u used ...as iam on R825F (XSA) and want to shift to USA..unlocked
And do anyone has the latest firmware that can be used to after changing the CSC region.
rmcomer said:
Last Friday I called AT&T about my NumberSync issues after my Active2 watch update. They said they'd call back when they researched it. I received a call this afternoon from AT&T about profile issues due to the new watch software and now my NumberSync issue is resolved. I was able to get my Sync Code and sync up my Galaxy s20 Ultra without any problems. A minute or so after syncing, I received tons of text messages that were sent to my phone from last week before the watch update.
Click to expand...
Click to collapse
As of today, August 7, no one has called me back to resolve this issue and numbersync still does not work for me. When trying to call or chat with ATT Support, I am told they have a high call volume. So, I have been promised by tech support that they have a solution and that I would be called within 48 hours and still no call. After trying several times, it appears they have to fix the problem and call you to fix the problem, because I still cannot get a code. I hope we can hear some good news from someone that we can finally get a code without needing a tech support call. I suppose we will get no tech support calls over the weekend.