search

OpenSeizureDetector / Android_Pebble_SD

The main OpenSeizureDetector Android App, that is published on the Android Play Store.
http://openseizuredetector.org.uk
GNU General Public License v3.0
9 stars 11 forks source link

V4.2.10: Data Sharing Screen Very Slow #199

Open jones139 opened 1 week ago

jones139 commented 1 week ago

If the user has a lot of data in the online database, the data sharing screen is very slow and appears unresponsive - the Android system prompts whether to wait or close the app.

The solution is probably to limit the number of events returned by the web API to a manageable number?

I will probably not fix this in the Android Java code, because I am thinking of moving the event data editing to a web application rather than a native Android Java activity so that you can edit on a computer as well as on a phone.

pmithrandir commented 1 week ago

What about grouping events on the server before sending them to the app?When Arthur make a seizure of 5 minutes... I have around 50 events to fill, all being about the same real case in the end.If the API were grouping them and sending only one thing to enrich... It would be easier and lighter.We could work on what could make multiple event one. I know you have a gripping per 2 minutes, but maybe we can find a more accurate way.That part being in python, it's more my thing. I could work on it this summer if you want.Pierre Sent from Android deviceLe 23 juin 2024 20:48, Graham Jones @.***> a écrit : If the user has a lot of data in the online database, the data sharing screen is very slow and appears unresponsive - the Android system prompts whether to wait or close the app. The solution is probably to limit the number of events returned by the web API to a manageable number? I will probably not fix this in the Android Java code, because I am thinking of moving the event data editing to a web application rather than a native Android Java activity so that you can edit on a computer as well as on a phone.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

jones139 commented 1 week ago

Yes, when I implement a fix, I'll include grouping events so you do not need to edit each one separately - I'm not sure if the grouping will happen on the server or the front end at the moment though - it might be best to do it on the front end so the user has the option of un-grouping in case two different events happened in close succession.