Another call for testers

[patrik]

Ok, reinstalled the fb-ink from this thread.

[root@(none) ~]# hexdump -x /dev/input/event1
0000000    eb30    5b7a    19c6    000c    0003    0001    0240    0000
0000010    eb30    5b7a    19eb    000c    0003    0000    03ec    0000
0000020    eb30    5b7a    19f7    000c    0003    0018    0065    0000
0000030    eb30    5b7a    1a03    000c    0001    014a    0001    0000
0000040    eb30    5b7a    1a0d    000c    0000    0000    0000    0000
0000050    eb30    5b7a    5867    000d    0003    0018    0000    0000
0000060    eb30    5b7a    588f    000d    0001    014a    0000    0000
0000070    eb30    5b7a    5898    000d    0000    0000    0000    0000

[root@(none) ~]# button_scan -p
[FBInk] Variable fb info: 1080x1440, 32bpp @ rotation: 1 (Clockwise, 90°)
[FBInk] Fontsize set to 24x24 (IBM base glyph size: 8x8)
[FBInk] Line length: 45 cols, Page size: 60 rows
[FBInk] It's a perfect fit!
[FBInk] Fixed fb info: ID is "mxc_epdc_fb", length of fb mem: 6684672 bytes & line length: 4352 bytes
[FBInk] Kernel's HZ value appears to be 100
Button color is expected to be #D9D9D9
We need to match two buttons each between 135 and 270 pixels wide!
Looking for buttons in a 810x432 rectangle, from (54, 792) to (864, 1224)
Failed end of match after 1 consecutive matches @ (522, 825)
Failed end of match after 1 consecutive matches @ (313, 826)
Failed end of match after 1 consecutive matches @ (385, 827)
Failed end of match after 1 consecutive matches @ (463, 827)
Failed end of match after 1 consecutive matches @ (501, 827)
Failed end of match after 1 consecutive matches @ (560, 827)
Failed end of match after 1 consecutive matches @ (120, 886)
Failed end of match after 1 consecutive matches @ (217, 902)
Failed end of match after 1 consecutive matches @ (110, 910)
Failed end of match after 1 consecutive matches @ (151, 914)
End of match 1 after 184 consecutive matches @ (390, 989)
End of match 2 after 184 consecutive matches @ (584, 989)
Matched on a 184x70 button! :)
x=1024, y=588
H2O²r1: x=415, y=491
Pressing the Connect button . . .
On iteration nr. 0, pixel (540, 1439) was #FFFFFF
On iteration nr. 1, pixel (540, 1439) was #FFFFFF
On iteration nr. 2, pixel (540, 1439) was #FFFFFF
On iteration nr. 3, pixel (540, 1439) was #FFFFFF
On iteration nr. 4, pixel (540, 1439) was #FFFFFF
On iteration nr. 5, pixel (540, 1439) was #FFFFFF
On iteration nr. 6, pixel (540, 1439) was #FFFFFF
On iteration nr. 7, pixel (540, 1439) was #FFFFFF
On iteration nr. 8, pixel (540, 1439) was #FFFFFF
On iteration nr. 9, pixel (540, 1439) was #FFFFFF
On iteration nr. 10, pixel (540, 1439) was #FFFFFF
On iteration nr. 11, pixel (540, 1439) was #FFFFFF
On iteration nr. 12, pixel (540, 1439) was #FFFFFF
On iteration nr. 13, pixel (540, 1439) was #FFFFFF
On iteration nr. 14, pixel (540, 1439) was #FFFFFF
On iteration nr. 15, pixel (540, 1439) was #FFFFFF
On iteration nr. 16, pixel (540, 1439) was #FFFFFF
On iteration nr. 17, pixel (540, 1439) was #FFFFFF
On iteration nr. 18, pixel (540, 1439) was #FFFFFF
On iteration nr. 19, pixel (540, 1439) was #FFFFFF
[FBInk] Failed to press the Connect button!

[patrik]

Hmm, it only says: "FBInk v1.4.0 for Kobo". Am I still using the wrong fbink?

[NiLuJe]

@patrik: That'd be the version from the FBInk thread, so, neither this one, nor the one from KoboStuff. o_O.

I'll double-check the attachment here, but I don't even have that file anymore on my end, so if it ended up in here, that's a serious mystery .

EDIT: Hmm, attachment looks good on my end. ISP or file manager shenanigans?

[patrik]

Ok, finally got the correct one...

I put up the image and it seems to have "pressed" since the image went away and the press took me to another menu, but the output said no success?

[root@(none) ~]# button_scan -p
[FBInk] Variable fb info: 1080x1440, 32bpp @ rotation: 1 (Clockwise, 90°)
[FBInk] Fontsize set to 24x24 (IBM base glyph size: 8x8)
[FBInk] Line length: 45 cols, Page size: 60 rows
[FBInk] It's a perfect fit!
[FBInk] Fixed fb info: ID is "mxc_epdc_fb", length of fb mem: 6684672 bytes & line length: 4352 bytes
[FBInk] Enabled Kobo w/o Multi-Touch quirks
[FBInk] Kernel's HZ value appears to be 100
Button color is expected to be #D9D9D9
We need to match two buttons each between 135 and 270 pixels wide!
Looking for buttons in a 810x432 rectangle, from (54, 792) to (864, 1224)
Failed end of match after 1 consecutive matches @ (522, 825)
Failed end of match after 1 consecutive matches @ (313, 826)
Failed end of match after 1 consecutive matches @ (385, 827)
Failed end of match after 1 consecutive matches @ (463, 827)
Failed end of match after 1 consecutive matches @ (501, 827)
Failed end of match after 1 consecutive matches @ (560, 827)
Failed end of match after 1 consecutive matches @ (120, 886)
Failed end of match after 1 consecutive matches @ (217, 902)
Failed end of match after 1 consecutive matches @ (110, 910)
Failed end of match after 1 consecutive matches @ (151, 914)
End of match 1 after 184 consecutive matches @ (390, 989)
End of match 2 after 184 consecutive matches @ (584, 989)
Matched on a 184x70 button! :)
x=1024, y=588
H2O²r1: x=415, y=491
Pressing the Connect button . . .
On iteration nr. 0, pixel (540, 1439) was #FFFFFF
On iteration nr. 1, pixel (540, 1439) was #FFFFFF
On iteration nr. 2, pixel (540, 1439) was #FFFFFF
On iteration nr. 3, pixel (540, 1439) was #FFFFFF
On iteration nr. 4, pixel (540, 1439) was #FFFFFF
On iteration nr. 5, pixel (540, 1439) was #FFFFFF
On iteration nr. 6, pixel (540, 1439) was #FFFFFF
On iteration nr. 7, pixel (540, 1439) was #FFFFFF
On iteration nr. 8, pixel (540, 1439) was #FFFFFF
On iteration nr. 9, pixel (540, 1439) was #FFFFFF
On iteration nr. 10, pixel (540, 1439) was #FFFFFF
On iteration nr. 11, pixel (540, 1439) was #FFFFFF
On iteration nr. 12, pixel (540, 1439) was #FFFFFF
On iteration nr. 13, pixel (540, 1439) was #FFFFFF
On iteration nr. 14, pixel (540, 1439) was #FFFFFF
On iteration nr. 15, pixel (540, 1439) was #FFFFFF
On iteration nr. 16, pixel (540, 1439) was #FFFFFF
On iteration nr. 17, pixel (540, 1439) was #FFFFFF
On iteration nr. 18, pixel (540, 1439) was #FFFFFF
On iteration nr. 19, pixel (540, 1439) was #FFFFFF
[FBInk] Failed to press the Connect button!

[NiLuJe]

@patrik: Yeah, that sounds correct, the detection only detects a "real" switch, not my screenshot trickery .

Thanks!

[codex-hex]

what about my device:Kobo Aura Edition 2?

[NiLuJe]

That's the Aura SE, r1 should be supported, while the r2 is a mystery wrapped in an enigma (but provided it actually behaves as it should, like a Mk7, also supported).

[jsonora]

v1.4.0-56-g2aff05a worked.

Clara HD:

~ # button_scan -p
[FBInk] Variable fb info: 1072x1448, 32bpp @ rotation: 3 (Counter Clockwise, 270°)
[FBInk] Fontsize set to 24x24 (IBM base glyph size: 8x8)
[FBInk] Line length: 44 cols, Page size: 60 rows
[FBInk] Fixed fb info: ID is "mxc_epdc_fb", length of fb mem: 6782976 bytes & line length: 4352 bytes
[FBInk] Enabled Kobo Mark 7 quirks
[FBInk] Kernel's HZ value appears to be 100
Button color is expected to be #D9D9D9
We need to match two buttons each between 134 and 268 pixels wide!
Looking for buttons in a 804x434 rectangle, from (53, 796) to (857, 1230)
Failed end of match after 1 consecutive matches @ (233, 835)
Failed end of match after 1 consecutive matches @ (499, 837)
Failed end of match after 1 consecutive matches @ (529, 840)
Failed end of match after 1 consecutive matches @ (530, 845)
Failed end of match after 1 consecutive matches @ (509, 847)
Failed end of match after 1 consecutive matches @ (408, 857)
Failed end of match after 1 consecutive matches @ (515, 858)
Failed end of match after 1 consecutive matches @ (504, 859)
Failed end of match after 1 consecutive matches @ (126, 897)
Failed end of match after 1 consecutive matches @ (87, 905)
Failed end of match after 1 consecutive matches @ (89, 906)
Failed end of match after 1 consecutive matches @ (317, 911)
Failed end of match after 1 consecutive matches @ (478, 916)
Failed end of match after 1 consecutive matches @ (777, 918)
Failed end of match after 1 consecutive matches @ (686, 919)
Failed end of match after 1 consecutive matches @ (483, 925)
Failed end of match after 1 consecutive matches @ (722, 925)
Failed end of match after 1 consecutive matches @ (309, 926)
Failed end of match after 1 consecutive matches @ (788, 929)
Failed end of match after 1 consecutive matches @ (488, 934)
Failed end of match after 1 consecutive matches @ (342, 935)
Failed end of match after 1 consecutive matches @ (788, 935)
End of match 1 after 205 consecutive matches @ (403, 969)
End of match 2 after 205 consecutive matches @ (618, 969)
Matched on a 205x70 button! :)
x=1004, y=556
H2O²r1: x=443, y=515
Pressing the Connect button . . .
On iteration nr. 0, pixel (536, 1447) was #FFFFFF
On iteration nr. 1, pixel (536, 1447) was #FFFFFF
On iteration nr. 2, pixel (536, 1447) was #FFFFFF
On iteration nr. 3, pixel (536, 1447) was #FFFFFF
On iteration nr. 4, pixel (536, 1447) was #FFFFFF
On iteration nr. 5, pixel (536, 1447) was #FFFFFF
On iteration nr. 6, pixel (536, 1447) was #000000
. . . appears to have been a success!

[sherman]

From the newest firmware thread...

Originally Posted by davidfor

• Config file option "AutoUsbGadget" has been added. If set to "true" in the config file, the device automatically connect to the PC when plugged in. This needs to be added to the "DeveloperSettings" section of the config file.

Has Kobo been watching us?

[NiLuJe]

@jsonora: Great! Thank you! .

@sherman:

[NiLuJe]

Resurrecting this thread because Forma, yay!

(Kernel isn't out yet, but at least the FW is flagged Mk7, the CPU is identical, so, the basics should work. That leaves orientation handling as my main concern... I'm hoping really really hard it's done properly and I won't have to jump through a billion hoops to make it behave... The cherry on top would be an accurate (and, ideally, cheap) way to tell which orientation is currently used...).

Provided they haven't scrapped the legacy interface, the current release *should* at least display stuff *somewhere* fine, but I attached a current build to the first post which properly detects the Forma, making sure it uses the Mk7 codepath.

[NiLuJe]

And it's that time of the year again .

If anyone with a brand new Libra would be willing to be a guinea pig, that'd be greatly appreciated .

(I'm hoping it'll essentially behave like a Forma, but some new stuff is hinting that maybe it won't...).