Note app isn't responsive


#1

The Note app opens normally, but if I tap on the + button to start new Note, nothing happens. The app doesn’t do anything! any work around?


#2

the note app requires that you use the stylus, it doesn’t respond to touch. Is that the problem you are running into?


#3

I do use the stylus. It is not responsive regardless


#4

Hello, could you try to reboot your device and try again? And please provide a picture or video to us if it still could not work.


#5

Hi Clair, rebooting didn’t help. And the forum software here doesn’t allow attaching video, how can i send you the video?


#6

Hello, in this case, you are suggested to submit this on Feedback via Settings/Feedback, and our relative colleagues will reply back as soon as possible.


#7

This is might be useful as well. Getting the logs from adb logcat shows NullPointerException when I tap on the new note button
05-23 08:14:03.020 4042 4171 E ActivityThread: Failed to find provider info for com.onyx.android.sdk.note.ContentProvider
05-23 08:14:03.021 4042 4171 W System.err: java.lang.NullPointerException: Attempt to invoke interface method ‘void android.database.Cursor.close()’ on a null object reference
05-23 08:14:03.021 4042 4171 W System.err: at android.database.CursorWrapper.close(CursorWrapper.java:50)
05-23 08:14:03.021 4042 4171 W System.err: at com.raizlabs.android.dbflow.sql.queriable.ModelLoader.load(SourceFile:74)
05-23 08:14:03.021 4042 4171 W System.err: at com.raizlabs.android.dbflow.sql.queriable.ListModelLoader.load(SourceFile:61)
05-23 08:14:03.021 4042 4171 W System.err: at com.raizlabs.android.dbflow.sql.queriable.ListModelLoader.load(SourceFile:15)
05-23 08:14:03.021 4042 4171 W System.err: at com.raizlabs.android.dbflow.sql.queriable.ModelLoader.load(SourceFile:65)
05-23 08:14:03.021 4042 4171 W System.err: at com.raizlabs.android.dbflow.sql.queriable.ListModelLoader.load(SourceFile:50)
05-23 08:14:03.021 4042 4171 W System.err: at com.raizlabs.android.dbflow.structure.provider.ContentUtils.queryList(SourceFile:255)
05-23 08:14:03.021 4042 4171 W System.err: at com.raizlabs.android.dbflow.structure.provider.ContentUtils.queryList(SourceFile:231)
05-23 08:14:03.021 4042 4171 W System.err: at com.onyx.android.sdk.scribble.provider.RemoteNoteProvider.loadAllNoteList(SourceFile:117)
05-23 08:14:03.021 4042 4171 W System.err: at com.onyx.android.sdk.note.ui.library.request.LibraryTitleRequest.execute(SourceFile:29)
05-23 08:14:03.021 4042 4171 W System.err: at com.onyx.android.sdk.rx.RxManager$1.a(SourceFile:122)
05-23 08:14:03.021 4042 4171 W System.err: at com.onyx.android.sdk.rx.RxManager$1.call(SourceFile:117)
05-23 08:14:03.021 4042 4171 W System.err: at io.reactivex.internal.operators.observable.ObservableFromCallable.subscribeActual(SourceFile:42)
05-23 08:14:03.021 4042 4171 W System.err: at io.reactivex.Observable.subscribe(SourceFile:12025)
05-23 08:14:03.021 4042 4171 W System.err: at io.reactivex.internal.operators.observable.ObservableSubscribeOn$b.run(SourceFile:96)
05-23 08:14:03.021 4042 4171 W System.err: at io.reactivex.internal.schedulers.ScheduledDirectTask.call(SourceFile:38)
05-23 08:14:03.021 4042 4171 W System.err: at io.reactivex.internal.schedulers.ScheduledDirectTask.call(SourceFile:26)
05-23 08:14:03.021 4042 4171 W System.err: at java.util.concurrent.FutureTask.run(FutureTask.java:237)
05-23 08:14:03.021 4042 4171 W System.err: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
05-23 08:14:03.021 4042 4171 W System.err: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
05-23 08:14:03.021 4042 4171 W System.err: at java.lang.Thread.run(Thread.java:818)


#8

Even submitting feedback is broken and throwing the exception
java.net.SocketTimeoutException: timeout
05-23 08:17:17.098 4042 4714 W System.err: at okio.Okio$4.newTimeoutException(SourceFile:232)
05-23 08:17:17.098 4042 4714 W System.err: at okio.AsyncTimeout.a(SourceFile:285)
05-23 08:17:17.099 4042 4714 W System.err: at okio.AsyncTimeout$1.write(SourceFile:184)
05-23 08:17:17.099 4042 4714 W System.err: at okio.b.flush(SourceFile:224)
05-23 08:17:17.099 4042 4714 W System.err: at okhttp3.internal.http1.Http1Codec$d.flush(SourceFile:301)
05-23 08:17:17.099 4042 4714 W System.err: at okio.ForwardingSink.flush(SourceFile:39)
05-23 08:17:17.100 4042 4714 W System.err: at okio.b.flush(SourceFile:226)
05-23 08:17:17.100 4042 4714 W System.err: at com.alibaba.sdk.android.oss.network.OSSRequestTask$ProgressTouchableRequestBody.writeTo(SourceFile:124)
05-23 08:17:17.100 4042 4714 W System.err: at okhttp3.internal.http.CallServerInterceptor.intercept(SourceFile:72)
05-23 08:17:17.100 4042 4714 W System.err: at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:147)
05-23 08:17:17.101 4042 4714 W System.err: at okhttp3.internal.connection.ConnectInterceptor.intercept(SourceFile:45)
05-23 08:17:17.101 4042 4714 W System.err: at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:147)
05-23 08:17:17.101 4042 4714 W System.err: at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:121)
05-23 08:17:17.101 4042 4714 W System.err: at okhttp3.internal.cache.CacheInterceptor.intercept(SourceFile:93)
05-23 08:17:17.102 4042 4714 W System.err: at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:147)
05-23 08:17:17.102 4042 4714 W System.err: at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:121)
05-23 08:17:17.102 4042 4714 W System.err: at okhttp3.internal.http.BridgeInterceptor.intercept(SourceFile:93)
05-23 08:17:17.102 4042 4714 W System.err: at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:147)
05-23 08:17:17.102 4042 4714 W System.err: at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(SourceFile:126)
05-23 08:17:17.102 4042 4714 W System.err: at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:147)
05-23 08:17:17.102 4042 4714 W System.err: at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:121)
05-23 08:17:17.103 4042 4714 W System.err: at okhttp3.a.e(SourceFile:200)
05-23 08:17:17.103 4042 4714 W System.err: at okhttp3.a.execute(SourceFile:77)
05-23 08:17:17.103 4042 4714 W System.err: at com.alibaba.sdk.android.oss.network.OSSRequestTask.call(SourceFile:227)
05-23 08:17:17.103 4042 4714 W System.err: at com.alibaba.sdk.android.oss.network.OSSRequestTask.call(SourceFile:44)
05-23 08:17:17.106 4042 4714 W System.err: at java.util.concurrent.FutureTask.run(FutureTask.java:237)
05-23 08:17:17.107 4042 4714 W System.err: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
05-23 08:17:17.107 4042 4714 W System.err: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
05-23 08:17:17.107 4042 4714 W System.err: at java.lang.Thread.run(Thread.java:818)
05-23 08:17:17.107 4042 4714 W System.err: Caused by: java.net.SocketException: Socket closed
05-23 08:17:17.110 4042 4714 W System.err: at libcore.io.Posix.sendtoBytes(Native Method)
05-23 08:17:17.110 4042 4714 W System.err: at libcore.io.Posix.sendto(Posix.java:211)
05-23 08:17:17.111 4042 4714 W System.err: at libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:278)
05-23 08:17:17.111 4042 4714 W System.err: at libcore.io.IoBridge.sendto(IoBridge.java:509)
05-23 08:17:17.111 4042 4714 W System.err: at java.net.PlainSocketImpl.write(PlainSocketImpl.java:500)
05-23 08:17:17.112 4042 4714 W System.err: at java.net.PlainSocketImpl.-wrap1(PlainSocketImpl.java)
05-23 08:17:17.112 4042 4714 W System.err: at java.net.PlainSocketImpl$PlainSocketOutputStream.write(PlainSocketImpl.java:266)
05-23 08:17:17.112 4042 4714 W System.err: at okio.Okio$1.write(SourceFile:79)
05-23 08:17:17.112 4042 4714 W System.err: at okio.AsyncTimeout$1.write(SourceFile:180)


#9

I think this makes it clear that there is a bug in the app
System.err: java.lang.NullPointerException: Attempt to invoke interface method ‘void android.database.Cursor.close()’ on a null object reference

But I have no access to any source code to fix it on my own, and Boox provides no means to update individual apps OTA. What can be the solution?


#10

I ended up doing factory reset to get it to work


#11

It is glad to hear that and we have forwarded that to our relative colleagues to follow up.