HTC replied now that colored LEDs are NOT supported by the custom Android version installed on the HTC Hero. This confirmed my fear that HTC is breaking the funcionality of notifications offered in the Android SDK.
>From my point of view it is just a starting point of problems we will see with Android getting modified by device manufacturers. On 20 Okt., 15:36, code_android_festival_way <festival.s...@googlemail.com> wrote: > [This is the follow up of a thread I have started in the android- > platform group] > > Hello. > > I am the developer of a heavily used application (over 110.000 active > installs) and got one problem with the Android platform. > > One of the features in my application uses the normal way of the > Android SDK to display a LED notification with a selectable color. The > color can be set by ledARGB flag > inhttp://developer.android.com/reference/android/app/Notification.html. > > This had been working with the emulator, the HTC G1 and the HTC Magic > (myTouch) but now users starting to report that the HTC Hero does not > show up different colors. (although the charging LED for the HTC Hero > is orange and the normal notification color is green) > > The same thing occurs for setting a vibrate pattern. (flag -> vibrate > inhttp://developer.android.com/reference/android/app/Notification.html) > This does not work on the HTC Hero US. (it does work on the EU/GSM > version of the Hero) > > Now I'm a bit worried that this list of basic SDK features not working > on Android devices gets longer and longer. (I have heared from > problems with alarms on the T-Mobile Pulse) > > How can we as developers handle such problems? How can we make sure > that our applications do not net served to not supported devices by > the Android market? Or how can we hide specific features from specific > handsets? > > I am ware of the following manifest > settings:http://developer.android.com/guide/topics/manifest/uses-feature-eleme...http://developer.android.com/guide/topics/manifest/uses-configuration... > > But they do not help me in these cases. > > I have tried to get some response by HTC but haven't gotten anything > untill now. > > It would be great to hear some of your opinions. > > Regards > > --- > > JBQ answered: > At this point in time this discussion is still somewhat off-topic in > this group, since none of the compatibility stuff is exposed in the > open. Android-developers might be a better place to discuss this. > > Those device-specific bugs are a definite concern, though, and we'll > need to either tighten the compatibility requirements or document that > those APIs aren't guaranteed to work on all devices. > > Thanks, > JBQ > > ---- > My answer: > You are right and I will start another topic in the Android-developers > group. > > From my point of view it would be ok if there would be a possibility > in the SDK (some methods) to get to know from code if the not > guaranteed APIs are available on a specific device or not. So > developers could hide features if the device does not allow them. > > But to be honest I'd like the first way more which means tightening > the compatibility requirements. > > At the moment all developers can do is to exclude some devices from > their support list because of being not 100% compatible with the > Android SDK offered by the Android open source project. > > Regards and thank you for your answer JBQ. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
