Since the update I’m affected by High cpu-usage by system_server (AAS) - #3 by broncheolus
Battery life is terrible. When AAS is running, after some time one CPU core is stuck at 100%. System_serve is constantly at 13% cpu usage and the battery consumption is above 800 mA while the handset gets noticable warm. Never had this (according to together.jolla ?old?) problem in over 12 years. Restart AAS is mending it just for a short time…and even when not using any Android app after restart, this reappears after some time.
After the update I did not install any Android app, or changed autostart settings for background services of any app. No patchmanager, nothing special apart from running CargoDock not sailjailed
So, AAS has to be off, if the mobile has to last a whole work day.
By by 
to my main calendar (fossify) and Matrix (Element). That’ll be my biggest painpoints… [I know the native alternatives…just in case, one would suggest to switch 
]
If anyone knows a workaround, or even a solution - that would be highly appreciated!!!
EDIT:
I removed the Jolla store Android apps and then the aas itself (see Removing Android AppSupport | Sailfish OS Documentation → 1. 1) & 1. 3) without touching all the other Android apps), shut down the device, reinstalled aas after Boot up … and all seemed normal then !!! 
. …until the next morning…when the system_serve was again at 13%… But, after aas restart: result!!! Right now it runs 24h like expected. …happy camper again and I hope system_serve behaves from now on.