[APP][2.1+] Gidder - Git server for Android - Android Apps and Games

{
"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"
}
The project in GutHub: https://github.com/antoniy/gidder
Gidder is a Git server implementation for Android that works on top of a SSH server. Access your code anywhere anytime using your Android device.
Gidder is a unique product in that it combines two very complementary ideas. The distributed version control that Git provides and the mobility of any Android device. As a reasult, you can store your projects safely and conveniently in your pocket device and just as easy access them using any WiFi connection. It doesn't matter if you are on a business trip in a hotel, at the office or at home, you can always sync your work using your Android device.
What's the fun of something if you can't share if with anyone else? That's why Gidder provides multiple users that can access any repository they have permissions to. You might want a colleague to be able to just peek at your code - no worries, Gidder gives you the ability to separate permissions to Pull and Push&Pull permissions. So with a simple click you can assign read-only permission to anyone.
Features:
Git server over SSH for accessing your repositories.
Support Push, Pull, Fetch and Clone Git operations which is all you need to achieve successful distribution with Git.
User management - create, create from contact, edit, delete, activate/deactivate, set/remove permissions to repositories.
Repository management - create, edit, delete, activate/deactivate, set/remove permissions for users.
Dynamic DNS integration. A convinient way to use the system when working in different WiFi networks and having a different IP on your laptop. By using Dynamic DNS you can easily access a server without worrying if your Git remote have the correct IP for the current WiFi network. Currently supported providers are No-IP and DynDNS.
Auto update Dynamic DNS hostname when WiFi is On.
Manually update Dynamic DNS with an update button.
Autostart/Autostop server on WiFi On/Off.
Configure server port.
Enable/Disable status bar notifications.
Application widget for Start/Stop the server.

Connection problem
Hi!
Must say that it's a great idea! I use git for storing all my document, regardless if I'm using my laptop or office computer. Adding the phone offers true mobility.
However, I'm having problem accessing the server:
~/git/AppData$ git push gidder
Permission denied (password).
fatal: The remote end hung up unexpectedly
After stopping the server I get the following:
~/git/AppData$ git push gidder
ssh: connect to host 10.10.10.170 port 2222: Connection refused
fatal: The remote end hung up unexpectedly
Which means that I'm talking to the right server. I never get prompted for the password, though. I'm pretty experienced with both ssh and git.
Keep up the good work!

cholmer said:
Hi!
Must say that it's a great idea! I use git for storing all my document, regardless if I'm using my laptop or office computer. Adding the phone offers true mobility.
However, I'm having problem accessing the server:
~/git/AppData$ git push gidder
Permission denied (password).
fatal: The remote end hung up unexpectedly
After stopping the server I get the following:
~/git/AppData$ git push gidder
ssh: connect to host 10.10.10.170 port 2222: Connection refused
fatal: The remote end hung up unexpectedly
Which means that I'm talking to the right server. I never get prompted for the password, though. I'm pretty experienced with both ssh and git.
Keep up the good work!
Click to expand...
Click to collapse
Thank you for your feedback! Can you provide me with additional information (steps to reproduce for example) so I can see if something is going wrong?
~antoniy~

Noob
oliuf4e said:
Thank you for your feedback! Can you provide me with additional information (steps to reproduce for example) so I can see if something is going wrong?
~antoniy~
Click to expand...
Click to collapse
Quick reply! Thanks!
The problem was completely on my side! My /etc/ssh/ssh_config was configured "PasswordAuthentication no", so it didn't allow password based authentication. I usually use pubkey for my gitrepo, so I didn't know I had that. Do you support pubkey?
I hope that someone could learn from my mistake. I found the problem by trying ssh alone like this:
ssh -v -v -v 10.10.10.170 -p 2222 -l guest

cholmer said:
Quick reply! Thanks!
The problem was completely on my side! My /etc/ssh/ssh_config was configured "PasswordAuthentication no", so it didn't allow password based authentication. I usually use pubkey for my gitrepo, so I didn't know I had that. Do you support pubkey?
I hope that someone could learn from my mistake. I found the problem by trying ssh alone like this:
ssh -v -v -v 10.10.10.170 -p 2222 -l guest
Click to expand...
Click to collapse
I'm glad you solve this issue. Regarding public key authentication support the answer is yes, of course I had this idea but for now I don't have nice and simple way to present this functionality. Because of the fact it's a pure client-side app and there are no back-end servers involved there ain't simple ways (at least to my knowledge) to transfer and manage pub keys for the application. Of course this feature is still in the queue for future implementations.
~antoniy~

Good stuff
Definitely a good start and very useful. It did take a bit of work to get going but not too bad... specifically I had to edit my local ~/.ssh/config to allow password auth with the dyndns host and had to do "git push origin master" after cloning the repo locally... but once that was done things worked great.
A couple of feature requests...
1. It would be great if I could set the location of the repo on my device. I have a galaxy tab 2 with a large capacity sdcard, but gidder sets the repo up on internal storage.
2. It would be great to be able to pull up a history of the repo on the device. Just a summary to see where things are at.

jasnell said:
Definitely a good start and very useful. It did take a bit of work to get going but not too bad... specifically I had to edit my local ~/.ssh/config to allow password auth with the dyndns host and had to do "git push origin master" after cloning the repo locally... but once that was done things worked great.
A couple of feature requests...
1. It would be great if I could set the location of the repo on my device. I have a galaxy tab 2 with a large capacity sdcard, but gidder sets the repo up on internal storage.
2. It would be great to be able to pull up a history of the repo on the device. Just a summary to see where things are at.
Click to expand...
Click to collapse
Okay, about the first request - I'll add a configuration option to specify where the repositories should be saved. When I got some time, I'll make it happen.
Regarding the repository browsing on the device - I'm not planning this for now. Don't have much time. You can use Roberto's app AGit to access repository on Gidder and browse the log as a workaround.
~antoniy~

This app is very interesting! I'll try it tomorrow, but already rated it on gplay. if it realy that app how i think i will donate it

Two Feature Request
This is a really awsome app. I've been stalling making it myself since I didn't have the time. It really needs a hotspot mode it isn't hard to implement, and maybe a tasker plugin.
If you need help on this, I wouldn't mind helping I just don't have the time to do it full-time. Since I'm trying to start releasing abunch of apps right now.

First off not trying to be an ass, sadly this is how it will come off.
I am not looking for the source code of the app but I am looking for the source code of the gpl components of this app
which must be hosted by the person who created the app upon any form of distribution.
The only way you would have to also release the source code of the app is if you statically linked to the git code or
any other gpl code.
currently from what I can tell you have violated the GPL License and if not corrected with in two weeks of now, I
will report this to the FSF.

devilsclaw said:
First off not trying to be an ass, sadly this is how it will come off.
I am not looking for the source code of the app but I am looking for the source code of the gpl components of this app
which must be hosted by the person who created the app upon any form of distribution.
The only way you would have to also release the source code of the app is if you statically linked to the git code or
any other gpl code.
currently from what I can tell you have violated the GPL License and if not corrected with in two weeks of now, I
will report this to the FSF.
Click to expand...
Click to collapse
Thank you for supporting the open source community that well. Hope some day you'll realise freeware software is another branch of that same side and you may support it as well. After all some people are investing their free time to do something for the community (and yes, it seams other people are playing "badass" online).
Never the less, there is a plan to go open source but that won't happen until I prepare the code so other people can understand it easily. And that is not and will never be related with what you're trying to do. To be honest people like you pushes me away from contributing than the other way around.
Thank you for your post, hope you're happy for what you're doing.
Regards,
Antoniy

Antoniy I wouldn't take offence to what devilsclaw has said in fact he's trying to help you out although IMHO his approach is a little heavy handed, but that's just my opinion. If he's going to threaten people with the FSF then IMHO it's up to him to try to help people comply with the licences, if they refuse the help then reporting them is probably appropriate.
(Disclaimer: I might not be 100% correct so please do some googling to be sure).
When you make use of libraries that have a GPL licence it means your code automatically has the GPL licence applied to it and have to make the source to your code available...hence why GPL is loved as much as it is hated. If you'd used LGPL licenced code then things would be a little different. Making the code available doesn't mean you have to host it somewhere or make it particularly public but you would have to provide it on request. So for instance if I emailed you and asked for your source you'd have to make it available to me I.e. email me a zip of the source, provide somewhere where I can download it from, etc. (don't worry I'm not going to do that ) because of the GPL licence.
I realise you have pride in the software you write and hence only want to make it "public" when you're happy with it and you can stick with that plan, as long as you provide the current source in whatever state it is in to anyone that actually requests it.
Hopefully this won't put you off as I think your application is great from watching your video and I'll be giving it a try, the fact it's free is fantastic!! All you need to do is probably do some research on what licences are applied to the code you're using and see how that affects your code. Be careful it's a bit of a minefield and there are plenty of misinterpretations/misundertandings out there. Once you've got a grip on what the different licences mean and the consequences of them then hopefully you'll be happy contributing in the future.
As a side-note, making the source available for your application will probably mean more people will use it. Source code is quite a sensitive thing to be storing in something you don't have 100% trust in, providing the source to your application will mean that users can establish that trust. As one of the review comments points out on Google Play they want to be sure the code they're storing through your app isn't being transmitted somewhere else without their knowledge.
HTH
mobby
oliuf4e said:
Thank you for supporting the open source community that well. Hope some day you'll realise freeware software is another branch of that same side and you may support it as well. After all some people are investing their free time to do something for the community (and yes, it seams other people are playing "badass" online).
Never the less, there is a plan to go open source but that won't happen until I prepare the code so other people can understand it easily. And that is not and will never be related with what you're trying to do. To be honest people like you pushes me away from contributing than the other way around.
Thank you for your post, hope you're happy for what you're doing.
Regards,
Antoniy
Click to expand...
Click to collapse

mobby001 said:
Antoniy I wouldn't take offence to what devilsclaw has said in fact he's trying to help you out although IMHO his approach is a little heavy handed, but that's just my opinion. If he's going to threaten people with the FSF then IMHO it's up to him to try to help people comply with the licences, if they refuse the help then reporting them is probably appropriate.
(Disclaimer: I might not be 100% correct so please do some googling to be sure).
When you make use of libraries that have a GPL licence it means your code automatically has the GPL licence applied to it and have to make the source to your code available...hence why GPL is loved as much as it is hated. If you'd used LGPL licenced code then things would be a little different. Making the code available doesn't mean you have to host it somewhere or make it particularly public but you would have to provide it on request. So for instance if I emailed you and asked for your source you'd have to make it available to me I.e. email me a zip of the source, provide somewhere where I can download it from, etc. (don't worry I'm not going to do that ) because of the GPL licence.
I realise you have pride in the software you write and hence only want to make it "public" when you're happy with it and you can stick with that plan, as long as you provide the current source in whatever state it is in to anyone that actually requests it.
Hopefully this won't put you off as I think your application is great from watching your video and I'll be giving it a try, the fact it's free is fantastic!! All you need to do is probably do some research on what licences are applied to the code you're using and see how that affects your code. Be careful it's a bit of a minefield and there are plenty of misinterpretations/misundertandings out there. Once you've got a grip on what the different licences mean and the consequences of them then hopefully you'll be happy contributing in the future.
As a side-note, making the source available for your application will probably mean more people will use it. Source code is quite a sensitive thing to be storing in something you don't have 100% trust in, providing the source to your application will mean that users can establish that trust. As one of the review comments points out on Google Play they want to be sure the code they're storing through your app isn't being transmitted somewhere else without their knowledge.
HTH
mobby
Click to expand...
Click to collapse
Hello Mobby and thank you for your response.
I'm aware with the differences in the licenses and the fact is - I'm not using any GPL licensed libraries. The libraries I'm using are Apache 2 License, MIT License and EDL and I'm not forced by any of those to provide my code to anyone. devilsclaw is just confused and want to educate people the strangest way possible. But anyway. My missing is that I have to list the name of the libraries and their licenses somewhere in my app - that's correct and should be fixed some time in the future. My app is not forced to be open-source and due to that fact and many more I still do not intend to make it open source.
Yes, I'm aware people needs to feel safe for their code, but being open source is not a MUST, it's a bonus that people should recognize. You cannot just go around telling people do this and do that without first stop and consider that you're talking about their time and money and also without consider that you might actually be wrong.
Anyway, let's leave it at that. When I find the time needed I'll release the app open source because there is no reason for me to keep it closed. It's just a tool I build for myself and share with others.
Hope you'll enjoy using it.
Regards,
Antoniy

Ah that's cool, glad the licences are not a problem.
Oh definitely open source is not a must and I hope you don't think I was implying that you must open source your code. I was just offering my opinion that it might be good.
In either case you've created a great app and I will certainly give it a try and leave a review on Google Play at some point.
oliuf4e said:
Hello Mobby and thank you for your response.
I'm aware with the differences in the licenses and the fact is - I'm not using any GPL licensed libraries. The libraries I'm using are Apache 2 License, MIT License and EDL and I'm not forced by any of those to provide my code to anyone. devilsclaw is just confused and want to educate people the strangest way possible. But anyway. My missing is that I have to list the name of the libraries and their licenses somewhere in my app - that's correct and should be fixed some time in the future. My app is not forced to be open-source and due to that fact and many more I still do not intend to make it open source.
Yes, I'm aware people needs to feel safe for their code, but being open source is not a MUST, it's a bonus that people should recognize. You cannot just go around telling people do this and do that without first stop and consider that you're talking about their time and money and also without consider that you might actually be wrong.
Anyway, let's leave it at that. When I find the time needed I'll release the app open source because there is no reason for me to keep it closed. It's just a tool I build for myself and share with others.
Hope you'll enjoy using it.
Regards,
Antoniy
Click to expand...
Click to collapse

mobby001 said:
Ah that's cool, glad the licences are not a problem.
Oh definitely open source is not a must and I hope you don't think I was implying that you must open source your code. I was just offering my opinion that it might be good.
In either case you've created a great app and I will certainly give it a try and leave a review on Google Play at some point.
Click to expand...
Click to collapse
Thank you again for joining the discussion and for sharing your opinion. I really appreciate it and I don't think you were pressing me to go open source or anything, so no worries. Hope you'll enjoy using the app.
Regards,
Antoniy

Feature request
I have been looking for this for ages as i have an android tv box connected to a couple of disks with an ssh server that i'm using as a NAS and always wished i could have some version control on it too. Sadly my tv box connects via cables rather than wireless so Gidder will not work in its current state. Any chance of cable support in the future?

thomaskwscott said:
I have been looking for this for ages as i have an android tv box connected to a couple of disks with an ssh server that i'm using as a NAS and always wished i could have some version control on it too. Sadly my tv box connects via cables rather than wireless so Gidder will not work in its current state. Any chance of cable support in the future?
Click to expand...
Click to collapse
I don't plan to support that feature because it's wished from just a couple of users and currently I just don't have the time. If you're android developer I could share the code with you and you can add the feature yourself.

Many thanks
oliuf4e said:
I don't plan to support that feature because it's wished from just a couple of users and currently I just don't have the time. If you're android developer I could share the code with you and you can add the feature yourself.
Click to expand...
Click to collapse
Thanks for the quick reply. I'm a developer by trade and dabble in android so would love to have a go. Obviously anything i come up with i'll merge back in.

thomaskwscott said:
Thanks for the quick reply. I'm a developer by trade and dabble in android so would love to have a go. Obviously anything i come up with i'll merge back in.
Click to expand...
Click to collapse
Sounds great. Please send me a personal message with your email and bitbucket account.
~Antoniy~

Hi,
I would want to transfer my repositories/users to another phone running Gidder. I've copied the Gidder directory from one phone to the other but when I run Gidder, the repositories/accounts aren't showing up.
Are there any other files I need to copy from the other phone?

Related

Collabertive Effort Community Update Application

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?

An application challenge for an altrustic purpose!

Hi.
I am using an HTC HD2.
So here's the challenge - or maybe not!
These guys (communicationautism.com) released PixTalk (see there download section), a WM application for children with Autism to allow them to communicate. The dark side (aka IPhone) have released a commercial application called Grace which achieves the same thing.
PixTalk is Open Source and the licence allows modification and redistribution.
The issue is this: I have been advised that it will not run on 800x420 screens (which is the HTC HD2). I get the following script:
ArgumentOutOfRangeException at System .IO.FileStream_Position(Int64value)
at Pixtalk>Form1.ctor()
at Pixtalk.Program.Main()
I am running it on an HTC HD2 1024Mhz with 800x480 display.
OS version is 5.2.23554.
I am running Microsoft .NET CF 3.5 (which is built into a customized ROM).
One thing I guarantee - I will be donating to the first person who can assist me as I have a 4 year old with Autism and I don't want to buy an IPhone!
Thanks in advance
Andrew
i'm sorry i'm not a developer, otherwise i would help you surely to make the app work, without any donation of course, the biggest one is the opportunity to can help your son.
bye!
ajt320 said:
ArgumentOutOfRangeException at System .IO.FileStream_Position(Int64value)
at Pixtalk>Form1.ctor()
at Pixtalk.Program.Main()
Click to expand...
Click to collapse
Doesn't sound like a screen related error, sounds more like you have a file that its trying to open and it's either missing or corrupt. You say it's open source, but I don't see the source available on their site ... do you have it or can point me to it? If so I'd be happy to take a peek.
-Chuck
I only have the CAB file and associated images at this stage. I have requested the program co-ordinator for the code and will get back to you as soon as I have it.
EDIT: Sorry it is not a CAB but an EXE.
The licence reads:
PixTalk is a software application for Windows Mobile 6 that allows people to communicate using icons. PixTalk has been funded by a grant from Microsoft Research.
Copyright (C)
Old Dominion University, Norfolk, VA, USA Claremont Graduate University, Claremont, CA, USA
This program is free software: you can redistribute it and/or modify it under the terms of the BSD License as published by the Open Source Initiative.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the Open Source Initiative OSI - The BSD License: Licensing
for more details opensource.org/licenses/bsd-license.php
Although I've never developed for compact .net, if you will be able to obtain the source, I'll do my best to help.
My uncle has Autism, Just wanted to thank you for putting this up!
Much respect!
I would donate to help If i wasnt so broke with 11 month old son..
Best of luck in your development!
I'll happily look at this once the source is available.
No donations required - I'm just a sucker for a good cause.
ajt320 said:
ArgumentOutOfRangeException at System .IO.FileStream_Position(Int64value)
Click to expand...
Click to collapse
it seems that the app tries to read data from a position in the file which is beyond the filesize.
e.g.
the file being read has a size of 2.000 bytes, and the app tries to read from position 2.500.
hebbe said:
it seems that the app tries to read data from a position in the file which is beyond the filesize.
e.g.
the file being read has a size of 2.000 bytes, and the app tries to read from position 2.500.
Click to expand...
Click to collapse
Or trying to read from a file that doesn't exist, and is being created by the stream object (whatever type of stream it actually is). It's pretty much guesswork until we see the source code.
Thanks
Thanks everyone for your great support.
The source code is on its way!
I just have to agree that the fix or updated version will be available to communicationautism.com for public download off their site.
The developer has said full credit will be attributable to those of you involved in the fix. I am hoping that will be some good cudos for you guys and gals!
ajt320 said:
Thanks everyone for your great support.
The source code is on its way!
I just have to agree that the fix or updated version will be available to communicationautism.com for public download off their site.
The developer has said full credit will be attributable to those of you involved in the fix. I am hoping that will be some good cudos for you guys and gals!
Click to expand...
Click to collapse
Nice one mate. It'll be like a busman's holiday
Source Code
Here is the source code for Pix Talk.
Please read the earlier posts for the condition attached to further development and also what the problem is all about.
rapidshare.com/files/381341025/pixtalk.zip
Please feel free to PM me with any questions or requests for other information.
To give you some idea of the IPhone applications check out: //blog.steventroughtonsmith.com/2010/03/grace-picture-exchange-for-non-verbal.html#comments
Thanks in advance to all who contribute to this extremely beneficial application. I will ensure that your names are revered far and wide!!!!!
Still Going
Hi all.
johncmolyneux is on board and it would be good to get some other members involved - good for the developers and good for XDA as this is truly a worthwhile application.
HELP
OK.
John M is unfortunately unable to assist.
Is there anyone else who may be interested?
Can you please re-upload the source code because it is no longer available for download.
Good Luck
Hope someone can help you with the app
Source Code
Hi.
Here is the code:
http://rapidshare.com/files/412861773/pixtalk.zip
Let me know if you need any assistance in any way whatsoever and I will see if I can oblige.
Thanks for your interest!
Please check your PM's. I have uploaded an initial working version for you to test.
Once any problems are fixed I will provide a public download link as well as a link to the source.
Thanks
Thanks a bunch!
Have downloaded and will test first thing in the morning.
Mate I appreciate the time you have put into it so far!
Greetz
Where can I find this updated version
Hi,
I just downloaded the app from the site, and seem to have similar issues. This is for my autistic son. I found this thread. Can I get the updated app - also for the HD2. I do have dev experience too, so if the source code is available, and the problem is not fixed, I can look at help at fixing it too.

[Q] Rules of Open Source development

Hi!
After only being a user for a long time, I've recently begun to develop for Android as well, and I think that I have identified quite a few niches that could use better apps. However, I've never collaborated on an Open Source project, and I'm really unsure what the written and unwritten rules of the subculture are. Could anyone point me in the direction of good resources to learn about them? I know I can probably find those through Google, but I wouldn't know if I'd end up on any site owned by Stallman or Shuttleworth and I'd rather be part of the mainstream, so to speak.
To indicate what kind of questions I'd like to have answered, without requiring anyone to answer them here: What level of expertise is required? Can I just join anyone and upload to their repository, relying on them to sort out the parts they want? When can or should I fork a project? When is it considered rude to take code snippets from someone? How sure can I be that the project's owner won't change the license and steal my code? How would those questions be answered if money is involved? Is it considered reasonable to make an Open Source application that people pay for in the Play Store? How would I handle contributions to such a project? What would be the best license to ensure that I both contribute to the Open Source movement and protect myself against people stealing code? (I. e. just forking it and slapping their name on it.) And many, many more - as I said, I'm really unsure how to start out with this.
Thanks very much in advance!
Regards,
David
Maybe I can help you on a few of those points. First off, feel free to fork anything you feel like, whenever you feel like something needs to change. Also feel free to push any changes you make back to the original project. The project owner can decide what to merge in. As for lisening, please note Im NOT A LAWYER, however, I think I can offer some general knowledge. If code is under a typical open source license, the code at that particular point in time is free to be viewed by anyone. A lot of open source licenses, though not all, are considered 'copy-left', in that any code DERIVED from the liscensed code also has to follow the same license (GPL comes to mind). This helps from people 'stealing' your code at a later point under a closed license. As for taking code snippets, it depends on the license of the code. If you grab a piece of code from a GPL codebase, whatever you're using that code in also has to be GPL licensed. You are in essence taking their code, and modified it. Learning more about different open source licenses might be something to look into, depending on how far you want to delve into this As for making people pay on Play store for open source projects, its certainly acceptable. A lot of people make money from open source software by prividing some form of 'support'. Whether thats tech support, or whether its compiling, packaging, and making it available (as you might do for an android app) you are providing some sort of service aside from the actual code that people will pay for. I've seen a few projects go this route. Hope this gives you more answers than it does questions! The OSS community I've found to be a pretty easy going group of people, so long as you follow a little common courtesy, and have a bit of common sense. Cheers!
Thanks a lot for your reply! It has certainly helped me to make my mind at ease - I know that Open Source people can often be _very_ friendly and open, but it seems like you really do not want to get on their bad side if you intend to be a developer. That's also why I especially worry about being rude, not about doing something illegal - the licenses themselves seem to be quite permissive.
Quick followup question on the money thing, though - is it accepted by Google if I offer a paid app in the Play Store and at the same time free on F-Droid? Or would I have to ask someone to compile and upload it there without my official participation? Because that would kinda be the ideal model for me - Open Source, free app on F-Droid and sideloaded, "lite" and paid versions in the Play Store. Something like that would be good to know before I actually begin thinking about deploying some app.

[APP][ALL ANDROID VERSIONS] DEVELOPER CONSOLE for Google Play [Open-Source]

Hi I have an Google Play Dev Accaunt and Google have for everything an App ( Google Analythic , Google I/O etc.) but not for thhe Google Play Developer Console and beccause that I made an app about that !
I know that app isn´t perfect and it unnecessary but I think it's nice for something even an app to have
Feedback is welcome !
And sorry for my bad english ...
Screenshots :
*Coming Soon*
The Open-Source Code is on GitHub :
https://github.com/Ch-Developer/Developer-Console
Click to expand...
Click to collapse
Download :
apk : View attachment 2887193
on Play Store : https://play.google.com/store/apps/....ai_christian_developer_app.Developer_Console
Developer_Console(2) is the old Version at the new Version changes :
#add imprint
#fix bug at log in
reserved
Well this just looks terrible.
ktetreault14 said:
Well this just looks terrible.
Click to expand...
Click to collapse
Why you so negative?
To op, great job
ktetreault14 said:
Well this just looks terrible.
Click to expand...
Click to collapse
Sorry but better than nothing or ?
gamepois0n said:
Why you so negative?
To op, great job
Click to expand...
Click to collapse
Thanks
I meant as in it looks like it steal your google sign in credentials.
ktetreault14 said:
I meant as in it looks like it steal your google sign in credentials.
Click to expand...
Click to collapse
Do not worry it does not. But if you do not believe me, here is the SOURCE code is made with beta AppInventor (http://beta.appinventor.mit.edu/)
View attachment Developer_Console.zip

			
				
believe me now?
sorry to sound truly negative but it is with best interest; but why would you be rfeleasing source code that is irrelevant to others to be able to check? if you are going to post a source code using a developement software thats minimally used to begin with? you might as well just make a simple layout, use buttons, and just load webviews to just load the mobile website for the developer console... as stupid as that may sound thats basically all i can truly think would be a good use for that because when its something as secure needed as the app developers developerconsole u will NEVER see too many people use random apps to access it, let alone using .shm and othe runknown file formats that dont open with notepad; so posting such soruce code is no use to any developer to "check for yourself" as it is still unccesable to the developers to check...
in other words basicly this topic should be marked as closed as there is no true way to check the legitmacy of this app and the codes submitted apon requested to see if its not malicious is irrelevant; as a google account hacking may be one thing; but a hacking to a developers console cannot be acceptible to other developers and thus why not many apps are made for the console as it just isnt trusted by other develoers to use unless it is really from "pub:Google inc." on google play
jkok said:
sorry to sound truly negative but it is with best interest; but why would you be rfeleasing source code that is irrelevant to others to be able to check? if you are going to post a source code using a developement software thats minimally used to begin with? you might as well just make a simple layout, use buttons, and just load webviews to just load the mobile website for the developer console... as stupid as that may sound thats basically all i can truly think would be a good use for that because when its something as secure needed as the app developers developerconsole u will NEVER see too many people use random apps to access it, let alone using .shm and othe runknown file formats that dont open with notepad; so posting such soruce code is no use to any developer to "check for yourself" as it is still unccesable to the developers to check...
in other words basicly this topic should be marked as closed as there is no true way to check the legitmacy of this app and the codes submitted apon requested to see if its not malicious is irrelevant; as a google account hacking may be one thing; but a hacking to a developers console cannot be acceptible to other developers and thus why not many apps are made for the console as it just isnt trusted by other develoers to use unless it is really from "pub:Google inc." on google play
Click to expand...
Click to collapse
So for example, I use a different google account for google for play and store in the browser I'm not always logged accaunt with my App Maker wherefore I use this app because I do not have an extra logout. And I can only repeat it is not a hack app that would AppInventor with the impossible
Based on the screenshots it seems like the app is just a bunch of WebViews that load the mobile version of the Dev Console. That isn't much different from just loading the page in the browser....and there's the added security concern about stealing account credentials as someone pointed out earlier.
Also, if you're going to make your project open source, don't share a proprietary format. Share the raw java source code on Github.
If they tell me how happy ... in a normal app with eclipse but I knew this I did with AppInventor as I have already written ...
davelee1054 said:
Based on the screenshots it seems like the app is just a bunch of WebViews that load the mobile version of the Dev Console. That isn't much different from just loading the page in the browser....and there's the added security concern about stealing account credentials as someone pointed out earlier.
Also, if you're going to make your project open source, don't share a proprietary format. Share the raw java source code on Github.
Click to expand...
Click to collapse
exactly! developers appericate when u "open source" to use a format we ALL can use and are comfortable with; i would prefeer even obfusticated java code that u need to route where all the things go thghen some random format they send out to use their program; but i have deminstrated to people in my local area that just because the app uses webviewsx it does not mean safe; there is still intents you can use to monitor keypresses in certain feilds (also why newer keyboard apps say they dont keep logs in their privacy notes because such things are known for keylogging)
and even if it is build in eclipse i dont feel i need to use an extention as he seems to make it sound like to just view it as i tried reading it in eclipse (as i removed notepad, wordpad, microsoft office so i can use eclipse on all documents) so even if i could see "the codes" why push your application to read the codes as even if u released the source, its still not readable without your extention program you made, and it may seem legitable to you as the developer (trust me on my app sms Tasks some things i do to it are questioned by some just for the fact its a sms-reciever client to control phones remotely with a pass phrase, u can see it in my sig for more details if u wanted further looks) but in regards to this not many people trust these things as you either need to use someone elses program to even read it, people dont trust random tools with little credits to it, and expecially when the app is sketchy and its logcats (and apk tool'd decompiled source codes when de-obfusticated) does show indeed this is WEBVIEWS but instead it also throws some exceptions, some exceteras, and a few more things then just loading a webview as it does, so im just saying that when you are doing stuff like these expecially something as secured needed as the developers console to release their apps, to release monitations, to make money and review statistics, not many people will trust a app to do so, and are even sketchy using mobile browsers to do so expecially from mobile internet (not wifi) as all networking is tracked from them and everything done on it even more then wifi-internet-compatible companies do even with VPN's and stuff theres some things that are truly not trusted in 3-rd party sources without true credibility, some people never trusted paypal in its early years due to it keeping logs of peoples creditcard information, social security information, and other details for tax-based incomes as even at its early times the encryptions used were minimal to what they have now
basicly if you read all the comments here, and all whats in them u will see that if you release the codes that made it, use it in a format we can all truly see and use as the sources u released are useless to debug or see its true credibility
Well said
-_- I gave you the source aso ....
Hey I make it to GitHub !
The Open-Source Code is on GitHub :
https://github.com/Ch-Developer/Developer-Console
Click to expand...
Click to collapse
Mhhhh..

[Mod][App][2.0 - 03.09.2016] IR Remote Gear 2

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.

Categories

Resources