Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#752
Rebase of earlier PR
On app open, if there is a nonzero amount of bytes remaining on your device, then you will Get a green popup saying that you have some amount of seconds of audio remaining to download.
Upon pressing the green tab, you will be taken to the sd card page, where there is a button that says 'click to download audio/memories'. It has a green progress bar and a warning stating that you should have good internet connection if yo want to download.
If you press the button, you will notice the green bar filling up and the percentage remaining increasing. This means that the storage bytes are being streamed successfully. If for any reason your internet disconnects, then the bar will stop progressing and you will need to repress the button to continue. The app will save how many bytes you have already streamed for in case you want to continue downloading.
If the backend doesn't receive data after the first packet for at least 10 seconds, the resulting audio file will be parsed. It uses VAD, then fat whisper to partition the audio file and processes them separately into memories (it is also flagged as storage. Each separate file is also saved in some backend.
Assuming a valid memory is created, the user will get a notification upon the backend finishing the parsing. If the user presses it, then the memory will automatically appear. It also works if you just go to the memory screen.