leoandroid
Newbie
Ok. I'm using the new firmware but the bug mentioned by grindinonyourm is still happen. the mouse pointer is replaced with your V play startup wallpaper.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Ok. I'm using the new firmware but the bug mentioned by grindinonyourm is still happen. the mouse pointer is replaced with your V play startup wallpaper.
Can you please explain to me how you managed to do that? I'm not kidding, Me and my colleague are unable to reproduce that kind of error. It doesn't really make any sense... maybe it's kernel related... don't know.... Please help me on that one
My english is very bad but i will try to!
Recently i installed the new firmware. I added google account and set my google account i one of LCD.
When i plugged off my box and plugged in in another TV happened the bug.
i dont know how to fix it, so i must re-install the firmware.
It's very strange because it's not allways.
The last weekend i've tried in other LCD and the bug has not been happened.
EDIT: The bug also happened without exchange my TV.. I plugged of box, but when i plugged in the bug is happened again.
Hi,
V-Play download section
There's new fw package, 2012-06-12, fixes Flash and probably other issues. Flash Player 10.2 is included in package.
Sorry for inconveniences and my apologies to all who downloaded last package (2012-06-11 over 60 downloads). I simply overlooked kernel configuration bug.... once again, sorry
You're a machine! i'm testing the last fw and now you makes a new release!
Great job
Hi,
V-Play download section
There's new fw package, 2012-06-12, fixes Flash and probably other issues. Flash Player 10.2 is included in package.
Sorry for inconveniences and my apologies to all who downloaded last package (2012-06-11 over 60 downloads). I simply overlooked kernel configuration bug.... once again, sorry
Update: f16ref firmware doesn't have that problems, just install Flash player from my site, it will work fine. From now on working Flash version will be included in all firmware releases.
Hi Stan1983. I appreciate your work. I am trying to install this firmware on a Measy X7. We start installing, this message apperar:
..." ert failed: getprop("ro.product.device")== "c03ref" || setprop("ro.build.product") -- "c03ref"
error in /udisk/update.zip
status 7)
-- Install apk aborted "....
Can you give me a clue? Thanks a lot.
Recovery says that firmware is not for your product. I'm developing firmwares for Visson ATV-108 c03ref and f16ref boards, I'm not into 'cooking' roms or something like that. I don't believe my firmware will work on your device, especially 'cause it's not based on c03ref board. Does your device use Amlogic chipset?
Stane:
Thank you very much for answering! Yes, is an ARM Cortex 9. I allready install an android 2.3 from other thread. But can not install a lot of applications. Here is my CPU detail. Thanks for your time!
/system/etc # cat /proc/cpuinfo
Processor : ARMv7 Processor rev 1 (v7l)
BogoMIPS : 1599.0
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part : 0xc09
CPU revision : 1
Hardware : AMLOGIC MESON-M1 8726M DVBC
Revision : 0020
Serial : 000000000000000b
Stane:
Thank you very much for answering! Yes, is an ARM Cortex 9. I allready install an android 2.3 from other thread. But can not install a lot of applications. Here is my CPU detail. Thanks for your time!
/system/etc # cat /proc/cpuinfo
Processor : ARMv7 Processor rev 1 (v7l)
BogoMIPS : 1599.0
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part : 0xc09
CPU revision : 1
Hardware : AMLOGIC MESON-M1 8726M DVBC
Revision : 0020
Serial : 000000000000000b
The update-script is different i see....Have a look from the wistar update.zip
Dear stane1983, I'm testing your new 20120611 FW on my f16ref board and it's a very good job! Issue about market are solved, speed and graphics are very improved with a better performance, flash player is working too. I have some questions:
- I still have no signal from A/V after boot the MBX but it can be manually set on Display>Output Mode>480i or 576i and in this case A/V out it's working but when you reboot the MBX the the system automatically set to HDMI by default and if you connect the MBX to a TV with only composite audio/video then you have no image and sound. Can you please check it when you will receive the f16 board and try to solve?
- Wi-fi sometime got disconnection (grey icon) and I noticed that the wi-fi signal power is lower than other devices connected to my wi-fi spot even the MBX is not far from it.
- I cannot put the MBX in standby or switch off using the iPazz Port which is full working (it can be done only with the remote control which is not working for all the other functions), is there any way to solve the issue considering that the MBX have no any power switch.
Thanks in advance, keep up your great job!
lucky lucky. cant hurt tho. if done right, it will extend the life of these devices.
@stane:
Thanks for your efforts for fixing flash. I'll test today and report here.
Btw. yesterday I tested the camera application with a web cam which used to work on 2.3.4. The application crashes immediately after starting it. The kernel detects the usb device, but maybe the v4l2 module is not compiled in your kernel (it does not get loaded anyway) ? I remember v4l2 was the module which used to be loaded by my 2.6.34 kernel on 2.3.4 fw.
What can we do about the annoying scaling issue ? Whenever I play a video it uses the full 720p screen, which on my tv, means that the image "gets outside" the screen. I've noticed this happening with any video player (standard, mx player, etc.).
Cheers.
You're right. v4l2 is not compiled with kernel. Will add it. During my testing and fixing kernel for not showing any picture I disabled it and forgot to enable...
About scaling issues, I need to go deep into Amplayer sources, currently they are not reading variables (if you set your screen position) but uses default values. It's very high on my todo list, will solve it, maby in next release... same thing for f16ref firmware. I belive the same behavior is on stock rom, but I'll change that
Ok, if you compile v4l2, could you also compile a few more: uinput.ko and xpad.ko ff-memless.ko ?
It seems that this is the case indeed. Maybe the ubootenv.var.720poutputx, etc. properties from build.prop might help here?