TeamAmaze / TeamAmaze/AmazeFileManager
FTP button in status bar pulldown does not start FTP server
Open
@TranceLove is already working on this.
Since Nov 27, 2020.
Area-FTP
Area-UIUX
Issue-Bug
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Describe the bug
The FTP button (icon) in the status (notification) bar pulldown does not start FTP server UNLESS the Amaze app is running.
If the app is running, the FTP button works as expected/designed.
If the app is not running, the logcat has
[11-26 18:24:44.615 7011:7011 V/FtpReceiver]
Received: com.amaze.filemanager.services.ftpservice.FTPReceiver.ACTION_START_FTPSERVER
[11-26 18:24:44.616 744:2836 W/ActivityManager]
Background start not allowed: service Intent { cmp=com.amaze.filemanager/.asynchronous.services.ftp.FtpService (has extras) } to com.amaze.filemanager/.asynchronous.services.ftp.FtpService from pid=7011 uid=10137 pkg=com.amaze.filemanager startFg?=false
[11-26 18:24:44.618 7011:7011 E/FtpReceiver]
Failed to start/stop on intent Not allowed to start service Intent { cmp=com.amaze.filemanager/.asynchronous.services.ftp.FtpService (has extras) }: app is in background uid UidRecord{cbbfc38 u0a137 RCVR idle change:uncached procs:1 seq(0,0,0)}
There was a related issue https://github.com/TeamAmaze/AmazeFileManager/issues/1337.
To Reproduce
Steps to reproduce the behavior:
- Restart the device. This ensures the Amaze app is not running.
- Pull down the status (notification) bar and push the Amaze's FTP button
- The button does not highlight and the FTP server does not start
- (Optionally, to confirm the button works if the app is running) Start the Amaze app
- Pull down the status bar and push FTP button
- The button is highlighted and the status message sys FTP server is running
Tablet (please complete the following information):
- Samsung Tab Pro 8.4 (SM-T320)
- OS: LineageOS 17.1 (Android 10)
- Rooted: yes, magisk
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.