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.
Related
It been a couple of weeks since i started the Cyanogen Updater - which made it to market in less than 24 hours. It was on everybody's TODO list and it just took one thread being opened to get it done.
Lets try and pull off another miracle....
LETS GIVE ANDROID REAL OBEX SUPPORT
Thanks to the openOBEX guys we have a command line tool to do the job - but that ain't quite good enough.
The average user doesn't want to have to type - thats barbaric in this day and age (personally i love it, but i am a little bit weird)
We have something to build on - it is already integrated in to cyanogens roms
We have two real options - include the required tools or just make the gui access the tools - either way, it can be done.
Yes, there is already Bluex... But why should we pay for something that the phone should already have???
If you are with me - post here. If you want to be a coder, tester, art-guy or just support us with a few thanks this is where to do it
You can PM me here or email me at [email protected]
Google Code
Bluetooth Stack Development Thread
OpenOBEX Thread
OpenOBEX @ Gitorious
Cyanogen's Experimental Branch
i will hellp you out a little bit with bugfiuxes and so but my primary thing is the updater
im fairly new to the whole android and dont know much but im willing to test. ive been testing CM roms since he started coming out with them.
This should be pretty simple, in theory anyway. All we technically have to do is have something that browses thru the filesystem (think SUFBS), and then when you click a file initiate the shell commands necessary or openobex. For recieving there could be a seperate tab at the bottom that when you switched to it it would open the socket to receive a file.
Art guy - reporting in!
Will lend my support whenever possible. As always, great to see more community oriented efforts like this. Once you guys get the app to a working point, I'll be happy to do some artwork for it like the CM Updater thread. Hopefully we can do this again fast.
great to have you on board again prash
i was hoping u n matt would find this thread
anyone who wants added to the google code administrator list - let me know and it shall be done
GOD bless you ALL!!
im sure when cyanogen sees this HE will bless us
im realloy glad to see another project, especially one as useful as this!
thanks....
all we need is some half-decent coders and we will be all set
it is theoretically very simple....but with time it will become more and more complex with extra features hopefully
Im going to jump right in and be THAT guy ... what is open obex?
OBEX=OBject EXchange=how protocol used when sending via bluetooth ot infrared
Open=open source=anyone can use the code with no copyright issues
OpenOBEX=2+2
This will be VERY interesting to follow, this is definately the only feature missing from android, and with prash doing graphics.... its gonna look good for sure (@ prash, using systemforce3... tried new dark hero, 3 hours later I was back to sf3... love the clock ) back on topic... if the knowledge of the coders here is anything to go by, I recon obex will be done by CM4.0.3
Hello,
i'm a sophomore college student look forward to learn how to code for android.. took two java classes in college.. how or where do i get started to learn the code, and may be i can be useful on the next project?
Click on my name at the bottom of the signature to email me..
kmassada said:
Hello,
i'm a sophomore college student look forward to learn how to code for android.. took two java classes in college.. how or where do i get started to learn the code, and may be i can be useful on the next project?
Click on my name at the bottom of the signature to email me..
Click to expand...
Click to collapse
Here's a start on learning
Also in college, computer science major, taken a bunch of programming classes so I'll try and be of some use
garok89 said:
It been a couple of weeks since i started the Cyanogen Updater - which made it to market in less than 24 hours. It was on everybody's TODO list and it just took one thread being opened to get it done.
Lets try and pull off another miracle....
LETS GIVE ANDROID REAL OBEX SUPPORT
Thanks to the openOBEX guys we have a command line tool to do the job - but that ain't quite good enough.
The average user doesn't want to have to type - thats barbaric in this day and age (personally i love it, but i am a little bit weird)
We have something to build on - it is already integrated in to cyanogens roms
We have two real options - include the required tools or just make the gui access the tools - either way, it can be done.
Yes, there is already Bluex... But why should we pay for something that the phone should already have???
If you are with me - post here. If you want to be a coder, tester, art-guy or just support us with a few thanks this is where to do it
You can PM me here or email me at [email protected]
Google Code
Bluetooth Stack Development Thread
OpenOBEX Thread
OpenOBEX @ Gitorious
Cyanogen's Experimental Branch
Click to expand...
Click to collapse
There is a aplication from the market called andrOBEX, and i think that app cover this.
Go to www.androbex.com and see if it is true, or try to work with the author to make it better.
If i'm wrong, count me in to help.
Does openobex support viewing directories and files which someone else is sharing and/or selecting your own directories for others to browse? I havent tried bluex but the description for that doesnt say whether it does or not, I dont know if that is based on openobex anyway though.
Would really like to see the development for this like the cyanogen updater, wish I could do something to help besides test.
i had no idea androbex existed - il look into it
this thread may be redundant....
Androbex doesn't appear to be able to receive files. Getting obexftp or something similar running shouldn't be hard. It just needs to be secure.
cyanogen said:
Androbex doesn't appear to be able to receive files. Getting obexftp or something similar running shouldn't be hard. It just needs to be secure.
Click to expand...
Click to collapse
Bluex can recieve with root access.
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?
So I'm planning on putting this on the android market and I really don't know much about java. Yes I have a lot of free time to learn it but I'm trying to get this done faster than it takes me to learn the java language (not to say that I'm not going to learn the language any way ). I am looking for a partner/team to help me make it an app on the android market. There will be a free version of the application (for xda users of course) and a paid version so that us as a team can make a profit for all our hard work. I my vision for the app is to make it completely universal for all of android. I have the files and tweaks all set already set so that I can have tweaks for ALL of android OS's because I've been holding on to these for a while waiting to see if I could learn java fast enough to do it alone. The specifics of my vision are to make seperate sections in the UI of the app so that the user can choose a category and apply tweaks according to that category. If you are interested in helping me make this an app for all of android phones then please let me know here or through pm. Also we will be splitting the profits equally. So if there are 5 of us we split it 5 ways, 3 of us split it 3 ways and so on and so on. Also I plan on only charging $0.50 - $1.00 for the app. I don't think that is too bad of a price. Can't wait to get this show on the road because I've been holding back on so much and releasing it with the app (which will be huge as is) will be so much more awesome
Can't wait to get to work with the team.
- Kifno
Dude you could've just hit me up on gtalk! I'll give you all the info and let you gitter done on your own. Nobody should be making anything off the work you put in to this!
my signature is better than yours
Okay we'll chat on gtalk later And once I do get it in apk format and on the market, I'm going to give you a big donation for helping me do this
Lol I don't do donations bro. This is fun. Once you start getting paid for it, it's not fun anymore! The whole idea behind xda (as I understand it) is to share information and have fun with what we do. That's why I've been defending your work since day one. I can tell how much fun you have doing this. I'll help as much as I can bro. Just make sure you come with me to the evo 3d when it drops!
my signature is better than yours
abadasstanker69 said:
Lol I don't do donations bro. This is fun. Once you start getting paid for it, it's not fun anymore! The whole idea behind xda (as I understand it) is to share information and have fun with what we do. That's why I've been defending your work since day one. I can tell how much fun you have doing this. I'll help as much as I can bro. Just make sure you come with me to the evo 3d when it drops!
my signature is better than yours
Click to expand...
Click to collapse
That's a great attitude brother, +1. And,
My MOS is better than yours.....(Scouts Out)
Suck it.....LOL
abadasstanker69 said:
Lol I don't do donations bro. This is fun. Once you start getting paid for it, it's not fun anymore! The whole idea behind xda (as I understand it) is to share information and have fun with what we do. That's why I've been defending your work since day one. I can tell how much fun you have doing this. I'll help as much as I can bro. Just make sure you come with me to the evo 3d when it drops!
my signature is better than yours
Click to expand...
Click to collapse
I was planning on the Epic 4G (mostly because I don't have the funds to get the Evo 3D). But I'll just stay on the HeroC longer until I have enough to get it so that I can be in the same sub-forum as you buddy And time to get started I'll email you right now if you are not online on gmail. And yes I have A LOT of fun developing. I get a huge smile on my face whenever I do something even better for our herocs
kifno said:
So I'm planning on putting this on the android market and I really don't know much about java. Yes I have a lot of free time to learn it but I'm trying to get this done faster than it takes me to learn the java language (not to say that I'm not going to learn the language any way ). I am looking for a partner/team to help me make it an app on the android market. There will be a free version of the application (for xda users of course) and a paid version so that us as a team can make a profit for all our hard work. I my vision for the app is to make it completely universal for all of android. I have the files and tweaks all set already set so that I can have tweaks for ALL of android OS's because I've been holding on to these for a while waiting to see if I could learn java fast enough to do it alone. The specifics of my vision are to make seperate sections in the UI of the app so that the user can choose a category and apply tweaks according to that category. If you are interested in helping me make this an app for all of android phones then please let me know here or through pm. Also we will be splitting the profits equally. So if there are 5 of us we split it 5 ways, 3 of us split it 3 ways and so on and so on. Also I plan on only charging $0.50 - $1.00 for the app. I don't think that is too bad of a price. Can't wait to get this show on the road because I've been holding back on so much and releasing it with the app (which will be huge as is) will be so much more awesome
Can't wait to get to work with the team.
- Kifno
Click to expand...
Click to collapse
Are you going to continue to use my code (and others' code) in your app? I'm only asking because just yesterday, I asked pretty much the same question you just asked today-- we're working on essentially the same project, however, I developed all of my code from scratch. If my battery tweak is going to be used commercially, I'd like to have some say in it-- and I'm pretty much in the same boat you are from a java development perspective. It could be a major coincidence, but it just made the same request in the board and it got me wondering what was up.
collin_ph said:
Are you going to continue to use my code (and others' code) in your app? I'm only asking because just yesterday, I asked pretty much the same question you just asked today-- we're working on essentially the same project, however, I developed all of my code from scratch. If my battery tweak is going to be used commercially, I'd like to have some say in it-- and I'm pretty much in the same boat you are from a java development perspective. It could be a major coincidence, but it just made the same request in the board and it got me wondering what was up.
Click to expand...
Click to collapse
The only code I used from other's was your code that determined the power source ( i have another 2 other methods of finding the power source if you don't want me to use your code). I developed all of my tweaks from scratch too as of i think v1.2 when I kicked out all other's tweaks that I just copied, pasted, and credited them. I wanted this to be my own work (besides the fact that i used your power source detecting code). But if you want you and I could team up on the app if you'd like. I used your power source code to make a setcpu replacement. Only thing is, is that I never studied user interfaces in bash scripting so i don't know how to give the user a choice as to what value they'd like certain profiles to be. I see you know how to do that in your script. I was going to look at how you did it and just remix it for my script but i'm going to come up with my own menu from scratch but this menu will be the app's menu and not a bash script menu and it won't be like yours, this is all kifno . But yeah other than your power source detecting code, which is pretty much the simplest way to find power source I just couldn't see it in root explorer when I didn't have access to a computer with adb shell for a while:
Code:
power=` cat /sys/class/power_source/battery/charging_source `
this is all kifno's work that i spent hours testing the new values and of the tweaks i came up with.
EDIT: also i've been talking about making this into an app for a long time so yeah it is just a coincidence. I just decided that I wouldn't be able to do it alone because I don't have the knowledge to do so alone....right now
EDIT 2: Also if you don't want me to use your power source detecting code I have another simple method of doing so, it just doesn't show usb charging. This is what I will use if you don't want me using your code that you use.
Code:
power_source=` cat /sys/class/power_supply/battery/status `
Then I will just revamp my tweak so that is is optimial for charging and not charging rather than optimal tweaks for usb charging, ac charging, and battery power. So no biggie if you don't want me to use your code because I had many other ways of determing it as well. also if you'd like to team up with me and my team of people who are going to help make my script an app i'd be glad to join forces to make one AWESOME app that will potentially be a MUST HAVE for the heroc. collin_ph batt tweak + kifno tweaks = YOUR HERO HAS JUST GAINED SUPER POWERS!!!!!
kifno said:
The only code I used from other's was your code that determined the power source ( i have another 2 other methods of finding the power source if you don't want me to use your code).
But yeah other than your power source detecting code, which is pretty much the simplest way to find power source I just couldn't see it in root explorer when I didn't have access to a computer with adb shell for a while:
Code:
power=` cat /sys/class/power_source/battery/charging_source `
this is all kifno's work that i spent hours testing the new values and of the tweaks i came up with.
Click to expand...
Click to collapse
You're... you're really serious? You're completely ignoring the fact that you so sloppily copied his code that you ended up leaving his name in the source?
You also copied verbatim the files from [MOD]Custom DNS Servers (etc/ppp/ip-down and etc/ppp/ip-up).
You even copied the etc/init.d/20userinit file from the collin_ph zip. The one that has NOTHING to do with the code you're using. The one that's an OUTDATED copy of the one that already comes with CyanogenMod. Did you realize that by overwriting the one in CM7 with yours, you have effectively REMOVED a feature from CyanogenMod? Between version 6 and 7, this file was updated to support user init scripts both in /sd-ext AND /data. But you wouldn't have included this file if you had ANY idea what it was really doing.
I'm still trying to figure out why you even copied it. There isn't a single thing in your script or collin_ph's script that depends on using it. But it's an obvious indication that you copied more than you would like to admit. And now you say you want to make this into a for-profit app? That's just plain insulting to the nature of XDA.
jasonmaloney said:
You're... you're really serious? You're completely ignoring the fact that you so sloppily copied his code that you ended up leaving his name in the source?
KIFNO: I wasn't trying to hide the fact that I did use his code. What's to hide? I have nothing to lie about.
You also copied verbatim the files from [MOD]Custom DNS Servers (etc/ppp/ip-down and etc/ppp/ip-up).
KIFNO: Those actually don't work lol. I just left them there from when I was using those in my personal v1.5 test builds. Would you like me to show you dated screenshots of all the test builds I have? That doesn't work. But I know another simple method to use custom dns servers on the heroc that will be in the app. So this is again, nothing to hide and actually if you look at the tweak I added my way of using the dns server in the 98kiftweaks file
You even copied the etc/init.d/20userinit file from the collin_ph zip. The one that has NOTHING to do with the code you're using. The one that's an OUTDATED copy of the one that already comes with CyanogenMod. Did you realize that by overwriting the one in CM7 with yours, you have effectively REMOVED a feature from CyanogenMod? Between version 6 and 7, this file was updated to support user init scripts both in /sd-ext AND /data. But you wouldn't have included this file if you had ANY idea what it was really doing.
KIFNO: I do know what I'm doing JM. You just don't THINK I know what I'm doing. And to be honest you do know somethings I don't know at times and I commend you on catching me on my mistakes at times I don't catch them before you do. But "hiding" evidence that I used other's work isn't something I need to be caught on because I tell people when I'm using another's work. So what's to hide when I'm being honest. And again v1.5 stable wasn't cleanly put together. And like I said nothing to hide I said I used some of collin_ph's stuff like a 100x in the kifno script thread if you were reading my post when I was releasing those TERRIBLE versions of v1.3-v1.5 test. So yeah nothing to hide and I know that already JM. Like I said v1.5 stable was sloppily thrown together and I didn't clean it up because I got so excited about releasing my kifCPU which I finally got to work. And that 20userinit file is something that again I knew didn't work/was useless for my script.
I'm still trying to figure out why you even copied it. There isn't a single thing in your script or collin_ph's script that depends on using it. But it's an obvious indication that you copied more than you would like to admit. And now you say you want to make this into a for-profit app? That's just plain insulting to the nature of XDA.
KIFNO: Jason, jason, jason. When I copied it, I never meant to use it When I opened collin_ph's script merged my v1.5 test folders with his folders and deleted what all I didn't need from his script's zip. Or at least I thougth I did because I left the 20userinit file in there. Also I have nothing to hide, in fact I'm typing up a documentation of what all my tweaks do right now! And also when describing something I used that I got from another person (collin_ph's power source bash code line which I posted above which I gave an example of one of my alternatives) I am crediting them and explaining what it does in their script and why I am using it for my script. And okay since using another's power source code is insulting since I want to make this a freeware/for-profit app, I just will go about doing all the things I needed from others (collin_ph's power source) my own way with the many backup methods of getting it done by getting rid of EVERY thing i've bored from other's and using my alternative methods of doing so for a certain tweak I have's purpose. Oh and jason, I have a question, kind of off subject but I've been urging to know, where did you learn java? I know where you learned about android (many documentations of the operating system because I notice you know a lot about what file does what in the system and how files connect to others).
Click to expand...
Click to collapse
Red the bold "kifno" text that is in red inside the quote.
Oh and the kifno method only way of doing things aka v1.6 will be released tomorrow along with the documentation that explains in my opinion/to my knowledge of what my tweaks are doing. And every other version I have that is online (because they contain other's way of doing things that i used for my tweaks purpose) will be deleted from the internet. I dont' want to insult xda. I'm just trying to help our heros be better
But back on topic though I have 1 person that has offered to help me in the process of making this an app. If any other's want to help me that'd be awesome.
And also if you do offer to help me i have a lot of files to send you that has everything i've been holding back from the script that i wanted to wait to release in the app version (so that everyone can really see true awesome-ness/why i love our hero )
and here we go again same **** different day
kifno said:
Red the bold "kifno" text that is in red inside the quote.
Click to expand...
Click to collapse
You just keep changing your story over and over again. You didn't add the line to credit collin_ph until after I pointed out his name in the script. And earlier in this thread, you said all you copied from him was one line of text, but now you say you merged the two together? You're insulting our intelligence.
And then you say the DNS stuff doesn't work and was left in? Just because your copying-and-pasting didn't work doesn't mean you didn't copy it.
Closing thread until I get word from Senior.
{
"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?
{
"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"
}
RootMyTV is a user-friendly exploit for rooting/jailbreaking LG webOS smart TVs.
Website: RootMy.TV
GitHub: https://github.com/RootMyTV/RootMyTV.github.io
For further details, and a full writeup, please check out the GitHub repo.
Spoiler: Original pre-release post
TL;DR; If you want root on any* current WebOS LG TV, do not install updates for the time being, and wait patiently. If you're a developer or researcher, read the latest update below.
*The exploit requires "ThinQ" support, which seems to only be available on TVs running WebOS 4.0+. I will update this when we know more about which versions support it.
RootMy.TV is an 0-click (kinda) web-to-root exploit for WebOS.
Website (placeholder): RootMy.TV
GitHub (placeholder): github.com/DavidBuchanan314/RootMyTV
After this bug in Download Manager was published (which, on its own, allows rooting the WebOS emulator), I was motivated to find new bugs which can be combined with it, to get root on actual TVs.
Given the relatively severe impact of this exploit chain, its publication will have to wait at least until LG makes official patches available for the Download Manager bug. After that, I will be publishing the exploit, along with a full writeup.
During my research, I received invaluable advice and information from members of the openlgtv Discord server - I definitely couldn't have done this without them. Please join us, if you would like to assist with testing the exploit etc. in the hopefully-near future: https://discord.gg/9sqAgHVRhP
Update 2021/02/15:
LG claims to have fixed the Download Manager bug, but they haven't really. To motivate LG to actually patch the bug, I will be disclosing my exploit chain to them under a 30-day public disclosure deadline - after which, I will be publishing the exploit here. Assuming I send my disclosure to LG email tonight, that sets the RootMyTV "release date" at 2021/03/19.
Update 2021/03/18:
The release date is now 2021/03/21 - I have a few things I need to finish up...
Update 2021/03/23:
Sorry for the delays...
I am attaching a bare-bones vulnerability report and PoC for the exploit, which is enough to get you root. This "pre-release" is intended for developers and researchers. If you're not a developer or researcher, please be wait for the "full" release, which will hopefully arrive in the coming weeks. The final release will be more user friendly, and include a "Homebrew Channel". If you would like to contribute to development of the Homebrew ecosystem, please visit us on Discord.
Some notes/disclaimers about the exploit: (READ FIRST!!!)
- This will void your warranty, don't blame me if anything goes wrong etc. etc.
- Amazon's "google play store" link, described in the writeup, is currently broken. As a workaround, you can search for "google search" on Amazon, Click the top result, Click "developer info", then click the link to Google's privacy policy. From there, you can click the menu icon in the top-right and continue with the rest of the instructions.
- Something I forgot to mention in the report - you must update the value of the "HOST_PREFIX" variable in index.html, to point to your local webserver.
- If you were previously using Developer Mode, then overwriting `start-devmode.sh` will have broken devmode features like `ares-install`, and the jailed sshd. You can fix this by putting the old `start-devmode.sh` back again, with some edits.
- For some TVs that don't have the ThinQ login page, you can access an equivalent page via "Account Management" in the settings. This doesn't work on my TV (the amazon link opens in the web browser), but apparently it works on some models/versions.
- The current version of the exploit will give you a root telnet server, accessible on the default port (23), without authentication.
Hi, my device OLED65CX6LA wait your Hack ..
This is exciting! I knew in my gut that I should avoid the update I saw pop up a few days ago. Can't wait to see what this all entails. Please give us an update when you can! :]
great job, thanks for this, can't wait for the final release
Thanks again for the efforts! I can confirm that worked like charm, I have tested on LGC9 05.00.03, very smooth, haven't seen any errors.
For me worked
OLED65CX6LA in italy
soft ver. 03.21.16
thanks
Connected to lgwebostv.fritz.box.
Escape character is '^]'.
webOS TV 5.2.0 LGwebOSTV
/ # ls
bin etc lib mnt proc share usr
boot home linuxrc opt run sys var
dev lg media overlay sbin tmp www
/ #
is possible to use oscam now?
lg 55uk6470plc
software version 5.30.10
WebOS version 4.3.0-9703
Confirmed working!
Is it possible to install Web OS FW of a LG Commercial Signage Display on to a matching Consumer Retail model? How?
I am the same model as your TV. However, as you mentioned, I searched for google search on Amazon and went in, and after that, I proceeded the same, but rooting did not work. Are there any other points where I can rooting?
Using com.webos.app.iot-thirdparty-login in webOS 4.9.1-53409 for this exploit doesn't seem to work anymore, because the app now seems to open all links in the web browser app instead of its own instance. No matter which link I tested, they all open the external web browser.
Update:
The underlying issue still exists though and I managed to use a slightly different method but the same privilege escalation method to get in anyways.
Code:
Connected to XXXXXXXXXX.
Escape character is '^]'.
webOS TV 4.9.1 LGwebOSTV
/ # uname -a
Linux LGwebOSTV 4.4.84-169.gld4tv.4 #1 SMP PREEMPT Fri Mar 12 02:53:12 EST 2021 aarch64 GNU/Linux
/ # whoami
root
LLP42 said:
Using com.webos.app.iot-thirdparty-login in webOS 4.9.1-53409 for this exploit doesn't seem to work anymore, because the app now seems to open all links in the web browser app instead of its own instance. No matter which link I tested, they all open the external web browser.
Update:
The underlying issue still exists though and I managed to use a slightly different method but the same privilege escalation method to get in anyways.
Click to expand...
Click to collapse
Perhaps you might share the approach you found so others don't struggle helplessly?
I had the same problem. After getting to the Amazon log in page, all links mentioned above opened in the web browser instead of within the ThinQ app. Eventually I tried entering non existent credentials into the Amazon login form, then after being prompted to enter a captcha, I again entered invalid credentials a second time. When shown the login form a third time I clicked the bottom link (can't remember what it was - maybe privacy or forgot password or similar) and this time the link opened within the ThinkQ app rather than an external browser, and I could then follow the rest of the exploit successfully.
Does rooting WebOS remove the DRM? Could someone check if Netflix is still working?
And if the DRM will be removed, is it possible to restore it by resetting it by it's factory defaults or a software update?
@retr0id awesome work! Have been waiting on this for a long time
roykaandorp said:
Does rooting WebOS remove the DRM? Could someone check if Netflix is still working?
And if the DRM will be removed, is it possible to restore it by resetting it by it's factory defaults or a software update?
@retr0id awesome work! Have been waiting on this for a long time
Click to expand...
Click to collapse
Currently root exploit in the first post only exposes root unjailed telnet session and disables some telemetry. It does not affect any existing apps, unless content providers add explicit root detection. (which in of itself would require jail escape exploit on their part) Netflix seems to work fine so far on 2018-era webOS 3.8 LG TV.
spartakles said:
Perhaps you might share the approach you found so others don't struggle helplessly?
Click to expand...
Click to collapse
If there really is a "0-click" exploit as promised, these steps become unnecessary.
Until then, anyone who knows the ropes should have no problem finding the way I mentioned. At least when you take a closer look at the source code of com.webos.app.iot-thirdparty-login. And if you have problems with this, you should probably leave this method alone anyway.
That's why I won't post any more details about it - at least for now.
LLP42 said:
If there really is a "0-click" exploit as promised, these steps become unnecessary.
Until then, anyone who knows the ropes should have no problem finding the way I mentioned. At least when you take a closer look at the source code of com.webos.app.iot-thirdparty-login. And if you have problems with this, you should probably leave this method alone anyway.
That's why I won't post any more details about it - at least for now.
Click to expand...
Click to collapse
What gibberish.
I provided a way forward to others in my response. I followed it and it worked, so I shared it.
You simply turned up with no useful information, just to say "hey your instructions no longer work. I found a way round it. Not going to share". It would seem you're posting on entirely the wrong forum.
spartakles said:
You simply turned up with no useful information, just to say "hey your instructions no longer work. I found a way round it. Not going to share"
Click to expand...
Click to collapse
That's not true at all. The info I shared is that the vulnerability is still present in the latest firmware v05.00.30 of the 2019 models and that it's still possible to use the exploit.
I also said that I do not share the details "for now", depending on the "0-click" exploit status.
spartakles said:
It would seem you're posting on entirely the wrong forum.
Click to expand...
Click to collapse
The official subtitle of this forum is:
Technical discussion of WebOS development and hacking. No noobs please.
Click to expand...
Click to collapse
So if anyone is wrong here, it's you.
This forum is not for users who need step-by-step instructions.
If someone can use this to make a custom firmware that adds back in the 120hz black frame insertion to the LG C9 (and maybe even older models) that would be amazing. LG removed the feature last minute despite it showing up in C9 reviews samples, but it did make it into the CX as OLED motion low and mid. I remember in some old interviews hearing that the feature is all algorithm based and could be added into older OLED TVs but they never did.
has anyone tested a LG 65SK8500LLA? Dont want to brick my one
MaxSnacks18 said:
If someone can use this to make a custom firmware that adds back in the 120hz black frame insertion to the LG C9 (and maybe even older models) that would be amazing. LG removed the feature last minute despite it showing up in C9 reviews samples, but it did make it into the CX as OLED motion low and mid. I remember in some old interviews hearing that the feature is all algorithm based and could be added into older OLED TVs but they never did.
Click to expand...
Click to collapse
If I am not wrong the OS does verification , so trying to modify something will trigger it to not boot....
As of now.
MaxSnacks18 said:
If someone can use this to make a custom firmware that adds back in the 120hz black frame insertion to the LG C9 (and maybe even older models) that would be amazing. LG removed the feature last minute despite it showing up in C9 reviews samples, but it did make it into the CX as OLED motion low and mid. I remember in some old interviews hearing that the feature is all algorithm based and could be added into older OLED TVs but they never did.
Click to expand...
Click to collapse
You're in luck. Just this week a user at AVSForum reported that you could enable Motion Pro on the C9/E9 with a simple command on the tv. The only disadvantage was that you need to execute this command with root privileges. Now that is where this thread comes in.
I've managed to get root access to my C9 and have executed the command and it works! Motion Pro low, medium and high is available and works at 120Hz.
This is the command that you need to execute:
Code:
luna-send -n 1 -f "luna://com.webos.service.config/setConfigs" '{ "configs": { "tv.model.motionProMode": "OLED Motion Pro" } }'