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

[Brody602]

@nzer @GreenPants @2forme

Just out of curiosity, can any of you tell me how certain you are that the USB ELM327 would work with the T6229A Android 4.0 head unit without a root?

Since apparently android 4.0 supports usb on the go?

Thanks guys!

[jx86]

I guess the only way for you to find out is to buy it and try for yourself. As nobody has the unit, nobody will be able to verify for you. Perhaps it might be best to go to Xda forum?

[GreenPants]

Originally Posted by sciallo

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.

With all of these devices, you should be able to echo characters/strings/values into them. From memory, I played around with the reset a bit and all it did was reboot the unit.

From what I can gather, this is how the stock apps interact with the kernel - the do the exact same thing to change audio routing etc. But it's been a few months since I really looked into it so I'm a bit fuzzy on it all.

[nzer]

Originally Posted by Brody602

@nzer @GreenPants @2forme

Just out of curiosity, can any of you tell me how certain you are that the USB ELM327 would work with the T6229A Android 4.0 head unit without a root?

Since apparently android 4.0 supports usb on the go?

Thanks guys!

Not certain at all. Buy one and try, I'd love to know.

My issue is that I prefer my HKS OB-LINK using the carscope app. It is Bluetooth only so needs the root to communicate with it.

[GreenPants]

Originally Posted by Brody602

@nzer @GreenPants @2forme

Just out of curiosity, can any of you tell me how certain you are that the USB ELM327 would work with the T6229A Android 4.0 head unit without a root?

Since apparently android 4.0 supports usb on the go?

Thanks guys!

At the end of the day it's just a crap shoot. Although Android 4.0 may have better support for USB OTG/Host, it is still relying on the Linux kernel under the hood - and there is nothing to stop developers from including or excluding whatever drivers they want.

Don't forget that besides the USB OTG/Host support, you also need the appropriate USB client driver for your USB ELM327.

I'm not sure how Android (4.0) handles random USB devices or serial ports - it is possible that you need root to be able to access these devices directly - unless there is an Android API to do this from within Java.

[GreenPants]

Originally Posted by sciallo

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...?

These should all be standard stream interfaces.

Can't remember the exact syntax, but try something like:

echo 1 > /sys/devices/virtual/sound/timer/power/wakeup

(Note: Not responsible if your car blows up as a result)

[GreenPants]

Originally Posted by sciallo

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

See attached

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...

Yeah, noticed that as well. Don't think that broke your unit.

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).

My guess would simply be a different file system. If it is designed to be stored on eMMC, it could be FAT32. If NAND, then possibly something like JFFS2/YAFFS. What processor is it for? The first few blocks may be special, designed to boot the processor and not actually part of a file system.

[GreenPants]

Does anybody know, or can they check for the FCC ID of the T7019a?

I'm guessing it should be printed/on a sticker somewhere on/in the unit.

[Brody602]

@GreenPants @2forme thanks for all the help, I might take a chance and buy the unit

[jx86]

.

[sciallo]

Originally Posted by GreenPants

With all of these devices, you should be able to echo characters/strings/values into them. From memory, I played around with the reset a bit and all it did was reboot the unit.

From what I can gather, this is how the stock apps interact with the kernel - the do the exact same thing to change audio routing etc. But it's been a few months since I really looked into it so I'm a bit fuzzy on it all.

Originally Posted by GreenPants

These should all be standard stream interfaces.

Can't remember the exact syntax, but try something like:

echo 1 > /sys/devices/virtual/sound/timer/power/wakeup

(Note: Not responsible if your car blows up as a result)

I did try that last night, but other than changing the output of cat, it didn't really do anything... I expected the unit to react to it... I'll try some more...

Originally Posted by GreenPants

See attached

I compared , not much difference. in the output of alsa_amixer you have 'Speaker Function' on.... Mine is off but so is someone else's who's sound is working. I tried to turn it on, no change. I wonder what does turn it on

Originally Posted by GreenPants

Yeah, noticed that as well. Don't think that broke your unit.


My guess would simply be a different file system. If it is designed to be stored on eMMC, it could be FAT32. If NAND, then possibly something like JFFS2/YAFFS. What processor is it for? The first few blocks may be special, designed to boot the processor and not actually part of a file system.

I believe it's an A9 the particular stock rom files that were posted here are for this unit I believe the specs for many others that are popping up on ebay are all the same, but don't quote me on that.

[sciallo]

Originally Posted by GreenPants

These should all be standard stream interfaces.

Can't remember the exact syntax, but try something like:

echo 1 > /sys/devices/virtual/sound/timer/power/wakeup

(Note: Not responsible if your car blows up as a result)

The only one I could get a reaction out of was brightness somewhere in there, numbers between 1 and 8 would change the brightness...

Anything I sent to reset or wakeup or any of the many others did nothing I could see. There is one for input and it changes between 1 and 7 depending on what's playing (DVD, Radio etc) I could also change /sys/devices/virtual/sound/timer/power/control from 'auto' to 'on' but can't tell if that does anything. /sys/devices/virtual/sound/timer/power/wakeup is empty and can't find any values that will stick or do anything.

I also checked sound out of the preamps, nothing. Speaking of the key beeps, do those come out of the preamps or just the amplified outs? No beeps out of the preamps for me...

I'm at a loss, I'll still see if they send me the latest MCU and if that does anything, but I think I'm ready to return it. Probably exchange it for the same one, they offered to exchange it for a 4.1 but I don't have a problem with how the 2.3 works and I want root. I just don't know that this isn't going to happen all over again... Maybe I'll just get a refund and wait...

[astranagan]

Can anyone send me a copy of the stock music app's apk? I uninstalled it with Titanium backup and I can't get it back now

[GreenPants]

Originally Posted by astranagan

Can anyone send me a copy of the stock music app's apk? I uninstalled it with Titanium backup and I can't get it back now

Stock, as in unmodifed? Or stock, as in the OEM one included in the hacked firmware?

If the latter, then you could have simply reloaded the OS.