[BUG?]Screen backlight turn on on SIP Keep alive

[Kaya84]

Hi,
I upgraded a YEALINK T21P-e2 firmware to latest one ( 52.81.0.110 ) and the backlight bug suddenly appeared (referring to http://forum.yealink.com/forum/showthrea...ode=linear ).

Going deep to the problem, i put syslog to level 6 and noticed:

Quote:<132>Jul 13 14:54:43 sys [967]: POFF<4+warnin> PC Cable connected
<134>Jul 13 14:54:43 sys [967]: SRV <6+info > get port 2 speed 10
<133>Jul 13 14:54:43 ipvp[1286]: IPVP<5+notice> 683.402.278:Message=0x00020000(0x00000001+0x00000002+0)
<134>Jul 13 14:54:43 ipvp[1286]: IPVP<6+info > 683.402.607:unknown msg,0x00020000,from 0xd28f9304 0x00000001, 0x00000002
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > BackLightManager::AddEvent [1]
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > objEvent.eType == BACK_LIGHT_DEFAULT || objEvent.brightTimer == 0
<134>Jul 13 14:54:43 Log [1313]: IDLE<6+info > [Network] OK
<134>Jul 13 14:54:43 sua [1151]: APP <6+info > [SIP] <IPC_rcv >:msg:0x00020000, wparam:0x00000001, lparam:0x00000002, id:Undefied on dspg
<134>Jul 13 14:54:43 Log [1313]: IDLE<6+info > CStatusManager: Notify Status Changed m_isOn=[1] [0]
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > BackLight Earse Event(4)
<134>Jul 13 14:54:43 Log [1313]: DIR <6+info > Directory: message(0x20000), wparam(0x1), lparam(0x2)
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Operation[1] to power saving
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]CPowerSavingManager::GetTimeoutOfOperation(1, 1499964883)
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Time[1499964883]: day=3, hour=16
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Time range: 1499929200~1499972400 type=0
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Timeout to power saving: 1500022483, interval=57600
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Time[1499972400]: day=3, hour=19
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Next time range: 1499972400~1500015600 type=1
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Timeout to power saving: 1499965483
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Timeout to power saving: 1499972400
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Timeout[1499972400] less than original timeout[1499972400], will not change.
<134>Jul 13 14:54:57 sua [1151]: DLG <6+info > [000] cb_nict_kill_transaction (id=358)
<134>Jul 13 14:54:57 sua [1151]: FSM <6+info > [000] free transaction ressource 358 0b8444c6210f580409e6ff6e5c60e718
<134>Jul 13 14:54:57 sua [1151]: FSM <6+info > [255] free nist ressource
<134>Jul 13 14:54:58 sua [1151]: DLG <6+info > [255] SIP: 192.168.4.2:5060 Keep Alive sent on UDP!
<134>Jul 13 14:55:03 Log [1111]: WEB <6+info > URI: /servlet?p=login&q=loginForm&jumpto=status
<134>Jul 13 14:55:03 Log [1111]: WEB <6+info > such session have invalidate,will to create a new session
<134>Jul 13 14:55:05 Log [1111]: WEB <6+info > URI: /servlet?p=login&q=getsessionid&Rajax=0.966261073536159
<134>Jul 13 14:55:05 Log [1111]: WEB <6+info > such session have invalidate,will to create a new session
<134>Jul 13 14:55:05 Log [1111]: WEB <6+info > such session have invalidate,will to create a new session
<134>Jul 13 14:55:05 Log [1111]: WEB <6+info > sessionNum: 6
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > URI: /servlet?p=login&q=login
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > Crypto get plain data : session id is equal
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > ip:192.168.4.99 Login at time=1499957706
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > ip:192.168.4.99 The password is right!
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > ip:192.168.4.99 Login in Success At time: [17035]
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > URI: /servlet?p=status&q=load
<134>Jul 13 14:55:06 Log [1313]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 2. result[2]
<134>Jul 13 14:55:06 Log [1111]: ETLL<6+info > mkit_call return(2,0)
<134>Jul 13 14:55:06 Log [1313]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 65537. result[65537]
<134>Jul 13 14:55:06 Log [1111]: ETLL<6+info > mkit_call return(65537,0)
<134>Jul 13 14:55:06 Log [1313]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
<134>Jul 13 14:55:06 Log [1111]: ETLL<6+info > mkit_call return(0,0)
<134>Jul 13 14:55:08 Log [1111]: WEB <6+info > URI: /servlet?p=settings-preference&q=load
<134>Jul 13 14:55:09 Log [1111]: WEB <6+info > URI: /servlet?p=settings-config&q=load
<134>Jul 13 14:55:12 Log [1111]: WEB <6+info > URI: /servlet?p=settings-config&q=exportLocalLog&type=1
<134>Jul 13 14:55:12 Log [1111]: WEB <6+info > Partition free(byte): /tmp/ [32448512], /config/ [86016], /data/ [86016]
<134>Jul 13 14:55:13 Log [1313]: BKLT<6+info > OnTimerOut InactiveLevel[0]
<134>Jul 13 14:55:13 Log [1313]: BKLT<6+info > PowerSaving_IsInPowerSavingMode [0]
<134>Jul 13 14:55:13 Log [1313]: BKLT<6+info > BackLight Set light(0)

So, what can be the problem that turn on and off backlights?

Thk!