Please remember to add a category to the bottom of each page that you create.
See categories help for further details, but most will probably be [[Category:HTC ModelName]].

Winca-Roadnav S100/S150

From XDA-Developers
Jump to: navigation, search
This article is a stub. You can help by adding to it (or other stubs) according to the style guide.
S150-S100 Platform
S150-S100 Platform.jpg
Model Number: See Page
Device Type: Head Unit
Manufacturer: Winca\Roadnav 32px
Release Date:
Operating System: Android -WindowsCE 6.0 32px
Dimensions: Double DIN
Weight: 3Kg (shipping)
Display: 6.2" WVGA 480x800 LCD (And up depending on car model variants)
Chipset: SAMSUNG S5PV210
RAM: Not Known
Internal Memory: 512 MB RAM, 4GB/8GB NAND
Memory Card: microSD/HC up to 32GB
Networks: N/A (via usb-host)
Wi-fi: N/A (via usb-host)
USB: Not Known
Bluetooth: Phone/headphone from phone built in. See details below
GPS: Yes
Video out: 2 rear out
Camera: Rearview Cam in (not visible by android)
Secondary Camera: Audio/Video In (not visible by android)
Battery: N/A (powered by vehicle)
Other features
Additional Features: DVD, TV (depending on model), Radio, Ipod connection, Steering wheel controls, remote control, USB Host


The manufacturer Winca (producer of the S60 platform) in 2012 has changed the company name in Roadnav and started producing the S100 Platform based on the WinCE Oparating System. Around mid 2013 they started producing a new Platform S150, based on the same hardware of S100 but with the Android Operating System.


This platform is based on WinCE 6.0, the main advantage of it is the lower boot time and a more user friendly interface. Some Themes and Tools for WinCE can be found on KoTiX's blog.


During end of 2013, the xda member stief found the way to convert his S100 unit to Android 4.03 using an SD recovery tool. This tool consist of an SD card with a special bootloader "fused" in. Initially only linux could fuse the bootloader but, later on, the procedure was fine tuned and a new windows tool SD-Flasher was found and proved to work perfeclty on windows machines by KoTiX.

Here you can find a tutorial explaining the conversion from WinCE to Android and in this archive the instructions to reverse back to WinCE. NOTE: Android 2.34 cannot run on S100 devices because of a missing encription chip.


Just like the S100 these come in many different variants for different car models. One distingushing factor at first sight is a much different stock layout:


Winca-Roadnav S150.jpg


  • Operating System: Android 2.3 for all models and 4.03 available just for a few models for now.
  • more to come, please add

This unit appeared on the original OUKU thread in post #897 and has [] forked to this thread]

See the Winca-Roadnav S100/S150 wiki page for more specs, details and howtos


These units run on top of a Samsung S5PV210 (smdkv210) 1Ghz Cortex A8 Single Core processor and are discussed at length in this forum thread, The first post on that thread, describes update procedures, natively supplied with Android 2.x and new procedures to upgrade to Android 4.0.
All these units, whether "pure android" or WinCE based ones, or even those with neither, are built with a couple of layers of hardware working together to allow integration of all components involved into a seemingly singular interface. It is important to know the basics of how these units are assembled and how they operate because it will allow us to understand reasons for certain limitations and problems as well as the benefits. Please read the MCU Explained Wiki page to better understand how these units differ from typical android devices and the role of MCU and 'native apps'.

External Links

Model identification

There are many variation of the same models, such as vehicle specific versions with just the front panel changed. Furthermore, there are different models that looks exactly the same on the outside. This makes it somewhat hard to identify exactly what model you are looking at. Specs and what shows in the "about" is often the best way to identify your model. When looking at ads for purchase, looking at screenshots, the advertised specs etc. can help.

  • Hardware
    • Operating System: Android
    • CPU: Samsung S5PV210 (smdkv210) 1Ghz Cortex A8 Single Core processor
    • Ram: 512 MB
    • iNand Memory: 4GB
  • Audio
    • 4x 45w Amplifier outputs
    • 1x Subwoofer output
    • 4x Pre-outs
    • External microphone connection
  • Features
    • External Memory:
      • Up to 32GB/SD Card
      • Up to 1TB Usb mass storage drive
    • Built-in Bluetooth (For hands free phone/audio streaming only)
    • GPS
    • iPod
    • RDS
    • Steering Wheel Control
    • WiFi and 3G (with USB dongle NOT HOT SWAPPABLE)
    • Connection of multiple USB devices through a USB hub, including wireless keyboards, USB memory sticks, and wireless dongles. These types of devices are hot-swappable.
    • Subwoofer Output
    • Resistive or Capacitive Touch Screen
    • Digital TV or Analog TV options
    • Display Ratio 16:9
    • Screen Size 6.2 inch (And up depending on car model variants)
    • Screen Resolution 800 x 480
    • DVD player Media Type DVD-R/RW, DVD+R/RW, AVI, MPEG4, CD, CD-R/RW, CD+R/RW, VCD, Mp3, WMA, JPEG, Mp4, DVD, WMV, MKV, WAV, JPG, TXT, PDF
    • Radio Response Bandwidth AM: 522 KHz-1620 KHz;FM: 87.5 MHz-108 MHz
    • Amplifier Max Output Power 45 Watts x 4
    • Remote Control
    • Connectors: 1 x A/V IN, 1 x A/V OUT, 1 x REARCAMERA, 1 x STEERING WHEEL CONTROL, 1 x IPOD, 1 x TV ANTENNA, 1 x POWER, 1 x AUX-IN, 1 x SUBWOOFER, 1 x USB, 1 x GPS ANTENNA
Note:Units that use the same case/face are coming out with newer android 4.x and upgraded internal hardware. Those are completely different units hardware-wise, Roms are not interchangable. They are believed to be variations of the AN-21 U model. (unverified).

Official Firmwares

Thanks to Allen Wong, a member of the S150 technical staff from CarNaviPlayer, you can find all the official firmwares for each model in the Hardware & Software section of your model product page. The latest official 4.03 fw for the I001 model is Here.

Custom Firmwares

A 2.34 custom firmware is available on the russian Forum

A 4.03 custom firmware from dimadina is available on the russian Forum

A 4.03 custom firmware from KoTiX is available on his blog. It include an Aroma installer and root access. Please read the install instructions and bug list before upgrading.

Service menu

The hidden menu (engineering) is accessed at BT screen by dialing number:

On 2.3.4 Gingerberad firmware: *#98723

On 4.0.3 IceCream Sandwich firmware: ##0323

Some IMPORTANT things you should know before flashing S100/S150 units

- Updating an MCU can be dangerous and brick your device if it's not done properly. Winca recommends, before proceeding with the update, to switch to Bluetooth mode, disconnect all the devices and than power off the unit; this is to put the MCU in a kind of idle\safe state.
- If something goes wrong you can always try to reflash your unit using the SD recovery tool available for your operating system; even if you see a black or full white screen the update procedure can still be done, just insert the SD recovery in the gps slot, power on and wait about 20-30 minutes... after that remove the sd and reboot.
- To upgrade android 2.34 to 4.03 is the same procedure to convert wince to android, because the fused bootloader is the same (u-boot_udsd.bin)
- To donwgrade android 4.03 to 2.3 you need a different bootloader (u-boot_sd.bin) fused in the SD card.
- To reflash S100 to WinCE or to convert an original android unit to WinCE, you have to use this archive and follow the included instructions.
- Only 4.03 firmware can run S100, It is possible to flash android 2.34 on S100 units but it won't run because of bootloops.
- S100 can not upgrade to Android 4.0, S100 units produced after Nov 2014 can not upgrade to Android 4.0 via old bootloader card.


Original 2.34 firmware could be rooted using Framaroot.

A new official android 4 firmware exists and has recently been released by forum user KoTiX2 with root built in. (Please update link on new releases or create a firmware section to list different versions.)

User Customisation

Custom Logos

- create your logo in png format 800x480

- convert it to rle format using the tool provided by user Gassi: PNG Converter

- create another png image for thumbnail preview with size 166x108

- name the rle and the thumb file with same name eg. mylogo.rle and mylogo.png

- copy these 2 files using root explorer (EsFileExplorer option enabled) in the Bootlogo\Logo folder

- go in settings->device->boot logo to apply your new logo.

- if you use the KoTiX ROM you can add your logos to the 'logo' folder so they will flashed within the rom files. Then you can set your preferred logo in the personize.prop file in the config folder

Custom Buttons

You can assign different functions by editing ADSet.xml in /config before flashing or on the unit itself, here is the list with the buttons you can choose from:

Old_Rem_open 20 Old_Rem_angle_dec 87 Old_Rem_angle_add 65 Old_Rem_src 70 Old_Rem_eject 9 Old_Rem_fr 29 Old_Rem_ff 31 Old_Rem_dvd 13 Old_Rem_play 25 Old_Rem_next 17 Old_Rem_prev 27 Old_Rem_navi 21 Old_Rem_goto 23 Old_Rem_disp 18 Old_Rem_menu 89 Old_Rem_band 8 Old_Rem_sound_add 80 Old_Rem_menu_up 72 Old_Rem_mute 94 Old_Rem_menu_left 6 Old_Rem_enter 5 Old_Rem_menu_right 3 Old_Rem_sound_dec 71 Old_Rem_menu_down 64 Old_Rem_mode 24 Old_Rem_1 68 Old_Rem_2 15 Old_Rem_3 81 Old_Rem_4 30 Old_Rem_5 14 Old_Rem_6 26 Old_Rem_7 82 Old_Rem_8 1 Old_Rem_9 69 Old_Rem_10 10 Old_Rem_0 83 Old_Rem_eq 85 Old_Rem_cap 74 Old_Rem_aud 7 Old_Soft_Rem_BT_Call 231 Old_Soft_Rem_BT2_Call 65 Old_Soft_Rem_BT_Recall 233 Old_Rem_test_poweron 234 Old_Rem_test_poweroff 237 Rem_volume_add 76 Rem_volume_dec 77 Rem_pow 75 Rem_KEY_pow 214 Rem_angle_dec 74 Rem_angle_add 73 Rem_open 72 Rem_nightmode 71 Rem_videomode 70 Rem_pip 69 Rem_eq 68 Rem_dvd 67 Rem_menu_up 66 Rem_src 65 Rem_menu_left 31 Rem_enter 30 Rem_menu_right 64 Rem_navi 27 Rem_menu_down 29 Rem_band 28 Rem_call_receive 26 Rem_menu 25 Rem_call_reject 24 Rem_eject 23 Rem_play 22 Rem_stop 21 Rem_disp 20 Rem_prev 19 Rem_ff 18 Rem_fr 17 Rem_next 16 Rem_setup 15 Rem_sound_dec 14 Rem_sound_add 13 Rem_mute 12 Rem_1 11 Rem_2 10 Rem_3 9 Rem_4 8 Rem_5 7 Rem_6 6 Rem_7 5 Rem_8 4 Rem_9 3 Rem_10 1 Rem_0 2 Rem_other 0 Rem_enter_GOD 32 Rem_digi_red 96 Rem_digi_green 97 Rem_digi_blue 98 Rem_digi_yellow 99 Rem_digi_epg 100 Rem_digi_key 101 Rem_digi_recall 102 Rem_digi_fav 103 Rem_digi_ttx 104 Rem_digi_menu 105 Rem_digi_info 106 Rem_digi_exit 107 Radio_Rem_prev 108 Radio_Rem_next 109 vdisc_Rem_nor 112 vdisc_Rem_fast 113 vdisc_Rem_delete 114 vdisc_Rem_copyexit 115 vdisc_Rem_disc1 116 vdisc_Rem_disc2 117 vdisc_Rem_disc3 118 vdisc_Rem_disc4 119 vdisc_Rem_disc5 120 vdisc_Rem_disc6 121 vdisc_Rem_disc7 122 vdisc_Rem_disc8 123 vdisc_Rem_disc9 124 vdisc_Rem_disc10 125 vdisc_Rem_disc11 126 vdisc_Rem_disc12 127 vdisc_Rem_disc13 128 vdisc_Rem_disc14 129 vdisc_Rem_disc15 130 vdisc_Rem_disc16 131 vdisc_Rem_disc17 132 vdisc_Rem_disc18 133 vdisc_Rem_disc19 134 vdisc_Rem_disc20 135 Rem_dvd_AB 138 Rem_dvd_zoom 139 Rem_dvd_angle 140 Rem_dvd_goto 141 Rem_usb 145 Rem_dvd_display 146 Rem_dvd_title 147 Rem_dvd_pbc 148 Rem_dvd_capture 149 Rem_dvd_return 150 Rem_dvd_audio 151 Rem_dvd_sub_t 152 Rem_dvd_Last_Memory 153 Rem_cd_save 154 Rem_dvd_repeat 155 Rem_dvd_random 156 Rem_AST_scan 158 Rem_scan 159 Soft_KEY_COLOR 154 soft_Rem_mode 155 Soft_Rem_cap 156 Soft_Rem_aud 157 Soft_Rem_aux 212 Soft_KEY_sound 159 Soft_GPS_POS 160 Soft_GPS_DES 161 Soft_GPS_ZOOMADD 162 Soft_GPS_ZOOMDEC 163 Soft_Rem_vcdc 164 Soft_KEY_tv 165 Soft_opel_BC 166 Soft_opel_OK 167 Soft_opel_LEFT 168 Soft_opel_RIGHT 169 Soft_opel_SET 170 Soft_opel_setexit 171 Soft_Rem_fm 172 Soft_Rem_am 173 Soft_opel_N1 176 Soft_opel_N2 177 Soft_opel_N3 178 Soft_opel_N4 179 Soft_opel_N5 180 Soft_opel_N6 181 Soft_opel_N7 182 Soft_opel_N8 183 Soft_opel_N9 184 Soft_Rem_cam 185 Soft_Rem_prodo_receive 202 cruze_Rem_config 203 cruze_Rem_time 203 cruze_Rem_back 204 Rem_steer_src 205 cruze_Rem_prev 206 cruze_Rem_next 207 Soft_Rem_left 215 Soft_Rem_right 216 Soft_Rem_enter 217 Rem_android_home 229 Rem_android_menu 230 Rem_android_back 231 Rem_null 255

Custom Configuration Backup

The user is able to save it's current configuration by copying the /config folder from the unit /bootlogo/config/. Root access is required.

By copying it over the /config folder used in the flashing process, after the upgrade is done, the unit automatically applies the user configuration.

Files in /config folder:


bindDir.conf - This are the directories in /mnt/sdnavi/ which you want to mount -o bind to /mnt/harddisk

FactoryModeValue.xml - SETTINGS FILE, pretty self explanatory, allows to set led color, and ... settings... use with caution!

Locales.xml - You can delete all those unwanted locales from here, leave only one or two, but ... I wouldn't bother, as you can set your language from elsewhere! And more languages are cool!

naviApps.conf - What GPS programs you have?!

personize.prop - This is like build.prop

Common problems

S100 firmware problems

- The Roadnav released new firmware(firmware version OS: S100-UNI.A20140721-A2.2 APP: S100-V1.8.9.0) on October 2014 and Nov 2014, this firmwar will allow the radio support station names. This function works well in Europe countries. But in North America, it will cause some problems, for example, the stations name display mess code instead of stations name or freq. Here is the problem video: This can be fixed by upgrade a new firmware which remove the radio station name function(please contact the dealer who sold you the S100 product and request the firmware). The radio works normally after new firmware update:

2.34 firmware problems

- If the unit is not booting completely (powered for a very short time) there are some error messages that appear, which require the unit to be reset to factory settings. There are some suspicions that this is caused by /cache partition corruption. This can be fixed by installing the Delayed shutdown hardware mod(forum user mihaiolimpiu).

- You can't access android standard system setting, although it's possible to access them the first time you install a apk. A separate app/shortcut has to be installed.

Solution required.

4.03 firmwares problems

- Steering wheel controls work only with stock players (stock apps).

- In order to hear voice directions from your navigation software, you must specify in the Settings->Navigation the application you are using, else you will have issues with radio and music players.

- Using the Custom 4.03 firmware that come with Google Apps included you have to enable the "Stay Awake" feature in the Developers Options in Settings menu.

- There is noise in the background of bluetooth connection.

- Some users reported a significant hissing noise. This is caused by wrong MCU.

- Reverse camera video stream is zoomed in. This is caused by wrong MCU. Use the one for Gingerbread that fits your unit.

- Bluetooth Music starts automatically, you have to disable Audio Media on phone.

- Built in stock music player closes because of lack of RAM on the device and improper coding. Also there are more bugs related to high memory usage in ICS (It's the same thing): Suddenly wallpaper is gone and only black background, Navi and Mp3 don't work well together, suddenly no navi sound or navi just shut down itself or Mp3 doesn't work, apps close without reason etc.

- IGO (GPS aps) starts sometimes faster than the card is made available so it gives an error and possibly resetting all setting.

- IGO (GPS aps) even if closed in last session keep autostarting on startup.

- Wireless once connected to a low quality network treats every subsequent connection as low quality thus won't be able to connect to any network for ~3Hours.

- SD card on HUAWEI modems are not recognized and show as corrupted.

- The stock firmware is ZOOMED because of low dpi settings. Kotix included a fix in his Aroma 2.1 firmware.

Compatible USB devices

Wifi Dongle

1. TP-Link TL-WN7200ND

2. TP-Link TL-WN727N (there are different versions of that donge, only v3 uses the 5370 chipset!)


4. LogiLink WL-1045 (RT5370)

Anyone based on chip ralink 2070, 2870, 3070, 5370, 8192 (for 4.03 only 5370)

Bluetooth Dongles

3G Dongles

Huawei: E160, E171, E173, E261, E352b(NOT Huawei E352),E1750, E1780, E3131, E1550, EC122.

ZTE: AC581, MF190, MF192, MF662.

Attention: The 3G APN is saved ONLY if it's valid and a proper connection is made. It's not possible to save another network's APN "for future use" without a valid, working SIM card!

USB Hubs

Self Powered

The units accept all sorts of HUBS, and thus it allows connecting more devices on the two USB ports. Keep in mind that the total power requirement of the devices (including HUB) must not exceed 500mA.

Confirmed working:

HAMA 4 port USB hub (unpowered).

Bus Powered

USB Storage Devices

About any Mass storage compliant device should work. Attention needs to be paid to the power consumption of the devices, external power supply or powered hub is strongly suggested for non solid state hard drives

Hardware mods

USB OTG location

Photo USB OTG (Hardware Mod) - the bottom 5 pins that are somewhat in the center of the picture are from left to right:

GND DataWhite DataGreen SENSE Vbus (Sense PIN doesn't need to be wired)

This allows to use ADB on PC to connect to the S150 android unit. (from forum user mihaiolimpiu)

USB access to CD magazine

Photo , the 6 holes port labeled CN3 - USB on the secondary board is in fact the virtual CD magazine and watching from above the board the pins are from left to right:

x x DataGreen DataWhite GND +5v (from forum user mihaiolimpiu)

Delayed shutdown

Schematic This is required to fix short start/stop interval bug in android gingerbread roms.

The shutdown of the unit can be delayed by installing a shutdown delay relay to the ACC line before the radio, it this way, by adding a delay when the ACC line goes off, we still allow the radio to do a complete startup. A delay of 30 seconds to 1 minute should be more than enough.

You can search for any delay relay that matches this specification: Automotive timer relay - delayed shutdown, positive command, positive output, 12V/40A YouTube Video (from forum user mihaiolimpiu)

Common installation mistakes

Bad radio reception

A lot of the newer cars have BUILT IN AMPLIFIERS, that are powered trough the radio's coaxial cable with +12V. Usually the amplifiers are located in the base of the antenna. Make shure you connect ANT Control to +12V (Accessories line or Antenna Control line if available). (from forum user mihaiolimpiu)

Night/Day Illumination doesn't work

Some cars use other protocols to send running parameters (think CANBUS) so you need to connect ILL+ (Illumination) to +12V from the headlights (or dashboard lights). You have to check that on that wire there is +12V ONLY when the headlight short/long beams are ON. Be careful that some cars turn off LOW BEAM when HIGH beam is Turned ON, In this case you have to use a relay or take 12V from the dashboard lights! (from forum user mihaiolimpiu)

The unit keeps playing after ignition key is removed

This could be ON PURPOSE but usually is just a mistake. Most installers tie together +12V to the ACC (Accessories line). This has the advantage that the radio keeps playing even without the key in the ignition, but it could empty your car battery in no time if you forget the unit ON.

Make sure +12V and Accessories are kept separate and properly connected!