Hi

I'm a bit confused on how I should transmit IR code via android devices.
I have this pronto hex for example:
9000, 4500, 560, 565, 560, 565, 560, 565, 560, 565, 560, 565, 560, 565, 560, 565, 560, 565, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560, 565, 560, 1690, 560, 565, 560, 565, 560, 565, 560, 565, 560, 565, 560, 565, 560, 1690, 560, 565, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560

which I know it should be sent with frequency of 38hz, as is.

on the other hand, I see this example in here:
[Link: stackoverflow.com]

which basically says that with the above IR code.
I need to manipulate the data and turn it into pulses or duration and only then to transmit the IR code.

can someone please help me to understand when I need to manipulate the pronto code and when I can send it as is?

in this project:
[Link: github.com]

they even do some more manipulation to get the frequency from the pronto hex code

and after running their algorithm on my pronto code I get something like this:
1376 5776 1376 1381 1376 1381 1376 5776...
which I try to send through the consumerIrManager which I guess is wrong...

question num 2:
should I treat differently pronto codes one looks like this:
(1#)
9000, 4500, 560, 565, 560, 565, 560, 565, 560, 565, 560, 565, 560, 565, 560, 565, 560, 565, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560, 565, 560, 1690, 560, 565, 560, 565, 560, 565, 560, 565, 560, 565, 560, 565, 560, 1690, 560, 565, 560, 1690, 560, 1690, 560, 1690, 560, 1690, 560

and the other like this:
(#2)
0000 006C 0022 0002 015B 00AD 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0016 0016 0041 0016 0016 0016 0041 0016 0041 0016 0041 0016 0016 0016 0016 0016 0041 0016 0016 0016 0041 0016 05F7 015B 0057 0016 0E6C

because if I run the algorithm on the second pronto here (#2) I get somethinglike this that looks valid:
frequency turns out to be 36044~
and the pattern: 432 432 432 432 864 ...