Re: [android-developers] Why is Android so buggy?
Android is buggy, yes, I totally agree with you. The most buggy release is Froyo, in Froyo, I cannot use Java NIO selector anymore, but it works fine in previous releases. On Mon, Jun 7, 2010 at 5:25 AM, 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.comandroid-developers%2bunsubscr...@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 at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Why is Android so buggy?
On 06/06/2010 11:25 PM, 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: [...] Since this thread seems to be still alive, I wanted to add something about your comparison with the iPhone situation. As it happens, I have just started to use XCode for a customer's project. And what I can say is that it is all but bugfree. Since you are mainly mentioning developer tools bugs, I can mention a terrific bug in XCode, where the intellisense thing is completely messing up the edited content, as if it wasn't properly redrawn or something. It really feels like I've mistyped something, but is just gone whenever I move to another file and come back. This bug has occured about a dozen time in very short time, and this is just a standard leopard snow system with a recent XCode installed. In regard to documentation, the help browser is everything but handy. Help pages are like 12 meters (40 feets ;) long in height, and whenever you press back, you come back to the top of the page. I neither want to troll nor to start an endless discussion, but I really felt like clarifying certain points. iPhone and Android are trying to push tech limits, and thus there are inevitable bugs on both side, that's it. -- Olivier -- 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
Re: [android-developers] Why is Android so buggy?
OK, the only example you bring up about ANDROID itself is the IOException-part... That is not even a _bug_, that is a usage error. Have you ever used BSD sockets in most other OS:es? It's up to you to handle connection timeouts. TCP/IP over the globe, and over slow/delayed networks will sometime cause big delays, so you can't just abort within a milli-second each time. The other stuff is about developer environment specific stuff, and of them only one is a real bug.. (The crash of the layout editor, which I agree is serious, but I never used it myself so I don't know if it affects many people..) Reg. Anton On Sun, Jun 6, 2010 at 11: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.comandroid-developers%2bunsubscr...@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 at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Why is Android so buggy?
On 06/09/2010 01:29 PM, Anton Persson wrote: OK, the only example you bring up about ANDROID itself is the IOException-part... That is not even a _bug_, that is a usage error. Have you ever used BSD sockets in most other OS:es? It's up to you to handle connection timeouts. TCP/IP over the globe, and over slow/delayed networks will sometime cause big delays, so you can't just abort within a milli-second each time. It's true that I did see my HTTP clients hanging before I fully read the docs and understood that I had to set specific timeouts. The other stuff is about developer environment specific stuff, and of them only one is a real bug.. (The crash of the layout editor, which I agree is serious, but I never used it myself so I don't know if it affects many people..) In this regard, I have to say that I just love the readability of Android XML layouts, as compared to Interface Builder so-called NIB files, where you have to cycle through all those little tabs in tiny windows to understand what's going on... Having a couple of bugs in the layout editor is really a minor issue compared to this. PS: I will not troll, I will not troll... ;) -- Olivier -- 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
Re: [android-developers] Why is Android so buggy?
On Wed, Jun 9, 2010 at 4:29 AM, Anton Persson don.juan...@gmail.com wrote: The other stuff is about developer environment specific stuff, and of them only one is a real bug.. (The crash of the layout editor, which I agree is serious, but I never used it myself so I don't know if it affects many people..) Just FYI for those who never used the editor, it's not an Eclipse crash. it's just the rendering that fails until you fix your layout. Eclipse is still usable but you have to switch to XML view to edit the layout. If you ran your app with such a layout, your app WOULD crash though. Is it a problem? Yes. Is it a major problem? Well it happens with one finicky widget that you're usually dropping once in a layout (it's not like it's a problem with buttons of checkboxes that you use all the time). Anyway, just explaining why it's been a low priority bug on our list. We've decided to add some much needed features (like Library Projects) instead of making the layout editor perfect, mostly because the editor can be used with a mix of the XML editor and the rendering for preview. We *are* working on it now though. Xav -- 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
Re: [android-developers] Why is Android so buggy?
Q: Why is Android so buggy? A: Because it's software - simple as that. On Sun, Jun 6, 2010 at 4: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. You compared Android to every existing piece of software there is? - TreKing - Chicago transit tracking app for Android-powered devices http://sites.google.com/site/rezmobileapps/treking -- 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
Re: [android-developers] Why is Android so buggy?
On Sun, Jun 6, 2010 at 2:25 PM, blahblah...@gmail.com blahblah...@gmail.com wrote: - 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. Ugh, we thought we had fixed this in rev 5 for the tools, but it looks like the fix isn't working on windows if you have a space in your standard java.ext.dirs path (which is the default anyway due to program Files). Anyway, I don't remember seeing someone complain that rev 5 didn't fix it for them (maybe you guys don't read the release notes?). I just checked in a fix for this. - When you view a TabWidget in the layout editor it crashes. This is know issue. The problem is that TabWidget cannot be used alone, it requires to be placed in a tabHost which must also contain a Framelayout (and both the Framelayout and the TabWidget must have very specific IDs, which the layout will automatically give, at least for the TabWidget). The problem is that the Android framework will throw and exception if something is missing regarding TabHost/TabWidget. Since the layout editor uses the Android view system to do the rendering, the rendering fail as well. Clearly we need to improve this particular use case, but right now we're focusing on having a layout editor that's actually usable. Xav -- 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] Why is Android so buggy?
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
Re: [android-developers] Why is Android so buggy?
I am not sure about the emulator menu button to unlock it being a bug... The one bug that really bothers me is the multi touch issue on different devices. I am not sure if it's been resolved, but last I read, it was impossible to make games with multi-touch controls due to an issue where after releasing the first touch point, then touching again it would register as the second touch point. From what I recall, someone on the android team said it was a hardware issue, yet, it appears on at least three different hardware platforms. I would think that would garner some major interest and a fix in 2.2 at the very latest, but not sure if it was or not. Still waiting for my 2.2 update for my moto droid. Supposedly sometime this month, but I am guessing next year before 2.2 gets released by Verizon. On Sun, Jun 6, 2010 at 2: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.comandroid-developers%2bunsubscr...@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 at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Why is Android so buggy?
I have spent my HTC magic for a year. So far, I am happy about that. On Mon, Jun 7, 2010 at 10:08 AM, Kevin Duffey andjar...@gmail.com wrote: I am not sure about the emulator menu button to unlock it being a bug... The one bug that really bothers me is the multi touch issue on different devices. I am not sure if it's been resolved, but last I read, it was impossible to make games with multi-touch controls due to an issue where after releasing the first touch point, then touching again it would register as the second touch point. From what I recall, someone on the android team said it was a hardware issue, yet, it appears on at least three different hardware platforms. I would think that would garner some major interest and a fix in 2.2 at the very latest, but not sure if it was or not. Still waiting for my 2.2 update for my moto droid. Supposedly sometime this month, but I am guessing next year before 2.2 gets released by Verizon. On Sun, Jun 6, 2010 at 2: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.comandroid-developers%2bunsubscr...@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%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Regards, Michael Leung http://www.itblogs.info http://www.michaelleung.info -- 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
