yashsingh1/xdaforums huggingface dataset:
[Samsung Gear 2] cracksmurf:
Development was a bit slow this past week due to working between 70-80hrs, but I have managed to get a little groundwork set. I'm definitely going to have to look into being able to add new button types, and I can foresee layout issues depending on how it generates a layout based on certain buttons. Though I will face those hurdles as I get to them. As it stands I should be able to get device functionality in there; even if it doesn't look pretty.

For now I have started working on getting through the list of device requests that were from the old thread. I've imported these into the Feature Requests tab. If you have a device that you would like added then feel free to place a request there and I will prioritize you since I'm not sure if some of the people who made those original requests are still around. If you see a request of yours or another device that you would like added then use the "UpVote" button. This will let me know which devices to prioritize. Please use the listed format for new requests to make things a little easier.

Secondly, I have been expanding my Google Sheets document to keep this all organized. The file has been made public for those who are curious on a specific devices progress. Others can also create new tabs and add a device to the list if they wish. All tabs that I create or devices that I have reviewed will be locked from editing, but feel free to get in there and add a device if you know where to find the hex codes. A couple useful sites are http://www.remotecentral.com/ and https://irdb.globalcache.com though i'm sure there are plenty more databases and forum locations to find codes for your devices.
[Samsung Gear 2] Garridon:
Ive added the hex codes for the devices i requested into your google sheets. Good luck with everything
[Samsung Gear 2] cracksmurf:
Looks good. Glad to see it was easy to grasp the button mappings in relation to their file name. I'll make sure to get these in on the first release. As I figure things out in subsequent releases I'll try and get custom buttons made up to match common device types like xbox controllers. This will make the resulting control look more fitting in style.

I'm at work till midnight tonight, but should be able to squeeze out a little time to throw your devices into the app and get some testing done. Looking to be a slow night anyways. Also, gotta reflash lollypop since my phone build currently isn't detecting the IR Blaster, unless biktor gets the next test release of marshmallow out that he was hinting at for today.
[Samsung Gear 2] cracksmurf:
A little progress. All devices that are listed as "In Progress" in the Feature Requests tab have been completed in the spreadsheet with all applicable codes.

I have also worked out a simple little system that allows me to export the document from Google Sheets into excel and load up a script which converts each cell into it's appropriate .button file. Once that is done it is simply a matter of dragging the files into the assets folder, compile the apk, sign the apk, and do some testing on device. As of right now I have done this with all the devices currently in the spreadsheet.

I'll try and get this compiled and signed today for testing. It will require transferring files do my desktop, remote into that and run all the compile/signing steps there since I can't install python or apk studio at work.
[Samsung Gear 2] cracksmurf:
So got it built using a test key (still haven't gotten around to creating my own keystore lol). Downgraded my Gear 2 to LP since the MM build I was using didn't have a working IR Remote. App loads up, tv's that were already in app here at work are functioning. Will test my devices at home that I added as new devices. Few minor errors that I noticed I made and need fixing. But otherwise this is pretty much ready to go as a first release. Maybe tomorrow if we are lucky. Layouts, custom buttons, and custom categories still need to be figured out, but functionality for everything else should be there. Though I will need the people that actually own these devices to test them out once I make the build available.
[Samsung Gear 2] Garridon:
This is fantastic to hear. I've kept my gear at lollipop due to all the problems I've heard about mm on it. But anyway it's not force closing so that's a great sign! xD how hard is it to make a keystore?
[Samsung Gear 2] cracksmurf:
Using pySignare it's supposed to be as simple as clicking a button and typing in some info. However, it's failing to work for me for some reason. I'll have to look into the official method of generating a keystore tomorrow since that tool isn't working for me. Worse comes to worse I can release using the test keystore. Not like I really need any security on this app due to it being more of a community project than a release of my own development at this point.
[Samsung Gear 2] zygh0st:
I didn't want to muck up the device requests with a non-standard feature request, plus I'm rather long winded so I thought it more appropriate to leave it here. Perhaps this has already been considered and subsequently dismissed, but wouldn't it be far simpler to create an interface for users to simply add their own devices to the app? Perhaps you could also provide the functionality to export and import device specifications to ease the burden of having to add devices redundantly in the event of data loss and let users share their own configurations? I disassembled the app itself some time ago to manually add in my own devices, but it was a curiosity more than a real effort and I stopped when I wasn't able to reconcile why the values in the app were slightly off from the IR code databases available online and couldn't effectively convert them to match, but I did note that the basic template was fairly universal looking so I would think it would be terribly difficult and the work would certainly pan out to be less than adding each request individually, but my perspective is from that of someone who's been writing code about as long as I've been able to write my name (24 years, wow I feel old!) so bear that in mind. Just a thought, and there may well be few enough requests for individual devices that it isn't worth the trouble to build something like that. Looking forward to seeing how things progress in any case and congratulations on picking it up!
[Samsung Gear 2] cracksmurf:
You make some valid points, and Bitstra was actually working on creating features similar to some of that before he had to abandon the project. While I do have some experience in coding its not very much. While I could probably figure out how to put together features like that it would take me way longer to implement than would be worth while; mainly due to the fact that I would be researching what everything is as I go. Don't get me wrong, I would absolutely love something like this, but due to my lack of experience I'm mostly limited to minor tweaks to the code. Things like expanding menu categories for devices, maybe adding more button types, or some layout changes.

As far as your statements on the IR hex codes being different? The only thing I can think if as to the codes being slightly off would be due to the number of slight variations manufacturers themselves implement into their devices. Say for a Samsung TV you might find 3-4 generic code variations or more. A lot of the time its trial and error to get the right code set for the device you are using. For the devices I've manually added I've had no problem working out the right code set that gives me all the right remotes features.

For the most part I picked up this project since I wanted to get my devices in for myself and figure I'd help others who had been making requests over the past year. I'm trying to create as much explanation as I do it so if others want to easily add devices in on their own they can. I've managed to put together a process where the hardest part is just finding the codes, then drop them in my Google doc, run the excel macro script to automatically export the .button files, and all that is left is to build and sign the apk. Right now we don't have too many people making requests so not that hard to keep up with, but the option is there for them to do the finding of the codes and entering them into the spreadsheet on their own and I'll just throw a quick build up afterward.

Perhaps I can throw a guide together for those who wish to do this entirely on their own. Plus im always welcome to help from those with more coding experience than i who want to implement better features.
[Samsung Gear 2] cracksmurf:
I plan on doing a few more changes regarding version number etc to ensure that the first release can simply be installed over previous releases without having to fully wipe the app from your device and then install it. Should be a quick and simple job. Once that's done I think I can get the first release out for you all today. I haven't put 100% of the old requests from bitstra's thread, but want to get my first release out there. I'll keep working on those and any new requests for the next release.

As always feel free to help out by finding the IR Hex codes for your specific device and either linking them to me in the request or inputting your device on the google spreadsheet to speed things up.
[Samsung Gear 2] cracksmurf:
Here is my first release of the updated IR Remote port.

https://www.androidfilehost.com/?fid=24438995911975157

Changelog

-Note

Due to taking over the project and not having the original keystore that bitsra was using, you will receive an [INSTALL_FAILED_UPDATE_INCOMPATIBLE] error if you attempt to install this app over top of his previous version. You must make sure that you remove the previous version before attempting to adb install my version.
[Samsung Gear 2] zygh0st:
The difference in the codes I was referring to was that they didn't agree with the codes online insofar as the initial few hex words would vary slightly from any I found online and I couldn't find the exact hex string for any device anywhere online, so I assumed they had been converted to work with the specific IR blaster in the watch.

As far as helping you write an interface such as it'd mentioned, I'd be very honored and happy to provide you with any assistance. Having said that, I will move to my next question.

Have you any plans to open source the project? I saw you mentioned documenting how others could add their own devices and I wasn't sure if you meant for them to do so via compiling from source or simply disassembling the so via apktool or the like.

Also, if you're still having trouble generating a keystore, I think I have a script that I'd written to do that, I'd just need to locate it but I'd be glad to share it. It seems daunting, but it's not so bad. If I'm not mistaken, I believe Android Studio provides a wizard to make a keystore as well, but I could be imagining it.
[Samsung Gear 2] cracksmurf:
Yeah i've noticed for the devices I have tested that there have been multiple variations of the code set for devices. One cause for the differentiation in the hex codes could possibly be the code referring to timings? Either way on my devices I was able to simply input the hex codes with no modification into the app and have them work on my devices (Though we can't be sure that will work for all devices until we try more).

I have absolutely no problem open sourcing any of my work. Although as of right now the progress I have made has simply been through that process of disassembling and tinkering with the code. (Bitstra has offered to share with me his work files from the project so just waiting on those to see if there's anything that could help more).

As far as the keystore, I've got that all managed out. Been a bit busy so hadn't had the time to sit down and work on the issue. Got that done today by just using the tools that came with java in cmd line. Really should get around to installing Android Studio as well. Been keeping it simple with notepad++ since I can use a portable version of that at work where I can't install more software.

A future project I would like to do is to create some good documentation and project files for those who would like to compile the project on their own; allowing for custom builds that only contain the devices that someone owns or wants in the app. Would also allow for more direct testing with different codesets instead of waiting for me to push out a new version when a codeset doesn't work on their device.
[Samsung Gear 2] Garridon:
Button tests for xbox one and samsung model HT

All the buttons on the xbox remote appears to be working fine. The only problems with it is (on the attached picture) the two circled buttons do the same thing (take you back to the home screen) you could remove one, i like the one that looks like an arrow pointing into a screen. The exit button doesnt appear to do anything and can be removed, the power on and power off individual buttons can be removed too. the button that is SLP can be removed (its the play pause toggle and doesnt work correctly on the xbox)

On the Samsung remote, most buttons function as they should with a few issues. The nav left and nav right both function as nav left. The nav down does not do anything really. You can remove the button assigned to number one.

I understand that the misassignments might be my fault so ill pm you the hex for the corrections.
[Samsung Gear 2] cracksmurf:
I'll take a look into the issues and hopefully get an incremental update completed and pushed out today to address them.
[Samsung Gear 2] Nick1602:
Well I just can`t install, already try to remove put again! but no way!

all the codes that whore in the tizen sansumg ir remote app was working fine to me.... and how I can learn some button of the control that dosen`t have in here?

the 2.0 no way to istall but already back to 1.6 no problem to install

could you help me out?
[Samsung Gear 2] cracksmurf:
What exact steps did you take and errors or issues are blocking you from installing? Did you remember to reboot device after uninstalling the app from /data and /app? I know it still thinks its there until a reboot. Which blocks the app from being adb installed.

Also just to confirm, you are running biktor's Android Wear port right?

PS: I'll work on getting next version with those 2 device fixed done asap. Had surprise family stop by for the weekend.
[Samsung Gear 2] Nick1602:
I could uninstall , however when I try to install, it 's that incompatibility failure problem

yes reboot after all the steps

I'm android wear on gear 2 version LCA43 5.1.1
[Samsung Gear 2] Wilsonb:
Hi,

Would it be possible to post quick apk install instructions on to the watch? Or is this something I install on the phone and it syncs it with the watch?​
[Samsung Gear 2] cracksmurf:
yup, this is installed directly onto the watch via adb. if you already have a previous version of the ir remote installed on your watch, you will have to uninstall it. Below are instructions on how to do so from my previous post/topic post. If you don't know how to use adb i'd recommend finding a guide for that. or I can see what i can find myself.

Removing Previous version

//If bundled from Biktor's Wear release as system app//

adb shell
su
mount -o rw,remount /system
rm -rf /system/app/org.esolutions.irremote-1
rm -rf /data/data/org.esolutions.irremote
mount -o ro,remount /system
reboot

//If manually installed//

adb shell
su
rm -rf /data/app/org.esolutions.irremote-1
rm -rf /data/data/org.esolutions.irremote
reboot

Installing new version

adb install -r IRremote_Gear2_2.0.apk
[Samsung Gear 2] LeHoang2206:
Android Wear 6.0.1 don't work IR :(
[Samsung Gear 2] vitdiesel:
HI Lehoang2206, minh dang dung gear 2 neo wear 6.0.1? lam sao de cai app vao aw khi dung ip6 ah?
[Samsung Gear 2] cracksmurf:
Biktor stated that he might be getting IR back in on beta 3 of his MM release. Until then we gotta stay on LP to keep IR functionality.
[Samsung Gear 2] Jaitsu:
Do you mean SDB instead of ADB? Or do you install the apk to the phone instead of to the watch? Orrr are we talking about Gear 2's flashed with Android Wear instead of Tizen? Sorry, I'm a little new to advanced stuff on smart watches.

EDIT: Herp. I'm blind. Yeah, okay, so this is for people using Android Wear instead of Tizen. Whoooopsie. Sorry!
[Samsung Gear 2] biktor_gj:
Hey, long time wanting to reply to this, I'm about to test IR on marshmallow and wondering if you would like me to include your app on the next release or if you think it's better just to have the HAL in place and link to your thread from the gear2 port thread so you can handle updates better...

I think it would be possible to just have a base system apk in place and whenever there's an update just up the version number so adb doesn't complain on already installed package, but I haven't tried so really not sure if it'll work fine ;)

Choice is yours, thanks for keeping up with the app!
[Samsung Gear 2] cracksmurf:
Yeah definitely feel free to put this in the rom. Been meaning to get another update with some of the updates/fixes out so perhaps I'll try and force myself to work on that today. Wasn't able to test with doing version updates over system file yet due to your rom including the previous version which was signed with a different key. but that would be the ideal setup; include whatever the newest version into your rom at time of build and then my incremental updates could just be placed over top in between rom builds.
[Samsung Gear 2] fernandogdl:
is there a possibility to add a function where you can manually add any device by putting a code? like universal remotes
[Samsung Gear 2] ProFragger:
[MENTION=1496184]cracksmurf[/MENTION] Thanks for your great work here, bud. One question/request. The Remote app on our phones allows us to add devices, or more than one TV in the house for example, but having different "Rooms" in the app. I noticed on the watch, however, there is only one room, and there by an ability to only add one TV code.

Does your app allow for extended functionality of having more than one TV code available, per watch? Appreciate your help and guidance and thanks again for your great work!
[Samsung Gear 2] cracksmurf:
I can look into this, but I highly doubt I'd be able to implement it. I have minimal coding experience. So while I can tinker and modify this app which was already created to suit our needs; adding in new features that change the functionality of how the underlying system works with IR codes might be outside of my capability.

Sry, the Gear 2 is the only Samsung device I have ever owned so not sure how the bundled app functions. Not really sure about these rooms you are talking about, but you can add as many TV codes as you want. Just click the button to add a new device, select TV, and select from the list of available TVs. During testing there was one point where I had every single device that was built into the app added as one of "My Remotes". I could easily scroll through any of them and select it to control that device; no matter what room I was in. Now if you are meaning two different TV's of the Same manufacturer that might have slightly different code sets, then it is just necessary for me to make two different entries for those devices and put their unique IR code set into each one.
[Samsung Gear 2] carvellwakeman:
[Device Type] TV

[Manufacturer] JVC

[Model Name] LT-32E478

I'm also getting this weird issue where I can't change the IR code on a button. If I try, the app crashes. I say this because there is already an option for a JVC tv, but it does not work on mine.
[Samsung Gear 2] cracksmurf:
Sry for the late reply. Been crazy hectic with work (Knocking out 16 hour work days). Finally moving back to normal schedule which will free up my afternoons and weekends again. I'm longgggg overdue for an update so I'll see about adding your specific JVC model into the app. Hopefully that will assist with your variation of the IR code.
[Samsung Gear 2] carvellwakeman:
Hey don't sweat it, we've all been there. It's been a couple months since I've been able to work on my own projects as well.
[Samsung Gear 2] code4power:
can not find for grunding tv
[Samsung Gear 2] Neroga:
Looks cool! Miss the IR blaster from my old OG Pro, and was happy to see the Gear 2 included one. The girly gave me hers and I quickly switched it over to Android wear so it would work on my 1+1 lol.

Sadly, it tells me my device isn't supported. Does this work on MM builds, or would I have to go back to LP (worth it for this!)?
[Samsung Gear 2] andronikal659:
can you make a .wgt of this app for Samsung Gear 2 for Tizen Wear? Thank you
[Samsung Gear 2] bobby09120:
i have panasonic air condiction how can i get on list device to add more device , i just have daikin and some of Chinese aircon only. tks you
[Samsung Gear 2] marcozpaulo:
Hello guys ... This post is simply fabulous !!! Thank you very much for the idea and willingness to help !!

I would like to request the inclusion of some codes of devices that I have at home (I'm from Brazil and here these devices are very commom). None of them appear in the application list.

There goes:

[Device Type] TV

[Manufacturer] AOC

[Model Name] LE48D1452

[Device Type] Audio

[Manufacturer] Sony

[Model Name] FH-B511

[Device Type] Air Cond

[Manufacturer] Comfee

[Model Name] Anyone. It doesn't matter

[Device Type] Air Cond

[Manufacturer] Komeco

[Model Name] Anyone. It doesn't matter too

Thank u very very much
[Samsung Gear 2] m4f1050:
[Device Type] Audio (AV Receiver is more appropriate)

[Manufacturer] Onkyo

[Model Name] TX-SR605

[Device Type] Audio (AV Receiver is more appropriate)

[Manufacturer] Sony

[Model Name] STR-DN840

[Device Type] TV

[Manufacturer] Vizio

[Model Name] M3D650SV / XVT3D650SV (prev model)

Both TV's look the same, FW is different and remotes are different, one has PIP and BT in menu, not sure how to access BT in the M3D650SV model and I believe they took out the PIP as well.
[Samsung Gear 2] Notre85:
Would it be possible to integrate the following devices:

Device Type unknown

Manufakturer Busch-Jaeger

Model: Red

Ir-Codes: device 29 from irdb.tk

Device Type unknown

Manufakturer Busch-Jaeger

Model: blue

Ir-Codes: device 30 from irdb.tk

Thank you!

Patrick
[Sony Cross-Device Development Themes and Apps] Marília de Oliveira:
Hi friends

Check out a beautiful theme for your xperia!

Good fun :D​

ScreenShots

How to install

*Download Thema attached

*install

*Reboot

See the new face of its Xperia ;)​

Do not forget to give me a thank you [:good:], it will be great for me because somehow will encourage me to keep my work and create new roms and mods! Thank you all

So far no bug was found. I ask you please file a bug found that I can fix. Thank you​
[Sony Cross-Device Development Themes and Apps] Pandemic:
Very awesome theme ^^

“Sent From MWE V9.5.0 On My Z3”
[Sony Cross-Device Development Themes and Apps] epr:
What's the Name of the clock widget?
[Sony Cross-Device Development Themes and Apps] mirok80:
Great
[Sony Cross-Device Development Themes and Apps] Marília de Oliveira:
Zooper Widget pro
[Sony Cross-Device Development Themes and Apps] pRakitik:
No more colors??
[Sony Cross-Device Development Themes and Apps] Marília de Oliveira:
No friend, will come more new themes
[Sony Cross-Device Development Themes and Apps] Skyreader:
Thanx 4 theme. Good job!
[Sony Cross-Device Development Themes and Apps] Rodrigo Toledo:
Stupendous theme! Parabéns guriaa!

Enviado de meu D6633 usando Tapatalk
[Sony Cross-Device Development Themes and Apps] Marília de Oliveira:
Thanks friend ! :D
[Sony Cross-Device Development Themes and Apps] Rishabh.srivastava96:
Thanx for this beautiful theme great job....☺
[Sony Cross-Device Development Themes and Apps] Marília de Oliveira:
Thanks :):)
[Sony Cross-Device Development Themes and Apps] Nu Pakachi:
Does the theme require xposed? Everything works just fine on my device except navigation bar and buttons. Xperia M5 dual E5663 with stock 5.1, rooted but locked BL and no xposed.
[G4 Q&A, Help & Troubleshooting] Mindspin_311:
Ever since receiving the 6.0 OTA, I cannot send MMS. Factory reset did not help. Thoughts?