[android-developers] Re: Splintering of the Market
I expect only a very small fraction of apps to actually target specific carriers. Apps that T-Mobile releases in the Market comes to mind, stuff that targets their own customer base and only theirs. On Oct 11, 5:54 am, MrChaz mrchazmob...@googlemail.com wrote: Having just received an e-mail from the Google about up-coming changes to the market I was wondering what other people thought of it. The bit that I don't like the sound of is: First, we have added the ability to target applications by carrier in all countries. For example, if you are showing your app in the United States, you can now choose among Sprint, T-Mobile, and Verizon Wireless. The deliberate splintering of the market by allowing carriers to essentially have own market with their own exclusive apps is a terrible idea in my opinion. It's going to make this confusing and annoying for users who see their friends using software on an identical phone and operating system but are unable to use it themselves. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Streetview Intent Format
The following code snippet works for me: Intent myIntent = new Intent(Intent.ACTION_VIEW, Uri.parse (google.streetview:cbll= + lat + , + lon + cbp=1,180,,0,1.0)); startActivity(myIntent); Note that street views are narrowly draw along streets. On Oct 11, 3:55 pm, ian stilbit...@gmail.com wrote: Has anyone built a Sreetview Intent? I tried the following and don;t see what is wrong: String uriString = google.streetview:cbll=44.640381,-63.575911cbp=1,90,,0,1.0; Uri uri = Uri.parse(uriString); startActivity(new Intent (Intent.ACTION_VIEW, uri)); Anybody have any suggestions or a working snippet? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: First QVGA Android Phone — HTC Tattoo™ — on sale October 2009. Is your applicat ion ready?
First off, thank you for approaching the dev community (I assume to speak for the rest here...) Question (cc to androidsupp...@htc.com, for reference: this is a response to your post in the Android Developers group): After devs exhaust the tools and resources that Donut offers, and access to a physical device is still needed to appropriately test the apps for the different screen sizes (and potentially other behavioral changes outside of that aspect) - does HTC offer a path to such devices outside of having to purchase the devices outright? Example: Augmented Reality apps rely on sensor inputs that DDMS does not seem to support, at least at this point (Outside of that, it's a pain to work with DDMS/emulators to begin with). At the current price point of the average app, it takes a considerable amount of executed sales to recover that potential cost, to a degree that the acquisition of the various devices to perpetuate the app beyond the current set of devices cannot be justified. (Assuming the dev is unwilling to go into the hole on an ongoing basis). On Oct 10, 8:46 am, htcand...@gmail.com htcand...@gmail.com wrote: HTC Corporation is set to launch the HTC Tattoo™ — the first Android phone with QVGA resolution — this month with major European and Asian operators. The QVGA screen has helped make the HTC Tattoo a very affordable offering, while it still maintains HTC Sense and features such as a 3 Megapixel camera, WiFi, GPS and 4-way D-pad navigation to ensure compatibility with your applications and provide an excellent user experience. Because it was designed as an affordable, customizable phone, we expect it will lead many new users to the Android platform and create additional demand for Android Market applications. HTC Tattoo is powered by Android 1.6, also referred to as Donut, in order to support the QVGA resolution. Due to the new Android Market's filtering mechanism, QVGA devices will only see applications which have been recompiled with Donut. We strongly recommend that you recompile your applications with Donut to ensure that it is available to Tattoo and other Donut devices that take advantage of new resolutions on the market. To help you reach your total potential customer base on Android Market, we would like to share our experiences about the porting process. We will be posting FAQs and porting suggestions on our website so that you can leverage what we have learned and get your QVGA compatible applications published quickly and effectively. Furthermore, if you encounter problems not mentioned in our FAQ section, feel free to email us at androidsupp...@htc.com. Our engineering support team will try our best to resolve any porting issues. For HTC – Tattoo QVGA Technical support, visithttp://developer.htc.com/ For more information on HTC Tattoo, visithttp://www.htc.com/www/product/tattoo/overview.html --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: WiMAX for Android
I am only ware of a build wayback, based on the M3-rc37 release. Performance was soso, and I am next to certain that out of the box, Android could not be made run in conjunction with WiMax. It sure would be a nice feat. On Oct 8, 12:42 pm, Michael Cheselka chese...@gmail.com wrote: Hello, I think android does run on the Nokia N810 WiMax edition. I'm not sure if the WiMax works. http://elinux.org/Android_on_OMAP Regards, Michael Cheselka 650-488-4820 On Thu, Oct 8, 2009 at 08:55, JoaJP joachim.pfeif...@gmail.com wrote: One could try to put a Nokia N810 WiMax edition on it. It won't run Android, but would be infinitely more interesting than a notebook PC, for sure. On Oct 8, 8:14 am, Marco Nelissen marc...@android.com wrote: You also need a phone that can act as a USB host. On Wed, Oct 7, 2009 at 6:11 PM, Roman ( T-Mobile USA) roman.baumgaert...@t-mobile.com wrote: Yep, you would have to implement the usb driver support for your WiMax card on Android which also includes platform/framework changes to recognize WiMax as a data interface. -- Roman Baumgaertner Sr. SW Engineer-OSDC ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Oct 7, 2:50 pm, Bala california.b...@gmail.com wrote: I am submitting this post from the Palo Alto Cal-train station, using Clearwire WiMax Innovation Network in Silicon Valley. The speed is unbelievable. Perhaps it is because the network is open only for the developers. If this kind of connectivity and speed is available to the public, then it will be awesome. Instead of the PC, can I use Android phone to access this network. I can connect the WiMAX modem through the USB on my phone. But I may need the WiMAX system software. Any help will be highly appreciated. Thanks, Bala --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Does StreetView work in Android?
Streetview's there, you have to call it as an Activity from within your app. You can find the intents list of Google's apps here, as published, anyway: http://developer.android.com/guide/appendix/g-app-intents.html This means you can't put an overlay on top of it, so it might not get you where you want in the first place. For Augmented Reality, you have to capture a Camera preview; there's a sample app that comes with the SDK that demonstrates that. There used to be a bug in it, though. I didn't check whether that's been fixed with the release of 1.6. If you dig some in this board, you can find the corrected code. On Oct 9, 5:41 pm, ian stilbit...@gmail.com wrote: Hi gang: StreetView just released for Canada this week. I am interested in using it to augment one of my apps set in downtown Montreal. Now the mapview method called something like setStreetView(true) does highlight the streets where streetview imagery is available, but that seems to be all it does. I don't believe that phones run Flash which seems to be a necessity for using Streetview. Am I missing something? That is, is there any way I can zoom into a Streetview image in one of my location-based Android apps just by providing the lat/long? If this isn't already available. I'm sure it is coming soon --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: WiMAX for Android
One could try to put a Nokia N810 WiMax edition on it. It won't run Android, but would be infinitely more interesting than a notebook PC, for sure. On Oct 8, 8:14 am, Marco Nelissen marc...@android.com wrote: You also need a phone that can act as a USB host. On Wed, Oct 7, 2009 at 6:11 PM, Roman ( T-Mobile USA) roman.baumgaert...@t-mobile.com wrote: Yep, you would have to implement the usb driver support for your WiMax card on Android which also includes platform/framework changes to recognize WiMax as a data interface. -- Roman Baumgaertner Sr. SW Engineer-OSDC ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Oct 7, 2:50 pm, Bala california.b...@gmail.com wrote: I am submitting this post from the Palo Alto Cal-train station, using Clearwire WiMax Innovation Network in Silicon Valley. The speed is unbelievable. Perhaps it is because the network is open only for the developers. If this kind of connectivity and speed is available to the public, then it will be awesome. Instead of the PC, can I use Android phone to access this network. I can connect the WiMAX modem through the USB on my phone. But I may need the WiMAX system software. Any help will be highly appreciated. Thanks, Bala --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: sdk 1.6 issues
I've spent a good evening or so to get my code in shape for 1.5. You should find the relevant changes in the release notes, although if I remember correctly I had to work through some issues that were not included in the release documentation. BTW, release notes here: http://developer.android.com/sdk/RELEASENOTES.html I also moved off of some deprecated stuff while at it, which did wonders to the responsiveness to accelerator readings. That was wayback when 1.5 came out. I believe the advise here is that you need to stay on the ball an follow the SDK releases more closely. On Oct 4, 4:38 pm, Hyperjetta hyperje...@gmail.com wrote: How do I go about fixing this issue? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Samsung Galaxy isn´t workin g after update - whole system error!!!
Hi Nox - I believe this is not right forum for this type of support question. Is this the Samsung PC Studio? If that's the case, it appears Samsung should be the right people to turn to. On Oct 3, 10:25 am, Nox v.beh...@googlemail.com wrote: Please help me On 3 Okt., 18:26, Nox v.beh...@googlemail.com wrote: Hi everybody, A few minutes ago I have updated my Samsung Galaxy with the New PC Studio for Germany (not Android 1.6!!!). After that, my mobile restarted and now the whole system isn´t working. There always appers an error message that process com.android.phone has stopped unexpectedly. Normaly( when I bought this phone ) I was able to tap to Wait, but now there is no way to do it. Now I can only tap to close but then it cuttes all my conections. This wouldn´t be the problem if it appeared only one time, but THE ERROR MESSAGE APPEARS EVERY 5 SECONDS!!! Do you know what to do now??? Will the problem be fixed with Android 1.6, which (I hope) will appear in Germany the next days??? Thanks in advance Viktor On 3 Okt., 18:25, Nox v.beh...@googlemail.com wrote: Hi everybody, A few minutes ago I have updated my Samsung Galaxy with the New PC Studio for Germany (not Android 1.6!!!). After that, my mobile restarted and now the whole system isn´t working. There always appers an error message that process com.android.phone has stopped unexpectedly. Normaly( when I bought this phone ) I was able to tap to Wait, but now there is no way to do it. Now I can only tap to close but then it cuttes all my conections. This wouldn´t be the problem if it appeared only one time, but THE ERROR MESSAGE APPEARS EVERY 5 SECONDS!!! Do you know what to do now??? Will the problem be fixed with Android 1.6, which (I hope) will appear in Germany the next days??? Thanks in advance Viktor --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Android 1.6 SDK is here!
I have a question re: the emulator. In order to test forward compatibility, I fired up the emulator that comes with the 1.6 SDK, but the firmware version shows 1.5 and the build is 1.5/Cupcake (looked up in Settings/About phone). Is this the expected behavior, and what can I get out of this to test forward compatibility of an 1.5- released app (I suspect, nothing)? On Sep 15, 3:22 pm, Xavier Ducrohet x...@android.com wrote: http://android-developers.blogspot.com/2009/09/android-16-sdk-is-here... Enjoy! -- Xavier Ducrohet Android Developer Tools Engineer Google Inc. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Android 1.6 SDK is here!
Uhm, thank you, I wasn't. I assumed $ android create would automatically go for 1.6. Problem solved. On Oct 3, 10:00 pm, Xavier Ducrohet x...@android.com wrote: Are you sure the AVD you're launching was created with the 1.6 target? Xav On Sat, Oct 3, 2009 at 9:57 PM, JoaJP joachim.pfeif...@gmail.com wrote: I have a question re: the emulator. In order to test forward compatibility, I fired up the emulator that comes with the 1.6 SDK, but the firmware version shows 1.5 and the build is 1.5/Cupcake (looked up in Settings/About phone). Is this the expected behavior, and what can I get out of this to test forward compatibility of an 1.5- released app (I suspect, nothing)? On Sep 15, 3:22 pm, Xavier Ducrohet x...@android.com wrote: http://android-developers.blogspot.com/2009/09/android-16-sdk-is-here... Enjoy! -- Xavier Ducrohet Android Developer Tools Engineer Google Inc. -- Xavier Ducrohet Android SDK Tech Lead Google Inc. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Educating users - this isn't an iphone!
Looks to me as if you gravitate towards the worst of both worlds. If you look at Android's differentiators you will find that you can build your player to keep it running in the background. In the eyes of the iPhone enthusiast, that alone should be enough to put your product on its own two feet... if you mention it in a diplomatic way. On Oct 1, 8:40 pm, niko20 nikolatesl...@yahoo.com wrote: I have a music app for android that works really well, and I've tried to model the app after other iphone music apps that I have seen. However, the problem is that I get emails from users about can it do like this app on the iphone, so then I try to write them an email back saying, yes, I'm trying to use some of those iphone apps as models, but this phone is not going to be able to do as powerful of an app as the iphone. For example, only 16MB heap space, and also limited CPU speed due to the interpreted java (not THAT slow, but still slow for real time audio stuff with lots of data). Also there are some features that users seem to want that are simply impossible, such as music apps with multitouch. Well the phone doesn't support/expose that to development, so that can never be done right now. How can we as devs help to educate the user base in some way so they realize that this phone isn't an iphone, but has other features that are still beneficial? (Other than emailing them about it) The worst thing is getting a rating/comment that says wish it did like app XXX on the iphone...lol well sorry but that really can't happen, not enough CPU/memory... Of course I also realize that we probably just have to put up with the comparisons, just the way it goes :) Everybody is going to compare it to the iphone. -niko --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Android as a virtual PBX
Oh yeah Asterisk. I spent a few hours last year to build Asterisk for ARM. On a Nokia N810, which runs proper Linux (Maemo), it ran right out of the box, without any compromise. I am sure you can figure what's on my holiday wish list. It'll be interesting to see how that plays out on a carrier network. It's two, three years already that orange kicked out a handful of MVNO's that sold SIP/RTP services on orange's UMTS network, so it might actually work decent enough. Personally, I've tried SIP/RTP on a UMTS network some three years ago, and with limited testing only, I found pretty heavy latency. Roman - in TCP/IP terms Asterisk isn't a server, it connects to VoIP providers like a SIP client. AFAIK NAT traversal is an issue only in a few special cases. Using a provider that supports IAX2 should help, too. Meanwhile at the ranch... From what I've seen, SipDroid isn't, to put it mildly, up to snuff. As much as I would like to tackle such a project, there's no solid case to commit resources to develop a SIP client, considering how Google keeps coming out with their own apps and telco solutions. On Sep 23, 7:17 pm, Chris Stratton cs07...@gmail.com wrote: On Sep 23, 6:18 am, Masoom Alam masoom.a...@gmail.com wrote: Can Android be used as Virtual PBX. This means that, it can work as a virtual attendant for playing specific music files, call fowarding, recording messages. SipDroid is already available but it is just a client soft phone. Not really clear if you mean android in the sense of currently available phone hardware running it, or in the sense of the software platform itself. If the former, then provided that you mean wifi and not 3g then its probably doable, though you might find it easier to just run asterisk on the hardware without android. Doing it seriously via 3g is probably not worthwhile. And bridging between voip and the cellular voice channel is not supported on any of the current phones (no access to in-call audio from the linux side). If you mean the software platform on some other hardware (beagle board?), maybe as a gui front end to configure something like asterisk, that could be interesting... probably more a topic for the android-porting list though. You do know about asterisk embedded linux pbx, right? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Android should provide remote database access for applications...
Naturally, you've got the right idea - and the elements are (almost) in place today. There's probably more legwork needed than a nicely wrapped framework would require, and there's a security concern that you need to cover yourself. What can be done today: - On the server side, you can use AppEngine to build a RESTful web server with a database back end. Authentication through Google Accounts. Bonus for using AppEngine: The user authentication is encrypted (SSL), right out of the box. - The aforementioned user authentication is integrated in the user facing part of the web server that you build. After logging on, it allows the user to check and manage his or her stored data - On the client side, use GET and POST methods to query the server (could be SOAP or something else, of course), based on the protocol that you implement. Most likely candidate is a XML-based protocol, I suppose. Where it's getting shaky as of today: The part where you access the implicit user authentication on the device. This is not covered by the Android SDK, and the solution currently is through a framework JAR that you download independent from the SDK. - At any rate, to comfort both users and dev, you do not gain or need access to user passwords, neither on the client, nor on the server side. - The downside as mentioned above, is the lacking formal integration of user account lookups in the SDK. As an added challenge, the user's gmail ID needs to directly travel along with every GET and POST call from the client side, or initially at least, if the protocol you implement has some form of session management. This is needed in order to allow the selection of the user's data in the backend database. The onus of encrypting the user's identifying information as part of your protocol is on you! JP On Sep 19, 2:48 pm, Moto medicalsou...@gmail.com wrote: The idea is to allow developers to access a remote database provided by google. In android the developer will need a special permission to be set at the manifest file. This could allow applications to keep a backup of users application data without having to sign in ever, seamless. Users could than sign-in to their gmail and see a list of applications that are currently storing data on their gmail space... The user could be allowed to wipe the data or even block the application from storing data to it... This idea make the most sense since Android will be a platform were users will be constantly changing android phones as new better ones come out... Well you get the idea... So what you think? GOOGLE you too! :) -Moto! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Emulator won't finish booting...
In my experience (all the way from m3), the emulator isn't quite as stable as one would expect... although it's improved considerably. Before you go out and buy new equipment, try to delete the emulator's data image. If the emulator doesn't find it, it creates a fresh one, so all you really lose is database and preferences data. Since 1.5 it's two files, userdata-qemu.img and cache.img They are tucked away somewhere in your home directory, see if you can find.android/avd/avd name.avd (that's the XP directory layout) On Sep 16, 6:43 am, Timothy Collins wookie...@gmail.com wrote: I'll take that under consideration... That might be a very good point. On Wed, Sep 16, 2009 at 9:40 AM, Mark Murphy mmur...@commonsware.comwrote: furby wrote: I actually am starting it using Eclipse... Really, just running the project. (I have to admit, I am rather new at Android development). I created an AVD earlier (While I was attempting to use Netbeans to develop Android apps - it didn't work out very well)... I am just wondering - how can it work one day and then the next day suddenly stop? Depending on the speed of your PC and other things that are going on at the time, the Android emulator may get hung up at the graphical Android logo. I am not aware of a workaround other than to improve system performance, either through hardware (e.g., more RAM) or software (e.g., less stuff running). -- Mark Murphy (a Commons Guy) http://commonsware.com|http://twitter.com/commonsguy Android Training in Germany, 18-22 January 2010:http://bignerdranch.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Hmm... at last ADC2 is out of our way ... tell about your app and experience
Not taking away from app functionality or presentation... inside vehicles you'll probably find that the earth magnetic field is disturbed to a degree that the compass readings are off for about any combination of device and vehicle. The ongoing proliferation of vehicles with electric propulsion systems, at least here in the Bay Area... won't make things easier going forward. Good luck though. JP On Sep 12, 9:02 am, Miles milesco...@gmail.com wrote: It's probably about time we introduced our app to the world, here goes... Application: AugSatNav Category: Travel Description: AugSatNav is the world’s first “true” augmented reality application to overlay navigation information directly upon a live video feed of the road ahead. Extended description and screenshots are available at our website:http://www.phyora.com/ Please excuse the reflections on the screen of my HTC Hero (its very hard taking photos of your screen outside) The app itself works great on foot, the compass in our HTC Hero suffers from interference when used inside a vehicle. It was a challenging app to build but I think it has the wow factor we were going for! As with most other devs, we have made significant improvements since the deadline; ultimately though, the app still works as intended. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: XML parser
Let me take exception to the concept... For large scale XML work (in the mobile environment, I qualify 1000+ lines as that), you should consider setting up a web server for the heavy lifting. Not only does that allow you to rely on established parsers, but CPU time is not nearly an issue as it is on the mobile side. As an added bonus, it opens up a dimension for data sharing between users. To query the server, use a lightweight protocol that's flat that can be parsed out with straight SAX. Could be JSON. That's what I do, anyway. On Sep 10, 3:04 am, sasi kumar sasikumar.it1...@gmail.com wrote: Hi guys, I have a doubt in xml parsing. i'm parsing a xml file. that xml file contains more than 14000 lines. I'm fetching 15 tag in that xml file. it is taking more than 7 times to fetch. b'coz 14000 lines * 15 tag. that much time it is taking. can any one suggess any idea for this to reduce time. or give some other coding to fetch xml data easily. no i'm using rssreader to fetch data as like in java. thanks in advance. -- Thanks Regards Sasi Kumar.S --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: AVD for Motorola Cliq?
Eric, I hope to suggest that the design of Motorola's products will be reaching towards a standard that does not require the dev community's familiarization with Motorola products to a level of detail that starts to shine through here. This actually applies to all device makers. HTC has been supplying the dev devices so far, so to me, that's the standard at this point. They've taken the plunge first, accommodated the limited production runs of dev devices, so now they deserve the privilege of taking the wheel. Assuming there's a series of quirks associated with Motorola's products, I'll make a prediction that hardly any dev will make the effort, or be in a position to effectively develop towards Moto devices in the first place. In other words, it just ain't going to happen, all the while the units move into the hands of expecting users that'll get bounced around between Google, devs and the device maker. Once we start seeing disclaimers in the already cramped Market app descriptions, to the effect: Tested on device X (good luck otherwise), we'll know we're at the point where noone wins. JP On Sep 11, 11:05 am, er...@motorola.com er...@motorola.com wrote: [I could've sworn I pressed send and yet my reply hasn't shown up. I'll try to paraphrase. I'm sure as soon as I press send this time, the original will show up. ;-) ] Mark, et. al., There is an SDK add-on for the Cliq under the MOTODEV AAP that is based on an older system build and had some issues with supporting the ALT keys. It's using the code name for the device, which is no secret. The issues have been fixed and a recent system image is in a newer package that we reviewed and approved last week. The file name uses the model number (MB200), which should work for either Cliq or DEXT. It may not have been pushed to the MOTODEV site with all the changes they were doing yesterday for the announcement. I don't know if it will be in the public MOTODEV area or still in the AAP. I'll follow- up on that. Mark, I don't think there was any intent to use published applications as a gating criteria for acceptance to the program. I'll pass your concerns on to the people who run the program. -E On Sep 11, 12:29 pm, Mark Murphy mmur...@commonsware.com wrote: Buzz Android wrote: There is an AVD. Access to it has been one of the benefits of the MOTODEV App Accelerator Program. Ah, that would explain matters. One of the annoyances of the App Accelerator Program is it expects me to lie on the application form to gain access (What is the name of your mobile application?), and therefore I haven't joined. I think we all knew that at some point there would be devices that didn't follow the same design model of the current devices. I worry about those who don't fit in the we all knew bucket, as I am sure there are some. That's part of the reason why we need to get the word out about what specific things developers need to consider for maximum compatibility. We'll go through the same thing once the first non-HVGA device (or ready-for-prime-time AVD) hits the streets (e.g., HTC Tattoo). Thanks for the info! -- Mark Murphy (a Commons Guy)http://commonsware.com|http://twitter.com/commonsguy Android 1.5 Programming Books:http://commonsware.com/books.html --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
