Jump to content

Mark S Morley

Members
  • Posts

    68
  • Joined

  • Last visited

Everything posted by Mark S Morley

  1. I'd say that this is abnormal. I have mine at 3 for a few minutes to get them warm but thereafter have to bring the temperatures down as it is uncomfortably warm. m.
  2. I ordered my S2 L&K with the space saver wheel - and was very glad of it when I managed to drive over a metal strip which shredded one of my tyres beyond repair. In rural southern Italy. On a Friday night. Before a three day weekend. Getting a replacement tyre was a challenge (in fact impossible). Having unloaded the fully laden car, I was very surprised to find that the standard 18" Sirius fitted the spare wheel well just fine, albeit with the tyre deflated. When I finally sourced a replacement tyre (in Athens) I got the fitters to try the wheel + inflated tyre in the well and it fitted fine... hence I've now replaced the space-saver with a fifth Sirius.
  3. They were fitted to L&K models (certainly pre-facelift) when the auto-dimming rear-view mirror was specified. This wasn't mentioned in the specification anywhere: just what they turned up with. m.
  4. For rooting my S3/S4/Note 8.0 and Note Edge (KitKat) I used this: https://autoroot.chainfire.eu/ HTH, m.
  5. Stuart, Just a data point in case it's helpful. I experienced the same problems as you with stability when moving from the "B" module to the "D". With the "B" my various Samsung devices (S3/S4/Note 8.0) would be reasonably stable with rSAP but would bug out occasionally and would drop back to HFP until the phone was rebooted. When I upgraded to the "D" unit in order to use the hot-spot I experience much the same problem with the device disconnecting after about 30 seconds. I had previously use the Android-rSAP application https://play.google.com/store/apps/details?id=com.android_rsap.rsap which replaces (or provides) the rSAP protocol on rooted devices. On a whim, I decided to try this again, having not needed it since running my Galaxy S2 and, impressively, it works flawlessly. It is rock-solid now on my current phone (Galaxy Note Edge) which bodes well for the Note 4 and has worked perfectly with both KitKat (4.4.4) and Lollipop (5.0.1) versions of Android. With respect to the phonebook problems, I had endless problems with partial or missing contacts until I installed this app (from the same developer) https://play.google.com/store/apps/details?id=com.android_rsap.irmc which does the same thing for the PBAP bluetooth profile - although IIRC this app doesn't require the phone to be rooted. Hope this helps, m.
  6. Mine stopped working this afternoon: the solution (found on here some years ago) was to reset the window position sensors by running all of the electric windows down and up to their full extent. Thereafter the folding mirrors were restored... m.
  7. I'll put some up at the weekend - once I've taught my 11 year old which buttons and pedals to press to get the different lights to show. On second thoughts, teaching him to use a camera might be a better plan m.
  8. I did say I'd report back when they arrived. A combination of excess work, not to mention the fact that SuperSkoda failed to ship them when promised, has meant that I haven't done so until now. I've had them fitted now for a fortnight and I'm pretty happy with them. The brake lights are, indeed, slightly illuminated but as far as I'm aware the fog light (singular) is not. They did warn me prior to (finally) dispatching them that they'd had a number of complaints and that for an RHD car I might have to reverse the control modules from their left and right markings (I didn't). The descriptions of the partially illuminated brakes sound rather worse than it actually is and I'm perfectly happy driving around with them without worrying about being pulled over for showing odd lights. Installation was rather more awkward than the SuperSkoda video suggested. Everything is plug-and-play, no problems there, but getting the magnetic control module into the void through the aperture is difficult, even for my small fingers. A little bit extra length on the cables would have made this so much easier. I certainly think that getting them back out again would be very difficult without unscrewing the magnetic part, at the very least. Anyway, I think the lights look great, day and night, and have added LED indicators to them. I also have a pair of LED reversing bulbs which I'll fit when I've got time. All I need now is LED indicators for the front... :sun: m.
  9. The black dappled area above and behind the mirror is where you need to mount these boxes if you have a heated windscreen. I have both Liber-T (France) and Telepass (Italy) tags fitted here and they work fine. m.
  10. Yes, it seems much better than those on the SC2s. I've only managed to kerb a wheel once (Channel Tunnel transporter) since having the Good Years. Previously I managed to kerb them regularly - turns out Dartmoor granite is quite unforgiving as a material for kerbstones Or maybe I'm just a better driver now m.
  11. As promised: the format of a WPL file that will work with the Columbus - either from the root of the SD card or the HDD. The text in the title tag is shown on the Columbus when broswing through the playlist. While playing the playlist, the "Mix" option randomly selects from all the tracks in the file. <?wpl version="1.0"?> <smil> <head> <meta name="Generator" content="Microsoft Windows Media Player -- 12.0.7601.17514"/> <meta name="ItemCount" content="19"/> <title>Playlist for Skoda Columbus</title> </head> <body> <seq> <media src="Music\Dir1\Dir1\Track 1.mp3"/> <media src="Music\Dir1\Dir1\Track 2.mp3"/> <media src="Music\Dir1\Dir1\Track 3.mp3"/> <media src="Music\Dir2\Dir1\Track 1.mp3"/> <media src="Music\Dir2\Dir1\Track 2.mp3"/> </seq> </body> </smil> Hope this helps, m.
  12. Columbus is on firmware 5218 and Bluetooth module is 3C8035730D. No problems with SMS being read out - apart from the shock value when triggering it accidentally :-) m.
  13. Yes, I've done about 11,000 on mine so far - with 7-8mm left all round. Definitely quieter than what the car arrived with - and better wearing: I think the originals were Continental SC2 - but can't remember. Much better grip, especially in the wet, and the car feels much more settled in cornering - purely subjective, of course. Can't comment on the snow performance in Devon :-)
  14. Yes, this is no problem. My phone is usually connected to the handsfree using rSAP, as an A2DP media player and to the Scantool all at the same time. HTH, m.
  15. I'll second this: Having gone through a pair of "no-name" OBD2 adapters off eBay, I bit the bullet and went for the ScanTool version. It just works. It plays very nicely with Torque, using the maximum symbol throughput as well as the battery-saving mode so that it can be plugged in permanently. Wow... can't believe how much the prices have come down. At least if my wife looks it up, now, I'm likely to survive m.
  16. Jamie, I did manage to achieve what you're trying to do back when I first got my Superb. The trick was to put all of the music into folders, as you want, and then to use a playlist which contains all of the tracks in it. Playing the playlist and then selecting "Mix" would then randomly choose from, effectively, all the music on the HDD - or a subset, depending on what you put in the playlist file(s). Now this is where my memory gets fuzzy. I believe the Columbus was supposed to support *.m3u playlists. However I'm pretty certain that I never got that option working properly. However, on a whim I tried it using the Windows Media Player Playlist format (*.wpl) and this worked fine, despite not being documented as being compatible. As I recall, the tricky thing was working out how the paths were represented on the Columbus and how to represent these in the wpl (XML) file. I soon lost interest in keeping the wpl file manually up-to-date when adding new albums and I no longer use this approach. I don't imagine that I'll be able to pull one of the wpl files off of my Columbus back on to the SD card, however, I wouldn't be at all surprised if there's an appropriately formatted file lying around on my laptop at home - I'll have a look later. Hope this helps, m. p.s. edited to add: yes, here I say I got it working with .wpl - pity I didn't say how...
  17. If you look round about here in the sticky thread I think there's more detail in which pins are not wired in the not A2DP compatible loom. I think it's a case of looking at the larger plug that goes into the Bluetooth module and seeing which pins are actually connected. A later post in the same thread suggests that this cable could also be used as a complete replacement rather than just adding in an additional wire. I don't know if that's true or not, but it looks right to me. HTH, m.
  18. That module should be fine - a quick look here shows that it supports the A2DP audio streaming. I believe the problem that you may run into is that the older Superbs are not wired for stereo sound from the bluetooth module. Getting this to work would then entail running an extra wire from the headunit down under the drivers seat to the bluetooth module :-/ I believe that several on here have done this, however. The settings won't be visible in the MFD until a compatible module is installed. I guess your present one isn't on the above list as being supported? HTH, m.
  19. I've spent much of a long summer in Greece trying to get 3 phones, 3 tablets and a 'phablet' to play nicely with my Superb - largely through trial and error - but other posters here have been great with pointing out the 'gotchas' involved. And, now, everything works as it should with internet access both home and abroad, phonebooks working across multiple devices and Torque too! :-)Sorting the S3 first is a good plan since it really should work out-of-the-box with rSAP. Good luck... m.
  20. It's compatible with rSAP but not with WiFi. There's a very useful reference chart here: http://wiki.ross-tech.com/wiki/index.php/Telephone_Retrofitting which says that your model is the equivalent of the 3C8035730B (which is what my MY12 Superb came with). Hope this helps, m.
  21. I'm afraid I can't help you there: I've only used 4G Samsung Galaxies S3, S4 and Note 8 with my car. They all come with unlocked bootloaders so it's just a straightforward case of rooting these and installing the rSAP profile. My Dad has a Nexus 5 and swears by it rather than at it so I reckon it must be pretty good to overcome that level of technophobia m.
  22. As well as reading out SMS you'll be able to read them on the Columbus or on the MFD. You'll also be able to compose SMS using the touchscreen. Using rSAP over HFP also gives you the advantage of using the external, active GSM/3G antenna on the roof (which gives much better reception). Given that you have the latest module, with Wi-Fi, it also means that you'll retain internet access for your phone as well as sharing access to anything else in the car... While this is possible with an Android phone normally, it will kill your battery. Oh wait, that's the other advantage: handing off all the cellphone functions to the car means that the battery on the phone isn't hit as hard. Hope this helps, m.
  23. Glad you got it working. Rooting sounds scary, sometimes looks scary but in practice isn't. A quick google suggests there are many ways - depending on the installed version of Android. For my Samsungs I used Chainfire's CF Auto-Root which seems to work with the Nexus 4 as well: http://www.android.gs/root-the-google-nexus-4-with-chainfire-cf-auto-root/ Cheers, m.
  24. The Galaxy S3 - should work (can't comment on the Nexus 4). I think all software versions of my S3 worked with both Samsung's rSAP implementation and that from android-rsap.com. m.
×
×
  • Create New...

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.