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.

https://play.google.com/store/apps/details?id=com.project.memoryerrorsafetwo

It’s built on the powerful Lazy Loading Adapter library I published on GitHub for public consumption. The adapter is extremely efficient and versatile. With support for images and video, local paths, remote uris, and ids of media in the phone’s Gallery content provider. The library has built in LRU caching, position highlighting, and a unique single thread blocking structure.

https://github.com/nseidm1/LazyLoadingAdapter

Go ahead, simplify your project, add some fast loading galleries of videos and images, and do it all with a couple of lines of code.

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.

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

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.

• Touch sensitive drag and drop contact list
• Innovative alphabetic sorting feature
• Android Market style swip-able pages
• Fantastic UI overhaul with a transparent call filters and settings page
• Croppable HD wallpaper for the contact list and the contact threads
• Countless new additions including 25 fonts and 19 built in messager themes
• Tweaks and enhancements to all code establishing a remarkable level of stability
• Complete compatibility with Android 4.0 Ice Cream Sandwich
• More, more, more……

Overall welcome to Shady 3.0, where what happens in Shady stays in Shady

Shady SMS 2.0 has countless new features compared to the original version. My most liked features include:

1. Sent and received notifications
2. MMS image, video, and text filtering
3. The 24 customizable notification icons
4. The awesome super backup and restore feature
5. The  4 different styles to the contact list, personally I use the medium thumbnail mode
6. The new Sensation theme for the messager

Overall there are way to many feature in total for me to go through all of them in a single post. Shady turned into a sophisticated messaging machine. When I first started coding Shady I would have never imagined it would have turned into such a complicated project, but users kept emailing asking for new features; and I kept adding them.

One of the most common requested features is sorting of the contact list. Unfortunately it won’t be possible in the current version for countless reason. To be brief I will have to recode the entire data storage mechanism in order to achieve the feature. When I think about releasing Shady SMS 3.0 sorting of the contact list is one big motivator.

Currently Shady is #11 is the Social category top paid apps list. It has been fluctuating between #10 and #11 for the past couple of months, but it looks like its staying at the top I thank all my loyal customers that have the patience to email me and ask for support rather than just ignorantly rant in the comments. Your intelligent decision to prose questions and implement troubleshooting to achieve results has made Shady an extremely successful application. I guarantee that 9/10 issues are already discussed in the Shady Market Description, but definitely click the new help menu in Shady! The new help menu detects if Go SMS, Chomp, Handcent, ATK, and Android Booster are installed and provides instructions/recommendations accordingly. It is now a smart help menu. It gets straight to the point and does not show information unless needed.

Between the help menu, the Market Description, and my email based technical support Shady is guaranteed to be an effective secret/hidden messaging application that will meet or exceed your expectations!

Here’s a scenario. Lets say you never changed the default “123″ password of Shady 1.0. Then you install Shady 2.0. When you dial your default passcode it will open both applications at the same time. This will confuse the heck out of un-tech savvy users. To avoid this confusing situation please follow the step above to remove Shady 1.0 from your telephone before installing Shady 2.0.

I gave up on trying to publish an update to Shady 1.0. I published Shady back on the market using a similar name, and a different package name. The different package name means Shady 2.0 will install on systems that have Shady 1.0 installed. There will be two separate applications causing a conflict.  Shady 1.0 needs to be manually removed using the Android Applications system menu. Press menu, press settings, press Applications, press Manage Applications. Locate “Memory Error”, select it, then uninstall. You’ll want to export all of your Shady contact first prior to manually removing it.

Then you can purchase Shady 2.0. This is the only way it can be. Google still hasn’t responded to my update issue. I simply cannot upload an update to the market for Shady 1.0. What a shame. I lost my stars, comments, and rank in the social category. I guess it will take some months to get my status back, but it will come back; it’s Shady

If you purchased Shady 1.0 within the last month I am offering refunds for the original product. You’ll be able to install Shady 2.0, and email me requesting that I refund Shady 1.0. Users owing a copy of Shady 1.0 older than 1 month can purchase the new Shady 2.0, but will not be offered a refund for 1.0 unless there is an extenuating circumstance.

I code Shady by myself, only by myself, and without the help of anyone else; it takes a lot of time and effort.

Please don’t be confused, its not that I don’t want to update Shady 1.0. I CANNOT update Shady 1.0. The Android Market Administrator panel is not accepting the upload. This situation was the only course of actions given the lack of response by the Google support team.

——————————————–

Shady 2.0 has been built, and debugged using Android 2.3 in Cyanogen Mod 7 RC1 for the Droid Incredible. Shady 2.0 takes advantage of the new JIT compiler enhancements, and memory management improvement, to establish a stable application above and beyond Shady 1.0. In many way this unfortunate situation is a good situation because Shady 2.0 is sooooo incredibly different and really requires a forced uninstall of the original. The new app, after a fresh install, is much much better than Shady 1.0 in soooo many ways!

22.47 contains a host of new features that started about a month ago with 22.20. Shady now contains a password recovery feature. Set a recovery phrase, in the main settings, and text your phone the phrase from any cellphone. Shady automatically responds with your access code.

My favorite new feature is the auto archive. Since the messager has to be completely processed in the UI thread, having a large thread was extremely slow. Now Shady only loads the last 50 messages, thus reducing the load time of the messager tremendously. When the archive is less than 500 messages the archive button says “normal”. When above 500 it says “large”, and when above 1000 it says “too large” and turns red. Handling large threads is difficult and slow. Above 500 messages the load time will be in the seconds. Above 1000 it may take several seconds for all messages to load. The read it takes time to load is because all messages need to be processed in the UI thread, and cannot be executed in a background thread. This causes the UI thread to hand until the entire thread is processed and displayed. I want to code a delete the entire archive button, which will conveniently save recent messages while also cleaning up the thread without requiring a full delete of the entire thread.

The archive is a big feature because is substantially decreases the load time, of the messager, when a contact has a large thread. Before the archive was coded some users mentioned the messager took a long time to load, and the only solution was to delete the entire thread. Now the messager is much more versatile. When I add the delete archive feature it will be even better.

There have been countless improvements since 22.19. The contact list is much better formatted with the large contact name. Instead of the “text” and “call” words, on the contact list, the contact animates showing the type of new message. Also convenient is the red message count at the top of the contact list. While I really want to work on re-organizing the contact list, particularly moving contacts with new messages to the top, I may hold off on such a feature until Shady 2.0. I don’t want to jeopardize stability! Shady’s data storage mechanism doesn’t make it easy to reorganize the list, and ultimately I want to recode Shady to use an entirely different storage mechanism, which will much better facilitate reorganizing the list.

Some improvements to the messager include the new larger editor at the bottom. It gives much more room to edit your message. In combination with the new font selection menu, if you reduce the font size, you can really fit a lot of text in message editor. The messager’s timing has also been adjusted making the animations much more smooth. Note that when your editing a message using the keyboard, the keyboard closes first then the message begins to send approximately .5 seconds later. Previously the message began to send immediately, which caused a stutter in the UI. This stutter was completely resolved using the new message send delay of .5 seconds; a much better UI feel.

Shady needed some tweaking to the screen off protection code. If the screen was turned off, and any dialog was open, it would causes a window to leak. This would cause Shady to crash. No good! I ended up create auto close code, for each dialog, to close the dialog automatically if it was left open when the program terminates. This completely eliminates a nasty crash condition associated with the screen off protection feature.

A little fix was the smileys in the stock theme. Fixed line wrapping and caps in landscape mode. I added an additional default login code; 321.

Shady 22.47 should be around for some time. I hope not as long as 22.19, which was around for 2 months I like updating, but many users post nasty comments about me updating too much; what a shame. If you want to remove Shady from your Market downloads tab please root your device and using Titanium Backup. With Titanium Backup you can backup Shady, uninstall using the remove from downloads tab option, and then restore the app. A simple solution for many users that constantly and unnecessarily complain about the downloads tab.

I have some more work to do on Shady before I begin working on a second generation. I want Shady 1.0 to be the best it can be, and then I will take it to another level. I have many plans for 2.0, most of which require a complete re-working of the data storage mechanism.

If you have a device released with 1.6 (Hero, Moment, Eris), or a Samsung/Droid2 with a SMS history tab, I provide full support for Cyanogen Mod 6, and other stock based ROMs. For Shady to work on your device the OS needs to be exchanged for a different operating system. Use unrevoked.com to root and Rom Manager to install an alt OS

Continuing on, Shady SMS uses many APIs in the Android SDK. It also uses an aspect of the Android OS that is not in the SDK, but built into the default source code of the stock messager on all Android models. Shady interacts effectively with the SMS/MMS content provider of the stock messager. This is not an issue that I have encountered. The primary issue that I have encountered a problem with is various customizations that manufacturers have done to the Android OS. Each manufacturer loves to place a skin on top of a stock Android build. This skin is causing a lot of problems ultimately rendering many devices incompatible with Shady. NOTE that I do not say that Shady is incompatible with any device, as it works on all devices. IT IS the manufacturers customizations that are incompatible with Shady.

The customizations that I am referring to are the history tabs. On Samsungs the contacts history tab caches SMS messages. Shady effectively and conclusively deletes the SMS message from the phone. You will not be able to see the SMS message in the stock messager. But the SMS messages still shows on the history tab. Samsung has coded their history tab not to mirror the SMS content provider. Since Samsung does not have an API for this history tab, Shady SMS messages will show likely and there is absolutely nothing that can be coded into Shady to address the issue. Samsung does not provide an option to disable the tab, at all!

I have a problem with the Android customizations coded by many manufacturers. They are going too far rendering a powerful application like Shady relatively useless. This is NOT an issue at all on HTC models. HTC does not cache SMS messages. I code on the Droid Incredible and it is clearly the device of choice for Shady. The HTC EVO 4G is also getting excellent comments.

Because of manufacturer customizations I am forced to define the best devices to purchase for use with Shady. Because I code on the Incredible I highly recommend the device. You will have the best performance because all of my testing is considering the custom HTC Sense skin used. Since the EVO 4G is comparable similar performance will be achieved. I have also received good comments for use with the Moto X, although I cannot confirm everything. Apparently the Droid 2 has a history tab as well.

There is always a solution. You must root your device and install a custom OS. Samsung devices are readily rootable, and ROM manager is quite effective at installing, and managing alternative operating systems. Cyanogen Mod 6 is based on stock Android released by Google. Shady works extremely well on Cyanogen!! If you have a device with a history tab, and want Shady to be as effective as possible, please consider rooting your device and installing such a replacement operating system. That, or consider exchanging your device for something that is compatible with Shady.

I apologize for these problems manufacturers have introduced into their custom skins. I hope Google addresses this problem, and forces manufacturers to stick with the stock Android build.

I would like to restate that Shady works on all Android, but there are many manufacturer customized Android operating systems that are not compatible with Shady. NOT THE OTHER WAY AROUND!

Notes:
1) In the main settings is a button at the bottom \”Settings Explanation\”.
2) The call mask feature, and dummy texts are disabled by default now.
3) Set custom notification sounds in the main setting!

Updates:
311) Fixed up the main settings explanation dialog accessible via the button at the bottom of the main settings
310) Dummy texts are off by default now
309) Added option to the main settings to enable missed call notifications. This option is useful for use with send to voicemail. Most phones send a notification for calls sent to voicemail, others do not
308) By default custom notification icons are off. The default Android SMS icon is now used. Custom notification icons can be turned on in the main settings
307) Added uncaught exception handler to messager, and contact list to catch anything not caught in a thread itself. It will automatically attach the stack trace to an email, please send it to me as everything is pre populated!
306) Added exception handling to login broadcast receiver just in case somehow the outgoing number is null. Go figure sometimes it is and it crashes Shady, but no more

1) The default notification icon will be the default icon of Android

2) I added exception handling for the login broadcast receiver to prevent strange crashing when the outgoing number is somehow null

3) I added a default exception handler for all threads to generate an email with the stack trace

4) I cleaned up the settings explanation in the main settings

21.02 includes:

305) Made the call mask feature optional because of its unpredictable behavior. The call mask creates a real contact on the fly, after the call is received but before the phone actually rings. Because of the millisecond timing required for this feature, slower phones usually don’t perform well. If the call mask was generated after the phone rang it would not work, and most likely would generate a blank contact in the real contact list, a little annoying but not a deal breaker. You can turn this option on in the main settings
304) When Shady receives a video it cannot be filtered because of Android OS limitations, particular SDK shortcoming. Shady will no longer delete the message as it was doing before, it will only add a message to the Shady contacts thread saying that video filtering cannot be supported

301) Shady has reached 32,000+ lines of code!

***) Shady is now optimized, compressed, and obfuscated

300) Now the contact list background is removed and added in the onstart and onstop, which will improve memory management

299) Moved the sent SMS broadcast receiver unregistration code to the ondestroy, which will allow the bar to be updated even if you move the messager to the background

298) When the messager was closing the default open message thread was set to zero, which would cause undesirable behavior

297) Now the messager stays alive in the background when pressing the home button

296) Removed override for onrotate, which should fix phones with sliding keyboards
295) Added additional condition to incoming MMS thread content observer reactivation code
294) Extracted all main settings, contact menu, and address dialog cleanup code and placed in contact list ondestroy
293) Removed delivery reports for the time being, they may be revisited in the future
292) Reverted incoming SMS dialog to the 16th, which was a completely stable version
291) Removed memory management in contact menu dialog

Timing is of the utmost importance with regard to proper thread behavior. Many timing adjustments have been made to ensure several things; 1) That the message sent bar updates properly, 2) That incoming SMS messages don’t overlap, 3) That outgoing SMS messages don’t overlap, 4) That re-drawing the messager screen does not overlap with 1, 2, and 3.

290) Added previously removed 1 sec delay in the very beginning of the incoming SMS thread. Silent, but very necessary

289) Fixed bug in contact menu dialog memory management

288) The messager’s edit text now starts without focus, which may fix a crash on devices with slide out keyboards
287) Substantially improved sent SMS bar response time

286) Added concurrent incoming SMS message detection, apparently something similar happens as compared to MMS temp messages, which was overlooked previously
285) Added 1 second delay to end of incoming SMS thread
284) Extended send SMS after thread delay to 3 seconds
283) Increased send SMS overlapping message delay to 2 seconds to improve sent message reporting
282) Increased SMS table check to 1.25 seconds, and delete SMS delay to 1.25 seconds (changed 280)
281) The best concurrent incoming MMS filtering code yet, as a coder the log tags really look great, this code is smart!!!

280) Added additional 1 second delay before deleting Shady SMS messages in an attempt to stabilize the algorithm
279) Additional memory managment of contact menu dialog
278) Tweaked memory management of contact menu dialog per a crash report today. The cleanup now takes place 4 seconds after the dialog is closed using a thread and a pause
277) Tweaked failed SMS download code in the incoming SMS thread
276) Removed premature Android cloud backup code, which causes a strange crash today

275) Verizon was having trouble with SMS messaging tonight. The SMS broadcast receiver was firing, but the message was never added to the SMS content provider. Because of this I added a 10 second timeout. If the broadcast receiver fires, and no message is added to the SMS content provider, the incoming SMS filter thread will break as if no message was received. This was preventing Shady from sending messages. To properly handle this situation a message will be added to the contacts thread stating that the carrier failed to deliver the message to the phone, and that the contact should be notified that the message wasnt received
274) Faster SMS message processing (progress bar)
273) Idiot proofed the removal of the 3 default background. Shady defaults back to the Leaf background
272) Forgot to set the default MMS icon to custom, as per the default main settings configuration

(NOTE) If you experience strange background scrambling in the messager, please change the background. This may result rarely, very rarely, because I removed 3 default background!!

268) Removed 3 default background images to reduce package size
267) Added excellent memory management in the incoming SMS/MMS threads. Reduced memory load translates to increased battery life
266) Fixed Shady registration checker bug on failed registration check
265) Shady now nicely supports concurrent, overlapping incoming MMS images