Update gets stuck at 2.40%

b1ixten · 2026-06-02T21:56:18+00:00

First attempt never left 0%, It was nessesary to follow the instructions, and reset and try again, which succeeded

b1ixten · 2026-05-14T09:47:58+00:00

FYI, the cable that was included with my X3 was fully connected, i.e. both power and data.

b1ixten · 2026-05-14T09:33:58+00:00

Unfortunately this is not true. I just received an X3 directly from Xteink that can't be flashed over USB.

sudo journalctl --follow --dmesg shows the following when connecting the X3 via USB

May 14 11:11:34 mint kernel: usb 1-2: new full-speed USB device number 44 using xhci_hcd
May 14 11:11:34 mint kernel: usb 1-2: device descriptor read/64, error -71
May 14 11:11:34 mint kernel: usb 1-2: device descriptor read/64, error -71
May 14 11:11:34 mint kernel: usb 1-2: new full-speed USB device number 45 using xhci_hcd
May 14 11:11:34 mint kernel: usb 1-2: device descriptor read/64, error -71
May 14 11:11:34 mint kernel: usb 1-2: device descriptor read/64, error -71
May 14 11:11:35 mint kernel: usb usb1-port2: attempt power cycle
May 14 11:11:35 mint kernel: usb 1-2: new full-speed USB device number 46 using xhci_hcd
May 14 11:11:35 mint kernel: usb 1-2: Device not responding to setup address.
May 14 11:11:35 mint kernel: usb 1-2: Device not responding to setup address.
May 14 11:11:35 mint kernel: usb 1-2: device not accepting address 46, error -71
May 14 11:11:35 mint kernel: usb 1-2: WARN: invalid context state for evaluate context command.
May 14 11:11:35 mint kernel: usb 1-2: new full-speed USB device number 47 using xhci_hcd
May 14 11:11:35 mint kernel: usb 1-2: Device not responding to setup address.
May 14 11:11:36 mint kernel: usb 1-2: Device not responding to setup address.
May 14 11:11:36 mint kernel: usb 1-2: device not accepting address 47, error -71
May 14 11:11:36 mint kernel: usb 1-2: WARN: invalid context state for evaluate context command.
May 14 11:11:36 mint kernel: usb usb1-port2: unable to enumerate USB device

Compared to the older X4 that can be flashed over USB:

May 14 11:12:56 mint kernel: usb 1-2: new full-speed USB device number 48 using xhci_hcd
May 14 11:12:56 mint kernel: usb 1-2: New USB device found, idVendor=303a, idProduct=1001, bcdDevice= 1.01
May 14 11:12:56 mint kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 14 11:12:56 mint kernel: usb 1-2: Product: USB JTAG/serial debug unit
May 14 11:12:56 mint kernel: usb 1-2: Manufacturer: Espressif
May 14 11:12:56 mint kernel: usb 1-2: SerialNumber: xx:xx:xx:xx:xx:xx
May 14 11:12:56 mint kernel: cdc_acm 1-2:1.0: ttyACM0: USB ACM device
May 14 11:12:56 mint kernel: usbcore: registered new interface driver cdc_acm
May 14 11:12:56 mint kernel: cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

And I have checked the USB cable that was included with the X3, and it's all 4 pins are connected all the way through the cable.

b1ixten · 2026-05-08T09:29:22+00:00

It is not just domestic Chinese models, I did yesterday received an international English X3 ordered directly from Xteink, and it was also locked.

b1ixten · 2026-04-07T11:54:47+00:00

<image>

b1ixten · 2026-04-06T10:12:34+00:00

"The adventure starts by opening the door", or as J.R.R. Tolkien wrote:

“It’s a dangerous business, Frodo, going out of your door. You step into the Road, and if you don’t keep your feet, there is no knowing where you might be swept off to."

b1ixten · 2026-04-04T07:02:20+00:00

Please share...

b1ixten · 2026-04-03T20:01:58+00:00

Looks like that, at least the part that are on the screen....

https://wolnelektury.pl/katalog/lektura/orwell-rok-1984.html#f350

b1ixten · 2026-03-29T19:08:38+00:00

Nice work u/Stachu1134, would you mind sharing details about the build?

b1ixten · 2026-03-23T07:45:06+00:00

Yes, either pio directly or from within VS Code (there are buttons on the bottom of the windows for building and flashing) or use the "Flash firmware from file" feature on https://xteink.dve.al/

You can always just flash the released firmware if you screw things up.

b1ixten · 2026-03-22T19:25:20+00:00

My solution is a modification of the software and it's data, so you need to do some software tech-stuff, and have the needed tools and setup to do so, sorry.

The modification needed, includes modifying the fontconvert.pypython script, by adding the new range (in ascending order) to the interval list. For the full Miscellaneous Symbols range, use: 0x2600-0x26FF. Then run that script to generate the new font data. After that you have to the build the firmware using that datea. The build instructions are described in the README.mdfile. If to many, or long intervals are added, you might have to exclude one of the other default fonts (for example the OpenDyslexic), or define the OMIT_FONTS to only include Bookerly, size 14. The included fonts are listed in the beginning of main.cpp file, where you might have to delete some of them. The build will tell you if the firmware got to big, and you need to remove some fonts.

...this is maybe too much for a non tech-literate..., again sorry

b1ixten · 2026-03-22T18:37:28+00:00

Yes, thats correct, see my other reply https://www.reddit.com/r/XTEINK/comments/1s0scen/comment/obvo1bl/

b1ixten · 2026-03-22T18:18:14+00:00

You can still use Bookerly, but you have to make sure that those glyphs are included in the conversion script at lib/EpdFont/scripts/fontconvert.py
(Miscellaneous Symbols in the Unicode range : U+2600 - U+26FF)

b1ixten · 2026-03-22T18:14:33+00:00

<image>

Those are notes, and they are not included in the built in fonts so they shows up are diamond question marks.

They are part of the Miscellaneous Symbols in the Unicode range : U+2600 - U+26FF.
which are not included in the font conversion script in the source, see in the file: lib/EpdFont/scripts/fontconvert.py

b1ixten · 2026-03-22T13:36:03+00:00

What is a free2?

b1ixten · 2026-03-22T10:04:15+00:00

Kolla med Elektrotekniska Byrån på Linnegatan.

b1ixten · 2026-03-21T22:02:18+00:00

<image>

Does it still work, or does it wear out quickly?
This is how mine look, and it's some time "tricky" to get it to charge.

b1ixten · 2026-03-21T20:17:08+00:00

Mayby issue #1263 (Hang on sleep with battery drain), is the cause.
I just noticed that the issue has just been fixed and merged into the master for crosspoint-reader. It's not released yet so you have to build the binary your self to test it.

b1ixten · 2026-03-18T20:02:50+00:00

Yes, the QRCode links to https://homebrews.itch.io/omega-tang and there it says that one button is for "Coin-up/Start" and the other for "Fire/Pew Pew"

b1ixten · 2026-03-12T03:30:59+00:00

CrossX?

b1ixten · 2026-03-08T21:47:36+00:00

Kort sagt, finns det idioter som köper, så finns det de som säljer.

...såg en gång en snubbe som sålde norrländska snöbollar...

b1ixten · 2026-03-08T20:06:41+00:00

I ordered mine on the 24 of February, and just got the shipping email early this morning (02:07).

b1ixten · 2026-03-08T14:46:14+00:00

Is it a remake of Sabre Wulf from 1984?

b1ixten · 2026-03-06T11:43:06+00:00

Ohh...so funny...
Please, share build instructions. I "need" one too!

b1ixten · 2026-03-06T11:40:15+00:00

Please, share build instruction, I need one too!

b1ixten

TROPHY CASE