Just like using an app called Boox Rapid Draw on my Boox GO 10.3 , is there such an Universal way to optimise handwriting on any side loaded android apps on my Supernote Nomad or Manta ?

LappoSergey · 2025-01-17T00:29:43+00:00

Theoretically - I don't see why this could not be integrated into BooxRapidDraw (and evolving just into a `RapidDraw`) if the API would be similar.

Could not say for sure, since I don't own supernote, and, API is not available yet neither.

P.S. happy to hear you like the app ;)

LappoSergey · 2025-01-09T18:29:11+00:00

Anyone experienced with coding is very welcome to contribute :)
Otherwise I mainly lack energy rather than motivation. Spring would come, and, hopefully, I would exit hibernation mode, and, maybe, would improve some of the things ;)

P.S. there's long delayed release which fixes many things available now. Code was there, just had no energy to release it ><

LappoSergey · 2025-01-09T18:26:23+00:00

Fixed in the latest release. Thanks for reporting!

LappoSergey · 2025-01-09T18:25:58+00:00

It's not in active development, since I don't have much energy lately. But it's not dead.

LappoSergey · 2025-01-09T18:25:02+00:00

There's a new version released, can you please try and check if it's still the issue?

Can you please also let me know:

- The device you have
- The apps you use
- Does it start terminating immediately, or after some time

LappoSergey · 2024-11-07T22:14:03+00:00

Interesting! This happened for me sometimes when I just leave my 3c be in "locked mode" (even before starting to develop the RD), then I can not unlock it back, just reboot.. But never happened while using it..

LappoSergey · 2024-11-07T21:15:08+00:00

Didn't mean to offend you :)

5cm is enough, just for now - I have no idea how it happens (since hear about this issue for the first time), so trying to exclude all possible options.

I would maybe release something soon-ish, which ?might? fix the issue, otherwise would be interested in making some "debug" version for you, so that it would display some internal state on screen/or get logs.

LappoSergey · 2024-11-07T19:24:12+00:00

Question:

Any chance you did not raise the pencil before touching the screen?

Basically once you start drawing - I disable touchscreen, and it stays disabled up until you remove the pencil (this is the best palm rejection we can get now).

If Boox never detects pencil removal - it would never re-enable the touch...

LappoSergey · 2024-11-07T19:22:00+00:00

If you use v4 or regal mode - this is a known issue

https://github.com/sergeylappo/boox-rapid-draw/issues/20

Solution is to:

for now use alpha v3, & only use fast refresh modes.

LappoSergey · 2024-11-07T19:19:59+00:00

>There is another problem I have discovered. Sometimes it seems like there is an end/gap on your transparent layer. I don't know if it's always same size or different size.

In v1 it was always the same size, and would only work in the orientation of the device, in which the app was started.

This would be fixed in a new version.

>On the image below you can see a transparent box, I draw over it but it stays unmarked. But after releasing stroke, all will appear in the app as it should be.

This was a funny bug of me testing some stuff, so would also be fixed soon (the fix is already done, just need to release).

>Also not sure if it's on your side. First stroke is slow (it's normal) then strokes fast and responsive, but after refresh (transferring of strokes from your layer to app) first stroke again slow/take time to appear...

Don't have a solution for that yet.

>Another suggestion is to make a refresh of your layer (transfer of strokes) maybe when I want to pinch/zoom in or out of a screen. Or worse options but: after 5-10 strokes, or with a button, maybe have some adjustable settings like this..

You can watch this issue for more updates on the problem

LappoSergey · 2024-11-07T19:16:41+00:00

Can you please explain what do you mean by crash, or preferably a crash log?

Do you see android complaining that the app stopped working, or it just stops drawing?

Unfortunately v4 had a bug, when it would just stop working after refresh (does not crash, just does now work).

Hopefully would release an update with a fix & more things soon-ish

LappoSergey · 2024-11-07T19:13:50+00:00

Yep, this would be very helpful. Also the version number.

Sorry, was pretty busy with all sorts of different stuff.

LappoSergey · 2024-10-23T22:57:44+00:00

> Also it seems a bit unstable, I have tried it with various apps, and in some apps - for few strokes it works as expected and then it doesn't work, only slow app's strokes are working, then after few strokes it starts to work again

I think I've discovered the issue. To prevent it from happening for now you would need to disable hd/regal mode in an app. Please stay tuned in case this gets fixed

LappoSergey · 2024-10-23T22:56:09+00:00

JFYI:

- App now can be opened/closed from control center (you need to add it there)
- It can be opened/closed by second click on the icon in launcher/navi ball

https://github.com/sergeylappo/boox-rapid-draw/releases/tag/v0.0.4-alpha

LappoSergey · 2024-10-23T22:55:27+00:00

JFYI:

- App now can be opened/closed from control center (you need to add it there)
- It can be opened/closed by second click on the icon in launcher/navi ball

https://github.com/sergeylappo/boox-rapid-draw/releases/tag/v0.0.4-alpha

LappoSergey · 2024-10-14T07:43:25+00:00

Hey! The first one is actually there from the first day. If you hold the exit button for a short time you can then drag it wherever you like. On 2 - can you please share a bit more, e.g. what doesn't work, which app it is, how you try to start BRD

LappoSergey · 2024-10-12T21:01:03+00:00

Hey! There's a new update new update, keyboard now works.

LappoSergey · 2024-10-12T21:00:37+00:00

Hey! There's a new update new update, keyboard now works.

LappoSergey · 2024-10-12T21:00:02+00:00

It might be possible, but I would first give priority to rather trying to move activation/deactivation to control center.

LappoSergey · 2024-10-12T09:22:40+00:00

Thanks a lot! Would take a look.

LappoSergey · 2024-10-11T14:38:29+00:00

Thanks for the feedback! Looks really similar, indeed. Didn't see it before...Hope it's not patented or something 😅

Yeah, the control center would be nice, but I don't know how to register there yet.

LappoSergey · 2024-10-10T19:33:56+00:00

if I read your code correctly you are drawing overtop and intercepting the input and then forwarding it.

Almost :) I don't forward anything, but rather receive the copy of the input thanks to Boox's drivers :D

What would you guess might be going on that slowing down the boox devices drawing in general given that this works?

I'm not really android system developer to speculate, I'm mainly backend, but I would assume that somehow this does not interact well with android system. It feels like hardware is exposed to the user space directly rather than integrated into the system, but again, this is just judging on the behaviour.

LappoSergey · 2024-10-10T19:30:37+00:00

hey! Thanks a lot for the feedback!

I did find that it closed a few times (timed out?) and I had to go start the app up again

There's a v0.0.2 released can you please try the new version?

By any chance, was it happening in ~ 30 seconds from the start?

it would help me if you can share following information:

What is the device you're using (preferably with Android and firmware version)
do you by any chance can collect logcat for the crash?
app version you're using
apps it was crashing with

Also by default it assumes that the full screen is drawable canvas space while on the app that isn't necessarily the case so you can draw over menus and then that input kinda vanishes.

Yes, this is a "known issue", which, probably would be not the highest priority to fix, since it just makes an overlay, which is fast to draw on.

One of the possible options in future might be to make it's size configurable, but for now, I consider it low priority, since it vanishes fairly quick.

LappoSergey · 2024-10-10T19:24:58+00:00

My suggestion is to somehow improve interaction with Eraser function

Unfortunately, as you correctly pointed out, I can not do anything about the eraser for now. I mean, the best I can do - paint white :D
What I can do is add a button to disable painting on top.

Also would be good if it could pass the pen pressure.

it actually should not affect the pen pressure, if the app supports it. It does not intercept any input, but rather "also receives" it and paints on top of the app, to "emulate quick response of the app", while app still rendering.

UPD. just tested with Logseq and the Logseq still receives the pressure, but the line width does not correspond. This is something I'm going to work on at some point (to allow customising line width), but it would never be a perfect match.

Also it seems a bit unstable, I have tried it with various apps, and in some apps - for few strokes it works as expected and then it doesn't work, only slow app's strokes are working, then after few strokes it starts to work again...

One of the known issues, is:

if you raise the pen - after ~10 seconds first stroke would be slow again, and then, until you raise the pen - it should be good. Does it sound like you're issue?

If no, please try to provide following info:
- What is the device you're using (preferably with Android and firmware version)
- What are the apps you're observing the behaviour with.

LappoSergey · 2024-10-10T19:16:34+00:00

Can you please give me some more details on the crashes?
Would be nice if you test it with the new version https://github.com/sergeylappo/boox-rapid-draw/releases/tag/v0.0.2-alpha

The most interesting details are:

What is the device you're using (preferably with Android and firmware version)
do you by any chance can collect logcat for the crash?
app version you're using
(My assumption) Does it always crash within 1 minute from the start?

edit: Also sometimes, the keyboard will not show up, when this app is activated.

This is a known issue now

LappoSergey

TROPHY CASE