Database Info

[APP]Log This - End-User Friendly Debug Logs!

Log This
by Mgamerz Productions
<50 downloads, 1 ratings (5 avg)
Free
{
"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"
}
Download Log This from Android Market
^^^This info does not update on it's own^^^
I have created a very simple but useful application called Log This. In short, it lets end-users get logcat logs (perhaps the app didn't crash - but it isn't working right.) without all the ADB fuss that surrounds logcat. It is meant to be simple for end users and powerful for developers.
It includes pastebin support that makes it easy to paste to your favorite android development forum, not mentioning any names that start with X.
Android Market Description said:
Log This is an application that can read logs given a provided tag and log level - and send them to developers. This saves them the hassle of having to use logcat on their computer with ADB.
As a developer, requesting the READ_LOGS permission is risky - it scares away a lot of users. Log This uses this permission, but is meant to be used by developers to request their end users to send in debug logs - one app to log em' all.
As an end user, you can install the app and help out your developers when they need debugging on specific phone models - provided they have logging enabled (perhaps via a logging mode).
It also can fetch kernel (panic) logs, as long as you supply the location of the log (a kernel developer can tell you if it does or not - not all kernels do)
This application is NOT optimized for tablets, but it should work on them. I don't have one to test with.
Permissions Explained:
READ_LOGS: Application has to be able to read the logs - the only data read is displayed in the email
INTERNET/CHECK_NETWORK_STATE: Advertising
WRITE_EXTERNAL_STORAGE: Used for building the log file. I leave the latest log as log.txt on the root of your media area (internal SD) so that you can always check it yourself.
Click to expand...
Click to collapse
I know there is an app called Log Collector already but I want to create some additional features.
Some new features that will be coming soon:
Three Click Logs - click on a file, accept the preview, click send. (file association)
I hope someday this app will be really useful.
Thoughts?

More otpions is always good. Thanks.

Balancing school, work, research (GibberTalk) and this app will be one great task

My friend and I were just discussing making an app like this. You beat us to the punch and you did a great job at doing that. Will it be okay to include your app in custom ROMs?

Of course! Just make sure it is linked to android market (so it will update itself). And as long as the rom isn't sold for money (I hear some roms are?). Happy cooking!

Awesome thanks a bunch!

Thanks! This should help a novice like myself.

just
want to say thanks

as6 said:
want to say thanks
Click to expand...
Click to collapse
Yes, but did you hit the "THANKS" button?

Hi,
I'm quite new to Android.
It definitely will be helpful to me when I want to help a developer.
I have a question.
Does this app run itself in the background or do I have to enable it?

You must run this app yourself. A logging service would seem kind of creepy Logcat is ~10000 long (thats as far as my eclipse one goes anyway) so you should have a good 10 minutes, unless your device just booted, then DLNA parser (at least on my atrix, perhaps its just the media scanner) will flood your logcat for like 10 minutes.
The way this app is intended to work (end users wise, not as devs)
Devs either have logging/debug mode or have logging on by default
end-user experiences odd behavior/crash (crashes on 2.2 can be sent through 'reporting' to the market)
End user asks dev why this doesn't work
Dev either A) gives user file that auto collects needed info (they just have to send), and they open it after they start the app/it doesn't work properly or B) dev gives them the needed info (not much) to fill out the forms and send it in.
PROFIT!

ja
MobileWon said:
Yes, but did you hit the "THANKS" button?
Click to expand...
Click to collapse
yes i did already hit the button

Forgive me for not fully understanding the logging process. I'm on Serendipity VII. Will your program 'turn on' logging, or is there something I still have to do to enable it?

Android has a user-hidden system called LogCat that is always running. You can oly see it with the logcat command built into the system (also accessible through ADB, its very VERY useful for developers for debugging/seeing what is going on). This just runs the 'logcat command' (prints out text) and filters it out. This app just captures that log command (with the filters)

Mgamerz said:
Android has a user-hidden system called LogCat that is always running. You can oly see it with the logcat command built into the system (also accessible through ADB, its very VERY useful for developers for debugging/seeing what is going on). This just runs the 'logcat command' (prints out text) and filters it out. This app just captures that log command (with the filters)
Click to expand...
Click to collapse
I see. I thought I'd read that you had to enable it in recovery or something - thank you for the education!

Hello,
I'm planning to communicate a procedure to use this app to the users of my own app who encounter problems.
There are however some questions / remarks I already have :
"Log an application tag" field : is this the TAG constant we pass to the android.util.Log.* calls ? In this case, I personally use several different tags in the same app so this would not be enough for all cases.
internationalization : the app is in english only, is it possible to help translating ? I can do it for french...
in the screenshots at the market, there is a screen that I don't have on my device : ss-480-1-1 (the one with the nice looking arrows "keep it private" / "make it public"), is it an old screen ?
From my first tests, it looks like there is not a lot of logs extracted, but I didn't tested it extensively. I'll will test it more and give you more feedback, thanks for this possibly great alternative to Log Collector !

I am soon going to add multiple tags, but they will all have to use the same level. I've been incredibly busy with my schoolwork that just started (and it sucks too!)
The app right now is english only. I can work on making it more translatable, but I throw a mix of R.string.xx with string literals.
The 'keep it private' screen isn't there cause it was a GIMPED photo. To promote your app you should add text. That would never fit on a small screen. Still trying to make screen scaling better than just scroll panes. It'll get there though.
How long before your app is released?
Edit: Or how long would you need? I have some ideas that could be wrapped around this:
Should all the tags be inline?
Should they be spread across .txt files? (Although that would be a bit more difficult as iirc the gmail app only supports up to 5)
I'd list more but my class is about to start

Mgamerz said:
I am soon going to add multiple tags, but they will all have to use the same level. I've been incredibly busy with my schoolwork that just started (and it sucks too!)
Click to expand...
Click to collapse
Don't worry, just do your schoolwork, I am not in need, just thinking about the next features I could implement in my app(s)
The app right now is english only. I can work on making it more translatable, but I throw a mix of R.string.xx with string literals.
Click to expand...
Click to collapse
Ok, no pb. If you need a translator in the future you know where to find me
The 'keep it private' screen isn't there cause it was a GIMPED photo. To promote your app you should add text. That would never fit on a small screen. Still trying to make screen scaling better than just scroll panes. It'll get there though.
Click to expand...
Click to collapse
Anyway, I was just curious. Using images to give important indications to user is probably not a very accessible thing...
How long before your app is released?
Click to expand...
Click to collapse
I've just released one already, soon in the app forum of xda, if I manage to get some time to do it right...
As I said, I'm not in need of any blocking feature... I think using "Log this" doesn't need to be programmatically integrated in the application, and that's a good point for me. We just need to tell users to install it and what parameters to use, on a per case basis.
Edit: Or how long would you need? I have some ideas that could be wrapped around this:
Should all the tags be inline?
Should they be spread across .txt files? (Although that would be a bit more difficult as iirc the gmail app only supports up to 5)
I'd list more but my class is about to start
Click to expand...
Click to collapse
I haven't thought about it yet, but a txt file looks too much complicated for users... Maybe it's best to uncheck the corresponding checkbox if there are multiple tags, or to use some generic patterns like "my.package.*"...
Also I was wondering if a simple URI like logthis://tag=TAG1&tag=TAG2&level=debug&... could be easily parsed as an Intent by some BroadcastReceiver...? This would help the developer give the user the right parameters via e-mail or other...
Again, this would require more thinking before considering those as good ideas and implement them... Maybe this will give you a starting point...

Nice tool, thanks a lot

@Mgamerz : Here is my app "SwitchDataSwitch" at xda : http://forum.xda-developers.com/showthread.php?t=1287025
I will soon include a chapter on how to use Log This in case of problem on the website : http://bitbucket.org/nicobo/switchdataswitch
Fyi, the next version might include a direct link to use Log This.
---------- Post added at 12:50 PM ---------- Previous post was at 12:49 PM ----------
By the way, this is a first test, I think I will generalize the use of both Log This and Log Collector in my future apps, thanks.

[APP][2.1+] Gidder - Git server for Android

{
"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?

@Kingo: Time to come clean

I call for the root-kit developers of Kingo to come out of the woodworks and come clean. I'm tired of reading about all the various security issues people bring up with using their rootkits.
RevolutionBolt said:
DOWNLOAD this software here!! 100% no virus detected.
Click to expand...
Click to collapse
Then, what is this? (Perhaps you think Trojans are ok?)
{
"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"
}
False positive or not, this should be worrisome to everybody, since it was on the most recent binary posted. If you do the same thing for their older binaries, you will find loads more issues. In addition I have still not seen anyone bother to do a thorough analysis of their windows execs or house-calls.
---
To Kingo Developers:
Given the highly dubious background to Kingo and the little information you provide to developers regarding your rooting app, I think it's time for you to stand up and come clean. Remember that even linking to your website was banned from XDA until recently. Nobody is asking you to give up the vulnerability you use to gain root or your other rooting secret.
But most of us would really like to know:
Why is your windows executable so damn large? (~24MB!)
(What exactly is in it that require it to be so, when most others level out ~5MB.)
What exact files are installed on the windows machine used?
What exact files are installed on the phone being rooted?
Why don't you just provide a flashable kernel or binary like everyone else does?
Who are you and why should anyone trust you?
(Especially when you seem to be afraid to come forward.)
What exact information is being sent to your servers?
Does rooting require an internet connection? (If so why?)
What is your business model, how do you make a living?
(Someone must be paying your website hosting costs etc.)
Until there is some more transparency in this, I will not recommend anyone to use your rooting method, even if I think it look very good.

A) This forum isn't an appropriate place to call someone out. To call for an audit or ask a question sure, but not to call them out to come clean
B) It contains exploits, of course it is going to trigger AV software, all exploits should. The packer used also likely causes AV detections. Su binary alone is enough to cause it on some devices
B) I've performed a fairly extensive investigation of Kingo. It is suspicious, it has the ability to fetch binaries remotely, and execute them locally. They were collecting serial/imei from devices, but they claim to have stopped this practice after I confronted them.
1 Why is your windows executable so damn large? (~24MB!)
(What exactly is in it that require it to be so, when most others level out ~5MB.)
2 What exact files are installed on the windows machine used?
3 What exact files are installed on the phone being rooted?
4 Why don't you just provide a flashable kernel or binary like everyone else does?
5 Who are you and why should anyone trust you?
(Especially when you seem to be afraid to come forward.)
6 What exact information is being sent to your servers?
7 Does rooting require an internet connection? (If so why?)
8 What is your business model, how do you make a living?
(Someone must be paying your website hosting costs etc.)
Click to expand...
Click to collapse
1- 24mb is relatively small now a days, simple games on mobile devices are much larger.
2- dunno
3- Varies per device and firmware
4- They are targeting the less technical user, this approach makes sense in that case (not that I like this approach)
5- Who are you and why should anyone trust you? or me for that matter?
6- Detailed information about the device, previously included IEMI, promised to stop havent verified
7- Remote fetching of drivers, and exploits.
8- Good question
E:V:A said:
Until there is some more transparency in this, I will not recommend anyone to use your rooting method, even if I think it look very good.
Click to expand...
Click to collapse
I recommend against rooting of devices period, especially for those concerned about security. If one feels they must have root, using an exploit from a well known and trusted source is best. No one should be using these exploit packs.

jcase said:
A) This forum isn't an appropriate place to call someone out. To call for an audit or ask a question sure, but not to call them out to come clean
Click to expand...
Click to collapse
Actually, why not? I guess it's just a matter of semantics and when the same people are making obvious false claims and avoid all the relevant questions, I really do think its time to use different words, but with the same meaning.
I recommend against rooting of devices period, especially for those concerned about security. If one feels they must have root, using an exploit from a well known and trusted source is best. No one should be using these exploit packs.
Click to expand...
Click to collapse
I guess that is the whole point. Many people are rooted for that exact reason, they no longer trust their service providers, their manufacturers, all for very good reasons. A cooked ROM by a recognized developer just seem way more safe than anything provided by Samsung, HTC, Verizon etc etc.

E:V:A said:
Actually, why not? I guess it's just a matter of semantics and when the same people are making obvious false claims and avoid all the relevant questions, I really do think its time to use different words, but with the same meaning.
Click to expand...
Click to collapse
Because it isn't the intended purpose of this forum, organizing an audit would serve the purpose far better.
E:V:A said:
I guess that is the whole point. Many people are rooted for that exact reason, they no longer trust their service providers, their manufacturers, all for very good reasons. A cooked ROM by a recognized developer just seem way more safe than anything provided by Samsung, HTC, Verizon etc etc.
Click to expand...
Click to collapse
Historically, "cooked" roms are far less secure than the firmware from the ODMs. Even ones that seem to focus on security have a history of using "public" private keys, or superuser control APKs with known vulnerabilities. They also do not get the security bulletins that AMSS members or OHA partners get, which leaves them months behind on critical patches.

@jcase: I think we're pretty much on the same page, but our vague and subjective definition of "secure" is probably what's bothering us. When I talk about security, I'm more concerned with being spied upon by external entities. This would indeed happen with the help and leakage of information due to nontransparent proprietary Apps and binaries. As for your sense of security, it's more about being hacked. Yes, then perhaps unrooted STOCK ROMs are more secure. But since the end user never have access to these security bulletins, which "security researchers" do have, they/we will never know about any vulnerabilities until it's too late. Determined hackers will always have an advantage as long as stock SW remains secret and unified across devices.
As for this thread. Ok, I agree, let's call for an "audit" instead...

Seriously, 3 no name anti-virus programs detect a virus and you think thats valid? Anti virus programs are so inefficient at finding anything, they should not even be used in most cases to argue with anything.
As for rooting, nobody should use a rooting method posted by somebody, at least no tools offered by by somebody online. There are official methods for that.
People who are new to android at best should not root their phones.
Also, what has been said about cooked roms is true. Sadly, its either live with an outdated rom or use a risky custom rom.
That is why you dont use an old smartphone to do business.

shadowcore said:
Seriously, 3 no name anti-virus programs detect a virus and you think thats valid? Anti virus programs are so inefficient at finding anything, they should not even be used in most cases to argue with anything.
As for rooting, nobody should use a rooting method posted by somebody, at least no tools offered by by somebody online. There are official methods for that.
People who are new to android at best should not root their phones.
Also, what has been said about cooked roms is true. Sadly, its either live with an outdated rom or use a risky custom rom.
That is why you dont use an old smartphone to do business.
Click to expand...
Click to collapse
Too bad it is absolutely valid, for a number of reasons.

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

IR Remote Gear 2
Maintained by cracksmurf​
Introduction
One feature that sets the Gear 2 apart from most other smart watches is the inclusion of the IR Blaster which allows us to control a variety of devices right from our wrists. Thanks to the work by biktor_gj in Porting Android to Gear 2 we have gained a lot of new functionality on this older device. However, due to the lack of Android Wear devices that possess an IR Blaster, bitstra started work on modifying the Gear 2 IR Remote. Due to circumstances, bitstra was eventually unable to continue development of this app. On 3/3/2016, development was officially handed over to me, cracksmurf. While I don't have too much experience in coding, I have managed to make some headway in expanding the app and including new devices. Hopefully this will be of use to other Gear 2 users.
Click to expand...
Click to collapse
Code:
*** Disclamer
-- This is project is a continuation of the app mod by bitstra. Original code is not my own and I do not take credit for it. There should be no negative impacts on your device. However, use of this app signifies acceptance of responsibility over any issues that may arise due to it's installation.
Images
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Installation Instructions
on linux or mac:
./adb install -r IRremote_Gear2_1.6.apk
on Windows:
adb install -r IRremote_Gear2_1.6.apk
Click to expand...
Click to collapse
Download
DL link for latest version:
IRremote_Gear2_2.0.apk
Click to expand...
Click to collapse
Changelog
Current changelog: -- 03/09/2016 IR Remote v2.0
[note] -- This is my first release.
[new] -- Added devices:
Audio-Denon-AVC2000
Audio-Samsung-HT-Z320
Camera-Canon-600d
Camera-Nikon-D5100
Console-Microsoft-Xbox One
TV-Konka-KL32PH92U
TV-TCL-LED32D2730M
TV-Hisense-Generic
TV-Free-Freebox Crystal​[changed] -- Completed code allowing for more categories that were already partially setup within the app. (plan to expand this for more categories in future releases).
[fixed] -- Currently no new fixes.
Older changelogs:
Current changelog: -- 07/17/2015 IR Remote v1.6
[note] -- This is the bitstra's latest release. All new development is starting from this release.
[new] -- Currently no new features.
[changed] -- Currently no new changes.
[fixed] -- Currently no new fixes.
Click to expand...
Click to collapse
FAQ
Q: How can I request a device be added to the app?
A: Please place all requests for new devices in the "Feature Request" tab above using the following format.
[Device Type] i.e. TV,Cable(or Set Top Box), Blue Ray...
[Manufacturer] i.e. JVC, Panasonic...
[Model Name] i.e. FTS 2505
Q: I'm receiving a [INSTALL_FAILED_UPDATE_INCOMPATIBLE] error when installing.
A: You are most likely updating from a system installed or incompatible version. Follow the below steps to uninstall and reinstall.
Removing Previous version
//If bundled from Biktor's Wear release as system app//
Code:
adb shell
su
mount -o rw,remount /system
rm -rf /system/app/org.esolutions.irremote-1
rm -rf /data/data/org.esolutions.irremote
mount -o ro,remount /system
reboot
//If manually installed//
Code:
adb shell
su
rm -rf /data/app/org.esolutions.irremote-1
rm -rf /data/data/org.esolutions.irremote
reboot
Installing new version
Code:
adb install -r IRremote_Gear2_2.0.apk
Click to expand...
Click to collapse
Thanks To/Credits
bitstra - For initial work on bringing us a fully functional IR Remote that runs on the Gear 2 within Android Wear. Also, for allowing me to continue this project to expand functionality for Gear 2 users.
biktor_gj - For porting Android Wear to the Gear 2
Click to expand...
Click to collapse
XDA:DevDB Information
IR Remote Gear 2, Device Specific App for the Samsung Gear 2
Contributors
cracksmurf
Version Information
Status: Testing
Created 2016-03-03
Last Updated 2016-03-03

Reserved

Well got the project page all finished. Welcome everyone. I hope to be able to meet your device needs on the Gear 2 IR Remote. Any device requests can go in the "Feature Request" tab at the top of the page and I will get to them as quickly as I can. For now I am working on getting the initial release out which includes extra device type categories and the previous requests from bitstra's thread.

Great to see you picked up this project. I will try and install on the new BETA version...

ratmkicksass said:
Great to see you picked up this project. I will try and install on the new BETA version...
Click to expand...
Click to collapse
The download available is still the version released by bitstra. I am currently working on getting my first release put together, and will hopefully have it out by this weekend. The current release was working just fine for me on the September 24th, 2015: Android Wear Lollipop - 5.1.1 (build LCA43) release by biktor_gj. However, last week I installed the test version of 6.0.1 and the app shot out an error saying that my device didn't have an IR Blaster. Most likely due to the fact that biktor hasn't finished getting all his code into that release (which is why you can't find it on the main topic post). Once he gets that out I'll be able to properly test on the new version of the OS. Hopefully there won't be any major changes needed on our end.
biktor_gj said:
IR: Haven't even pushed it yet
Click to expand...
Click to collapse

Awesome to see he let you do this, if theres anything i can do to help let me know. Im no coder but maybe some bug testing?

Development was a bit slow this past week due to working between 70-80hrs, but I have managed to get a little groundwork set. I'm definitely going to have to look into being able to add new button types, and I can foresee layout issues depending on how it generates a layout based on certain buttons. Though I will face those hurdles as I get to them. As it stands I should be able to get device functionality in there; even if it doesn't look pretty.
For now I have started working on getting through the list of device requests that were from the old thread. I've imported these into the Feature Requests tab. If you have a device that you would like added then feel free to place a request there and I will prioritize you since I'm not sure if some of the people who made those original requests are still around. If you see a request of yours or another device that you would like added then use the "UpVote" button. This will let me know which devices to prioritize. Please use the listed format for new requests to make things a little easier.
Secondly, I have been expanding my Google Sheets document to keep this all organized. The file has been made public for those who are curious on a specific devices progress. Others can also create new tabs and add a device to the list if they wish. All tabs that I create or devices that I have reviewed will be locked from editing, but feel free to get in there and add a device if you know where to find the hex codes. A couple useful sites are http://www.remotecentral.com/ and https://irdb.globalcache.com though i'm sure there are plenty more databases and forum locations to find codes for your devices.

Ive added the hex codes for the devices i requested into your google sheets. Good luck with everything

Garridon said:
Ive added the hex codes for the devices i requested into your google sheets. Good luck with everything
Click to expand...
Click to collapse
Looks good. Glad to see it was easy to grasp the button mappings in relation to their file name. I'll make sure to get these in on the first release. As I figure things out in subsequent releases I'll try and get custom buttons made up to match common device types like xbox controllers. This will make the resulting control look more fitting in style.
I'm at work till midnight tonight, but should be able to squeeze out a little time to throw your devices into the app and get some testing done. Looking to be a slow night anyways. Also, gotta reflash lollypop since my phone build currently isn't detecting the IR Blaster, unless biktor gets the next test release of marshmallow out that he was hinting at for today.

A little progress. All devices that are listed as "In Progress" in the Feature Requests tab have been completed in the spreadsheet with all applicable codes.
I have also worked out a simple little system that allows me to export the document from Google Sheets into excel and load up a script which converts each cell into it's appropriate .button file. Once that is done it is simply a matter of dragging the files into the assets folder, compile the apk, sign the apk, and do some testing on device. As of right now I have done this with all the devices currently in the spreadsheet.
I'll try and get this compiled and signed today for testing. It will require transferring files do my desktop, remote into that and run all the compile/signing steps there since I can't install python or apk studio at work.

So got it built using a test key (still haven't gotten around to creating my own keystore lol). Downgraded my Gear 2 to LP since the MM build I was using didn't have a working IR Remote. App loads up, tv's that were already in app here at work are functioning. Will test my devices at home that I added as new devices. Few minor errors that I noticed I made and need fixing. But otherwise this is pretty much ready to go as a first release. Maybe tomorrow if we are lucky. Layouts, custom buttons, and custom categories still need to be figured out, but functionality for everything else should be there. Though I will need the people that actually own these devices to test them out once I make the build available.

cracksmurf said:
So got it built using a test key (still haven't gotten around to creating my own keystore lol). Downgraded my Gear 2 to LP since the MM build I was using didn't have a working IR Remote. App loads up, tv's that were already in app here at work are functioning. Will test my devices at home that I added as new devices. Few minor errors that I noticed I made and need fixing. But otherwise this is pretty much ready to go as a first release. Maybe tomorrow if we are lucky. Layouts, custom buttons, and custom categories still need to be figured out, but functionality for everything else should be there. Though I will need the people that actually own these devices to test them out once I make the build available.
Click to expand...
Click to collapse
This is fantastic to hear. I've kept my gear at lollipop due to all the problems I've heard about mm on it. But anyway it's not force closing so that's a great sign! xD how hard is it to make a keystore?
Sent from my HTC One_M8 using Tapatalk

Garridon said:
This is fantastic to hear. I've kept my gear at lollipop due to all the problems I've heard about mm on it. But anyway it's not force closing so that's a great sign! xD how hard is it to make a keystore?
Click to expand...
Click to collapse
Using pySignare it's supposed to be as simple as clicking a button and typing in some info. However, it's failing to work for me for some reason. I'll have to look into the official method of generating a keystore tomorrow since that tool isn't working for me. Worse comes to worse I can release using the test keystore. Not like I really need any security on this app due to it being more of a community project than a release of my own development at this point.

I didn't want to muck up the device requests with a non-standard feature request, plus I'm rather long winded so I thought it more appropriate to leave it here. Perhaps this has already been considered and subsequently dismissed, but wouldn't it be far simpler to create an interface for users to simply add their own devices to the app? Perhaps you could also provide the functionality to export and import device specifications to ease the burden of having to add devices redundantly in the event of data loss and let users share their own configurations? I disassembled the app itself some time ago to manually add in my own devices, but it was a curiosity more than a real effort and I stopped when I wasn't able to reconcile why the values in the app were slightly off from the IR code databases available online and couldn't effectively convert them to match, but I did note that the basic template was fairly universal looking so I would think it would be terribly difficult and the work would certainly pan out to be less than adding each request individually, but my perspective is from that of someone who's been writing code about as long as I've been able to write my name (24 years, wow I feel old!) so bear that in mind. Just a thought, and there may well be few enough requests for individual devices that it isn't worth the trouble to build something like that. Looking forward to seeing how things progress in any case and congratulations on picking it up!

zygh0st said:
I didn't want to muck up the device requests with a non-standard feature request, plus I'm rather long winded so I thought it more appropriate to leave it here. Perhaps this has already been considered and subsequently dismissed, but wouldn't it be far simpler to create an interface for users to simply add their own devices to the app? Perhaps you could also provide the functionality to export and import device specifications to ease the burden of having to add devices redundantly in the event of data loss and let users share their own configurations? I disassembled the app itself some time ago to manually add in my own devices, but it was a curiosity more than a real effort and I stopped when I wasn't able to reconcile why the values in the app were slightly off from the IR code databases available online and couldn't effectively convert them to match, but I did note that the basic template was fairly universal looking so I would think it would be terribly difficult and the work would certainly pan out to be less than adding each request individually, but my perspective is from that of someone who's been writing code about as long as I've been able to write my name (24 years, wow I feel old!) so bear that in mind. Just a thought, and there may well be few enough requests for individual devices that it isn't worth the trouble to build something like that. Looking forward to seeing how things progress in any case and congratulations on picking it up!
Click to expand...
Click to collapse
You make some valid points, and Bitstra was actually working on creating features similar to some of that before he had to abandon the project. While I do have some experience in coding its not very much. While I could probably figure out how to put together features like that it would take me way longer to implement than would be worth while; mainly due to the fact that I would be researching what everything is as I go. Don't get me wrong, I would absolutely love something like this, but due to my lack of experience I'm mostly limited to minor tweaks to the code. Things like expanding menu categories for devices, maybe adding more button types, or some layout changes.
As far as your statements on the IR hex codes being different? The only thing I can think if as to the codes being slightly off would be due to the number of slight variations manufacturers themselves implement into their devices. Say for a Samsung TV you might find 3-4 generic code variations or more. A lot of the time its trial and error to get the right code set for the device you are using. For the devices I've manually added I've had no problem working out the right code set that gives me all the right remotes features.
For the most part I picked up this project since I wanted to get my devices in for myself and figure I'd help others who had been making requests over the past year. I'm trying to create as much explanation as I do it so if others want to easily add devices in on their own they can. I've managed to put together a process where the hardest part is just finding the codes, then drop them in my Google doc, run the excel macro script to automatically export the .button files, and all that is left is to build and sign the apk. Right now we don't have too many people making requests so not that hard to keep up with, but the option is there for them to do the finding of the codes and entering them into the spreadsheet on their own and I'll just throw a quick build up afterward.
Perhaps I can throw a guide together for those who wish to do this entirely on their own. Plus im always welcome to help from those with more coding experience than i who want to implement better features.

I plan on doing a few more changes regarding version number etc to ensure that the first release can simply be installed over previous releases without having to fully wipe the app from your device and then install it. Should be a quick and simple job. Once that's done I think I can get the first release out for you all today. I haven't put 100% of the old requests from bitstra's thread, but want to get my first release out there. I'll keep working on those and any new requests for the next release.
As always feel free to help out by finding the IR Hex codes for your specific device and either linking them to me in the request or inputting your device on the google spreadsheet to speed things up.

Here is my first release of the updated IR Remote port.
https://www.androidfilehost.com/?fid=24438995911975157
Changelog
Current changelog: -- 03/09/2016 IR Remote v2.0
[note] -- This is my first release.
[new] -- Added devices:
Audio-Denon-AVC2000
Audio-Samsung-HT-Z320
Camera-Canon-600d
Camera-Nikon-D5100
Console-Microsoft-Xbox One
TV-Konka-KL32PH92U
TV-TCL-LED32D2730M
TV-Hisense-Generic
TV-Free-Freebox Crystal​[changed] -- Completed code allowing for more categories that were already partially setup within the app. (plan to expand this for more categories in future releases).
[fixed] -- Currently no new fixes.
Click to expand...
Click to collapse
-Note
Due to taking over the project and not having the original keystore that bitsra was using, you will receive an [INSTALL_FAILED_UPDATE_INCOMPATIBLE] error if you attempt to install this app over top of his previous version. You must make sure that you remove the previous version before attempting to adb install my version.
Removing Previous version
//If bundled from Biktor's Wear release as system app//
Code:
adb shell
su
mount -o rw,remount /system
rm -rf /system/app/org.esolutions.irremote-1
rm -rf /data/data/org.esolutions.irremote
mount -o ro,remount /system
reboot
//If manually installed//
Code:
adb shell
su
rm -rf /data/app/org.esolutions.irremote-1
rm -rf /data/data/org.esolutions.irremote
reboot
Installing new version
Code:
adb install -r IRremote_Gear2_2.0.apk
Click to expand...
Click to collapse

cracksmurf said:
You make some valid points, and Bitstra was actually working on creating features similar to some of that before he had to abandon the project. While I do have some experience in coding its not very much. While I could probably figure out how to put together features like that it would take me way longer to implement than would be worth while; mainly due to the fact that I would be researching what everything is as I go. Don't get me wrong, I would absolutely love something like this, but due to my lack of experience I'm mostly limited to minor tweaks to the code. Things like expanding menu categories for devices, maybe adding more button types, or some layout changes.
As far as your statements on the IR hex codes being different? The only thing I can think if as to the codes being slightly off would be due to the number of slight variations manufacturers themselves implement into their devices. Say for a Samsung TV you might find 3-4 generic code variations or more. A lot of the time its trial and error to get the right code set for the device you are using. For the devices I've manually added I've had no problem working out the right code set that gives me all the right remotes features.
For the most part I picked up this project since I wanted to get my devices in for myself and figure I'd help others who had been making requests over the past year. I'm trying to create as much explanation as I do it so if others want to easily add devices in on their own they can. I've managed to put together a process where the hardest part is just finding the codes, then drop them in my Google doc, run the excel macro script to automatically export the .button files, and all that is left is to build and sign the apk. Right now we don't have too many people making requests so not that hard to keep up with, but the option is there for them to do the finding of the codes and entering them into the spreadsheet on their own and I'll just throw a quick build up afterward.
Perhaps I can throw a guide together for those who wish to do this entirely on their own. Plus im always welcome to help from those with more coding experience than i who want to implement better features.
Click to expand...
Click to collapse
The difference in the codes I was referring to was that they didn't agree with the codes online insofar as the initial few hex words would vary slightly from any I found online and I couldn't find the exact hex string for any device anywhere online, so I assumed they had been converted to work with the specific IR blaster in the watch.
As far as helping you write an interface such as it'd mentioned, I'd be very honored and happy to provide you with any assistance. Having said that, I will move to my next question.
Have you any plans to open source the project? I saw you mentioned documenting how others could add their own devices and I wasn't sure if you meant for them to do so via compiling from source or simply disassembling the so via apktool or the like.
Also, if you're still having trouble generating a keystore, I think I have a script that I'd written to do that, I'd just need to locate it but I'd be glad to share it. It seems daunting, but it's not so bad. If I'm not mistaken, I believe Android Studio provides a wizard to make a keystore as well, but I could be imagining it.

zygh0st said:
The difference in the codes I was referring to was that they didn't agree with the codes online insofar as the initial few hex words would vary slightly from any I found online and I couldn't find the exact hex string for any device anywhere online, so I assumed they had been converted to work with the specific IR blaster in the watch.
As far as helping you write an interface such as it'd mentioned, I'd be very honored and happy to provide you with any assistance. Having said that, I will move to my next question.
Have you any plans to open source the project? I saw you mentioned documenting how others could add their own devices and I wasn't sure if you meant for them to do so via compiling from source or simply disassembling the so via apktool or the like.
Also, if you're still having trouble generating a keystore, I think I have a script that I'd written to do that, I'd just need to locate it but I'd be glad to share it. It seems daunting, but it's not so bad. If I'm not mistaken, I believe Android Studio provides a wizard to make a keystore as well, but I could be imagining it.
Click to expand...
Click to collapse
Yeah i've noticed for the devices I have tested that there have been multiple variations of the code set for devices. One cause for the differentiation in the hex codes could possibly be the code referring to timings? Either way on my devices I was able to simply input the hex codes with no modification into the app and have them work on my devices (Though we can't be sure that will work for all devices until we try more).
I have absolutely no problem open sourcing any of my work. Although as of right now the progress I have made has simply been through that process of disassembling and tinkering with the code. (Bitstra has offered to share with me his work files from the project so just waiting on those to see if there's anything that could help more).
As far as the keystore, I've got that all managed out. Been a bit busy so hadn't had the time to sit down and work on the issue. Got that done today by just using the tools that came with java in cmd line. Really should get around to installing Android Studio as well. Been keeping it simple with notepad++ since I can use a portable version of that at work where I can't install more software.
A future project I would like to do is to create some good documentation and project files for those who would like to compile the project on their own; allowing for custom builds that only contain the devices that someone owns or wants in the app. Would also allow for more direct testing with different codesets instead of waiting for me to push out a new version when a codeset doesn't work on their device.

Button tests for xbox one and samsung model HT
cracksmurf said:
Here is my first release of the updated IR Remote port.
https://www.androidfilehost.com/?fid=24438995911975157
Changelog
-Note
Due to taking over the project and not having the original keystore that bitsra was using, you will receive an [INSTALL_FAILED_UPDATE_INCOMPATIBLE] error if you attempt to install this app over top of his previous version. You must make sure that you remove the previous version before attempting to adb install my version.
Click to expand...
Click to collapse
All the buttons on the xbox remote appears to be working fine. The only problems with it is (on the attached picture) the two circled buttons do the same thing (take you back to the home screen) you could remove one, i like the one that looks like an arrow pointing into a screen. The exit button doesnt appear to do anything and can be removed, the power on and power off individual buttons can be removed too. the button that is SLP can be removed (its the play pause toggle and doesnt work correctly on the xbox)
On the Samsung remote, most buttons function as they should with a few issues. The nav left and nav right both function as nav left. The nav down does not do anything really. You can remove the button assigned to number one.
I understand that the misassignments might be my fault so ill pm you the hex for the corrections.

[projekt.] is a bit touchy on bad reviews.. with good reason?

Hello everyone!
I had a bit of a critical outlet on Substratum. Let me explain why. I've been having some buggy experiences with Substratum overall. Apps not even booting, awkward contrast issues (dark text on dark background and the opposite), bootloops that needed fixing with the Substratum recovery zip, seeing "up-to-date" on layers after I uninstalled them all and rebooted, you name it. The issues have been consistent since Nougat received OMS support, throughout several ROMs. Now, I've always found a way to work around the issues or I sorted it by combining several themes. I've gladly spent some money on premium themes like Flux, Spectrum or Glow but after flashing the first public Android Oreo ROM for OnePlus One, I was a bit surprised by the way [projekt.] handled things. I rooted with Magisk 14.0 and on Substratum installation, I was greeted with this screen:
{
"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"
}
I was not presented with a root request at any point.
When tapping "DOWNLOAD NOW!" it took me to andromeda ★ substratum stock rootless backend (Unreleased) that is rather expensive for an add-on (€1.99) and call me Jon Snow here but shouldn't 'rootless' already be a part of Substratum itself? I also wondered why this wasn't released by [projekt.] but by [projekt.] development team.
I uninstalled the official Substratum (v842) and sideloaded a "bleeding edge build" (v846) from a channel I've been following on Telegram (not sure if I'm allowed to share it so I won't). That one immediately prompted for root and works great. Ironically, after applying themes with that one, replacing the sideloaded build with the official Play Store version now works too. The main point is that I was forced into payment first, so I posted the following review on Play and got the reply stated below it:
I found that last sentence to be somewhat unprofessional: "Or you could always create your own theming app.", it's the type of answer I would expect of a XDA troll or in a flame, not by a representative of the community-driven project that has now become the most prominent player in Android theming. Its presence here as "XDA Community app" dictates that it should be free all the way, no?
https://forum.xda-developers.com/announcement.php?a=81 said:
11. Don’t post with the intention of selling something.
Click to expand...
Click to collapse
The Andromeda thread cleverly works around this as follows:
nicholaschum said:
Play Store (Andromeda): You can install the latest Substratum on Android Oreo, unrooted, and it will prompt you directly (can't link due to paid addon)
Click to expand...
Click to collapse
I could be in the wrong here. Heck, I probably am, but why? If it had remained unanswered, it would just've been another silly review but considering I seem to have struck a chord here, I'd love to have your opinion. Who better than the community itself to judge me :silly:

Timmmmaaahh said:
I was greeted with this screen:
I was not presented with a root request at any point.
Click to expand...
Click to collapse
Timmmmaaahh said:
I uninstalled the official Substratum (v842) and sideloaded a "bleeding edge build" (v846) from a channel I've been following on Telegram (not sure if I'm allowed to share it so I won't).
Click to expand...
Click to collapse
Every version on Play Store always requests root, but the act of uninstalling the Play Store version in favor of the Telegram debug versions reset the reauthentication trigger on SuperSU/Magisk, so you were asked for it again.
Timmmmaaahh said:
When tapping "DOWNLOAD NOW!" it took me to andromeda ★ substratum stock rootless backend (Unreleased) that is rather expensive for an add-on (€1.99) and call me Jon Snow here but shouldn't 'rootless' already be a part of Substratum itself? I also wondered why this wasn't released by [projekt.] but by [projekt.] development team.
Click to expand...
Click to collapse
This addon is not included in Substratum for several reasons. Firstly, the nature of the app requires it to be run in a static manner as a normal Java desktop app. Secondly, just like Theme Interfacer, we aren't meant to update it often, requiring a full restart of the device. They are released by our company, of which XDA works with as a partner.
Timmmmaaahh said:
The main point is that I was forced into payment first, so I posted the following review on Play and got the reply stated below it:
Click to expand...
Click to collapse
You weren't forced into payment, you just were not aware that reinstalling the application would reset the authentication prompt delivered through Magisk/SuperSU.
Timmmmaaahh said:
I found that last sentence to be somewhat unprofessional: "Or you could always create your own theming app.", it's the type of answer I would expect of a XDA troll or in a flame, not by a representative of the community-driven project that has now become the most prominent player in Android theming. Its presence here as "XDA Community app" dictates that it should be free all the way, no?
Click to expand...
Click to collapse
I hope you understand that by one-starring our application, you have every right to do so. But using it to get our attention, you resorted to the lowest of Play Store reviews already. I'm not saying anyone did anything wrong, but you could have contacted us directly regarding complaints or bug reports. You can check our source code and see that we have not touched the root requester logic for root checks in a long while, yet it magically works after uninstalling the Play Store version (different signature from our CI builds) - the reason is due to the authentication on Magisk/SuperSU.
I hope you understand that you could have easily spoken to us, but you ended up using the Play Store's review place. You could have contacted me here, and I would be able to help you. We are all trying to have fun, if you believe that us asking for a small payment for all our work is too much to ask for, then what Char said was rather correct, you should try building it yourself.
Timmmmaaahh said:
The Andromeda thread cleverly works around this as follows:
Click to expand...
Click to collapse
Not "cleverly", it's for respecting the forum rules. We are in partnership with XDA afterall, just compare our Play Store address with the Contact address on the site.

Timmmmaaahh said:
Hello everyone!
I had a bit of a critical outlet on Substratum. Let me explain why. I've been having some buggy experiences with Substratum overall. Apps not even booting, awkward contrast issues (dark text on dark background and the opposite), bootloops that needed fixing with the Substratum recovery zip, seeing "up-to-date" on layers after I uninstalled them all and rebooted, you name it. The issues have been consistent since Nougat received OMS support, throughout several ROMs. Now, I've always found a way to work around the issues or I sorted it by combining several themes. I've gladly spent some money on premium themes like Flux, Spectrum or Glow but after flashing the first public Android Oreo ROM for OnePlus One, I was a bit surprised by the way [projekt.] handled things. I rooted with Magisk 14.0 and on Substratum installation, I was greeted with this screen:
I was not presented with a root request at any point.
When tapping "DOWNLOAD NOW!" it took me to andromeda ★ substratum stock rootless backend (Unreleased) that is rather expensive for an add-on (€1.99) and call me Jon Snow here but shouldn't 'rootless' already be a part of Substratum itself? I also wondered why this wasn't released by [projekt.] but by [projekt.] development team.
I uninstalled the official Substratum (v842) and sideloaded a "bleeding edge build" (v846) from a channel I've been following on Telegram (not sure if I'm allowed to share it so I won't). That one immediately prompted for root and works great. Ironically, after applying themes with that one, replacing the sideloaded build with the official Play Store version now works too. The main point is that I was forced into payment first, so I posted the following review on Play and got the reply stated below it:
I found that last sentence to be somewhat unprofessional: "Or you could always create your own theming app.", it's the type of answer I would expect of a XDA troll or in a flame, not by a representative of the community-driven project that has now become the most prominent player in Android theming. Its presence here as "XDA Community app" dictates that it should be free all the way, no?
The Andromeda thread cleverly works around this as follows:
I could be in the wrong here. Heck, I probably am, but why? If it had remained unanswered, it would just've been another silly review but considering I seem to have struck a chord here, I'd love to have your opinion. Who better than the community itself to judge me :silly:
Click to expand...
Click to collapse
Since you know where our thread is, it would have been better for you to bring your concerns over being 'forced' to purchase Andromeda to us here, rather than in the reviews on the play store.

@nicholaschum @Char_G
Good day!
Look at that, mister Chum himself responds and that is, naturally, very much appreciated. About the term 'force', of course I could find my way around it, this is more about the people that can't. And don't think I didn't consult anyone beforehand, I'd spoken about aforementioned issues to theme developers and people that exceed my skill level with great length. But you're right, I should've gone to the source, that approach was wrong of me. I have adjusted the review yesterday. Fact remains, though, that Substratum still has a long way to go in terms of compatibility and stability. I'm glad I had your undivided attention to the matter. In all honesty, I personally din't consider Play Store reviews to be as 'significant' as they seem to be judging by the reaction. Of course, I'm not a developer, how would I know. Therefore I offer my apologies and I'll be more considerate upon writing further reviews.
It's a little troubling, still, that non-rooted users are still forced into payment or did I misunderstand that? Say a 6P owner takes the official Oreo update and installs Substratum, that person will have to pay for Andromeda for any theming to work, right? I'm not saying that's bad practise, it is well within your right to get paid for the tremendous amount of amazing work you guys do. Heck, I wouldn't even mind an ad or two in Substratum. I'm merely highlighting the fine line between your profitable enterprise and the free open source nature of this community.
For the record, again, that is completely unrelated to my endless respect for your work.

Timmmmaaahh said:
@nicholaschum @Char_G
Good day!
Look at that, mister Chum himself responds and that is, naturally, very much appreciated. About the term 'force', of course I could find my way around it, this is more about the people that can't. And don't think I didn't consult anyone beforehand, I'd spoken about aforementioned issues to theme developers and people that exceed my skill level with great length. But you're right, I should've gone to the source, that approach was wrong of me. I have adjusted the review yesterday. Fact remains, though, that Substratum still has a long way to go in terms of compatibility and stability. I'm glad I had your undivided attention to the matter. In all honesty, I personally din't consider Play Store reviews to be as 'significant' as they seem to be judging by the reaction. Of course, I'm not a developer, how would I know. Therefore I offer my apologies and I'll be more considerate upon writing further reviews.
It's a little troubling, still, that non-rooted users are still forced into payment or did I misunderstand that? Say a 6P owner takes the official Oreo update and installs Substratum, that person will have to pay for Andromeda for any theming to work, right? I'm not saying that's bad practise, it is well within your right to get paid for the tremendous amount of amazing work you guys do. Heck, I wouldn't even mind an ad or two in Substratum. I'm merely highlighting the fine line between your profitable enterprise and the free open source nature of this community.
For the record, again, that is completely unrelated to my endless respect for your work.
Click to expand...
Click to collapse
Again, no one is being 'forced' to do anything, they are quite welcome to use Substratum with root or with a supported custom ROM for free. If they choose to stay unrooted, then they will have to choose between paying the small fee to use Substratum with andromeda or theming manually without our apps to ease the process.