[Motorola Droid RAZR] Ohmster:
Extended Build Report, cm11 04/22

* Yeah, yeah. Another darned book by Ohmster. I will figure out how to say things shorter, I am working on it. Give me a chance, please. :fingers-crossed:

Installed Build 04/22 on 04/22 @ 6:12 PDT

Upgraded from 04/21 to 04/22 OTA from settings menu, totally hands off. Update went very smooth, rebooted to system, tapped Xframwork installer and rebooted to restore Xposed modules. All went very well. No apparent bugs, everything seemed to work well. GPS, camera, WiFi.

Follow up report Build 04/22 Today Wednesday, April 23, 2014 @ 9:56 PM EST

Noticed that Google voice typing no longer working. Also onscreen keyboard keys no longer produced key press tick sounds that I had enabled. I like the feedback I get from the sound, confirming the button press. Voice typing would produce the gray ½ window with white circle. Never turned red to beep and accept voice input. Only way to restore it was a reboot. Same thing would occur within an hour of rebooting. Reported this in a post to this thread. Did have Bluetooth turned on, but headset was turned off and NOT connected. Did not think this as relevant at the time.

Stargo noticed this and commented on it, it is a confirmed bug in this build by Micheal, AKA Stargo. Senior Member, Droid developer, and OMAP4 team leader:

The culprit is bluetooth. Once you disconnect from a bluetooth device, audio-routing is messed up. This is due to a big bluetooth-change on monday and probably affects many more devices. I've just debugged it and know exactly what's going wrong, but I'm too tired now to think of a clean fix, run a build (45min), test it and push it to CM. Tomorrow...

Stargo, Micheal, is a brilliant young open source developer and is also a very personable guy.

We are very lucky to have him

. Really technical guys are often absorbed in their work and are not socially tolerant to engage in chit chat or get involved with the end users. I have found this to be the case all throughout my life. Micheal is one of the very rare exceptions. Thank you, Mr. Gernoth.

So it will be fixed. I did remove Battery Doctor as I thought it might be putting voice typing to sleep. A system app, not usually allowed to be pushed to sleep. No, it didn't help as explained above. But, after uninstalling Battery Doctor, I was at 20% battery and dropping, fast, 4 hours off charge. Reinstalled Battery Doctor. Charging time was predicted at 3½ hours, actual time, about 45 minutes. Battery Doctor uses three stages to charge; rapid to normal then trickle at near 100%. Very good app. I did not use an hour of talk time and without any battery saving measures, I did run out of battery to 20% within 4 hours.

Possible bug or issue with my phone.

End Report

Thoughts to the group as a whole:

By the way, we have a wonderful mix of very experienced members here and many of them here [MENTION=3322848]JakeDHS07[/MENTION] [MENTION=5685307]ef141[/MENTION] and many others, who install new builds almost every day, to test them and put them through their paces. The most important thing about these tests are the reports they give back to the group. The install method such as clean or OTA, how it went, any bugs or anomalies with the update or working rom. Better yet are the followup reports on how it holds out for daily use, a day or two later. These reports are

pure gold

to the group and especially the members who really need a phone 24/7, want to stay current, and cannot afford to test a new build that might be gold or might be a termite nest. We are all very grateful to you guys and gals for performing these tests and reports and submitting them to the group. Personally, I feel they are so important as to warrant a special title for the test so it can be found easily by searching such as the words "Build Report" in the title with build date and/or within the body of the post. Perhaps if we all come together and can somehow mark build reports so they can easily be found, it would be a boon to everyone. "Bug reports" or issues are another area that might warrant a special title to those searching for issues to help themselves. Since these may not be true "bug reports" but can be due to a user with a dirty install, corrupted data, or other individual issue, some other term should be used or thought of. Open to suggestions, anyone? I do not set the rules so all input and thoughts from anyone are always welcome.

I really shouldn't comment in build reports like this with group suggestions and keep them what they are, build reports. But if we can come up with a system to mark important posts such as build reports and anomalies to be easily found, it was worth the effort. I will try not to prolong build reports with such dialog in the future. Thanks guys. :cool: