Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 11/02/2016 in File Comments

  1. 2 points
    For me I had to make 2 adjustments in Display settings for the HDMI to work properly. 1) I manually set the resolution 2) If I recall I had to set the setting "Color Depth Setting" to off. I guess these settings all depend on your TV and you may have to play with them. Mine is an old Samsung non-smart TV.
  2. 1 point
    The display issue you describe is something we cannot fix We found this varies by the TV you use the box on, as we have 8 different brands of TVs in our office and it works fine on 6 of them. This is the main reason this will stay in Beta, we had another development team to make 7.1, without having the full Uboot files of Android for these boxes. You can leave the box turned on 24/7, it will use a very small amount of electricity when doing this Me personally, I haven't turned off my box or rebooted it in over 6 months.
  3. 1 point
    So a couple of days using the unit with 7.1 (GUI takes a little getting used to) and the only annoyance is that when the unit is powered down and turned on again, you have to remove and reinsert the HDMI cable for the image to appear on the monitor/TV (have tested on 2 TV's and a 23" monitor). I attempted the fix that worked for Rick White (Justin advised turning off Automatic Display Resolution in Display settings), unfortunately it still does it. Apart from that, happy.
  4. 1 point
    And now upgraded to 7.1 😀 Props to the Support guys involved in working to resolve this. Started off bumpy and you folks came through. QV, give it a bash. I hope it works (follow bineredondat's instructions in the comments).
  5. 1 point
    Right, downloaded the 7.1 files again, reformatted the SD Card to FAT32, copied files to root and followed the update procedure as outlined to the letter. Status bar with oscillating multi-coloured rings appeared, ran through installation phase to Erase and screen went black. Unplugged HDMI and re-inserted without disconnecting power at any point and VOILA! We have 7.1 installed Thank you ever so kindly. Always a pleasure to eat humble pie when my views are changed by solid support.
  6. 1 point
    After 2 attempts, successfully unbricked the unit. Thanks to the Tech Support guys on here. It is appreciated.
  7. 1 point
    It worked! My bricked 495PRO is back to Lollipop. Kudos to MyGica support. Also, thanks for including USB Burning Tool (UBT) in the download package. There's lots of versions floating around so it's great that you provided a functional copy (v2.0.6.2) along with the img file. Your instructions show a different version but I can confirm that v2.0.6.2 worked fine. As noted, no NAND pin shorting was required (whew!) so there's no need to open the box, however, I had to use the USB port other than the one indicated in the instructions. That is, I had to plug my cable into the "front" USB port closest to the SD card slot. Also, in my case, I didn't have to hold down the power button. The 495PRO was immediately recognized by UBT when the USB was plugged in. The other USB port (towards the back) did not work with UBT regardless if the power button was held (or not) when the power was applied. Perhaps there have been minor hardware tweaks during the 495PRO's life cycle? Anyway, thanks again MyGica! I appreciate the responsive customer support. QV
  8. 1 point
    Hopefully this helps people that had a messed up upgrade. They were very kind to upgrade the software for us instead of the usual "planned obsolescence" of most android devices. I have recommended MyGica to several other friends and will continue to do so. Cheers guys 👍
  9. 1 point
    I spoke too soon. I reformatted the SD card, redownloaded the file just for safety and reupdated the firmware. I ended up with a lot of noise on screen and pulled the power to reboot it. The TV image was freaking out and is why I assumed it was bricked (blinking image). I had to unplug the HDMI cable and replug it back in. From another post I saw Justin suggested this fix that I think applies: So far it looks like it working now. Very happy!
  10. 1 point
    Waiting on the final version for numerous 1800 E's, are you there yet?
  11. 1 point
    I have read a couple of others' issue reports and based on my past experience I went through to find the solution. I would recommend to bring up CWM (Clock Work Mode) menu, and try to CLEAR SYSTEM CACHE before you can install/upgrafe Lollilop 5.11. I always do this every time and I don't have a problem.
  12. 1 point
    How did you resolve it? I have the same issue. It started to install and then stopped. Now all I have is a black screen. I've tried resetting, but can't get anything but the black screen.
×
×
  • Create New...