-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
M-Droid not working on Android 4.4 #21
Comments
Can you plug the device on your computer, enable USB debugging and then sens me the output of |
Currently I don't have access to my System, will upload the output when I can access my System (24 hours). |
@Avizini Thanks in advance, will investigate once I have the output :p |
Actually I was able to generate a log file using a android app(root). I am doing this for the first time and have no idea about the information it has in it, can you give me your email address to confirm that it doesn't contain any sensitive data?
…On 2018 3 22 07:34:01 UTC, SkyzohKey ***@***.***> wrote:
@Avizini Thanks in advance, will investigate once I have the output :p
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#21 (comment)
--
Avizini
|
@Avizini The logcat does contains informations about Android processes and debug informations. What I'm interested in is the part about MDroid, so that I can see why it does crash. You can of course send me the logs at [email protected] :) |
Mail Sent.
…On 2018 3 22 07:59:59 UTC, SkyzohKey ***@***.***> wrote:
@Avizini The logcat does contains informations about Android processes
and debug informations. What I'm interested in is the part about
MDroid, so that I can see why it does crash.
You can of course send me the logs at ***@***.*** :)
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#21 (comment)
--
Avizini
|
@Avizini Thanks, gotta take a look at the logs, I'll come back to you once I've found the problem (and fixed it :p) |
I have the same problem with Galaxy J1 J100h, Android 4.4.4 and M-Droid 5.4. Is it right, that M-Droid should run with Android>=4.1? [1] Link to the F-Droid Forum: M-Droid doesn’t start |
I am running KitKat 4.4 with the latest M-Droid app, downloaded from GitHub releases. The app crashes as soon as I launch it. I have attached a recording below.
The text was updated successfully, but these errors were encountered: