tarabostes

I have some issues with this latest update. The lights on my 380 do not behave properly, the network activity light stays on when the device is in standby. I encountered the HDMI bug two times so far: once the screen was black and the second time it was flashing with a static image of the last image displayed on the screen and the speed was increasing... From these points of view the previous update was perfect for me. One last detail: is there anything that can be done to improve the behavior of the mouse cursor when used with the MyGica remote? It used to move better be more controllable but lately it barely moves on the screen even with new batteries in the remote and from 1m distance.

For the 1st time in a long while my 380 took the update without freezing at ~80%. Great! What's new in this update?

I hit some bumps after the initial flash and I had to reflash (2-3 more attempts). I cannot say what went wrong but when i tried to restart, my 380 would not go beyond the 4x-8x logo. "Third time's the charm", flashed from recovery every time and in the end all went well. It's fast, very fast this ROM. No problems with play store but I never had any problems before. I went ahead and installed SPMC 15 and it's running great. I used the android app Kernel Adiutor (silly name IMHO) to set the governor to interactive as with hotplug (default) I had some issues playing x265. It rocks ever since Did a few tests for the HDMI issue and it seems to be completely fixed now. I miss the auto-stand-by feature, hate the screen-saver one. Can you please bring back the auto stand-by feature as it was in the 2014.1105 ROM? Thanks for this update!!!

So far the update went well. I no longer updated from with the Android update app but I started in recovery and flashed from there. Did factory reset and rebooted after. More to come...

Downloading and will post feedback soon. Thanks!

I have been testing the latest beta firmware on my 380 and it doesn't go in stand-by anymore. The 2 LEDs are turned on green all the time and the network activity one keeps blinking. One would turn off and the other one would go red in stand-by. I flashed clean and even did factory reset. First time it froze at ~80%, I waited 10 minutes then I cut the power and turned it back on. It finished flashing and once it booted up I did the factory reset procedure from Android.

I had the flickering issues 2 or 3 times so far and I was able to solve it only by rebooting the device. There was a post suggesting to set the resolution fixed to 1080p / 30 fps but in my case I had the black screen issues even after setting that. In my case I learned to start the TV 1st, then switch to the MyGica input and it is working ok after. I have MyGica connected directly to my TV but I can't say if that makes a difference. In my case it is stable, I had even weeks of uptime (only standby used). Try SPMC, see if it makes a difference. How much free space you have on your device? If you press on the menu button while it is playing the videos, how much buffer you have? (see the last 2 lines) What resolution do you have set on your TV? I agree a firmware update to fix these issues is badly needed.

I so I did factory reset and video worked for a day or so. After that it was back to video stuttering badly and not watchable. I did a reset again and it works for a day or so. This is really frustrating and buggy update. I had to do this because wanted to go with Kodi, otherwise 2014 update was just fine. HDMI blackout and blinking issue remains. When power on the unit after standby video either is blackout or would start flickering. Kids use this to watch cartoons and they are really annoying me why its not working . I bought 2 mygica units and both are now unusable. I should have kept my old stupid media player. Atleast fix the video stuttering asap. The fact you have 2 units with the same issue makes me believe the 2 Mygicas might not be the problem. A defective unit can happen but 2 the same time? Highly unlikely IMHO. What sources are you watching? What format? What / how many apps you have installed? What player are you using for those files? The built in MyGica Kodi app? How about MX Player? Can you test with the official stable Kodi? Can you test with SPMC? Have you tried with different format video files just to get a more complete picture of the possible issue? If you are playing the video files from the internet or a network location, can you try with the same video files on a USB stick or USB HDD? Don't be upset... we'll sort it out!

Thanks for the update, Justin. Good to know you're fine There are some knowledgeable folks around here so I would say things have gone pretty well around here (support wise). Of course, I am speaking about this model section that I kept an eye on. Been testing a 812-H for more than a month and I must say I'm impressed. I'm really looking forward to the MyGica 1900 to see how it will play along. I've had my share of issues with the 380 and 582 but I'm pretty satisfied. Ciao!

Same thing happened to me on a brand new box that came with the 1105 firmware. It froze while updating the firmware at ~75% I waited 2h before I unplugged the power cable and I plugged back in. After that it started by flashing again the firmware and this time it completed the process. Just to make sure it went fine, once it booted, I did a factory reset and it worked fine ever since. Try doing a factory reset and see if your issues will be resolved. Good luck! BTW: Where is Justin?

Great news, enjoy your MyGica!

Maybe there is something wrong with the micro sd card. Do you have another you can test with? Try getting in recovery without the micro sd in, then insert it and try upgrading the firmware.

1st have only the micro sd connected and no other USB drives. Try the second method to get in recovery, wipe data and cache then restart the device. If still not working, try to reflash using my previous instructions.

If the device still can boot, use the reboot program and just chose the option to boot in Recovery. If your device doesn't boot, here are the steps: 1. Prepare a micro sd card formatrd with FAT32 2. Extract the .IMG firmware file and then change the extension from .IMG to .ZIP (not sure what OS you have but make sure it's done properly) 3. Copy the renamed file in the root of your memory card then insert the card in the device. 4. For the 582: connect the power cable of the device while inserting a pin/paperclip in the tiny hole from the bottom of your device. Once you insert the paperclip you should feel a switch clicking when pressed. For the 380: connect the power cable of the device with the power button pressed. 5. After connecting the power cable wait ~10 seconds then take out the paper clip for 582 / release the power button for the 380. 6. If the procedure was done properly you should be in recovery and you should see a menu with some numbered options. 7. The best now is to have a USB mouse connected to the device. Use the scroll wheel to go up and down in the menus then the left click to activate the highlighted option. 8. Wipe the data (make sure you select the option (YES, wipe DATA) 9. Wipe the cache (wiping the cache might not be necessary but I always do it anyway). 10. Once the cache is wiped, chose the option to update/flash. In the following menu do not chose from EXT but the other option (from USB). 11. You should be able to see the files you have on your microsd. Go and select the .zip file you renamed in step 2. 12. If all went well, you should see the device verifying the integrity of the zip file then you should see the little android and a progress bar at the bottom. 13. The whole flashing process might take 5-10 minutes so be patient. At the end, your device will reboot automatically. 14. The 1st boot will be slow so be patient again. That's pretty much it. Try this before returning your MyGica, it should work. If there is one thing I would advise anybody using any Android device like MyGica: as much as possible, try to never unplug the power of your device!!! The file system on its various partitions might get corrupted and your device might not boot anymore and in this case you ca try wiping the cache and try booting again but if this option doesn't work, wiping data or replafhing might be the only option. If you see your device frozen in no matter what program, try pressing the HOME button first and see if you are able to get out of the frozen app. Use the app to reboot as the Android OS will take care of closing all apps properly. Something else you can try is to keep the MENU button pressed until you see a circle with a rocket taking off and then your background apps/services will be cleared, releasing their used memory. I hope my explanations make sense, if there is something that's not clear just let me know and I'll try to explain it better. Cheers!

What about the issue with the screen going black temporarily when you fast forward or rewind in XBMC/Kodi? I have the problem occasionally, when I turn on the TV and the MyGica 582 and the screen is blank. If I switch input to something else and then back to the Mygica it comes back. It is not consistent. All connetions are HDMI. Receiver is a Denon AVR-1713. TV is Sharp Aquos LC-80LE632U. BTW, this problem is not new with this firmware. It has been there in the previous one as well. I also have the problem with the screen going blank when starting a video or fast forwarding or rewinding when hardware acceleration is on in KODI. I saw somebody in the 1800 feedback thread was suggesting the switch the TV to the MyGica input before powering on / bringing the MyGica on from standby. Let the TV 'wait' for the signal then switch the MyGica on. It worked for me a few times. It may be a pointer for finding the cause of this bug. BTW: Is Justin gone, on vacation maybe? Didn't see him around for almost a week

1) Go back to 1105 firmware for the time being until the next firmware comes out and probably your issue gets sorted. 2) I have the same problem, would love to see a fix (btw: I'm using a Logitech KR400 wireless keyboard with touchpad). 3) I remember the firmware for the 582 and 1800 were interchangeable BUT there were some setting files that had to be changed, to compensate for the memory difference. The 582 with the memory settings for 1800 would crawl and even crash (low memory killer, number of background apps, etc.). I wonder if this parameters were not missed in the latest 582 firmware. I have also a Minix X8 and I must say it's flying compared to the 380/582 and the only difference is the quantity of memory that is double. Now you are mentioning 1200 which is in fact a dual core player so normally it shouldn't be faster but if there is something that I noticed in the last 2-3 firmware releases, the quantity of Google junk files is waaaaay higher than before (probably the GMS effect:) ?). I bet if you disable/delete all unneeded Google apps and background services your 582 would fly.

Make sure you extract the .img file from the archive. I remember Justin was mentioning wiping the cache could be a possible solution for OTA problems. You can also flash the update from the recovery as a last resort but you would have to do a few extra steps.

Yes, it happens to me, too. I have the 380 connected to my Sharp 82U connected directly with just the HDMI cable. I had no issues like this with any firmware before and including 1105. The beta firmware that followed had the problem and now the latest release does the same thing. It is random and it doesn't happen all the time. I have my 380 set to go in stand-by after 12 minutes I had it set like this in all previous firmwares. I start the TV, I switch the input, then I press the power button for the 380 to come from stand-by and it does but 3-4 out of 10 the lights are green but the screen stays black. If I press the power button again it will go in stand-by but upon pressing it again the LED will turn from red to green but screen will stay black. If I wait another 12 minutes to go in stand-by by itself again then I try again, most of the times it might work. I had an issue with the latest firmware update, where the system froze at the 1st restart after the OTA update was installed so the only solution was to clean flash the image. What I can say is this bug was introduced after the 1105 firmware update. Otherwise the system is really fast and I had no significant crashes with the latest firmware.