yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Karmacom:
upgrading from normal 4.0.3 to KOTIX's Official 4.0.3 Aroma V2.0 - please help

Hi, I have some autistic-detailed-style questions (since I really need things explained with a spoon - a saying/term her in Norway,not sure it makes sense in english):

1: How do I upgrade to KoTiX's official 4.0.3 Aroma V2.0 when I allready have a pre-installed 4.0.3 installed? I see many guides/tutorials for how to upgrade from WINCE/S100, from Android 2.3.4/5 and so on, but none that explains what you need to upgrade from 4.0.3 to 4.0.3, what type7version of u-boot_udsd.bin bootloader file do I need etc?

2: The GPS is totally whack on my pre-installed 4.0.3 system, meaning the GPS is delayed/rubberbanding/lagging, shows wrong speed (double of my cars actual speed etc.) I read that this was a 4.0.3 bug, if so, will the bug still be there with KoTiX's 4.0.3 mod or might I get lucky? If its a bug, is there anything that can be done to port/copy over some of the system/dev files from 2.3.4? or maybe another better faster than 9600-baud antenna that works with S150? (does any brand work?) If it works flawless in 2.3.4 what are the backdraws of using 2.3.4 instead of 4.0.3, since GB/2.3.4 is pretty... old, will latest version of cygic etc work fine in 2.3.4? What about other apps, like gmail, youtube, contacts, google account, play store etc in 2.3.4? ( I dont care about the looks, since I can always use a home-launcher replacement)

3: What files do i need to save before upgrading? I dont mean just ADSet.xml, but the LOCATION / path (internal memory? sdcard?) of the ADset.xml, is there a default "factory" one, and one actual used on my device? Just so that I don't start saving the factory one, which will probarbly just contain generic values that has nothing to do with my device. I saw in "About my phone" in settings, and the MCU, FLASH, RADIO, GPS version info in that page did not correspond with the values i found in a bootlogo/config/ADset.xml.

The reason of question number 3 is that I am very, very afraid of loosing steering control, which of at the moment works flawlessly.

It would be very nice, and I would be ever gratefull, If someone could spoonfeed (this is where that spoon-analogy comes into play) me step-by-step on how to do this.

Basically:

1: locations of what to read from where to identify my units hardware.

2: What files i need to make a backup of.

3: What bootloader I need to be able to go from one 4.0.3 -> another 4.0.3 ( I reckon the SD-fusing with Friendlyarm for Windows is needed).

4: What backed up files/values needs to go back where after the upgrade.

Thanks in advance, and I sincerely appologize to and sympethize with the eyes of those whom actually read my whole post.
[Android Head-Units] mitsucats:
Hello.

Thank you that was the error. Now all works fine
[Android Head-Units] Candanga:
S150 predecessor?

Hi there,

I was looking in the market for a head unit to fit my Chevy, but the only one avail ATM is a WinCE-based one (which is OK, but Im still not convinced with some functions).

Anyone knows if a S150 predecessor is coming anytime soon?

And something else, for anyone running any of these HU in a Chevy, are all the car settings avail under the settings menu? I can't see to find any info on this on the manuals.

Cheers (:
[Android Head-Units] Karmacom:
root for 4.0.3

I have read in some other posts in the forum that one should make a backup of current /config folder, the put that into the winca folder before flashing.

The only problem is, how can I get to the contents of the /config folder? Im allready on pre-installed 4.0.3 that came with the unit and unless I have some way to root it i cant copy that folder since its in the root of the system memory. (the folder in bootlogo: bootlogo/config just has generic values so I suspect there's no use in backup up that folder).

Any way I can copy the root /config folder from my s150 or root it BEFORE/WITHOUT flashing new firmware (thus loosing my old /config folder? maybe a version of the aroma installer that just flash the kernel or something or just install root on a current 4.0.3 system?

or perhaps just removing the /config <- folder from the SD-card contents in the winca folder used to flash with?

Any ideas anyone? *hint hint KoTiX* :)
[Android Head-Units] KoTiX2:
OK sorry for the delay but i have a real life too. :p

If you have a unit with 4.03 Fw means you have a i001 unit, correct? If so, then you don't have to change anything in the config as the 4.03 Fw is made for i001.

To update a 4.03 Fw you normally don't need the SD fused, simply put the winca folder on root of SD and :

If you have the beta Fw installed ( i know you don't know) put SD in normal slot (not GPS one)

If you have 21/01/2014 Fw put SD in GPS slot

Then you can run system update from settings

If you have latest 28/03/2014 you are out of games! Well not really, i just have no idea how to do it from settings update.

Lucky us that we have the SD bootloader... In any case that none of the above won't work you can always use the SD recovery.
[Android Head-Units] Karmacom:
There is something wrong with my browser, keeps adding all my replies to one single post..

My buildnumber says IML74K20132212 so guessing its beta from 2013?

My phone info says MCU is N002 and FLASH is S00C

My ADSet.xml in bootlogo says C001

Does that tell you anything?

---------- Post added at 10:52 PM ---------- Previous post was at 10:31 PM ----------
[Android Head-Units] KoTiX2:
It just tell me that you have an older build and an older mcu then the one we all have right now.

It doesn't really matter if it was a beta or not, just try the system update putting sd in the dvd slot , if it doesn't start updating then put the sd in the gps slot and it will start.
[Android Head-Units] Karmacom:
Ok I will do it (I have the one in the picture yes) *shaking in terror*

Should I flash Flash,MCU and BT aswell? (since I have old N002 and not V003?) and what about Flash and BT?
[Android Head-Units] KoTiX2:
you can avoid BT because it hasn't changed since year, flash is the same you have already so you can avoid that too.
[Android Head-Units] Karmacom:
Ok, got it.

One last thing: the adset.xml in your aroma v2.0 says:

<define id="0" derivativeID="0" name="I001"/>

<openLogo id="0"/>

<LCD id="2"/>

the one allready in my unit in bootlogo/config says:

<define id="1" derivativeID="0" name="C001"/>

<openLogo id="0"/>

<LCD id="2"/>

So the define id is different, should i put the adset.xml from my own units bootlogo/config in the sdcad config/ before trying to upgrade, or should I go with define id="0"? (shouldnt define id be 1 for the model on the picture you posted?)
[Android Head-Units] KoTiX2:
OOps that is my mistake! Sorry, your config is correct:

<define id="1" derivativeID="0" name="C001"/>

<openLogo id="0"/>

<LCD id="2"/>
[Android Head-Units] ouzzat:
the control on the steering wheel does not work I047-ix35

after updating firmware 4.03, the control on the steering wheel does not work, I instaled 2.34 firmware and still the same problem.

Please help me find a firmware that can work.

Radio-I047 IX35 car
[Android Head-Units] Karmacom:
I have now ugraded, to your Aroma V2.1 and it works perfectly, as in P-E-R-F-E-C-T! :laugh:

All the GPS-issues with lagged/rubberbanding GPS and double carspeed is all gone! Cygic and everything else works like a charm!

As soon as I get my paycheck I'm donating those 50USD, you deserve a millionfold of that though for your work.

ALL MUST HAIL AND OBEY KoTiX ELECTROMAGNETIC ESSENCE! HIS WORD IS LAW, BE AWED BY HIS ELECTROMAGNETIC PRESENCE!!!! REPENT!! Uh.eh.... so anyhow...

I know im stretching it now but:

1:

Is it possible to bake in the standard Android/Google "Contacts" into a V2.2 as a system-app, and "Accounts and Sync..." in Settings?

2: I tried to apply a factory reset to make FactoryModeValue.xml kick in with different key colors on the buttons. But nothing happens when I start it pushing SRC for 5-10 seconds, it just starts but nothing else special happens.

Is there another way to factory reset? or perhaps another way to change the key colors from other than red, red-orange or green? Maybe an app/apk from earlier versions of from similar units?

Where does the values from FactoryModeValue.xml end up in the system, is it possible to find a file there, in root dev/class etc or something and edit it directly?

Anyhow, you have really saved my life, I now have a working GPS with no hickups, and ROOT! (And steering wheel controls worked out-of-the-box, no problems there. :good: )

:good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good:

---------- Post added at 08:47 AM ---------- Previous post was at 08:32 AM ----------

Now that my S150 is totally AWSOMENESS thanks to KoTiX Aroma V2.1 I'm going to make some variations of the radio-app's background colors by editing the APK (If possible, not all APK's will respond well to editing).

Going to start with black (basically no background at all), brushed metal, white (no background, just plain white).

If all goes well I plan on making a version for every color in the rainbow. Red radio just doesnt look good in my car (Toyota Avensis, all HUD's and lights in it are pale yellow-orange).

This will be a work in progress, and I will post some apk's and screenshots soon. :fingers-crossed:
[Android Head-Units] KoTiX2:
https://disk.yandex.com/public/?hash=c6Fn/KruuWlTMmbqxq4bdhoZ/tHa2KxUwZ2K16JkTYU=

Here you go! ;) :good:
[Android Head-Units] ouzzat:
le contrôle sur le volant ne fonctionne pas I047-ix35

thank you KoTiX2, I'll try
[Android Head-Units] Karmacom:
Battery level

I saw in some file (a .conf or rc in system, note sure don't remember will check later) that the S150 simulates battery level for some reasons, probarbly compability, and there it's been set at 5% charge i think.

The problem with that is that in some apps, like Cygic, the battery-level icon is constantly flashing, which is annoying.

Is there any reason this cant be set highe, ex, 95% (if 100% is a problem due to charge-disconnect actions etc) ?
[Android Head-Units] KoTiX2:
:D

This is the correct link:

https://disk.yandex.com/public/?hash=oSASD8NEDU2EC+aWu5v+uZkE1W3OA6kHhJRFjAh2SS0=
[Android Head-Units] Karmacom:
delayed start

KoTiX (or anyone else who might know), do you happen to know what script (and where / in what directory) that handles starting of applications that were on last time before the unit was turned off? (ex: if Navi-app was on before turning off the unit, then it will start that the next time you turn on your unit).

The reason I'm asking is becaue if you have a large SD-card with lots of media/files on it, it takes some time to do initial scan of that card before it mounts, resulting in the same SD-card not being avaivable to many of the Navi-apps when they restart at boot (they then give error "No SD-card mounted, please try again.." <- Sygic.

If there is a script that handles this, maybe I can set a timed delay or a FileExist condition-check to wait for complete mounting of extsd or sdCard.

Any suggestions appreciated. :fingers-crossed:
[Android Head-Units] KoTiX2:
The phone application is not a standard google app, so i don't know if ti will ever work as a normal phone. Btw i'll check if there are any other google app missing even after installing gapps

I can answer the color question: C001 has 3 color leds, i802 has multicolor leds. Those color settings are for i802 model, your model have only red/orange/green.

..ssshhh!!! don't tell anybody there is a 2.1 version!! ;)

Can't wait to see your mods :good::laugh:

---------- Post added at 01:54 PM ---------- Previous post was at 01:51 PM ----------

Wincaservice.apk handles all the apps priorities and startup and it cannot be modified.

I don't know if you can fix that using apps like tasker or startup managers
[Android Head-Units] Karmacom:
Its basically called contacts.apk, part of gapps originally, not fused/linked with the phone.apk because contacts can be used for things like gmail etc. I have had some luck earlier (on other Android devices) on sideloading them as system-apps and/or simply installing as a user app linked up to a google-account, though deodexed.

NOOOOOO! ..... NOOOOOOOOOOOOOOOOO!!! AAARGH....... *dies* :crying: oh well, guess ill have to buy some colored transparent foil to put inside the buttons and get my screwdriver and tools....

Hm? I meant the 2.0 one, ->one<- so I... wrote... 1 instead.. of.... ... "one"? and then it... seemed like.. or.. well... looked like V2.1 .. but I meant "the V2 one".. yes thats it, thats what I really meant.... *runs*

It gets refreshed from source each boot?

Possible to modify it before compiling the source image for upgrade?

Maybe set permission on it so it wont be allowed to run at boot/start, and then use a startup manager to mock/imitate it.

Is it the company winca who makes the original firmwares for all the devices? Are any of them possible to contact by email/website or here on xda?

Are you using multitool to decompile/compile the FM-radio app (when you made the RDS-titles bigger etc)?

And last but not leastt, sorry for bombarding you with so many questions.
[Android Head-Units] DSGVW:
so.... is there a 2.1 version? Anything drastically different than the 2.0 update? Looking to install it on my i305 unit and hoping not to lose my steering wheel controls this time around :)
[Android Head-Units] Csi02:
This fix working for me to!

Thx
[Android Head-Units] KoTiX2:
Unfortunately We don't have any source file.

Yes they are but they don't answer to modding questions.

I use multitool, someother use apkstudio.

---------- Post added at 06:05 PM ---------- Previous post was at 05:58 PM ----------

Yes and no, let me explain: a russian friend is making a mod to run the UI @160 DPI to male it work in the same way the 2.34 Fw does, without zoomed apps essentially.

He's making his own rom and i'm just copying the modded parts and adding them as an option in aroma, so kudos to him for this mod.

Whenever he finish it and with his permission i'll release the 2.1.
[Android Head-Units] Karmacom:
bootanimation

How can I change the bootanimation on S150? (not bootLOGO, but the "android" animation"). I dont see any system/media/bootanimation.zip, just aa system/bin/botanimation that is probarbly a script (havent opened it yet).

Is there a way to make the system/bin/bootanimation script call up system/media/bootanimation.zip ?

EDIT: Checked it out, the file itself is a binary, not a script. I'm using KoTiX's 4.0.3 Aroma V2 firmware
[Android Head-Units] mtresk:
Put bootanimation.zip in data/local. Works on 2.3.4.
[Android Head-Units] tdfbr:
s100 km/l instead of l/100km

Anybody know if it's possible to change fuel consumption unit to Km/L (instead of l/100km) ?

Windows CE S100 C088 (citroen c4).
[Android Head-Units] Karmacom:
thanklss, lol :) Just as I saw your post I found this in system/bin/bootanimation:

debug.sf.nobootanimation 0 BootAnimation boot animation disabled -shutdown vold.decrypt trigger_restart_min_framework /system/media/shutdownanimation.zip /system/media/bootanimation-encrypted.zip /data/local/bootanimation.zip /system/media/bootanimation.zip desc.txt descMap is null %d %d %d p %d %d %s images/android-logo-mask.png images/android-logo-shine.png SurfaceFlinger died, exiting

Looks like it looks for 3 bootanimation.zip (included the encrypted one) before finally going for the images/android-logo-mask.png images/android-logo-shine.png if it doesnt find any zips.

the binary itself (bin/bootanimation) actually a some alpha and animation engine which it processes/renders in realtime on images/android-logo-mask.png images/android-logo-shine.png from what I can understand. (found this further up in the binary:

lQuerySurface eglDestroyContext eglDestroySurface eglCreateContext eglSwapBuffers eglMakeCurrent eglCreateWindowSurface eglTerminate eglInitialize eglGetDisplay glClearColor glBindTexture glBlendFunc glClear glDeleteTextures glDisable glEnable glGenTextures glScissor glShadeModel glTexEnvx glTexImage2D glTexParameterx glTexParameteriv glTexSubImage2D glDrawTexiOES ... etc..)
[Android Head-Units] mtresk:
Sorry, my english is far from perfect and i can not undestand what you are realy looking for. You can create you own animation and put in in right place http://xdaforums.com/show....php?t=1852621
[Android Head-Units] ouzzat:
le Contrôle sur le volant ne FONCTIONNE Pas I047-ix35
[Android Head-Units] 1mdl:
update?

Hello, my S150 comme with original 4.0.3 from china. The only bug is the speed : 285 km/h when i drive at 140 km/h. Does this update solve the problem...?

Thanks:D
[Android Head-Units] ouzzat:
le Contrôle sur le volant ne FONCTIONNE Pas I047-ix35

thank you for your effort with meKoTiX2.

Always steering wheel does not work.

* info of the device:

Model Name: I047

MCU Version: D003

Flash Version: S00C

IAP 0002

CAN CONNECT INFO: FAIL

---------- Post added at 11:32 PM ---------- Previous post was at 10:44 PM ----------
[Android Head-Units] Karmacom:
The speedbug is 4.0.3 beta related in combination with old MCU-version (I think).

The Official 4.3 Aroma V2 from KoTiX fixed that problem for me 100%, I flashed the MCU that came with it.

But first:

1: Make sure you make a backup of your /bootlogo/config folder

2: Go into "Settings" -> "About phone" (on the bottom of settings). Write down and post here what it says for

Name/MCU/Build-version/Flash/DVD/Radio

3: Post a picture of your actual unit, or the product-link from where you bought it, so that we can tell exactly what version of S150 you have and thus what config-settings to use .

4: Don't drive at 140km/h lol :)
[Android Head-Units] ausbean:
sd card

Is it me or has the SD card slot stopped working with V2 firmware?
[Android Head-Units] Karmacom:
Ok, so I've screwed up some parts, need to reflash 4.0.3 V2, but for V2 i need to use SD Recovery / SD Fusing method.

What bin-file / other files do I need to reflash V2?

( I assume its not the same files needed as when going from WINCE or A 2.3.4).
[Android Head-Units] mtresk:
You need the same bootloader that you use for upgrade to 4.0.3.
[Android Head-Units] Karmacom:
I never used the bootloader, my unit came with 4.0.3 and I upgraded via "Settings" -> "System Update".

There are 3 different methods / ways to upgrade to 4.0.3 with bootloader, depending on what you're upgrading from (e.g from wince -> 4.0.3 uses another bin-file than from 2.3.4 -> 4.0.3 etc) *as far as I understand it, BUT: the chances that i've misunderstood what i've read earlier are very high*
[Android Head-Units] DJorgio:
Am i being to ambitious? Nav and Music (At the same time)?

So i have gotten to the stage where Navigation is acceptable, Music is acceptable (with Jet Audio) but asking the device to do both is too resourceful, sure i can get them to play together but after a shot period both apps expierence lag as the ram is quickly depleted.

Has anyone else got nav and music to work, I would love to get rid of the annoying built in music player which tries to take control all the time.

I have tried a few things like to increase SD Card cache, tried a few memory managers but the ram is just not there.

Any suggestions?
[Android Head-Units] 1mdl:
like answererd

Look ait the pictures please
[Android Head-Units] KoTiX2:
With this latest fw, i already posted before, I'm not able to flash another fw using the "System Update".

In the beta build flash was possible from dvd slot, in january was from gps slot, in this march release update won't start from any of them. I'm wondering if they also changed the name of the zip needed to update... for sure they have messed up something or changed something that we don't know.

Have you tryed to update using the original 28/03 fw?

Regarding SD recovery bootloaders: we have 2 bootloaders, one for 2.34 fw and one for 4.03 fw.

It doesn't matter from which fw you are coming from, if you had wince or a 2.34 or a 4.03 fw.

If you want to flash a 4.03 you have to use the uboot_udsd.bin file.

If you want to flash the 2.34 fw you have to use the uboot_sd.bin file. (it's written in the wiki too).

If you want to flash wince you have to fuse the nb0 bootloader using wince-sdboot.

:D
[Android Head-Units] Karmacom:
Hi, I meant a photo of your unit or a link to the product where you bought it if theres a website where you bought it, I need to know how it looks like so that the model can be identified (there are many versions of S150), I dont need pictures of "settings".

Also, write down the buildnumber and post it here, its in "About phone" aswell (in the bottom i believe), should show something like:

"build version: IML74K20132212"
[Android Head-Units] Karmacom:
So I've managed to fuse a SD recovery card, and reinstalled Aroma V2, but all old settings is kept.Is there some way to either wipe data, cache and dalvik cache from within android? Nandroid/Rom toolbox?

OR

Possible to boot into CWM somehow with hardware-buttons / a special update/cwm.zip or triggered from a Android-app (again, Rom Toolbox?) to gain access to the CWM-menu that would allow you to reset the unit completely?

---------- Post added at 02:33 PM ---------- Previous post was at 02:29 PM ----------

Another thing i've noticed:

If you mess around enough (with what I dont know, thus this post) the NAVI app wont autostart again at reboot even though it was open and active when the unit turned off. Is there a setting somewhere for this I have missed? When I installed fresh 4.0.3 from beta 4.0.3 that came with the unit, NAVI app would autostart if it was open when unit was turned off. But now, for some reason it wont autostart (even though it remembers current progress if im in the middle of navigation to a location if i start the NAVI app manually by pushing "NAVI".

This goes for any NAVI app. The way my system is now, no NAVi app will autostart, be it SYGIC, NAVIGON or Google Nagivation/MAPS.
[Android Head-Units] KoTiX2:
Really? Are you sure it kept all settings?? you've got to tell me how you did it! I'm struggling to find a way to don't delete user data during flash :P

In the beta fw there was the possibility to don't erase everything, in the last 2 official release i couldn't find a way. For sure once the sd recovery is started it automatically erase everything even if you don't install nothing. To check it simply choose "Quit" instead of full or custom install in my aroma.

There is no custom recovery because we don't have source files and we cannot buil one from nothing.

There is a standard android recovery that is useless for us

I hope you understand it's not easy to work on this android unit because to test every mod you make you have to go on the car to test it, it's not like having your phone on the desk and try out everything on the fly or even better trought adb commands.

My wife hate me everytime i go on the car for it :P so i do my tests at work during lunch time or even while i drive to/from work.

Sometimes, if i'm not too tired, i dedicate a couple of hours at night preparing the mod that i'll test the next morning.

So it takes really a lot of time even for doing small things such as moving a string in an apk.

Ciao :)