Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong reported usage for Farhan #18

Open
bagnacauda opened this issue Feb 28, 2023 · 10 comments
Open

Wrong reported usage for Farhan #18

bagnacauda opened this issue Feb 28, 2023 · 10 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@bagnacauda
Copy link

Just installed the app, it reports 50+ minutes of usage.
Screenshot_20230228-105713_Farhan

@tahaak67
Copy link
Owner

tahaak67 commented Mar 1, 2023

Thanks for reporting, since this happened yesterday can you go back to yesterday's usage and check if the usage for Farhan is still at 56m?

@bagnacauda
Copy link
Author

Yesterday is now at 2 minutes, but today is at 40+(which is wrong):
Screenshot 20230301-074223_Farhan

@tahaak67 tahaak67 added the bug Something isn't working label Mar 1, 2023
@Wjxfi
Copy link

Wjxfi commented Mar 4, 2023

The same thing happened to me

I opened the app and it showed 56 minutes

@tahaak67
Copy link
Owner

tahaak67 commented Mar 5, 2023

bruh every time i see issue like this it makes me regret adding this feature 😂 (bad joke), since my test for calculating the duration is passing im guessing that the Android API is returning invalid data? i can't confirm yet since it didn't happen on devices i tested on.
I'll try my best to look into it.

@Warden20
Copy link

It is still happening

@tahaak67 tahaak67 added the help wanted Extra attention is needed label Dec 26, 2023
@hollisticated-horse
Copy link

hollisticated-horse commented Jan 2, 2024

Hello, same problem here.

@tahaak67 How do you calculate farhan usage time ? from the Android API ? maybe remove that amount from the data and have the app count itself the time spent on it ?

I have the proprietary app ActionDash running along side Farhan, and the numbers ActionDash provides are very different: 2h7min (with one to two minutes attributed to Farhan) from ActionDash vs 4h15min from Farhan.
So Farhan usage time count is wrong, so is two other app as well, one of which is my launcher Quickstep (stock AOSP shell/launcher).
Seems that ActionDash removes the launcher from the time count (my guess), where in Farhan I can see 54min from Quickstep.

@tahaak67
Copy link
Owner

tahaak67 commented Jan 6, 2024

Hello, same problem here.

@tahaak67 How do you calculate farhan usage time ? from the Android API ? maybe remove that amount from the data and have the app count itself the time spent on it ?

Farhan relies on events provided by the android api to calculate and display usage time, during my testing the durations displayed per app by Farhan were identical to thoes provided by digital wellbeing i even wrote test cases for the calculation method and it passed no matter what i provide as input. idk maybe there is something wrong with my implementation that i can't see?.
there was a time when i stayed on a game ideling for a while and digital wellbing didn't display any usage for that game while Farhan displayed the currect duration.

this needs further investigation and will take time as i don't have much time to work on it atm

@tahaak67
Copy link
Owner

tahaak67 commented Jul 2, 2024

does this still occur after the last update?

@tomaszk8266
Copy link

For me, it still occurs.

@hle-cer
Copy link

hle-cer commented Jul 9, 2024

yes its still wrong for me.
Screenshot_20240709-204402
how is this even possible 🤣🤣
I use graphene os without digital wellbeing. idk if that has something to do with it. It seems to be reporting the time when app was running in background as screen time 🫤

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

7 participants