Chinese Ca-Fi knockoff has been rooted! Torque works!

[sciallo]

Originally Posted by nzer

Weird. Are you saying you get no sound from the stock music app and navi?

@GreenPants do you have any ideas as I haven't had this happen to me so can't see it being a root file issue given most of us have not had this occur.

I get no sound from anything but button keypresses (If set to beep). The live vu-meter wallpaper shows music playing too...

This is driving me insane, I think something told the amp portion of the unit to route the sound elsewhere or mute it, and nothing told it to turn it back. What's been driving me crazier is that NOTHING seems to reset the firmwares settings. A bunch of settings like tv mode, radio region etc.... For example, I renamed my phone's BT "expy BT" and nothing I do changes that. Reflash, restore to default, Diconnect all power overnight, reset...

"Expy BT" is still there, and so are many other settings, so I wonder if a "stay quiet" internal invisible magic setting is there too.

Someone On the xda forums with a unit that originally had a 2.11.** firmware reported he downgraded with the Hal9k and he doesn't have any problem so It must be something else. The supplier sent me a link to an old MCU, so that was worthless... I'm still trying to get the right MCU from them, but I suspect the problem is elsewhere...

Been trying to install and uninstall apps like winamp to see if I can get one to "unmute" the audio. I also tried to connect to external BT speaker through my BT dongle, still no sound even out of the external speaker... I'm reaching the baking point and about to pull the plug and return the thing...

[nzer]

Originally Posted by sciallo

I get no sound from anything but button keypresses (If set to beep). The live vu-meter wallpaper shows music playing too...

This is driving me insane, I think something told the amp portion of the unit to route the sound elsewhere or mute it, and nothing told it to turn it back. What's been driving me crazier is that NOTHING seems to reset the firmwares settings. A bunch of settings like tv mode, radio region etc.... For example, I renamed my phone's BT "expy BT" and nothing I do changes that. Reflash, restore to default, Diconnect all power overnight, reset...

"Expy BT" is still there, and so are many other settings, so I wonder if a "stay quiet" internal invisible magic setting is there too.

Someone On the xda forums with a unit that originally had a 2.11.** firmware reported he downgraded with the Hal9k and he doesn't have any problem so It must be something else. The supplier sent me a link to an old MCU, so that was worthless... I'm still trying to get the right MCU from them, but I suspect the problem is elsewhere...

Been trying to install and uninstall apps like winamp to see if I can get one to "unmute" the audio. I also tried to connect to external BT speaker through my BT dongle, still no sound even out of the external speaker... I'm reaching the baking point and about to pull the plug and return the thing...

I suspect it is a problem with your unit. Was it working fine before rooting it?

Return it and get another I reckon. Hopefully they will accept it back rooted as they should be able to reset it.

[onlykillzz]

ok so i have read all 55 pages now.. man that was a long read

i have also noticed there are some other units on the market that are offering 1gb ram think this would still work with the hacked rom

link:
http://www.ebay.com/itm/190901883660...84.m1423.l2649

also this one says its also has windows CE but its the right sharp / model
http://www.ebay.com/itm/190892858003...84.m1423.l2649

not sure if its the right one?

any help would be good

and one last thing has anyone played around with the steering wheel controls ?

[GreenPants]

Originally Posted by nzer

Weird. Are you saying you get no sound from the stock music app and navi?

@GreenPants do you have any ideas as I haven't had this happen to me so can't see it being a root file issue given most of us have not had this occur.

Sorry, can't be too much help here. I'm mostly guessing at what happens under the hood. I don't think that any generic Android apps would affect this muting issue - the only ones that are likely to change things are the stock apps: Phone, Radio, Video, TV, DVD, Navi, Music. Try playing audio using each stock app, including TV & DVD/CD.

[GreenPants]

For all you folks wanting to get standard Android app audio to work properly, it looks like there is a 'The 3rd party application priority' tickbox in Settings->Sounds that you could try selecting. All of a sudden the sound on Angry Birds started working correctly without having to run Video or anything beforehand.

I've played with my system and turned the key beep on - that sounds like a hardware beep that is probably completely independent of the audio routing.

I also assigned the mute function to one of the keys and it seemed to work as you'd expect. Mute/unmute worked, as well as using the volume knob to unmute.

@sciallo:
Is it possible that there is a hardware/cabling reason for the muting behaviour? I can't think of all the lines out the back of the unit off the top of my head, but could any of those being shorted result in volume muting? (There is a Sounds setting for muting the volume during reversing, for example - if the unit always thought you were in reverse, then that could explain things)

I know that you mentioned 'factory wipes' - are you referring to the Factory Reset option in the menu?

When I get some time, I might sit down and record every configuration in the settings menu - it might help to play spot-the-difference.

[GreenPants]

Copy of the T7019 settings menu structure (plus my settings) attached.

[Brody602]

@GreenPants Hey you got mentioned a few times so you probably missed the post tuat Nzer mentioned you for me. I found a new unit on tradesolytion with orange/amber led's that is a toyota fit, running android 4.0. And i was wondering if you can help out with a root at all. Or if you know anything about one. This unit is the T6229A . I've made serveral posts with questions on page 54, and here is the post you were mentioned in.

http://www.ft86club.com/forums/showp...postcount=1183

Thanks in advance for all your help

[GreenPants]

Sorry Brody602, but my part of the equation didn't deal with the actual rooting of the device. I just took an Android image where someone else already did the hard lifting and tweaked it a bit.

I think your best bet would be to study the resources over on xda-developers to see if there are any generic ways to gain root on a device. I've only done it once on my phone - but even that was a step-by-step howto guide specifically for my phone type.

[glorydays]

do any of these Chinese headunits have capacitive touch screens?

[nzer]

Originally Posted by glorydays

do any of these Chinese headunits have capacitive touch screens?

T7019a and TUN21 both have capacitive screens.

[sciallo]

Originally Posted by GreenPants

For all you folks wanting to get standard Android app audio to work properly, it looks like there is a 'The 3rd party application priority' tickbox in Settings->Sounds that you could try selecting. All of a sudden the sound on Angry Birds started working correctly without having to run Video or anything beforehand.

I've played with my system and turned the key beep on - that sounds like a hardware beep that is probably completely independent of the audio routing.

I also assigned the mute function to one of the keys and it seemed to work as you'd expect. Mute/unmute worked, as well as using the volume knob to unmute.

@sciallo:
Is it possible that there is a hardware/cabling reason for the muting behaviour? I can't think of all the lines out the back of the unit off the top of my head, but could any of those being shorted result in volume muting? (There is a Sounds setting for muting the volume during reversing, for example - if the unit always thought you were in reverse, then that could explain things)

I know that you mentioned 'factory wipes' - are you referring to the Factory Reset option in the menu?

When I get some time, I might sit down and record every configuration in the settings menu - it might help to play spot-the-difference.

Yes, I was referring to the "factory reset" but I have tried all I could think of, including reflashing and soft resets with pen..

I have experimented with backup mute, enabling that and connecting the reverse wire. I also tried connecting to a bluetooth speaker through the dongle and I get no sound out of that either. CD/DVD is one app the active wallpaper doesn't seem to sense. I'm at a loss, and about ready to figure out how to ship it back to china :-(

I've used linux for years, so I'm not new to command line, but I'd say I'm new to hacking android, however this little sound problem is getting me to dig deeper than I have before into android inner-workings

Got your list of settings and it seems pretty consistent with mine...

If I could ask a favour to anybody, would you mind sending me the output of a couple of commands in a terminal:

cat /proc/asound/cards

getprop

and

alsa_amixer

(You can send that output to a text file so it's easy to move around, for example

getprop > /sdcard/extsd/getprop.txt

will output to a getprop.txt file on your external card...)

Also do take a look at those files, some interesting things: seems like there is a setprop for backlight and the alsamixer has a bunch of options, one in particular looks like is about mic sensitivity... Of course not hearing anything out of my unit my experimenting tells me very little other than "no dice, you're not getting audio back this easy"

Another kind of interesting discovery, was messing with a wireless keyboard (logitech k400) pressing fn+esc and fn+-> (end) puts the unit in some weird almost-sleep-state, screen off music still plays (unfortunately) and by 'plays' I mean it doesn't pause, not that I can hear it... dunno about sound, but it lower it's consumption (my power supply makes noise proportionally not that I measured it), also, if I press the button I assigned to screen dim, the screen comes on but not the unit, not until I press home or something else or press the above combination again... Just kind of interesting to know, as I was thinking of ways to wire the unit to not have to reboot for short stops... (By the way I am NOT at this point suggesting you try as I don't know that keyboard and it's short-cuts aren't what caused my problem)

Originally Posted by Brody602

@GreenPants Hey you got mentioned a few times so you probably missed the post tuat Nzer mentioned you for me. I found a new unit on tradesolytion with orange/amber led's that is a toyota fit, running android 4.0. And i was wondering if you can help out with a root at all. Or if you know anything about one. This unit is the T6229A . I've made serveral posts with questions on page 54, and here is the post you were mentioned in.

http://www.ft86club.com/forums/showp...postcount=1183

Thanks in advance for all your help

They posted stock firmware at the XDA forums for one of the new pure 4.1 radios (probably the same), I tried taking a look at that to see if it could be rooted the same way as the HAL9K... It seems like it's encrypted in some way, I couldn't simply loop-mount any of the files, so it's going to be a bit more complicated to root those (at least for my abilities).

I am considering one if I end up returning this one, but not if there is no root...

[GreenPants]

@sciallo - will hopefully get to that later, but I think the area you really want to be looking is the sbd driver, rather than the linux/android sound subsystem.

From what I have gathered by looking at some of the decompiled stock app binaries is that the sbd driver is responsible for the audio routing. If I read my notes correctly, then possibly:

sys/virtual/sbd/misc/source

[sciallo]

Originally Posted by GreenPants

@sciallo - will hopefully get to that later, but I think the area you really want to be looking is the sbd driver, rather than the linux/android sound subsystem.

From what I have gathered by looking at some of the decompiled stock app binaries is that the sbd driver is responsible for the audio routing. If I read my notes correctly, then possibly:

sys/virtual/sbd/misc/source

Yeap, I got a copy of those outputs, nothing that different there, thanks, I'll look into sbd.

[sciallo]

Originally Posted by GreenPants

@sciallo - will hopefully get to that later, but I think the area you really want to be looking is the sbd driver, rather than the linux/android sound subsystem.

From what I have gathered by looking at some of the decompiled stock app binaries is that the sbd driver is responsible for the audio routing. If I read my notes correctly, then possibly:

sys/virtual/sbd/misc/source

The whole /sys/devices is a pretty good maze, lot's of references to sbd, with most of them linking to these files and folders:

# ls /sys/devices/virtual/sbd/misc/
uevent
subsystem/
power/
source
lheadrest
rheadrest
phone
reverse
navi
reset
#

Looks like devices for IO type devices, so you're probably right, it's probably around here, but it's a little above my paygrade... no Idea what to do with this...

any clue what that "reset" file/device is? I was hoping it could give me that master reset I've been wishing for. Thing is set for write only, and even changing that I can't get even cat to read it... Experimenting I see the "cat reverse" switching from 0 to 1 if I connect the wire, but writing to it does nothing... Like I said it's a bit above my head.

Also a 'cat /sys/devices/virtual/sound/timer/power/control' returns 'auto'
and 'cat /sys/devices/virtual/sound/timer/power/wakeup' returns an empty string...
Wouldn't mind being able to try to set to 1...?

I have so much to learn