FORUMS

CUSPTECH Android Headunit

58 posts
Thanks Meter: 1
 
By ryrager, Member on 4th February 2014, 08:18 PM
Post Reply Subscribe to Thread Email Thread
22nd June 2015, 11:56 PM |#181  
itsme1976's Avatar
Junior Member
Thanks Meter: 0
 
More
Thanks so much for the ROM's MrNisse

Which of the rom; s should I use for best results such as bluetooth, OBDII and USB.
Hope you can help me.
Read in the forum that you should beter be use the 2013 version because of
Bluetooth, OBDII and USB???
I am now on the August version 2013 it's worthless
 
 
29th June 2015, 03:33 PM |#182  
Junior Member
Thanks Meter: 0
 
More
I have a problem with the touch screen digitizer, anyone knows where i can buy this part?.
Model car dvd player: CP-K006, 8 inch multitouch.
For Kia Sportage

I apreciate your support.

BR
Carlos

Enviado desde mi SM-P900 mediante Tapatalk
6th November 2015, 11:28 AM |#183  
Junior Member
Thanks Meter: 0
 
More
Hi
I have asked this before, but have never got an answer on the issue.

What do I need (hardware, settings............) to connect a Bluetooth OBDII reader to my CUSP Android radio running Android 4.4.2. (English version from 24-03-2015).
It worked fine when I was running Android 2.3.4, but I can't get the Bluetooth (USB) setting in Android to work (when I activate it it returns to OFF after a few seconds).
I use a little "no name" USB bluetooth dongle that CUSP sold me together with the radio.
Hope someone can help me with my problem, so I can use the Torque program on my car radio again.

Many regards
MrNisse
4th February 2016, 01:11 AM |#184  
Junior Member
Thanks Meter: 0
 
More
Hello,

New to the group. Got this unit a few months ago and since day 1 the audio (from any source) cuts in and out at random. There's no pattern, ad I have no idea how to fix it, apparently cusp support neither.

The About screen in Settings says I have MCU Sept 14 2015. Android 4.4.4

Any ideas?
4th February 2016, 02:19 AM |#185  
Member
Thanks Meter: 5
 
More
Hmm. There could be many reasons for this.
The cusp devices are not very beefy in terms of hardware performance. So check if you have a cpu intensive app that is running in the background.
Did you check the contact between the harness of your car and the adapter? Maybe there is a bad contact?
Are you using the speaker out or the line out of the device?
If you are using the speaker out, you are using the integrated amp (tda xxxx), that one could be faulty or not well soldered.
So to verify this, try using the line out of the device with any device that can accept line level input (external mini amp, or maybe a recording device).
Do you have the problem only while driving, or even when the vehicle is parking?

I don't have your mcu version nor 4.4.4, so may be they updated some parts and did not test it very well. I remember at some 4.4.2 version of Android where cusp put a faulty asound.conf file in the vendor folder. Try moving that file to another folder restart the device and check the sound.
4th February 2016, 06:06 AM |#186  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by tobias.s

Hmm. There could be many reasons for this.
The cusp devices are not very beefy in terms of hardware performance. So check if you have a cpu intensive app that is running in the background.
Did you check the contact between the harness of your car and the adapter? Maybe there is a bad contact?
Are you using the speaker out or the line out of the device?
If you are using the speaker out, you are using the integrated amp (tda xxxx), that one could be faulty or not well soldered.
So to verify this, try using the line out of the device with any device that can accept line level input (external mini amp, or maybe a recording device).
Do you have the problem only while driving, or even when the vehicle is parking?

I don't have your mcu version nor 4.4.4, so may be they updated some parts and did not test it very well. I remember at some 4.4.2 version of Android where cusp put a faulty asound.conf file in the vendor folder. Try moving that file to another folder restart the device and check the sound.

Tobias.s thanks for your response,

There are no tasks running in the background that could make the CPU have some hick ups. The harness looks alright and the audio cutting off happens with the vehicle moving and/or parked.

I opened the unit and took everything apart and it all looked well soldered and tidy.

This unit is connected directly thru my stock amplifier and I don't see any line out on the device itself.

Could you elaborate on that faulty file you were referring to?

Thanks.
4th February 2016, 12:23 PM |#187  
Member
Thanks Meter: 5
 
More
Hey,

concerning the file: its name is asound.conf . I don't remember exactly where it was saved. I guess it was /etc/vendor or /etc/vendor/sound . Unfortunately I don't have a cusp device installed anymore in my car to check its exact location. But a folder names vendor was involved. Check with a root explorer the exact location and then just move the file into a backup folder of your own, so that the file does not exist anymore in the vendor folder or subfolder. This way, android takes a default audio configuration instead of the faulty config edited by cusp. This is also a solution to install 3rd party equilizers like ViPER4Android on that device. With the bad file installed, Viper cannot be activated on these devices.

Quote:

This unit is connected directly thru my stock amplifier and I don't see any line out on the device itself.

Usually these devices are deliverd with an adapter suited for your car harness. If they did not change their pcb, you have on the back of the device a black 18pin connector with an installed fuse and a second narrow white connector in the middle . (check my uploaded picture)
I don't know exactly how your device is connected to your stock amplifier(with stock amp you mean the one that came oem with the car, right?).
May be you can check this: if your sound wires use the black connector (this way each speaker has its own 2 wires), then you are using the integrated amp from cusp. In this case, you usually need a high low adapter to send an adapted audio signal to your stock amp unless your amp can receive high audio signals. Additional infos could help here, what type of amp, car aso...
The other white narrow connector, connects to an adapter with many RCA Cinch connectors. Among these connectors you get 2 rca conectors for Line level out for the right and the left signal and a separate one for a subwoofer.

The reason why you should test these line outs is to narrow down the problem. If the integrated Amp is faulty, the sound on the line outs should be ok because they don't go thourgh the amp circuit.
If the sound is also bad on the line out then you got a deeper problem on the codec or audio switching circuit.

Uploaded picture:
1=Adapter with line in and out for audio and video.
2=Front left and front right rca line outs
3=Black connector for onboard amplified sound out, directly to speakers.
4=Car dependent harness
Attached Thumbnails
Click image for larger version

Name:	DSC_0035.jpg
Views:	20
Size:	89.3 KB
ID:	3633626  
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes