Sony XAV-AX3200 usage with Smart World App2Car adapter

Thanks Kazza055.

Good point about the miss typing. I see that too.

I suspect that the touch screens on these car radios are no where near as sensitive as they need to be for this type of use.

When using them in normal situations, all the buttons are quite big and little accuracy is needed and very little user input is required, so I would not notice the issues.

When I use mine with CarPlay, I use Siri to find addresses etc, so never need to type. I haven't tested that usage, but it is probably similar.

Edit: I tried using my Apple Pencil on the screen and found I could get more accuracy, I guess because the point is so small (the only way I could get the keyboard space bar input to work). I also noticed that the centre of a button was not necessary the point that it was accepting the input. So finger inputs are probably too large of an area of the screen to get the correct accuracy.

You could try updating the keyboard app, I found "gboard" and updated it and it has improved the response, I can now at least use the on screen keyboard.

It seems that the keyboard comes from the plugged in device rather than the screen.

Thanks, glad to see that you have had a little progress with this issues.
For me, I have decided that this solution is not fit for my purpose and am looking at of the solutions.

I may go with the dedicated device from Smart World that is designed to mount to the top of the dash or look at a tablet mounted somewhere in the car, or replace the car radio with an Android type.

Thanks for your input bungarra (WA).

I think you are probably correct about the sensitivity of the screens.

The newer units such as the one in your 300, probably have better specifications than a cheap car radio that has CarPlay features.

The poor sensitivity is noticeable in everything I try to do in Android, trying to enter searches, settings etc all act similar.

Based on my experience, I felt the App2Car adaptor worked as designed and do not think the poor experience was anything to do with it.

I did not do a lot of testing due to the interface issues with the Sony unit.

The Sony unit only has a resolution of 800x480 pixels but it also is a resistive touch screen. I believe that these two specs are the key to the successful usage.

The low resolution only allows so much definition on the screen so the map size was not great. This did not concern me too much as google and apple maps are similar in this respect.

The resistive touch needs pressure and accuracy, so they really important and why it is a very poor experience near the edges where key buttons are placed in Android and Exploroz app. Also, the Sony unit's screen is set back with a pronounced bezel around it, making it difficult to apply pressure near the screen edges. Capacitive touch screens would be much better in this situation.

Generally, Resistive Touch screens are also not multipoint touch, making navigating a map much more cumbersome as you need to use arrows and zoom buttons much more.

In saying all of this, Smart World have been supportive and have been very responsive in returning the App2Car unit. I was careful to keep all packaging in case I needed to return in.

My recommendation would be to check the specs of the unit in the car first (I did not), what type of touch interface it has and if the screen is recessed back or not. I think you will want a flush screen with capacitive touch for this to work well.