Skip to content
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

[3.20] LineageOS 16: AFWall+ closes on boot, log service failure and empty #1027

Closed
develBuzz opened this issue Oct 20, 2019 · 6 comments
Closed

Comments

@develBuzz
Copy link

develBuzz commented Oct 20, 2019

Currently using:

  • LOS 16 with Security Updates October 2019
  • version 3.20 BETA 2(checked: same error with version 3.20)
  • log service enabled
  • no error if log service is disabled (checked)

If log serice is enabled log file is empty.

Solution: switch back to 3.10, log works as expected. No error on boot.

Log:
10-20 00:36:44.706 E/AndroidRuntime( 2301): FATAL EXCEPTION: main
10-20 00:36:44.706 E/AndroidRuntime( 2301): Process: dev.ukanth.ufirewall, PID: 2301
10-20 00:36:44.706 E/AndroidRuntime( 2301): android.app.RemoteServiceException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{30ad649 u0 dev.ukanth.ufirewall/.service.LogService}
10-20 00:36:44.706 E/AndroidRuntime( 2301): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1745)
10-20 00:36:44.706 E/AndroidRuntime( 2301): at android.os.Handler.dispatchMessage(Handler.java:106)
10-20 00:36:44.706 E/AndroidRuntime( 2301): at android.os.Looper.loop(Looper.java:193)
10-20 00:36:44.706 E/AndroidRuntime( 2301): at android.app.ActivityThread.main(ActivityThread.java:6718)
10-20 00:36:44.706 E/AndroidRuntime( 2301): at java.lang.reflect.Method.invoke(Native Method)
10-20 00:36:44.706 E/AndroidRuntime( 2301): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
10-20 00:36:44.706 E/AndroidRuntime( 2301): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

@develBuzz develBuzz changed the title AFWAll+ close on startup- 2nd start ok AFWall+ close on boot, log service failure - restart ok Oct 20, 2019
@develBuzz develBuzz changed the title AFWall+ close on boot, log service failure - restart ok AFWall+ closes on boot, log service failure - restart ok Oct 20, 2019
@develBuzz develBuzz changed the title AFWall+ closes on boot, log service failure - restart ok [3.20] LineageOS: AFWall+ closes on boot, log service failure Oct 20, 2019
@develBuzz develBuzz changed the title [3.20] LineageOS: AFWall+ closes on boot, log service failure [3.20] LineageOS 16: AFWall+ closes on boot, log service failure Oct 20, 2019
@develBuzz develBuzz changed the title [3.20] LineageOS 16: AFWall+ closes on boot, log service failure [3.20] LineageOS 16: AFWall+ closes on boot, log service failure and empty Oct 20, 2019
@jw243
Copy link

jw243 commented Oct 25, 2019

Same problem here. In version 3.2.0 (donate version), log service does not work. Log protocoll is always empty.

@ukanth
Copy link
Owner

ukanth commented Nov 13, 2019

@desmonk
Copy link

desmonk commented Nov 13, 2019

Please check this version.
https://www.dropbox.com/s/p9ibfqxrasgs158/AFWall%2B_3.3.0-Test.apk?dl=0

On the same boat. Tested 3.3.0. Log still empty. Able to start at boot. But while enabling Startup data leak, got no confirmation toast. Speed is a bit slow than before on boot as well.

@ukanth
Copy link
Owner

ukanth commented Nov 14, 2019

Please provide logcat along with firewall rules. Otherwise I can't fix the problem.

@ukanth
Copy link
Owner

ukanth commented Nov 15, 2019

Fixed in 3.3.0. Closing.

@ukanth ukanth closed this as completed Nov 15, 2019
@develBuzz
Copy link
Author

Ty, it is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants