postak05

So my experience - maybe I have some strange/fake MyGica 1900AC (have 8GB eMMC only): After half a year I decided to upgrade Kitkat 4.4 to Lollipop 5.1 on my MyGica 1900AC. All I have to say - nothing changed for me from time I tried it last. My issues on Lollipop 5.1: - no ethernet at all (LED blinking, but system not recognizing hardware (no ETH0 at all - chip on board is RTL8211F), WiFi OK. - Lollipop unstable for me. I installed Factory defaults files, Root for 5.1 and then Standby patch. Still got problems with standby, sometimes the box restarts itself to MyGica logo, Kodi 17.1 freezes - but I think it's system problem, not KODIs So now I'm back to KitKat 4.4, ETH0 recognized (so it is not HW issue), LAN working (after powersupply is unplugged I have to restart BOX to LAN show up - only once). When I use memory cleanup trick, I have no standby issues at all. Something about Kodi 17.1 / MyGica Media center - the main problem is missing support of TLS 1.2 in Android 4.4, but it can be probably solved (it will be hard work): http://stackoverflow.com/questions/37705367/how-do-i-get-tls-1-2-to-work-in-android-4-4-without-the-help-of-google-play-serv http://stackoverflow.com/questions/32545073/android-4-4-2-and-tls-1-2 https://blog.dev-area.net/2015/08/13/android-4-1-enable-tls-1-1-and-tls-1-2/ http://stackoverflow.com/questions/28943660/how-to-enable-tls-1-2-support-in-an-android-application-running-on-android-4-1 But I'm not sure, these are changes, that MyGica team did in their fork of KODI...

Ok, I did some research today and I can confirm (on Android 4.4): - running KODI 16.1, put to standby, resume from standby => PROBLEM (screen flickering with KODI image, no reaction to remote) - launcher home screen, put to standby, resume from standby => NO PROBLEM

Yesterday, I got some OTA update for my ATV1900AC (Android 4.4). It's true, that I havent run my box since approx. 20.12.2016. I found new icons on main screen - "Power" and "Maintenance" icon like in the Android 5.1 build. The build date is something about 20.7.2016 (didn't realized what was the date before, but I think it was same), so I tried several tests with standby. Short time standby (several minutes) worked fine. I tried to Standby box over night then. What a surprise when the box started without problem this morning! I'll test my box more. If this will be ok, I will stay with only one problem - wired networking after power off not working (no network icon). I have to reboot box using remote. I am not sure when this problem occur, but it seems it's always after longer PowerOff (power supply pulled out of the socket). Happy New Year to everyone!

Luke, what remote do you have?

Guys with "StandBy problem", please try this: When the box is working (normal screen), try to put it to Standby (with remote), wait 3 seconds and try it to Wakeup again with remote. Did the box woke up? I tried my MyGica several days ago and when I put it to Standby and immediately try to wake up my box, it works. When I put box to Standby and wait more time, it will not wake up. (version 4.4 or 5.1 - doesn't matter, maybe 5.1 working a little bit better)

root exist for 5.1 like IMG file - manual update (update_Mygica_ATV1900AC_5.1_root_patch.img)

Dear support, first to your questions. - I got this unit from my friend and he cant remember where he bought it (SN is MS0505715340319 - read from android system) - I used latest 5.1 firmware from first post of this thread (used factory_restore.rar) - Unit should be MyGica 1900AC More details going on: Yesterday I tried to reflash my unit with Kitkat (4.4) image from this forum (4.4 ATV 1900AC.zip). Remote was not working at all, so I decided to search info on internet. I found modified file remote.conf, so now my box is on 4.4 (+ OTA upgrade) with working remote (but also with some "standby/power on" bug - box will not wake up after standby). I tried to reflash 5.1 again, but now there's no ETH0 interface in system. In 4.4 ethernet is working fine, so it is not hardware problem... Thanks

Just for completing previous post - I flashed version "1.0.1b" dated november 24 2016

Is KR-32 remote supported? Today I installed some 5.1 firmware (not sure exactly which version), but I can "Power on" this unit only - no other buttons working. KR-32 with old "4.4.2" firmware was working fine... (I am sure its not box / remote problem) Edit: If not supported, which firmware (4.4.2) should I download to restore KR-32 remote support?

POST DELETED DUE TO THE SAME MESSAGE BEING POSTED MULTIPLE PLACES QUESTION WAS ANSWERED IN OTHER LOCATION