remarkable-hacks icon indicating copy to clipboard operation
remarkable-hacks copied to clipboard

rm2: 2.14.1.866 slow to load on first install compared to unpatched

Open yduf opened this issue 2 years ago • 2 comments

Hello,

It is more information for others than anything else, because I thought at first that the patch wasn't working. see info below.

Regards,

Yves

__ Noticing that patch was available, I have upgraded my rm2 to 2.14.1.866. When applying latest patch, the rm screen flash, then get stuck on loading progress bar (at least one minute), to the point I thought it was not installing properly.

That why's I have done Ctrl-C and No (ie no permanent install), screen flash again, but I was still stuck on loading progress bar at some point.

Shuting down the system with shutdown now, restart the UI in a working mode.

While I was writting this, I waited long enough, and it happens to work. Just once patch is applied, system is really slow to load (compared to unpatched version).

I accepted the version, it reboots and then load with a normal amount of time.

Here are the output from the script, in ssh console:

reMarkable
╺━┓┏━╸┏━┓┏━┓   ┏━┓╻ ╻┏━╸┏━┓┏━┓
┏━┛┣╸ ┣┳┛┃ ┃   ┗━┓┃ ┃┃╺┓┣━┫┣┳┛
┗━╸┗━╸╹┗╸┗━┛   ┗━┛┗━┛┗━┛╹ ╹╹┗╸
reMarkable: ~/ sh -c "$(wget https://raw.githubusercontent.com/ddvk/remarkable-hacks/master/patch.sh -O-)"                
Connecting to raw.githubusercontent.com (185.199.110.133:443)
wget: note: TLS certificate validation not implemented
writing to stdout
-                    100% |*************************************************************************************| 11108  0:00:00 ETA
written to stdout
Disk space seems to be enough.
rM2 Version 2.14.1.866 - patch_35.2.01
Connecting to github.com (140.82.121.3:443)
wget: note: TLS certificate validation not implemented
Connecting to raw.githubusercontent.com (185.199.111.133:443)
saving to '/home/rmhacks/patch_35.2.01'
patch_35.2.01        100% |*************************************************************************************| 91822  0:00:00 ETA
'/home/rmhacks/patch_35.2.01' saved
Connecting to github.com (140.82.121.3:443)
wget: note: TLS certificate validation not implemented
Connecting to raw.githubusercontent.com (185.199.109.133:443)
saving to '/home/rmhacks/patch.sh'
patch.sh             100% |*************************************************************************************| 11108  0:00:00 ETA
'/home/rmhacks/patch.sh' saved
Failed to stop rm2fb.service: Unit rm2fb.service not loaded.
killall: remarkable-shutdown: no process killed
killall: xochitl: no process killed
Cleaning up...

**********************************************
Trying to start the patched version...
You can play around, press CTRL-C when done!
**********************************************

Registering exit handlers
Reading waveforms from /usr/share/remarkable/320_R292_AFBC21_ED103TC2M1_TC.wbf
Running INIT (87 phases)
11:25:36.885 qt.qpa.input             evdevtouch: Using device discovery
11:25:36.891 qt.qpa.input             evdevtouch: Adding device at /dev/input/event2
11:25:36.892 qt.qpa.input             evdevtouch: Using device /dev/input/event2
11:25:36.893 qt.qpa.input             evdevtouch: /dev/input/event2: Protocol type B  (multi), filtered=no
11:25:36.894 qt.qpa.input             evdevtouch: /dev/input/event2: min X: 0 max X: 1403
11:25:36.895 qt.qpa.input             evdevtouch: /dev/input/event2: min Y: 0 max Y: 1871
11:25:36.896 qt.qpa.input             evdevtouch: /dev/input/event2: min pressure: 0 max pressure: 0
11:25:36.897 qt.qpa.input             evdevtouch: /dev/input/event2: device name: pt_mt
11:25:44.531 qt.qpa.input             evdevtouch: Updating QInputDeviceManager device count: 1 touch devices, 0 pending handler(s)

=<>= here is the waiting parts.

yduf avatar Jul 22 '22 11:07 yduf

Not really sure that it is the right place to post, but how did you upgrade to rm2 2.14.1.866 ?? I tried on mine but it is still stuck to 2.14.0.861. I than thought that I had to make an official upgrade to 2.14.1.866 and then applying the patch but there isn't any official 2.14.0.861 upgrade... I would like to understand the correct process. From what are we supposed to uipgrade ? an official version ? The last patched version ? Any help would be much appreciated ! :)

Reddevil57 avatar Jul 26 '22 08:07 Reddevil57

After each upgrade, I am disabling automatic updates. So to upgrade to 2.14.1.866, (or any latest version), I am just using Menu/Settings/General then Software version button then enable automatic update, and check for updates.

It has worked each time.

But I don't remenber the specific version I was updating from, 2.12.x or 2.13.x ?

yduf avatar Jul 26 '22 14:07 yduf