Fix Meshtastic#80: Increase screen timeout to 5 minutes

Merge upstream

Update

Added Beginner's Guide

Merge from original repo

Resync with Upstream

merge from original repository

* fix assertion failure
```
22:57:36 64409 [PositionPlugin] FIXME-update-db Sniffing packet
22:57:36 64409 [PositionPlugin] Delivering rx packet (id=0x5851f437 Fr0xa1 To0xff, WantAck0, HopLim3 Ch0x0 Portnum=3 rxtime=1628895456 priority=10)
22:57:36 64409 [PositionPlugin] Forwarding to phone (id=0x5851f437 Fr0xa1 To0xff, WantAck0, HopLim3 Ch0x0 Portnum=3 rxtime=1628895456 priority=10)
22:57:36 64409 [PositionPlugin] Update DB node 0x85f4da1, rx_time=1628895456
22:57:36 64409 [PositionPlugin] Plugin routing considered
22:57:36 64409 [PositionPlugin] Add packet record (id=0x5851f437 Fr0xa1 To0xff, WantAck0, HopLim3 Ch0x0 Portnum=3 rxtime=1628895456 priority=10)
22:57:36 64409 [PositionPlugin] Expanding short PSK #1
22:57:36 64409 [PositionPlugin] Installing AES128 key!
22:57:36 64409 [PositionPlugin] enqueuing for send (id=0x5851f437 Fr0xa1 To0xff, WantAck0, HopLim3 Ch0xb1 encrypted rxtime=1628895456 priority=10)
22:57:36 64409 [PositionPlugin] (bw=125, sf=12, cr=4/8) packet symLen=32 ms, payloadSize=22, time 2596 ms
22:57:36 64409 [PositionPlugin] txGood=6,rxGood=10,rxBad=0
22:57:36 64409 [PositionPlugin] AirTime - Packet transmitted : 2596ms
22:57:36 64409 [RadioIf] assert failed src/mesh/RadioLibInterface.cpp: 240, void RadioLibInterface::handleReceiveInterrupt(), test=isReceiving
```

Radiolib sync upstream

Patch 1

Pull master

* Tryfix: Local replica for build problem

* Update platformio.ini

* use the real repo again

* BRC 2024 Golden Spike Data

* Configurable units, based on pull #1

Not exactly the same change; the interim number must be feet for use with golden spike data as-is.

* update meshtastic 2.6 with BRC 2025 Golden Spike

* add performance improvements

* fixed roads + script to make roads

* refactored string generation to allow getting hour & street separately for multi-line display

* Display BRC location on self location page

* formatting fixes via `trunk fmt`

* Show BRC location of favorite node

---------

Co-authored-by: Gaetan Gueraud <exadeci@gmail.com>

* BRC 2024 Golden Spike Data

* Configurable units, based on pull #1

Not exactly the same change; the interim number must be feet for use with golden spike data as-is.

* update meshtastic 2.6 with BRC 2025 Golden Spike

* add performance improvements

* fixed roads + script to make roads

* refactored string generation to allow getting hour & street separately for multi-line display

* Display BRC location on self location page

* formatting fixes via `trunk fmt`

* Show BRC location of favorite node

---------

Co-authored-by: Gaetan Gueraud <exadeci@gmail.com>

* BRC 2024 Golden Spike Data

* Configurable units, based on pull #1

Not exactly the same change; the interim number must be feet for use with golden spike data as-is.

* update meshtastic 2.6 with BRC 2025 Golden Spike

* add performance improvements

* fixed roads + script to make roads

* refactored string generation to allow getting hour & street separately for multi-line display

* Display BRC location on self location page

* formatting fixes via `trunk fmt`

* Show BRC location of favorite node

---------

Co-authored-by: Gaetan Gueraud <exadeci@gmail.com>

* BRC 2024 Golden Spike Data

* Configurable units, based on pull #1

Not exactly the same change; the interim number must be feet for use with golden spike data as-is.

* update meshtastic 2.6 with BRC 2025 Golden Spike

* add performance improvements

* fixed roads + script to make roads

* refactored string generation to allow getting hour & street separately for multi-line display

* Display BRC location on self location page

* formatting fixes via `trunk fmt`

* Show BRC location of favorite node

---------

Co-authored-by: Gaetan Gueraud <exadeci@gmail.com>

…cking

When i2c_read_byte() detects NESSO_I2C_FAIL_THRESHOLD (3) consecutive
failures it automatically attempts to recover the bus and logs every step
to Serial so the working config can be identified.

Recovery sequence:
  1. Wire.end() + Wire.begin() at 10/50/100/400 kHz — probe PI4IO (0x43)
     after each to confirm bus is live
  2. If reinit alone fails: 9-pulse manual SCL clocking to free any slave
     holding SDA low mid-transaction, then retry each frequency above
  3. Each step prints [I2C-RECOVERY] lines including per-pulse SDA state,
     result, and a ">>> Report this frequency <<<" line on success

Sample output to paste back:
  [I2C] 3 consecutive failures (last: addr=0x43 reg=0x13 err=2)
  [I2C-RECOVERY] === Attempt meshtastic#1 after 3 consecutive failures ===
  [I2C-RECOVERY] freq=10kHz (10000 Hz) -> FAIL
  [I2C-RECOVERY] freq=100kHz (100000 Hz) -> OK
  [I2C-RECOVERY] SUCCESS with simple reinit at 100kHz
  [I2C-RECOVERY] >>> Report this frequency: 100kHz <<<

https://claude.ai/code/session_018GPndZj6m6bVJmFSvDqMqV

Adds a one-shot diagnostic module (ARDUINO_NESSO_N1 only) that runs a
full hardware scan when KEY2 is held (ALT_LONG event). Results printed
to serial log and shown as an 8-second overlay banner on screen.

Tests covered:
  - KEY2 confirmed by the trigger itself
  - FT5x06 touch (0x38): I2C probe + chip_vendor_id/firmware_id
  - BMI270 accel (0x68): chip ID read (expect 0x24), internal status
  - BQ27220 fuel gauge (0x55): probe + voltage register
  - AW32001E charger (0x49): probe + reg0
  - PI4IO meshtastic#1 (0x43) and meshtastic#2 (0x44): probe + IN_STA (buttons, VIN_DETECT)

Uses raw Wire calls (bypasses variant.cpp failure counter) so probing
a sleeping/absent device does not trigger I2C bus recovery.

https://claude.ai/code/session_018GPndZj6m6bVJmFSvDqMqV