Does anyone know if Google will ever update the tutorials in the DevGuide to 1.5? I myself highly doubt it but I'm still looking for that ray of hope, looking through source code hasn't helped me learn (some I find don't have comments at all). Does anyone else know of any other Android Application Development tutorials? (tried googling couldn't find anything except the Google one's)
all the source code has ample comments, download that(don't ask me how) and read through that, they will probably release updates for the tutorials when they release chrome for linux(was supposed to be released 6 months after the windows ver.) so when i have chrome on my computer you can have updates for your tutorials
Alright looks like I gotta boot up Linux again ( that is the only way to get the source code isn't it?) besides I liked Linux so much more but I needed my sanity when doing tasks that are windows based
it's not the only way, but it is a hell of a lot easier, i haven't touched windows in three years and just enrolled in schooling to get my micro**** certs, so i gotta go find a windows comp in my basement(really outdated)
Ha Ha Ha, once I get used to Linux I think I might go cold-turkey on windows.
Related
Hello all,
This post is in regard to the Google Android Challenge put out by Google to create/develop new software for the Google Android shell. If you haven't had a chance to read about it, it's basically a new OS created by Google to run on any type of PDAesque cellular phone. The challenge issued is then to develop new software for this OS (written in Java) so that when it is released it will have software available for it.
My question to all of you is what software would you like to see developed for this new OS? The reason I am asking for ideas is because I am a CS undergraduate student working in a research group to create one of these programs. Ergo, I figured asking you guys what you'd like to see created would be the best way to get ideas that will make sense and benefit the community.
Any ideas you submit here may be used in the creation of new software--if you require idea copyrights that can be worked out.
Thank you all in advance,
Jake
Jake Lake
Undergraduate Student at LCSC Lewiston, ID
Hello Jake,
We'll I'm a Java programmer too, not thinking of entering the challenge though. Had a quick look at the SDK for Android and it does'nt seem like pure java, more like a hybrid of C and Java does'nt it?
Since I have'nt had a thorough look at it, I'd like to ask you a few questions regarding the freedom to program on the platform.
Since it does'nt use the "normal" JVM but googles Davlik where theres no byte code but script code, does it allow better interaction with the hardware, and is it faster? Also can you implement equallizers and other effects in a media based application, which of course was not possible on J2ME. I was thinking on a All-round mediaplayer for Android, something like Rockbox which maybe found at www.rockbox.org which is a linux based program used on iPods etc.. but has been ported to Linux based EZX phones.
Regards,
Akshay
I know how to do the WM stuff - and have some old kitchens. I used to be fairly involved in doing my own back in the Kaiser days, but never did publish them (there were always questions about whether it was REALLY kosher to do so)
Well, Android is Open Source (mostly) and so I'd like to get involved with it for the HD2. I'll publish here and maintain as well - if I come up with something useful.
Does anyone have a framework to start with on getting started? Is it best done from Windows (Win7 here) or do I need to build up a Linux box for this?
If it's already here (I looked around) please point me to it... or any online resource for that matter.
Mostly interested in cooking up NAND stuff....
(I build and write software - including kernel code in the FreeBSD realm, so I'm familiar with the "hows" - just need the correct pointers to the tools and bits I need along with a primer; I can take it from there.)
Thanks in advance!
I'm interested in the same kind of info, but it seems it's a secret kept somewhat close to the chest, and although there are tutorials aplenty for the end user, there is a clear lack of tuturials on how to make your own ROMs (be it WinMo, or Android). Either "chefs" don't want any more clutter and garbage around, or they don't think there is interest on such info...
Anyway, here is an article to get you started (little meat in the info, but dig around the wiki):
http://www.htc-linux.org/wiki/index.php?title=QuickDeveloperStartGuide
u Guy's even have take look to chef corner in this site
I have been trying to learn how to do some android development for work and keep running into problems. I find it hard to believe that people are able to create a lot of these apps with the Google development tools in such poor condition.
I have set up a development system with eclipse and the android tools. One of the first problems I ran into is ADB crashing whenever I tried to debug and there was a device attached to the system. Didn't matter if I was trying to debug on the device or emulator, ADB would crash. I was finally able to get the problem fixed by using the Composite ADB interface driver instead of the plain ADB interface (would it really hurt Google to add one sentence to the directions to tell people this?)
Now every time I go to debug, the emulator comes up in Chinese/Japaneses. I type in English and it converts it. I can fix it by changing the input method, but I have to do it every time I start the emulator. I have Googled looking for a solution and have found this is a known problem that has been around for almost a year and there is no resolution with it. The bug reports I have found on the android site even lists them still as NEW!
When trying to debug a problem, I wanted to delete the shared preference file for the app as it seems like it had become corrupted and every time it went to read it, the app would force close. (And when this happen, the debugger perspective would come up but for the life of me, I could not find any information as to what caused the fault or any sort of stack trace to look back and see where in my code it failed).
If you are an app developer, are you running into these issues? Have you found ways to work around the problems? I just can't believe that this is the way people develop for this platform. I'm ready to tell my boss that we forget about the platform unless we can find some stable development tools, otherwise we will be spending more time fighting with the tools than working on the app.
If anyone has any suggestions, I would really like to hear them. I'm not a noob when it comes to software development (20+ years as a software engineer), but I have never seen development tools for such a major platform, be this poorly done. What am I missing?
I'm a professional developer as well too. 20 years or so as a C/C++ developer, but I've worked most of my career as a Unix developer. Naturally, I use linux where possible and my Eclipse setup on Gentoo linux is pretty stable. I tried on Win7-64 but it was buggy as heck. I believe that the problem is with Java. There seems to be so many ways to set it up wrong that I'm not sure you can set it up right under windows.
I find it ironic that Oracle is trying to sue Google for making a JVM that actually works!
I havent had any of your mentioned issues. I am running eclipse on a 32 vista machine and a 64 bit windows 7 machine.
Not sure what I may have done different that you for setup. But I followed the Android application development for dummies book. The author goes step by step of what to download and how to install and configure. Even though your software experience is way beyond this book maybe its worth picking it up to read the install notes.
FreeTheWorld said:
I havent had any of your mentioned issues. I am running eclipse on a 32 vista machine and a 64 bit windows 7 machine.
Not sure what I may have done different that you for setup. But I followed the Android application development for dummies book. The author goes step by step of what to download and how to install and configure. Even though your software experience is way beyond this book maybe its worth picking it up to read the install notes.
Click to expand...
Click to collapse
I picked up the book, "Sams Teach Yourself Android Application Development in 24 Hours" and it has a section for setting up the environment too. Followed it to the letter several times and always had this problems. I think the issue comes down to the books were written using version 6 and 7 of the SDK and the current version, 8, has introduced some problems the books don't cover. For example, the tools directory has been split into two directories, tools and platform-tools. When you first download the SDK, you don't get everything you had like before until you update the SDK.
I have talked to several other people who also had the problem with the ADB crashing like I did, even started a thread here about it. No one could get any help anywhere on resolving the issue. I think the problems I have that others don't see is because they started with an earlier version of the SDK.
Gene Poole said:
I'm a professional developer as well too. 20 years or so as a C/C++ developer, but I've worked most of my career as a Unix developer. Naturally, I use linux where possible and my Eclipse setup on Gentoo linux is pretty stable. I tried on Win7-64 but it was buggy as heck. I believe that the problem is with Java. There seems to be so many ways to set it up wrong that I'm not sure you can set it up right under windows.
I find it ironic that Oracle is trying to sue Google for making a JVM that actually works!
Click to expand...
Click to collapse
I have also setup the development platform on a linux system and haven't had the problems I have with Windows 7 64bit. I also feel a lot of the problems have come from the Windows 64bit platform and even windows in general. I tried installing on a clean 64bit and 32bit Windows 7 and was still having the ADB problem. As soon as I get my tax refunds, I'm going to get a work desk setup at home so I can try using my linux system (it sits on the floor with no monitor and is my network server). Boss will really love it if I tell him we have to set up linux platforms to develop on. Guy is a bit of a tight wad when it comes to equipment.
edboston said:
If you are an app developer, are you running into these issues?
Click to expand...
Click to collapse
Nope, I didn't have any stability problems with SDK. I use linux 32-bit, didn't try to work on a Windows, MacOS and/or 64-bit arch.
I've not seen any of your problems, either.
FYI, I followed these instructions to set up the env:
http://developer.android.com/resources/tutorials/hello-world.html
(Environment - WinXP/32 netbook)
Eclipse is buggy. The most annoying issue with it is that the auto complete freezes your computer at times.
An alternative is IntelliJ. They offer a free community addition. I work with one dev that swears by it.
I use Windows7x64 and Ubuntu 10.10 to develop my apps. I use IntelliJ mostly because I find Eclipse to be convoluted overcomplicated mess. I think the Android integration in Eclipse is better, especially around editing some of the key XML files but I despise how projects are organized in Eclipse.
The OS you use really doesn't matter the results are the same, once you're up and running the work will be the same so the OS becomes irrelevant. The IDE becomes the differentiator.
I haven't met with the issues you mentioned, but as you said it can be because I installed the sdk a long time ago (after google anounced the eclair). I'm using eclipse and yes, that program is full of bugs, but I read an article about developing for android in Netbeans (my personal favorite). You can read it here: http://androidportal.hu/2011-01-09/fejlesztes-androidra-netbeans-segitsegevel (it's hungarian, but google translate is our friend)
Sent from my GT-I5700 using XDA App
MotoDev Studio 2.01
stick to 32-bit Galileo
for the slow autocomplete problem, I've made sure to use eclipse Galileo, something in Helios was causing massive lag. Also make sure you're running the 32-bit version of eclipse, even if your machine is 64-bit, there are definitely some bugs last time I tried to install ADT on 64-bit eclipse.
the new tools directory was a bit of a pain after updating to the latest API but nothing too bad once you figured it out.
I haven't had many of the other problems you mentioned. I always debug with adb logcat from terminal, and you can always hop into the device with adb shell.
I use eclipse every day at work so I've kind of gotten used to all the little quirks. I had the chinese text problem with the emulator, but I do most of my testing on a real phone. I use the emulator just to try out different resolutions.
Hi All,
I'm a software developer, reasonably comfortable with compiling apps in Linux, though still got more to learn on inner workings of the full system.
I've been thinking about following the Linux from Scratch book for a while - and also about converting my Nook e-reader into a useful device for developing on when out im the sun.
I guess there are some significant challenges here - device trees and commercial secrets, perhaps some crypto keys used for signing update images to boot (I'm familiar with these problems, but not solutions or good workarounds).
What I'd really like is a good understanding of:
- what tool chain I need to setup
- What has been tried already and what the problems were
- any further help/datasheets that can get me going
I'd have posted this in the 'android development' area as the closest forum for what l'm trying to do, but apparently I'm not allowed until I've got my post count up - so I'm being forced to post in 'general'. If someone agrees and can move it, that would be great.
P.s. I have searched the xda site, but I'm not finding what I'm looking for. I'm sure it must be here somewhere, so any pointers/links on where it is would be appreciated.
SimonSimpson said:
Hi All,
I'm a software developer, reasonably comfortable with compiling apps in Linux, though still got more to learn on inner workings of the full system.
I've been thinking about following the Linux from Scratch book for a while - and also about converting my Nook e-reader into a useful device for developing on when out im the sun.
I guess there are some significant challenges here - device trees and commercial secrets, perhaps some crypto keys used for signing update images to boot (I'm familiar with these problems, but not solutions or good workarounds).
What I'd really like is a good understanding of:
- what tool chain I need to setup
- What has been tried already and what the problems were
- any further help/datasheets that can get me going
I'd have posted this in the 'android development' area as the closest forum for what l'm trying to do, but apparently I'm not allowed until I've got my post count up - so I'm being forced to post in 'general'. If someone agrees and can move it, that would be great.
P.s. I have searched the xda site, but I'm not finding what I'm looking for. I'm sure it must be here somewhere, so any pointers/links on where it is would be appreciated.
Click to expand...
Click to collapse
I have tried to get info on such things three times over 2 years for different devices, no one every seems to point me in the right direction, the most i have been able to find out is how to make compile cm and a little bit of how to customize roms, not to be a downer but i think the process is often so different for ever device and difficulties usually happen that the only people that build roms are people that have either have experience I n some form from their job, just edit existing source for cm(updating to a new version, customizing roms ect...) or have screwed with the stuff for years till the point that they just figured out alot of problems themselves. Wish a could find a good guide myself to atleast get the basic dependencies required for a device to boot together, if i could get something to boot the rest of the issues could be worked out with trial and error, boot noone on xda, Android authority, Reddit or cm's own forums goes into enough depth to make that possible.
Hi jaykoerner,
Thanks for your reply - good to know I'm not alone with my echo!
I've discovered some useful links if anyone wants to begin getting to grips with all this...
1. XDA Devs has a wiki (not sure how to find from the forum links...?)
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch
2. There's a (atleast one) customized kernel (and probably a dev-tool chain) available on GitHub:
https://github.com/javifo/NST/tree/master/kernel -- including kernel compilation instructions
https://github.com/javifo/NST -- root of the repository.
3. Parallel to Raspberry Pi kernel compilation (so you may want to learn from that as it probably has more articles)
https://www.raspberrypi.org/documentation/linux/kernel/building.md
I'll post more when I next do something with the information (Still want to understand more on the android HAL)
Hope that helps someone!
SS.
SimonSimpson said:
Hi jaykoerner,
Thanks for your reply - good to know I'm not alone with my echo!
I've discovered some useful links if anyone wants to begin getting to grips with all this...
1. XDA Devs has a wiki (not sure how to find from the forum links...?)
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch
2. There's a (atleast one) customized kernel (and probably a dev-tool chain) available on GitHub:
https://github.com/javifo/NST/tree/master/kernel -- including kernel compilation instructions
https://github.com/javifo/NST -- root of the repository.
3. Parallel to Raspberry Pi kernel compilation (so you may want to learn from that as it probably has more articles)
https://www.raspberrypi.org/documentation/linux/kernel/building.md
I'll post more when I next do something with the information (Still want to understand more on the android HAL)
Hope that helps someone!
SS.
Click to expand...
Click to collapse
My initial thought was that toolchain should match the underlay Linux kernel of Eclair (2.6.x.y) for us to be sure it could be run on NST. This info that I still have to search through is certainly helpful. Thanks!
SimonSimpson said:
I guess there are some significant challenges here - device trees and commercial secrets, perhaps some crypto keys used for signing update images to boot...
Click to expand...
Click to collapse
Neither the NST or the newer glows use device trees.
In the Glows this is all handled by the custom ntxconfig which allows simple configuration.
For building Android apps, you use the straight Android SDK, possibly also the Android NDK (for native code).
You'd also use the NDK for building command line utilities.
I've never built a kernel from scratch, but I have binary modified/patched them.
There is the simpler bit of patching system image ramdisks which can be conviently handled by my imgutil.exe in the signature.
If you want to do audio, you really are better off with the Glow4 (7.8") which actually supports it.
I've looked around on stack overflow and other places trying to find answers. I have software I want to install on my phone so I can more easily chat, send files, links, etc. on LANs that I work within throughout my day. This program works well for me: https://www.beebeep.net/download
I can use this on my windows and linux boxes. I want to integrate my phones into this communications array.
I'm looking at the snapcraft or any of the other linux variants. I can't figure out how to run a linux app on droid.
I can ssh through the terminal and so on. I can perform other functions that one normally does in BASH though now that I think of it, I haven't tried crontab. Anyway, how could I get this BeeBeep script to work on my android? Can anyone help solve this problem?
I have not seen anything on this, but very interested in this Linux development...
I did see an XDA section for only Ubuntu Touch...
I don't know about direct onto android but apparently it can be done to Chromebooks and I know that android apps can be converted to work on Chromebooks too so perhaps it can be reversed?
https://www.androidcentral.com/how-install-linux-apps-your-chromebook
So basically if an app could be converted to work on a Chromebook could it then be further converted to work on Android?
Seems like a long shot but you never know.
I've seen Windows apps / games work on Android, I've had Wolfenstein, quake arena and doom 3 ports on my phone so I would assume that Linux being a much closer cousin to Android would be an easier chore.
What you need is a framework to do the work for you, not to emulate but to directly port..
Can't find much online but I think if you dig enough you may find something
Certainly interesting though, best of luck pal.
If I find something, I'll post in development. This is a backburner project, but clearly it's one I need to take on myself. Thanx for your responses.