Elipsa New Kobo (N604) [Elipsa - ed.]

[ottischwenk]

Originally Posted by davidfor

So, being bought out by Kobo made the same developers dumb.

The Kobo Developerso of course - everything was fine before the takeover.
Kobo tried the Android update, which did not succeed and which broke a lot of devices.
Devices with exchangeable SD could be saved, others that had gone through this update had to be replaced.

As of now, I will be careful not to warn Kobo fanatics about the anything but high-quality engineering of this company's products.

[Pjama]

Originally Posted by rantanplan

He can disrupt the forum because everyone chimes in instead of leaving him alone or ignore him. You're all enablers.

That’s right, it’s my fault. Nothing to do with ottoschwenck, nope nope, nope. Damn, it’s always my fault, just like real life.

[Pjama]

And, FWIW, I would have ignored him, but it was just becoming increasingly impossible. Every time I visit my blood pressure rises. In fact, it seems I’ve been ignoring him for 52
PAGES!!!

I’m sure there are many many people like myself that read his garbage and just decide not to post on this, previously interesting and uplifting thread. So, in the end, all that’s left is the to and fro. It’s a shame, as davidfor's posts are very interesting, and yet he gets shouted down all the time. Why is this happening?

[Uncle Robin]

Originally Posted by rantanplan

He can disrupt the forum because everyone chimes in instead of leaving him alone or ignore him. You're all enablers.

All generalizations are dangerous, including this one. Everyone doesn't chime in, and to say "you're all enablers" is both factually wrong and insulting to those who choose not engage with the person in question - I won't make pronominal assumptions about their gender.

[Pjama]

Originally Posted by Uncle Robin

All generalizations are dangerous, including this one. Everyone doesn't chime in, and to say "you're all enablers" is both factually wrong and insulting to those who choose not engage with the person in question - I won't make pronominal assumptions about their gender.

Yeah, nevermind on the Internet everyone is a dog, on the Internet everyone is assumed to be a guy. It’s pathetic.

Anxiously awaiting mansplaining. 3, 2, 1.

And, I guess this was ottoschwenck's ultimate aim, so, congratulations to you!

[davidfor]

Originally Posted by ottischwenk

The Kobo Developerso of course - everything was fine before the takeover.
Kobo tried the Android update, which did not succeed and which broke a lot of devices.
Devices with exchangeable SD could be saved, others that had gone through this update had to be replaced.

So you believe that when Kobo took over tolino, that they sacked the tolino developers and put together a whole new team to further develop the tolino software. Seriously? Do you have proof of this?

But, it is good to see you are holding true to form. You picked the least important thing in the post to comment on. And refuse to answer any actual requests for information.

As of now, I will be careful not to warn Kobo fanatics about the anything but high-quality engineering of this company's products.

No, you should be careful not to go sprouting your "knowledge" about products you have no experience with. Stating that you don't like a companies products, is one thing. Calling people stupid because they like those products is another thing. Stating you had problems with a companies products is OK. Insulting people who have not had good experiences with those same products not. Saying you are not interested in a product, perfectly reasonable. Insulting people who think the product might suit them, again not OK.

All you are doing is putting people and a company down and when someone calls you on it, asking for explanations, you ignore them. Which is your pattern in just about every thread you post in.

[Uncle Robin]

Originally Posted by Pjama

Anxiously awaiting mansplaining. 3, 2, 1.

I'll try to oblige, as soon as I get the hang of manspreading - apparently it's required of Y chromosome carriers, but I've never mastered it.

[trekk]

Originally Posted by Pjama

Yeah, nevermind on the Internet everyone is a dog, on the Internet everyone is assumed to be a guy. It’s pathetic.

I didn't mean to participate in all this controversy, but actually rantanplan knows ottischwenk's gender. Otti is quite active in german forums, as is rantanplan. Of course you could'nt possibly know that.

[ottischwenk]

Originally Posted by davidfor

So you believe that when Kobo took over tolino, that they sacked the tolino developers and put together a whole new team to further develop the tolino software. Seriously? Do you have proof of this?

Yes.

Calling people stupid because they like those products is another thing.

But it's stupid to like a product you have no idea about just because it's from Kobo.
Incidentally, based on the existing configuration, I can say that the product will be like all Kobo products that I have examined - just so good that it is not very obvious how badly it was developed.

[Skydog]

Originally Posted by Pjama

Horrible. Why you are allowed to disrupt this forum in this way, I will never understand. I see your name and my heart sinks. Congratulations for being a disruptive arse.

Why be bothered needlessly? The ignore option in your settings is a wonderful thing. In fact, I have no idea what the individual has posted thanks to that very feature.

[Uncle Robin]

Originally Posted by Skydog

Why be bothered needlessly? The ignore option in your settings is a wonderful thing. In fact, I have no idea what the individual has posted thanks to that very feature.

A limitation of the feature whose specific application we are strictly forbidden to identify is that quoting circumvents it. Were someone else to assiduously reply with lengthy, comprehensive quoting of a person on one's own list, the content one chose not to see is effectively rendered very visible. Sadly.

[Skydog]

Originally Posted by Uncle Robin

A limitation of the feature whose specific application we are strictly forbidden to identify is that quoting circumvents it. Were someone else to assiduously reply with lengthy, comprehensive quoting of a person on one's own list, the content one chose not to see is effectively rendered very visible. Sadly.

True but, at least in my case, it requires extra effort to divert my eyes and actually read quotes. They too are easily passed over/ignored.

[geek1011]

Originally Posted by davidfor

Yes, very sure.

I asked about the apparent audio support and was given a very firm no. But I was told Bluetooth would be used for pairing keyboards. I questioned that as I had not seen any reference to this before. I am not sure, but I don't I think that it is in the firmware that was on the few review devices, but it is in the firmware that has been discovered.

I do indeed see stuff which looks for HID devices, but the thing is, that same code also looks for audio devices (and they're both over DBus, so I don't think it's for other devices). Now, since I do see AVRCP-related stuff, one possibility is that they're planning to allow audio devices to be paired to use their keys to control book pagination. That would fit in with the large amount of new stuff related to key debugging. And, the devs might have experimented with audio for fun (it might be possible to make use of it if they leave that code in the final version, though). Or, alternatively, whatever they're using for BT might have a GStreamer dependency to support AVRCP.

Either way, none of it will actually be usable right now since it isn't connected to the UI, and the Bluetooth DBus daemon isn't shipped (at least in the firmware update).

---

I think I might be able to dig up what the AVRCP key stuff is for though, which should clear things up a bit. For anyone interested, here's the hex I need to figure out the encoding of to be able to give a more confident response about what the A2DP and AVRCP stuff is for:

Spoiler:

514d41500000000100000026000000000161ffff0101000000 0000000067ffff0100001300000000006cffff010000150000 00000069ffff0100001200000000006affff01000014000000 00008bffff0100005500000000016affff0100009000000000 016cffff010000910000000000aeffff010000000000000000 0bffff00000030000000000002ffff00000031000000000003 ffff00000032000000000004ffff00000033000000000005ff ff00000034000000000006ffff00000035000000000007ffff 00000036000000000008ffff00000037000000000009ffff00 00003800000000000affff00000039000000000034ffff0000 002e00000000001cffff01000005000000000192ffff010001 18000000000193ffff01000119000000000195ffff0100ffff 0000000000abffff01000109000000000166ffff0100010900 0000000164ffff01000000000000000073ffff010000720000 00000072ffff01000070000000000071ffff01000071000000 0000c8ffff010000800000000000a6ffff0100008100000000 00c9ffff010000850000000000a3ffff010000830000000000 a5ffff010000820000000000a7ffff010000840000000000a8 ffff010000c50000000000d0ffff0100010200000000.

I think it's https://doc.qt.io/qt-5/qmap.html, so I'll probably just try reading it from a QDataStream.

Edit 3: Hmm, it's not a plain QMap. I'm going to have to put a bit more effort into this.

Edit 4: So, it appears to have a header composed of a few int32s, then an array of structs containing int16s, int8s, and int32s. I'll have put something together to decode them, then figure out what they mean.

Edit 5: Here's a quick dump. I'll need to do some guessing and/or cross-reference against /usr/local/Kobo/generic/libkeys.so.

Spoiler:

 000  struct { Magic int32; H2 int32; H3 int32; H4 int32 }{Magic:1364017488, H2:1, H3:38, H4:0}
 016  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:353, B:-1, C:16842752, D:0, E:0, F:0}
 028  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:103, B:-1, C:16777235, D:0, E:0, F:0}
 040  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:108, B:-1, C:16777237, D:0, E:0, F:0}
 052  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:105, B:-1, C:16777234, D:0, E:0, F:0}
 064  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:106, B:-1, C:16777236, D:0, E:0, F:0}
 076  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:139, B:-1, C:16777301, D:0, E:0, F:0}
 088  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:362, B:-1, C:16777360, D:0, E:0, F:0}
 100  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:364, B:-1, C:16777361, D:0, E:0, F:0}
 112  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:174, B:-1, C:16777216, D:0, E:0, F:0}
 124  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:11, B:-1, C:48, D:0, E:0, F:0}
 136  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:2, B:-1, C:49, D:0, E:0, F:0}
 148  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:3, B:-1, C:50, D:0, E:0, F:0}
 160  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:4, B:-1, C:51, D:0, E:0, F:0}
 172  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:5, B:-1, C:52, D:0, E:0, F:0}
 184  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:6, B:-1, C:53, D:0, E:0, F:0}
 196  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:7, B:-1, C:54, D:0, E:0, F:0}
 208  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:8, B:-1, C:55, D:0, E:0, F:0}
 220  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:9, B:-1, C:56, D:0, E:0, F:0}
 232  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:10, B:-1, C:57, D:0, E:0, F:0}
 244  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:52, B:-1, C:46, D:0, E:0, F:0}
 256  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:28, B:-1, C:16777221, D:0, E:0, F:0}
 268  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:402, B:-1, C:16777496, D:0, E:0, F:0}
 280  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:403, B:-1, C:16777497, D:0, E:0, F:0}
 292  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:405, B:-1, C:16842751, D:0, E:0, F:0}
 304  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:171, B:-1, C:16777481, D:0, E:0, F:0}
 316  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:358, B:-1, C:16777481, D:0, E:0, F:0}
 328  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:356, B:-1, C:16777216, D:0, E:0, F:0}
 340  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:115, B:-1, C:16777330, D:0, E:0, F:0}
 352  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:114, B:-1, C:16777328, D:0, E:0, F:0}
 364  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:113, B:-1, C:16777329, D:0, E:0, F:0}
 376  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:200, B:-1, C:16777344, D:0, E:0, F:0}
 388  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:166, B:-1, C:16777345, D:0, E:0, F:0}
 400  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:201, B:-1, C:16777349, D:0, E:0, F:0}
 412  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:163, B:-1, C:16777347, D:0, E:0, F:0}
 424  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:165, B:-1, C:16777346, D:0, E:0, F:0}
 436  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:167, B:-1, C:16777348, D:0, E:0, F:0}
 448  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:168, B:-1, C:16777413, D:0, E:0, F:0}
 460  struct { A int16; B int16; C int32; D int8; E int8; F int16 }{A:208, B:-1, C:16777474, D:0, E:0, F:0}
 472  EOF

package main

import (
	"encoding/binary"
	"fmt"
	"io"
	"os"
)

func main() {
	f, err := os.Open("/home/patrick/src/qrc/test/17623/keys/avrcp.qmap")
	if err != nil {
		panic(err)
	}
	defer f.Close()

	var hdr struct {
		Magic int32
		H2    int32
		H3    int32
		H4    int32
	}
	if off, err := f.Seek(0, io.SeekCurrent); err != nil {
		panic(err)
	} else {
		fmt.Printf("% 04d  ", off)
	}
	if err := binary.Read(f, binary.BigEndian, &hdr); err != nil {
		panic(err)
	}
	fmt.Printf("%#v\n", hdr)

	for {
		var it struct {
			A int16
			B int16
			C int32
			D int8
			E int8
			F int16
		}
		if off, err := f.Seek(0, io.SeekCurrent); err != nil {
			panic(err)
		} else {
			fmt.Printf("% 04d  ", off)
		}
		if err := binary.Read(f, binary.BigEndian, &it); err == io.EOF {
			fmt.Printf("EOF\n")
			break
		} else if err != nil {
			panic(err)
		}
		fmt.Printf("%#v\n", it)
	}
}

Edit 6: It appears that field C is a Qt::Key.

[Amon_Re]

Originally Posted by ottischwenk

The Forma screen has more pixels than the Elipsa and if you don't need a pen, the added value is simply being able to afford such an expensive device.

I'm pretty sure they both have exactly the same number of pixels, but I do want a 10.3" device, not for the pen (although that's a nice added bonus) but specifically to read stuff that's meant to be read on something bigger than the average 7" or even 8" size.

I actually already own such a device (Boyue) but it's sadly damaged due to a fall.

[Uncle Robin]

Originally Posted by Skydog

True but, at least in my case, it requires extra effort to divert my eyes and actually read quotes. They too are easily passed over/ignored.

I do wonder how many OPs give up hoping for an answer to their query when their thread ends getting hijacked by the sort diversionary rants to prompt some to avail themselves of that feature of the forum software. They may not know that the feature exists, and may decide that 60 pages of insults and anger for too much to sift through for a handful of on-topic, helpful replies.