georgef

I had similar issues when I first started using Android Auto. I discovered the usb socket on my phone was "iffy" (technical term) and that the phone/car setup was very sensitive to cable choice. I don't know whether the fine conductors in cables break or become detached or whatever but I found changinging cables helped. Also, "not optimising" battery usage also helped - this is not a problem cos the phone will be charging via the cable anyway.

I have a spare steel wheel with an unused tyre and an unused toolkit I will sell. Where are you? Both from a Fabia III and original kit.

Ah - the insurance woes. I seem to recall the premium difference between the 110PS and the 95PS was marginal although my daughter is now 23 and that might have a bearing. Interestingly, when I learned to drive the Mk1 Golf GTi was the hot hatch and had about 110PS - no one would have let a 17 year old loose in a MK1 GTi but my daughter drove my 100PS 1.9Tdi fabia 1 and the 1.2 110PS that I replaced it with. Mind you, the Mk1 GTi was probably a lot luighter and more nimble but still.

Sorry. Slow to the discussion. I have a 110PS SEL with the 6 speed gearbox. My daughter has a MKIII with the 95PS 5 speed gearbox. Round town I don't notice much difference. On the motorway I would rather be in mine than hers. The extra gear makes for much more relaxed driving at motorway speeds - lower engine speed, lower noise and much less of a rushed feeling.

I am confident it is not the cable. I use Android Auto with a Samsung phone, an ancient Sony and my wife's new Nokia 5.1. All phones work well. My daughter uses a Huawei phone and when we got the Fabia we tried to use AA on her phone with the car. It simply wouldn't work. Research on the interweb reveals that there is an issue with AA and car head units. Google and Huawei know about this and both have been promising fixes for a couple of years and neither seems to have made a breakthrough. Oddly, AA works on my daughter's phone if used a stand-alnoe device - that is not connected to the car but it will not work when connected to the car. I am delighted that you have got your Huawei to work but you must be one of very few Huawei users who have succeeded.

I use Waze on my Samsung A3 (2017). The voice control does not seem as good as Google Maps (and the car is fitted with voice control). But, for me, the huge real world advantages of Waze are the reporting by other "Wazers" of hazards on trhe road and the visual appearance of the mapping. Waze appeals to me more than the Google Maps. However, Google Maps' lane guidance is fantastic.

I know the Huawei P9 is not compatible with Android Auto. I rather suspect the P8 may not be. Google and Huawei have known about this problem since about 2016 but so far have failed to resolve the issue. Both blame the other. A quick internet search will result in numerous people reporting this incompatibility. The easy solution might appear to be to buy a second but cheap Android phone to use in car, but Android Auto requires a data connection so a cheap phone is not the easy work-around solution it first appears to be. That said, my wife's Motorola E works perfectly well in my Fabia as an Android Auto "server".

See PM

I had a 1.2 tsi 110 and this year changed to a 1.0 tsi 110. Leaving aside the physical differences, the 1.0l has a noticeably different engine noise - I hear similarities in the characteristics of the noise with the 1.4 3 cylinder diesel. The petrol engine is plainly less noisier than the diesel but there is a similar 3 cylinder note. The 3 cylinder engine feels less torquey than the 4 cylinder engine despite the figures. My daughter thinks the 3 cylinder isn't as fast as the 4 cylinder (despite the figures) but that may just be the 3 cylinder engine is not yet run in. I tend to agree with Gerrycan's observations. In truth, the differences between the two engines is, to me, for practical putrposes, very marginal.

I quite like Android Auto and the voice commands seem reasonably effective (the car is equipped with voice control) although a previous Fabia without voice control could handle AA just as well. I like the Waze interface and the principle behind Waze but have not found the voice control as good as Google Maps itself. One thing I do like about Android Auto is that it is always up to date - unlike the satnav in my other cars. I would have no hesitation in recommending Android Auto (providing the phone supports it - my daughter's Huwei P9 lite doesn't support AA and that can be a pain - so check that your phone, or the phone you are thinking about, supports AA before you take the plunge.

My car has a full size steel wheel with a 185/60 x 15 Nexen tyre fitted. The wheel has a yellow sticker on it indicating a speed restriction.

I am not sure from the V5 that you can tell what the car has been used for other than VW were the registered keeper. It could well have been a demonstrator or a management fleet car or a something like that. You cannot tell from the V5 how many drivers have driven it. If you are anxious about the history, maybe this is not the car for you.

I think that it is a not uncommon phenonemon whereby one doesn't notice things until there is "a reason" to notice them. In this case, you have the Fabia and now you notice others. That said, I think there are more on the roads than there were when I got mine 15 months ago - which is hardly surprising.

Very nice. It looks exactly the same as mine. Enjoy it. We Quartz Grey owners are a select minority.

Ok - I bought a Samsung A3 (2017) model. 4.7 inch screen. 2GB Ram, 16GB internal storage and capacity for a 256GB SD card. Should do me. The screen is nice and sharp and it works with Android Auto. I am getting used to the Google Maps (not as good as Here Maps on windows) but as Windows isn't compatible with the car, beggars can't be choosers. Thanks for all your help. I will give flac files a go.