yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] KoTiX2:
You have to try each configuration until you find the one that is ok for your model, the first part is ok :

<DATE>
<define id="216" derivativeID="0" name="C216"/>
<openLogo id="0"/>
<LCD id="1"/>
</DATE>

you need to find the right second part:

<configuration winca="1">
<!--C079-->
<ADValue>
<ADValue1 v0="231" v1="197" v2="38" v3="211" v4="73" v5="145" v6="21" v7="128" v8="100" v9="159" v10="223" v11="5" v12="171" v13="32" v14="255" v15="255"/>
<ADValue2 v0="3" v1="21" v2="38" v3="171" v4="73" v5="197" v6="110" v7="211" v8="145" v9="223" v10="50" v11="231" v12="213" v13="232"/>
</ADValue>
<ADFunc>
<ADFunc1 v0="Rem_src" v1="Rem_eq" v2="Rem_sound_add" v3="Rem_eject" v4="Rem_sound_dec" v5="Soft_Rem_left" v6="Rem_navi" v7="Soft_Rem_right" v8="Rem_dvd" v9="Rem_call_receive" v10="Rem_menu" v11="Rem_call_reject" v12="Rem_scan" v13="Rem_play" v14="Rem_null" v15="Rem_null"/>
<ADFunc2 v0="Rem_nightmode" v1="Rem_1" v2="Soft_Rem_aux" v3="Rem_ast" v4="Rem_ff" v5="Rem_band" v6="Rem_fr" v7="Rem_next" v8="Rem_stop" v9="Rem_prev" v10="Rem_pow" v11="Rem_mute" v12="Rem_usb" v13="Soft_Rem_enter"/>
</ADFunc>
</configuration>

or

<configuration winca="4">
<!--C229-->
<ADValue>
<ADValue1 v0="3" v1="149" v2="178" v3="191" v4="239" v5="223" v6="255" v7="255" v8="255" v9="255" v10="255" v11="255" v12="255" v13="255" v14="255" v15="255"/>
<ADValue2 v0="255" v1="255" v2="255" v3="255" v4="255" v5="255" v6="255" v7="255" v8="255" v9="255" v10="255" v11="255" v12="255" v13="255"/>
</ADValue>
<ADFunc>
<ADFunc1 v0="Rem_pow" v1="Rem_eject" v2="Rem_src" v3="Rem_nightmode" v4="Rem_navi" v5="Rem_band" v6="Rem_null" v7="Rem_null" v8="Rem_null" v9="Rem_null" v10="Rem_null" v11="Rem_null" v12="Rem_null" v13="Rem_null" v14="Rem_null" v15="Rem_null"/>
<ADFunc2 v0="Rem_null" v1="Rem_null" v2="Rem_null" v3="Rem_null" v4="Rem_null" v5="Rem_null" v6="Rem_null" v7="Rem_null" v8="Rem_null" v9="Rem_null" v10="Rem_null" v11="Rem_null" v12="Rem_null" v13="Rem_null"/>
</ADFunc>
</configuration>

Or any other until you find it.

I don't know if yo uhave to change the number after winca= try and figure it out.
[Android Head-Units] Cristallx:
Kotix,

Tomorrow I'm free and I'm going to try yours suggestions.

THANKS a lot !
[Android Head-Units] dom_christo:
Is this the white screen bug that you are talking about?

Happened a few times this morning after flashing the new firmware last night.

http://i.imgur.com/TkOwiLv.jpg

http://i.imgur.com/KXs2eKk.jpg

Seemed to be working OK last night when I was setting it up, could be a time out issue?
[Android Head-Units] TvBIFI:
I bet this lines should do the trick

i´ve compared an C005 with C216 ADSet.XML and the only change was the define Line

---------- Post added at 12:07 AM ---------- Previous post was at 12:05 AM ----------

possibly work around is Settings / Developer / stay awake when plugged in
[Android Head-Units] sammybarlow:
Yes that looks the same. Does it Happen after 5 minutes? It Is the screen lock and can be resolved by going into settings and selecting the "do not put the unit into standby on charging option" or words similar to that effect.
[Android Head-Units] deemag:
Thank you!

But whats about new devices that are sold now with pre-installed Android 4?

All of this all have same bug?
[Android Head-Units] donaldta:
Well, yes but I do not believe the manufacturer considers this a bug. This mechanism is obviously

intended

by design. You cannot "accidently" program an OnKey listener to pick up both Linux scancodes and Android keycodes regardless of the app in focus then block other programs from reacting to it. The programming required for this functionality has to be intended.
[Android Head-Units] deemag:
But Android 2.3.4 works fine with PowerAMP. Does it mean that manufactures implemented this functionality in 2.3.4 and forgot about it in 4.0 ?
[Android Head-Units] donaldta:
:eek:

No, that meant they decided to change the functionality from 2.3.4 to instead trap the signals in 4.0.3 version of Android. I'm not sure how I can make this any clearer to you that they had to intentionally add this "feature" in order for this to occur. These are lines of code that had to be written specifically for this to work this way. It wasn't an accident. It wasn't oversight. It wasn't happenstance. It was I-N-T-E-N-T-I-O-N-A-L when they updated their software code from the older version of Android to the newer version.

An analogy would be like when they started enforcing the laws against the sale of cigarettes and alcohol to minors. The day before this occurred, you could send your kid to the corner store and have them grab a pack of cigarettes or 12-pack for you. Now a days the people involved can get arrested for this. That's because of the change and this was intentional.
[Android Head-Units] ildiko2:
It can't be because of the 9600Baud-GPS. Navigation works flewently on 2.3.4-firmware !

...maybe it's because of 4.0.3. need much more ressources

...or (thats what i think) the GPS-part of the 4.0.3 firmware has a bug !!!
[Android Head-Units] deemag:
I'm sorry, i had to write 'forgot' word in quoutes. I mean that I'm understand this intent thing.

So there is no chance now to get it works.

And at the same time I can't flash my unit to 2.3.4 firmware? (S100)
[Android Head-Units] donaldta:
Well, we can play around to try and get it to work. Maybe try installing Autorun Manager. Start the app and wait for the initialization to complete. Find that app(s) that is intercepting the multimedia keys and click on it. All of its listeners will be on the bottom with check boxes marked. . Uncheck the ones like "remote control". Reboot the device. Wash, rinse, repeat until you kind find the correct receivers to disable.

Not sure. I don't know.
[Android Head-Units] deemag:
Thanks, I will try it today!
[Android Head-Units] dom_christo:
That did the trick! Cheers.
[Android Head-Units] KoTiX2:
Until now all I tryed to have at least two buttons working with poweramp was a complete failure, maybe you are more lucky than me :P

Everybody who tryed to flash a 2.34 fw on s100 got bootloops after flash, it does flash flawlessy (you have to use the right bootloader) but then android can't boot.

Again... maybe you are more lucky and you'll got it working. :P

Ciao :)
[Android Head-Units] np27np27:
Yes I can't install 2.3 on my s100 either. Surely someone has managed to do this? Maybe someone can check the Russian 4pna forums.

Or has the s150 slightly different hardware? I thought they were meant to be the same units?
[Android Head-Units] Cristallx:
Yes!!! The hard buttons work :) , so now i changed my S100 WinCe device to a full working S150 Android 4.03 device ..

I wanna thank all the developers here on XDA for the hard work and the sharing of their knowledge.

Here is my working ADset file for everybody that wanna change the S100 for Kia Ceed (model 2013 C216 WinCe) device to a I216 (Android) .

<?xml version="1.0" encoding="utf-8"?>

<!--注意属性与值之间中“=”要不留空格-->

<ADSet>

<versions></versions>

<DATE>

<define id="216" derivativeID="0" name="c216"/>

<openLogo id="0"/>

<LCD id="2"/>

</DATE>

<configuration winca="4">

<!--C229-->

<ADValue>

<ADValue1 v0="3" v1="149" v2="178" v3="191" v4="239" v5="223" v6="255" v7="255" v8="255" v9="255" v10="255" v11="255" v12="255" v13="255" v14="255" v15="255"/>

<ADValue2 v0="255" v1="255" v2="255" v3="255" v4="255" v5="255" v6="255" v7="255" v8="255" v9="255" v10="255" v11="255" v12="255" v13="255"/>

</ADValue>

<ADFunc>

<ADFunc1 v0="Rem_android_home" v1="Rem_eq" v2="Rem_sound_add" v3="Rem_eject" v4="Rem_sound_dec" v5="Soft_Rem_left" v6="Rem_navi" v7="Soft_Rem_right" v8="Rem_dvd" v9="Rem_call_receive" v10="Rem_band" v11="Rem_call_reject" v12="Rem_mute" v13="Rem_play" v14="Rem_null" v15="Rem_null"/>

<ADFunc2 v0="Rem_nightmode" v1="Rem_1" v2="Soft_Rem_aux" v3="Rem_2" v4="Rem_ff" v5="Rem_3" v6="Rem_fr" v7="Rem_4" v8="Rem_stop" v9="Rem_5" v10="Rem_KEY_pow" v11="Rem_6" v12="Rem_usb" v13="Soft_Rem_enter"/>

</ADFunc>

</configuration>
[Android Head-Units] KoTiX2:
Great!! :good:

But, really, this is your File:

<?xml version="1.0" encoding="utf-8"?>
<!--注意属性与值之间中“=”要不留空格-->
<ADSet>
<versions></versions>
<DATE>
<define id="216" derivativeID="0" name="c216"/>
<openLogo id="0"/>
<LCD id="2"/>
</DATE>

<configuration winca="4">
<!--C229-->
<ADValue>
<ADValue1 v0="3" v1="149" v2="178" v3="191" v4="239" v5="223" v6="255" v7="255" v8="255" v9="255" v10="255" v11="255" v12="255" v13="255" v14="255" v15="255"/>
<ADValue2 v0="255" v1="255" v2="255" v3="255" v4="255" v5="255" v6="255" v7="255" v8="255" v9="255" v10="255" v11="255" v12="255" v13="255"/>
</ADValue>
<ADFunc>
<ADFunc1 v0="Rem_android_home" v1="Rem_eq" v2="Rem_sound_add" v3="Rem_eject" v4="Rem_sound_dec" v5="Soft_Rem_left" v6="Rem_navi" v7="Soft_Rem_right" v8="Rem_dvd" v9="Rem_call_receive" v10="Rem_band" v11="Rem_call_reject" v12="Rem_mute" v13="Rem_play" v14="Rem_null" v15="Rem_null"/>
<ADFunc2 v0="Rem_nightmode" v1="Rem_1" v2="Soft_Rem_aux" v3="Rem_2" v4="Rem_ff" v5="Rem_3" v6="Rem_fr" v7="Rem_4" v8="Rem_stop" v9="Rem_5" v10="Rem_KEY_pow" v11="Rem_6" v12="Rem_usb" v13="Soft_Rem_enter"/>
</ADFunc>
</configuration>
</ADSet>

The rest of it is commented out and not readed by the sw, so please edit your loooooong post and leave just this part. Tnx ;)

As you can see your C216 unit is using the button configuration from C229.

Other people having problems with the hard button should do the same thing, find their button config looking in the original wince ADset.xml
[Android Head-Units] Cristallx:
So ... post edited ;) .

Thanks !
[Android Head-Units] w3bm4n:
Yes! This option worked for me, no more white screen, thank you! ;)
[Android Head-Units] jemael972:
Waze

anyone find a version of waze who works with android 4.0 FW ????

3.6 OR 3.5.1.4 maybe works
[Android Head-Units] donaldta:
Since it seems you're a broken record about this. Have you tried contacting the developer for support? This may be a better idea than to arbitrarily install older Waze versions with hope it will work. Another thing... Do you have Google Maps and Google Play Services installed on your system? Waze is dependant on these packages being installed for it to work appropriately. Before we try to find you an alternate Waze package let's try troubleshooting what's wrong with the current 3.7.7.0 version on your device.

If Waze is automatically force closing after you launch it, then use these commands in a terminal app to gather the information about the problem.

$ [COLOR="RoyalBlue"][B]su[/B][/COLOR]
# [B][COLOR="RoyalBlue"]logcat -c; sleep 1; am start -n com.waze/.FreeMapAppActivity; sleep 10; logcat -df /mnt/sdcard/waze-logcat.txt[/COLOR][/B]

If Waze takes some time or requires certain manipulation before it force closes, then use these commands in a terminal app to gather the information about the problem:

$ [COLOR="RoyalBlue"][B]su[/B][/COLOR]
# [B][COLOR="RoyalBlue"]logcat -c; sleep 1; am start -n com.waze/.FreeMapAppActivity[/COLOR][/B]
[COLOR="Silver"](do whatever is necessary to make Waze force close)[/COLOR]
# [B][COLOR="RoyalBlue"]logcat -df /mnt/sdcard/waze-logcat.txt[/COLOR][/B]

Either way, the output of the problem should appear as a text file located in /mnt/sdcard named, "waze-logcat.txt". If you upload the file, I can take a look at why you're having problems.
[Android Head-Units] gochapka:
Dear, so I understand your excellent explanation of the smartphone is a "hosts" and OBD2 adapter is a "client".

However, if the smartphone sends music via Bluetooth to Car-DVD unit, then the smartphone is a "host" and the Car-DVD unit that is?

I interpret that is also a "hosts" and that BT also sends data to the smartphone.

Then we have the smartphone and Car-DVD unit are "hosts", and exchanging data with each other.

On the other OBD2 adapter not only sends data to the smartphone, but you can eliminate errors, sending your smartphone data to it, then the adapter would also be a 'hosts'.

Conclusion; being all "hosts" would not have communication problems, no? Or is there something that I missed and I do not understand?.

Greetings.

PS: I hope I understand this explanation. :silly:
[Android Head-Units] Allen Wong:
Firmware for S100/S150

Sorry for late reply to many questions from you guys. I can only have a look at this forum after my daily work.

Here are some new firmwares:

S100 Wince OS Firmware For C012 released

Version:6.0

OS:S100-UNI.A20131106-V2.0

APP:S100-V1.4.8.0

MCU:F00K S00B

Product page: Mazda 6 2008-2012 Aftermarket Navigation Autoradio

Check "Hardware & Software" to see the download link.

S100 Wince OS Firmware For C045 released

Version: 6.0

OS: S100-UNI.A20140106-A2.1

APP: S100-V1.0.9.0

MCU: 000L S00E

Product page: Chevrolet Cruze 2008-2012 Autoradio GPS Navigation Head Unit

Check "Hardware & Software" to see the download link.

S100 Wince OS Firmware For C050 released

Version:6.0

OS:S100-UNI.A20140106-A2.1

APP:S100-V1.1.9.13

MCU:E00L S00E

Product page: Audi A4 S4 RS4 2002-2008 Autoradio GPS Navigation Head Unit

Check "Hardware & Software" to see the download link.

Android 2.3 OS Firmware For I008 released

Version: 2.3

Build number: GRJ22.V4.04.08-20140115

MCU: B003

FLASH: S00C

Product page: Android OS Navigation Radio Player For Hyundai Santa Fe

Check "Hardware & Software" to see the download link.

Here is a video show you how to upgrade the firmware 2.3 to 2.3 or s100 to s100.

https://www.youtube.com/watch?v=SS7W4NN8XlE

Do Not guarantee it will work the same as 4.0 <->2.3 or S100 <->4.0.

Upgrade the firmware at your own risk.
[Android Head-Units] bypo:
Thanks Allen.

First post updated with those firmwares!
[Android Head-Units] gochapka:
Hi [MENTION=5699280]Allen Wong[/MENTION] ! Could here raise the FW Special DVR S150 camera model, please.

Also indicate how to proceed for the upgrade of this camera.

Thank you!
[Android Head-Units] donaldta:
The "Car-DVD" is a client while your smartphone is a host.

No, the data can be sent bi-directionally between host and client. The problem is pairing. Two Bluetooth clients cannot pair with one another.

No.

:eek: Who's on First?

No

Yes
[Android Head-Units] Allen Wong:
What's the issue of your DVR camera? A short demo video will be helpful.
[Android Head-Units] donaldta:
Allen, his problems are documented (with pictures) in Post #693.
[Android Head-Units] gochapka:
@donaldta & [MENTION=5699280]Allen Wong[/MENTION], Thanks donaldta but some of those problems were solved and the new FW 4.0.3 and IGO.apk which supplied Allen, the major problem that remains unresolved is the cámaraDVR.

I will make a video trying to explain what happens, thank you very much.

However, Allen, in your e-mail I sent some information about how many days now, I have no trouble making new samples.

Greetings.

Unfortunately I had an accident with the car and it has not been possible to register!! :(
[Android Head-Units] costinradu:
Hi Allen, any hope for Audi-a4-s4-rs4-2002-2008 Android firmware?
[Android Head-Units] TvBIFI:
Add following lines to Sys.txt

[android]
fullscreen=1
[Android Head-Units] TvBIFI:
tried testing 3.7.7.0 on my rom but no luck

The app starts but says "Couldnt find SDCard"

i will try tomorow this or u try (found at waze.com)

I found that the problem is caused by a temporary file called smdl2tmp1.asec that is used during some installations (I think of apps that are movable to SD) but does not get deleted for some reason, most notably when you run out of space. Because of this, the system can't create it and treats it as an error, rather than figuring out that it's stale and simply deleting it.

The solution? Go and delete smdl2tmp1.asec yourself. From what I can tell, it could reside in 2 locations:

/sdcard/.android_secure - this is an invisible folder on your SD card, which you can access with any file manager, like ASTRO
/mnt/secure/asec/ - access to this folder requires root and a program like Root Explorer
Look for smdl2tmp1.asec in these folders and delete any ones you see.
[Android Head-Units] Gassi2106:
My device is show an error when i plugged in the second sd card.(GPS sd or media sd)

Gesendet von meinem HUAWEI U9508 mit Tapatalk
[Android Head-Units] DenisMS79:
Allen Wong

Hello Prompt for my device has firmware?

S100 Wince OS Firmware For C206 released

Version:6.0

OS:S100-UNI.A20131106-V2.0

APP:S100-V1.2.8.0

MCU:A00K S00B C206

DVD:1227 V100 7705

BT:20121204

CAN BUS: YES

OEM Info: A002
[Android Head-Units] TortoiseCat:
IX45

Hi mister allen, no updates for the Santa Fè III series ( IX45)?

have a nice day
[Android Head-Units] jemael972:
I test with root explorer but no smdl2tmp1.asec on the device.. I will back again in 2.3

Envoyé de mon SM-N9005 en utilisant Tapatalk
[Android Head-Units] dom_christo:
Some quirks with 4.03 anyone else experiencing similar issues?

Bluetooth:

Volume in calls is REALLY soft. I have to turn the volume up to about 30~

Audio streaming is REALLY loud. At volume 10 it is very distorted.

(I have given up on streaming Bluetooth audio, using poweramp with USB drive.)

Application volume:

Poweramp volume seems to be really soft compared to beta 4.03? Increasing the “Video” application volume seems to increase volume for poweramp.

Reverse camera: seems “Zoomed in” it cuts off maybe 25% of the screen. Bug in both Beta and Official 4.03 firmware. Worked fine in version 2. Anyone have any pointers on where to start troubleshooting? IM guessing it might be a resolution / region setting PAL / NTSC or something like that.

Application handling. First time I had the radio open, Opened poweramp and it closed the radio app. Like it should. However I haven’t been able to replicate this behaviour. Both applications stay open, both will play sound.

If somehow I manage to get Poweramp to be the only application open, I would like poweramp to be the application that starts when the unit powers on. However it will open the last used “stock” application. Anyway to change this? I think there has already been some discussion on this.

Have not fully tested GPS function yet. But keen to use Google Maps / Nav. When opening google maps I can see it says my location accurate to 999990 meters or something along those lines. Enabling all location / gps does not seem to effect anything.

Voice control? Would be cool if we could integrate google now / voice search to call contacts etc. But this would be a big project im guessing.

A weird issue though, when I try to make a voice command on my phone, say to call a contact, the head unit seems to hijack the command? And nothing seems to happen. Might have to turn off Bluetooth mic or something like that to the command goes straight to the phone.

Anyway very happy with this release so far. Seems to be working better than the beta firmware.

Big Thanks to all who have spent endless hours on this. Your efforts are much appreciated.
[MENTION=5389783]donaldta[/MENTION] and [MENTION=2734955]KoTiX2[/MENTION]

And [MENTION=5306553]bypo[/MENTION] for starting this glorious thread :D
[Android Head-Units] belciugc:
Fiat Bravo C250 s100 unit

Hi Allen,

Can you please upload the last firmware for C250 s100 unit(for Fiat Bravo)

Thanks
[Android Head-Units] Franky692:
Grj22.v4.04.08-20140115

Hi everybody,

I would like to try the GRJ22.V4.04.08-20140115....

if I take any GRJ22.V4.04.08-20140115

I unrar it on a SD

I replace the config directory with mine (I061)

I insert SD in Music Video slot on my HU.

I go into settings and hit "firmware update"

Thats all?

Anybody is trying GRJ22.V4.04.08-20140115?
[Android Head-Units] cretu_24:
Hi there,

Same problems here and for the moment i'm back in 2.3

Android 2.3 OS Firmware For I802 released.

Version: 2.3

Build number: GRJ22.V4.00.00-20131121

MCU: P002

FLASH: S00C

Product page: Android OS Universal Double Din DVD Player Navigation System

Check "Hardware & Software" to see the download link.

I'm waiting for good news with 4.0.3 version and thank you again for all the work !
[Android Head-Units] KoTiX2:
You can change the App volume in the second page of the Volume adjust screen.

Everythink is controlled by the winca.service.apk and it's not moddable, btw You can try using "tasker" or "llama" to adjust the sequence as you like.

Maybe with gapps installed we will be able to have voice recognition directly on the unit instead of the phone?

Cheers :)
[Android Head-Units] royalhawk2002:
Could you please post the link to the russian post and also the link to the sw ? Thank you.
[Android Head-Units] alejo:
Waze and other problems

Hi everyone,

I have managed to D/L and install Waze thru Aptoide (www.aptoide.com), it is an app store that allows you to download pretty much any APK without checking what kind of device you have. For those people that have gotten the SD card error when trying to run Waze, insert a 2GB SD card in the right side slot and it will work. The 4.03 FW seems to have cut access to the 4GB internal memory which was available as an SD Card in the 2.3 FW, that may be why Waze and other apps that need to store data in the SD partition do not run. Is there any workaround for this?
[Android Head-Units] nitroalfa:
android 2.3.4 af work

this is the link http://4pna.com/showpost.php?p=359354&postcount=5111 this is download http://www.sendspace.com/file/i7yfbn
[Android Head-Units] jemael972:
If i undestand ... i m actually in 4.03FW the 2go SD card method dont works ??
[Android Head-Units] donaldta:
Nope. Google did not officially support offline "voice typing" until Jellybean (Android 4.2 - API level 17). However, it was enabled for select Android 4.1 devices based on hardware specifications. The "Download Offline Speech Recognition: Enables voice input while offline" option was found in Settings > Languages & Input > Google Voice Typing settings.

You might be able to use Voice Command without Internet from Google Play to perform similar yet limited functionality.
[Android Head-Units] tommern_nor:
Downgrade from 4.0.3 to 2.3

Hi everyone.

I would like to downgrade from 4.0.3 and test the 2.3 version and have downloaded the files and put them in winca folder and on the root of sd card just like when i upgraded from win CE but the screen is only black and upgrade not starting.

I have downloaded the official 2.3 for wolksvagen in the first post.

What files do I need on the sd card besides the one in the rar file and can i do a system upgrade from the menu in 4.0.3??

Thanks in advance.
[Android Head-Units] deemag:
Somebody have troubles with 3G USB modem on 4.0 official with root access (KoTiX ROM)?

I just can't get my 3G modem works. In android 4.0.3 beta modem working just fine.

Now in 4.0 official (by KoTiX) it's just blinking blue (searching 3G network). APN settings is fine.

And i can't get debug 'ppp information' in android log files. But it was possible in 4.0.3. beta.

And in russian forum at least 1 man have same troubles.

He said that his modem works in 4.0.3. beta and in android 4.0 official (without root)
[Android Head-Units] tommern_nor:
I also had problems with my ZTE 190 usb modem, i cold not get it to work in 4.0.3 official or the version with root. However i managed to get around the problem with PPP Widget, when setting it ut manually i got it to work but everytime i restart the stereo i had to connect it manually again.

So i am hoping to try the official 2.3 but when i try to upgrade i only get black screen, it will not start the update/downgrade. Even reset and power button does not help.

I am hoping to get help with this issue so i can try the modem in 2.3 version.
[Android Head-Units] Franky692:
In your opinion what the difference between this file from russia friends and one of the GRJ22.V4.04.08-20140115 linked in the first post.

In the first one there is the CAN clima managment that is not used in my I061 with board without DSP ver 1.01.

Seems that the russia one is V4.04.09-20140115 instead of V4.04.08-20140115

Which one Should I use copying my config folder?