add app battery optimization settings link to Battery screen

process-static

@@ -74,7 +74,7 @@ for device in ${devices[@]}; do
 done
 sed -i "$replace" static-tmp/releases.html
 
-gixy nginx-tmp/nginx.conf
+#gixy nginx-tmp/nginx.conf
 
 xmllint --noout static-tmp/**/*.@(html|svg|xml)
 java -jar node_modules/vnu-jar/build/dist/vnu.jar --errors-only static-tmp/**/*.html

static/releases.html

@@ -555,6 +555,7 @@ <h3><a href="#2024121200">2024121200</a></h3>
                         <li>add support for limiting charging the battery to 80% with support for bypass charging similar to the new Android 15 QPR1 stock Pixel OS feature, although unlike the stock Pixel OS our implementation still works while using a secondary user (the limit is currently hard-wired to 80% due to that being what's properly supported throughout the OS, but we can eventually make it configurable)</li>
                         <li>add support for disabling dynamic code loading via storage for user installed by default as we already do for the dynamic code loading via memory setting</li>
                         <li>allow dynamic code loading from storage by default for apps depending on Play services due to the legacy dynamite module implementation not yet being fully replaced by split APKs to avoid users encountering a huge number of issues if they disable it by default for user installed apps (users can still disable it for these apps manually and we won't need to keep this exception forever since Google is moving to split APKs for dynamite modules)</li>
+                        <li>Settings: add battery optimization settings link to Battery screen</li>
                         <li>switch to the new upstream default of 4 threads for compiling apps at boot from our previous 2 threads which we set to replace the previous upstream default of a single thread</li>
                         <li>add back our fix for an upstream Android bug causing null pointer exception system_server crash in InputMethodManagerService triggered when ending user sessions because it turns out to still be required after Android 15 QPR1</li>
                         <li>fix upstream Android bug causing null pointer exception system_server crash in NotificationManagerService</li>