Sony XAV-AX3005DB disconnecting usb - Android Auto General

Has anyone here used a Sony XAV-AX3005DB? I just installed it on my Suzuki Grand Vitara. While it seems to work ok, it will seemingly randomly drop the USB connection to my OnePlus 3t while using Android Auto (with Spotify and Maps running). Really annoying when following directions and it crashes!
Sometimes it shows an error message like "USB device not supported", but other times it doesn't show any message and the head unit seems to reboot. Reconnecting the USB cable can sometimes start android auto but I've also had it in a state where it will no longer load Android Auto. I had to reboot my phone for it to be recognised the the head unit.
My wife was using it with her Moto G6 and said it worked fine, until I got in the car as a passenger and the head unit crashed within about 5-10 minutes of our journey.
I've tried a different USB-C cable, turning off battery saving on Android Auto on my phone and enabling USB debugging, but it doesn't seem to have worked. I really don't want to have to take the head unit out and take it back but looks like I might have to.
Anyone else have these issues? Sorry if this is in the wrong forum, feel free to move it.

Hi rcwsr,
I have similar issues using Google Pixel to connect to the Sony XAV-AX3005DB. Using my wife's iPhone works fine with Carplay, but when I connect my Pixel, the connection randomly drops and the USB DEVICE NOT SUPPORTED pops up.
It looks like if you use a bit more data (e.g. streaming spotify or something) it crashes.
I guess we have to wait for a firmware update.
rcwsr said:
Has anyone here used a Sony XAV-AX3005DB? I just installed it on my Suzuki Grand Vitara. While it seems to work ok, it will seemingly randomly drop the USB connection to my OnePlus 3t while using Android Auto (with Spotify and Maps running). Really annoying when following directions and it crashes!
Sometimes it shows an error message like "USB device not supported", but other times it doesn't show any message and the head unit seems to reboot. Reconnecting the USB cable can sometimes start android auto but I've also had it in a state where it will no longer load Android Auto. I had to reboot my phone for it to be recognised the the head unit.
My wife was using it with her Moto G6 and said it worked fine, until I got in the car as a passenger and the head unit crashed within about 5-10 minutes of our journey.
I've tried a different USB-C cable, turning off battery saving on Android Auto on my phone and enabling USB debugging, but it doesn't seem to have worked. I really don't want to have to take the head unit out and take it back but looks like I might have to.
Anyone else have these issues? Sorry if this is in the wrong forum, feel free to move it.
Click to expand...
Click to collapse

I've had exactly the same problem with Moto G6 (4GB RAM/64GB Flash) and XAV-AX3005DB.
Tried upgrading XAV firmware from 1.10 to 1.11, no-fix.
Upgraded Moto G6 from Android 8.0 to 9.0, no-fix.
Tried various "usual" fixes like developer mode, USB debugging - still no-fix.
There is a flying USB lead out of the back of the Sony. I've got an extension USB cable plugged into this. Replacing or getting rid of the extension cable is the only thing I haven't got round to trying yet (I need to take the fascia back off to do this).
I've got a Logcat file out of the G6 that shows Android Auto crashing. I'll include it below, but I'm not sure it'll be of any use. From reading the above thread, it feels it's more a problem with the Sony than the Moto.
2019-04-02 17:55:50.370 3174-3230/? I/chatty: uid=1000(system) ActivityManager expire 1 line
2019-04-02 17:55:50.405 3174-3630/? I/chatty: uid=1000(system) ConnectivitySer expire 2 lines
2019-04-02 17:55:51.447 3174-3233/? I/chatty: uid=1000(system) ActivityManager expire 10 lines
2019-04-02 17:55:51.864 3174-4809/? I/chatty: uid=1000(system) Binder:3174_14 expire 5 lines
2019-04-02 17:55:52.240 3174-4653/? I/chatty: uid=1000(system) Binder:3174_E expire 10 lines
2019-04-02 17:56:00.008 3174-3174/? I/chatty: uid=1000 system_server expire 10 lines
2019-04-02 17:56:02.575 3174-3608/? I/chatty: uid=1000(system) HwBinder:3174_3 expire 3 lines
2019-04-02 17:56:02.575 3174-3263/? I/chatty: uid=1000(system) android.fg expire 40 lines
2019-04-02 17:56:02.600 3174-3489/? I/chatty: uid=1000(system) UEventObserver expire 16 lines
2019-04-02 17:56:03.555 3174-3264/? I/chatty: uid=1000(system) android.io expire 2 lines
2019-04-02 17:56:03.566 3174-3230/? I/chatty: uid=1000(system) ActivityManager expire 38 lines
2019-04-02 17:56:03.696 3174-4839/? I/chatty: uid=1000(system) Binder:3174_1D expire 3 lines
2019-04-02 17:56:03.702 3174-4657/? I/chatty: uid=1000(system) Binder:3174_10 expire 5 lines
2019-04-02 17:56:03.703 3174-4831/? I/chatty: uid=1000(system) Binder:3174_17 expire 8 lines
2019-04-02 17:56:03.711 3174-4830/? I/chatty: uid=1000(system) Binder:3174_16 expire 1 line
2019-04-02 17:56:03.718 3174-4535/? I/chatty: uid=1000(system) Binder:3174_B expire 9 lines
2019-04-02 17:56:03.748 3174-3852/? I/chatty: uid=1000(system) Binder:3174_7 expire 2 lines
2019-04-02 17:56:03.797 3174-3643/? I/chatty: uid=1000(system) Binder:3174_4 expire 4 lines
2019-04-02 17:56:04.337 3174-4837/? I/chatty: uid=1000(system) Binder:3174_1B expire 1 line
2019-04-02 17:56:04.567 3174-3265/? I/chatty: uid=1000(system) android.display expire 6 lines
2019-04-02 17:56:05.982 2717-2897/? E/storaged: getDiskStats failed with result NOT_SUPPORTED and size 0
2019-04-02 17:56:06.122 3174-4707/? I/chatty: uid=1000(system) Binder:3174_12 expire 2 lines
2019-04-02 17:56:14.563 3174-4814/? I/chatty: uid=1000(system) Binder:3174_15 expire 3 lines
2019-04-02 17:56:41.390 3174-3639/? I/chatty: uid=1000(system) Binder:3174_3 expire 3 lines
2019-04-02 17:56:41.396 3174-4840/? I/chatty: uid=1000(system) Binder:3174_1E expire 6 lines
2019-04-02 17:56:41.409 3174-4832/? I/chatty: uid=1000(system) Binder:3174_18 expire 3 lines
2019-04-02 17:56:41.630 3174-4650/? I/chatty: uid=1000(system) Binder:3174_D expire 5 lines
2019-04-02 17:56:45.479 3174-3187/? I/chatty: uid=1000(system) Binder:3174_2 expire 5 lines
2019-04-02 17:56:52.708 3174-4705/? I/chatty: uid=1000(system) Binder:3174_11 expire 1 line
2019-04-02 17:57:05.984 2717-2897/? E/storaged: getDiskStats failed with result NOT_SUPPORTED and size 0
2019-04-02 17:57:13.814 3174-3174/? I/chatty: uid=1000 system_server expire 10 lines
2019-04-02 17:57:13.884 3174-4710/? I/chatty: uid=1000(system) Binder:3174_13 expire 7 lines
2019-04-02 17:57:15.422 3174-3233/? I/chatty: uid=1000(system) ActivityManager expire 2 lines
2019-04-02 17:57:15.539 3174-4840/? I/chatty: uid=1000(system) Binder:3174_1E expire 9 lines
2019-04-02 17:57:17.804 3174-4653/? I/chatty: uid=1000(system) Binder:3174_E expire 6 lines
2019-04-02 17:57:17.924 3174-3230/? I/chatty: uid=1000(system) ActivityManager expire 37 lines
2019-04-02 17:57:19.773 3174-3489/? I/chatty: uid=1000(system) UEventObserver expire 21 lines
2019-04-02 17:57:19.791 3174-3278/? I/chatty: uid=1000(system) HwBinder:3174_1 expire 4 lines
2019-04-02 17:57:19.792 3174-3263/? I/chatty: uid=1000(system) android.fg expire 34 lines
2019-04-02 17:57:19.822 3174-4842/? I/chatty: uid=1000(system) Binder:3174_20 expire 3 lines
2019-04-02 17:57:20.115 3174-4809/? I/chatty: uid=1000(system) Binder:3174_14 expire 6 lines
2019-04-02 17:57:24.551 3174-3186/? I/chatty: uid=1000(system) Binder:3174_1 expire 6 lines
2019-04-02 17:57:24.989 3174-3264/? I/chatty: uid=1000(system) android.io expire 2 lines
2019-04-02 17:57:25.011 3174-3643/? I/chatty: uid=1000(system) Binder:3174_4 expire 1 line
2019-04-02 17:57:25.533 3174-4657/? I/chatty: uid=1000(system) Binder:3174_10 expire 5 lines
2019-04-02 17:57:25.681 3174-3265/? I/chatty: uid=1000(system) android.display expire 14 lines
2019-04-02 17:57:25.691 3174-4832/? I/chatty: uid=1000(system) Binder:3174_18 expire 3 lines
2019-04-02 17:57:27.438 3174-3174/? I/chatty: uid=1000 system_server expire 19 lines
2019-04-02 17:57:28.306 3174-4830/? I/chatty: uid=1000(system) Binder:3174_16 expire 1 line
2019-04-02 17:57:28.580 3174-4831/? I/chatty: uid=1000(system) Binder:3174_17 expire 1 line
2019-04-02 17:57:29.014 3174-4835/? I/chatty: uid=1000(system) Binder:3174_19 expire 4 lines
2019-04-02 17:57:30.067 3174-4838/? I/chatty: uid=1000(system) Binder:3174_1C expire 2 lines
2019-04-02 17:57:30.314 3174-3485/? I/chatty: uid=1000(system) android.anim expire 3 lines
2019-04-02 17:57:30.622 3174-4837/? I/chatty: uid=1000(system) Binder:3174_1B expire 4 lines
2019-04-02 17:57:31.057 3174-4814/? I/chatty: uid=1000(system) Binder:3174_15 expire 2 lines
2019-04-02 17:57:43.841 3174-4839/? I/chatty: uid=1000(system) Binder:3174_1D expire 1 line
2019-04-02 17:57:55.027 3174-4707/? I/chatty: uid=1000(system) Binder:3174_12 expire 1 line
2019-04-02 17:57:55.287 3174-4655/? I/chatty: uid=1000(system) Binder:3174_F expire 2 lines
2019-04-02 17:57:56.480 3174-4839/? I/chatty: uid=1000(system) Binder:3174_1D expire 1 line
2019-04-02 17:57:56.488 3174-3230/? I/chatty: uid=1000(system) ActivityManager expire 29 lines
2019-04-02 17:57:56.508 3174-4840/? I/chatty: uid=1000(system) Binder:3174_1E expire 3 lines
2019-04-02 17:57:56.534 3174-3489/? I/chatty: uid=1000(system) UEventObserver expire 13 lines
2019-04-02 17:57:56.732 3174-4710/? I/chatty: uid=1000(system) Binder:3174_13 expire 7 lines
2019-04-02 17:57:56.938 3174-3233/? I/chatty: uid=1000(system) ActivityManager expire 2 lines
2019-04-02 17:57:56.949 3174-4653/? I/chatty: uid=1000(system) Binder:3174_E expire 4 lines
2019-04-02 17:57:57.326 3174-3263/? I/chatty: uid=1000(system) android.fg expire 17 lines
2019-04-02 17:57:57.829 3174-3776/? I/chatty: uid=1000(system) Binder:3174_6 expire 1 line
2019-04-02 17:57:57.848 3174-4814/? I/chatty: uid=1000(system) Binder:3174_15 expire 2 lines
2019-04-02 17:57:57.850 3174-4839/? I/chatty: uid=1000(system) Binder:3174_1D expire 3 lines
2019-04-02 17:57:57.859 3174-4837/? I/chatty: uid=1000(system) Binder:3174_1B expire 7 lines
2019-04-02 17:57:57.940 3174-3264/? I/chatty: uid=1000(system) android.io expire 1 line
2019-04-02 17:57:57.955 3174-3265/? I/chatty: uid=1000(system) android.display expire 21 lines
2019-04-02 17:57:58.019 3174-4705/? I/chatty: uid=1000(system) Binder:3174_11 expire 10 lines
2019-04-02 17:57:58.132 3174-4461/? I/chatty: uid=1000(system) Binder:3174_A expire 6 lines
2019-04-02 17:57:58.609 3174-4842/? I/chatty: uid=1000(system) Binder:3174_20 expire 2 lines
2019-04-02 17:57:58.942 3174-3174/? I/chatty: uid=1000 system_server expire 30 lines
2019-04-02 17:58:00.043 3174-3761/? I/chatty: uid=1000(system) Binder:3174_5 expire 3 lines
2019-04-02 17:58:00.050 3174-4838/? I/chatty: uid=1000(system) Binder:3174_1C expire 9 lines
2019-04-02 17:58:00.326 3174-4835/? I/chatty: uid=1000(system) Binder:3174_19 expire 1 line
2019-04-02 17:58:00.515 3174-3852/? I/chatty: uid=1000(system) Binder:3174_7 expire 1 line
2019-04-02 17:58:00.768 3174-3485/? I/chatty: uid=1000(system) android.anim expire 3 lines
2019-04-02 17:58:00.809 3174-4831/? I/chatty: uid=1000(system) Binder:3174_17 expire 6 lines
--------- beginning of crash
2019-04-02 17:58:01.253 7777-7777/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.google.android.projection.gearheadrojection, PID: 7777
java.lang.UnsupportedOperationException: Cannot use this method if service has not been started
at bwh.a(SourceFile:2)
at frs.b(SourceFile:148)
at fog.m(SourceFile:52)
at com.google.android.gms.car.internal.CarActivityHostImpl.a(SourceFile:499)
at com.google.android.gms.car.internal.CarActivityHostImpl.u(SourceFile:226)
at eck.run(SourceFile:3)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at com.google.android.gms.libs.punchclock.threads.TracingHandler.dispatchMessage(SourceFile:9)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6923)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:870)
2019-04-02 17:58:05.985 2717-2897/? E/storaged: getDiskStats failed with result NOT_SUPPORTED and size 0
2019-04-02 17:58:57.302 3174-3938/? I/chatty: uid=1000(system) uteStateMachine expire 15 lines
2019-04-02 17:58:57.303 3174-3936/? I/chatty: uid=1000(system) BluetoothRouteM expire 2 lines
2019-04-02 17:58:59.635 3174-3760/? I/chatty: uid=1000(system) HwBinder:3174_4 expire 1 line
2019-04-02 17:59:00.409 3174-4535/? I/chatty: uid=1000(system) Binder:3174_B expire 1 line
2019-04-02 17:59:01.975 3174-4839/? I/chatty: uid=1000(system) Binder:3174_1D expire 5 lines
2019-04-02 17:59:05.988 2717-2897/? E/storaged: getDiskStats failed with result NOT_SUPPORTED and size 0
2019-04-02 17:59:07.338 3174-3761/? I/chatty: uid=1000(system) Binder:3174_5 expire 4 lines
2019-04-02 17:59:07.375 3174-3230/? I/chatty: uid=1000(system) ActivityManager expire 21 lines
2019-04-02 17:59:07.450 3174-3187/? I/chatty: uid=1000(system) Binder:3174_2 expire 7 lines
2019-04-02 17:59:08.278 3174-3174/? I/chatty: uid=1000 system_server expire 15 lines
2019-04-02 17:59:08.759 3174-4705/? I/chatty: uid=1000(system) Binder:3174_11 expire 2 lines
2019-04-02 17:59:16.835 3174-3606/? I/chatty: uid=1000(system) InputReader expire 2 lines
2019-04-02 17:59:17.341 3174-3275/? I/chatty: uid=1000(system) PowerManagerSer expire 12 lines
2019-04-02 17:59:17.388 3174-3265/? I/chatty: uid=1000(system) android.display expire 11 lines
2019-04-02 17:59:17.564 3174-3263/? I/chatty: uid=1000(system) android.fg expire 6 lines

Sorted - USB Extension Cable
I finally managed to sort this (after about 3 months).
I was using a 1m USB extension cable and this caused all the problems.
Got rid of the extension cable and it now seems to work 100% of the time.

nggrant said:
I finally managed to sort this (after about 3 months).
I was using a 1m USB extension cable and this caused all the problems.
Got rid of the extension cable and it now seems to work 100% of the time.
Click to expand...
Click to collapse
Me too have this problem in op3t, xav-ax3000 and a brand new Honda... Connected the Head unit cable to the Honda USB cable.... Other Android phone at the Sony service center is working fine.... Have to disconnect the extra cable and check

How does a different cable fox this?
I have the same crashes on my android auto and I'm using a 20cm usb to usb type c to my phone straight from the headunit.
Would a different cable fix it?
And do you need a small storage size usb to update the firmware ?
Finally found people with the same issue as me !

Related

Board/Device popularity

I was poking around the boards this morning and got curious as to which one might be the most popular and, by extension, which device is most popular. So, I pulled all the current 'viewers' from the boards and did a little math. To be honest, I was a little surprised as to how far up the chart some of the devices were (and how low others were).
Code:
Device Viewers
Blackstone 526
Diamond 485
Dream 416
Raphael 275
Kaiser 215
Xperia 212
Sapphire 162
Topaz 132
Hermes 119
Wizard 84
Rhodium 79
Polaris 77
Trinity 51
Elf 49
Universal 47
Artemis 42
Atom 40
Excalibur 40
Prophet 33
Blue Angel 32
Himalaya / Andes 24
Vogue 23
Vox 22
Nike 21
Titan 21
Athena 20
Magician 20
Sable 19
Jade 18
Treo 750 15
Herald 13
Gene 12
Wallaby 10
Shift 8
Tornado 8
Opal 7
Wings 7
Treo Pro 6
Alpine 5
Rose 5
Iolite 4
StarTrek 4
Charmer 3
Apache 2
Breeze 2
Hero 2
Juno 2
Oxygen 2
Pharos 2
Typhoon 2
Cavalier 1
Hurricane 1
Maple 1
Monet 1
Sedna 1
Beetles 0
Libra 0
Keep in mind, this is at 10:15am EDT. I might do this again later this evening and see what I come up with.
Interesting results
it seems that these results should be taken about every hour, then filter through them based on the countries and time zones where these particular models were sold in without the need of importing.
I have the feeling that certain hours, especially afternoon and early night hours in the US, will have a much higher ratio of Raphaels and Kaisers than during any other time. On the same note, the Blackstone will almost certainly be at it's best during similar hours in Western Europe. Just my assumption.
Go Blackstone
Thought I'd run another report this afternoon. Seems like the boards are a lot less busy on a Thursday afternoon (at least on the US East Coast).
Code:
Dream 524
Blackstone 511
Diamond 486
Raphael 314
Kaiser 265
Xperia 224
Topaz 140
Sapphire 110
Hermes 98
Rhodium 91
Wizard 78
Universal 67
Polaris 62
Excalibur 54
Prophet 49
Elf 47
Artemis 46
Trinity 35
Vogue 33
Herald 30
Athena 25
Nike 23
Blue Angel 22
Titan 22
Himalaya & Andes 20
Magician 20
Vox 18
Atom 16
Jade 16
Sable 16
Treo 750 16
Gene 9
Hero 9
StarTrek 9
Tornado 8
Charmer 7
Alpine 5
Iolite 5
Pharos 5
Shift 5
Opal 4
Treo Pro 4
Wings 4
Hurricane 3
Juno 3
Maple 3
Rose 3
Apache 2
Typhoon 2
Wallaby 2
Cavalier 1
Monet 1
Oxygen 1
Breeze 0
Libra 0
Sedna 0
Again, take this popularity contest with a grain of salt. Pulled @ 2009-07-09 16:08 EDT
Edit:
I just noticed the Beetles board is gone. Hope I didn't have anything to do with it.

Google Trade In value for Pixel 3 XL Disappointing

Current trade in value for a 64 GB Pixel 3 XL is $260. I've been a loyal Nexus/Google user for the last few years and I'm quite disappointed about the trade in amounts compared to the last two years. In case anyone was also wondering, below were my previous trade in values:
Oct 9, 2018 - Pixel 2 XL $325
Nov 27, 2017 - Pixel XL $405
Does anyone remember or know if we should expect the trade in values for previous-gen Pixels to increase in the next month or two?
I can't imagine they would increase. Would be happy to hear if I'm wrong about that.
BTW, if anyone is interested Pixel 2 trade in price is $110.
It could be worse. Google only wanted to give me $60 for my G7 lol. Just head over to Swappa, my dude.
Check with your carrier as well.
T-Mobile I believe is doing a $300 trade in for the Pixel 3 and 3 XL.

Some pictures with RENO 2

Some pictures with RENO 2 by night, and Museum

Why there is no compere between pixel 5 and onePlus 8 PRO at any video? is it because

Hello
Why there is no compare between pixel 5 and onePlus 8 PRO at any video? is it because that it is mid range?
Thanks

Mi 10 Ultra is...back?

Xiaomi unexpectedly brought back two flagship 2020 smartphones on Snapdragon 865 | gagadget.com
Xiaomi once again began selling flagship smartphones on the chip Snapdragon 865, which were introduced more than two years ago.
gagadget.com

Categories

Resources