[Android 7 Beta] A5BD_EN_N_Firmware_20190801_v2.5.0.2beta.rar

Discussion in 'Egreat A5 Firmware' started by Iron man, Aug 2, 2019.

  1. Iron man

    Iron man Administrator Staff Member

    Warning: This Beta firmware upgrade will clear all the date of your media player, and may have some unknown problems. Please upgrade with caution.

    I. info
    [Android 7 Beta] A5BD_EN_N_Firmware_20190801_v2.5.0.2beta.rar
    MD5: 47FEAF93C66E0DAA459619DEEBE79748
    Download link: http://data.egreatworld.com/A5BD_EN_N_Firmware_20190801_v2.5.0.2beta.rar

    II. Changelog
    Poster V3.0.6 upgrade:

    1. The poster wall function was upgraded to 3.0.
    2. Add the hard disk that has been loaded with posters for offline use.
    3. Add operation prompt text.
    4. Add the function of deleting posters.
    5. Add sorting function.
    6. Optimize and update local path loading logic.
    7. Optimize for direct loading of high-resolution posters.
    8. Optimize the backstage acquisition speed of poster data to improve user experience.
    9. Fix the problem of unplugging hard disk after adding local path as classification.
    10. Fix an issue where you might not be able to add network paths on Android7.
    11. Fix the disorder issue of the classification collection of local paths.
    12. Add AK83 remote control adaptation support.
    13. Add network disconnection and connection status prompts.
    14. Add Long press the "menu" button of remote control on the home page for 8 seconds to force switching 720P60Hz.
    15. Fix the login problem with GooglePlayStore.
    16. Preinstall Kodi and other common apps.
    17. Add the function of infrared IR on and off control separately.
  2. E_CS

    E_CS Well-Known Member

  3. Nice Monkey

    Nice Monkey Active Member

    Let the testing start. The release number went up a lot suggesting many interim internal versions. I am anxious to see what the finds/opinions are. :p

    As I have only the A10 and A11 still nothing to do for me. :(
    I understand the findings on this beta for A5 and A8 Pro only will be bug fixed first before a general normal release will be made available for all current platforms.
    Last edited: Aug 2, 2019
    depmesh and nenito2k like this.
  4. nenito2k

    nenito2k Well-Known Member

    @E_CS and @Iron man does this include playstore pack ? downloading now as i have waited too long...my internet is slow so other people will have it before me surely :)
    will report later, and for what is it worth thanks @Morgan and egreat team
    Last edited: Aug 2, 2019
  5. WiperX34

    WiperX34 Member

    I think it's in: "15. Fix the login problem with GooglePlayStore."
    I will try the FW after I go home :)
    nenito2k likes this.
  6. nenito2k

    nenito2k Well-Known Member

    gave the french forum and AVS word of the news...as activity was DEAD over there! hope it helps them :)
    @E_CS and @Iron man you DID not mention "update only in Force to recovery system mode"

    In my case i cant get the green android using the indicated usb port... Cant update !! and yes my usb is MBR and yes my usb is less than 16gb size !

    Robot only appears if i use usb3 port or the other side usb 2..but later i get error !!! Help
    Last edited: Aug 2, 2019
    WiperX34 likes this.
  7. Nice Monkey

    Nice Monkey Active Member

    As far as I remember one needs to change from USB2 to USB3 when running into the error. The first try via USB2 till the ring comes (bootloader A7) and then USB3 to the final install. Something like that. I think the bootloaders from Android 5.1 (Robot) and Android 7 (Ring) have a different USB port preference. This for going back and forth between A5 and A7.

    If the A5 already is on Android 7 FW 2.0.1.0 Beta then a normal upgrade via USB should work. No need for emergency flashing at all.
  8. nenito2k

    nenito2k Well-Known Member

    get the error on usb 2 and 3...and never got the rainbow...only robot is i use other usb ports...but alas...i get then the error; i am now formatting in fat32 on pc using the FULL format not quick...i will see if it helps

    Edit : just partionned my hdd to have an 8gb part in fat32 and still nothing !
    Last edited: Aug 2, 2019
  9. b0g0m0l

    b0g0m0l New Member

    1. Can't recognize movies with Russian name, doesn't add posters.
    2. DTS not working
  10. nenito2k

    nenito2k Well-Known Member

    Issue 1 is to be expected i suppose..
    Issue 2 is a huuuge issue !!!

    On my side.. Impossible to force recovery.. I have been trying gor 3 hours !
  11. Nice Monkey

    Nice Monkey Active Member

    Isn't your player already on Android 7 FW 2.0.1.0 Beta? Anyway you managed to install that one before. Just do that once more and next standard upgrade via USB to this FW. :)

    Simply can't imagine DTS does not work in general?
  12. nenito2k

    nenito2k Well-Known Member

    No monkey.. I am on lollipop...
  13. b0g0m0l

    b0g0m0l New Member

    Tried different settings that sound is not
    1.JPG
    2.JPG


    And if you disable DTS compatibility mode
    nenito2k likes this.
  14. Nice Monkey

    Nice Monkey Active Member

    I always had problems with the Chinese interpretation of "compatibility mode". I understand what "compatible" means under Amplifier Compatibility but activating a "DTS compatibility mode" for me means that the format is NOT native supported and it must be changed to LPCM to make output compatible. That is what you see. Useful for TV's without DTS support e.g. and my setting is OFF accordingly. Also TrueHD compatibility mode must be OFF to avoid DD signal degradation/stripping. This for those Egreat does not sound as good as it should/could in DD-HD modes. I would change the options accordingly myself to: "Convert DTS to LPCM" and "Convert TrueHD to DD standard". Then more people will understands what is meant.

    One would also presume these settings are inactive when "HDMI passthrough is set to ON", which they apparently are not.

    Confusing isn't it. I think I reported this in the past, but changing Chinglish is not that easy. They also regularly use "Open"and "Close" when they mean to say "On"and "Off" having apparently the same translations in Chinese.

    Happy testing!
    Last edited: Aug 2, 2019
  15. nenito2k

    nenito2k Well-Known Member

    @Nice Monkey cluster size maybe the problem in the usb recovery ? default seems no good
  16. Nice Monkey

    Nice Monkey Active Member

    Bootloaders are simple pieces of code and inflexible. Logical and Physical Sectors must be 512 bytes for sure. My working stick uses 1 sector per cluster hence 512 bytes too!
    Old (=smaller) sticks are better as these use low values.
    Last edited: Aug 2, 2019
  17. nenito2k

    nenito2k Well-Known Member

    I can only format fat32 up to 64kb cluster on my usb anyway i selected that and oher sizes and its no good ! Will try to borrow a usb tomorrow
  18. briguy65

    briguy65 Member

    Good luck Nenito -- I hope you can get updated. I am curious as to whether the black bars bug will stay corrected with Android 7, as well as maybe a Vidon update as well, but since I have only an A10 I will have to wait patiently as well as everyone else.
  19. nenito2k

    nenito2k Well-Known Member

    black bar has been ok since over a year ago...as hisilicon fixed the issue on the SOC...for now i have given up on update as i have no other usb drives..
  20. E_CS

    E_CS Well-Known Member

    @nenito2k
    Search for old USB 2.0/3.0 flash 4GB/8GB then format FAT32 with default cluster.
    Migration from Android 5.1.1 to Android 7.0 will work also with cheap USB flash 16GB/32GB/128GB like DataTraveler 100 G3 but need use MiniTool Partition Wizard to make 8GB(~7374MB)/4GB(~3638MB) MBR primary FAT32 partition.
    Note: conversion from USB GB size are made from commercial value of GB to real size of MB read on Partition Tool.
    Newest model USB 3.1 flash as DataTraveler Elite G2 with writing speed over 50MB is not recommended(for me not working) for migration from Android 5.1.1 to Android 7 or back.
    If box already on Android 7 v2.0.1.0 OTA update/USB update from Settings/info will work just fine not need to use paper clip.

    Copy/paste of post from here.
    When successful boot with recovery.img from USB 2.0 port with RST using paper clip
    [​IMG]
    Android 7 rainbow circle animation will be display
    [​IMG]
    USB MUST be MBR formatted as FAT32 with partition maxim 8GB.
    Can use MiniTool Partition Wizard if not have 2GB, 4GB, 8GB USB pen or don't know if is MBR formatted as FAT32.

    Trying update to Android 7.0 if will see Android droid animation update will fail.
    [​IMG]

    Loading update.zip fails for Android 5.1.1 & 7.0.
    [​IMG]

Share This Page