yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] jakejm79:
Just thought I would chime in about my new unit, got the capacitive screen version from our_style and flashed Hal9Ks latest firmware (left the MCU alone) and installed an external mic. Everything works great, got USB OBDII working and several other root apps. Also the external mic seems to have solved my voice search problems with the car running, now I can just press a button my steering wheel, say navigate to XXX and I have instant turn by turn directions without my hands every leaving the wheel.
[Android Head-Units] sciallo:
:good:

Awesome to hear. Good to know leaving the MCU alone does it.... DON'T TOUCH IT!

Hopefully there will be a new MCU available for peace of mind soon.
[Android Head-Units] daveaus:
Hi all, I am using an Australian nav app called Metroview. I have got tasker to start it 30 seconds after booting which works great. The only problem is just as it finishes loading I get the force close / wait / report prompt. By the time the message comes up its working fine in the background so I just hit wait and Im straight in, is there a way to stop this message?
[Android Head-Units] Shaharov:
Ok... Loaded the rom from hal9k... Works great... How do I reload sygic with the license key that came with the unit?
[Android Head-Units] Shaharov:
Ok... Got the new mcu from the manufacturer... Heres what they wrote......

So..... DO NOT DOWN GRADE YOUR MCU FROM 2.11 TO 2.10 AS IT WILL BREAK

However... If you do re-upgrade it with this... Should work... Will test in the morning
[Android Head-Units] jakejm79:
Is this the same 2.11 that comes on the newer units or is it a later version than what they came shipped with?
[Android Head-Units] sciallo:
Glad you got it, I wish my seller could have gotten that before I sent mine back :(

Oh well, shopping for my next one...

Does anyone have this version? do we know if it's the same with just a different face? Hal9k roms still apply?

I think I would like it better. Built in input, full size sd card (cheaper cards, more flexibility: read micro or mini with adapter), my car interior lighting is green and the rest of the buttons only work for built in apps anyway...

Drawback: no button left to remap for screen dimming, I plan on automating dimming and more with IOIO anyway.

http://www.aliexpress.com/item/New-...versal-2Din-with-Radio-GPS-3G/1028670207.html
[Android Head-Units] jakejm79:
Check the thread of at ft86club.com, I believe that unit is mentioned over there, it is technically a different model number than the Ouku, but shares much of the same guts and I believe there is a way to adapt Hal9K's roms for it.
[Android Head-Units] SWEUP:
I'm using an earlier Hal9k_ rom but thinking to upgrade to his latest 31.07.2013. Anyone using this one? Happy with it?

My biggest problem is that native app "takes over" audio from other Google Play apps, is this solved in the newest Hal9k_ rom?
[Android Head-Units] Shaharov:
I think it is... but not sure. It's meant for the newer versions, but I downgraded and can't rememeber the exact number except it was 2.11.4-xxx
[Android Head-Units] sciallo:
Mine was 2.11.4-1-10-0101 just like the one linked here ...before I downgraded it a month ago.

So, did re-upgrading fix the sound?
[Android Head-Units] Shaharov:
I'm using it.. I found its working quite well but not sure about the taking over part (at least I havent noticed). If you have a newer unit, just dont upgrade the MCU as the one included is 2.10.9 and will cause the sound system to fail.

---------- Post added at 11:22 PM ---------- Previous post was at 11:14 PM ----------

yep... worked perfectly
[Android Head-Units] jakejm79:
Yes it is the same MCU the newer units ship with so no upgrade unless you downgraded first.

There is a setting in the sound menu for 3rd party apps to 'unsurp' the sound or something similar, basically with it checked, whenever an android app plays a sound (be it a notification, game, movie, music, etc) it will kill the audio stream from the other components (radio, ipod, disc, aux, etc) nice thing about this is that if you start winamp for example you don't have to kill the radio app first, but if you'd like to play a game while listening to the radio then you have to uncheck it and the two audio streams will be mixed together. The nominated nav and phone app are always mixed regardless of this setting, there is a nav volume setting to adjust the amount of mix.
[Android Head-Units] SWEUP:
Thanks, I see that my current MCU is 2.10.8 and Hal9k_ rom 31.07.2013 is using MCU 2.10.9.

Do you mean I should not use MCU 2.10.9? Can i upgrade my unit to 31.07.2013 without update the MCU?
[Android Head-Units] sciallo:
It will work fine either way, you can upgrade without upgrading the mcu or IN YOUR CASE you can also update the MCU (to 2.10.9). AFAIK only units shipped with MCU 2.11.4 will loose sound if changed.

I don't think anyone has tried updating MCU from a lower version to this newer one, but I assume it would give the same result: loss of sound.

It's not a big risk (anymore) as we now have MCUs to revert to...
[Android Head-Units] SWEUP:
Thanks, will try to update them both.

EDIT: the update went well. Unfortunately the audio take over from the native apps are still there, eg: when native music is playing and I start Google music both audio are playing simultanious.

Found one issue, when launching Youtube app, i got information that I need to download Google Play Services, but when doing so I got issue message "other user id in service". Any idea how to solve this?
[Android Head-Units] jakejm79:
Have you tried check the usurp 3rd party apps box in the sound settings menu?
[Android Head-Units] donaldta:
This is most likely due to a Shared User ID conflict in signatures with another Google Package. I had the similar problem on another device after trying to re-install Google Service Framework (com.google.android.gsf) after a firmware update because Google Play Services (com.google.android.gms) had remained after the upgrade and had a different list of signatures that it would accept. In my case, I had to uninstall GMS in order to install GSF then I was able to reinstall GSF.

If you have root access, then you can use "dumpsys package > /mnt/sdcard/output.txt" to ascertain the information. You'll be looking for any Google packages that use a Shared User ID. If you don't have root access then perhaps using an earlier version, like Youtube_2.5.16.apk will be better suited for you because it was released before Google Play Services.
[Android Head-Units] jakejm79:
Does anyone have any input on unpacking and packing the system.img? I would like to add a couple of files to Hal9K's most recent version (or the most recent version I have) so the cheaper USB OBDII dongles would be supported out of the box, rather than having to modify things later. Is there any signature process involved or is it just simply repacking them? Do I need to worry about setting permissions for the added files or are they set per folder so they should match the other files?
[Android Head-Units] abbgc123:
S150_I802

Hello,

I hope you can help. I purchased S150_802 unit just a week ago. I'm experiencing exactly what you had and I did exactly what you did, were you lucky to solve it. Please let me if you did.
[Android Head-Units] sciallo:
There is now a separate thread on the S150_802:

http://xdaforums.com/showthread.php?t=2503964&page=18

Hopefully they can help you there...
[Android Head-Units] abbgc123:
Hi,

Do you have by any chance the S150_C001 for the universal unit I802, the latest if poosible please.
[Android Head-Units] SWEUP:
Thanks, it's checked. I tried to de-select and later select it again but no luck. Can you switch from native music app and just start another music app without both playing simultaneous? I think someone earlier in this thread said that "Tasker" might be a way to go, will try this.

Thanks, I looked for com.google.android.gsf and com.google.android.gsm in "Applications" (settings) but couldnt find them. I have to read how to use dumpsys and see if this could help. Strange issue
[Android Head-Units] donaldta:
They're not going to appear in the app drawer since they are installed as system services. If you are looking for them in the Settings application under Managing Applications, they are not going to appear in their package name. Google Services Framework is the application name of "com.google.android.gsf" package and Google Play Services is the application name of the "com.google.android.gsm" package

You can use "dumpsys" from either an "adb shell" or terminal software on your Android device.
[Android Head-Units] chris.r.r:
Has anyone ever tried to mod the apks in Hal9ks image? I decompiled them and browsed through the resources - I'm pretty sure that we could give the apps a much better and cleaner look by only modifing the resources. Does that work or is there a reason why it shouldn't? Signing, checksum, etc?
[Android Head-Units] sciallo:
someone at http://www.ft86club.com/forums/showthread.php?p=1107961#post1107961 did just that, he made a modified hal9k with the main difference being a different color scheme on the stock apks (mainly changed from blue to red) so I don't think that should be a problem. If I remember right the bluetooth app wasn't working after mods, so in the newest version he reversed the changes to that apk, not sure if he figured out what's up with that one.
[Android Head-Units] Shaharov:
Im running the newest hal9k image and have 2 questions:

1) is it possible to change what apps are aon the dock at the bottom of the screen. some are redundant to buttons and some (ipod) I would never use. It would be nice to change these yo common applications

2) is anyone using a usb bluetooth dongle. Ive tried a couple but none were recognized. If so what model or chipset are you using? Id like to get my odb module working
[Android Head-Units] donaldta:
Have you considered using a USB ODB2 cable? They're often less expensive and have a much quicker response time. The only caveat is whether or not the USB to Serial drivers a part of the system rom.

You can have a better idea of what you can use on your Android device if you use "lsmod" from a Terminal App, like Android Terminal Emulator or using "adb shell" from a computer with the Android Developer Tools installed.
[Android Head-Units] sciallo:
I plan on using ADB launcher, you can replace the launcher with a number of available ones https://play.google.com/store/apps/details?id=org.adw.launcher&hl=en

I was lucky enough that one of the bluetooth dongles I had laying around worked. Search this thread for it, there have been plenty of links to working dongles in the past. One thing to keep in mind, you should try to boot the radio with the dongle already plugged in, it's been reported that they are not hot-swappable. Also you will need to install something like https://play.google.com/store/apps/details?id=com.bluetooth.Lite&hl=en to manage it as there is no bluetooth section in the settings.
[Android Head-Units] Shaharov:
Thanks... Completely forgot about changing the launcher (its been years since I last used ADB). So far Ive tried 2 dongles with no luck (but in a terminal the bluetooth drivers are there)
[Android Head-Units] donaldta:
.

Would you be able to provide the output of "lsmod" with one of your USB BT connected after a reboot and not connected after a reboot? It'll be interesting to see if it is actually being recognized. Also, remember it has to be reboot because from the feedback of other users, it sounds like they didn't enable Linux hotplug on this unit. So, it will need to be present while it boots to appropriately link the module to the device..

Btw, did you install an app like Quick Bluetooth Lite, since it seems whomever put together this ROM has hidden the access to the Bluetooth settings at least directly from the Settings app.
[Android Head-Units] jakejm79:
So I spent a couple of hours on tweaking some of Hal9k's firmware, its the version from 6/14/2013 system version 2.20.21, since that was the most recent version I had available.

Anyway it is basically the same but with these two additions:

1. Built in fix for downloading large apps from the Play Store.

2. Support for USB OBDII dongles that use the cp210x.ko module like this one: http://www.ebay.com/itm/ELM327-OBDI...t=Motors_Automotive_Tools&hash=item4d12f3c662

To simplify things I have made 2 packages for the two different touch screens, also the MCU file is not included in the update, since it isn't required and upgrading/downgrading to the wrong one can cause loss of sound.

Resistive Screen - https://www.dropbox.com/s/oicpt71njh3kfwq/Resistive screen.rar

Capacitive Screen - https://www.dropbox.com/s/j6m5rd1t6y5cqmn/Capacitive screen.rar

Credits:

Greenpant over at ft86club.com forum, for the fix to allow large app downloading (in the uramdisk.img) and for this help with linux.

Brady Alleman over at http://brady.thtech.net/ for the USB ODBII fix (code for the module is available on his blog, Brady I found no way to contact you, if you have a problem with me distributing this, please let me know and I will remove it.

Hal9K for the base files and for enabling root.

I have tried this on both a resistive screen unit and a capacitive screen unit with no problems, but use at your own risk, I'm not responsible for any issues.
[Android Head-Units] sciallo:
Well done, Thanks!

About the whole MCU thing...

Careful: I think the issue starts with MCU 2.11.4 or so. There are units that shipped with MCU 2.11.1 that had no problem with the downgrade (so I assume they might have a problem with an upgrade :confused: )

See This Post ...That's one of the things that threw me off making me think the issue was not with the MCU...

Since MCU upgrade and Rom upgrades seem two completely separate and indipendent processes, there is no need for the MCU file to be on the card for a Rom upgrade, and no need for any of the rom files to update MCU.

It may be safer to just get the MCU files out of the updates and have them as stand alone downloads. No real need to upgrade MCU from what came with the unit, especially if it's already the newest or possibly even newer in the future.
[Android Head-Units] jakejm79:
Ok I will make the changes then and just have two downloads, I just didn't want anyone to be running an older MCU that was incompatible with a newer system.img, but I suspect the chances of that happening are slight.

Thanks for the heads up, I didn't realize people had units that had shipped with 2.11.1, I thought the only ones had been the 2.11.4 units that have the problem if you downgrade, one a side note, I wonder if some of the hardware has changed for the MCU/internal amp, I have noticed that my new capacitive unit does appear as loud as my older one.
[Android Head-Units] sciallo:
Something must have changed in the hardware, who knows what...

There might be many more units that originally came with 2.11.1 but we wouldn't know since they downgraded that without an obvious problem (but didn't need to and might have lost some benefit...) I don't think using latest rom on older MCU is really a problem, and that can still be upgraded separately, just not downgraded "by accident" :)
[Android Head-Units] Shaharov:
They Changed the sound module in the radios with the 2.11.4 MCU... if you downgrade they will not work as the MCU isn't compatible with the old hardware. I'm not sure if upgrading the old firmware to 2.11.4 will work either.
[Android Head-Units] Shaharov:
Both with or without usb dongle plugged in when booting I get this... Basically I guess I dont have a dongle that's compatable
[Android Head-Units] donaldta:
Are you sure? There is a difference in the output that between the two lsmod commands, I am assuming that you had a usb bluetooth adapter connected then disconnected between the execution of the two commands.

Here is an explanation of the output.

The first column contains the name of the module.

The second column refers to the memory size of the module, in bytes.

The third column lists how many instances of the module are currently loaded. A value of zero represents an unloaded module.

The fourth column states if the module depends upon another module to be present in order to function, and lists those other modules.

The fifth column lists what load state the module is in: Live, Loading, or Unloading are the only possible values.

The sixth column lists the current kernel memory offset for the loaded module. This information can be useful for debugging purposes, or for profiling tools such as oprofile.

You have the following modules/drivers present; Realtek RTL

8192CU

(Realtek USB to WiFi),

V

N

T9271

(Via USB to WiFi), Fuse (

F

ilesystem In

U

ser

S

pac

e

), PL203 (

P

ro

L

ific Serial to USB), FTDI_SIO (

F

uture

T

echnologies

D

evices

I

nternational

S

erial

I

nput/

O

utput to USB), BTUSB (

B

lue

T

ooth

USB

Host Controller Interface), RFCOMM (

R

adio

F

requency

Com

munication - Serial to Bluetooth), L2CAP (

L

ogical

L

ink

C

ontrol and

A

daptation

P

rotocol), SCO (

S

ynchronous

C

onnection

O

riented), and BLUETOOTH (Bluetooth Hardware Abstraction Layer).

Between two instances of lsmod, it shows a difference of two btusb and five l2cap modules loaded. Given your output, I'd bet that they are being recognized but the underlying Linux operating system. If you type "dmesg" after installing connecting the Bluetooth USB dongle to display the kernel messages and the last lines should reflect it.
[Android Head-Units] jakejm79:
Can you expand on this at all, my recent model with 2.11.4 MCU seems to have a much lower sound output than my previous model with a 2.10.X MCU, all out put is ran through a 4 channel amp, so maybe just the preamp voltage changed and I need to adjust the gain settings or if I am SOL.
[Android Head-Units] Shaharov:
Never noticed the difference till you pointed out of the btusb loaded. I'll look at the dmsg tomorrow and see what's happening.

---------- Post added at 06:52 AM ---------- Previous post was at 06:45 AM ----------

Actually... I really dont know that much. I'm being a parrot for the email that was sent to me by the manufacture when I asked for the 2.11.4 mcu. Somewhere in this forum is a copy of that email.
[Android Head-Units] jakejm79:
Got the HDPI icons to display permanently with ADW:
[Android Head-Units] sciallo:
Care to elaborate?
[Android Head-Units] Shaharov:
Ive noticed tha tthe icons are smaller (mdpi?). howd u get them to change... I dont have much experiance with adw, besides using it

---------- Post added at 01:05 AM ---------- Previous post was at 12:50 AM ----------

Just read on the 4pdu forum (as best I can). if you upgrade the mcu from an older unit, ie 2.10 to 2.11.4 you will also loose sound. just want to confirm here if anyone has experenced this?
[Android Head-Units] jakejm79:
Basically the exact same fix I did to make newer versions of FB fill the whole screen, see my original post here: http://xdaforums.com/showpost.php?p=46718327&postcount=1811

Basically download xposed installer, install the xposed framework, then install the xposed app settings app and enable it in the installer app (under modules), open the app settings app and find ADW and check the 'X-large res box' save and restart ADW then select the HDPI hack under the advanced settings for ADW.

Make sure you used the versions of the xposed installer and app settings for GB.

Yes [MENTION=3081576]sciallo[/MENTION] had that problem with losing sound, he ended up returning his unit, since he was at the time unable to get a copy of the 2.11.4 MCU to reupgrade and his seller didn't seem to think that was the problem.
[Android Head-Units] sciallo:
Yeap, I still can't get over the waste of time and returm postage...

It does sound like that for what I can make out of google transation, I experienced the problem with DOWNGRADING, I thought someone confirmed the same problem with upgrading from 2.10 to 2.11.4 but can't find it here, it must have been the 4PDA mention I was thinking of...

Restoring MCU to one that works fixes it if you feel like trying :D
[Android Head-Units] Steve_Goral:
Hey guys, seems like a lots happened since I was last here.

Just to save me trawling through all these pages, where is the best place to ge one of these units. I've found a few places but they all seem to be different units, is there a "best" unit? Or are the pretty much all the same?
[Android Head-Units] jakejm79:
Steve what are your goals, there are several pure android units, including some newer 4.1 versions, but if you are looking to root your device then your limited to either the S150 or the Ouku, currently has of right now root is the only way to get OBDII connectivity so if that is of any concern you will want a device that can be rooted.

Ebay is normally the preferred source thought alibaba or aliexpress our also sources.

There is this unit on ebay fully rooted and ready to go with USB OBDII: http://www.ebay.com/itm/231109034198

[/shameless plug]
[Android Head-Units] KID52:
Not true as of this morning :victory:

The new 4.1 unit has been successfully rooted, check out the thread for details.

http://xdaforums.com/showthread.php?p=48167524#post48167524
[Android Head-Units] Steve_Goral:
I was looking at this one, it's got 1GB of RAM so it looks better but is it worth it? Does it really need that much RAM? I was only really going to use it for web browsing and music.

http://www.ebay.co.uk/itm/Capacitiv...JG_Auto_Pieces_Autoradios&hash=item485cbeb7ec
[Android Head-Units] KID52:
Take a look at the thread I mentioned above, there is a video review and various bits of useful information.

If you live in the US then you can get the unit for just $300, for us in the EU the price is a lot more, around $500.

I would have said it is worth it, given that the unit has very capable hardware, and now it has been rooted, I am sure many more things will be developed for it including OBD functionality.

Apps are only going to get more demanding, so why get such outdated hardware and software?
[Android Head-Units] Steve_Goral:
Has anyone done a comparison between this and a purpose built carpc? I'm trying to work out which will be better, at the moment I'm thinking this unit might be a perfect solution. I'll watch the video later and see if I can make up my mind.
[Android Head-Units] jakejm79:
Damn it and I just bought a new capactive Ouku too, oh well USB OBDII is still an unkown on the 4.1 unit, plus I haven't seen many in the same style has the Ouku (which I prefer) only in the S150/180 style.
[Android Head-Units] KID52:
Correct, everything is still very much a work in progress.

I have seen some in the OUKU style, but until someone buys one, we cannot confirm if the hardware/software is the same. The listings state the CPU is still an A8, but a dual core. Whereas the unit we are talking about definitely has an A9.
[Android Head-Units] donaldta:
As far as getting root for the other units, maybe they can test if their unit is vulnerable to the Masterkey exploit using SRT App Scanner. The key to getting root really depended on [MENTION=5554780]bmj67[/MENTION] getting the SettingsProvider.apk to [MENTION=531561]WonderEkin[/MENTION]. Without those two, it seems like obtaining root access would have never happened. It just goes to show you how much can be accomplished in the spirit of cooperation with XDA users.
[Android Head-Units] KID52:
Agreed.

It was lucky that a similar app had been developed by [MENTION=531561]WonderEkin[/MENTION], and then thanks to [MENTION=5554780]bmj67[/MENTION] doing some digging to find an apk running as System.

Many thanks to these guys again.