| title |
|---|
Docs |
Welcome to the offcial cSploit documentations page.
We are in a delicate first phase of this project and we are not stable, yet. Currently we are moving many parts of the code into a new core. Even if you see a release marked as release, this does not mean that it has no bugs. My apologies for that, I'm doing my best to achieve a stable app ✌️.
A short error message it's often self-explanatory. Sometimes it too difficult to explain an issue with a short message and here you can find a few common exmaples that explain some errors:
- cannot start process: this message is printed when the core of cSploit cannot start the required process.
cmdreturned #number: this message is printed whencmdhas exited with an error codenumbercmdkilled by signalnumber: this message is printed whencmdhas been killed by signalnumber
The above errors are bugs that are specific for your device. Hence please report them if no one already did.
I'm human, thus i can fail. This is why we need a good issue tracker like the one provided by github. I'm working on an automated way of reporting bugs directly from the app just by clicking on a button. Until then you have to manually collect your logcat and share it on the github issues page.
Q: Is cSploit the same as dSploit ?
A: The basic code is the same but I'm continuing the development since dSploit has been oficcially merged into zANTI2.
Q: When will feature XYZ implemented or bug ABC fixed?
A: Like on every other open source project - don't ask for ETA 😁
Q: How can I contribute to cSploit ?
A: There are many ways to contribute: by donating, by improving the source code or by correcting my English on this website.