[android-developers] Re: Android SDK and Helios - compatibility problems?
You can make a separate workspace to test if that is a factor in the problem you are experiencing. On Jul 14, 11:14 pm, SChaser crotalistig...@gmail.com wrote: I have experienced the same problems. Deleting the workspace is not an option. Is there a way to reset it? I'd hate to have to back up an eclipse version just for this. On Jun 28, 12:44 pm, Xavier Ducrohet x...@android.com wrote: The Android plug-ins are compatible with Eclispe 3.6 Make sure you had Contact all update sites during install to find required software checked in when you installed them. I would delete the workspace (or try with a different one) to see if that helps. On Sun, Jun 27, 2010 at 8:04 PM, SChaser crotalistig...@gmail.com wrote: Are folks having success withHelios(Eclipse 3.6) and the latest SDK (r_06)? I am havingproblemsgetting the Eclipse DDMS to work;. It is missing most of its views (such as logcat) and complained about that the first time I ran it (but not since, so I don't have a list of what is going on. I had a previous working version with a prior Eclipse, but started from scratch with this one. The steps were: *Download and install (via unzip)Helios *Download and unzip files for SDK *Run SDK setup and download everything it would download. **It complained that some packages available were incompatible and it wouldn't download (or list) them *Install the Eclipse plug-in fromhttps://dl-ssl.google.com/android/eclipse/ using the Eclipse new software dialog IsHeliosincompatible? Or am I doing something wrong? Thanks -- 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 -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- 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: Problems installing Eclipse with Android.
Does your question 1 refer to the step in installation where you use the AVD and SDK Manager to install build target packages? If so, you can choose to install all of them without using up too much space on a big machine. If you install all of the build targets you will be sure to be compatible with example code that is set up for various API levels. A null pointer exception reported in Eclipse that occurs in an Android XML editor usually means the visual editor could not interpret or create the XML correctly. The most common case I see that is attempting to use a layout editor where a View class has been subclassed and the subclass name is used in the layout - the layout editor can't handle that. So I suspect you have encountered something similar. Edit the XML by hand - switch to the xml view using the tabs at the bottom of the editor pane - and make sure that there are no errors in the XML file. On Jun 30, 10:01 am, Albion albio...@gmail.com wrote: I've been following the tutorial at this page...http://www.vogella.de/articles/Android/article.html I had originally sent an e-mail to the author of the tutorial who promptly told me that I shouldn't e-mail him about his tutorial, but should ask this group instead. Below is a copy of the e-mail I sent him, I am hoping someone here can help. -- I am running Windows 7 Business x64 with the latest Microsoft updates. Eclipse Helios Build: 20100617-1415 (IDE for Java Developers), Android SDK r06, Android Developer Tools 0.9.7.v201005071157-36220, Java JDK 6 update 20. All on a Quad core E5345 with 8gig of RAM and lots and lots of hard drive space (space isn't an issue). 1) In Section 2.3 under Select available packages and select the latest version of the SDK. your tutorial tells me to select all of the Android 2.2 packages. What if I only want to code in Android 1.6? Will I also need to get the 1.6 packages? The same for 2.1? 2) In section 4.3 you tell me to open strings.xml under res/values. When I select the resource tab for strings.xml there is nothing listed under Resource Elements, where you say I should see hello (String) and app_name (String). When I try to add an element or do anything else with the elements listed I get an error: An error has occurred. See error log for more details. java.lang.NullPointerException. Even when I select the strings.xml tab next to the resource tab and try to manually change the text, for each character I type I get the same error. Google has turned up nothing for that error on Eclipse with Android. I've tried completely removing and reinstalling Eclipse and Android SDK, making sure I followed your tutorial for both Eclipse install and Android install much much closer. When I got back to the point of section 4.3 I got the same errors. All in all I tried reinstalling both Eclipse and Android SDK 3 times, following your tutorial closer each time, with the same result. Any ideas what I may be doing wrong? I really appreciate the tutorial and your help. Thanks -- -Craig -- 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: AIDL, Binder, ResultReceiver, and Performance
On page 267 of Android Application Development, the AIDL-generated code for APIDemos example is formatted for readbility and dissected, and shows how calls within a process get short-circuited and do not actually use IPC. Amazon doesn't allow posting links into Look Inside previews of books, but searching for aidl and proxy will get you there. On Jun 25, 4:08 pm, Mark Murphy mmur...@commonsware.com wrote: On Fri, Jun 25, 2010 at 3:50 PM, Dianne Hackborn hack...@android.com wrote: AIDL/Binder by design don't have a performance impact when making a call in the same process. This turns into a direct call on to the target's interface implementation. Ah! That's good to know. The big thing this introduces is a whole lot more effort and complexity for the developer, as they now need to deal with AIDL interfaces. At least that's hidden for ResultReceiver, which has the AIDL stuff baked in. If the purpose of this code (and I haven't looked at it to know) is to send a command to the service and get told later when it is done, then this is a reasonable approach. There are some potential edge cases where the result won't be delivered though (if the process is in the background and gets killed and its service restarted), so I would recommend giving it a PendingIntent to deliver a result to the activity rather than an interface to a live object. You can make this with Activity.createPendingResult(). :: scribbles furiously in notebook :: On the other hand, if the purpose of this is to tell the service about the activity running for it to know about and send information back during that time, it is bad because this is not the semantics of startService(). You want to use bindService() for that. Yeah, I haven't fully investigated the app, so I don't know precisely what your team's intentions were when they wrote it. But, this info is fantastic -- many thanks! -- Mark Murphy (a Commons Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 1.6 Available! -- 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: Why is Android so buggy?
Android issue tracking is in the open, so the numbers are available to anyone: There have been a bit over 9000 issues reported. about 600 released (fixed and shipped) and 600 for future release. It's hard to characterize all combinations of issue type and status. For example, there are 8 unreproducible enhancements. There are about 3500 new (not yet reviewed) defects. Issues can be starred so priority in Android issues is democratic. Of the 64 assigned issues, the only ones that have a house on fire number of stars are bugs in the alarm clock. So if your issue isn't getting attention, maybe it's fairly obscure. However there are a couple hundred New issues with a significant number of fans. Plus a couple dozen more highly rated issues that have been reviewed. Again, this is hard to characterize: Are the low-priority assigned issues sitting there waiting for higher priority issues to be cleared? On the whole, the number of high priority unresolved issues looks OK for a system the size of Android, especially with an open and democratic input side for issue tracking. The only qualitative problem I can identify looking at the way the voting system on defects works is that the most user-visible issues get 10X the votes of serious but less visible issues. I think Google's bug reviewers can figure that out. It looks like Google has about 7 people working on bug fixing plus a few other engineers with assigned issues. So it looks like there is no resource imbalance. There might be separate sources of issues, such as OEMs' and carriers' QA processes that might contain issues not visible here, but with the large number of Android users, it is unlikely there is a mass of hidden issues. Based on the available numbers, I don't think you can say Android is very buggy. On Jun 6, 5:25 pm, blahblah...@gmail.com blahblah...@gmail.com wrote: It seems that Android is very buggy compared not only to the iPhone, but to pretty much any other software. It's not just minor bugs either - pretty much every developer will come across many serious bugs. Some examples: - When you run the sdk setup.exe, the very first thing that happens is that it informs you that it can't connect using https, so you have to change the options to use 'http' instead. This appears to be a bug in the .exe rather than any kind of user issue because the https url works fine in the browser and this error seems to affect everyone. Sure, it's trivial to work around (just do a google search and you figure it out in 5 seconds), but the user shouldn't have to do that. It makes it look unprofessional. - When you view a TabWidget in the layout editor it crashes. - Every time you run an app in the emulator, it starts off with the screen locked so you need to press the Menu key. - Various socket bugs (or perhaps all the same bug) related to IOException not happening. Even something as simple as just trying to connect to a remote host that is not listening will cause it to hang instead of immediately returning an error. All of these bugs have been logged for months (some by me, some by other people) with no indication of any fix. At the moment I'm just using the emulator, but I'm wondering if the phones themselves are this buggy or if all the bugs are just in the development environment and emulator. -- 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: Is it possible to draw to a home screen icon?
I should add that you would have to get the launcher to update by broadcasting an intent with the action ACTION_PACKAGE_CHANGED. But that should be a general way to implement what Sense UI does by changing app icons. On Jun 5, 10:42 pm, Zigurd zigurd.medni...@gmail.com wrote: Try Live Wallpapers:http://developer.android.com/resources/articles/live-wallpapers.html App icons are not accessible outside the launcher. At best, you might be able to hack something by turning activity aliases on and off and changing an app icon that way. That is, you might have an second app icon that serves as a kind of notification, for example, and you could turn it on/off, or run through a sequence of icon variations, with PackageManager calls to enable/disable the component names corresponding to the aliases. But there is no way to borrow the Launcher's app icon views and draw into them. -- 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: Is it possible to draw to a home screen icon?
If you can't send ACTION_PACKAGE_CHANGED, how are alternative markets/ installers supposed to work? While it looks like if you sent ACTION_PACKAGE_ADDED the same thing would happen, based on the filter Launcher sets up, that seems less correct. I agree that Sense UI probably has some cooperating mechanism between their launcher and their apps. I was experimenting with activity aliases as a way of turning on and off the ability to launch into multiple different activities in the same app. Is that still kosher? I replied here because it seems that you could use the same technique to change icons. On Jun 6, 2:40 pm, Dianne Hackborn hack...@android.com wrote: On Sun, Jun 6, 2010 at 6:44 AM, Zigurd zigurd.medni...@gmail.com wrote: I should add that you would have to get the launcher to update by broadcasting an intent with the action ACTION_PACKAGE_CHANGED. You should not send this kind of broadcast. In fact in newer platforms you can't. But that should be a general way to implement what Sense UI does by changing app icons. Sense UI probably has some special cases hard-coded in to things. Being able to change app icons is something we'd like to do at some point, but has been a lower priority than many other things. I don't know when it may happen. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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: Is it possible to draw to a home screen icon?
Ow. Yeah, that would not be friendly to shortcuts. And I also see how alternative installers work, too, now that I looked into it. It appears that what I want to do would require an app downloading an update of itself and installing it in order to show a different set of launcher icons, and that's just not worth it to change the look of one icon on the fly. On Jun 6, 9:26 pm, Dianne Hackborn hack...@android.com wrote: On Sun, Jun 6, 2010 at 2:30 PM, Zigurd zigurd.medni...@gmail.com wrote: If you can't send ACTION_PACKAGE_CHANGED, how are alternative markets/ installers supposed to work? While it looks like if you sent ACTION_PACKAGE_ADDED the same thing would happen, based on the filter Launcher sets up, that seems less correct. The system sends these when it installs or otherwise modifies packages. Alternative markets don't get to directly install apps (and at this level, neither does the regular market); they ask the system to, and it does the right thing. I was experimenting with activity aliases as a way of turning on and off the ability to launch into multiple different activities in the same app. Is that still kosher? I replied here because it seems that you could use the same technique to change icons. You could do this, but if the user has made a shortcut to your app this would break it. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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: Is it possible to draw to a home screen icon?
Try Live Wallpapers: http://developer.android.com/resources/articles/live-wallpapers.html App icons are not accessible outside the launcher. At best, you might be able to hack something by turning activity aliases on and off and changing an app icon that way. That is, you might have an second app icon that serves as a kind of notification, for example, and you could turn it on/off, or run through a sequence of icon variations, with PackageManager calls to enable/disable the component names corresponding to the aliases. But there is no way to borrow the Launcher's app icon views and draw into them. -- 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: Why ADB and DDMS cannot recognize my phone in Ubuntu?
You say you have an Acer device. Have you tried the line below?
SUBSYSTEM==usb, ATTR{idVendor}==0502, MODE=0666,
GROUP=plugdev
Note that the ATTR{idVendor}== uses the id for Acer listed on
the dev guide page. My previous example used the ID for Motorola,
which works for my Droid.
Also:
1. Make sure usb debugging is turned on in Android, from the Home
screen, use Option Menu Key - Settings - Applications - Development
- USB Debugging
2. Make sure you have restarted the udev service with the line
service udev restart
Try not to mix in stopping the adb server and restarting it as root.
That makes everything else a red herring, since adb running as root
will have access to your device. However, if you give up and need a
workaround you can use adb server-kill followed by sudo adb server-
strart
Does that improve your results?
On May 31, 5:40 am, Ichi ukas...@gmail.com wrote:
Well, I've tried all the solutions mentioned above, but none of them
work for me...
Is there any one ever tested Acer Liquid on Ubuntu 10.04?
Still thanks for all you guys' help here.
On 5月30日, 下午10時51分, Zigurd zigurd.medni...@gmail.com wrote:
Gubatron's solution works, but necessarily because of the udev rules
file. He also has you restart the adb server as root. That, by itself
will work, but it is a workaround until you can figure out the correct
udev rules for your system.
I have a file named /etc/udev/rules.d/51-android.rules that contains
the line
SUBSYSTEM==usb, ATTR{idVendor}==22b8, MODE=0666, GROUP=plugdev
That works for my Motorola Droid
According to the comments on this Ubuntu
issue:https://bugs.launchpad.net/ubuntu/+source/udev/+bug/316215youshould
not need a udev rule at all if you are running 10.4., but after some
experimentation, this does not seem to be true, at least for my Droid.
Maybe a G1 is recognized automatically now.
On May 30, 8:05 am, Gubatron gubat...@gmail.com wrote:
I wrote a post about this a few days ago
Here it is in case you haven't solved it
yethttp://www.gubatron.com/blog/2010/05/28/solved-eclipse-cant-see-my-an...
On May 27, 12:36 am, Ichi ukas...@gmail.com wrote:
Hi,
I am trying to connect my Acer Liquid with ADB and DDMS under Ubuntu
10.04
I read some posts and already add the VID (0502) and PID(3202) in /etc/
udev/rules.d/51-android.rules,
but adb devices still list my phone's name as question mark
().
When I try DDMS, I got the following error:
E/DDMS: device () request rejected: device not found
Is there something I missed?
--
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: Why ADB and DDMS cannot recognize my phone in Ubuntu?
Gubatron's solution works, but necessarily because of the udev rules
file. He also has you restart the adb server as root. That, by itself
will work, but it is a workaround until you can figure out the correct
udev rules for your system.
I have a file named /etc/udev/rules.d/51-android.rules that contains
the line
SUBSYSTEM==usb, ATTR{idVendor}==22b8, MODE=0666, GROUP=plugdev
That works for my Motorola Droid
According to the comments on this Ubuntu issue:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/316215 you should
not need a udev rule at all if you are running 10.4., but after some
experimentation, this does not seem to be true, at least for my Droid.
Maybe a G1 is recognized automatically now.
On May 30, 8:05 am, Gubatron gubat...@gmail.com wrote:
I wrote a post about this a few days ago
Here it is in case you haven't solved it
yethttp://www.gubatron.com/blog/2010/05/28/solved-eclipse-cant-see-my-an...
On May 27, 12:36 am, Ichi ukas...@gmail.com wrote:
Hi,
I am trying to connect my Acer Liquid with ADB and DDMS under Ubuntu
10.04
I read some posts and already add the VID (0502) and PID(3202) in /etc/
udev/rules.d/51-android.rules,
but adb devices still list my phone's name as question mark
().
When I try DDMS, I got the following error:
E/DDMS: device () request rejected: device not found
Is there something I missed?
--
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: Documentation errors in Developing on a Device?
Yeah, I see that it specifies debugging as part of the goal of setting up. And since running in the emulator is enough to validate that the SDK is set up correctly, I see that consolidating the instructions for running and debugging is a valid decision. I also see that if you specify that Settings is an item on the default Home app menu, that actually makes it simpler to do it that way than to direct the user to the Settings activity. Still, that makes it even more clearly an error that Settings' was dropped from the chain of menu selections to get to that setting. This page is a very concise, but often unclear set of instructions. Lots of beginners get stuck at this point. Another example I found is that restarting the udev server is left out of the instructions for setting up the udev rule for Linux systems. -- 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] Documentation errors in Developing on a Device?
On the documentation page Developing on a Device http://developer.android.com/guide/developing/device.html there may be two errors in the section Setting up a Device for Development. First: To run (not debug) an app on a device, you do not need to set the debuggable attribute in the manifest. The documentation implies this is a requirement. It may be a good idea, but, when stepping an absolute beginner through the process of running their first app, this is an unnecessary detour. Second: The instructions for turning on USB debugging don't mention the Settings activity: On the device, go to the home screen, press MENU, select Applications Development, then enable USB debugging. The first error is more of a quibble, but the second seems to be actual misinformation that may puzzle a beginner, wondering why there isn't an Applications item on the Home app menu. In most cases this should go Settings Applications Development USB Debugging, and the menu key is not involved. Am I misreading something on this documentation page? -- 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: How to warn user when back button is pressed to navigate out of my application?
Maybe an audible cue that they are about to navigate back out? But, as others have said, that navigation should have no bad consequences, so the user need not be aware of it. While a home navigation in the option menu is not desirable, that would be one way to enable your users to return to the top of your application. Give this anchor activity a meaningful name and give the user a menu item so they can get to it from anywhere, if your users really need that. This article http://developer.android.com/guide/practices/ui_guidelines/activity_task_design.html covers how navigation should work. On Apr 27, 3:43 am, Xiongzh zx.zhangxi...@gmail.com wrote: Yes, I have keep in back stack what should in the back stack. But sometimes customers just want to navigate to the activity in the bottom of the stack, i.e, the first view the see, the main view I assume. They are not intent to leave my application. That's why they ask for a confirmation when they leave by back button. On Apr 27, 3:31 pm, patbenatar patbena...@gmail.com wrote: Wait I'm a bit confused... If the user wants to hit the back button to go back to the previous Activity, I'm assuming you're talking about a previous Activity within your app? This functionality is native to Android and should be maintained throughout your app. If you start an activity for result and then finish it, it will be removed from your back stack. If your users complain that the back button does not act natively [going back to the previous Activity], maybe rethink how you pass of from Activity to Activity throughout your app. If this page the user wants to return to is important enough for your users to complain about their inability to return to it, you should keep it in the back stack so they can return to it. Sorry if this is a misunderstanding of your message. -Nick On Apr 27, 12:22 am, Xiongzh zx.zhangxi...@gmail.com wrote: Some of my customers are accustomed to use the back button to go back to the previous activity. Some complained that they often navigate out of the application by pressing back button. I think it would be nice to customers if they can be warned. Thanks for your suggestion. How do think the approach I used? On Apr 27, 2:43 pm, Nicholas Albion nalb...@gmail.com wrote: My first thought was to suggest that you rethink if you really need to do this - maybe your app isn't going to be as important to your users as you may think. But then, I been frustrated in the past by games which exit in the middle of the game if you press too far right... Maybe you should provide an option (which you'd only ever ask once): Always confirm before exiting I can find some posts on how to warn user when the back button is pressed to 'quit' the application. The common answer is to catch the key down event by onKeyDown, or use startActivityForResult(). My approach is to restart the activity in onStop(). Is it a better choice? Please help to check if there's anything inappropriate. -- 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 athttp://groups.google.com/group/android-developers?hl=en -- 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 athttp://groups.google.com/group/android-developers?hl=en -- 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 athttp://groups.google.com/group/android-developers?hl=en -- 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 athttp://groups.google.com/group/android-developers?hl=en -- 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
[android-developers] Re: How many Android phones have touchscreens?
OK, I see the Alessi counter-top Android TV has touch http://www.engadget.com/2010/04/23/alessitab-android-touchscreen-for-fancy-european-kitchens And, yes, I can see that non-touch UI probably needs an update from the AWT-ish original support in Android, if it is to be as good as possible for big TVs and such. On Apr 21, 4:29 pm, Dianne Hackborn hack...@android.com wrote: I can more strongly say that today, to be able to ship an Android compatible phone (and thus have Market), you need to have a touch screen. If/when at some point in the future devices without touch-screens are considered to be Android compatible, appropriate work for existing third party applications will be done, as we have done in the past: either having some kind of compatibility so that they can still run with a decent experience (as was done with the new density support), or applying filtering so that those applications will not be visible to users until specifically updated to support the new kind of device (as was done for example for devices with smaller screens). While making your app work well with a DPAD is nice, I don't recommend developers go out of their way today to try to make a touch-oriented UI work without a touch screen. That time would be better spent on improving the touch experience. On Wed, Apr 21, 2010 at 1:20 PM, Zigurd zigurd.medni...@gmail.com wrote: All current Android phones have touch-screens. However, Android's UI is designed to be operated using the d-pad, moving a focus and using a select button as well as by touch. I think all the standard apps that are part of most Android phones can work without touch. If, for example, you consider an Android in-car system with steering wheel buttons, or an Android TV as possible target platforms, you would want your apps to function without touch, too, and should include non-touch test cases in your test plan. On Apr 21, 6:06 am, Sean Hodges seanhodge...@googlemail.com wrote: If you are a beginner, you should really be posting to the android-beginners list. I believe all of the current Android phones have touch screens. On Wed, Apr 21, 2010 at 10:24 AM, angushir...@googlemail.com angushir...@yahoo.co.uk wrote: Hi all, a simple question from a beginner - how many of Android phones support touchscreen applications? Angus -- 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.comandroid-developers%2Bunsubs cr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- 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.comandroid-developers%2Bunsubs cr...@googlegroups.com For more options, visit this group athttp:// groups.google.com/group/android-developers?hl=en -- 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.comandroid-developers%2Bunsubs cr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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 athttp://groups.google.com/group/android-developers?hl=en -- 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: How many Android phones have touchscreens?
All current Android phones have touch-screens. However, Android's UI is designed to be operated using the d-pad, moving a focus and using a select button as well as by touch. I think all the standard apps that are part of most Android phones can work without touch. If, for example, you consider an Android in-car system with steering wheel buttons, or an Android TV as possible target platforms, you would want your apps to function without touch, too, and should include non-touch test cases in your test plan. On Apr 21, 6:06 am, Sean Hodges seanhodge...@googlemail.com wrote: If you are a beginner, you should really be posting to the android-beginners list. I believe all of the current Android phones have touch screens. On Wed, Apr 21, 2010 at 10:24 AM, angushir...@googlemail.com angushir...@yahoo.co.uk wrote: Hi all, a simple question from a beginner - how many of Android phones support touchscreen applications? Angus -- 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 -- 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 athttp://groups.google.com/group/android-developers?hl=en -- 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.speech.action.RECOGNIZE_SPEECH activity not found
Handle the exception. There is no guarantee that an Intent will get a match, and the situation can change as the user adds and deletes applications. Conceivably, matches could go away in future version of Android, or in a port of Android with very different hardware than a phone. So even if it works in many Android configurations, this is still an exception you should handle. If your application requires an Intent match to work, you should notify the user of the error and then exit your application. -- 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: adb can't list my attached device
colin.t...@gmail.com posted the link to the documentation, above. If, for some reason, that doesn't work on your Linux setup, you can try this, in your tools, directory: ./adb kill-server sudo ./adb start-server Then start Eclipse. -- 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: Passing a LinearLayout from one Activity to another
I'm sure you are starting to see that what you thought of doing was made intentionally difficult. The reason is that, if you do it right, taking the code for an activity and moving it to another application is easy. It's part of Android's modularity. The data you pass using an Intent object, and return using Activity.setResult(int, Intent), enables one Activity to ask another to perform an operation, like cropping an image or editing an audio clip, and return the result. This is meant to work across applications about as readily as it works within an application. The documentation for the Intent class describes the standard actions, categories, etc. you can match to in your intent filters to enable your application to provide functionality to other applications, and how you can use those parameters to find Activity objects in other applications that will do things for you. But this is turning into more of a beginner topic. I thought you might be getting at something else. -- 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: Passing a LinearLayout from one Activity to another
When I wrote I'm sure you are starting to see that what you thought of doing was made intentionally difficult I was referring the fact that when you create an instance of LinearLayout, or any other class in the View hierarchy, you have to specify a Context (an abstract class) in the constructor of the View. The concrete class that is the relevant Context object for your View classes is the Activity. That is, Android was designed not to do what you were thinking of, and to tie all View instances to an existing instance of Activity. So, yes, it is not possible make an instance of View before you make an instance of Activity and associate the two later on, now and likely ever. You can, however, create the specifications for a set of View objects in XML, pass the XML as a String in the Intent, and have the new Activity build its View objects from the specifications. Look at the ViewInflate and XmlPullParser classes. -- 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: Passing a LinearLayout from one Activity to another
Can you clarify what you are trying to do? It's hard to see why you want to do what you are asking about. If you are trying to display the same information, from the same data model, in two identical-looking views in two different activities, you should create a class that extends AdapterView if your data model contains several of the same kind of thing. If the data is all different kinds, use the observer/observable classes in either android.database or java.util to connect two views to the same data using an implementation of the observer pattern. If the views can be in two different apps, use a ContentProvider component. If you want the views to look identical, use the same XML to specify how they look. On Feb 28, 10:36 am, Aniruddh Bajirao abaji...@gmail.com wrote: For a rather crazy reason I am trying to pass a linearLayout from one activity to another. -- 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] onActivityResult called before setResult
I have a program where onActivityResult is being called with the correct request code, and a null Intent parameter, before the the Activity being launched begins. And, when that Activity calls setResult, onActivityResult is not called. This is probably some error indication, but for what? No exception is thrown in the startActivityForResult call. The Activity being started starts correctly, gets all the parameters correctly, runs correctly and calls setResult with the correct results. Both Activity objects are in the same application. --~--~-~--~~~---~--~~ 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: onActivityResult called before setResult
That appears to be the problem. The confusing thing was that singleInstance was set on a different Activity in the same app. Thanks!! --~--~-~--~~~---~--~~ 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: Displaying virtual keyboard in a custom View
I came across your query while I was researching controlling input methods. While I have not yet coded this up myself, from reading the documentation, and from the type used to refer to the instance of EditableInputConnection, it looks like you want the InputConnection interface, which is documented. I'd guess that EditableInputConnection implements that interface. --~--~-~--~~~---~--~~ 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] Ubuntu Jaunty and adb not playing well together
Trying to get an Ubuntu Jaunty system to talk to a dev phone. I have
the 1.5 sdk and the new master branch of the sources.
If I change the udev rules to:
SUBSYSTEM==usb, ATTRS{idVendor}==0bb4, MODE=0666
...I'm able to mount the memory card and read and write to it. But the
command:
adb devices
...shows only the emulator (so adb appears to work with the new sdk),
but not the handset.
Any ideas?
--~--~-~--~~~---~--~~
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: Ubuntu Jaunty and adb not playing well together
There does not appear to be another udev rules file starting with 50
in Ubuntu Jaunty.
I did find a workaround that works: Remove (or comment-out) the udev
rule, and set permissions on adb to run as root. Rebooted, and now
adb devices results in...
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT91RLZ01056device
...I just got this result moments ago, so I have not checked that
everything depending on this functions correctly, but it's progress
relative to where I was.
On Apr 15, 4:03 pm, David Turner di...@android.com wrote:
I believe there is a conflict in latest versions of Ubuntu, try to rename
your 50-android-something
rule file to 51-android-something, because Ubuntu recently added another
50-something file that
appears to be resetting/overriding the definitions here.
Let us know if this works.
On Wed, Apr 15, 2009 at 9:56 PM, Zigurd zigurd.medni...@gmail.com wrote:
Trying to get an Ubuntu Jaunty system to talk to a dev phone. I have
the 1.5 sdk and the new master branch of the sources.
If I change the udev rules to:
SUBSYSTEM==usb, ATTRS{idVendor}==0bb4, MODE=0666
...I'm able to mount the memory card and read and write to it. But the
command:
adb devices
...shows only the emulator (so adb appears to work with the new sdk),
but not the handset.
Any ideas?
--~--~-~--~~~---~--~~
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: Ubuntu Jaunty and adb not playing well together
My not-very-elegant solution indicates this is a permission issue. The udev rule appears to set permissions, so it probably isn't being run. It would be nice to verify the udev rule match, but I'm a udev n00b and can't find what the ATTRS (formerly SYSFS) rule is supposed to match. --~--~-~--~~~---~--~~ 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: How to call RIL?
Some information on telephony internals, PhoneApp, and communications between PhoneApp and the RIL can be found in an upcoming book published by O'Reilly called Android Application Development. It is available on the O'Reilly Roughcuts site in draft form: http://safari.oreilly.com/9780596156220 The chapter on telephony internals is mainly oriented around illustrating what happens within and underneath the TelephonyManager API, using the logging facilities. Although it is targeted to an application developer who needs to go beyond the documentation, it does provide brief explanations of the telephony internals classes and the implementations of those interfaces found in the sources. Maybe that can get you started on a full understanding of the relationship between the telephony UI apps, PhoneApp, and rild. It will, at least, walk you through the steps to observe the traffic between PhoneApp and rild using adb. ZM On Nov 28, 8:53 am, sunil [EMAIL PROTECTED] wrote: Hi Jeff Hamilton, May i know if there is any documentation available which explains about the RIL layer , Telephony Manager layer and the service layer. Regards, Sunil. On Nov 18, 7:35 am, Jeff Hamilton [EMAIL PROTECTED] wrote: Thanks for your reply. But the TelephonyManager doesn't provide enough information for us. We really need to get more informaiton from the RIL layer. What information do you need from the RIL that isn't provided by the TelephonyManager APIs? -Jeff --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
