Ca-Fi Dashlinq4 Android 4.1.1 Car Stereo - WHOA BABY!

[Orisai]

Originally Posted by protpibe

There are only two stereo channels for amp output (Left and Right) plus one subwoofer out. This may complicate things if you are running 4 amplified speakers. I supposed you could always use an RCA splitter to create dual left and rights and balance them with the gain on the amp, but it seems like a work around.

Wrong...

Each stereo sound channel is comprised by a pair of RCA connectors (red and white), and each channel is comprised by two speakers (left and right), so you can have your 4 amplified speakers (front and rear pairs of speakers).

As for the subwoofer, being it a monoaural speaker, you don't need two RCA outputs to run it. You can use a "Y-splitter" or just one of the RCA channels for the subwoofer and set the gain accordingly.

Originally Posted by protpibe

The iPod support sucks. The app is terrible. It doesn't even read playlists off of your iPod. Truth be told, at least a third of the time I need to reboot the head unit just to play the iPod.

Neither Ca-Fi nor Android's fault Apple forces their own retarded proprietary stuff instead of standard, widely used audio and data interfaces such as AUX and USB.

Originally Posted by protpibe

Torque and bluetooth OBDII dongles. It is not always automatic and half the time you'll be going into settings to manually search for the OBDII dongle.

Common issue about bluetooth devices. I'd use a USB OBD-II scanner if I were you. They're way faster and you can leave them plugged with no battery drains like bluetooth scanners.

Originally Posted by protpibe

The Bluetooth mic is built into the front of the head unit. I've been told that this mic is harder to make out than the old pioneer headliner mounted mic. As far as I can tell, there is no mic input on the rear of the deck to allow an external mic to be hooked up.

You can ask them to add an external mic jack on the headunit's back when you buy yout unit.

Originally Posted by protpibe

The audio will mute when you put the car in reverse (if you have a backup camera). I've played with the setting to stop it from muting, but regardless of if it's on or off, it will mute when you put the car in reverse.

Have you upgraded the firmware recently? It might be a software issue.

Originally Posted by protpibe

The Glare is terrible. I have 35% tint all around and if the sun is behind me, I can't see anything on the screen.

I agree on this, but you can use an anti-glare screen protector. Most capacitive screens have this issue too, including those of mobile phones and tablets.

Originally Posted by protpibe

With all that being said, I like the head unit overall but if it didn't let me use Torqu, I probably would switch to something else.

Are you using Ca-Fi's OBD-2 bluetooth scanner, or a generic one from eBay? Torque may not work with chinese generic/clone adapters.

[bwthor]

The last time I got a version with CarHome disabled, I did a check of all the files, and the only one that was changed was factory.prop, and the line ro.carhome.plug=aTFRUfxByEGVtZUFjdGl2fxByEXR5fxByE was removed.

I tried it on this update, and it worked too.

At your own risk...
On the downloaded update, modify the factory.prop file located in update-->images-->manufactorycfg
Remove the line ro.carhome.plug=aTFRUfxByEGVtZUFjdGl2fxByEXR5fxByE
Save and flash.
Worked for me, but YMMV...

Now to get root working. Anyone try Towelroot?

[bwthor]

Originally Posted by protpibe

The audio will mute when you put the car in reverse (if you have a backup camera). I've played with the setting to stop it from muting, but regardless of if it's on or off, it will mute when you put the car in reverse.

There is a setting under Settings-->Sound to set your reversing volume. By default it is set to zero. So there are two spots, the one I just mentioned, then the one to mute if in reverse.

Originally Posted by protpibe

The Glare is terrible. I have 35% tint all around and if the sun is behind me, I can't see anything on the screen.

Are you getting full brightness from the screen? I'm curious if you have your headlight linkage wiring correct? The unit in my opinion the screen is plenty bright, and I don't think I've ever thought the glare was too bad.

[protpibe]

Originally Posted by Orisai

Wrong...

Each stereo sound channel is comprised by a pair of RCA connectors (red and white), and each channel is comprised by two speakers (left and right), so you can have your 4 amplified speakers (front and rear pairs of speakers).

As for the subwoofer, being it a monoaural speaker, you don't need two RCA outputs to run it. You can use a "Y-splitter" or just one of the RCA channels for the subwoofer and set the gain accordingly.



Neither Ca-Fi nor Android's fault Apple forces their own retarded proprietary stuff instead of standard, widely used audio and data interfaces such as AUX and USB.



Common issue about bluetooth devices. I'd use a USB OBD-II scanner if I were you. They're way faster and you can leave them plugged with no battery drains like bluetooth scanners.



You can ask them to add an external mic jack on the headunit's back when you buy yout unit.



Have you upgraded the firmware recently? It might be a software issue.



I agree on this, but you can use an anti-glare screen protector. Most capacitive screens have this issue too, including those of mobile phones and tablets.




Are you using Ca-Fi's OBD-2 bluetooth scanner, or a generic one from eBay? Torque may not work with chinese generic/clone adapters.

You sure about that?



There's a left and right audio output. Am I missing something because I read your reply as there are a front l/r and a rear l/r set of outputs. Also, I'm aware that a subwoofer is a mono channel

I've tried both the CaFi dongle and the elm dongle. Both will randomly not show up as connected. I don't drive around with Torque on my screen so it's not the end of the world, it's more nitpicking than anything.

I installed the latest firmware tonight so we'll see if any of the other niggles work themselves out.

@bwthor I didn't realize there was a second setting. Thanks for pointing it out

[BlkR]

so noone has had problem with bluetooth streaming to one speaker only ?

[Foobar]

Originally Posted by BlkR

so noone has had problem with bluetooth streaming to one speaker only ?

No problem here.

Sent from my Nexus 5 using Tapatalk

[SilverlightPony]

Originally Posted by Orisai

Wrong...

Each stereo sound channel is comprised by a pair of RCA connectors (red and white), and each channel is comprised by two speakers (left and right), so you can have your 4 amplified speakers (front and rear pairs of speakers).

Incorrect. One channel = one single RCA connector (red for right, white for left). The Dashlinq4 has only one set of stereo line-out jacks, and a mono subwoofer output, as shown in Protpibe's post.

[DC2R]

I wiped stereo and Wi-Fi still won't come on. Guess I'll Fla flash update and see what happens

Sent from my SM-N900T using Tapatalk

[DC2R]

Flashed newest update and Wi-Fi is back.
Removed CarHome line from prop file and replaced partition file with one posted here.Going to flash now and if all goes well work on root

Sent from my SM-N900T using Tapatalk

[DC2R]

No luck with root. Tried old method. Tried installing other version of root my anu.(wouldn't install apk). Tried towel root with no luck....

Sent from my SM-N900T using Tapatalk

[SilverlightPony]

Someone remind me, how long does it usually take to flash an update? And how long should it sit there saying "Target device is <somethingsomething>" before visibly doing something else?

[DC2R]

Originally Posted by SilverlightPony

Someone remind me, how long does it usually take to flash an update? And how long should it sit there saying "Target device is <somethingsomething>" before visibly doing something else?

should only take about two minutes. trust me i just flashed 4 times.

[protpibe]

Originally Posted by SilverlightPony

Someone remind me, how long does it usually take to flash an update? And how long should it sit there saying "Target device is <somethingsomething>" before visibly doing something else?

I had the same problem. You need to make sure the update folder Is the only file on the sd card, otherwise it just sits there and says target device

[SilverlightPony]

Originally Posted by protpibe

I had the same problem. You need to make sure the update folder Is the only file on the sd card, otherwise it just sits there and says target device

Actually, it was a bad SD card. I swapped it with another one with the same contents (system "Update" folder and the MCU update file) and it started moving immediately.