dixonary / draft-remarkable Goto Github PK

On the reMarkable 2
Using rm2fb per ddvk/remarkable2-framebuffer#35

Touchinput and starting apps etc works great, however the pen doesn't seem to be recognized at all as an input device.

In an effort to make projects for the reMarkable tablet easier to find on GitHub, a common topic named remarkable-tablet has been established (See reHackable/awesome-reMarkable#1).

It would be awesome if you could tag this project with the remarkable-tablet topic.

There's more info on Classifying your repository with topics available in the GitHub help.

A list of already tagged projects can be found here: Projects in Topic remarkable-tablet.

After updating to 2.6.2.75, the following types of problems appear when launching draft:

parsing file 01-xochitl
file:///usr/share/draft/qml/MenuItem.qml:15: TypeError: Cannot read property 'right' of null
file:///usr/share/draft/qml/MenuItem.qml:14: TypeError: Cannot read property 'left' of null
Creating window
...

How about a prepackaged build? It would save people a lot of effort.

Originally posted by @Evidlo in #3 (comment)

@Evidlo is correct! A binary build will be forthcoming the next time Draft is built by me (and possibly with new features? We'll see!)

I would recommend subscribing to this issue if you want to know when that is done.

Hi! When I run draft.pro in Qt Creator, I get the following error:
The remote file system has only 0 megabytes of free space, but 5 megabytes are required

Running df -h of my reMarkable gives me the following:

root@remarkable:/# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root               213.5M    209.5M         0 100% /
devtmpfs                 88.6M         0     88.6M   0% /dev
tmpfs                   249.1M         0    249.1M   0% /dev/shm
tmpfs                   249.1M      8.4M    240.7M   3% /run
tmpfs                   249.1M         0    249.1M   0% /sys/fs/cgroup
tmpfs                   249.1M      4.0K    249.1M   0% /tmp
tmpfs                   249.1M         0    249.1M   0% /var/volatile
/dev/mmcblk1p7            6.5G    690.1M      5.5G  11% /home
/dev/mmcblk1p1           19.0M      3.7M     15.3M  19% /var/lib/uboot

I've noticed that a couple other folks have reported this issue, but I haven't seen any solutions for it yet. Maybe it's a more recent issue having to do with the latest 1.8 rM update?

Any options or help are appreciated. Curious to hear if anyone else has encountered this or what running a df -h on your rM looks like...

Thanks!

As xochitl is disabled and draft enabled at startup, then the Wifi stack is not running !

If I launch Wikipedia (for example), nothing work because it is not able to fetch data, the wifi is not started.

If I launch first xochitl (from draft launcher) then quit (using Menu -> Settings -> Restart), as codex is still running the Wifi stay active, then launch of Wikipedia will be able to fetch data from the web.

Any workaround ? A way to start the Wifi stack from Draft launcher ?

This is how to reproduce:

• Installed qtcreator in arch linux (version 4.9.3)
• Git clone this repo
• Open file pointing to draft.pro
• Project gets loaded, I click on the green arrow on the left bottom side
• This error shows up:

I've installed draft on my reMarkable running version 2.0.2.0 and whenever I turn on the device, all I see is a white screen. I'm still able to press the buttons in the launcher, I can even see a faint outline of them because the display haven't done a full update, and everything works fine if I use button-capture-reMarkable to exit xochitl, but on the initial boot, the launcher is completely blank.

Let me know if I can provide anything to help solving this problem. Thanks!

Please add a license, so other developers know what they are allowed to do with it.
Preferable MIT license

Can we add an automatic power-off for the draft?

Now, when xochitl automatic power-off, it goes to draft, which will not power off. Therefore, it wastes energy and looks bad.

I know reMarkable 2 is bleeding edge. draft (and my own apps) built against the reMarkable 1 toolchain fail to render the UI and this error comes out on stderr:

Creating window
Framebuffer has wrong id: "mxs-lcdif"

I'm mostly sharing so folks know and to see if anyone in the broader community has made more progress with rm v2. I intend to poke around more at the weekend and would love to help with any effort to get rm v2 working.

Hello! I'm not new to compiling software, but I am new to QtCreator, and how to set it up for sending software to the reMarkable.

More detailed instructions would be greatly appreciated!

When Xochitl is first in sleep mode, and then turns off, the ReMarkable does not turn off, but goes back to the Draft Launcher.

This has a big implication for battery life, since it is then slowly draining.

I'm not sure there is an easy way to check if Xochitl wanted to turn the system off, but maybe it is possible to check the same configuration file from Draft to see if more than X minutes have passed, and if so, execute the shutdown handler?

When there are more than 7 apps in the config folder, the list overflows and there does not seem to be a way to scroll it.

Replication steps for the issue:

• Install Draft from opkg
• Install Keywriter form opkg
• Configure Draft to launch Keywriter
• Go into Keywriter
• Can't get back to the Draft launcher, tried tapping on each corner and each button in read and write Keywriter mode

Suggested options:
Similarly to Remux and Oxide add a default button capture event, so on one of the button presses the user can get back to the Draft launcher.

Thanks for the consideration.

~/draft-reMarkable$ arm-remarkable-linux-gnueabi-g++  -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a9 --sysroot=/opt/codex/rm10x/3.1.15/sysroots/cortexa9hf-neon-remarkable-linux-gnueabi -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed --sysroot=/opt/codex/rm10x/3.1.15/sysroots/cortexa9hf-neon-remarkable-linux-gnueabi -Wl,-O1 -o draft main.o mainview.o options.o handler.o moc_handler.o   -lqsgepaper /opt/codex/rm10x/3.1.15/sysroots/cortexa9hf-neon-remarkable-linux-gnueabi/usr/lib/libQt5Quick.so /opt/codex/rm10x/3.1.15/sysroots/cortexa9hf-neon-remarkable-linux-gnueabi/usr/lib/libQt5Gui.so /opt/codex/rm10x/3.1.15/sysroots/cortexa9hf-neon-remarkable-linux-gnueabi/usr/lib/libQt5QmlModels.so /opt/codex/rm10x/3.1.15/sysroots/cortexa9hf-neon-remarkable-linux-gnueabi/usr/lib/libQt5Qml.so /opt/codex/rm10x/3.1.15/sysroots/cortexa9hf-neon-remarkable-linux-gnueabi/usr/lib/libQt5Network.so /opt/codex/rm10x/3.1.15/sysroots/cortexa9hf-neon-remarkable-linux-gnueabi/usr/lib/libQt5Core.so -lpthread
/opt/codex/rm10x/3.1.15/sysroots/x86_64-codexsdk-linux/usr/libexec/arm-remarkable-linux-gnueabi/gcc/arm-remarkable-linux-gnueabi/9.3.0/real-ld: cannot find -lqsgepaper
collect2: error: ld returned 1 exit status

how to solve it?

In the second git clone it says dixionary instead of dixonary.

I configured Draft to launch Plato, but there seems to be a problem where Draft is receiving touch inputs and drawing over Plato.

Might it be possible to kill Draft and relaunch it when the launched application quits?

https://remarkable.engineering/oecore-x86_64-cortexa9hf-neon-toolchain-zero-gravitas-1.8-23.9.2019.sh

I installed draft through toltec with opkg install draft. After downloading and installing, I was prompted to disable the xochitl launcher, and switch to draft with:

systemctl disable --now xochitl
systemctl enable --now draft

I then rebooted the device with reboot now, but the device is failing to launch. It is perpetually stuck on the "reMarkable is starting" screen.

According to #31, WiFi doesn't start until xochitl does, so I can't access with SSH in order to disable draft and reenable xochitl.

Is there anything I can do here to recover the device?

I am using an experimental build of ReMarkable 2 frame buffer from the Toltec repository. All functions seem to be working properly for Tarnish and KoReader. However the time required to register a touch input on the app switcher and FingerTerm appears to be approximately 0.75 seconds. Close to the “long press” threshold.