I am raising this observation again, as it seems to happen very frequent for slow device on first launch immediately after the apk is installed. The stanza request seems not specific but generally is on system startup after installation. Not sure if this is due to large amount of Omemo data need to be process during system up, as I do not remember such frequent reply timeout before implementing Omemo.
See also:
Smack 4.2.1-beta2-SNAPSHOT: No response received within reply timeout even when reply is received well within the specified PacketReplyTimeout.
Smack Omemo Identities Regenerate failed on slow android device due to reply timeout
=============== aTalk logcat capture on Sony Xperia Tablet S ================
08-25 09:19:24.450 E/αTalk: [14] org.jivesoftware.smack.roster.Roster.processException() Exception reloading roster
org.jivesoftware.smack.SmackException$NoResponseException: No response received within reply timeout. Timeout was 10000ms (~10s). Waited for response using: IQReplyFilter: iqAndIdFilter (AndFilter: (OrFilter: (IQTypeFilter: type=error, IQTypeFilter: type=result), StanzaIdFilter: id=0ibal-113)), : fromFilter (OrFilter: (FromMatchesFilter (full): null, FromMatchesFilter (ignoreResourcepart): smith476@atalk.org, FromMatchesFilter (full): atalk.org)).
at org.jivesoftware.smack.AbstractXMPPConnection$7.run(AbstractXMPPConnection.java :1560)
…
08-25 09:21:37.420 D/SMACK: SENT (0): BckyQ4ns69pHmGYCVndH3uG41d1r4l/sm8xngtt6GTtr</signedPreKeyPu blic>bxomkKsXqZstMjOSepmsgUp4iulcaCNDg0K5Y40NJtZLMi5fnCou mst3T4a5HMuV22DrtuTcePsQMLSSBQLojA==BaYfEh9 Rp5HJDsSROw4MIW84Ub1tkyEhEf1BFZ1pARtU<preKeyPublic
…
preKeyId=‘37’>BVvzWjAJlRIwDPh1tcy/PhsANiqSP6/pYW8KrFChdM9UBYMYj8B0UQic6xwPqlEPdKgan3gRFmS6Yxvy+rrjMA4ABfBOWPLFT62aTCNlKE
08-25 09:21:37.650 D/SMACK: SENT (0): <iq id='0ibal-113’ type=‘get’>30a1591ab3403f8842d938ebc363db39789de62548</ph oto>
08-25 09:21:43.380 D/SMACK: RECV (0):
08-25 09:21:43.410 D/SMACK: RECV (0):
08-25 09:21:43.410 D/SMACK: RECV (0):