Seems that anything based on browser (so pretty much all web apps) is kicking battery hard. Listening music that was on device via Music Player didn't drain device so hard, obviously.Seems like TELEports and Axolotl don't drain so much neither, even tho Axolotl is prevented from closing.
So, at this point, native aps - cool, web based - drain.
@zilladog A bit late on the subject here but I currently use a Xperia X on T-Mobile and everything seems to work for me pretty well. Occasionally a SMS or MMS will fail to come through but I had the same issue on my Nexus 5. That said I haven't had any deal breaker issues thus far and I daily drive it.
@mario-ch I got myself mixed up with program names earlier: I meant to type that the official "Emma" tool is the cranky one sometimes about unlocked bootloaders and finding the right firmware. The free apps XperiFirm and newflasher are sometimes needed for reverting a Sony device successfully to stock. With an XA2 Ultra, I never got Emma to work, and had to use the combo I mentioned to do that revert step from the zendesk page.
@fredldotme No, I'm on stable. But thanks for the information.
The drain is still there. It's most likely UBsync's fault because it's the latest app I installed 😅 I'll just try to uninstall it and go back to manual backing up to my NC 😃
As above with ubports-installer_0.8.4-beta_linux_x86_64.AppImage failed (latest version available) and I was unable to get the downloaded file SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.zip / *.img accepted, I used ubports-installer_0.7.4-beta_linux_x86_64.AppImage, a previous version I still had on my computer and this worked.
After that I was able to reinstall with ubports-installer_0.8.4-beta_linux_x86_64.AppImage (latest version). This time it was not requested to manually download the image file. Installation worked.
Still there is the issue in ubports installer version 0.8.4 (ubports-installer_0.8.4-beta_linux_x86_64.AppImage) that installation of the image file failed before and why it is now working.
In case it helps anyone else I think I worked out why my phone stopped booting after updating. Originally it was running the /community/fredldotme/devel channel. I think I must have accidentally switched it to /arm64/hydris/devel in the phone settings playing around one day. In the phone they both show up as Development but in the installer you see the full path and can tell them apart.
Not sure if this was the problem, but I assume swapping between devel channels is not a good idea!