[SOLVED] Mediacom Smart Tv Mini M-STAS2100

louigi600 · 06-22-2014, 05:15 AM

I recently got one of these cheap Andrpod TV dongles.

It was in offer at just under 50 Euro ... and on the box it said tons of interesting things like: dual cobe 1.5 Ghz cpu, wifi, full HD, DLNA.
I has the assistant open up a box to have a peep at the documentation inside and I found therein that id should be an allwinner A20 SOC based device and that it had 1Gb of ram. That convinced me to buy one.

I went home, wired it up, and got disappointed:
the USB debug feature for connecting to PC has been crippled,
the android on it supports SMB browsing but the device has been somhow crippled to render smb browsing impossible,
cpuinfo says it's a dual core ARMv7 (implementer 0x41 arch 7 variant 0x3 part 0xc09) but says mothing about sunXi instead it reports it's a RK30board,
cpufreq says that the fastest allowed frequency is 1.6Ghz,
the firmware has hcitools (for bluethooth) but the kernel lacks support,
cannot access all partitions to check if it really is A20 (should find a script.bin somewhere) because it requires rooting,
antutu benckmark only scores 9105 with a really crappy 6FPS while doing 3D graphics even the single core A13 XZPAD700 tops the 3D performance with a single core and supposedly the same Mali 400 GPU,
the firmware lacks google play (but can be installed via the wifi link).

If I knew all this information I don't think I'd have one now

I opened op the casing to have a look inside but there are soldered metal shields that prevent seeing the CPU the onlu usefull information inside was a label on the board (IMT DG08_V2.0 20130703).

Can anyone confirm what type of SOC this board uses ?

According to here it's a RK3066 SOC based board but I'm not 100% sure on this.

louigi600 · 06-23-2014, 03:58 PM

I was able to hack a little more information out of /proc:
cmdline

Code:

console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x004A0000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x00004000@0x00004000(kernel),0x00008000@0x00008000(boot),0x00008000@0x00010000(recovery),0x000C0000@0x00018000(backup),0x00040000@0x000D8000(cache),0x00200000@0x00118000(userdata),0x00002000@0x00318000(kpanic),0x00100000@0x0031A000(system),-@0x0041A000(user) bootver=2013-06-21#1.34 firmware_ver=4.1.1

mtd

Code:

dev:    size   erasesize  name
mtd0: 00400000 00004000 "misc"
mtd1: 00800000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 01000000 00004000 "recovery"
mtd4: 18000000 00004000 "backup"
mtd5: 08000000 00004000 "cache"
mtd6: 40000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic"
mtd8: 20000000 00004000 "system"
mtd9: 6a200000 00004000 "user"

partitions

Code:

major minor  #blocks  name

  31        0       4096 mtdblock0
  31        1       8192 mtdblock1
  31        2      16384 mtdblock2
  31        3      16384 mtdblock3
  31        4     393216 mtdblock4
  31        5     131072 mtdblock5
  31        6    1048576 mtdblock6
  31        7       4096 mtdblock7
  31        8     524288 mtdblock8
  31        9    1738752 mtdblock9

cpuinfo

Code:

Processor       : ARMv7 Processor rev 0 (v7l)
processor       : 0
BogoMIPS        : 1007.67

processor       : 1
BogoMIPS        : 1007.67

Features        : swp half thumb fastmult vfp edsp neon vfpv3 
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x3
CPU part        : 0xc09
CPU revision    : 0

Hardware        : RK30board
Revision        : 0000
Serial          : 0000000000000000

The odd thing is that I found the cifs module loaded ... Fail to figure out why I can't mount smb shares (that I've tested to work properly on other pc) ... maybe busybox mount does not like the syntax:

Code:

busybox mount -t cifs //192.168.0.155/share /mnt/share

I get told that there's something wrong with the arguments
I did a little search and have not yet had a chance to check out this king do suggestion:

Code:

busybox mount -t cifs \\\\192.168.0.12\\mydata /mnt/myData

The good thing is that the device need's not much work to get a root shell on a terminal emulator.

Can't get usb debug and/or usb storage to be detected on external PC, not sure if kernel is missing usb gadget support or if the mincro and standard usb conenctions are connected to the soc's USB 2 ports leaving the otg port unconnected or if some other sort of deliberate crippling has been applied by Mediacom.

louigi600 · 06-26-2014, 03:58 PM

Still no luck neither with cifs nor with nfs. Although both are working correctly on other linux systems (including ARM ones) I cant seem to be able to mount either on any of my android 4+ systems. The best I can get is a permission denied (that is nonsense because it's a public share with guest access).
Anyone have any workarounds ?

louigi600 · 06-28-2014, 06:41 AM

I don't know exactly why but things started working when I created an account for accessing the SMB share. The guest acces seems to be snobed by all my android devices but they all seem to like the same shared device when accessed with the non guest user account.

Both mounting from terminal emulator and browsing the share via APP are now working ... but may require several attempts before actually getting it to browse/mount correctly. Video playback over wifi from the smb share is somewhat jerky

louigi600 · 06-29-2014, 08:27 PM

Quote:

Originally Posted by louigi600

Can anyone confirm what type of SOC this board uses ?

According to here it's a RK3066 SOC based board but I'm not 100% sure on this.

Well I'm still not 100% sure on this but having a look at the RK SOC's characteristics chart I think that the only one that fit's what I found by lurking around with the terminal emulator is the RK3066/68.

If anyone is interested in having an ordinary linux distribution on this device here's a useful link.