• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Android 2.3 & 4.0 WiFi Internet HD 1080P HDMI Google TV Box ARM Cortex A9 Firmware

@stevan58: A/V fix will be included in next release, problem was in kernel configuration. Boot environment variables were not saved (scaling and video resolution) because ubootenv partition didn't actually exist.

@jandy123: Flash from market will not work, already tested.... :(
 
stane1983 said:
2. You're sure about codecs? What about AC3 and DTS?
6. I'm not sure what do you mean by that, allow overclocking?
Click to expand...

2. Here my codecs patch on 4pda.ru: http://4pda.ru/forum/dl/post/1763849/Patch_Codecs_2012_04_19.zip
Most codecs from RealPlay.tv firmware, some from Geniatech firmware
main(most) version: commit-66bde9d build_2012-04-19
audiodsp_codec_ac3: commit-a8400ac build_2012-04-03
audiodsp_codec_dca: commit-b1860f0 build_2012-03-28
audiodsp_codec_ddp_dcv: commit-3d9be56 build_2012-03-28
audiodsp_codec_mad_old: NSN Release
audiodsp_codec_mp3_lp: svn486 build_2011-12-07
audiodsp_codec_mp3: NSN Release
audiodsp_codec_ogg: svn384 build_2011-07-01
AC3 works. DTS not checked.

6. Yes, overclocking.
 
Hey Stane, this is great! Some questions:

1) In all usb (wifi and BT) devices, it seems there's more limited driver access in this ICS, can it be ? Or its fixed with the new kernel?

2) Support for "DD+ or E-AC-3" ?

Thank you!
 
grindinonyourm said:
STANE!

Cursor | Android Developers

Second public command, copystringtobuffer

This would be the command to load the mouse cursor into a buffer by memory address..and this would create the bug with the mouse cursor that we are experiencing. Have a look..
Click to expand...

Did you actually read the article? :D It's database cursor, and what is database cursor you can find out here: Cursor (databases) - Wikipedia, the free encyclopedia

In general. this has nothing to do with mouse pointer...
 
Hi there.

I have the first version ATV-101 that I got from Visson about a year ago.

I stopped using it because it wasn't working as smoothly as my Geniatech box, which was more stable. The problems I was having was mostly related to hardware accelerated decoding of hi-def RTMP streams.

I'm curious if there is some new firmware that I can try with this box. I'm not sure if mine has 256mb or 512mb, I need to confirm. But is there a recent Android 2.3 or Android 4.0 that I can try?

Thanks.
 
jorgebirck said:
Hey Stane, this is great! Some questions:

1) In all usb (wifi and BT) devices, it seems there's more limited driver access in this ICS, can it be ? Or its fixed with the new kernel?

2) Support for "DD+ or E-AC-3" ?

Thank you!
Click to expand...

1) Much more USB support will be included in next release. I will add it to kernel
2) Will see about codecs. I don't have any example of dd+ or eac3 encoding.... You have any link for testing purposes?
 
delysid said:
2. Here my codecs patch on 4pda.ru: http://4pda.ru/forum/dl/post/1763849/Patch_Codecs_2012_04_19.zip
Most codecs from RealPlay.tv firmware, some from Geniatech firmware
main(most) version: commit-66bde9d build_2012-04-19
audiodsp_codec_ac3: commit-a8400ac build_2012-04-03
audiodsp_codec_dca: commit-b1860f0 build_2012-03-28
audiodsp_codec_ddp_dcv: commit-3d9be56 build_2012-03-28
audiodsp_codec_mad_old: NSN Release
audiodsp_codec_mp3_lp: svn486 build_2011-12-07
audiodsp_codec_mp3: NSN Release
audiodsp_codec_ogg: svn384 build_2011-07-01
AC3 works. DTS not checked.

6. Yes, overclocking.
Click to expand...

Ok, I downloaded codecs and will integrate it if DTS works. About overclocking, I'm not really fun of overclocking, I used to overclock cpu to 900 MHz and it seemed to be unstable for some users. I can add overclock feature trough some script available on system partition.
 
jandy123 said:
It behaves much like there is some sort of memory leak, because after attempting to play some flash video, the system becomes very unstable. I could see the free memory going down (as low as 20 MB), then the android system starts killing lots of applications in an attempt to free more memory. After this, even without doing anything, memory goes down again, system starts killing applications and so on -- this repeats up to the point that the system freezes.
Click to expand...

Have you looked at the logcat output when this is happening? What we noticed on the Geniatech box is there is an issue with the Amlogic hardware acceleration. I believe the same is happening on the Visson box. We would see the following repeatedly in the logcat:

04-01 08:44:11.008 I/amffmpeg( 81): [avio_seek]fill buffer error -5
04-01 08:44:11.008 I/amffmpeg( 81): [avio_seek]fill buffer error -5
04-01 08:44:11.008 I/amffmpeg( 81): [avio_seek]fill buffer error -5
04-01 08:44:11.008 I/amffmpeg( 81): [avio_seek]fill buffer error -5


This error occurs repeatedly, thousands of times per minute, and causes the whole thing to slow down until you reboot.

This was fixed with the 03-17-2012 firmware update from Geniatech, so I assume it was fixed by Amlogic. I don't know if this fix ever made it to the Visson box.

Open terminal or SSH session and just watch the logcat. Or use an app like LogcatVM from the market.
 
avirex said:
Have you looked at the logcat output when this is happening? What we noticed on the Geniatech box is there is an issue with the Amlogic hardware acceleration. I believe the same is happening on the Visson box. We would see the following repeatedly in the logcat:

04-01 08:44:11.008 I/amffmpeg( 81): [avio_seek]fill buffer error -5
04-01 08:44:11.008 I/amffmpeg( 81): [avio_seek]fill buffer error -5
04-01 08:44:11.008 I/amffmpeg( 81): [avio_seek]fill buffer error -5
04-01 08:44:11.008 I/amffmpeg( 81): [avio_seek]fill buffer error -5


This error occurs repeatedly, thousands of times per minute, and causes the whole thing to slow down until you reboot.

This was fixed with the 03-17-2012 firmware update from Geniatech, so I assume it was fixed by Amlogic. I don't know if this fix ever made it to the Visson box.

Open terminal or SSH session and just watch the logcat. Or use an app like LogcatVM from the market.
Click to expand...

I'm using latest published sources from Amlogic, 2012-05-01 and they didn't fix that. I'll try something else...
 
stane1983 said:
I'm using latest published sources from Amlogic, 2012-05-01 and they didn't fix that. I'll try something else...
Click to expand...

So you DO have that error?

I wonder if Geniatech did something special in their 3/17 release to fix it...

I was able to reproduce this error at will, and it usually occurs when trying to stop/exit a network stream that is using hardware decoding. The amffmpeg process does not exit gracefully.
 
Hi Stane,

Do you have this problem?

every time i update the firmware, a new device is added to my google play
 

Attachments

  • Play.JPG
    Play.JPG
    145.1 KB · Views: 178
avirex said:
Have you looked at the logcat output when this is happening? What we noticed on the Geniatech box is there is an issue with the Amlogic hardware acceleration. I believe the same is happening on the Visson box. We would see the following repeatedly in the logcat:

04-01 08:44:11.008 I/amffmpeg( 81): [avio_seek]fill buffer error -5
04-01 08:44:11.008 I/amffmpeg( 81): [avio_seek]fill buffer error -5
04-01 08:44:11.008 I/amffmpeg( 81): [avio_seek]fill buffer error -5
04-01 08:44:11.008 I/amffmpeg( 81): [avio_seek]fill buffer error -5


This error occurs repeatedly, thousands of times per minute, and causes the whole thing to slow down until you reboot.

This was fixed with the 03-17-2012 firmware update from Geniatech, so I assume it was fixed by Amlogic. I don't know if this fix ever made it to the Visson box.

Open terminal or SSH session and just watch the logcat. Or use an app like LogcatVM from the market.
Click to expand...

I confirm, I cannot see the above error. As I said, the problem seems to appear when I switch to full screen. In windowed mode dmesg output seems to look fine:

06-14 23:22:29.435 E/ ( 1421): AMLHWVideoDecoder(0x67eb2000:0x0) - codec_init OK (476x360), rate=3840, ratio=338
06-14 23:22:29.435 I/amcodec ( 1421): [codec_pause]p->has_audio=0
06-14 23:22:29.435 I/amcodec ( 1421): video_pause!
06-14 23:22:29.435 I/FlashPaintSurface( 1421): needsBlending false
06-14 23:22:29.445 E/ ( 1421): HW decoder grabbed
06-14 23:22:29.445 E/ ( 1421): AMLHWVideoDecoder::SeekTo - start preroll - pts=0 prev pts=0
06-14 23:22:29.445 E/ ( 1421): AMLHWVideoDecoder(0x67eb2000)::SeekTo(0), write=0, isPreroll=1
06-14 23:22:29.445 E/ ( 1421): AMLHWVideoDecoder(0x67eb2000:0x67eb2000)::UpdatePlane() screen={1280,672}, orientation=0
06-14 23:22:29.445 E/ ( 1421): AMLHWVideoDecoder::UpdatePlane()
06-14 23:22:29.445 E/ ( 1421): m_dest=(0 0 0 0) m_lastDest=(134217727 134217727 134217727 134217727)
06-14 23:22:29.445 E/ ( 1421): m_source=(0 0 476 360) m_lastSource=(134217727 134217727 134217727 134217727)
06-14 23:22:29.445 E/ ( 1421): resX=1280 resY=672 orientation=0 m_lastOrientation=-1 m_layer=0

When I switch to full screen, I start getting lots of

06-14 23:22:29.445 E/ ( 1421): AMLHWVideoDecoder(0x67eb2000:0x67eb2000)::UpdatePlane() screen={1280,672}, orientation=0

but the screen stays black, while sound continues normally. At this stage, I cannot recover anymore, and all I get is a black screen. After a while with audio and black screen, sound stops and system practically freezes.

During the whole process LOTS of processes get kill. Btw. I noticed that using ICS, the system is rather low on memory anyways, compared to 2.3.4 ; maybe the dalvik heap can be lowered to 64 mb as well ?
 
Hi guys, help !!
I use ATV-108 Mediafire 4.0.3 (c03ref) and till now I did not have problems more than usuals.
After I tried to check "return to factory settings" I saw an A9 on TV screen and after that screen became blank and device does not react at all.
Red and blue lights are on but nothing more, reset button is frozen, no possibility to upgrade, absolutely no reaction.
Please help..!
 
matinaki said:
Hi guys, help !!
I use ATV-108 Mediafire 4.0.3 (c03ref) and till now I did not have problems more than usuals.
After I tried to check "return to factory settings" I saw an A9 on TV screen and after that screen became blank and device does not react at all.
Red and blue lights are on but nothing more, reset button is frozen, no possibility to upgrade, absolutely no reaction.
Please help..!
Click to expand...

V-Play download section

Try with recovery SD Card... pdf instructions are included in SDTool..
And buy a beer to Stane if it hepls... ;)
 
LeftyVz said:
V-Play download section

Try with recovery SD Card... pdf instructions are included in SDTool..
And buy a beer to Stane if it hepls... ;)
Click to expand...

Thanks man, actually I did recovery card, according to the following steps:
1) Using a formatted SD card, and following pdf instructions, I selected u-boot-aml-ucl.bin file and pushed "make SD card", bar was loaded and after I pushed ok.
2)I moved out SD card form PC (XP), installed again and did copy-paste on the root of the card all 7 firmware files.
3)I securely moved card out of PC and inserted in TV box, which was powered on.
4) In the beginning TV screen was dark but after 15 sec became bright and stucked there.
5) both lights, red and blue were constantly on with no reaction.
I tried also to activate system following upgrade procedure by pressing reset button, power on, but lamp did not blink at all..
I would appreciaty anyone's help..
 
matinaki said:
Thanks man, actually I did recovery card, according to the following steps:
1) Using a formatted SD card, and following pdf instructions, I selected u-boot-aml-ucl.bin file and pushed "make SD card", bar was loaded and after I pushed ok.
2)I moved out SD card form PC (XP), installed again and did copy-paste on the root of the card all 7 firmware files.
3)I securely moved card out of PC and inserted in TV box, which was powered on.
4) In the beginning TV screen was dark but after 15 sec became bright and stucked there.
5) both lights, red and blue were constantly on with no reaction.
I tried also to activate system following upgrade procedure by pressing reset button, power on, but lamp did not blink at all..
I would appreciaty anyone's help..
Click to expand...

There are problems with some sdcards.... Try small one (2Gb) and should not be sdhc. When you do recovery card, turn your box off and then use paperclip procedure.... Box must be off when you insert recovery sdcard and you have to power it on with reset button pressed.
 
hansmaiser said:
Device checker sazs it is a:
MBX DVBT reference board (c03ref)

Any idea why this wont work?
Click to expand...

There might be couple of reasons. My firmware uses 512 Mb system partition, so if you don't have at least 1 Gb of internal memory it wont work. Next thing, try with original Visson firmware first (02-25 or 04-23). You will probably have to install firmware twice (read my faq), because of different bootloaders.
 
stane1983 said:
There are problems with some sdcards.... Try small one (2Gb) and should not be sdhc. When you do recovery card, turn your box off and then use paperclip procedure.... Box must be off when you insert recovery sdcard and you have to power it on with reset button pressed.
Click to expand...


Well my friend, recovery card which I used is a simple SD 8Gb, not HC.
This card I used many many times for upgrading with several firmwares without any problem.
Anyway, I will try with a small one 250Mb and I will follow your instructions.
Thanks a lot.
 
You must log in or register to reply here.
Back
Top Bottom