yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] dom_christo:
my SWC started magically working in 4.03 :D

not sure how or why, just decided to re-map the buttons and they started working.

Something weird I have noticed with 4.03.

1. A stock audio application has to be opened in order for Poweramp audio to be heard? Anyone else experienced this?

2. Reverse camera seems to be "zoomed in" usually have 2 red, 2 yellow, 2 green guide lines (2.34 android) in 4.03 the red lines are gone because it seems zoomed in.

3. Last application opened auto-launches on start up. Anyway to disable this? Diddnt notice this happening in 2.34.
[Android Head-Units] deemag:
Your SWC doesn't work at all before this moment?

My SWC works fine with default audio/video player and radio/tv

But it's not working with PowerAMP :(
[Android Head-Units] KoTiX2:
@DonaldUnfortunately your app force close as all the three version of tasker :(

Almost all the startup managers or autorun apps I've tryed or they don't see the winca service app or they see it as already set to start at boot.

So we need to find another solution... Because I can modify all the winca applications except the winca service, will it be possible to add an intent to all these applications to run the StartService when I run each of them?

@dom_christo1. there is a big problem with audio priority, if you run bluetooth you won't be able to have audio back until you switch to another winca source or if you run the radioplayer or musicplayer you'll have both audio playing togheter. To avoid this I normally switch to the videoplayer first and than start poweramp. If you use another launcher, Poweramp plays normally but then you'll need to run the wincaservice.apk to start the other services again... (I know it's wierd and a pain).

2. I don't have a reverse camera

3. I don't know

@deemagMe and donaldta are trying to figure out a way to make the SWC working with poweramp, maybe you can help on this too?
[Android Head-Units] deemag:
Sure, but I'm not sure what exactly I have to do. Can you say me please?

I'm found that some values from ADSet.xml and WheelValue.xml also located in file "wincaService.odex" (app/wincaService.odex)

But I need to de-odex this first http://xdaforums.com/showthread.php?t=1208320

Or it's a wrong way?
[Android Head-Units] KoTiX2:
No, i was referring to try to do what Donaldta explained here:

BTW if you need the deodexed version of all the apk and jars you can find them here:

https://www.dropbox.com/sh/d66kynshavj0e7y/qhCZPk7L50

or in my latest rom with gps fix here:

https://www.dropbox.com/s/4214u7lmpunstms/update_S150A.zip
[Android Head-Units] DenisMS79:
The whole day today tested on three applications at speeds up to 120 km/h Shows exactly on the speedometer.

Thank you, great job.

Root access is not enough.
[Android Head-Units] KoTiX2:
Part of the system folder with keylayout:

https://www.dropbox.com/sh/d66kynshavj0e7y/qhCZPk7L50

ok, here is the link to the s3c-keypad.kl:

https://www.dropbox.com/s/8pauer5k0qzi7gl/s3c-keypad.kl

Of course we have a similar procedure to save the swc buttons config, maybe we just don't have so many options.

I'll test your generic.kl tomorrow, everything is clear now :)

I'll build up my custom rom and flash it, like I do almost everyday now :P
[Android Head-Units] donaldta:
Seriously? Are you kidding me? Tell me you're joking. If you didn't have root access all this time, then why haven't you just inject the su binary to /system/xbin directory and the SuperSU.apk in /system/app directory?
[Android Head-Units] KoTiX2:
I told everybody I'm a noob in this kind of things :P

Su in xbin is already there and busybox in bin too :)

I just have no idea what to do for rooting android except using prepacked tools and following some tutorials for my phones.
[Android Head-Units] donaldta:
I see. lol. Well, let me explain so you know. There's a difference between "rooting an Android device" and "having root access". "Rooting a phone" usually involves exploiting security holes so that you can place a su binary into command directory (usually /system/xbin). Having root access means you can use the su binary to gain root level privileges. In other words, you can type "su" at the "$" prompt of a terminal and it will change into "#" and be able to do much more than the standard user could.

If you have an "su" binary that isn't managed then you want to replace it with one that is, like SuperSU. This will prevent newly installed or updated apps from gaining root access without your permission.
[Android Head-Units] KoTiX2:
I feel a little dumb right now but that's OK :)

This mean that i don't have to solder the otg cable anymore, right? The unit will be rooted just adding supersu.apk?
[Android Head-Units] donaldta:
Yes. But, if you're going to use the SuperSU.apk you should also replace the other su binary with the one that came with it.

Maybe before you do that test if you already had root access by typing "su" at at terminal prompt then type "id".

Btw, if you already do have root access then "OTG Cable" might have a lower priority for you. Unless you need a means of troubleshooting problems in the boot process which I believe you had asked before.
[Android Head-Units] donaldta:
Okay, try this one. I built it from scratch using Eclipse from the Android Developer's Toolkit.
[Android Head-Units] nbbankov:
Video does not show file driving

No sure if this was already answered, but I started getting a message - "Do not watch while driving…" when I try to play a DVD while in motion. How do I get rid of this?
[Android Head-Units] Franky692:
Connect the brake wire to GROUND! If I remenber the BLUE one.... with the BRAKE label. :)
[Android Head-Units] KoTiX2:
Ok guys, the 4.03 firmware is ROOTED!! :) (it has never been so easy)

My next firmware release will be a "System update" only, pratically it will not erase your apps, datas and will not make any upgrade to bootloader, kernel, BT, MCU. We have only one version of them for the 4.03 fw and we don't need to update them all the times.

@Donald

Good news with your generic.kl, now pushing Next/Prev swc buttons poweramp switch songs correctly and in the same time those buttons acts as phone and menu buttons too, but i beleive this is what you were expecting, right?

Regarding the wincaservicestart.apk, it install correctly but it doesn't do anything... should i put it in the system/app folder?

looking the problem from another side could it be maybe that the BOOT_COMPLETE condition is never verified until the default launcher has started? Is there a way to check if the condition is true?

... we definitively have to buy you a beer ;)
[Android Head-Units] stief:
Great work Guys!!!!

Awaiting your next release
[Android Head-Units] donaldta:
:good: Excellent. Pretty simple now that you know what "rooting" means, huh? ;)

Btw, now you that have root you can replace most files in place without having to flash it. Although, I wouldn't recommend in place replacements in the /system/lib and /system/framework directories.

I was actually not expecting it to do both at the same time. Are you sure that's how it works? How do they react in the stock music apps? I was actually only expecting the buttons to switched not for them to activate both functions at the same time. Please verify and elaborate more and explain better because the next step is to segregate the generic.kl file with a custom one.

Yes, it can go into the /system/app folder but for testing purposes it can be installed normally. It is supposed to be triggered by "BOOT COMPLETED" broadcast to startservice "com.winca.service/.StartService". Try emulating the broadcast by using the "am broadcast -a android.intent.action.BOOT_COMPLETED" in a terminal app or adb shell. That should trigger my APK to trigger the winca service, if it didn't do it while it actually booted it is possible it is executing it too early. Though it sounds strange. It is probably a bug in my APK that I couldn't duplicate in the Android Virtual Device.

In any case, I will need the files from the following outputs to troubleshoot it:

$ [B][COLOR="RoyalBlue"]su[/COLOR][/B]
# [B][COLOR="RoyalBlue"]reboot[/COLOR][/B]
[COLOR="Gray"](wait for system to restart and boot process to quiesce completely)[/COLOR]
$ [COLOR="RoyalBlue"][B]su[/B][/COLOR]
# [COLOR="RoyalBlue"][B]logcat -df /mnt/sdcard/reboot-logcat.txt[/B][/COLOR]

$ [B][COLOR="RoyalBlue"]su[/COLOR][/B]
# [B][COLOR="RoyalBlue"]logcat -c; sleep 1; am broadcast -a android.intent.action.BOOT_COMPLETED; sleep 5; logcat -df /mnt/sdcard/bootcomp-logcat.txt[/B][/COLOR]
[COLOR="Gray"](Sorry, I know its a long line)[/COLOR]
[Android Head-Units] badboy007:
Great Work Man!!!!
[Android Head-Units] royalhawk2002:
This means that we must first update our units to the 4.03 beta FW and then install your "System Update"? :D
[Android Head-Units] DenisMS79:
Very good, looking forward to the update.
[Android Head-Units] KoTiX2:
Well I can release it in both way, a full upgrade to 4.03 fw with mcu flash included and just an update of the "system" folder for the already 4.03 users. Btw I'm thinking to learn how to use the aroma installer so you can choice what to flash what not.

@Donald I'll check better the buttons behaviour and report back.

In the Wincaservice.apk manifest, at the end there is:

<receiver android:name="com.winca.service.PackagesMonitor">
<intent-filter>
<action android:name="android.intent.action.PACKAGE_ADDED" />
<action android:name="android.intent.action.PACKAGE_REMOVED" />
<action android:name="android.intent.action.PACKAGE_CHANGED" />
<data android:scheme="package" />
</intent-filter>
</receiver>
<receiver android:name=".BootReceiver">
<intent-filter>
<action android:name="android.intent.action.BOOT_COMPLETED" />
</intent-filter>
</receiver>

and i can tell you that some time the service start after adding a new app, meaning that the PackagesMonitor receiver work (not sure if it works with every new app or just new launchers) but I've never seen the service running at startup.

I'll try all those commands in terminal and report back all the logs and results. (I'll probably connect an usb keyboard for it :cool: )
[Android Head-Units] donaldta:
Yes, the "android.intent.action.*" means that it is a Android OS intent not one specific to any launcher. However, I should point out that just because you see the AndroidManifest.xml file has permission and receiver for "android.intent.action.BOOT_COMPLETED" that only means there is sub-routine that triggers off of the broadcast. However, that does not mean it loads the specific ".StartService" class that we want. You'd have to debug the .BootReceiver class to identify exactly what it does when it receives the broadcast.

Like I conveyed before, I know that it starts up but not really sure what it does. Based on your feedback so far It sounds like it is closing itself after acting on the Boot Complete broadcast and not doing much else.

Here is a copy of a standard Generic.kl along with s3c_ts.kl and Vendor_dead_Product_beef.kl files which have the custom keys. Please test one or other. It should return the keys back to the stock orientation. The only difference is that we're splitting it off from the Generic.kl file. I'm not sure if both will work but at least one will work. If they both work then you'd only one to keep one or the other.

Once you've got one working and responds properly then please go through the list of all possible functions and remap them with your SWC buttons. You'll need to verify which functions actually reports a scancode in the KeyTest app and write it down. Also make a note of any scancodes that are missing from the custom file or any keys that do not work as it should.
[Android Head-Units] nbbankov:
My unit has a canbus decoder, which I guess decodes and triggers the brake switch to the unit and wires are not individually labelled. And just to re-confirm, when I find the wire, it needs to be ground, not 12v?
[Android Head-Units] KoTiX2:
I didn't have much time today, btw the command "am broadcast -a android.intent.action.BOOT_COMPLETED" didn't launch the service

Here is the first reboot-logcat.txt:

https://www.dropbox.com/s/qouzr8ho9cod4bc/reboot-logcat.txt

I need a keyboard for the other one :(

I couldn't test your new keylayouts because i had only esExplorer and even activating the rootexplorer option it did not let me write in the keylayout folder (permission denied), maybe i need the real rootexplorer app for that? I'll zip 2 roms with the 2 different kl files to test them .

Anyway i tested more the modded generic.kl: the phone button does the next function in poweramp and does the phone function too, the menu button does only the prev function in poweramp but maybe because there is no a "menu" function in the winca controls, i bet that if i set that button to another function like "Radio" it will have a double function too (radio+prev).
[Android Head-Units] stief:
You can also just disable the handbrake option in the menu. in 4.03 you have to use the engineering menu. In 2.x you'll have to use the hidden menu.
[Android Head-Units] gochapka:
help me!

Dear all , a pleasure to be in a place where there is so much wisdom!

I have several problems ... besides not fluent in English ( helped me with Google Translate) and developer but I'm not an electrical engineer and have knowledge of electronics and programming VBA so true modus operandi of the medium know ... with my device 2 DIN Chinese Car DVD , Android OS , and in the thread http://xdaforums.com/showthread.php?t=2618732 something I said and do not merit here.

From what I read and I understand I can just make this post as my unit goes to WinC6.0 ? that's my intention and that Android OS is very erratic and has a very poor user interface.

But reading this thread , who kindly recommended me " donaldta " , it is possible that the drive to pass S100 S150 ? Achieving perhaps best operation and performance ?

I have the firmware files in the device OS versions of Android OS as WinC , I can prove smoothly inserted into the SD slot DVD WinC try to operate in ?

I have many more questions and others will appear , I hope to attend as I am very disappointed with this device as well not bother much about my ignorance and possible misunderstandings on these issues.

Regarding post it on this thread is because I have files that are almost identical to those shown here .

Best regards . Gustavo .
[Android Head-Units] stief:
Hi Gustavo,

Seems like you have the S150.

At this moment we're not able to flash WinCe on the S150.

I suggest you try the latest 2.3 firmware or better the latest build KoTiX will publish soon.
[Android Head-Units] mihaiolimpiu:
[MENTION=2734955]KoTiX2[/MENTION]: If you have root and want to modify files on System you have to MOUNT it first as R/W in EsFile Explorer. It's mounted by default as read only.
[Android Head-Units] KoTiX2:
[MENTION=1991847]mihaiolimpiu[/MENTION] Tnx I got it, now :P

I zipped this Update so you guys can have root acces and maybe you can help a little fixing the problems with this beta fw.

There is nothing new except root addition and gps fix of course.

It will update just the system partition, no bootloaders, kernel, recovery, mcu etc will be flashed so it's intended to be used only by an people with already flashed 4.03 fw.

It can be flashed throught the "SystemUpgrade" function in the setting menu like a standard fw from the SD slot (not the GPS one), YOU will tell me if it's needed to be copied in the root of the SD, in a "winca" folder or in both.

Later on today I'll probably build a full rom too.

[MENTION=5389783]donaldta[/MENTION], I tryed yours keylayout but they didn't worked, with mcu-keylayout.kl the home button on the unit stopped working, with vendor_0000 everything worked in the same way as original file.

EDIT:Here is the second logcat for BOOT_COMPLETED: https://www.dropbox.com/s/vw3ggs29w57rnph/bootCOMPLETE-logcat.txt

I'm sorry i have really a little time to spend on the car lately, if i had the unit on my desk would be alot of easyer. :(
[Android Head-Units] stief:
:good: Thank you.... Thank you ......Thank you!!! :good:

Fasted flash I ever did.

If using the sytemUpgrade, you only have to create a Winca folder en put the file in it.

Also tried the root of the SD just to be sure but that didn't work.

Didn't have time to test further but guess I'm rooted!! :cool:

Will look in to getting write access on sd card in GPS slot and USB later this week.
[Android Head-Units] KoTiX2:
Maybe just run SuperSU one time and it will ask you to update the SU binary
[Android Head-Units] Gassi2106:
Is the playstore in this update include?

Gesendet von meinem HUAWEI U9508 mit Tapatalk
[Android Head-Units] DenisMS79:
Thank you. Tomorrow I'll try to update.
[Android Head-Units] gochapka:
Oh yes! S150!!!

Indeed ! , After publishing my post I dedicated myself to read them ( unfortunately by anxiety and discomfort misoperation did backwards) of this thread (so far I got to # 355) and I have noticed that it is S150 is what I suspected and now have confirmed me , thanks stief !

I do not want to distort the thread with my various problems but since we do not know if anyone else has the special DVR front camera for S100- S150 units installed , in addition to recording or operates in a very irregular way , we may have been raised here and I did not realize that I have something annoying is that the DVR function still operational but one has the equipment operating and visualizing the Radio ( for example) and want to go to see the camera DVR Radio turns off must increasingly put back in operation, you can change that?

My unit has the 2.3.4 , truly awful both the GUI and its stability is very erratic (do not know if maybe the hardware is not the problem ) .

I still keep this interesting thread .

Thanks and regards .
[Android Head-Units] donaldta:
Excellent. We'll work on the vendor_0000_product_0000.kl file from now on. I think the other file is only valid on older versions of Android but I am not sure where the cutoff is, I do know the vendor/product files are not recognized in 2.3 though whereas the "named" file is.

Hmm, seems to be contextually similar to standard reboot that you posted earlier. Darn it. I'm going to probably have to bring this up on stackoverflow. In the Android Virtual Device that I'm testing it on and developing against, it at least shows up in the logcat messages.

# [COLOR="RoyalBlue"][B]logcat -c; sleep 1; am broadcast -a android.intent.action.BOOT_COMPLETED; sleep 20; logcat -d | grep winca[/B][/COLOR]
Broadcasting: Intent { act=android.intent.action.BOOT_COMPLETED }
Broadcast completed: result=0
W/ActivityManager( 80): Unable to start service Intent { cmp=[COLOR="Red"]com.winca.service/.StartService[/COLOR] }: not found
#

Don't worry about the "not found" message. That just means I don't have the actual com.winca.service package installed, so its service is not registered. I cannot install the package either because the SharedUserID is System and signed with a different keystore than that on the AVD. Gimme a few days, I'll come up with something.

No worries. I don't even have this unit. I'm helping

you

and those others that do too, so its no sweat off my back if there are delays on feedback. As they say, I help those whom help themselves. The sooner that anyone can verify the all the possible SWC functions which registers a scancode in the keytest app, the quicker I can spit out files to test. At least, we now have the standard generic.kl and a custom keylayout file in place. Stuff like that just burns at my OCD.
[Android Head-Units] KoTiX2:
Ok, This is the full ROM with MCU flash and everything:

https://dl.dropboxusercontent.com/u/87479392/KoTiX_GPS_rooted_deodexed_FULL4.03.rar

This is just the system update for already 4.03 users that I posted before (just to keep them togheter):

https://www.dropbox.com/s/4214u7lmpunstms/update_S150A.zip
[Android Head-Units] donaldta:
Actually in retrospect, are you sure that the standard Google Generic.kl file is in place and not the stock one from the S150? I ask because the custom files that I uploaded didn't include a reference for "KEYCODE_HOME" in it, as its scancode from the MCU was not referenced anywhere in the thread.
[Android Head-Units] KoTiX2:
Probably i was a bit on hurry when i tryed but i'm sure that the files were replaced correctly, i will check better tomorrow at lunch time what is happening.

Maybe somebody else now can test it too, having root access..... Please?
[Android Head-Units] donaldta:
Cool. You can alway add it manually. Use keytest app to find out the correct scancode and then add, "key {scancode} HOME" in the file using a text editor, like the ES Notepad in their File Explorer.
[Android Head-Units] KoTiX2:
Could the last post on this thread:

http://stackoverflow.com/questions/2784441/trying-to-start-a-service-on-boot-on-android

be the cause of the service not starting?

Where he say "Be attention..."
[Android Head-Units] donaldta:
You mean this post?

It is possible but we cannot edit the com.winca.service apk without their keystore to do anything about it. But if you're referring to my APK, I have not registered a service or an activity. It only has a receiver that starts up a service from a different package when it gets the boot complete broadcast. Maybe I should decompile the stock launcher and winca.service apks to figure out what they are doing differently. But, that would take me a couple weeks as I am not at all comfortable with smali or backsmali code for Dalvik.
[Android Head-Units] KoTiX2:
Tnx Donald, don't worry about it, sooner or later a final firmware will come out with most of things fixed. You don't have to spend 2 weeks of your time trying to fix a beta fw for a unit you don't even own.

P.S. i received this morning an e-mail from a winca developer... He answered to an e-mail i sent him last year during this period, telling me that they are closed till february 6th forma chinese newyear.

....better than never. :p
[Android Head-Units] donaldta:
Well, technically, that's not two weeks of my time but a guesstimate of how long it would take me based on my free time and comfort level with Dalvik code. And that's not even fixing the beta fw, that's just understanding what two packages are doing differently than a third-party launcher.

I'll still pursue trying to get my package to load the com.winca.service.StartService service and work with you getting the SWCs working the "standard" Android way instead of how they implemented in this beta. If this is how they started, who knows what they might fsck up in the released version. At least by the time it is officially released you have gained some files and knowledge on how to fix it.
[Android Head-Units] donaldta:
Posted the question on StackOverflow, "Cannot start an external service from a boot_complete receiver".
[Android Head-Units] ildiko2:
Status bar (Back / Home / Menu) not klickable after reboot

Dear Pro's ! I have read all the posts in this thread - but didn't find an answer to my problem.

I tested all of 2.3.4-firmwares in this thread with my S150 i008 (SantaFe) and I have allways the same strange problem:

When i do "touch screen calibration" everything works fine, i can click on all areas on the screen including Status Bar (Back / home / Menu)

After restart the status bar items are hardly not accesible (only very small line of tochscreen on the top reacts), But e.g. buttons of keyboard are calibrated perfectly.

When i do fresh calibration, the status bar works fine again until next reboot.

Doeas anyone of you have the same problem or maybe solution???

thank you for your hints.
[Android Head-Units] donaldta:
In retrospect to the answers given on Stackoverflow, can you please try pushing my APK into the /system/app directory, making sure the permissions is as followed "-rw-r--r--" which is "chmod 644 {filename}" and then reboot it? If it still doesn't work that way, I'll need the two outputs as specified in Post #546.

Also, "dumpsys package com.winca.service.start > /mnt/sdcard/winca-dumpsys.txt"