CannedMessage module function (keys) are missing currently.

The BQ27220 does not provide useful information.

OperationConfigA Values:0x0
External Thermistor Selected: NO
BATT_GD Pin Polarity High: NO
BATT_GD Function Enabled: NO
Can Enter SLEEP State: NO
slpwakechg Function Enabled: NO
Write Temperature Function Enabled: NO
Battery Insertion Detection Enabled: NO
Battery Insertion Pin Pull - Up Enabled: NO
Pin Function Code (PFC) Mode: 0
Wake - Up Function Enabled: NO
Wake - Up Threshold 1: 0
Wake - Up Threshold 0: 0

OperationConfigB Values:0x0
Default Seal Option Enabled: NO
Non - Removable Option Set: NO
INT_BREM Function Enabled: NO
INT_BATL Function Enabled: NO
INT_STATE Function Enabled: NO
INT_OCV Function Enabled: NO
INT_OT Function Enabled: NO
INT_POL Function Enabled (High - Level Polarity): NO
INT_FOCV Function Enabled: NO

Standard query:
        - AtRate:0 mA
        - AtRateTimeToEmpty:0 minutes
        - Temperature:-273.15 ℃
        - BatteryVoltage:0 mV
        - InstantaneousCurrent:0 mAh
        - RemainingCapacity:0 mAh
        - FullChargeCapacity:0 mAh
        - DesignCapacity:0 mAh
        - TimeToEmpty:0 minutes
        - TimeToFull:0 minutes
        - StandbyCurrent:0 mA
        - StandbyTimeToEmpty:0 minutes
        - MaxLoadCurrent:0 mA
        - MaxLoadTimeToEmpty:0 minute
        - RawCoulombCount:0 mAh
        - AveragePower:0 mW
        - InternalTemperature:-273.15 ℃
        - CycleCount:0
        - StateOfCharge:0 %
        - StateOfHealth:0 %
        - RequestChargingVoltage:0 mV
        - RequestChargingCurrent:0 mA
        - BTPDischargeSet:0 mAh
        - BTPChargeSet:0 mAh

Operation Status:
        - getIsConfigUpdateMode:NO
        - getIsBtpThresholdExceeded:NO
        - getIsCapacityAccumulationThrottled:NO
        - getIsInitializationComplete:NO
        - getIsDischargeCycleCompliant:NO
        - getIsBatteryVoltageBelowEdv2:NO
        - getSecurityAccessLevel:0
        - getIsCalibrationModeEnabled:NO

Battery Status:
===============================================

TCA8418 treatment is a bit better but still needs some work.
There is a modifierFlag variable for the modifier keys, so the TCA8418TapMap can have 7 columns.
Shift: modifierFlag bit 1
alt: modifierFlag bit 2
Sym: modifierFlag bit 3
src_input.zip
The formatting needs a little tweaking. . :)

I can confirm that this is somewhat working today, as-is. Keyboard input is very slow and the shift keys don't work (but you can double-tap a letter to make it caps). Backspace and enter work. You can send and receive messages through the radio.

It's not polished yet, but it does actually function as a standalone device with keyboard, screen, radio, and buzzer notifications.

This is awesome. My little TDP is alive and usable for the first time now! Thank you both for getting it to this point!

I can confirm that this is somewhat working today, as-is. Keyboard input is very slow and the shift keys don't work (but you can double-tap a letter to make it caps). Backspace and enter work. You can send and receive messages through the radio.

It's not polished yet, but it does actually function as a standalone device with keyboard, screen, radio, and buzzer notifications.

This is awesome. My little TDP is alive and usable for the first time now! Thank you both for getting it to this point!

Try the contents of the zip file. The code is a bit messy but it works better. Shift, alt, Sym too.

These firmware updates are for the T-Deck Pro "4G" version or the "voice" version? Or is it irrelevant?
Thank you.

@Szetya Yep, that's a nice improvement.

@adrianTNT I'm using it on the 4G.

@adrianTNT It is irrelevant at the moment because neither option is supported. It will probably have to be split later as it uses common PINs.

Has anyone disassembled it yet? 😉 LTR553ALS location found? I ordered from aliexpress. Also plan on installing a BME280 or BME688 once I take the time.

@Nasimovy
You may try if the refactored class is still working with your keyboard device 😅

@Nasimovy You may try if the refactored class is still working with your keyboard device 😅

WAO! I'll look at this tomorrow on t-deck pro. The value of modifierFalg can be up to 7 at the moment (shift + alt + sym) so the tapMap array can be up to 7+1 columns. There are plenty of possibilities to handle special events or use special characters. And the two shifts can be handled separately and then 15+1 combinations are possible for each key (which is a lot) 😂
(The t-lora pager is coming soon. Version 868MHz is already available on the official site (ordered today))

WAO! I'll look at this tomorrow on t-deck pro. The value of modifierFalg can be up to 7 at the moment (shift + alt + sym) so the tapMap array can be up to 7+1 columns.

I tried to use the same keys as on the T-Deck with quite similar behavior. The only difference is that instead of ALT+C - key now can use ALT+key directly.

TCA8418 is capable of requesting 3 buttons at once (under certain matrix rules) which is not currently used and I don't think it is needed. Currently shift increases the modifierFalg value by 1, alt by 2 and sym by 4. Before the _TCA8418_MULTI_TAP_THRESHOLD time expires, the modifier keys can be pressed in sequence to use different combinations e.g. shift & alt & key. Which gives the index of the third key of tapMap.
It would be a good idea to have some information about the state of the modifierFalg on the display but the top line of the display is full.

TCA8418 is capable of requesting 3 buttons at once (under certain matrix rules) which is not currently used and I don't think it is needed. Currently shift increases the modifierFalg value by 1, alt by 2 and sym by 4. Before the _TCA8418_MULTI_TAP_THRESHOLD time expires, the modifier keys can be pressed in sequence to use different combinations e.g. shift & alt & key. Which gives the index of the third key of tapMap. It would be a good idea to have some information about the state of the modifierFalg on the display but the top line of the display is full.

I've modified all this already, i.e. implemented the multi-key press and removed the long press which we don't use on T-Deck. I guess nobody wants to press more than one modifier key in sequence which would also simplify the logic and the programming.
What is currently not working is that the shift key can be held while typing a series of capital alphabetic characters. Looks like an issue with the modifier state.
From what you are suggesting I assume you've never worked with a T-Deck, right?

TCA8418 is capable of requesting 3 buttons at once (under certain matrix rules) which is not currently used and I don't think it is needed. Currently shift increases the modifierFalg value by 1, alt by 2 and sym by 4. Before the _TCA8418_MULTI_TAP_THRESHOLD time expires, the modifier keys can be pressed in sequence to use different combinations e.g. shift & alt & key. Which gives the index of the third key of tapMap. It would be a good idea to have some information about the state of the modifierFalg on the display but the top line of the display is full.

I've modified all this already, i.e. implemented the multi-key press and removed the long press which we don't use on T-Deck. I guess nobody wants to press more than one modifier key in sequence which would also simplify the logic and the programming. What is currently not working is that the shift key can be held while typing a series of capital alphabetic characters. Looks like an issue with the modifier state. From what you are suggesting I assume you've never worked with a T-Deck, right?

For me, it was not uncomfortable to press several buttons in a row during my tests. The beauty of it all is that you can approach the same thing in different ways. 😉
I have no problem with your solution, that's not why I wrote it. I haven't tried your version yet (I'll take the time this afternoon).
I have a first generation t-deck but I don't use it.

TCA8418 is capable of requesting 3 buttons at once (under certain matrix rules) which is not currently used and I don't think it is needed. Currently shift increases the modifierFalg value by 1, alt by 2 and sym by 4. Before the _TCA8418_MULTI_TAP_THRESHOLD time expires, the modifier keys can be pressed in sequence to use different combinations e.g. shift & alt & key. Which gives the index of the third key of tapMap. It would be a good idea to have some information about the state of the modifierFalg on the display but the top line of the display is full.

I've modified all this already, i.e. implemented the multi-key press and removed the long press which we don't use on T-Deck. I guess nobody wants to press more than one modifier key in sequence which would also simplify the logic and the programming. What is currently not working is that the shift key can be held while typing a series of capital alphabetic characters. Looks like an issue with the modifier state. From what you are suggesting I assume you've never worked with a T-Deck, right?

For me, it was not uncomfortable to press several buttons in a row during my tests. The beauty of it all is that you can approach the same thing in different ways. 😉 I have no problem with your solution, that's not why I wrote it. I haven't tried your version yet (I'll take the time this afternoon). I have a first generation t-deck but I don't use it.

If you take a look at the meshtastic map of Hungary, you will understand why you don't need a qwerty device. It's currently a hobby for some crazy people. 😂 No good infrastructure and no good coverage. Also 433MHz and 868MHz devices are very mixed. Chances are high that messages will not reach their destination.

At what point do we call this good enough to merge, then start adding incremental PRs to smooth out the remaining issues?

(I say "we" as if I wrote a single line of this, which I did not. 😀)

At what point do we call this good enough to merge, then start adding incremental PRs to smooth out the remaining issues?

I would say when the biggest show stoppers are gone. Otherwise we'll get a sh*t storm of bug reports for the things we know already.

Personally - I just compiled and flashed the "latest" version - based on 2.7.2 - and the battery reporting issues are still happening - some functionality is absolutely better - but there's clearly more work to do - otherwise - yeah - there's gonna be a slurry of bug reports.

It DID report it was charging when I first turned it on after this update - but the previous behavior has returned. (This is with an "update" rather than a full erase mind you) - if this has been fixed and I am doing something wrong - by all means call me out. lol

@mverch67 Thanks for this!

Okay - just rebuilt and flashed your changes to the 4G variant I have here - my I2S variant is coming soon.

So far - the unit at first boot is reporting that it is plugged in (the plug notification - not battery and charging) - and is not changing from that state for quite a while - so far it still has not changed, and it has been about 15 minutes. This is obviously because it was just plugged in via USB for flashing - but it is not showing that it is on battery coming out of that state.

After a forced reboot - same thing - still reporting plugged in.

Now - I just plugged in the device to a simple power only USB after that to try and "trick" it into resetting the charging notification... and the device reboot itself.

After the random reset (after being plugged in) - it now shows a charging icon, and charging appears to be working.

Unplugging from that now properly shows that it is on battery.

SO - it works - mostly! There's some wonkiness in the first cycle, and the reporting percentage when it's charging versus what it actually has (mine is saying 42% when off battery - but it says it's at 60% when charging until I unplug it - so there's a pretty wide discrepancy there of 20-30% between what it reports while charging versus what it reports on battery... I will see if it gets to 100% on charging and then take it off the charger to see if that corrects the issue or if it's still reporting low when taking off charge.

I'll report back in a bit.

Cheers!

@mr-tbot

If you've ever flashed one of the previous firmware versions you need to either remove the battery or let it completely run empty (until it does not wake up anymore), otherwise the PMM will not be reprogrammed correctly. That's why you saw that device is not charging.

Copy - I will just let it run down today and cycle it.

In my instance - coming from a previous build - leaving it at 100% for a while it's now aligned in it's reporting initially - but in a couple minutes it's already down 2% - so - I almost guarantee it's the calibration like you said.

thanks!

So - little follow-up here.

Fully charged my 4G variant - either it takes a while to realize it's unplugged - or is not detecting properly - detects after a reboot.

My battery life on this unit is not on par with what I would expect from an e-ink device - my t-deck plus lasts considerably longer... at least in my case so far. Once my I2S variant comes in I'll do a side by side battery test...

Looking forward to further updates!

I've been experimenting with this build too. So far battery charging appears to be working after I let it run down completely, but can't really comment on expected battery life yet.

I have however been struggling to get the device to broadcast messages a lot, seems to have very poor signal. It also appears to be sending hi/bye messages on sleep and wake?

There's also an off-by-one error on the eink refresh with it not triggering an update on quite a few of the screens including when typing in free text messages it always misses the last pressed character in the update. Similarly disconnecting charging cable does not update until the next input.

Good to see things making progress though!

@mr-tbot

I would expect from an e-ink device - my t-deck plus lasts considerably longer... at least in my case so far.

This is probably because you are running the T-Deck Pro with BT on but T-Deck Plus with BT off? If so I suggest to disable BT on the Pro and then compare the runtimes.
Also device role should be same (ideally client mute if you are indoors).

In the LilyGo T-Deck main menu it is not visible where the device is connected, the name of the connected device could be added to the fifth icon from the top, where it is - signal status. Thank you. Mirarak

In the LilyGo T-Deck main menu it is not visible where the device is connected, the name of the connected device could be added to the fifth icon from the top, where it is - signal status. Thank you. Mirarak

Sorry, you're wrong here. This PR is for T-Deck Pro...

I2S version arrived today - so I have both variants now for testing! =)

Compiled and tested, works great!
Yet I'm wondering if the standard ui is the best choice and even if it is the navigation is not so great tbh

maybe move the variant dir to the new structure before merging?

@mverch67
e.kbchar same in the following lines:

I flashed my T-Deck Pro with the latest alpha. First I tried a full erase with the UI, and upon rebooting the keyboard led came on and started to flash, which is the first sign of life I have seen on this device since I let the battery run down months ago. But the display never changed, just flashing led. Then I tried again without the Mesh UI, and the device rebooting with the vibration motor going non-stop. Encouraging that this has an effect on the device, but not working for me yey. Any advice?

I flashed my T-Deck Pro with the latest alpha. First I tried a full erase with the UI, and upon rebooting the keyboard led came on and started to flash, which is the first sign of life I have seen on this device since I let the battery run down months ago. But the display never changed, just flashing led. Then I tried again without the Mesh UI, and the device rebooting with the vibration motor going non-stop. Encouraging that this has an effect on the device, but not working for me yey. Any advice?

Did you put the device into DFU mode before flashing?