[GH-ISSUE #2183] It is suggested to optimize the power consumption of mobile device clients #1738

Closed
opened 2026-05-05 13:06:58 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @MindFollowing on GitHub (Jan 11, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2183

The solution you want

Mobile device client battery optimization
Alternatives considered

Sleep function of mobile device client
How to implement this function

  1. Battery historian is used to analyze the power consumption to optimize the program
  2. FRP service can sleep or wake up the client
    Application scenarios of this function
Originally created by @MindFollowing on GitHub (Jan 11, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2183 <!-- From Chinese to English by machine translation, welcome to revise and polish. --> **The solution you want** <!--A clear and concise description of the solution you want. --> Mobile device client battery optimization **Alternatives considered** <!--A clear and concise description of any alternative solutions or features you have considered. --> Sleep function of mobile device client **How to implement this function** <!--Implementation steps for the solution you want. --> 1. Battery historian is used to analyze the power consumption to optimize the program 2. FRP service can sleep or wake up the client **Application scenarios of this function** <!--Make a clear and concise description of the application scenario of the solution you want. -->
gitea-mirror 2026-05-05 13:06:58 -06:00
Author
Owner

@fatedier commented on GitHub (Jan 17, 2021):

We have on plan for that now, it's not designed as mobile app. Maybe it can be supported by others?

<!-- gh-comment-id:761808322 --> @fatedier commented on GitHub (Jan 17, 2021): We have on plan for that now, it's not designed as mobile app. Maybe it can be supported by others?
Author
Owner

@github-actions[bot] commented on GitHub (Mar 4, 2021):

Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.

<!-- gh-comment-id:790205658 --> @github-actions[bot] commented on GitHub (Mar 4, 2021): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.
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: github-starred/frp#1738
No description provided.