Related
As long as a Rom doesn't include googlebits it should be fine on google code right? It would be nice to use for bug tracking and a quick downloading service.
Doubt it, since I imagine that a lot of bits are closed-source and harvested from existing ROM dumps and so forth.
I believe quietblongs was the only dev here that actually built his roms from source. With that said. I mean the entire thing except some libs. But I'm not sure if anyone else is doing this. I think most of the aosp roms we have are ports with maybe compiled frameworks from source. Again that's just a guess.
But speaking of quietblongs... I wish he'd come back and make us a bad ass 2.1 aosp build.(a hint to quiet to build us another bare bones build)
I have a "generic" 2.1 AOSP build. The problem is getting the HTC vendor/oem stuff incorporated. I have tried following Cyanogen's lead with his "vendor overlay" in git, also borrowing from Lox's GSM hero stuff, but when I build it that way ((via "lunch htc_heroc-eng") I still end up needing to manually copy the proprietary files one-by one into build to get a resulting system.img. In other words, I'm missing a script that should do this during the build. Since nobody seems to be building for CDMA hero (I find directions for dream, magic, and nexus only), I basically don't trust my result enough to upload for others.
Building 2.1 as "generic-eng" is trivially easy, we could have a "nightly build" setup if we wanted. But getting the vendor stuff properly incorporated into the build (and having the build use these files to generate its source) is not a clear process to me yet. I'm learning but it takes time I don't always have.
On a side note, maybe someone could comment on whether a fresh build with the vendor stuff could/would solve ongoing issues like the camera or whether that is a 2.7/2.9 kernel issue that needs a backport.
5tr4t4 said:
I have a "generic" 2.1 AOSP build. The problem is getting the HTC vendor/oem stuff incorporated. I have tried following Cyanogen's lead with his "vendor overlay" in git, also borrowing from Lox's GSM hero stuff, but when I build it that way ((via "lunch htc_heroc-eng") I still end up needing to manually copy the proprietary files one-by one into build to get a resulting system.img. In other words, I'm missing a script that should do this during the build. Since nobody seems to be building for CDMA hero (I find directions for dream and magic only), I basically don't trust my result enough to upload for others.
Building 2.1 as "generic-eng" is trivially easy, we could have a "nightly build" setup if we wanted. But getting the vendor stuff properly incorporated into the build (and having the build use these files to generate its source) is not a clear process to me yet. I'm learning but it takes time I don't always have.
On a side note, maybe someone could comment on whether a fresh build with the vendor stuff could/would solve ongoing issues like the camera or whether that is a 2.7/2.9 kernel issue that needs a backport.
Click to expand...
Click to collapse
Yeah u will always need proprietary files to build aosp. That's what vendor is for. I've started gathering and trying to setup a community vendor for cdma heros. But just been to busy to finish. Will try soon though an put it on github for all to use.
But as for camera drivers and stuff like that. Ur gonna find that making libcamera build isn't gonna happen as of yet in 2.x aosp. Because it is broken as of the moment and doesn't make. The only solution to gettin camera into an aosp build is to use the libcamera and other camera libs from mine and Flipz HTC Rom. But even then ur gonna need a compatible kernel camera driver to work with it. As of now we haven't got that working fully. But also even once we get the driver working ur gonna have issues in aosp builds with camera as the gsm hero devs have found. As it stands now the aosp camera doesn't fully support our camera. Leaving them left with a 3m camera and I believe no video. It seems that HTC did some extra work in their camera.apk to finish up and give full support for our camera. The problem with that and aosp is like most HTC apks work in and with a HTC modified frameworks. So it goes deep into the framework.jar and many other frameworks files. I won't say it can't be hacked in some how but I will say it won't be easy. But if u manage to pull it of please share because a lot of devs have tried and haven't managed to pull it off as of yet.
Maybe you can point me in the right direction. Attached is my "vendor overlay" attempt. In the first case it's just Lox's stuff for hero with "heroc" in all the right places. The "extract" script is mine, modified by me given Cyanogen's nexus overlay example.
If you can create a git of a proper overlay, that would be great. Even if, as you say, it doesn't get us all the way to a working AOSP ROM.
Lox's language in his extract script is like Cyanogen's in his git repo, ie "who the hell knows if this is right, just guessing". So in that spirit, here is my attempt: a little experience mixed with vendor hatred mixed with voodoo
Feel free to correct me as you can, I would be grateful for a leg up from someone who has been at this longer.
P.S. I can't believe I had to "zip" up a tar.gz tarball to get it to attach to a dev forum (Invalid file). Man, I'm getting old.
P.S.S The included "kernel" file is a zImage I built from your toastcgh 2.7 sources in git. The wlan.ko was built against that...I should double-check that fact...
Ah well, maybe when they redo the forums here they'll think about bug tracking etc but I doubt it.
I did build my aosp rom from source, just built it using the gsm hero's vendor tree, made small adjustments to it for the heroc files. so yea, my rom is from google code to answer the OP's question.
darchstar said:
I did build my aosp rom from source, just built it using the gsm hero's vendor tree, made small adjustments to it for the heroc files. so yea, my rom is from google code to answer the OP's question.
Click to expand...
Click to collapse
EDIT: OHH, I completely misread your thread title, I probably could use google code for my aosp rom to track bugs
darchstar said:
EDIT: OHH, I completely misread your thread title, I probably could use google code for my aosp rom to track bugs
Click to expand...
Click to collapse
Right, I think we all misread it, I believe he was asking why we don't host our code somewhere, like Google Code, with a real bug tracking system, versioning controls, etc. He's got a great point, actually. It would be very nice to have a shared AOSP space, somewhere to see the files and track the issues and changes. ROM development based on AOSP could go on as usual on XDA with that base.
5tr4t4 said:
Right, I think we all misread it, I believe he was asking why we don't host our code somewhere, like Google Code, with a real bug tracking system, versioning controls, etc. He's got a great point, actually. It would be very nice to have a shared AOSP space, somewhere to see the files and track the issues and changes. ROM development based on AOSP could go on as usual on XDA with that base.
Click to expand...
Click to collapse
I got it
The issue is that Google Code won't allow you to host anything you don't have the right to distribute.
5tr4t4 said:
Right, I think we all misread it, I believe he was asking why we don't host our code somewhere, like Google Code, with a real bug tracking system, versioning controls, etc. He's got a great point, actually. It would be very nice to have a shared AOSP space, somewhere to see the files and track the issues and changes. ROM development based on AOSP could go on as usual on XDA with that base.
Click to expand...
Click to collapse
It would minimize on duplicate bug reports at least.
jonnythan said:
I got it
The issue is that Google Code won't allow you to host anything you don't have the right to distribute.
Click to expand...
Click to collapse
Understood, but the proprietary stuff can be pulled from the phone and/or from official releases for other HTC devices given the right script. That's why we need the vendor overlay.
I suppose the follow up question is, "why not just contribute to Android's AOSP core code in git, why create a forked AOSP repo?". That might be right, but we still need the overlay to pull the right files from the device. Perhaps taostcfh or quietblongs or darchstar already have this stuff ready and I'm just late to the game (probably ). Fine, I'd love to see that work so I can help out where possible.
<mini-rant>
This OEM/vendor crap really sucks...should I just repeat what has been said everywhere (and knocked down for very sound business reasons): Google should have released Android under GPL.
</mini-rant>
5tr4t4 said:
Right, I think we all misread it, I believe he was asking why we don't host our code somewhere, like Google Code, with a real bug tracking system, versioning controls, etc. He's got a great point, actually. It would be very nice to have a shared AOSP space, somewhere to see the files and track the issues and changes. ROM development based on AOSP could go on as usual on XDA with that base.
Click to expand...
Click to collapse
Exactly, thanks.
What keeps one of us from leasing a server to share for our (XDA) own CVS, bug-tracking and compiling?
ffolkes said:
What keeps one of us from leasing a server to share for our (XDA) own CVS, bug-tracking and compiling?
Click to expand...
Click to collapse
The fact that someone has to pay for it.
jonnythan said:
The fact that someone has to pay for it.
Click to expand...
Click to collapse
I've got a server but I'm not too familar with CVS, if anyone wants to lend a hand...
ffolkes said:
I've got a server but I'm not too familar with CVS, if anyone wants to lend a hand...
Click to expand...
Click to collapse
I have one too, but I would advocate for something more public, like git or sourceforge or Google Code, XDA, etc. You would want to make sure that you were gaining sharing capabilities and not just isolating yourself...either from upstream improvements or from other community stuff here and on other forums. A thousand people sharing is better than 10-20 people with a server, IMHO XDA has already proven that.
Plus, getting a development server going with all of the niceties of CVS et al is not easy...and there are ready-made solutions already available. None of this addresses jonnythan's point that some of this development is in legal limbo...what happens when someone , even by accident, pushes the google bits onto your public server?
...maybe you would get a cease and desist letter and become famous, LOL.
5tr4t4 said:
...maybe you would get a cease and desist letter and become famous, LOL.
Click to expand...
Click to collapse
Someone needs to combine the power of a forum with the legal protection of a public download site and the bug tracking of google code.
Apparently, I'm too lazy to code that all myself
{
"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?
This goes out to all the dev's working on OSP's or directly with source files and have used Git n Github. I have been trying to setup the development env on my m/c. I am really confused regarding how Git, Gerrit and Repo relate to each other. I know that Git is a VCS, Gerrit is a Code review system, No idea about Repo. I would be really grateful if one of the devs could take time out to explain how these technologies interface with each other using simple eg like the on going CM development. I'm not asking for precise commands, I'll learn that...just wanted to know the high-level working.
Thnx!
Git is a VCS. It was created and is developed mainly by Linus Torvalds, originally for helping in Linux kernel development. It is now very widely used (e.g. GitHub) for open and closed source projects.
Repo is a Python script created by Google for Android. Some would say it's just a wrapper around Git, but it's not so simple. AOSP (and others based on it) consists of many separate projects. All of these are in a specific Git repository so that separate development can go on in each of these without creating merging conflicts or some other bad things. These projects all have a manifest file that describes all of the Git servers, repositories and project paths. You can see the differences in manifest files e.g. among this (CM), this (AOSP) and this (LiquidSmooth).
Gerrit is a code review system also developed by Google for Android. It is like a clone of the mainline source (all of the projects tracked in repo) with an addition of it being open to anybody (registered users in most cases). When you have a good idea, fix or improvement, you start a local branch in your synced repo directory and push them for review. You can ask a developer to review your code and he/she will tell his/her opinion about it either by asking you to upload a new patchset, implementing and adding it to mainline with some modified code or not accepting it because of some issue. Or just somebody finds it useful and looks into it. (Example: My patch for Samsung OMX. My change committed into CM repo.)
TIA! Can't wait buddy!
OT: Don't stress urselves too much man! TC
EDIT: In the meantime I've setup git on my system, and also created a Github account and created a demo repository to play with. After following a few guides at codeschool and git-immersion, I now understand the basics of git, but still confused regarding gerrit and repo. Eagerly waiting for ur reply bro!
I edited my first post. You can find my answer there.
That's a pretty good explanation bro. Thanx for taking time to explain at length!
Thanx!
Tapatalked from my Galaxy R GT-I9103 using XDA Premium App
I don't go to sleep until I utilize my quota of 8 thanx a day!
DIRECT SMALI TO JAVA CONVERTER(This is a work-in-progress. Hop in if you can help!)
Welcome guys!
This project is born because there isn't any reliable way to convert a bunch of smali files into something you can really import into eclipse and compile away. I've lost a few projects in a recent 1 TB HDD crash and man, it wasn't pretty to see I couldn't even get them back with JD-GUI or something. I've done the same with a few .NET projects of mine, so why can't I on Android? you can, but sometimes the tools (JD-GUI or JAD) go nuts and attempting to fix them just gives you a headache so...
Being a smali modder for quite some time, I managed to realize that the entire smali code, if analyzed correctly, it can be converted back to java. We mentally do it when we make smali mods, all I'm attempting to do is to automate the process and make it easier for everyone. Also, it would be really useful to be able to recompile a few Jars and APKs in order to fix device bugs (which is also another reason why I'm working on this).
Some of you would say there is already JD-GUI and JAD, but they're not a real true 1:1 conversion and also most of the times they're not compile-able. Also, There's JEB Android Decompiler but no way I'm gonna pay such a price for something I've been doing mentally and that I can automate with a script made in about a week or a few months. The tool could be great, but the price is too high and my own country's restrictions don't allow me to buy it even if I ever get the money.
The idea here, is to make an app that can translate Smali to Java, directly. Of course, it requires a bit of analysis. It needs to analyze the class directives, the methods and their prologue (parameters, declaration, etc), class annotations and method instructions. So far, I've managed to develop most of the analyzer with a few basic instructions set up for demo purposes.
Of course, I know it needs a bit more work: some variables/instructions don't appear, types are incomplete or missing, etc. But that's why I'm here: I can work on this alone, but, first, it wouldn't be fair. Also, I'm human and by default I have bugs, so I might skip something and make the code go bogus and stuff. And finally, I'd like to request the help of the community. I made this project to see if there's enough attention and contribution from the smart people here, and if there is, I'm gonna give it all to make this project do what it says, 100% error-free.
Note: IT NEEDS .NET FRAMEWORK 3.5. Yeah, and VS 2012. I assume you can make it work with VS2010 or I can make a version soon if there's enough interest, or heck, even Mono as long as it has Linq (I make heavy use of it). The idea is to make a good, open-source parser you can compile even on an arduino with Mono and it will work. But for now, this will have to do. It is my own code and I decided to share it to see if there's interest. If there's enough, I'll do everything I can to provide the tools needed for you guys to help me make this project a reality.
Also, it seems it works with SharpDevelop, so you can compile it under Linux too!
How to contribute:
Source code (active Github): https://github.com/darkguy2008/smali2java
IRC Channel: #smali2java in irc.freenode.net . You can also join us in development chit-chat through web IRC client here.
Fork away!
Well, hoping to attract the attention of you hackers 'round here
- DARKGuy
XDA:DevDB Information
Smali2Java, a Tool/Utility for the Android General
Contributors
darkguy2008
Version Information
Status: Testing
Created 2013-12-31
Last Updated 2014-01-04
Reserved
Thanks for your effort. May I request a small readme or setup guide as I'm generally a Linux user trying this out on my Windows machine?
Sent from my SAMSUNG-SGH-I727 using Tapatalk
This is great, really interested in this, and is the project open source?
robcore said:
Thanks for your effort. May I request a small readme or setup guide as I'm generally a Linux user trying this out on my Windows machine?
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
Hello!
Oh, sure, here's a small resume but if you need more help don't hesitate to ask
First you need to install Visual Studio 2010 or Visual Studio 2012, I don't know if the express editions work, but they should. Then, if you use VS2010, you need to install the 4.5 .NET Targeting Pack for VS2010 which you can find on the MS website. If you install VS2012, it comes with it preinstalled.
Then, I assume you can double-click the .csproj (project file) and it'll open inside a blank solution that will ask you to save before you can compile it (press F5 to build & run). Also, make sure to edit Program.cs and modify it where it says to edit and put the absolute path of a smali file of your choice (for example, C:\users\you\desktop\someclass.smali). There's no need to put double-backslashes due to the "@" before the string literal.
Also, I think it could also work with .NET 3.5 or 4.0, but I didn't test it as I was hesitant to make something that I could publish on here. Over the next few days I'll keep working on it and keep you guys updated
ricky310711 said:
This is great, really interested in this, and is the project open source?
Click to expand...
Click to collapse
Thanks for your interest! I'm glad and yes! you can download the whole source code and binary from the Download section here in the black top bar over the first post. That's the idea open-source and easy to understand!
darkguy2008 said:
Thanks for your interest! I'm glad and yes! you can download the whole source code and binary from the Download section here in the black top bar over the first post. That's the idea open-source and easy to understand!
Click to expand...
Click to collapse
Thanks will definately check it out when I get home!
Thanks so much, trying it now!
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Alright, I finally learned how to use GitHub (it wasn't that hard... yet, lol), so here's a link for you all to try (it's in the main post, too): https://github.com/darkguy2008/smali2java
Also, I modified the code a bit... removed the whole switch/case stuff for each instruction and changed it to functions. Also, SmaliVM is now the main class where the translation to Java happens. I've also made a "buffer system" because, in smali, you need to process a lot of lines to create one Java line, so every smali line adds up stuff to the buffer (if needed) and it "flushes" on each .line directive. So far, so good.
Fork away and I'm eager to see your pull requests!
darkguy2008 said:
Alright, I finally learned how to use GitHub (it wasn't that hard... yet, lol), so here's a link for you all to try (it's in the main post, too): https://github.com/darkguy2008/smali2java
Also, I modified the code a bit... removed the whole switch/case stuff for each instruction and changed it to functions. Also, SmaliVM is now the main class where the translation to Java happens. I've also made a "buffer system" because, in smali, you need to process a lot of lines to create one Java line, so every smali line adds up stuff to the buffer (if needed) and it "flushes" on each .line directive. So far, so good.
Fork away and I'm eager to see your pull requests!
Click to expand...
Click to collapse
404 not found?
ricky310711 said:
404 not found?
Click to expand...
Click to collapse
Whoops, sorry, fixed! stupid reply box, it ate the "va" in my "java" lol.
It's also corrected in the main post
Very interesting, i can't find a word to say! Congrats man and thanks very much!
http://www.xda-developers.com/andro...onverter-makes-smali-more-developer-friendly/
Good luck with your project
yashade2001 said:
Very interesting, i can't find a word to say! Congrats man and thanks very much!
Click to expand...
Click to collapse
thanks for the support! I'm glad you're interested! any kind of help is welcome
eagleeyetom said:
http://www.xda-developers.com/andro...onverter-makes-smali-more-developer-friendly/
Good luck with your project
Click to expand...
Click to collapse
Oh wow! this is great!! thank you very much!! :laugh::victory: these kind of things really give a lot of motivation to keep projects going! :good: love the review, hehe
I had so much trouble with small files before. I don't really work with them much now. Wish that this was there to help me. Keep it up!
Excellent work man! Confirmed working with SharpDevelop + .NET 4.0 too, 3.5 is not possible since some namespaces used are not available prior to 4.0.
Btw there seems to be a bug in SmaliLine.cs, line 135 where the value 0 supposed to be 1, otherwise keep getting index out of bound error.
Code:
if (sWords.Length < [B][COLOR="Red"]1[/COLOR][/B])
Also i did some modification to the main function, so there is no need to recompile everytime, now i can simply run in in command prompt or with batch file.
Code:
if (args.Length == 0)
{
Console.WriteLine("ERROR: No Input File!");
Environment.Exit(1);
}
String sFile = args[0];
Really hope to see this project get more usable soon. Good Luck!
thehacka1 said:
I had so much trouble with small files before. I don't really work with them much now. Wish that this was there to help me. Keep it up!
Click to expand...
Click to collapse
Me too haha, smali files are a headache... they're kinda easy to understand, but man aren't they harder to read? thanks for the support!
codelover said:
Excellent work man! Confirmed working with SharpDevelop + .NET 4.0 too, 3.5 is not possible since some namespaces used are not available prior to 4.0.
Btw i did some modification to the main function, so there is no need to recompile everytime, now i can simply run in in command prompt or with batch file.
Click to expand...
Click to collapse
Hey man, thanks a lot! It's awesome to know it works cross-platform now don't worry, I just pushed a few commits and lowered the framework version, I assume you can test with 3.5 now.
Also, thanks for the code, I just pushed it to the main repo. I actually refactored a few things, hopefully it's easier to understand and handle now. Also, it now works in a buffer-like way so with some work, it will be able to handle lots of smali instructions in a single Java line as it should be
very interested with this project.. hope it will be a simple to use..
This is awesome! I've been working with MIUI for quite some time now, and their utter lack of source code is both frustrating and difficult to work with. Porting eventually works, but for my current ROM, theirs is based on 4.2.2, where the US version went from 4.1.2 to 4.3. So, it works, but it's still not 100%. I'm going to get set up for this and see what I can do with actual source for some of the screwed frameworks.
As I haven't even downloaded anything yet...how crazy difficult would it be to do a whole .jar or .apk...or ROM using this?
petrukgrinder said:
very interested with this project.. hope it will be a simple to use..
Click to expand...
Click to collapse
Thanks for the support! that's one of the main objectives: it should be
digitalhigh said:
This is awesome! I've been working with MIUI for quite some time now, and their utter lack of source code is both frustrating and difficult to work with. Porting eventually works, but for my current ROM, theirs is based on 4.2.2, where the US version went from 4.1.2 to 4.3. So, it works, but it's still not 100%. I'm going to get set up for this and see what I can do with actual source for some of the screwed frameworks.
As I haven't even downloaded anything yet...how crazy difficult would it be to do a whole .jar or .apk...or ROM using this?
Click to expand...
Click to collapse
Yeah man I feel your pain, I also have the same issue with my ZTE device. Of course the main idea is to be able to get back code from your own APKs-JARs but if it works for fixing bugs or allowing more ports on other devices, awesome.
For now the app isn't even usable, it's a bunch of code which tries to translate maybe two or three smali instructions to java but it's not ready for even a small APK. I assume that the fire test should be trying to convert a whole jar file or two, but it could take maybe a few months for it to do that, depending on how much work the project gets from the community.
hello im also tried to do something like this converter but im stack at "if for etc" also i found this http://forum.xda-developers.com/showthread.php?t=2430413 is very good .
i tried to to talk with developer to help him but no answer yet
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.