Reply to post

Hot!IVONA blocked by Voice Manager even though it's functional otherwise

Author
zeco
User
  • Total Posts : 0
  • Reward points: 0
  • Joined: 2017/06/02 20:14:14
  • Status: offline
2018/09/10 05:51:37 (permalink)

IVONA blocked by Voice Manager even though it's functional otherwise

The version 15.1.7 app update (Aug 24, three updates ago) contained "a lot of code gymnastics to make the obsolete IVONA TTS voices work in @Voice" and "Trying to detect and suggest solutions for damaged TTS voices installed on user's device".
 
(I'm one of those holdouts who cannot let go of IVONA, because for me the US-English "Kendra" still hasn't been matched in quality by any voice on offer at the alternative TTS engines by Acapela, Cereproc, and others. For me the most important quality is that I can absorb text content at high speeds without getting my attention strained by sloppy mispronunciations, sound artifacts, or treble spikes. For German TTS I found Acapela's "Klaus" to be superior to IVONA's "Marlene" in that regard, so it's not because I'm just overly sentimental or anything like that.)
 
IVONA actually still seems to be functional on my Android 7.1 device and I almost never had any issues using it in @Voice with the Voice Manager before the v15.1.17 update. But since the update, when Voice Manager is enabled and the next article in line is English (after a non-English one), @Voice will throw an error popup saying "This voice is not working correctly. We suggest selecting a different one, or reinstalling this voice correctly. [OK]"
 
When I turn off the Voice Manager by switching to "Use only the system default voice" and selecting IVONA in the system settings, @Voice will use it without issue. So it seems that IVONA is falsely being detected as damaged by the Voice Manager in my case. Or what else could be the problem?
 
I realize that IVONA has been discontinued as an app since 2016 and that @Voice is in no way responsible for compatibility issues that come up in newer Android versions, so this is *not* a complaint or bug report. I'm just trying to figure out if something can be done to make it work with the Voice Manager again.
 
So right now I have to switch TTS engines manually each time the language of my added articles changes, instead of having the Voice Manager do it automatically (which I find super useful). One solution might be if you offered an extra checkbox option to deactivate the damaged TTS detection.
 
I installed and reinstalled IVONA using preserved apk and obb files. I'm pretty sure the file permissions are ok.
 
I have root access to my device, so I can take a deeper look under the hood if you're interested in some details or want to have me try something out.
post edited by zeco - 2018/09/10 05:52:50

3 Replies Related Threads

    Admin
    Administrator
    • Total Posts : 275
    • Reward points: 0
    • Joined: 2010/11/22 00:00:00
    • Location: USA
    • Status: offline
    Re: IVONA blocked by Voice Manager even though it's functional otherwise 2018/09/10 07:56:32 (permalink)
    IVONA is really not working well. When the app tries to select it as the voice to read text with, it is giving me back an error status, when you see that message. It is due to the erroneous interaction of Ivona TTS voice software and the new versions of Android system.
     
    One questions, which of Ivona voices do you have installed on your device? When testing my devices, and from some other users, I discovered that when Amy and Gwyneth English voices are present together on a device, there is a lot of trouble. Maybe the same situation happens with Kendra and Gwyneth, not sure here. If you have Gwyneth voice installed, please uninstall it completely, then try the normal use of other Ivona voices, please let me know if this changes anything. Or if you really like Gwyneth, uninstall Amy first, then also Kendra, test both situations and tell me the result.
     
    Greg
    zeco
    User
    • Total Posts : 0
    • Reward points: 0
    • Joined: 2017/06/02 20:14:14
    • Status: offline
    Re: IVONA blocked by Voice Manager even though it's functional otherwise 2018/09/16 01:42:00 (permalink)
    I randomly found that IVONA won't report the error status to @Voice's Voice Manager after you start the com.ivona.ttslib.CheckVoiceData activity of the com.ivona.tts app.
     
    In adb / termux it works using this line:
     
       am start -n com.ivona.tts/com.ivona.ttslib.CheckVoiceData
     
    In Tasker you can create a Launch App action, long-press IVONA and select com.ivona.ttslib.CheckVoiceData
     
    I haven't tested this, but according to this you would be able to implement it in Android using this code:
     
       Intent intent = new Intent();
       intent.setComponent(new ComponentName("com.ivona.tts", "com.ivona.ttslib.CheckVoiceData"));
       startActivity(intent);
     
    I found this after I realized that IVONA would always work with the Voice Manager as soon as I started one of the respective voice name apps from the app drawer. So eventually I looked into the AndroidManifest.xml of IVONA's main app (only to later find out that Tasker would have listed the activities much easier) and tried the activities that are declared there.
     
    So I guess if the Voice Manager sees a problem with IVONA, it could try to prod IVONA back to life by starting the CheckVoiceData activity. You only have to do it once, or until the com.ivona.tts process that usually stays active in the background gets killed and restarted.
    Admin
    Administrator
    • Total Posts : 275
    • Reward points: 0
    • Joined: 2010/11/22 00:00:00
    • Location: USA
    • Status: offline
    Re: IVONA blocked by Voice Manager even though it's functional otherwise 2018/09/16 10:59:40 (permalink)
    Interesting, thank you very much for sharing this insight, Zeco! I'm testing the idea of inserting similar code into @Voice app, but for now it's not clear if it will really help there. Will see what I can find out.
     
    Greg
    Jump to:
    © 2018 APG vNext Commercial Version 5.1