Kobo Start Menu 09

[CH23]

Originally Posted by tshering

Different from the other dirver, he touch driver for the H2o2v2 does not adjust to the rotation of the application, but is in a fixed position. Therefore my intention was to turn the framebuffer orientation 180, degree, and at the same time the KSM application's screen also 180 degree. I did however not understand that the touch coordinates are really horizontally mirrored, rather than rotated. Evidently, I did not read your report until the end.

I might not have been clear enough, but that is indeed the issue.

You mean with regard to KSM. KSM and Koreader are totally independent of each other.

Sorry for being short, but I have to dash the door.

oops. I shouldn't try to solve these things while half asleep hahaha.

[NiLuJe]

@CH23: Thank you! Created a PR thanks to your results .

Quick question: do the frontlight & naturallight controls work properly inside KOReader?

[CH23]

Originally Posted by NiLuJe

@CH23: Thank you! Created a PR thanks to your results .

Quick question: do the frontlight & naturallight controls work properly inside KOReader?

both invlasovsoft and koreader, frontlight works, but when you turn on the naturalight, the light dims

[tshering]

Originally Posted by CH23

The correct ksmrotate value is 2
The correct mrotate value is 270

Are you sure that ksmrotation=2? Is this the value you set in ksmhome.sh? How about the other variables, do they all take the same value as snow? Also for starting koreader and vlasovsoft launcher?

[CH23]

Originally Posted by tshering

Are you sure that ksmrotation=2? Is this the value you set in ksmhome.sh? How about the other variables, do they all take the same value as snow? Also for starting koreader and vlasovsoft launcher?

Ksmrotation=2

Mrotation=270
enablerotation=false

It seems very similar to snow; same driver, same rotation.
also touch in vlasovsoft has been fixed now.

One more thing to note: ksm and koreader both take over the frontlight+naturallight setting from nickel, but can't set naturallight themselves.

Koreader, when adding warmth, becomes less warm, and the normal backlight setting has no effect on the orange light

[tshering]

Originally Posted by CH23

Ksmrotation=2

Mrotation=270
enablerotation=false

It seems very similar to snow; same driver, same rotation.
also touch in vlasovsoft has been fixed now.

One more thing to note: ksm and koreader both take over the frontlight+naturallight setting from nickel, but can't set naturallight themselves.

Koreader, when adding warmth, becomes less warm, and the normal backlight setting has no effect on the orange light

Thank you for the information. I am somehow surprised about ksmrotation=2; since snow has 0.
I have another question. When you started the webinterface, was there a timing problem? Did you have to increase the waiting time in killautormcatsomepoint.sh?

[CH23]

Originally Posted by tshering

Thank you for the information. I am somehow surprised about ksmrotation=2; since snow has 0.
I have another question. When you started the webinterface, was there a timing problem? Did you have to increase the waiting time in killautormcatsomepoint.sh?

When starting, it takes 20 seconds before I can see the KSM. I did try to increase timing, but not sure if I actually got that to work.

I'll see if I have the time this afternoon, and re-install everything from scratch.

[seanos]

Originally Posted by CH23

No wiki, just a number of threads (like the one you're in now)

What a horror show! There seems to be some very useful information in threads like this, but it’s largely useless since the signal-to-noise ratio is so high and it’s pretty impossible for someone landing on a post from a search to tell if it’s applicable to the current version.

[CH23]

Originally Posted by seanos

What a horror show! There seems to be some very useful information in threads like this, but it’s largely useless since the signal-to-noise ratio is so high and it’s pretty impossible for someone landing on a post from a search to tell if it’s applicable to the current version.

Considering Tshering is the only developer(as far as i am aware) you can report your bugs in this thread.

I agree it's not optimal, but it works.

[cramoisi]

@CH3 did you disable the wifi after ksm9 first install ? if not perhaps it's that which slow down you thing at boot.

Disable wifi on start up by selecting: "tools" > "ksm diverse.msh" > "auto enable wifi off.sh".
Prevent command over the device via wifi: set with "configure" the value of "[general]allowRmcViaWifi" to false.
Note: enabling wifi on start up may slow starting KSM considerably.

(from post #1)

[seanos]

Originally Posted by CH23

Considering Tshering is the only developer(as far as i am aware) you can report your bugs in this thread.

I agree it's not optimal, but it works.

I disagree that it works. Obviously it’s up to tshering in the end, but adding answers to a FAQ/Wiki that you can refer to saves answering the same questions over and over. And often those answers take more than one post and are interrupted by many other questions, making the information difficult to reuse.

[tshering]

Originally Posted by CH23

When starting, it takes 20 seconds before I can see the KSM. I did try to increase timing, but not sure if I actually got that to work.

I'll see if I have the time this afternoon, and re-install everything from scratch.

Maybe it is not worth reinstalling anything at this point. I have already started to rewrite some parts of the scripts. As I said I feel unsure about the two rotation settings. Could you check them again? You would exit nickel, and then when KSM shows again properly and is correctly responding to touch, you would check the two variables with the webinterface; for instance "echo $ksmrotate", "echo $mrotation"; or "printenv" to see the whole list.

[jlynton]

Originally Posted by seanos

What a horror show! There seems to be some very useful information in threads like this, but it’s largely useless since the signal-to-noise ratio is so high and it’s pretty impossible for someone landing on a post from a search to tell if it’s applicable to the current version.

I agree that it is not ideal, but I, for one, am extremely grateful to tshering for all the hard work that he puts into KSM!

[CH23]

Originally Posted by tshering

Maybe it is not worth reinstalling anything at this point. I have already started to rewrite some parts of the scripts. As I said I feel unsure about the two rotation settings. Could you check them again? You would exit nickel, and then when KSM shows again properly and is correctly responding to touch, you would check the two variables with the webinterface; for instance "echo $ksmrotate", "echo $mrotation"; or "printenv" to see the whole list.

### executed:echo $ksmrotate

2

### executed:echo $mrotation

270

 ### executed:printenv

CONTENT_TYPE=application/x-www-form-urlencoded
GATEWAY_INTERFACE=CGI/1.1
ksmGeometryValuesN=
poweroffRotation=90
USER=root
UBOOT_MMC=/etc/u-boot/mx6sll-ntx/u-boot.mmc
mrotation=270
poweroffRandomdir=
prevlevel=N
REMOTE_ADDR=#########
QUERY_STRING=com_value=printenv&history=date&com_type=shell
ksmImageWidthLandscape=750
ksmGeometryValuesS=
HOME=/
powerOffDelay=0.8
ksmFontDir=/adds/kbmenu/fonts
ksmrotate=2
ntxfw_sz=9474
HTTP_USER_AGENT=##################################
REMOTE_PORT=56742
deleteSDRsOnboard=false
HTTP_ACCEPT=text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
ksmGeometryValuesW=
runlevel=S
CONTENT_LENGTH=46
koreaderbasedir=/mnt/onboard/.adds
NICKEL_HOME=/mnt/onboard/.kobo
DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-chCzxDdtl6,guid=1###################2
SCRIPT_FILENAME=/adds/kbmenu/rmc/cgi-bin/processcommands.sh
HTTP_HOST=##########:8087
kobomenuMenuBarFontsize=50
nickelpreload=
kobomenuShowClock=false
UBOOT_RECOVERY=/etc/u-boot/mx6sll-ntx/u-boot.recovery
REQUEST_URI=/cgi-bin/processcommands.sh
SERVER_SOFTWARE=busybox httpd/1.22.0.kobo
useDropbear=true
boot_port=1
CPU=mx6sll
provideSleepInMainMenu=false
KSMfrontlightlevel=20
TERM=vt102
waveform_p=0x9fd70000
hwcfg_p=0x9ffffe00
dontTamperwithFrontlight=true
PLATFORM=mx6sll-ntx
WIFI_MODULE=8189fs
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/lib:
HTTP_ACCEPT_LANGUAGE=en-GB,en;q=0.5
HTTP_REFERER=http://##########:8087/rmc_test.html
SERVER_PROTOCOL=HTTP/1.0
QWS_NO_SHARE_FONTS=1
vlasovsoftbasedir=/mnt/onboard/.adds/vlasovsoft
platobasedir=/mnt/onboard/.adds/plato
mousedriver=libKoboTS_h2o2.so
LANG=en_US.UTF-8
fbrotatevalue=0
PATH_INFO=
waveform_sz=2686280
hwcfg_sz=110
SHELL=/bin/sh
WIFI_MODULE_PATH=/drivers/mx6sll-ntx/wifi/8189fs.ko
REQUEST_METHOD=POST
ksmImageWidthPortrait=566
allowRmcViaWifi=true
ksmGeometryValuesE=
avoidPickel=false
PRODUCT=nova
INTERFACE=eth0
kobomenuFontsize=60
PRODUCT_ID=unknown
ksmuser=/mnt/onboard/.adds/kbmenu_user
PWD=/adds/kbmenu/rmc/cgi-bin
KSMdebugmode=false
SCRIPT_NAME=/cgi-bin/processcommands.sh
QWS_MOUSE_PROTO=KoboTS_h2o2
ntxfw_p=0x9fd6da00
ksmroot=/adds/kbmenu

[tshering]

Thank you for the informatinon. Since you did not mention anything, I supposed the updated touch driver solved the touch problem. But on the Koreader thread I read that the problem persists in KSM.
I just compared the pertinent reports, and I have a problem understanding what actually is the issue.

Originally Posted by CH23

Right now touch is 'flipped' (when i touch in top left, it thinks i touch bottom left)

Originally Posted by CH23

If i touch on the left, it will register on the right
If i touch on the right, it will register on the left
If i touch at the top, it will register on the top
If i touch at the bottom, it will register on the bottom

Originally Posted by CH23

As KSM has the same kind of issue (image correct, touch left/right swapped) I believe this is the same issue for both.

The first description does not agree with the second and third. Which one is correct? Or do they refer to different versions of the touch driver?

Do you have currently the latest version of libKoboTS_h2o2.so in adds/kbmenu/Qt/plugins/mousedrivers?

Could you do the following? (With the latest touch driver):

• exit nickel
• press "kill KSM"
• execute

  export ksmrotate=0 mrotation=90; $ksmroot/kobomenu.sh "a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z"

• touch the screen; when you select one of the options (not the buttons on the bottom) you should see the selected item (letter a-Z) in the output field of the webinterface (at this point you would have to execute the command newly in order to repeat the test); when you press one of the buttons, the list of options should move accordingly.

Originally Posted by CH23

added nova to adds/kbmenu/onstart/ksmhome.sh

What exactly did you do?