AVR Freaks

If your BT devise are configured to act as simple wireless UARTs then data transmission after Reset, Discovery, Bonding, and SPPConnecting is straightforward.

 Ok so there is a mode to enter, I do not see it in the data sheet or the tons of write ups?

This is an extremely common device. No one here has heard of the HC-05  and HC-06 ? They are often both used in slave to slave when it is not important to have a server. It uses AT commands to set up but those commands also come out from the  connected device. I communicate via UART to it and that just echos over the BT.

Sure but that is basically the entire reason for me asking any of this?  I have found a lot of write up on this device, and many examples but they all send characters.  This is not what I'm asking for. 

No, it's just the initial 'AT' that does the commands, but you did bring up a good point, I could always do a 2 byte. That gives me 8 bits for a control mask to signal other things as well, I like that idea. 

Also I guess having the module is my main problem because when you said pin 34 I was thinking huh?

I guess this may be the state pin (6)?

Can you actually define in engineering terms what "not allow" and "gets all mad" actually means in this context ??

  My best guess is that the receiver (android) sees 0 as a null and thus crashes the implementation.

avrcandies, that helps thx.

jgmdesign, the issues was the command state. Your just not following the flow of the topic here, you addressing my original question after the answer was given. In other words we already know what the problem was.

Thx for all the answers.

I understand that but I'm not the android developer as was pretty much told 0's are not going to fly. My weight in this case is not enough to change that. If he posts the issue on stack overflow ill link it ;) But the AVR side is fine, I can send all 0-255 data with no issues. but also keep in mind that the issue here is that the BT chip seems to be in command mode and is echoing all the data to the other BT device. My android developer took the day off so, we wait. 

Well my question was more of a, am I doing this right? Am I missing something.  That more then a problem I need to fix.  

 One way is binary to ASCII so 12345 becomes "12345" and so on. But it's quite wasteful of data bandwidth. 

 This is what I meant in my initial post when I said. 

Now I'm thinking this was a bad idea and maybe I need to send strings like '0x00' ...'0xff' but that is going to take a long time to send 64 bytes for example. 

Your other idea is a fine idea along with the sending two bytes for one byte posted earlier. My colleague suggested delimiters. I guess that could work but I favor the two byte or the trick you mentioned.  I guess from my perspective I was hoping there was an AT command for sending data.  "AT+sendd0d1d2d3d4d5d.... Though it arrears I am limited to sending via the UART one charter at a time (or a string of) and as many point out data is data. The Android is the issue in this case and maybe the entire issue here. Strange things are happening. 

examples.

1) I can not send a 0 as it has issues with that.

2) I need an end character and some times it sees this end charter in the string where it does not exist. 

3) Data sends over randomly. It changes when I send the same data. If I send 1,2,3,4,5 I get 1,2,3,4,120 or 1,2,3,120,4.

Not being able to develop on the android side is certainly not helping. I'm being asked to send the data as strings but from a bandwidth point of view that is horribly wasteful. Though I'm in that battle of well, it works with other BT device.... So it's a question of am I doing it right and as far a I can tell, I am. I think the android developer needs to learn how to handle data but he says I'm doing it just like everyone else....Yet he says thigns like maybe I should convert decimal to hex... I'm thinking.. wow, this is what I'm working with?

Anyways, not looking for help there, just wanted to make sure I was not over looking something here. I assumed In practices there is nothing wrong with me sending data over UART. A 0 is a 0 is a 'null' and that is that. Maybe more info then was needed at this point but this is the problem I'm dealing with. 

I also just notice there are hc-06 and 05's and one or the other his this AT command button on it. I'm going to assume if the button is not pressed or in the case where it is absent there is a pull down resister holding it low. So in all cases it must be in so called data mode. Maybe the AT command I use are echoing on the Android and causes the issues, not sure? More to look in to now.

I think uuencode will work and I'm sure there is a library for them android types ;)

Ok, LOL, let me put this literal then...

The guy coding the Android is a pain in the ass millennial, know it all shit heat, that does not understand simple concepts, and thinks his yourtube channel knows everything (thus he does) and I know jack shit.. Trying to help him leads to I know what I'm doing... So I mean I can not even get to the code let a one Debug on it. 

I do my part he does his..