FW 1.2.52 goes into sleep mode okay using ~ 2.7mA however the Battery read out is not correct - reading low.
FW 1.2.53 fixes the battery reading however the unit is not going to sleep.
Correction for wrong battery display on tlora_v2_1_16 board by @costonisp in #1120
With the display on I am seeing ~ 53 mA .The display does turn off ~ 47mA but then the Bluetooth Light keeps flashing and the unit will not go to sleep after 300 seconds
Any one else having this issue?
For version 1.49 I am reading about 14 mA in sleep mode.
The Android app does have the option - isAlwaysPowered which I have still unchecked.
So if version 1.2.52 goes to sleep and only consumes 2.7mA in sleep mode and 1.2.53 won’t sleep then something else was changed accidentally?
1.2.52 and forward does not do the “device is connected but sleeping” thing in android anymore. Are you sure you are using the right version of the heltec firmware for you battery pins?
also, if you are interested in better understanding what the device is doing under the hood, consider capturing the serial log via USB cable. this can be easily done installing VSCode and platformio plugin, but there are many options, even putty works.
Yes - I have the Heltec V2.1(with the diagonal cap).
I just upgraded my Android App from 1.2.52 to 1.2.55.
Under advanced settings I tried the slider both ways for the device sleep period of 300 in seconds.
For FW 1.2.52 it goes to sleep. For 1.2.53 the screen turns off after 1 minute but then it never goes to sleep.
I just got another board from Amazon - I am going to try it tonight - I did have a board in the past that the divider for the battery was off.
The defaults in firmware 1.2.52 and beyond are the best experience, they will override previous settings. You don’t want to add back that problematic sleep behavior
I’m confused… I’m seeing a much higher power drain on portable, battery-powered T-Beams since 1.2.52 (default settings), hence I’m reluctant to upgrade remote, solar-powered nodes whose power budget relies on sleep mode.
I didn’t notice a “problematic sleep behavior” before 1.2.52, so I’m a bit concerned.
The problematic “the device is connected but sleeping” functionality has been removed as default, there is no BLE sleep state the radio is off and messaging fails to work until the button on the device is pressed. You can turn it back on with is_power_saving in configuration, but remote nodes should be set as routers with BLE off, so not sure how this would have impacted any router nodes.
Oh I see, I must have misunderstood! Yes, this change makes sense.
I’ll investigate the higher-than-before battery drain I’m experiencing to see whether it’s in line with that.
After some days of testing, I’m happy to report a massive improvement in usability due to the Bluetooth sleep off by default! Much much better now, cheers!