Why kill apps? I’m an Android developer. A top tier Android developer. And I ask you, why would you kill apps? Your reasoning for killing apps to save battery life is irrational and illogical. It’s impossible for an app designer to accommodate their app being killed in most instances! Killing an app can potentially cause the app to not work especially if the app is dependent on services and broadcast receivers registered in the manifest.
Conclusions: Unless your a developer, or a power use DO NOT KILL APPS!
If you don’t like the app, or the app is causing a problem UNINSTALL IT, REMOVE IT, but DO NOT KILL IT unless you fully understand that you can be causing the device and the application to malfunction.
« Shady Photo & Video Safe 4.0+ w/ the New LazyLoadingAdapter
Samsung and Motorola love to customize android. While recently their new skins are getting better and better they always have little bugs they introduce as a result of their customizations. One issue on most Samsung and Motorola phones is with listview transcript mode normal. Transcript mode is supposed to scroll to the bottom when a notify data set changed is called and only when the last item is visible. What my users report is essentially funny scrolling behavior. While transcript mode normal works beautifully and as expected on Nexus phones, Samsung and Motorola phones are predictably funny using this feature. I’ve contemplated handling scrolling to the bottom manually, but I have yet to implement the change.
Unfortunately because of these manufacturer customization issues I recommend not using transcript mode normal, just handle scrolling manually. These scrolling bugs still exist on Android 4.0 versions of Android.
In the end my recommendation is to BUY Nexus phones. Unfortunately I cannot recommend any Android phone with a custom skin until manufacturers stop butchering Android. Nexus phones are pure Android, without a butchered operating system.
Shady Photo & Video Safe 4.0+ w/ the New LazyLoadingAdapter »« Samsung Overrides Action Bar Overflow Menu
(Update) Turns out this is likely only on the Verizon GS3
As of 9AM on 7/13/2012 the LED notifications of Samsung Galaxy S3 devices in the US are broken. I don’t know if it’s all carriers, but….. It’s definite that the SGS3 does not respect either the deprecated or modern methods of settings the blink rate and color of the LED. The color tables are borked, where Color.BLUE, Color.RED do no generate the respective colors. The blink rate does not respect millisecond off and on values defined.
To be specific the follow deprecated notification methods do not work properly:
notification.ledARGB = Color.GREEN;
notification.ledOnMS = 300;
notification.ledOffMS = 1000;
notification.flags |= Notification.FLAG_SHOW_LIGHTS;
Also the following modern notification methods do not work properly:
notification.setLights(Color.GREEN, 500, 5000);
More Info over at LightFlow
Samsung Overrides Action Bar Overflow Menu »« Shady 3.0 26.19
Shady has gone through hundreds upon hundreds of updates over the years. The current version is my best implementation yet. It’s fully Android 4.0 Ice Cream Sandwich compatible, and is also designed to be future compatible with new Android versions. Shady 3.0 will never become outdated. There hasn’t been a single crash report in over 2 months, quite a rare accomplishment for an Android application. With over 10,000 active users it’s proving to be extraordinarily stable and reliable.
The quality of the product is great, sales and the userbase is another story. Why do Android user not buy applications? I would really love to code Android apps fulltime, but it’s simply not a profitable business in the niche I’m in. I truly wish it was.
Samsung Galaxy S3 (SGS3) LED Colors and Blink Rate Broken »« Shady SMS 3.0
