TeamAmaze / TeamAmaze/AmazeFileManager
Smb support with additional sockets
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
I am using LINKSYS router, and AmazeFileManager username/password combination fails in using SMB service. However, it could be approached by my default system manager, VLC-android, and the apps I created myself. After I looking into the code, I found AmazeFileManager use jcifs-ng socket only, which has many limitations. I would like you to extend this App by unifying additional smb providers such as smbj-rpc、smbj、and jcifs. (LINKSYS accessible by jcifs).
A good reference project for such approach is [S](https://github.com/xyoye/SmbPlayHelper), which can be adopted directly with minimum effort.
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.
Research direction
Start by tracing AmazeFileManager's current jcifs-ng SMB socket usage and compare it with the provider-unification approach in SmbPlayHelper. Determine how smbj-rpc, smbj, and jcifs would be integrated, then verify that the app can authenticate to SMB services such as the LINKSYS router.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100