Skip to content

HOWTO Report Bug

Jump to bottom
CHEF-KOCH edited this page Apr 30, 2015 · 19 revisions

Index

You should NOT

  • You should NOT contact the carrier or the store in which you purchase the phone. They can't help you with software related problems. Any Application developers support their own applications! - So AFWall+ does!
  • You should NOT use the comment section in the Google Play Store section to report issues. The comment section is a peer-to-peer channel in which consumers can leave messages and ratings. This should be used to recommend or not recommend the application. If you are NOT a paid customer, developers can not access your email address to contact you about your concerns directly. Often developers get unusable comments in the Google Play Store (ie This app does not work!!). Without contacting the developer directly, there is nothing that can be done and your comment can be marked as SPAM.
  • You should NOT report bugs in the XDA thread because we may never see the message, since we not daily monitor all new stuff.
  • DO NOT set a milestone unless you are a developer and expect to fix the bug yourself. By default disabled to any new contributor.

Before contacting support

  • Watch the Changelog.md / Todo.md files if the problem is already fixed or on our radar.
  • Can you document the steps to reproduce it so that it happens every time? - Or is it only once?
  • Search and browse current tickets to make sure someone hasn't already reported your issue.
  • Make sure you have the latest version of the application/source code. This can be done by checking the Google Play Store for updates or push the latest GitHub source and compile yourself.
  • Make sure you have the latest Android OS updates (stable -> no nightly's!). This can be done in Settings on the phone, via Over-the-Air (OTA updates) or manually on XDA by downloading another ROM which may fix your problem.
  • Make sure you know the version of Android you are running on your phone. This can be found in the Setting under About Phone.
  • Make sure there is only AFWall+ installed and enabled, other tools like Avast can make some troubles if they are enabled.
  • Make sure you enabled the in-build loggin option under Preferences - Log Preferences and enable the Enable Firewall Logs option. In the main menu you can now hit Firewall Logs. Now you can see an Export to SDCard option, which will export you log to /sdcard/afwall/rules.log.
  • Make sure your disabled all your custom scripts before you test the problem, we not supporting problems which may caused by external/optional rules if there are wrong or simply if you don't know how to handle it.
  • Ensure that AFWall+ was tested with several options that comes with it, sometimes it's easier to play with the settings to solve the problem as debugging all possibility's which may cause the problem.

How do I capture my logcat?

  • This is VERY important especially for any crashes. To do this I recommend an application like aLogCat or Catlog which is totally free available on Google Play Store. Both of these programs can dump their logs to a .txt file, which is very useful for debugging. Or, you can do it in terminal emulator. The most important part of the logcat are when AFWall+ first starts and logs around the time when your problem occurred. Generally it's a good idea to just capture the whole thing and attach that as discussed when reporting your issue. The logcat is only 64Kb big (adb logcat -g) - so you have to act quickly after a problem occurs - this is a Google Android OS limitation to not flood the console.

Logcat step-by-step via Terminal Emulator

Through Terminal Emulator:

Type su and hit enter before you run the logcat command!

The code for logcat to output to a file is:

logcat > name of problem.txt

You can also add the -f argument:

logcat -f name of problem.txt

How I prefer to do it is this way:

logcat -v long > name of problem.txt

Logcat will be saved under:

/dev/log/[system]

If you want the log on your sdcard type this:

logcat -d -f /sdcard/name of problem.txt *:V

With the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line. -f tell it where to save the log to and -d makes it dump the logcat.

Important: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writing to a file, you need to press ctrl+c.

Logcat step-by-step via SDK

The simplest way is to use an application, like Catlog, but logcats captured this way are not always sufficient. The best way to capture a logcat is:

  • Install the Android SDK (Click Download for other platforms for a minimal download) an light alternative to the huge SDK is the ADB 15 seconds installer.
  • Make sure you can connect to your device via USB (see here for drivers and instructions)
  • Enable AFWall+ logging in the main settings (you can also export it to /sdcard/)
  • Power off your device
  • Start logging by entering this command on the command line: adb logcat >log.txt
  • Power on your device
  • Reproduce the problem
  • Send us the logcat

Upload the captured logcat somewhere, for example using your Google Drive, Dropbox, Pastebin and link to it from the issue you (should) have created or send it directly via email. Don't forget to mention the uid/package name/process name of the application to look into when it's relevant.

Sending bug report

Directly via AFWall+:

  • Copy and/or send the integrated LogCat within AFWall+ (under Firewall Rules/Send error report) via eMail.

On GitHub:

  • Create a new ticket ("New Issues") here on GitHub.
  • Make sure you include Phone Name and Model (ie Samsung Galaxy SII I-9100)
  • Make sure you include version of Android (ie Android 5.1)
  • Make sure you include your problem description. Your problem description should be a step-by-step way to reproduce your problem. Details are very important! Without any information it does not help the developers to find the problem and fix them!
  • Make sure you not use a CM nightly, CM does not allow nightly bug reports because it's unstable and some things may change with upcoming versions.
  • Upload any sample files if necessary (i.e. if AFWall+ crashes when apply your new rules, upload a sample that causes crash - Logcat or it never happened!).
  • You can copy and paste the output to a site like defuse.ca or export them with the copy/export function.

Template for GitHub

This is a small template you can use to provide a useful bug report. Make sure you filled in all nessary information we need. AFWall+ must be running (Green AFWall+ shield activated!), if not we can't say if it's a AFWall+ related problem or something else.

  • AFWall+ Mode (whitelist [default enabled]/blacklist)
  • [your text/file or link]
  • Android ROM + exactly versions number
  • [your text/file or link]
  • What steps will reproduce the problem?
  • [your text/file or link]
  • Additional security software installed (like XPrivacy/Avast)? Is it really deactivated?!
  • [your text/file or link]
  • What is the expected output? What do you see instead?
  • [your text/file or link]
  • Attach your rules.log (IPv4 + IPv6)
  • [your text/file or link]
  • iptables -v -n -L
  • [your text/file or link]
  • ip rule list
  • [your text/file or link]
  • ip route show table (number)
  • [your text/file or link]
  • iptables -L -t mangle (only on VPN)
  • [your text/file or link]
  • Type 'adb bugreport' via ADB (only necessary if there is a crash)
  • [your text/file or link]
  • Please provide any additional information below (e.g. logcat).
  • [your text/file or link]
  • Which binaries are used for BusyBox/IPTables?
  • [your text/file or link]
  • Which DNS-proxy option is in usage?
  • [your text/file or link]
  • Are the experimental options enabled/disabled?!
  • [your text/file or link]
  • On DNS related problems please provide 'adb shell dumpsys connectivity | grep DnsAddresses' + 'nslookup google.com' + 'getprop | grep dns'
  • [your text/file or link]
  • For general connectivity problems please provide 'adb shell dumpsys connectivity'
  • [your text/file or link]

⚠️ More details always means more and faster/better help! ⚠️

After sending the report

  • Be open to work with the developers to help us to resolve your problem. Remember: AFWall+ is free do not expect 24 hours support per day!
  • If you want to donating something to the developer there is also an AFWall+ (Donate) version on Google Play Store. This have exact the same functionality except support to import Droidwall rules.

Custom ROMs

Some custom ROMs come with their own shells and utilities. If you are using a custom ROM, check its documentation to find out what's available and what's not. For security reasons some binary's are not present e.g. on the Guardian ROM.

⚠️ We generally do not support nighty's/alpha's/rc's/beta's ROMs - due the mass of updates we not monitoring all changes that was possible included by them. First try a stable version and see if it works. ⚠️

Useful Links

Footer

Clone this wiki locally