All Projects

Sharing from some apps leads to an error and the impossibility to share the file

No need for description

No need for description

No need for description

It would be better to only use it to start the server

Rare reports, not reproducible, but similar causes.

Example stack trace:

java.lang.RuntimeException: Unable to create service net.outlyer.nettype.MonitorService: java.lang.IllegalArgumentException: contentIntent required: pkg=net.outlyer.nettype id=1 notification=Notification(vibrate=null,sound=null,defaults=0x0,flags=0x2)
	at android.app.ActivityThread.handleCreateService(ActivityThread.java:1974)
	at android.app.ActivityThread.access$2500(ActivityThread.java:121)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:994)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loop(Looper.java:130)
	at android.app.ActivityThread.main(ActivityThread.java:3714)
	at java.lang.reflect.Method.invokeNative(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:507)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:864)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:622)
	at dalvik.system.NativeStart.main(Native Method)
	Caused by: java.lang.IllegalArgumentException: contentIntent required: pkg=net.outlyer.nettype id=1 notification=Notification(vibrate=null,sound=null,defaults=0x0,flags=0x2)
	at android.os.Parcel.readException(Parcel.java:1326)
	at android.os.Parcel.readException(Parcel.java:1276)
	at android.app.INotificationManager$Stub$Proxy.enqueueNotificationWithTag(INotificationManager.java:274)
	at android.app.NotificationManager.notify(NotificationManager.java:111)
	at android.app.NotificationManager.notify(NotificationManager.java:91)
	at net.outlyer.nettype.MonitorService.b(MonitorService.java:201)
	at net.outlyer.nettype.MonitorService.onCreate(MonitorService.java:80)
	at android.app.ActivityThread.handleCreateService(ActivityThread.java:1964)
	... 10 more

Not reproducible. Example stack strace:

java.lang.NullPointerException
	at net.outlyer.nettype.MonitorService.b(MonitorService.java:316)
	at net.outlyer.nettype.MonitorService.a(MonitorService.java:292)
	at net.outlyer.nettype.l.onDataConnectionStateChanged(MonitorService.java:160)
	at android.telephony.PhoneStateListener$2.handleMessage(PhoneStateListener.java:339)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loop(Looper.java:130)
	at android.app.ActivityThread.main(ActivityThread.java:3683)
	at java.lang.reflect.Method.invokeNative(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:507)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:875)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:633)
	at dalvik.system.NativeStart.main(Native Method)

The updated version to return to the Play Store isn’t adapted to the new notification system

Submitted by Adjel

When roaming no network type is indicated.

Device: Nexus 5

NOTE: Not a bug report, misunderstanding on my part

Received reports on newer devices, sync changes from older droids’ branch

Affects new droids and old droids branches.

Has never been reported in the developer console.

This is a meta-item depending on bugs/features required to complete before releasing nettype 1.5.1.

1.5.1 is a hotfix release for issues found during the staged release of 1.5.

Previous:  FS#215  (1.5),  FS#252  (1.4),  FS#203  (1.3)
Next: FS#329 (1.6)

Reported by Sarah Thomasson 15/08/2017 on Google Play:

“The new ‘4’ is missing the triangle in the body of the glyph 4 -.-”

Reported by Andrew 21/8/2017 over email

[...] on my HTC 10 running Marshmallow, it fails to startup on boot.

Lollipop’s new handling of ongoing notifications makes Nettype’s notification to stay on the lockscreen.

Brought up by Andrey Simakov and Theos Greg on Google Play.

Starting with Marshmallow (API level 23, Android 6.0) READ_PHONE_STATE is considered a dangerous permission (and as a result it can be revoked by the user at any time) but at the same time it is no longer required to check connection status.

Should restrict it to old API levels (NOTE the API documentation don’t mention this requirement anymore, but old devices DO require it).