So... don't ignore the low space warning. Delete something.
Ever missed an SMS on your Android? Here's why. (long-standing bug)
41–50 of 69 posts
Re: Ever missed an SMS on your Android? Here's why. (long-standing bug)
#42Type approval must be a walk over these days as long as you have a flash UI.
Re: Ever missed an SMS on your Android? Here's why. (long-standing bug)
#43This is one of the examples where I'm concerned about my own professionality because i can't grasp why Google would overlook such an error for such a long time. Maybe there is a reason but my feeble mind can't bend around it?
Easily reproducible doesn't equal easily fixed.
Re: Ever missed an SMS on your Android? Here's why. (long-standing bug)
#44Because of the high quality of iOS and it's large market reach, Android development had to be rushed a great deal. This caused most of the programming power to go towards developing base features (android 1.x - 2.x) or implementing tablet features when the iPad arrived, and almost no resources were left for developers support (the emulators are awfully slow, severe lack of animations framework, etc...) and for bug fi…
Ah right, when Apple stops innovating, then?
Re: Ever missed an SMS on your Android? Here's why. (long-standing bug)
#45Earlier quoted context omitted.
appears not to have been fixed yet by Google Or by anyone whining on the bug tracker who say this issue is ruining their life.
So, you have to be able to fix bugs in Android if you want to use it? I somehow doubt that Google wants to sell Android phones only to the 20 million developers in the world who could (theoretically) fix bugs.
Basically, Google has no incentive to fix this bug, but the people complaining about it do. So they should do the fixing if they actually want it fixed.
(Technically, the OEM or carriers should fix this bug, and they are probably working on it Behind The Scenes.)
Re: Ever missed an SMS on your Android? Here's why. (long-standing bug)
#46Earlier quoted context omitted.
appears not to have been fixed yet by Google Or by anyone whining on the bug tracker who say this issue is ruining their life.
Android development is done only by Google. When they're ready, they release a new version along with its source code.
There are also a number of third-party Android distributions (CyanogenMod, etc.) that accept patches and do nightly releases.
If there is a bug in Android, and it is "ruining your life", it's your fault for not fixing it.
Re: Ever missed an SMS on your Android? Here's why. (long-standing bug)
#47Earlier quoted context omitted.
Just treat it as "+1 I'm affected too". Could be written better, but it at least shows the number of people affected / annoyed by specific bug.
The problem is that nobody from google seems to read these bug reports.
Re: Ever missed an SMS on your Android? Here's why. (long-standing bug)
#48Earlier quoted context omitted.
So, you have to be able to fix bugs in Android if you want to use it? I somehow doubt that Google wants to sell Android phones only to the 20 million developers in the world who could (theoretically) fix bugs.
Well, they don't sell Android phones. The carriers do. Google benefits from you doing Google searches on the phones, which is unaffected by this. Basically, Google has no incentive to fix this bug, but the people complaining about it do. So they should do the fixing if they actually want it fixed. (Technically, the OEM or carriers should fix this bug, and they are probably working on it Behind The Scenes.)
Your opinion seems to truly be that you can expect no reliable help from Google when you encounter a bug in Android which is pretty mind-blowing to me. I don’t think that Google is quiet so deaf.
Re: Ever missed an SMS on your Android? Here's why. (long-standing bug)
#49Re: Ever missed an SMS on your Android? Here's why. (long-standing bug)
#50This is one of the examples where I'm concerned about my own professionality because i can't grasp why Google would overlook such an error for such a long time. Maybe there is a reason but my feeble mind can't bend around it?
Easily reproducible doesn't equal easily fixed.
Really fixing it would require something more intelligent about the way Android handles space, such as reserving an amount of the internal memory for "critical" applications, or moving caches to SD card. The reason caches aren't on the SD card, I believe, is something philosophical at Google. They're holding onto the belief that people actually swap them with some regularity, rather than using them as user-expandable internal storage. Why Browser should merrily suck up an 80MB cache on my tiny internal memory is beyond me.