Android bluetooth news broadcast time delay problem-CodePudding

Excuse me, I in bluetooth information to get the message there is always a certain delay, delay time of different mobile phones each are not identical, fast 50 ms delay, slow 500 ms delay, want no delay is there a way to get news?

CodePudding user response:

500 ms an exaggeration, you are a traditional bluetooth or BLE, I met some BLE mobile transmission interval less than 50 ms cannot be accepted. No delay should be could not have a system and the hardware that determines, unless it is your own code to handle the long

CodePudding user response:

reference 1st floor yung7086 response:

500 ms an exaggeration, you are a traditional bluetooth or BLE, I met some BLE mobile transmission interval less than 50 ms cannot be accepted. No delay should be could not have a system and the hardware that determines, unless it is your own code to handle the long

BLE, receipt write soon, only receives the message delay,

CodePudding user response:

refer to the second floor qumoy response:

Quote: refer to 1st floor yung7086 response:

500 ms an exaggeration, you are a traditional bluetooth or BLE, I met some BLE mobile transmission interval less than 50 ms cannot be accepted. No delay should be could not have a system and the hardware of this decision, unless it is your own code to handle the long

BLE, receipt write soon, the presence of delay, just receive a message

BLE have try using the phone more anyway, it is all sorts of problems, such as one of my vivo, send disconnected at a time, I nearly got disconnected callback code, but the equipment is always delayed three or four seconds to begin to disconnect, I meizu sending interval less than 50 ms can appear nestlings, but you say to accept the message delay, from when to begin to calculate time, from the equipment to your code inside take 50-500 ms word is normal, transmit to must be to time consuming

CodePudding user response:

BLE I think itself is not suitable for real-time environment, because the amount of data transferred is very small, a little bit big for basic need subcontract transmission of data, is bound to lead to delay, suggested by comparing the way to determine whether BLE transmission delay caused by itself, or is caused by writing code takes longer, if it is in itself a bluetooth transmission delay length, or advice in place to wait for a little bit about the packet, itself not take a BLE for two years, I don't know right, anyway, before we sit BLE is short of real-time communication, and a little bit far packet loss serious, finally gave up using BLE transmission mode

CodePudding user response:

reference 1st floor yung7086 response:

500 ms an exaggeration, you are a traditional bluetooth or BLE, I met some BLE mobile transmission interval less than 50 ms cannot be accepted. No delay should be could not have a system and the hardware that determines, unless it is your own code to handle the long

reference yung7086 reply: 3/f

Quote: refer to the second floor qumoy response:

Quote: refer to 1st floor yung7086 response:

500 ms an exaggeration, you are a traditional bluetooth or BLE, I met some BLE mobile transmission interval less than 50 ms cannot be accepted. No delay should be could not have a system and the hardware of this decision, unless it is your own code to handle the long

BLE, receipt write soon, the presence of delay, just receive a message

BLE have try using the phone more anyway, it is all sorts of problems, such as one of my vivo, send disconnected at a time, I nearly got disconnected callback code, but the equipment is always delayed three or four seconds to begin to disconnect, I meizu sending interval less than 50 ms can appear nestlings, but you say to accept the message delay, from when to begin to calculate time, from the equipment to your code inside take 50-500 ms word is normal, transmit to must be to time consuming

Delay time are instructions issued to receive the reply after this period of time, take the time from inside the callback function between there is a delay, feel to solve this problem only from the bluetooth chip level, application side can only be optimized,