TeamAmaze / TeamAmaze/AmazeFileManager
mountFileSystemRW not working with default mount command
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
I found out that Amaze doesn't properly remount /system to rw state. It's because it parse from mount command output and default toolbox output is missing some words. So I have to use mount from busybox.
Toolbox Output
/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
Busybox Output
/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/system on /system type ext4 (ro,seclabel,relatime,data=ordered)
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 locating mountFileSystemRW and the code that parses mount command output. Compare the toolbox format shown in the issue with the busybox format, then verify that the default command correctly identifies /system as read-only and remounts it read-write.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100