Related
Hi all,
I have a concept for a single update application that would be driven from the AndroidSPIN release database so all developers could use it for ROM, Themes, Applications and anything releases to devices.
If you wouldn't mind taking a couple of minutes to read this post, I would greatly appreciate it.
http://www.androidspin.com/forum/viewtopic.php?f=260&t=226
I'd really love to get a group together to collaborate and either help design this and/or write an application and back end to do it.
Let me know what you think.
Thanks
Simon
Sounds like an awesome idea, I'd love to help any way I can, but I dont fit in any of the needed positions for the post. Looking forward to see what develops though
Fantastic idea!
I only ever use XDA so god knows what I'm missing out on elsewhere and to be honest after searching the word android on google and trawling through one crap site after another becomes tiresome so hence the 'XDA only' policy.
Sorry I can't offer any programming skills but you have my support on this project whole heartedly, not that it counts for much I know buh MeH!
Hope you can get this off the ground.
As I mentioned to Simon already, I was thinking about building an update application for my ROM. I love the idea of having an on-phone ROM database, update capability, something that can easily be used by any developer in the community.
Some initial thoughts on functionality:
- Browse ROMs
- Download ROMs to SD Card
- Monitor specific ROMs for updates
- Monitor currently running ROM for updates
I'm willing to lend a hand on the Android side of things, but this will be a large undertaking and we will also need some people to contribute to the UI, server side of things, etc.
I do iPhone UI design for applications now (I don't have an iPhone, but most of my contracts and clients are iPhone based), but let me know and I can whip up anything you guys need UI related.
Send me a PM and I can get the ball rolling on how the functionality can be laid out as well.
Even tho I know I wouldnt be able to help out with this. I know I would love to test this out if you needed it.
Its a great idea!!!
I know a teeny bit of Java, and I'm working on becoming an Android developer, so if anything needs doing on the Android side of things, I'm willing to contribute.
Although I may not know as much as some others, I'm definitely a fast learner. I have a few books on Android development I'm reading through right now.
michinohatoresu said:
I know a teeny bit of Java, and I'm working on becoming an Android developer, so if anything needs doing on the Android side of things, I'm willing to contribute.
Although I may not know as much as some others, I'm definitely a fast learner. I have a few books on Android development I'm reading through right now.
Click to expand...
Click to collapse
Well, we can reuse a lot of code from Cyanogen updater.
akirah said:
Well, we can reuse a lot of code from Cyanogen updater.
Click to expand...
Click to collapse
Well, of course.
If anything else needs doing, however, I volunteer what spare time I have.
akirah said:
Well, we can reuse a lot of code from Cyanogen updater.
Click to expand...
Click to collapse
Could be easily done, would require quite a lot of laborious work ripping out all the stuff you wouldn't need though.
I would take a look at this but unfortunately I have another Android project on at the moment which is taking all my development spare time.
@SimonNWalker What sort of backend having you got going? REST? SOAP?
Ups wrong theread
not that it matters (since i kept the source 100% open)....
you have my blessing to tear the cmupdater to shreds if it will give us a unified solution to all our ROM cravings
firefart has done a good job of keeping the code pretty clean so there shouldnt be too many issues with grabbing it
and the new code for the screenshots for themes could probably be used to the advantage of this project with ease
I'm not really interested in a rom updater, but a market replacement with an "upgrade all" feature (à la apt-get / yum) drawing from multiple repositories would be most exciting.
The Cyanogen updater could be used, it just needs some modifications. Stuff like sub-sections and update all
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
willmav5000 said:
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
Click to expand...
Click to collapse
The only other method I would consider, besides JSON, is an advanced and well thought out web-based form that the developer is forced to complete upon uploading a ROM. This would place more burden on the server, but should be relatively easy to attach the provided ROM information to the rom database.
Think: Check boxes for firmware compatibilities, check boxes for device compatibilities, version number, change log, etc.
Maybe something a little like this?
Wow this would be/ is gonna be awsome!
I would suggest also that you can backup your sd card settings (and maybe also sms...) to an ftp server (or some other server you can install on your pc) from this app...
like (incremential) backup>partition>wipe>install update>boot>getbackupback
problem is to get the server adress back after wipe. maybe stored in web database and encrypted with phone imei number? or uploaded as google
whatever...
or just not wiping that single adress
just saying ^^
willmav5000 said:
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
Click to expand...
Click to collapse
JSON is just a file format. The CM Updater works via a static JSON file that gets updated manually. The way I'd design this (which is what I asked a couple of posts back) is a dynamic web service (probably REST based) which delivered JSON dynamically. Wouldn't be too difficult at all.
As SimonWalker said he's using PHP + MySQL I'm guessing that's already being done.
@garok89: CM Updater is completely open-source therefore blessings are not needed to use the source. Really don't understand all the "credit" crap here on XDA.
senab said:
@garok89: CM Updater is completely open-source therefore blessings are not needed to use the source. Really don't understand all the "credit" crap here on XDA.
Click to expand...
Click to collapse
I know it is open and I don't need to give my blessing for people to use the source. I did so because a lot of people don't feel comfortable using other peoples code without permission, regardless of whether or not its 100% open source.
And as for the 'credit crap'... I don't see you asking for your name to be removed from the 'about' section of the app
I am not asking for any credit
Anyway, lets not get off topic...
Guys, before this becomes Android Open Alliance, the sequel (you all remember how that went), I think we better set up a way to work together first and then toss in the speculative stuff later.
How about starting simple; set up a wave?
Greetings fellow Android users!
I wanted to take a moment to let everyone here know that I've just been added to the team at SwypeInc specifically to handle the overwhelming amount of emails and forum posts related to the Swype beta for Android. The staff at Swype care deeply about their users, and went out of their way to get in touch with me - an avid Swype user and supporter - fly me to their offices in Seattle, and hire me to help with their ongoing community interactions. We know that a lot of users have felt somewhat neglected regarding our ability to respond quickly to their requests for support, and are eager to do something about that issue!
So for those of you who are Swype beta users (and if you aren't, head over to beta.swype.com to be added once we re-open registration!), I encourage you to log in to our forums (http://swype.uservoice.com), post your questions, feature requests, or other concerns, or email me at [email protected]. I'll make sure you receive the attention that everyone here at SwypeInc feels you deserve.
I look forward to helping Swype and the Android community grow the relationship that has already helped us improve Swype, and hopefully improve the way you all enter text on your Android-powered devices.
All i want to know is what there will be other dictionary's available..
I like it.... and its very good..
but i need it in Dutch if i am going to use it as default softkeyboard.
anheuer said:
All i want to know is what there will be other dictionary's available..
I like it.... and its very good..
but i need it in Dutch if i am going to use it as default softkeyboard.
Click to expand...
Click to collapse
New language dictionaries is an ongoing priority for Swype. Our development team is working all the time to add more languages. Currently, there are a number of languages that we have dictionaries for that aren't included in the beta. Dutch is actually included in this list. For a full list of languages supported (and planned additional supported languages), see this thread on the Swype forums: http://swype.uservoice.com/forums/17482-swype/suggestions/443262-swype-s-language-support-
This post is a bit old, but it should serve its purpose
I'll pass along your desire to have Dutch (and other languages) included in the beta and hopefully we'll be able to add them to future beta releases. Thanks for the feedback!
is the new swype be availabe to test the 1.29 that isin the new mytouch slide.
rbaggio00 said:
is the new swype be availabe to test the 1.29 that isin the new mytouch slide.
Click to expand...
Click to collapse
You will rarely see a beta update that reflects perfectly a partner release, because most of our partners customize Swype to their liking for the device it's being released on. The beta, on the other hand, is a stock/standard configuration that Swype uses internally as our base recommendation to our partners. So, no, there is no update to the MyTouch version. But there should be an update coming down the line sometime relatively soon.
I'm hoping to get some help with a collaborative list of applications for the latest android. The list will be comprised of the application filename, where it comes from(ie: CyanogenMod, OTA, GApps, AOSP, etc), what it's purpose is(brief description), and whether or not it is safe to remove(possibly also a column for what applications are dependent on it, if necessary.)
I know there have been other attempts at this, however I cannot find an up-to-date version.
I have started, but honestly don't know what a lot of the applications do. This will be something that I will edit over the next few days when I have the time and patience, and hopefully others will join in as well.
Here's the link if anyone feels like chipping in. Feel free to reformat it to look prettier, or prepare it with BB code for later use in a forum post.
Any help is greatly appreciated, and I hope that once this is done, it will help some people out.
I'll also include - in the final post - a prewritten script (for use in recovery) which can remove all of the apps that are "safe to remove" (so that people can edit it to their liking)
Hello XDA,
I'm releasing a modified version of Kik to the public. This is version 7.9 - without video playback support. I created this in January after discovering an exploit within Kik Messenger that allowed me to crash other users. This gave birth to what are known as "lag codes", which are long strings that cause instability within Kik.
If you're on kik and people post strings like:
0la.3p.snai7.eo.490.0la.3p.snai7.eo.490.0la.3p.snai7.eo.490.0la.3p.snai7.eo.490.(etc)(shout out to TL1 for his work in this area)
you will lag, ios and android are affected by this.
I have modified the parser within Kik to stop those short lag codes from causing lag.
I issued these Pikik clients to only a handful of individuals (hardcoded their usernames and disabled editing) , typically being used to crash pedophile chatrooms. Someone in this handful decided to leak the file. They attached AndroRat and distributed it under my credibility and name and I don't appreciate that.
The exploit (along with other exploits I've discovered) and suggested fixes have been emailed to Kik without reply.
This is version 7.9 without video support. You can do the same with 8.0+ as I have done but I don't want to distribute that yet. as I'd like to make a menu via smali to add additional features to Kik. (Confirmed fake camera is possible among other things) Hopefully within that time, Kik will patch the exploits I've emailed them about.
Please be respectful to one another with Pikik, it can cause issues for other users without Pikik if you so choose.
I will create additional links if necessary. Happy Easter.
May 6 update:
Added Kik 8.0apk for video playback. Added another layer of lag protection.
-gunther210
Admin note: APK has been removed due to legal complaint from Kik. Do not re-upload. https://github.com/xda/Notices/blob/master/2015/Kik-20150624.md
Warning, I would not recommend trusting. The app was leaked. Gunther stated that he would release the application to the public in the month of July.
424aca said:
Warning, I would not recommend trusting. The app was leaked. Gunther stated that he would release the application to the public in the month of July.
Click to expand...
Click to collapse
Hey mate, that wasn't the case.
I planned to publish the technical details of the xss exploit within kik.com in July but that also leaked.
I encourage anyone to decompile this apk and look for anything malicious or suspicious if they don't trust it. It isn't my style to do that.
I understand you're just looking out for the community.
Take care mate.
Apologies and Results
Yah sorry to come out as aggressive or as if I was pointing fingers. If you are truly gunther, then you are very much aware of the presence of individuals on kik who post links which intercept IP's and I see a new exploit regarding a phishing link "video" with your name on it etc. I just want individuals to be careful. Because I made seemingly false accusations, I have done the task of running a scan on the app in a virtual machine (genymotion) running a various security scans on it. Only avast gave a security warning, but upon rescan it was gone. I have uploaded four images of four different tests. Please, proceed with caution for this application is as wonderful as you anticipate it to be. To those that have root and xposed, i would advise using I believe xprivacy to block any SMS or call log interaction which this app may present if the proof supplied below does not suffice your paranoia which I seem to be having right now.
-424aca
View attachment 3247779
View attachment 3247780
View attachment 3247781
View attachment 3247782
Thx for the tests.
I'm aware of the games being played on Kik. That's not likely to go away but their lack of willingness to correct the problems leaves everyone vulnerable. At least this protects a regular user from another regular user being annoying. The xss exploit needs to be patched immediately. The amount of people getting phished is amazing. I regret sharing info about that exploit.
As I mentioned long ago to anyone on Kik who asks the status quo kik hacker question "can you get ips thru kik?" My response has always been the image handler. The way kik handles their images has been exploitable forever but I'm not yet certain to what degree. After reporting the 2 "main" exploits to Kik, I moved onto checking out my suspicions and getting some confirmation/vindication.
The entire handler for images is a wreck. It's possible to create corrupt image headers (see my pastebin) which will crash Android upon receiving said picture. It's possible to create corrupt image headers to get IP addresses via images (confirmed on iOS by Host 4/6/2015). It's possible to create corrupt image headers to crash Android for lack of associated action.
It's possible to send videos as Gallery, Gallery as Camera, Camera as "Gunther", custom icons, and most likely offsite pngs (apache log taps). It is possible to build a card that exploits these same flaws but with more parameters. The card:// handler is probably only "more secure" because less people use it.
The fact that I can send you a picture that crashes your kik is absurd and it was obvious to me this style of attack would be possible from the first glance at it.
I like Kik but it is a dangerous hangout lately.
424aca said:
Yah sorry to come out as aggressive or as if I was pointing fingers. If you are truly gunther, then you are very much aware of the presence of individuals on kik who post links which intercept IP's and I see a new exploit regarding a phishing link "video" with your name on it etc. I just want individuals to be careful. Because I made seemingly false accusations, I have done the task of running a scan on the app in a virtual machine (genymotion) running a various security scans on it. Only avast gave a security warning, but upon rescan it was gone. I have uploaded four images of four different tests. Please, proceed with caution for this application is as wonderful as you anticipate it to be. To those that have root and xposed, i would advise using I believe xprivacy to block any SMS or call log interaction which this app may present if the proof supplied below does not suffice your paranoia which I seem to be having right now.
-424aca
View attachment 3247779
View attachment 3247780
View attachment 3247781
View attachment 3247782
Click to expand...
Click to collapse
So is it safe or not?
I don't like its dark background. Fix it
PrinceCoc said:
I don't like its dark background. Fix it
Click to expand...
Click to collapse
I changed mine to white.
I recommended you do not try this app. Probably the maker of this modified version add some malicious things. Or something for stealing personal infos
GreekDragon said:
I recommended you do not try this app. Probably the maker of this modified version add some malicious things. Or something for stealing personal infos
Click to expand...
Click to collapse
Damn I've already been using it
GreekDragon said:
I recommended you do not try this app. Probably the maker of this modified version add some malicious things. Or something for stealing personal infos
Click to expand...
Click to collapse
I didn't. Instead of talking dumb ****, why don't you decompile it and check for yourself. I have no desire to take anyone's info.
ODSTZ3RO said:
Damn I've already been using it
Click to expand...
Click to collapse
You're fine mate.
Me Host and Link have been working together on adding several features for pikik2 and their similar releases.
For now pikik2 will be:
Based on 8.1.x
Probable:
Turn off read receipts (Host)
Turn off typing notification (Host)
AntiLagV2 (Gunther)
Fake-Camera Mod (Gunther)
AntiLagv2 secondary check (Link)
(Theme choices by download if below doesn't work)
Possible:
Turning links on/off
AntiLagv2 override by conditional regex by input
Selectable Theme by input
Selectable Image background (Link/Host)*
*This works now but needs some more tweaking.
If you or someone you know is a smali pro, please PM me.
We are hoping to build these ideas as switches from a panel within kik
Also. If you're interested in building an Xposed Module to do these things, please PM me and I will help point to where the above things are taking place.
All credits will be given
If someone wants to reach us on kik. Check in #pikik
Appreciative said:
I didn't. Instead of talking dumb ****, why don't you decompile it and check for yourself. I have no desire to take anyone's info.
You're fine mate.
Me Host and Link have been working together on adding several features for pikik2 and their similar releases.
For now pikik2 will be:
Based on 8.1.x
Probable:
Turn off read receipts (Host)
Turn off typing notification (Host)
AntiLagV2 (Gunther)
Fake-Camera Mod (Gunther)
AntiLagv2 secondary check (Link)
(Theme choices by download if below doesn't work)
Possible:
Turning links on/off
AntiLagv2 override by conditional regex by input
Selectable Theme by input
Selectable Image background (Link)
If you or someone you know is a smali pro, please PM me.
We are hoping to build these ideas as switches from a panel within kik
Also. If you're interested in building an Xposed Module to do these things, please PM me and I will help point to where the above things are taking place.
All credits will be given
If someone wants to reach us on kik. Check in #pikik
Click to expand...
Click to collapse
OK I wasn't going to delete it I just changed its appearance a bit.
NOT working?
I have tried to download the File but i keep getting an error saying I don't have the app installed when I do? Maybe it's because a recent update that I did yesterday April 14, 2016. Any help?
Delete the kik you already have
INTRUTHS said:
I have tried to download the File but i keep getting an error saying I don't have the app installed when I do? Maybe it's because a recent update that I did yesterday April 14, 2016. Any help?
Click to expand...
Click to collapse
Yeah man your in the future, please tell us what its like in 2016
I reeeaally enjoy this app. Buuuut I like the new material design update (8.2.0) more. Pls update.
gallowsArisen said:
I reeeaally enjoy this app. Buuuut I like the new material design update (8.2.0) more. Pls update.
Click to expand...
Click to collapse
Didn't you read the post, their working on it, if you know someone that's good with smali tell them to contact us at #pikik
theattackingdildo said:
Didn't you read the post, their working on it, if you know someone that's good with smali teller them to contact us at #pikik
Click to expand...
Click to collapse
Sorry. I'll look out for anyone with experience. I'm in a few good groups so I'll ask around.
gallowsArisen said:
Sorry. I'll look out for anyone with experience. I'm in a few good groups so I'll ask around.
Click to expand...
Click to collapse
I'll ask some people about it.
First, let me/us say thanks for all the support. It helps keep us motivated to get pikik2 how we want it.
Updates:
We have pretty much narrowed down all the future feature locations.
We are still stuck in the same spot however.
We need a little advice or guidance on how to use toggles and inputs.
We can build the toggles, we can associate them in the places they need to be. But, we aren't sure how to do the following:
We need a generic or simple way to write and read toggle values into the database or preferences. We need to be able to pull these into smali. We are getting progress on Smali knowledge and may be able to import the values ourselves but we need to have a better understanding of how to implement this.
We want to create a check box, no problem. How do we add the value of check box (or inputs) into the db or prefs in the simplest way?
Next, how do we then read the value out of these?
We are reading to use <checkboxprefs but that's not working easy for us so far. We have tried literally hundreds of tests at this point.
My last test was duplicating the widget check box and associating it.
We need help. Someone. Give us a run down of the fastest way to what we need, please. As always, credits will be given.
Thanks mates,
gunther210
I will make a thread asking for more direct help when I have enough posts to do so. Anyone out there who has any advice, we will investigate.
Thanks again.
IR Remote Gear 2
Maintained by cracksmurf
Introduction
One feature that sets the Gear 2 apart from most other smart watches is the inclusion of the IR Blaster which allows us to control a variety of devices right from our wrists. Thanks to the work by biktor_gj in Porting Android to Gear 2 we have gained a lot of new functionality on this older device. However, due to the lack of Android Wear devices that possess an IR Blaster, bitstra started work on modifying the Gear 2 IR Remote. Due to circumstances, bitstra was eventually unable to continue development of this app. On 3/3/2016, development was officially handed over to me, cracksmurf. While I don't have too much experience in coding, I have managed to make some headway in expanding the app and including new devices. Hopefully this will be of use to other Gear 2 users.
Click to expand...
Click to collapse
Code:
*** Disclamer
-- This is project is a continuation of the app mod by bitstra. Original code is not my own and I do not take credit for it. There should be no negative impacts on your device. However, use of this app signifies acceptance of responsibility over any issues that may arise due to it's installation.
Images
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Installation Instructions
on linux or mac:
./adb install -r IRremote_Gear2_1.6.apk
on Windows:
adb install -r IRremote_Gear2_1.6.apk
Click to expand...
Click to collapse
Download
DL link for latest version:
IRremote_Gear2_2.0.apk
Click to expand...
Click to collapse
Changelog
Current changelog: -- 03/09/2016 IR Remote v2.0
[note] -- This is my first release.
[new] -- Added devices:
Audio-Denon-AVC2000
Audio-Samsung-HT-Z320
Camera-Canon-600d
Camera-Nikon-D5100
Console-Microsoft-Xbox One
TV-Konka-KL32PH92U
TV-TCL-LED32D2730M
TV-Hisense-Generic
TV-Free-Freebox Crystal[changed] -- Completed code allowing for more categories that were already partially setup within the app. (plan to expand this for more categories in future releases).
[fixed] -- Currently no new fixes.
Older changelogs:
Current changelog: -- 07/17/2015 IR Remote v1.6
[note] -- This is the bitstra's latest release. All new development is starting from this release.
[new] -- Currently no new features.
[changed] -- Currently no new changes.
[fixed] -- Currently no new fixes.
Click to expand...
Click to collapse
FAQ
Q: How can I request a device be added to the app?
A: Please place all requests for new devices in the "Feature Request" tab above using the following format.
[Device Type] i.e. TV,Cable(or Set Top Box), Blue Ray...
[Manufacturer] i.e. JVC, Panasonic...
[Model Name] i.e. FTS 2505
Q: I'm receiving a [INSTALL_FAILED_UPDATE_INCOMPATIBLE] error when installing.
A: You are most likely updating from a system installed or incompatible version. Follow the below steps to uninstall and reinstall.
Removing Previous version
//If bundled from Biktor's Wear release as system app//
Code:
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//
Code:
adb shell
su
rm -rf /data/app/org.esolutions.irremote-1
rm -rf /data/data/org.esolutions.irremote
reboot
Installing new version
Code:
adb install -r IRremote_Gear2_2.0.apk
Click to expand...
Click to collapse
Thanks To/Credits
bitstra - For initial work on bringing us a fully functional IR Remote that runs on the Gear 2 within Android Wear. Also, for allowing me to continue this project to expand functionality for Gear 2 users.
biktor_gj - For porting Android Wear to the Gear 2
Click to expand...
Click to collapse
XDA:DevDB Information
IR Remote Gear 2, Device Specific App for the Samsung Gear 2
Contributors
cracksmurf
Version Information
Status: Testing
Created 2016-03-03
Last Updated 2016-03-03
Reserved
Well got the project page all finished. Welcome everyone. I hope to be able to meet your device needs on the Gear 2 IR Remote. Any device requests can go in the "Feature Request" tab at the top of the page and I will get to them as quickly as I can. For now I am working on getting the initial release out which includes extra device type categories and the previous requests from bitstra's thread.
Great to see you picked up this project. I will try and install on the new BETA version...
ratmkicksass said:
Great to see you picked up this project. I will try and install on the new BETA version...
Click to expand...
Click to collapse
The download available is still the version released by bitstra. I am currently working on getting my first release put together, and will hopefully have it out by this weekend. The current release was working just fine for me on the September 24th, 2015: Android Wear Lollipop - 5.1.1 (build LCA43) release by biktor_gj. However, last week I installed the test version of 6.0.1 and the app shot out an error saying that my device didn't have an IR Blaster. Most likely due to the fact that biktor hasn't finished getting all his code into that release (which is why you can't find it on the main topic post). Once he gets that out I'll be able to properly test on the new version of the OS. Hopefully there won't be any major changes needed on our end.
biktor_gj said:
IR: Haven't even pushed it yet
Click to expand...
Click to collapse
Awesome to see he let you do this, if theres anything i can do to help let me know. Im no coder but maybe some bug testing?
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.
Ive added the hex codes for the devices i requested into your google sheets. Good luck with everything
Garridon said:
Ive added the hex codes for the devices i requested into your google sheets. Good luck with everything
Click to expand...
Click to collapse
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.
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.
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.
cracksmurf said:
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.
Click to expand...
Click to collapse
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?
Sent from my HTC One_M8 using Tapatalk
Garridon said:
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?
Click to expand...
Click to collapse
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.
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!
zygh0st said:
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!
Click to expand...
Click to collapse
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.
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.
Here is my first release of the updated IR Remote port.
https://www.androidfilehost.com/?fid=24438995911975157
Changelog
Current changelog: -- 03/09/2016 IR Remote v2.0
[note] -- This is my first release.
[new] -- Added devices:
Audio-Denon-AVC2000
Audio-Samsung-HT-Z320
Camera-Canon-600d
Camera-Nikon-D5100
Console-Microsoft-Xbox One
TV-Konka-KL32PH92U
TV-TCL-LED32D2730M
TV-Hisense-Generic
TV-Free-Freebox Crystal[changed] -- Completed code allowing for more categories that were already partially setup within the app. (plan to expand this for more categories in future releases).
[fixed] -- Currently no new fixes.
Click to expand...
Click to collapse
-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.
Removing Previous version
//If bundled from Biktor's Wear release as system app//
Code:
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//
Code:
adb shell
su
rm -rf /data/app/org.esolutions.irremote-1
rm -rf /data/data/org.esolutions.irremote
reboot
Installing new version
Code:
adb install -r IRremote_Gear2_2.0.apk
Click to expand...
Click to collapse
cracksmurf said:
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.
Click to expand...
Click to collapse
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.
zygh0st said:
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.
Click to expand...
Click to collapse
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.
Button tests for xbox one and samsung model HT
cracksmurf said:
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.
Click to expand...
Click to collapse
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.