-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stable merge for week 6 of 2022 #556
Conversation
New Packages: * Add new rmkit apps: dumbskull, rpncalc and wordlet (#542) * Add package for Folly (z-machine interpreter) (#543) Updated Packages: * Update KOReader to v2022.01 (#517) * Update innernet to 1.5.3 (#545) * Update to all rmkit applications (#542) * Update plato to 0.9.25 (#534) * Update rm2fb to v0.0.14 (#552) Misc: * Remove outdated todo from opkg completion (#541)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested packages successfully on both models.
Sidenote: Since 2.12.1.527 is not supported yet. I had to add this to /opt/etc/rm2fb.conf
to make it work.
thanks so much for testing!! this should contain rm2fb support for latest xochitl (2.12.1.527), if it doesn't we should update this pr |
oops. you're right. not sure why but I had configure errors when updating and though they might have missed and it worked afterwards. Might have not applied rm2 specific updates though. Not entirely sure, but removing the config and rebooting works. |
When starting plato from remux, the app is correctly launched and shows up both on screen and on htop, but it does not appear as started in the remux menu (no memory usage is visible). Switching back and forth between other apps and plato through remux does work. If I tap the blank square beside “Plato” in the menu, where the memory usage would normally appear, Plato is not killed, but the Plato screen is henceforth not recalled properly when switching to another app and back to Plato. I’m curious if anyone else can reproduce that bug? Does anyone know whether it’s been reported elsewhere already (I couldn’t find any reference from a quick search)? |
|
|
Tested on rM2 2.12. |
New Packages:
Updated Packages:
Misc: