View Single Post
Old 12-07-2019, 11:44 PM   #704
rtiangha
Evangelist
rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.
 
Posts: 495
Karma: 356531
Join Date: Jul 2016
Location: 'burta, Canada
Device: Kobo Glo HD
OK, I modified rcS to add in the Aura H2O driver (I think; I don't have the device so I can't test it to see if it works).

Based on user reports, it looks like the Clara, Forma and Libra work with the H2O2 driver, so there's nothing left to be changed on that front.

The only device I'm unsure about is the Aura Edition 2 v2 currently being sold by Walmart (I think). Same code name as the v1 (star) but has an ID of 379 and is classified as a Mark 7 device. So it's missing, but from what I can tell, it's the only one left in their supported product line. Not sure if we should assume it uses the same driver as the v1 (libKoboTS.so) or the same one as the other Mark 7 devices (libKoboTS_h2o2.so, in which case, I think no change would be needed and it should just work by default with this newer version of KSM09). It'd be nice for someone with access to that device to test and confirm.

(Edit: And I have no idea why line 174 reads
Code:
export export QWS_MOUSE_PROTO=KoboTS
so I deleted that extra export; let me know if that is actually needed).

As for the other 'Add Forma and Libra data to the "case $PRODUCT in ..." block' task, currently, that section in KSM09 looks like this:

Spoiler:
Code:
    case $PRODUCT in
      kraken|phoenix|star)
        export COORDINATES="80 870 70 70 200 870 70 70";;
      snow)
        export COORDINATES="180 -1200 100 100 320 -1200 100 100";;
      dragon|dahlia|alyssum|nova)
        export COORDINATES="120 1220 100 100 280 1220 100 100";;
      daylight)
        export COORDINATES="100 1640 200 200 300 1640 200 200";;
      *)
        export COORDINATES="55 685 60 60 150 685 60 60";
    esac


while in firmware 4.18.13737, it looks like this:

Spoiler:
Code:
	case $PRODUCT in
		kraken|phoenix)
			export COORDINATES="200 740 350 150";;
		snow)
			export COORDINATES="250 -1050 570 150";;
		star)
			export COORDINATES="160 740 400 150";;
		dragon|dahlia)
			export COORDINATES="260 1070 540 130";;
		alyssum)
			export COORDINATES="240 1070 550 150";;
		daylight)
			export COORDINATES="320 1400 730 170";;
		nova)
			export COORDINATES="250 1070 600 150";;
		frost)
			export COORDINATES="350 1400 750 200";;
		storm)
			export COORDINATES="325 1240 610 150";;
		*)
			export COORDINATES="140 600 300 70";;
		
	esac


Is it good enough to just copy/paste that section in? I'm assuming that if that's done, then KSM09 will no longer work on older firmwares (which probably wouldn't be an issue to worry about because newer hardware won't run on older firmware anyways so no need to support that), correct? Or is there a reason why the KSM09 version looks so different?

Last edited by rtiangha; 12-08-2019 at 12:22 AM.
rtiangha is offline   Reply With Quote