1. Dear customers, partners, and friends of Zidoo/Eversolo around the world,

    As the Mid-Autumn Festival approaches, we would like to extend our warmest wishes to you and your loved ones. May this special occasion bring you peace, happiness, and a wonderful time together.

    Please note that our team will be on holiday from September 25 to 27 and October 1 to 7, 2026. We will resume normal work on September 28 and October 8, respectively.

    If you have any urgent inquiries during the holidays, please contact us at service@zidoo.tv or service@eversolo.com.

    Thank you for your continued support and understanding. We look forward to being back and assisting you as usual after the holidays.

    Warm regards,
    The Zidoo & Eversolo Teams

    Dismiss Notice

Eversolo bugs

Discussion in 'Eversolo DMP-A6' started by Eric777, Sep 27, 2023.

  1. Eric777

    Eric777 Active Member

    Hi! I've met some bugs on a new DMP-A6 with firmware 1.1.80:

    * On DMP A6 itself:
    - when I select my language (french), there is a check near it but all the elements stay in english. Even if I reboot the DMP or change to French Canada. There are only some elements like reboot which are translated!

    * On smartphone app:
    - when I display all albums (or all artists) and I select one of them, the app bug: there is a black screen instead of the list of tracks and, after one second, the start menu is displayed. No tracks are showed! It's not useable.
    On DMP-A6 directly, when I select "Tracks", the tracks are well displayed.
    - I notice that the list of tracks from an album is well displayed on the app if I click on current track, swipe to the left and click on the current album.
    - In settings, in General, there is each time the error "expected url scheme 'http' or 'https' but no colon was found" when I click on some options like Language, Input method, Power mode...

    Someone kwows what I could do to correct that?
     
    Last edited: Oct 2, 2023
  2. Eric777

    Eric777 Active Member

    Hi, I've launched a debug on the smartphone, here is the error :

    09-28 19:07:30.692 14759 14759 E AndroidRuntime: FATAL EXCEPTION: main
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: Process: com.eversolo.control, PID: 14759
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.eversolo.control/com.zidoo.control.phone.module.music.activity.AlbumActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String com.eversolo.mylibrary.bean.ZcpDevice.getHost()' on a null object reference
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2667)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2728)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1479)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6130)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String com.eversolo.mylibrary.bean.ZcpDevice.getHost()' on a null object reference
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at com.zidoo.control.phone.module.music.utils.MusicImageLoader.<init>(MusicImageLoader.java:64)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at com.zidoo.control.phone.module.music.utils.MusicImageLoader.create(MusicImageLoader.java:82)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at com.zidoo.control.phone.module.music.adapter.MusicAdapterV2.<init>(MusicAdapterV2.java:32)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at com.zidoo.control.phone.module.music.fragment.sub.SubFragment.onViewCreated(SubFragment.java:122)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at androidx.fragment.app.Fragment.performViewCreated(Fragment.java:2987)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:546)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:282)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:2189)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:2100)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:2002)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at androidx.fragment.app.FragmentManager.dispatchStateChange(FragmentManager.java:3138)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at androidx.fragment.app.FragmentManager.dispatchActivityCreated(FragmentManager.java:3072)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at androidx.fragment.app.FragmentController.dispatchActivityCreated(FragmentController.java:251)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at androidx.fragment.app.FragmentActivity.onStart(FragmentActivity.java:502)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1249)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at android.app.Activity.performStart(Activity.java:6740)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2630)
    09-28 19:07:30.692 14759 14759 E AndroidRuntime: ... 9 more
    09-28 19:07:30.695 1871 10119 W ActivityManager: Force finishing activity com.eversolo.control/com.zidoo.control.phone.module.music.activity.AlbumActivity
    09-28 19:07:30.695 1871 14921 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:877 com.android.server.am.ActivityManagerService$24.run:14273 <bottom of call stack> <bottom of call stack> <bottom of call stack>
     
  3. Eric777

    Eric777 Active Member

    After a discussion with the support, I'm happy to tell you that the last version of the APK resolved all the bugs I've mentioned. :):):)
     
  4. Roy N

    Roy N New Member

    Cool Eric, thanks. :)
     
  5. FotoModo

    FotoModo New Member

    Unfortunately I still have this "Expected URL scheme" probem and no idea, how to get rid of it. But only on my Xiaomi Redmi Note 11 Pro 5G. My older Xiaomi Redmi Note 8 Pro with older Android is behaving just fine. Any idea what could I do? I am pretty surprised, that there aren't massive complaints about this all over the forums.
     
  6. Eric777

    Eric777 Active Member

    Hi Fotomodo. Which version of APK have you installed?
     
  7. FotoModo

    FotoModo New Member


    Hi Eric777, always the latest one in both phones, actually v1.11.61
     
  8. Eric777

    Eric777 Active Member

    Ok, perhaps you could write to the support?
    In my case, because this forum didn't help me, I've taken some videos of Android screen with a tool named AndroidRec to explain clearly the bug and I've listed all the steps to reproduce the bug.
    (and the bug was present on my 2 recent devices with old version of Android).
     
    FotoModo likes this.
  9. FotoModo

    FotoModo New Member

    Hi Eric777, I did nothing about it, just bought A8 and new phone last weekend - Xiaomi Redmi Note 14 Pro and... the bug is still there, on the same place!!! Isn't it wonderful
     

Share This Page