[Motorola Droid RAZR] Ohmster:
That is a good answer. You would be surprised at how many developers I have contacted (Always be polite and to the point.) and have gotten help from. One would think that developers have no time for the public and you will never get anymore than a "canned response". Not true, many of them, especially open source or small dollar apps are not *that* busy so they cannot answer you. It is in their best interest to fix any bugs that might have gotten by, they *love* to hear praise about their work or project, and can and will be quite willing to help you.

I am a likeable guy and make friends easily, once the people realize and accept that "I talk to darned much" and get over it, many people will help me or become friends. I got a free, lifetime platinum license for cBlocker, one of the best call blockers for a phone that I ever saw from the developer. I never asked for it nor complained about the app. I bought and paid for it's predecessor, Call Blocker Gold. Jamie the developer, became my friend, we talked, traded stories, and when my Droid X would no longer block anonymous calls after Jellybean I think it was, he worked with me, through logs, to solve the problem. He had a manual entry to block calls as well as build in ones such as block anonymous calls, blacklist contacts, and block from the call log. The manual entry pad was strictly numeric so you could add a phone number to block, and give it a name afterwards. It turned out, while looking through the logs, that the way Android labeled private or anonymous calls was by code name for that type of call. The code name for it was changed in the OS change so if Call Blocker was looking for "private" or "anonymous", it would never find it anymore because the new OS now labeled them as "UNKNOWN". Now Jaimie could have just modified his code to look for the new call label, but instead I suggested he give an alphanumeric keyboard and not just a numerical one. He made a special build just for me to test it. So now that I know what to look for by running Log Cat during calls and examining them, we discovered the new labels and I could just type in "UNKNOWN" or whatever I want, and it worked perfectly!

So, Jaimie got his app fixed, I got what I wanted, and he left the alphanumeric keyboard in the "Advanced Settings". Now that was really cool because now I can block any type of call I like, based on the log entries and quickly got rid of telemarketers, anonymous calls, private calls, or when someone turns off caller ID or dials *67 prior to dialing. Next thing I knew, Jaimie sent me a lifetime platinum license for the app. Wow, that was cool because you can purchase different types of licenses and none of them were "lifetime" and the app was and is still the best call blocker.

CM11 changed the need for such an app by including a blacklist for calls and text. That is what my nice app does, only my app has many more options. See? If you do contact a developer, be nice, polite, state your business, and give some praise. You will be surprised at what you get sometimes. :victory:

---------- Post added at 11:54 PM ---------- Previous post was at 11:03 PM ----------

Yeah. CM11 is "not very good" at seeing through the lockscreen or backlight off sleep sometimes. Especially in Bluetooth. A lot of it is, like Jake said, older apps that are not up to Kit Kat quite yet. Kit Kat really changed the rules for apps, system load, and memory management. Apps were getting bolder and bolder, demanding new permissions, staying "open" and running, forever, forcing the user to buy a new phone every 2 years just to keep up with it. Enough is enough so Google created Kit Kat, which does not put up with that crap. You, app, you done yet? No, well I say you are, GO TO BED! ....and, "Make it so".

Facebook, always open, Google services of every kind, always open, but Google was nice about it. Since they are "the creators and maintainers", they *do* have to keep many of their services open and running. But they maintain a small footprint. When I installed a couple of new, great graphics and cool looking games, "Let's Golf 3" and "777 Slots" I was at first bowled over by the amazing graphics, hey this is great stuff. But, in short order, I remembered that there is no such thing as free lunch and these game apps really proved it. For one, "Let's Golf 3" with all of it's charming and amazing graphics, had NO Exit or Quite button. Huh? How do you make it go away then? Tap the home button was the only way, except it never quit running, eating up the memory, the precious system resources. And when I finally got a good task killer and killed the app (Can be done in Settings/Apps too.), the darned thing respawned as fast as I could kill it. Why? So they could embed advertisements into your device. Same thing for 777 Slots. To make it worse, these "free games" would let you play this amazing stuff for a couple of rounds, 2 or 3 holes in golf, and a few pulls of the handle in slots, then you had to "Buy credits" to play more, with real money! WTF?!! There was a way to keep playing free, but you had to do a lot of boring BS and wait days to get another coin or hole of Golf, or, you could get your wallet out. I was appalled and removed the apps forever. Kit Kat would NEVER allow that stay on forever thing but it cannot kill the play for cash BS.

Oh my, I really got off topic, didn't I? :eek:

Yeah the Bluetooth behind the black screen had always been an issue. I do have a good relationship with Micheal, our developer, and helped to get the artificial speech in Bluetooth issue patched and fixed. Stargo cannot reproduce orange bars and signal problems in Nuremberg with GSM so that will be quite an issue. They are two entirely different radio systems and they are NOT compatible in any way. So signal may be an issue for a while but I can ask and help him with the Bluetooth black-screen issue. Since he just finished up a serious problem in Bluetooth, he might want to take that one on. But right now, I got him working with me on the video cam issue. The pause release dot is so freaking tiny (2mm) that 9 out of 10 times you will hit the surrounding screen before hitting the dot. The screen in the vid cam is touch sensitive to take a photo while recording video, and it works quite well. But if you touch the screen while in pause, it freaks out, crashes the recording, and you lose the entire video file or end up with a huge, useless tmp file you must delete. He showed me in the code that there are 3 different size bitmaps for the un-pause dot and he *does* get the bigger dot so he can safely un-pause video and continue recording. Since we do not get the big dot, you take a 90% risk of trashing the entire video if you dare to pause and resume while recording. He has a friend in the Nexus dev section that can look into it. I suggested an if/then statement in the code to stop the touch sensitive surrounding screen during pause to stop even an accidental touch to the screen in pause from trashing the video. We will see how it goes.

Give me a little time and I will get some more info or a fix for the Bluetooth. CM11 still needs work on Bluetooth but Jake is right, the app developers have to write code up to the Kit Kat spec and we should hold them accountable, in a very polite and friendly manor when we ask them for help. It is not all cm11's fault.

'night guys! :cool: