Related
Has anyone tried the remote control software Total Remote with the related infra red transmitter module on the XDA(http://www.griffintechnology.com/griffinmobile/totalremote/index.html)
I am trying it with the XDA II.
To send it works fine, but I am having big trouble to make it learn.
Felipe
More details on this product
I have checked the website but cannot find out more details.
What hardware does the product come with? It looks like a small round "ball" and from the website sounds like it plugs in via the speaker socket.
How does this "ball" attach to the PDA?
Do you have to use the earphone socket on the PDA for the "ball" to work? If so does that mean all sounds are directed through the "ball" and you get no sounds from the PDA until the headphone jack is unplugged?
at least judging from that ipaq picture is does use the audio connector because thats where the ipaqs connector is
Here is what I discovered with my experience using the Total Remote:
1st- Yes it is like a ball with two (they claim) powerfull IR trasmitter (see site)
2nd - Yes it goes on the earphone jack
3rd - Yes you lose the sound while using it. But the you just need to lose the conector a little not take it all off.
4th- Since the conector in the XDA II is proprietary, you will need to buy a special adaptor. I found one at expansys and it work pretty well, plus it is small and is curved, so if you use the standard XDA II case you can bend the wire and conector to the side of the case and plug the TR module, you then can adapt some kind of tape or leather on the side of it to keep it protected and tight with the case.
5th - The software promises to be far better then the pronto from philips. In a matter of fact it comes with a module that let you use the files used on the pronto software but they don´t appear to be as good as thee Total Remote one.
6th - The module and software will work very fine to TRANSMIT and also from a good distance (large rooms)
BUT NOT EVERYTHING IS A SEA OF ROSES: Lets enumerate the bad points.
1st - And most important, the XDA II is not capable of receive any IR signal from any remote controle and I tryed more the 15 , with diferent distances (even with the IR window of the XDA II and the remote controler windows touching each other) and diferent time pressing the buttons. If it can´t receive it cant learn, if it can´t learn it useless, unless you use any of the pre determined profiles, wich I do not because I bought this for customization. And no the module will not work to receive the signals only the IRda port of the XDA II.
2nd - By needing the adaptor you rise the cost of the entire package.
3rd - The Techsupp of Griffing technology is very bad. They do not read my emails with attention, they do not have much interest to solve problems or they are really dumb regarding the matter including their own software and module and they do not force themselves (creativity and imagination) to try a workaround with their customers. Plus they are rude.
BUT there is a possible way around the learning problem. But that involves more then only the Total Remote software and hardware and the XDA II.
I did not tested this yet but I really think this can work.
As I already told you, the Total Remote let us use the pronto files, in a matter of fact it emulate the pronto software.
If you have the software to design the pronto pages, you can do it and also get the right IR codes from the Remotte Central site. There is a very good chance you can get exactly the IR code you will need for each button on your virtual control. So it is not as pratical as learning directly from the remote control, but it is a solution.
But there is a higher level of solution for this too.
If you have a Pronto, Marantz or any other remote controler that use those files on Pronto software and hardware, you can just use it to learn all the IR signals from other controls and then load it on the computer, after that you can access the IR codes from the Pronto design software and aply them to the pages of your new virtual remote that will be loaded to the XDA II and used with Total Remote.
Unfortunatelly you will not be able to use Total Remote, but only the Pronto emulator, wich I think there is some disvantage points like lower page resolution.
If at least the people in Griffin let us aply the IR code from the software , this would make things much better. But I think they are not inclined even to take suggestion.
Hope this helps.
Any questions?
Felipe
Thank you!
It was a very interesting and clear description.
Thank you for taking the time to expain us all of that.
Chris
Thanks for that
Thanks,
That was quite enlightening.
I think I'll hold off on it though. My main use would require learning I think and it sounds convoluted to get it to use these learned commands. I think I'll have to look for something else!
sure i would had liked using my xda2 as a remote but with all that it's more trouble then it's worth
that is so informative,
but its also expensive and INTENSIVE. Clever though it seems, its hard o setup and involves additional hardware. What i would have wished for...Remote Control applications that only uses the existing XDA 2 IR port...if only it could THROW signales that far.
But thanks for the info. I might try it someday, when perfected.
There is hope! This is what I am waiting for!
Hi!
Have a look at this SD to IR remote:
http://www.novii.tv/blaster/
it now works only with PALM (on just with a few model) but the the developer promises he is developing a version for PPC!!!
Chris
chameleon said:
that is so informative,
but its also expensive and INTENSIVE. Clever though it seems, its hard o setup and involves additional hardware. What i would have wished for...Remote Control applications that only uses the existing XDA 2 IR port...if only it could THROW signales that far.
But thanks for the info. I might try it someday, when perfected.
Click to expand...
Click to collapse
Yes unfortunatelly it is an expessive and very complex solution. But at least in part I did not choosed this.
I live outside USA and this make things more complicated.
I first bought the TR, then I discovered that it does not work with the earphone jack.
Since I could not get a refund from the TR because I am not in USA and I still would like to make use of it (even because I had already paid for), I then spent more money with the earphone adaptor.
And for my bad luck, the XDA II did not worked learning those controls.
The complicated part comes from the fact that now I spent more money with two pieces of hardware and since my nature is not to give up expecially with computer things, I then tryed to find another way to make it work. I even took in consideation to remove the actual IRda and substitute it with another kind of IR emitter.
I don´t have much time also but as soon as I get some I will try my theory and let you know if it work.
Meanwhile I really suggest you to buy from another company. It is more cheapper and give less headaches.
Felipe
Have some1 tried to:...
To learn the codes using the biult in IR on the XDA and then replug the thing on the earphones jack to use the remote ?????
It's an obvious thing that may be overlooked.... perhaps ?letme know...
BTW I"m looking for the pin out of the Ir that goes onto the earphone jack as I hava stripped the ir from an IPAQ 2210 and wanna attach it to my XDA IIs....
any advise ???
Here is an interesting link. It seems you can record the "sounds" that infrared emits and utilize it. Although the article refers to ipod it also says it will work with pocket pc and laptop etc. 100 feet range.
http://features.engadget.com/entry/6336778455600767/
ok i have a htc eris and a peripheral ir blaster that connects through the headphone jack can someone make an app that uses this to control tvs and such
who makes it
Is it the total remote made by griffin? Is it the Novii?
Hey guys I am a newbie to app development and I have gotten as far as doing the tip calculator. I am trying to make an intervalometer app based on the ti- calculator app at the link below. Basically, it would use the headphone jack to trigger a camera remote shutter release at a predictable rate for time lapse photography on a Canon DSLR. Here is the TI-83 reference. Any idea how to do this on android. Any help or advice is greatly appreciated.
http://potatoeskillme.com/code/ti-86-intervalometer-for-canon-xti/
Dude, I'm really sorry I'm not skilled enough (yet) to help make this happen.
What a fantastic idea! I would love to see this happen.
Anyone have an idea how to access the audio port in code? I have to close the loop on the headphone jack for an instant and then release it.
You are attacking the wrong hole.
Audio jacks don't behave in the same way as the TI data jack.
Investigate using USB.
I would love to see some sort of wireless control of the camera's basic functions, similar to the hardware wireless control modules for those cameras.
Perhaps easier to accomplish and just as nice would be a way to make the camera a wi-fi storage device for those level Canon cameras. It would be sweet to snap shots to the phone for easy posting to the various places Android supports.
My guess would be that Dalvik (SDK level Code) doesn't have access to hardware level controls.
So this would have to have some Native (NDK Code) in c++ written to make it work. I don't think it would be entirely difficult for someone, but I personally have never tried to use an audio jack for anything other than..well...audio.
Kcarpenter said:
My guess would be that Dalvik (SDK level Code) doesn't have access to hardware level controls.
So this would have to have some Native (NDK Code) in c++ written to make it work. I don't think it would be entirely difficult for someone, but I personally have never tried to use an audio jack for anything other than..well...audio.
Click to expand...
Click to collapse
Yeah, that was kinda what I was afraid of. I have really bitten off more than I can chew with this project.
How I understand the wired remote works is that it just "shorts" the connection.
Now you may be able to simulate that by sending tones through the left/right and/or both poles. (one focuses the other shoots)
You could probably test if this would work by playing music through the cable and see if the camera reacts. I don't have a 1/8th to 1/16th cable or else I would try it myself because I am interested if it would work.
Here is a link of how to make a remote switch which you might find handy if you pursue this.
http://martybugs.net/photography/remote.cgi
Someone mentioned using the usb which would open a whole new world of what you can do. If you have ever played around with the canon software then you know you can control all the camera features from a computer and that should be possible to do on our phones but it would be a lot of work to write an app like that.
centran said:
How I understand the wired remote works is that it just "shorts" the connection.
Now you may be able to simulate that by sending tones through the left/right and/or both poles. (one focuses the other shoots)
You could probably test if this would work by playing music through the cable and see if the camera reacts. I don't have a 1/8th to 1/16th cable or else I would try it myself because I am interested if it would work.
Here is a link of how to make a remote switch which you might find handy if you pursue this.
http://martybugs.net/photography/remote.cgi
Someone mentioned using the usb which would open a whole new world of what you can do. If you have ever played around with the canon software then you know you can control all the camera features from a computer and that should be possible to do on our phones but it would be a lot of work to write an app like that.
Click to expand...
Click to collapse
USB is the way to go. I've written a few apps for windows that control canon cameras using the canon sdk. Unfortunately, the SDK is all C++, so a wrapper is needed to work with java. Plus there are functions that are windows specific. The other option for Linux is libgphoto2. Unfortunately, documentation is not the greatest (nor is it for csdk).
If I had more time, I would have coded this already. But all my coding time is spent programming for work.
centran said:
How I understand the wired remote works is that it just "shorts" the connection.
Now you may be able to simulate that by sending tones through the left/right and/or both poles. (one focuses the other shoots)
You could probably test if this would work by playing music through the cable and see if the camera reacts. I don't have a 1/8th to 1/16th cable or else I would try it myself because I am interested if it would work.
Here is a link of how to make a remote switch which you might find handy if you pursue this.
http://martybugs.net/photography/remote.cgi
Someone mentioned using the usb which would open a whole new world of what you can do. If you have ever played around with the canon software then you know you can control all the camera features from a computer and that should be possible to do on our phones but it would be a lot of work to write an app like that.
Click to expand...
Click to collapse
I am going to test your audio idea and see if it shorts the connection. Yeah, I wish I even knew where to begin with working on the USB. I am very new to this. The farthest I have gotten is building a potential layout for the program.
I just looked up some stuff.
I think the canon remote needs a little over 3volts to trigger the shutter. You are not going to be able to get anywhere close to that with the audio output.
I think the only option is to go through the usb.
centran said:
I just looked up some stuff.
I think the canon remote needs a little over 3volts to trigger the shutter. You are not going to be able to get anywhere close to that with the audio output.
I think the only option is to go through the usb.
Click to expand...
Click to collapse
Thank you for the info. I am downloading the Canon SDK right now(not that I have any idea what to do with it at this point).
is this still going? we are about to make the gsm hero usb-host-mode-able, then all that is missing is libgphoto2 and gphoto2... anyone fancy porting it?
First of all, sorry for my English.
I was searching in Google for something like this and I can't find nothing.
Using the usb is not simple, but the audio option is not crazy at all.
Obviously, that option will require some kind of interface, but can be much simple than the USB option.
You can generate different audio frequencies, for example, 1 KHz for focus and 5 KHz for shutter. With a filter for each frequency you can separate the signal in two circuits. Each circuit can trigger the camera with a transistor, in open collector configuration.
Whatever, if you choose one or another (USB or audio) you will must make some kind of electronic interface.
If someone can works with the software, I can do my part with the circuit. I'm sure that will be easy to build for anyone, even if you don't know electronics.
I am also looking into doing this sort of app, but I am starting with a Pentax k110d... Some camera's only require you to short out the wires, and doing so with the audio headphone jack seems to be possible, from the quick little test I just did with a media player, a 3.5mm jack extension cord, and a multimeter. When the track was playing, i got some resistance across the poles, but when I stopped it, I got nothing registering.
I had actually just given up on the headphone jack, and was looking into doing it over USB as well. I might just have to do several code paths, depending on what kind of camera the person is hooking up /ponder
Alrighty, I just did some more testing with a quick framework app that I had been working on for this. There is apparently a constant 1.7 mV on the headphone jack, which is enough to trigger the shutter release on my camera... boo urns... and when the tone is played, the voltage actually drops, because as all learned ppl know(at least those who paid some attention in physics) is that according to Ohms law, Resistance goes up, Voltage goes down.
Any progress on this?
I would love an intervalometer on Android for my Canon EOS 550D
+1 for the development of such app & hardware it may need.
i hate to bust your bubble but this died over a year ago
ya, development has kinda stalled out... I realized that it is not possible to do over the headphone jack, as there is always voltage there, and I don't know if it is possible just over usb...
The only way I can think that this would be possible would be to get ahold of a google hardware kit/arduino dev kit, and then program that.
I have a nokia remote (AD-54) and was wondering if it could be possible to make it work with SGS with some software mod, or is it physically impossible? It's a nice remote with 3.5 socket, allowing me to plug in my own headphones, and would be great for controlling music playback (cause with just the touch screen it's a pain really). The mic on this remote works fine with SGS as far as I've read, but the controls don't.
www.rolmobile.es/tienda/images/hs45-ad54_312X312.jpg
And, if it's not possible, do you know of any wired remote with 3.5 socket and music controls that works with SGS?
Cheers.
Ditto - I would love a remote for my headphones to control the music player as well.
Nokia might work...
I went ahead and bought one of these.... it does not work out of the box, sound is not output correctly.
What does work is switching the phone into TV out mode. In TV out mode the sound is right. However I can't get the buttons to work at all.
When the phone is not in TV out mode then the headphone socket output is different and non-Nokia compatible. I don't know if that means iPhone accessories work or not.
Its a hardware limitation. I very much doubt the SGS is designed to receive input, apart from microphone streams, through the headphone socket.
Nokia handsets know there is another bit or byte or what ever it is coming through which in turn activates a function. SGS doesn't. The way the Nokia headset is designed, it really only works with Nokias, even to give or accept sound as an output/input.
SargeRX8 said:
Its a hardware limitation.
Click to expand...
Click to collapse
Ok.
SargeRX8 said:
I very much doubt the SGS is designed to receive input, apart from microphone streams, through the headphone socket.
Click to expand...
Click to collapse
Oh wait, you're just guessing you don't know if it's a hardware limitation or not - and you're wrong.
SargeRX8 said:
Nokia handsets know there is another bit or byte or what ever it is coming through which in turn activates a function.
Click to expand...
Click to collapse
Thanks for that exact explanation.
SargeRX8 said:
SGS doesn't.
Click to expand...
Click to collapse
Of course it doesn't. I'd have posted that the attachment worked if it did.
SargeRX8 said:
The way the Nokia headset is designed, it really only works with Nokias, even to give or accept sound as an output/input.
Click to expand...
Click to collapse
That's bollocks too. It outputs sound just fine. The question which you've not answered is if the SGS can "see" the signal generated when a button is pressed on the Nokia remote. You don't know the answer so why are you trying to answer the question with "It's a hardware limitation.". All you have done in your post is guess the answer as no. I'd guess it was a no too, but I don't know either, which is why I'm asking.
On forums it just clutters things up and adds useless content to a thread if people who don't know the answer try to answer it by making it up. I appreciate you're trying to help, but unless you know the answer to the question then you're not helping at all.
You can use alternative music players like Tunewiki or Cube. They can play the next song by pressing the headset button twice
Device like this one uses the Mic connection for remote
http://pinoutsguide.com/HeadsetsHeadphones/blackberry_9700_headset_pinout.shtml
it *looks like the two are inverted for the SGS (and you have a function for "PushButton")
http://pinoutsguide.com/HeadsetsHeadphones/samsung_galaxy_headset_pinout.shtml
Altough this one states that it is the same
http://pinouts.ru/HeadsetsHeadphones/nokia_handsfree_pinout.shtml
and we know that nokia's TV-Out are working.
For the buttons to work, the OS has to understand the same command as on the nokia, is it responding to anything when you push the buttons?
Remember that enabling TV out mode changes the pinout of the phone.
In "normal" mode with a Nokia control adapter in sound is not correct.
In TV out mode with a Nokia control adapter sound is correct.
In neither case do the Nokia buttons do anything - Play/pause, stop, fwd, rwd, vol+, vol-.
I'm sure the phone is only Nokia compatible when TV out is enabled. In this mode we don't know if..
1) The hardware of the phone can receive a signal from the buttons.
2) The firmware of the phone allows this to be passed to the software.
3) Software can use this input for media players.
Outside of Nokia mode, I don't know the answer to the pinouts.
Of the three pinout links you posted... http://pinoutsguide.com/HeadsetsHeadphones/samsung_galaxy_headset_pinout.shtml seems to be verified. There are three posts saying it's incorrect, but they simply say that the left and right channels are reversed. It's implied from that then that the other aspects are correct.
I think since we're no further forward it wouldn't be a total waste for me to go ahead and get one of the iPhone control adapters off eBay and see what the result is?
Halkus said:
Ok.
Oh wait, you're just guessing you don't know if it's a hardware limitation or not - and you're wrong.
Thanks for that exact explanation.
Of course it doesn't. I'd have posted that the attachment worked if it did.
That's bollocks too. It outputs sound just fine. The question which you've not answered is if the SGS can "see" the signal generated when a button is pressed on the Nokia remote. You don't know the answer so why are you trying to answer the question with "It's a hardware limitation.". All you have done in your post is guess the answer as no. I'd guess it was a no too, but I don't know either, which is why I'm asking.
On forums it just clutters things up and adds useless content to a thread if people who don't know the answer try to answer it by making it up. I appreciate you're trying to help, but unless you know the answer to the question then you're not helping at all.
Click to expand...
Click to collapse
I try to help and you insult me? You are clearly a dunce. Ill stay out of your thread.
I was making a guess based on what is known. The hardware inside the SGS is different to the nokia. That link posted above proved the pinout is different thus proving what I said to be correct, its a hardware limitation. What the Nokia headset sends out as a signal is not going to be received by the SGS.
Kindly get bent and refrain from posting your useless crap. Unless you work for Samsung or Nokia as a hardware engineer or they release the information, or you've spent time following the circuit of the phones, you will too be making a guess.
In non tv mode the sound works fine for me. Are u sure you have a real Nokia ad54. A couple of the fakes I got off eBay don't work correctly. If u have a real one the sound works fine for music/books and when u get a call the sound will also work.
Sent from my GT-I9000M using Tapatalk
lgkahn said:
In non tv mode the sound works fine for me. Are u sure you have a real Nokia ad54. A couple of the fakes I got off eBay don't work correctly. If u have a real one the sound works fine for music/books and when u get a call the sound will also work.
Sent from my GT-I9000M using Tapatalk
Click to expand...
Click to collapse
I cannot be sure if I have a real one or a fake. Music sounds ok when it's not in TV out mode, but some parts are missing on some tracks. I'm guessing I'm hearing left or right channel only on both sides - but I'd need to find a file to test that with to be sure.
The one I got looks exactly like the one at the top of this thread. It came without the headphones. It even had the cable tie wrapped in the same way.
Argh! I've just done a left/right channel test... and in normal and in TV out mode the left and right channels are separate and correct. It turns out the AD-54 I have has a slightly dodgy connection.
The test I used is here - http://www.wooferbasstest.com/left-and-right-channel-verification-audio-systems/sound-effects.html if that's any use to anyone.
So after taking a complete wrong turning... apologies... back to what t1mman was saying...
There is no response at all from the Nokia buttons. I've even made sure I'm wiggling the wires about while I do it with both the device switched to the in position and the off position. As I'm still not convinced though I wouldn't mind lgkahn's input on it - Do the buttons work in any way for you on the AD-54?
We know at this stage then that the Samsung and the Nokia both use the same channel (ring2) (my rusty electrical knowledge tells me that it is not possible to use ground?). However the SGS is either incapable of seeing the Nokia signals, or is not looking for them so ignores them... I think that's the summary of where things are.
Going forward from here I think there's no point in trying a iPod pushbutton thing - so unless someone has a different opinion I won't bother getting one off eBay.
It would be interesting for someone who knows more about the phone itself to let us know if it's even conceivable to try to see if the phone is seeing a signal, because if it is seeing a signal then perhaps it could be taught to respond to it? I'm way out of my depth there.
Other than that though, it seems to me that the Nokia device serves no purpose, and the only way to pause/play music is to use an app that pauses/plays when the headphones are disconnected.
hi, i guess that this approach is dead isnt?
I want to know the same..
Anyone on here used the iCade 8-Bitty Bluetooth controller with any emulators on the HTC One yet? I was able get one cheap but I know how buggy this stuff can be with different phone manufacturers. I really wish Android supported Bluetooth controllers without having to use an app. I play a lot of emulation on my phone and the on screen touch controls just aren't the same. I have read that some custom phone Rom's have capabilities of supporting devices like Wii-motes and PS3 controllers. But it seems neither work on HTC devices with Stock Roms. I hope it works when it finally arrives! :fingers-crossed:
Actually, the Wiimote does work on the Sense rooms with BluezIME. You have to download the separate file as per the instructions in the app, but works fine. It emulates an HID device so I don't believe the joysticks work on a classic controller, but good enough for SNES games. Hope this helps - maybe I should post a separate thread so people know about this method.
Btw I checked BluezIME and with the hid enabler, it has a setting for iCade. Even better!
soul44 said:
Actually, the Wiimote does work on the Sense rooms with BluezIME. You have to download the separate file as per the instructions in the app, but works fine. It emulates an HID device so I don't believe the joysticks work on a classic controller, but good enough for SNES games. Hope this helps - maybe I should post a separate thread so people know about this method.
Btw I checked BluezIME and with the hid enabler, it has a setting for iCade. Even better!
Click to expand...
Click to collapse
Wow I will have to check that out. I did a lot of searching online the other night and downloaded an app for Wiimotes but it wouldn't connect to my controller. It came out with some error saying it had known issues with Sense Roms. I also tried the PS3 one and it also had issues. SNES games is exactly what I wanted a controller for. Thanks!
Newer Wiimotes won't connect. To any Rom You'll have to find an older one. Theres literally no way sense could cause a Bluetooth controller to not work.
Sent from my HTCONE using xda app-developers app
youkosnake said:
Newer Wiimotes won't connect. To any Rom You'll have to find an older one. Theres literally no way sense could cause a Bluetooth controller to not work.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Granted I have a limited understanding of this, but it seems to me the blue tooth stack is integrated in to Sense (or Touch with for Samsung phones)
My relatively new Wiimote (the new motion plus) and classic works fine in BluezIME. And the wiimote/sixaxis apps both say they usually don't work with sense roms. BluezIME works because it emulates HID mode, natively supported. Fwiw.
soul44 said:
Granted I have a limited understanding of this, but it seems to me the blue tooth stack is integrated in to Sense (or Touch with for Samsung phones)
My relatively new Wiimote (the new motion plus) and classic works fine in BluezIME. And the wiimote/sixaxis apps both say they usually don't work with sense roms. BluezIME works because it emulates HID mode, natively supported. Fwiw.
Click to expand...
Click to collapse
I should reword. Newer Wiimotes won't work. Wiimotes with motion plus do. It has something to do with the Bluetooth key in the wiimotes themselves. They won't even work on pc.
I don't see how a bluetooth lib would be changed to the point it breaks functionality(or at all really) but I suppose sense could be an issue.
Sent from my HTCONE using xda app-developers app
I believe the old ones I have are from a launch system, so I can't speak for new ones. But they never worked on my Evo 3D (I don't recall if I tried BluezIME, only the Wiimote app. Once Cyanogenmod was ported, they worked without a hitch. So it seems to be some issue with how HTC implements Bluetooth, beyond that I can't say. Oddly, I believe One X users were able to use them, I'm not sure, but if so that's very unusual that it's back to not working. Oh well. BluezIME works fine for my purposes, usb-otg cable is in the mail and I'm hoping that works, if not no big deal
I have an original launch Wii controller and I was able to get it to connect. It took a couple tries it kept asking for a passkey. But eventually it took. So it does work which is great. But when I plugged in the classic controller it got a little crazy. Setting up the button mapping in SuperGNES didn't go very well. It was almost like a button was auto pressing everytime I selected a button to map. I'm a little too tired to figure it out tonight but will probably dig into it a little more tomorrow.
Sent from my HTCONE using xda app-developers app
So bad news - I bought a USB-OTG cable. Keyboard, mouse, thumbdrive, all plug and play. Works fine. But PS3 remote and an old off-brand I had lying around do not. Why do they insist on removing gamepad support? It works fine in stock Android - has since, what, ICS? Guess I'll probably jump to MIUI, supposing we see it. Maybe I'll take a stab at the kernel source and see what I can find. Doubt I'm skilled enough for that sort of thing, though.
My iCade 8Bitty controller finally came in today. It works great with the emulators I use. Didn't have to do anything fancy to get it to work, pretty smooth sailing. Simple set up. Looks like it will work with any app/game that says it supports it. :good:
Too lazy to look for the info at 4AM, but yes, Sense is a major issue that breaks Bluetooth functionality. Something in Sense was causing a conflict in the Bluetooth driver, so HTC disabled certain functions in the driver. As a result, Wiimotes, as well as some other devices, won't work. Apparently HTC finally got around to fixing the issue rather than just sweeping it under the rug. Good for them. And us.
I managed to add three remote control profiles into my M20P, click on customise in huawei smart remote app and start adding..have fun.
Make sure you place remote ir close to about 2 cm to phone ir. Also you don't have to press and hold for 2 seconds, just press once and it will be registered. Remember to save before using the smart remote otherwise you will have to reprogram it again. Also reprogram buttons if they don't work after programming.
Nothing surprising, both the Mate 10 Pro and the Mate 9 Pro, and I guess some previous ones, did it as well. It's one thing I always liked about Huawei phones, with the other major brands abandoning the IR port. WiFi is the future, but IR is still needed by a lot of devices. The only downside is that it's able to learn just in the native app, forget about make it learn signals in other apps supporting signal learning like AnyMote. Unless Huawei recently opened its APIs, which I doubt.
I agree it's very handy. I can control my room's light/ventilator, my PC's 2.1 sound system, my Headphones Amp and pretty much everything else.