Are there any sites or forums that are heavy on N1/Android command line discussion? I don't mean simple "how-to use the command line" stuff, but sites where people are working to port Linux shell utilities, creating scripts or figuring out new tricks for the N1/Android shell?
For example, there was a discussion here about rescanning the sdcard for new media and people posted apps that could do it. My first reaction was that, instead of using an app, there's probably a way to do it with a one-liner script and run it from GScript with a single click. I didn't look into it, and I'm sure there's no interest in that particular question, but are there any geeks out there who like figuring out things like that?
There are a few command line related threads here and my googling indicates there are a few at other boards from time to time, but for the most part, they're lost in the mix.
Related
Thanks for taking a look at it. Hopefully soon I'll have much more going on in it.
v0.1a
adb cmd shell integration
ability to script adb commands
ability to save and edit scripts
local adb, no need to download the sdk
requires:
windows xp+
.net framework 3.5
instructions:
unzip
plug in phone
run adbwin.exe
that's it, not much more to it
any ideas, thoughts, constructive criticism would be great
again, thanks for taking a look
in the future I'd like to implement possibly a drag-drop interface for adb shell ls / push / pull, etc like a file manager
Us Linux guys never get any love.. hmm
Love the idea though, keep it up.
Excellent work, can't wait to see what else is in store for this... Posted a link on the AC forum...
i've been trying to do something like this for linux users, i am just afraid that if we release a nice little GUI for any of the operating systems in order to use adb we'll have more people with messed up phones. personally i prefer to work in the terminal, i set mine to green on black to remember the old days(before my time).
tubaking182 said:
i've been trying to do something like this for linux users, i am just afraid that if we release a nice little GUI for any of the operating systems in order to use adb we'll have more people with messed up phones. personally i prefer to work in the terminal, i set mine to green on black to remember the old days(before my time).
Click to expand...
Click to collapse
True I think terminal is just easy to use for everything.
tubaking182 said:
i've been trying to do something like this for linux users, i am just afraid that if we release a nice little GUI for any of the operating systems in order to use adb we'll have more people with messed up phones. personally i prefer to work in the terminal, i set mine to green on black to remember the old days(before my time).
Click to expand...
Click to collapse
yeah, but a properly built GUI would save a lot of time on daily chores like typing adb push path path. could have programmed a java version, but I am not sure if I would spend more time drawing the window or implementing the logic...
This is a great idea. I'd pay for a license.
Hello all so Im new to android I came over from BB I got sick of the worthless OS they keep updating. Im trying to get up to speed everything with android. I got root last night using the unevoked's new process. As Im reading different threads I keep hearing people refer to adb shell. What is this? I also have a PC and a MAC but I'm more of a Mac guy, is most the stuff you need to do better done on PC or can it be done on Mac's because they talk about opening a command line which of course is done in DOS. Can anyone shed light on this for me? Thanks in advance
adb is a part of the Google Android SDK. http://developer.android.com/sdk/index.html It's available for Mac, PC, or Linux. Really, it boils down to preference. I believe setup is easier for Linux and Macs, but it's still pretty easy for a PC.
You can use Terminal, or whatever. It just needs a command-line interface for you to type into.
Thank you for the link and the explanation. I think its been to long since Ive had a open source device im way behind the curve i guess. Is there a good thread or a site for someone like me to start at that will start at the beginning and explain what SDK is and everything else?
Firstly, for a general how to of what's going on with our device, adb, so on and so forth, this thread is pretty awesome:
http://forum.xda-developers.com/showthread.php?t=709220
For a more in depth explanation of development and the like hit up:
http://developer.android.com
For the vast majority of what you're going to be doing, you need to be pretty familiar with command line scripts and the like. Also, if you want to write applications, you'll need to know java. If you really aren't all that interested in developing and just want to know about adb, that first link is a pretty good crash course.
Hi, I am an Android development newbie that has grasp of general concepts, played with ADB a little, and Eclipse a little.
My current idea is to develope an app that actually decodes the various memory stats for Android, merely as an education for my Android development. I do not intend to create "yet another task killer".
I know about free, meminfo, and procrank.
My overall objective are to run one of those (maybe all of them and somehow merge the numbers), get their numbers, parse them, and then display some sort of graph that will show where the memory went. Or in other words, I want to write something similar to DiskUsage, but for RAM.
So the question is... How do you run one of these shell (or busybox) commands, and get the output, so a Java program can parse it? My Google-fu is weak and I can't seem to find any references on this. though I think I am using the wrong keywords.
I know there's an app called Meminfo that displays cat /proc/meminfo so I know it can be done. Heck, SetCPU also does it (and much more under Info)
kschang said:
Hi, I am an Android development newbie that has grasp of general concepts, played with ADB a little, and Eclipse a little.
My current idea is to develope an app that actually decodes the various memory stats for Android, merely as an education for my Android development. I do not intend to create "yet another task killer".
I know about free, meminfo, and procrank.
My overall objective are to run one of those (maybe all of them and somehow merge the numbers), get their numbers, parse them, and then display some sort of graph that will show where the memory went. Or in other words, I want to write something similar to DiskUsage, but for RAM.
So the question is... How do you run one of these shell (or busybox) commands, and get the output, so a Java program can parse it? My Google-fu is weak and I can't seem to find any references on this. though I think I am using the wrong keywords.
I know there's an app called Meminfo that displays cat /proc/meminfo so I know it can be done. Heck, SetCPU also does it (and much more under Info)
Click to expand...
Click to collapse
For executing shell commands, look for code examples that use Runtime.getRuntime().exec(); like this post.
Depending on what you want to do, you may not need to execute shell commands to get this information: just open /proc/meminfo (or whateever) directly as a regular file and parse the content.
- jc
Got that. Thanks. I may go with the meminfo as that seem to be the most painless way to get started.
Hey everyone; it wouldn't let me post in the development subforum due to the fact that I just joined, but I figured my topic would be just as relevant here.
I'm a sophomore CompSci major. Java is my strong point, but I'm far from a master. I know syntax, I know how to follow what's going on in more advanced programs, but writing them is the tough part. Anyway, I would like to create my first app; something simple. I was thinking a calculator with a small clipboard on the side (hold the button to store the number displayed in the window, hit it to place that value). It would be insanely helpful for my physics class.
So a few questions for you guys:
-Is there anything I should know beforehand? Anything to be careful of?
-Can I use Eclipse? I tried with App Inventor, and it's too limited.
-How do I obtain examples of more complex apps? Can I unpackage the apk files into java classes?
-Is there a site similar to the sun library, where it lists the available classes/objects/imports?
I'm sorry if I don't know the lingo just yet (of Droid or Java). Picking this all up is a little difficult for me, but I'm trying
Thank you in advance for even taking the time to read this. I understand rookies must aggravate you guys, but from what I've seen, the community has been nothing but welcoming!
You can definitely use Android SDK with Eclipse.
This guide will help you with install and set up process
http://developer.android.com/sdk/installing.html
SDK also contains sample projects that you can use for learning.
I don't remember about unpackaging apk files, but I'm pretty sure they contain already compiled .class files, which will be of no use to you.
And here's Android's reference page:
http://developer.android.com/reference/packages.html
Also the dev guide is very useful for learning the basics:
http://developer.android.com/guide/index.html
Resources section has useful tutorials as well!
Hope that helps. Good luck with your app!
Thank you, meshdub! And all branching from the same site; sure made me look bad...but on the upside, you've introduced me to a source I will be able to use throughout my software development lifetime.
If there's any more you or anyone else could give me as far as what to expect or look out for, please let me know! I'm honestly a little intimidated by this; I'm not too familiar with forums, and I've heard how difficult app developing can be.
But this should keep me occupied for a while, and again, thank you very much
I am looking for analysis tools specific for Android app development!
I have found many tools online that are not specific for Android, only for Java, either free or commercial, like the famous FindBugs but it is not interprocedural so for example it loses several bad NullPointerExceptions that may occur at runtime! Other tools (like CheckStyle) perform just a syntax check that sometimes is not so powerful, and other tools are not suitable for Android app development
What are, among the available tools, those that you prefer and really use?
What kind of properties do these tools check?
What kind of bugs do these tools detect and remove (among the most common errors that an Android developer may do)?
Please help me with sharing your experiences and suggestions, thanks!
Nobody uses any tool for detecting bugs?
What kind of bugs are you specifically looking for? Solving NullPointers is hard to do automatically, it'll probably just show you where the error is and what it is.
And the emulator/logcat does that, too...
bassie1995 said:
What kind of bugs are you specifically looking for? Solving NullPointers is hard to do automatically, it'll probably just show you where the error is and what it is.
And the emulator/logcat does that, too...
Click to expand...
Click to collapse
I would like to detect the most common errors that may happen during Android app development, like NullPointerExceptions, ClassCastExceptions, OutOfMemory Errors, and so on... but with tools like FindBugs that don't need to execute the app first.
subtask said:
I would like to detect the most common errors that may happen during Android app development, like NullPointerExceptions, ClassCastExceptions, OutOfMemory Errors, and so on... but with tools like FindBugs that don't need to execute the app first.
Click to expand...
Click to collapse
I don't think that's really possible, it would have to be able to reason about and come up with the behaviour of your code like a human... Computers need to run it. The easiest thing you'll get right now is an explanation of what went wrong where, I think...
bassie1995 said:
I don't think that's really possible, it would have to be able to reason about and come up with the behaviour of your code like a human... Computers need to run it. The easiest thing you'll get right now is an explanation of what went wrong where, I think...
Click to expand...
Click to collapse
If you run FindBugs in your source code, it is able to detect many things, like potential NullPointerExceptions, before running your app...but unfortunately it is not powerful enough to detect interprocedural NullPointerExceptions...that's the reason I am looking for something different...
subtask said:
If you run FindBugs in your source code, it is able to detect many things, like potential NullPointerExceptions, before running your app...but unfortunately it is not powerful enough to detect interprocedural NullPointerExceptions...that's the reason I am looking for something different...
Click to expand...
Click to collapse
Yep, that's what I meant. Anyhow, I don't know about anything like it .
The Android SDK provides some API for automatic testing.
You will need to create a test project which checks the functions you want to achieve.
This can be used to ensure that your app is still working correctly after adding new features.
Hi
"static analysis tools" is probably the term you want to be using when looking for these sort of tools, the wikipedia page give a good selection to be going on with http://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis
Although I would add that if you're getting a lot of these sort of errors then you probably need to work on your own code writing skills and take the time to understand how and when these sort of issues occur rather than just relying on a plethora of tools which keep you dumb to what's going on! You'll benefit from it in the long run
One thing you might give a try is JetBrains Android Studio. It seems to have a decent static analysis tool which is the same used for ReSharper with Visual Studio.
Try Lint, it comes with ADT,
with Eclipse you can right click your project, ans under android tools you will see something like check lint errors
It will create lots of errors, which are just recomendations, you can simply delete those errors.
Tapatalked... just Tapatalked...
If you're mainly looking for a way to detect NPEs then IntelliJ/Android Studio comes with NPE (and other exceptions) detection. It's based on a new set of annotations implemented in the latest SDK and is very accurate, much better than Eclipse's code analysis.
But honestly, the best tool to find bugs remains Logcat imo, it's verbose enough to find-out the origin of most bugs.