-
@Enrico13011978 How can I get in touch with the support support group? There wasn't an issue with the original firmware.
-
@furkanonder You can find various devices in the forum in the support category. Create a new support thread there and wait until someone responds.
-
@furkanonder As per my experience, I would like inform you that my device's battery has been fully charged in the morning. After 20 min, I have seen battery drain to 96%.
Device's network is set to 4G, where I used it only for calling and texting, internet usage is almost rare on my device, only for updating and downloading Apps.
Therefore, my assumption that 4G network drains the batter fast.
Even though do not have 4G data and do not need to use cellular data while navigating or other stuff.
Try to set it 3G network and monitor your battery consumption.
-
@furkanonder said in Significant Battery Drain with Wi-Fi Enabled on Pixel 3a:
How can I get in touch with the support group?
In addition to the forum, you can try https://t.me/ubports_pixel3a
-
Hello everyone,
I’m experiencing a significant battery drain on my Pixel 3a running Ubuntu Touch. When Wi-Fi is enabled, the battery drops from 100% to 10% in about 6 hours. However, when I turn off Wi-Fi, the battery only drops by about 15% in the same period.
I’ve reset the phone to factory settings and tested again without installing any additional apps, but the issue persists.
Has anyone else encountered this problem or have any suggestions for troubleshooting?
This issue was discussed here and as a result it was suggested that it be moved here.
-
F furkanonder referenced this topic
-
@furkanonder Can you give some context, like which version you have, is there anything that you've installed, or any app in background that does not suspend ( via UT Tweak Tool ).
Maybe try on RC ? -
@furkanonder said in Significant Battery Drain with Wi-Fi Enabled on Pixel 3a:
This issue was discussed here and as a result it was suggested that it be moved here.
As support for your issue already started on your previous thread I don't see why it would be more effective to split the effort... So I merge the two and if you think getting more support in general support and not pixel 3a support section then so be it...
What about my suggestion for trying telegram support channel ?
-
K Keneda moved this topic from Google Pixel 3a/3a XL
-
@lduboeuf said in Significant Battery Drain with Wi-Fi Enabled on Pixel 3a:
@furkanonder Can you give some context, like which version you have, is there anything that you've installed, or any app in background that does not suspend ( via UT Tweak Tool ).
Maybe try on RC ?OS: Ubuntu Touch 20.04(OTA-4)
Build details
OS update channel: 20.04/arm64/android9plus/stable
OS build number: OTA-4
Kernel: 4.9.124-geb83cc0ec835-ab545 (arm64)
Build ABI: arm64-little_endian-lp64
Device image part: 20231223-26259
Device build description: lineage_sargo-userdebug 9 PQ3A.190801.002545 test-keysWhat do you mean RC?
-
@Keneda said in Significant Battery Drain with Wi-Fi Enabled on Pixel 3a:
What about my suggestion for trying telegram support channel ?
I mentioned this on the telegram channel, but there is no solution yet.
-
@furkanonder said in Significant Battery Drain with Wi-Fi Enabled on Pixel 3a:
What do you mean RC?
RC is for "release candidate".
It defines a pre stable testing channel available on any device that has stable channel.@furkanonder said in Significant Battery Drain with Wi-Fi Enabled on Pixel 3a:
OS update channel: 20.04/arm64/android9plus/stable
OS build number: OTA-4Here is something not normal.
Actually a device running 20.04 stable channel should be on OTA5.See here, the last RC version is testing pre stable OTA6 (A.K.A. OTA6 "RC"):
https://forums.ubports.com/topic/10475/call-for-testing-ubuntu-touch-20-04-ota-6/Another thing that bothers:
@furkanonder said in Significant Battery Drain with Wi-Fi Enabled on Pixel 3a:
Device build description: lineage_sargo-userdebug 9 PQ3A.190801.002545 test-keys
Your device should have this android version installed before installing Ubuntu Touch on it :
Make sure to revert to factory image PQ3B.190801.002 before continuing.
See here :
-
A arubislander forked this topic
