https://play.google.com/store/apps/details?id=me.piebridge.brevent
In general, we will use a similar tool to ensure that the app exits to save power.
Plugins cannot be added to the power save list can cause errors during use.
FTP and WiFi plugins don't add the list then work fine, normal power consumption.
After the LAN plug-in is launched once, even if you exit, it will use a lot of power in the subsequent time.
LAN-Plugin used a lot of power
Moderators: Hacker, petermad, Stefan2, white
- ghisler(Author)
- Site Admin
- Posts: 50532
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Re: LAN-Plugin used a lot of power
That's strange, it should use any CPU power at all when not used. Do you connect via SMB1 or SMB2?
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Re: LAN-Plugin used a lot of power
Smb2, server had disabled smb1.
- ghisler(Author)
- Site Admin
- Posts: 50532
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Re: LAN-Plugin used a lot of power
I see - it looks like the SMB2 library doesn't have a disconnect function - the connection stays open in the background. But this shouldn't cause any activity as long as there is no data traffic...
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Re: LAN-Plugin used a lot of power
Reproduce the problem and try to solve it?
- ghisler(Author)
- Site Admin
- Posts: 50532
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Re: LAN-Plugin used a lot of power
I have tried to reproduce the problem:
1. Connect via SMB2
2. Check with app "System Panel" - the plugin has used 1s CPU
3. Checked an hour later - the plugin has still only used 1s CPU
4. Checked again 3 hours later - the plugin has disappeared from the active tasks
I have also checked the source of the SMB library - there is just one background thread, and it sits idle, waiting on InputStream.read().
Sorry, I have no idea how I should reproduce your findings.
1. Connect via SMB2
2. Check with app "System Panel" - the plugin has used 1s CPU
3. Checked an hour later - the plugin has still only used 1s CPU
4. Checked again 3 hours later - the plugin has disappeared from the active tasks
I have also checked the source of the SMB library - there is just one background thread, and it sits idle, waiting on InputStream.read().
Sorry, I have no idea how I should reproduce your findings.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com