-
-
Notifications
You must be signed in to change notification settings - Fork 62
2. Troubleshooting
You can find the logs in the Android/data folder in the storage device that you have installed the app onto. You may archive these logs or send the plain text context of the logs in an issue thread or when asking for support. If the logs do not suffice, you may be asked to provide debug information with a logcat.
It would be helpful if you mention your device manufacturer and model, and what you were doing and how a developer might reproduce the issue. Screenshots or a video recording of the issue are especially appreciated.
That's not good and is at the top of the priority list for investigation. Please make an issue and include your logs as above as soon as possible so that this may be resolved in a timely manner.
It is very likely that this is a storage permissions issue due to scoped storage. If your phone is made by a Chinese manufacturer or uses a Chinese variant of Android, you may refer to this suggestion.
If this is not the case, please provide your device manufacturer when reporting the issue along with a video recording or screenshot of you attempting to pick the file and exiting back to the menu if possible. What is particularly important information for debugging purposes is the directory path of the file you are trying to pick, which may show itself in the Player tab or in a log file.
Please ensure that your Android WebView is updated before use of the app. If your Android WebView is outdated, please update and try with a fresh reinstallation of the application. If you are experiencing issues and your Android WebView is up-to-date, feel free to make an issue and provide details on your device.
Sometimes, the problems are in the files being imported themselves not being in exactly the right format they should be, while other times, there may be an edge case the app does not handle.
You will need share the dictionary file for debugging purposes, provide any logs if available, as well as mention what dictionary format it is.
Please first check that you have the correct target language selected by clicking on the three dot button on the top right of the home menu and selecting Language settings. If this is not the case, it is possible that there could be an improvement in a language's search algorithm implementation.
Please provide a search term, the output you are currently getting and your desired output when reporting the issue. Alternatively, this may be an issue with a dictionary format importing correctly or an issue with the dictionary being imported. See the next question below.
If you are using a Yomichan dictionary with structured-content tags, these are currently unsupported and the app should indicate to you how many dictionary entries were omitted from the import. This issue is being tracked here. You may import an alternative version of the dictionary that does not use structured-content. Image entries are also currently unsupported.
If you are having issues with other dictionary formats, please feel free to make an issue. Provide the dictionary file with screenshots, and mention your expected output or behavior.
On older devices that are very scarce on storage space, it is possible that Android WebView will decide to wipe the cache from time to time. You may export backups from ッツ Ebook Reader from time to time if you are concerned that this may happen.
The solution to this issue would be to have the app back up either the raw IndexedDB data or ッツ exported data regularly, and import automatically when a wipe is detected. An implementation of this solution is currently in experimental stages, and this issue is tracked here.
You can adjust subtitle delay and add an audio allowance by using Adjust Subtitle Timing and Appearance in the video player.
Subtitle delay will offset when the subtitle should start and end. Audio allowance will bidirectionally increase the duration start and end of the exported audio.
If you are using PGS or image-based subtitles, these are unsupported. If you are using subtitles with fancy styling, the app may have trouble parsing them.
If you are streaming media from a network source such as Jellyfin or Plex, Select Subtitle Track will say that embedded subtitles are not supported. This is because subtitle data is spliced across an entire video file. Getting an embedded subtitle means that the entire file must be downloaded, which goes against the purpose of streamed video. Since jidoujisho requires an entire subtitle file be supplied and available, this makes it impossible to support these subtitles.
Using the app as an external player for Jellyfin will still allow the use of external subtitles, so managing and ensuring external subtitles are available on your PC and streaming them on your phone is a convenient remote setup. Alternatively, please import external subtitles stored in your local device storage instead.
Check if the position and duration in the bottom bar of the video player does not have red text. This will change the duration on the video player to the position to the end duration of the current subtitle.
Red text indicates that the video player is in Shadowing Mode, a feature that can be used to repeat subtitles, which is useful for shadowing or when practicing your own pronunciation or for hearing a sentence over and over again. You can turn this off by tapping on the duration again, and the duration should return back to normal.
This is because ffmpeg is busy processing embedded subtitles and cannot handle image and audio export at the time being.
You may need to wait a couple of seconds or minutes until this is done before you can export a card. You may check Select Subtitle Track in the Player menu to see the embedded subtitles load in individually. When subtitle tracks are all done loading, you may export a card appropriately.
You may be viewing HDR video. Unfortunately, the backing VLC player has issues with HDR playback when using hardware acceleration. Please consider watching an SDR version of the content you are playing instead.
Videos that are age-restricted unfortunately cannot be played with this app, or YouTube will return them in a format that does not work well with the backing VLC player. These are limitations of the methods in the dependencies that the app uses to get usable stream manifests from YouTube.
There is a strange issue with M4B format files that causes the backing VLC player to return a wrong duration for the audio file during playback. Converting these files to MP4 with ffmpeg for use with the app resolves this issue.
The app web scrapes from Google's search results in order to get lyrics for songs. Make a Google search with the format of Song Name - Artist Name and see if the search results load correctly with lyrics. It is possible that you may be blocking Google with a VPN, or that your country blocks its use.
Please first ensure that you have copied and pasted your API key from OpenAI correctly. You may check your usage quota here. You must have a usable allowance in order for the API calls to work. A pay-as-you-go plan may cost you less than $1 or $2 a month.
Token-less methods to being able to interact with an AI language model are being evaluated for consideration. The app previously did not require use of API keys, but unexpected downtimes and unreliability has made the app switch to using the official API.