View Single Post
Old 12-15-2023, 02:52 PM   #48
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by mitseas View Post
That is as easy as ssh from within KOReader and unziping that version in /mnt/private?
That should work.

You can also use the safemode tool included as part of the platform instructions (press the home button at boot, when the little dots are displayed).

You should see an image like https://github.com/pazos/cervantes-s...ges/usbnet.png and be able to connect to telnet as usual.

In that mode calling the program will show you logs and block your terminal until the program is closed.


If you try this way you can uncompress the old version in a different directory and call koreader.sh from there.



Quote:
Originally Posted by mitseas View Post
By the way before trying KOReader the stock reading app was crashing (on developer's firmware) on every page turn.
Yup, it was fixed in master (see https://github.com/bq/cervantes/pull/9) but never hit a release.

Quote:
Originally Posted by mitseas View Post
Now that I am already in the developer's mode can I reset the device to an "almost" original state to check the Frontlight and the stock reading app?
Stock doesn't matter anymore . If you're serious documenting the behaviour please read https://github.com/koreader/koreader...ment-439700537

try to reproduce, write different (in range) values to the sysfs nodes and see if you find a particular pattern.


You can also see their github repo and find the way they do the pattern correction, if there's any.

Anyhow, we're doing the proper thing with the hardware (writting to the right nodes within the proper ranges). Also the code that does light is under a HAL, so implementing pattern correction for a specific platform might not be as easy as it sounds.

Quote:
Originally Posted by mitseas View Post
All the files I used are from the archive dot org so they may not be the latest. Do you maybe have those?
I do, it's named "hackers_update_Cervantes4_702.zip". It should be exactly the same you're currently at.
pazos is offline   Reply With Quote