Last Build Date: Fri, 24 Jul 2009 10:24:11 -0400Copyright: Copyright 2009
Thu, 23 Jul 2009 13:54:05 -0400
Ahem Motorola HQ-Android guys, the blog has moved to:
You will find coverage of the AndCooper Android Dev tool there.
Wed, 10 Jun 2009 07:43:34 -0400Some new resources at AndMob have popped up including code examples, both links to Eclipse and Netbeans plugins and etc. You can find the link to AndMob on the right side of where this blog moved to, namely Mobilebytes. Also do not forget AndroidSnippets and Stackoverflow even has an Andorid area of questions and answers. Recent AndroidSnippets additions are featured on AndMob. You can reach Stackoverflow from my MobileBytes right menu and do an andoird word search in the search box to find the Android development questisn and answers.
Mon, 8 Jun 2009 03:02:52 -0400
To my OEM readers such as RIM, SonyEricsson, Nokia, Motorola, and etc. As I progress towards the last seps in the AndCooper Android Build Tool 0.1 release I have moved my blogging to a new platform and site. The new site is:
on the wordpress blog/CMS platform. since I am able to post sample code easier with wordpress and etc I would like to see my OEM blog readers at my new site of Android Code and Development blogging. Hopefully, I will see yoru readership there. Hopefully, at some point PLanetAndorid changes their blogroll links and feed crawing to include and craw my new Android development Blog.
Sat, 6 Jun 2009 04:07:19 -0400
Some new Android Programming Wiki Articles at Mobilebytes. Link in right side menu under Profiles, FredGrott's Knols. I have moved my blogging over to Mobielbytes, so please change your bookmark to:
Thu, 4 Jun 2009 07:01:56 -0400
I at my Mobilebytes Post updated the link to the Android Google IO 2009 slides, once they have them up today that is where you can find links to each individual presentation and slide group.
Once gain, I have moved my blogging to Mobilebytes, change your bookmarks to:
Wed, 3 Jun 2009 09:06:25 -0400You will find details about when the Android Google IO 2009 slides and presentations will be up at this post.
Tue, 2 Jun 2009 10:05:11 -0400
I started covering the AndCooper Build Tool coding internals at MobileBytes blog. In the first part I cover how I detect the SDK version and adjust the SDK tools location and add-on apis. If you have not adjusted your feed reader, everything now is blogged at MobileBytes and the feed is:
AndCooper 0.1 release and release notes posted late Today at MobileBytes blog.
Mon, 1 Jun 2009 06:45:14 -0400
Late today, you wil find coverage of the first release of AndCooper 0.1, the Android Applications Ant based Build Tool, at the MobileBytes blog. Details of where to download, supported features in 0.1 and plans for 0.2 will be disclosed.
As we await the uploading of the Google 2009 IO Android Presentations to Youtube I expect to upload some Android Code Examples and Analysis discussions to my MobileBytes blog to show the challenges of Androdi code optimization for application development.
I have moved all my blogging to MobileBytes blog, but will remind everyone to change their links and bookmarks for another week or two.
For those still using Roller(Jrolller). Rick Ross and the Dzone crew is hard at work hardening the wordpress blogging solution for blogging use on the dzone networks. I am sure registrations to wordpress powered blogging from Dzone will occur shortly.
Sun, 31 May 2009 06:20:57 -0400
i started a new more focused Mobile blog where Android is covered, called MobileBytes. The RSS feed is:
The Roller blog system really has not kept up with changes and improvements in blogging. Hopefully, my switch to the wordpress blogging platform will enocurage a lot more in-depth coverage of mobile technology and Android. Yes, there is already soem Android posts this morning.
Fri, 29 May 2009 08:42:47 -0400
One of the challenges of developing the AndCooper build tool of Android application development is the IDE and ANT interactions. For example, lets asy you have a typical build system based on ANT. How many of those ant taskdef libraries do you have to put in your IDE ant path setting?
If you guess all of them you would be somewhat wrong and would have a build that at would not work as expected. In the AndCooper case its 12 including the ant taskdef libraries from the Android SDK. The whole idea is once AndCooper is installed you can point your IDE java builder setting to use the AndCooper set of build scripts as the java builder for that project so as you develop code the IDE will use AndCooper to build the project in increments and generate soem code analysis data reports to assist in the development process.
Thus, its vital that I get which ant taskdef libraries to put on the IDE ant path correct so the user of AndCooper can jump right into developing code with AndCooper. The lucky part is that each IDE seems to accept that you must load the same subset of taskdef libraries on the IDE ant classpath.
Thu, 28 May 2009 08:01:08 -0400
The strongest reasons for going beyond the Google ADT plugins to a full build system is in this little benchmark from the Dalvik VM on Java Project:
P905i (500MHz - UniPhier 4M + JBlend)
Google Dev Phone 1 (528MHz - MSM7201A)
P905i (Java Dalvik VM on JBlend)
For those that have not read benchmarks before the higher the number the faster the speed. Notice not only the slower speed but also that there are no outliners in the Dalvik on Android benchmark data. That means that Dalvik VM has optimized duplicate transfer instructions when converting from stack based to register based. Thus a large part of the old J2ME optimization strategies that were base dupon eliminating transfer instructions by changing code structure will not work.
Thus, we need ways to collect certain data about the code so that we can determine some new optimization strategies because the Dalvik platform-independent JIT is still far off at this moment. Well, unless there is an announcement today that I do not know about. Thus it is one of the main drives for the AndCooper project.
Tue, 26 May 2009 17:31:02 -0400
Okay lets drive some people really freaking nuts including Motorola. The Android Hacker Quiz:
1. True or False. To get accurate profile data from the emulator or ADP you must run it in debug mode. Answer: False, under debug the emulator and or device runs a slower verifier. Thus, to get profile data you change a certain file to lengthen the number of times the traces.txt file is rolled over(default is 4 and that is not enough as logcat is written to screen or file in 64k chunks) and change stdio to output to the traces.txt file to get full logcat in those files. Reboot the device and grab those sets of traces.txt files.
2 The Dalvik verfier an be toggled on the emulator and the chocies are fast, portable, and debug. When testing for a new device that you do not have which verifier is more accurate or closer to actual device performance? Answer: Portable as the fast Dalvik verifier is optimized for current hardware not the future device you are attempting to get profiling data. While choosing the portable verifier will result in worse performance numbers when compared to fast it will be closer to the actual device until you have more accurate performance data.
See all the new stuff that is being exposed to building a new build system such as AndCooper?
Tue, 26 May 2009 10:51:04 -0400
Issue 965 in the Android Bug DB indicates at the end in comments a Proguard setting that you should be using when including 3rd party jars and obfuscating with Proguard for Android applications. For this to work you need Proguad 4.4 beta and you switch off peephole optimizations in the Proguard configuration paramters. If a 3rd party jar is obfuscated using an obfuscator with peephole optimization it will fail in Android DVM.
From SDK 1.0 forward we have not been able to use obfuscation because we did not have a no peephole switch on obfuscators to deal with the difference in bytecode verifiers between JVMs and the DVM, now we do. Proguard however has had the feature turned off from version 4 to about 4.3 due to conflicts with other JVMs(has had the optimization, ie pephole tuned off not the swtich itself). Its just one of the many details I have had to go through and anlayze so that the AndCooper build tool has some effectiveness for developers.
Once agian to use obfuscation and otimizers with Android 1.0 through Andorid 1.5 you should be using Proguard 4.4. beta and turn off peephole optimizations. or any previous version as the peephole optimization is not enabled in versions prior to 4.4, ie version 4.0 through version 4.3.
Tue, 26 May 2009 06:32:33 -0400
Recently there has been talk about Android on Netbooks. One of the reasosn why I am being so particular on the release of AndCooper Android Applicatiosn Build system is that is has to support multiple development modes in java development such as possibly google gears and etc. let me explain.
Microsoft's apporach to netbooks has been oh lets run native applications on the mobiel OS and mobiel processor. That is not the Android strategy. The Android strategy is cloud based or in other words java appplications plus hybrid java applications where the cloud is accessed via google gears or etc Even in not connected mode its access the stuff google gears downloaded so thatyo can access and cahgne fo example google docs.
A hybrid mobile application say a RIA with offline access such as the Google Gears does nto nee dthe same real heavy requirement sthat a Mcirosoft Office desktop application has and thus is perfect for the netBook model where the netbook is subsidized by mobile operators that want cusotmers to have mobile broadband.
However, Google Gears in non webView Andorid application is not the only use case. How about those webview applications? Well, yes webvie acces to Google Gears is turned off, however have you considered the power of the GWT compiler? View this talk, you can use GWT compiler as the css/js code optimizer for webview applications.
The reason Motorola and other OEMs have not seen this yet, is because I have been quite about it as I needed a build tool developed in a certain way to provide the code analysis hooks so that I could develop two webview demos one withoutusing GWT and one using GWT to demo its full glory. Because one cannot predict what changes in workflow will provide the next agile methods for hybrid webview webkit Android applications the AndCooper while it has a focus on webview applications has a deeper code analysis basis os that its flexible enough that you could use it to prove the valeu of a new dev approach as you would have the statistics through code analaysis and etc to prove the new approach.
I wonder what happens when the OEMs figure out that Android WebView applications can be optimized using the GWT compiler?
Mon, 25 May 2009 08:28:52 -0400
As I finish the first alpha version of AndCooper Android application Build System its features are:
-Code analysis reports collated together by the qalab framework
-Support for compiling Android jar librariers with same build framework
-Code obfuscation and optimization support by integrating with the proguard framework
Sun, 24 May 2009 21:04:28 -0400A few days before Google I/O and what should appear? Android devices coming to AT and T , Verizon, and Sprint in 2009. Its about to get interesting for iPhone, competition.
Sat, 23 May 2009 18:14:01 -0400
Basically, the whole idea of the AndCooper Android Java Application Build System Tool has been that you would pace this tool in your project folder and because you can point your IDE to use the build script as the java builder you would right away automatically have a somewhat automatic continous build tool setup that would generate code analysis reprots that than could be used as feedbackas you code.
Because the developer would have access to the analysis in a feedback loop code quality improves, Android Application stability improves and thus has a direct measurable improvement in user happiness and etc. The difficulty is not in trying out such things as Xradar, Sonar, or Qalabs to see which one would fit as the one to merge all the coe analysis reports into a resonable hub of reports but getting feedback from stakeholders.
Without direct feedback from some stakeholders in the OEM community I have had to guess which implementation decisions needed to be made and guess at how to make it flexible enough to satisfy all stakeholders from the one-person development shop up to the level of the OEM shop that is developing applications to be pre-packed on the Android device.
Fri, 22 May 2009 10:14:16 -0400A Mozilla recruiter contacted me and wants to interview me for a Java/XML front end dev position on the Fennec team. It should be an interesting conversation.
Wed, 20 May 2009 14:50:30 -0400
I am finishing up the build rules for AndCooper over the next two days. Since some basic tasks such as compile and etc indirectly integrate with the reports task will be working on the reports build rules and tsk on Thursday.
Feels somewhat wierd putting in logic to support Android Sdk 2.0, 2.5, 3.0, 3.5, and 4.0 versions. But that is how fast things are moving.
Wed, 20 May 2009 03:16:40 -0400
Something very interesting. Some of us have been exposed to virtual labs such as in j2me where you able to test using unit tests, mock objects, and etc across devices. Usually, you have to learn a new API and etc.
Because of the way the unit testing framework, mock objects, and etc was incorporated into Android OS you can get the power of the Virtual Labs concept by just writing the build system of scripts in a specific way. Yes, AndCooper Build System scripts is being written that way.
I wonder how many Android OS device OEMs such as Motorola have picked that up as its somewhat non obvious on the application development side.
Tue, 19 May 2009 04:12:23 -0400
OEMs face some very particular challenges with Android. A particular set of challenges is community related. Let me explain.
If you peruse reports from Android Device consumers and users you see some patterns in that there are problems reported that are directly attributed to code quality and using the qa code metircs feedback loop in an agile way. Although Goolge and OHA have worked hard on he Eclipse ADT plugin set of tools, ADT is not to the point where you have a click through to qa code metrics yet with easy access for Android application developers.
Thus with the first X-mas season with 8 million Android devices in consumer hands looming we need a stop-gap tool that allows Android application developers easy access to those qa code metrics loops os that application code quality changes in order to reflect device and OS stability. Part of the reasoning for starting AndCooper Android Build System project is that I saw the need for OEMs to lead this charge towards developer easy accessible qa code metrics to improve application stability.
That renewed focus on application stability than has some direct effects on the impression of Android OS stability among OEM clients. I really believe that Motorola could lead that set of challenges. The question is how do you convince an OEM that they should lead in this manner? An intersting challenge, certainly.
Mon, 18 May 2009 07:14:37 -0400
It seems with new reports of MIDs based on Andoroid this summer that Android OS 2.0 has flash support. the meaning is actually a bit more subtle. Performance wise and other wise you will not see Adobe AIR applications on Android devices as of yet and you will not see Adobe AIR applications on Android until w3c web widgets are supported probably. However, video applications through flash get a huge boost.
That means one type or class of applications, Mobile RIA as in WebView, will become default replacement for Adobe AIR like applications on Android. That requires more qa code metrics in the development environment than the current ADT Eclipse plugin provides. For these reasons I am pushing out the AndCooper build system at this time. The first stable release is this week.
Sat, 16 May 2009 09:17:45 -0400
With increasing daily interest from RIM, SonyEricsson, Nokia, and Motorola I probably should layout my thesis for the need for the AndCooper Android Java Applications Build System. At some point the complexitiy of Java SE on mobile and the need for more feedback loops among team members presents the need for a more powerfull build system.
The challenge is finding a way to limit the build script changes in such a way that you have a powerfull workflow system in which you can change the workflow by project without breaking the complex build system scripts. In this way AndCooper becomes your build system engineer without the expense of actually having such a person on the development team.
How do we do this? No matter what point you are in Android Java Application development you are still producing an artifact. If it is a qa test report, the compile task and or debug tasks are still executed. Thus, our workflow system could be based upon those artifacts. For example, I could use the antlion project's artifact definition to define the build system entry-point-tasks into something like apk-production, apk-debug-emulator, apk-debug-adp-device, jar-build-lib and etc.
Than it becomes somewhat easier to change workflow as you only have to change the artifact file. Of course there are some other little tricks.
For example, you can map a copy of the logcat output to the traces.txt file. Why do that? Remember, the profiling commands only trigger a buffer output of 64k at a time. Thus, if we take advantage of knowing that the traces.txt file is rotated and go in and change some files to allow the stdio output mapping to automatically happen and for the traces.txt file to be roated at a higher number than 4 than we can match up the graphical display of that traces.txt information with our log statement information which eliminates the need for a Fiel Appender on the log framework side.
Thus, we not only have an apk artifact in the workflow to process, we also have that traces.txt set of files as artifacts to process. And its sub-artifact in that the entry-point-artifact as far as the beginning AndCooper build task would be apk-debug-emulator or apk-debug-adp task.
Some other tricks are to have the individual reports qa tasks run only if something is there and use something like the qalab framework as the hub to amass the reports together into one comprehensive report-hub package of information.
Its kind of fun building the AndCooper tool.
Fri, 15 May 2009 07:48:24 -0400Want Log4j syntax on Android for logger statements? I found the MicroLog4Andorid stuff at this link. You will still have to download MicroLogger source as you need the core package imports. What it gives you is some Log4j syntax in your logger stuff and a file appender so that you can get file logs.
Thu, 14 May 2009 11:45:43 -0400Okay, here is what is known about Android 2.0 aka Donut. Supports WVGA and QVGA and coming sometime between now and q4th 2009. The Android 2.0 SDK also coming sometime between now and q4th 2009.
Wed, 13 May 2009 09:21:16 -0400The AndCooper Build System for Android Java Applications project site is up. It will look better when I have the support and set up pages and the first release up in the next few days.
Tue, 12 May 2009 06:35:11 -0400
A new Build System Tool for the Androdi Community for developing Android Applications is being developer with the first production ready version being released 6 days from today. Its called AndCooper with a slight dedication to that first Mobile Cellar call placed by Martin Cooper several decades ago.
-Code quality and analysis reports merged into one standardized report view.
-Web dashboard to view reports
-Use your favorite IDE
-ASF 2 License
-In Apache Ant form
-proper calling of emulator using the new AVDs
-instrument testing including emma hooks
Should be interesting.
Mon, 11 May 2009 07:57:24 -0400ADT 0.9.1 is out with a new UI wizard to create AVDs called AVD Manager and that is reachable once you update your plugins from the windows menu.
Fri, 8 May 2009 07:12:42 -0400
If you do some digging into the build and buildrules templates provided with the Android SDK you wil find a an ANT property target in default properties. This is not an AVD target but an API level target. So what can we do with ths neat hook?
It means that I can use this as an API level seelctor to select such items as different PMD rulesets. Neat huh?
Thu, 7 May 2009 06:35:03 -0400
The new Android Application Build Tool is almost finished. over the next few days finishing the main build cycle tasks, the reports tasks, and the reports dash board. I fully expect to put it up at Google Code for the community.
I still have to come up with a project name. The tool is IDE agnostic and thus you will be able to use it no mater if you use Eclipse, NetBeans, XCode, or etc.
Wed, 6 May 2009 03:32:36 -0400I have been looking for a sign of who the new OHA members might be announced at Google I/O in 2009. This post seems to indicate that maybe Verizon might be the surprise at Google I/O.
Tue, 5 May 2009 12:43:29 -0400
As many of you know the Maven versions of Android ANT tools have only been updated for SDK 1.0 and no sign on when they may be updated for SDK 1.5. Android is different in that we have almost full JavaSE on mobile instead of limited j2me. That requries a little more qa and code analysis , reporting, and etc well at least if you want ot move the fast Agile way in development
I found something that may be of use, its called Glean. Basically its a package of ANT scripts that run the code reporting and analysis tools with a nice groovy dashboard. it has a nice way to extend so that I could customize that for Android development. I could re-use my own Android ANT build scripts and use those lessons to extend Glean for Android.
The particular hole I see at the monent is computing code coverage. That will have to wait for a tool that the Android team(Google and OHA) are currently working on as it.
Mon, 4 May 2009 09:48:24 -0400
You know if I was tasked with developing some Android applications that might be included on an OEM handset the first library I would hack up is the MicroLog library. Why? Because it would give two distinct benefits.
You would get theLog4j syntax and features and you would be albe to included Andorid Instrumental testing integration. Hmm lead developer started hacking up MicroLog for Android, maybe I should just take two days and hack it up rest of the way.
Mon, 4 May 2009 05:17:55 -0400Here is a sample Android Build File. I used APIVIZ to generate UML diagrams directly embedded in the javadocs. I also included targts to generate jar library, sign an APK file to be published, and etc. I included a testing target for instrumental testing and a way for the build fiel to get copied to src/tests so that target runs correctly. This build file is to be considered alpah, ie use at yoru own risk although I think I have a lot of the bugs corrected in this alpha form.
Sun, 3 May 2009 00:38:47 -0400
Lately, I have developed a habit on Saturdays to have my browser open to Live Twit to listen to the Gillmor Gang on Saturdays. First my bias in two areas, my idea for a Loopt clone usng WebkitWebview I owe in part to listening to ideas exposed on the GillllMor Gang since last year and my second bias is that I had the displesure of running into Open Social Platform lack of intelligent brain cells in previous deelings with someone from Google within the Open Social Platform group.
Point One, T-Mobile sold 1 million G1 deivces in 6 months which is the exact same period thay Apple took to sell theie2G iPhone devices which means it beat streat expectations. which directly answers the how many G1's were sold without giving ground. Second, how many 2G iPhones did consumers hold onto as the counter point thrown out there by, I think by MA,
Third, Andorid OS is directly related to other Gogoel products through its ease of connecting to cloud APIs and other Google APIs. Wise the F up when you appear on Gillmor gang that you are handed an unique marketing opportunity and bring your effing A Game! the which is better debate is not handled by open versus closed because that is what everyone in 2nd place resorrts to.
However, open does in fact bring more effective user features due to the implementation differences by being open. Its the difference between a clsoed activity stream such as MySpace or facebook and a soemewhat open public activity stream such as twitter. This is not college where you may have splet through summer classes in Calculus due to overbooked classes yet still passed with A- in Calculus due to still doing the class homework and retaking the in-class quizes.
You actually have to care enough to think intelligently about doign some ground prepapration work to bring your A Game. Google bring your effing A Game. Considering that the selling point to developers is that inclusion set of Google Cloud APIs included in the Android SDk and devices it might be wise to finally bring your effing A Game. Okay, rant off.
Sat, 2 May 2009 15:46:31 -0400Some of my Android Knol wiki articles have gained a Top-Viewed-Author-Award. Thanks to all those who have read and have used them thus far.
Fri, 1 May 2009 05:53:04 -0400
Several months ago in several tech conferences the likes of Facebook, MySpace, YouTube, and etc described the rapid growth in mobile web viewing. Now lets clarify this, you pay for that mobiel web service as its not like certain landline services where you have a flat rate for no matter how much you use.
That means now to sell the Android device to the mobile carrier or operator the degree and choices in Mobile Web Sergvice Applications across both consumer and business is now more important in selling that specific device. T-Mobile's data trends in the US indicate for G1 that they experienced a 4-fold increase in data service use and revenue specifically mobile web use and GPS.
That should indicate in the next feew months a rapid demand of those Andorid Developers with both WebKit WebView experience and GPS application experience as each handset OEM such as Motoroal finalizes their Mobile Web Services and LBS Application stacks for their Android devices.
This also implies that we should start seeing significant ramp=up of both Android Developer Groups organized by Geographic location and Android BarCamps this summer. It should be an interesting summer for Android Application Developers.
Thu, 30 Apr 2009 06:53:05 -0400Google is partnering with several groups including Motorola to form local Android Developer groups. The cross postings about this are on the local LUGS mailing lists, If you are in the Chicagoland area the join page is here.
Wed, 29 Apr 2009 11:56:41 -0400
Motorola's first Android devices are coming to ..wait for it..it validates 2 of my predictions..Verizon! According to this BGR post, the device is called Calgary.
So we have Android devices coming to USA $2, USA #3 and USA #4 mobile operators in terms of number of subscribers in q2, q3, and q4 of 2009. It is goinjg to get real interesting.
Tue, 28 Apr 2009 12:41:04 -0400
The issue at hand in finishing my example Android BuildScript is what to do with the AVDs. It seems to me the only time you would need to worry about such issues is in the running of multiple emulators whereas you need to pass the AVD name to the emulator via the emulator start command. I think following the apk-configuraitons and the apk-config-name style might be of use say in an avd_list.properties file.
Also remember that we now run mutliple emulators via the AVDs so its somewhat important and of course everyone wants the ability to test against different SDK versions and hardware setups which can be accomplished by using AVDs. Than of course do an emulator_list.properties usng the same concepts and than a set of multiple emualtor launch/install tasks.
Tue, 28 Apr 2009 04:18:06 -0400DailyDev has released a BiRT ANT task for use with Apache ANT.
Mon, 27 Apr 2009 05:41:32 -0400Here is a Sample Android Apppliation Build file(its extremely alpha, dropbox download link) and the ruleset file I use for is the one detailed by XLV-Labs in this post.Warning, its extremely alpha and use at your own risk and the instrumental tests target is not fully finished.
Sun, 26 Apr 2009 15:32:13 -0400
I should be posting the first version of an Example Android Build Script System tonight. The key items in place is the instrumental testing, checkstyle, pmd, jdepend and some other magic.
Some professional/commerical stuff is coming up so I had to modify some things to get a basic set-up and tools so that I could do this in a more agile way. I will also be posting some utility classes that I have developed by building on others previous explorations. For example, a logger utlity class to better filter LogCat stuff and etc.
As far as the Android articles, some are outlined and I am just waiting on some things to be in-place so that I can put them up and that should happen between now and next weekend. I kept the Android Build simpe in certain ways so that I coudl use it to get a teaching/tutorial article out of it and thus it will not be integrated with Ivy or Maven as of yet.
Fri, 24 Apr 2009 02:10:47 -0400
There has been a lot of rumour and speculation about the next USA Mobile Operator that will deploy Android in 2009. Lets get ready to be surprised.
First, a lot of Mobile Operators in the USA depend upon directed data services, directed in that something like video casting services earns good data revenue due to its direct marketing through partnerships with video media. For example Verizon Wireless has VCast.
How many know that the PacketVideo did the engineering work for the operating system libs/frameworks that enable vcast on multiple mobile operating systems? In 2007 this is why Packet Video becoming an OHA member was such a big delaas OpenCore is the open source framework to make that happen on Android. Being able to do video in Andrioid SDK 1.5 indicates that OpenCore is full support is close to finalization in the Andorid SDK.
While consumer LBS/GPS is still a future 'Apple-on-the-tree' to be plucked as far as amount of revenue for mobile operators mobile video such as Verizon's vcast is here and now data service revenue that is a sellable data service that sells the handsets. Since OpenCore is now finalizing up in the Andorid SDK via both SDK 1.5 and beyond its just a matterr of time for one USA Mobile Operator past T-Mobile to gear up to deploying Android.
A simple search of indeed.com shows that Verizon is hiring poelep with Android skills and knowledge actually listed in the job ads. Spirnt is also hiring at their KS dev center some Android skilled people for their dev program. In other words the Sprint and Verizson announcements are imminent! There are no comperative job ads for AT and T in hiring Android skilled people at AT and T dev centers.
Now which would you rather do believe the un-informed bullshit in that Huff post or actually deal with reality? In other words that bet you placed in Android in becoming an Android developer is about to pay off. Ignore the BS and prepare yourelf to take advantage when the Verizon and Sprint Andorid announcements come this year.
For those that like to follow along I usually post my links to raw data and analysis through my friendfeed account which is now set to post those links to my twitter account. You can find links to both profiles at the right side bar on this blog.
Thu, 23 Apr 2009 15:29:01 -0400
Remember that Android ANT Build Article I promised to write? With more than on SDK release his year including SDK 1.5 you will find times when you need to use an ANT build script to drive such things as the emulator, prepare proejct docs, and etc and thus having an effective Android ANT Build script becomes just as a much welcomed tool as the IDE. I should have it up at AndMob Wiki some time this weekend.
Thu, 23 Apr 2009 01:30:04 -0400
So why did I start Homez(which used to be called Zyle)?
I started HomeZ because I wanted to explore several concepts at once. I wanted to explore other dock uset nterfaces for the home screen. But more importantly I wanted to see how we could incoporate OEM branding into the HomeScreen without hitting the user over the head with it. Obviously in the above example that development screen with the Moto Logo could have some livefolders and what are called aliases on that as shortcuts. This way when the user flings a page they are remided of the brand by the thumbnail popup and would choose that page if needing to update serivces and etc.
We could even make use of that middle bottom panel which wil be a delete zone by putting the OEM logo there.
Wed, 22 Apr 2009 18:26:30 -0400
I have about 25 Android Applications in development. Eight are to a certain state that I will be posting demo videos in the next few days and those eight are:
HomeZ(it used to be called Zyle)
Xspot(Yes the Loopt Clone)
Obviously both the HomeScreen replacement, HomeZ, and the FileManager, ZileZanger, have handset OEM implications. Maybe that is why SonyEricsson is competing with Motorola in reading this site mupliple times daily and an obvious other area as well. Personally, I have a soft spot for Motorola in that for several years I have 'lived' somewhat close to their HQ.
The other 17 Android Applications are in different areas with some being Android Desktop Widgets using the new AppWidget API.
Wed, 22 Apr 2009 12:51:37 -0400Th newest version of PMD and the PMD Eclipse plugin have Android features. Xavier Le Vourch of XLV Labs was nice enough to wrtie up a basic blog post dettailing how to use the new features in PMD for Andrpoid.
Mon, 20 Apr 2009 03:59:11 -0400The home screen replacement that I am developing called Zyle:
is being renamed to HomeZ and I should have some more demo videos this week. From a marketing perspective it made sense to have the name indicate the feature set of the application in some manner. Why the Motorola symbols in it?
Sun, 19 Apr 2009 17:50:29 -0400The libpthread.so thread crash that was fixed in Java6-10 is showing up again. I was using Java6-13 and Eclipse 3.4.2 and everything seem to trigger it on Ubuntu 9.0.4 32-bit. I am not sure if the workaround at the bottom of this old bug report works.