[GH-ISSUE #176] (reader app) issue when scrolling up a text after pressing the button home #63

Closed
opened 2026-05-06 13:14:59 +02:00 by BreizhHardware · 6 comments

Originally created by @mathurien on GitHub (Mar 15, 2022).
Original GitHub issue: https://github.com/UpsilonNumworks/Upsilon/issues/176

Describe the bug
when you go on the reader app and you scroll down a text, if you press the home button and you go back to your text in the reader, you won't be able to scroll up anymore

To Reproduce
Steps to reproduce the behavior:

  1. go to the reader app
  2. select a text
  3. scroll down your text
  4. press the home button
  5. go back to the text in the reader app
  6. try to scroll up
  7. see issue

Screenshots

https://user-images.githubusercontent.com/101398581/158471737-bf86db82-2191-498c-b916-cff8d70e7fdd.mp4

Device (please complete the following information):

  • The device on which you're running Upsilon : n110
  • Upsilon Version: 1.0.0-dev
  • Upsilon commit: public
Originally created by @mathurien on GitHub (Mar 15, 2022). Original GitHub issue: https://github.com/UpsilonNumworks/Upsilon/issues/176 **Describe the bug** when you go on the reader app and you scroll down a text, if you press the home button and you go back to your text in the reader, you won't be able to scroll up anymore **To Reproduce** Steps to reproduce the behavior: 1. go to the reader app 2. select a text 3. scroll down your text 4. press the home button 5. go back to the text in the reader app 6. try to scroll up 7. see issue **Screenshots** https://user-images.githubusercontent.com/101398581/158471737-bf86db82-2191-498c-b916-cff8d70e7fdd.mp4 **Device (please complete the following information):** - The device on which you're running Upsilon : n110 - Upsilon Version: 1.0.0-dev - Upsilon commit: public
BreizhHardware 2026-05-06 13:15:00 +02:00
  • closed this issue
  • added the
    fixed
    bug
    labels
Author
Owner

@fmOOmf commented on GitHub (Mar 16, 2022):

Hello.

Same issue for me : randomly, the "reader" app freezes, requiring a hard reset.
I think it appears when (but not every time) one quits reading whereas not being in the first page.
When coming back to reader, reader resumes displaying (it displays the same page than before quiting : there is a memory). Then randomly, it freezes when scrolling up.

If this behavior is confirmed, it means there is a way to avoid the freeze, going up to the first page before quiting the app.
It may help until the issue is fixed.

<!-- gh-comment-id:1068871071 --> @fmOOmf commented on GitHub (Mar 16, 2022): Hello. Same issue for me : randomly, the "reader" app freezes, requiring a hard reset. I think it appears when (but not every time) one quits reading whereas not being in the first page. When coming back to reader, reader resumes displaying (it displays the same page than before quiting : there is a memory). Then randomly, it freezes when scrolling up. If this behavior is confirmed, it means there is a way to avoid the freeze, going up to the first page before quiting the app. It may help until the issue is fixed.
Author
Owner

@fmOOmf commented on GitHub (May 9, 2022):

Bonjour à toute l'équipe.
Avec la rev01 stable :
Impossible de revenir dans les pages précédentes d'un fichier liseuse qu'on a déjà commencé à lire. Ca dit : "Attention à la syntaxe". Il faut reset pour fix.
Peut-on désactiver la mémorisation du curseur ?

<!-- gh-comment-id:1120687024 --> @fmOOmf commented on GitHub (May 9, 2022): Bonjour à toute l'équipe. Avec la rev01 stable : Impossible de revenir dans les pages précédentes d'un fichier liseuse qu'on a déjà commencé à lire. Ca dit : "Attention à la syntaxe". Il faut reset pour fix. Peut-on désactiver la mémorisation du curseur ?
Author
Owner

@Lauryy06 commented on GitHub (Jun 19, 2022):

Est-il possible d'avoir un exemple de fichier qui a ce bug ?

<!-- gh-comment-id:1159653042 --> @Lauryy06 commented on GitHub (Jun 19, 2022): Est-il possible d'avoir un exemple de fichier qui a ce bug ?
Author
Owner

@fmOOmf commented on GitHub (Jun 19, 2022):

Bonjour.
Oui, par exemple celui-ci.
Si on va en page 2, et qu'on quitte la lecture du fichier.
Alors quand on ré-ouvre le fichier, il se positionne bien en page 2, mais il est impossible de remonter en page 1.
On ne peut pas uploader un *.urt => je le transmets par discord.

<!-- gh-comment-id:1159773063 --> @fmOOmf commented on GitHub (Jun 19, 2022): Bonjour. Oui, par exemple celui-ci. Si on va en page 2, et qu'on quitte la lecture du fichier. Alors quand on ré-ouvre le fichier, il se positionne bien en page 2, mais il est impossible de remonter en page 1. On ne peut pas uploader un *.urt => je le transmets par discord.
Author
Owner

@Lauryy06 commented on GitHub (Jun 27, 2022):

It's fixed ! 2a234305f3

<!-- gh-comment-id:1167207802 --> @Lauryy06 commented on GitHub (Jun 27, 2022): It's fixed ! 2a234305f331b38199c7d61798e06a9ab050aa3d
Author
Owner

@fmOOmf commented on GitHub (Jun 28, 2022):

Merci Lauryy !
Cela va aider à démocratiser l'utilisation de Upsilon.


Great ! Thanks a lot.

<!-- gh-comment-id:1168309791 --> @fmOOmf commented on GitHub (Jun 28, 2022): Merci Lauryy ! Cela va aider à démocratiser l'utilisation de Upsilon. --- Great ! Thanks a lot.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Upsilon#63
No description provided.