daimajia / daimajia/droidwall

Rules do not get applied reliably on startup

Open
#262 0 comments 0 reactions 0 assignees View on GitHub
auto-migrated Priority-Medium Type-Defect
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

```
1. Boot the phone
2. DroidWall -> Show rules (empty/stock chains)

It's a 50/50 chance the rules will be applied by droidwall at system startup.
Sometimes they are applied, sometimes not.
I've found at least one more user in market comments that described exactly the
same issue.

If i'll find something useful in logcat i will add it.

Droidwall v1.5.7
Android 2.3.7 CM7.2 (final)
Huawei U8510 (ARMv6/MSM7227/MDPI/HVGA)

```

Original issue reported on code.google.com by `Ris...@gmail.com` on 1 Jul 2012 at 6:08

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the startup behavior on the listed Android 2.3.7 and DroidWall v1.5.7 environment, then inspect logcat during boot and rule application. The issue mentions no source files or tests; done means rules are reliably applied at system startup rather than leaving empty or stock chains.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.