View Single Post
Old 03-10-2022, 06:13 AM   #16
mergen3107
Wizard
mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.
 
mergen3107's Avatar
 
Posts: 1,520
Karma: 5000046
Join Date: Feb 2012
Location: Cape Canaveral
Device: Kindle Scribe
Quote:
Originally Posted by Renate View Post
Two solutions:
1) Use Magisk and don't touch /vendor or /system
By the way, just recently I was able to update with Onyx upx file, whereas my /system is a bit modified (Lock/Unlock sound files are swapped, and unzip binary is replaced). After the update I had to do these changes anyway.
I guess this is because that was a full update (1.1 GB+). Problem you mention should reveal on incremental updates, right?

P.S. I am sorry for off-topic, but is there a way to replace a system binary systemless-ly? Like, Magisk has system-less hosts file replacement.

The problem is that KOReader relies on unzip's encoding. On my Onyx's Android 10 the unzip binary is ancient and doesn't handle Cyrillic encoding. So I had to replace it by a fresher binary.
mergen3107 is offline   Reply With Quote