[Motorola Droid 3] JetpackJohn:
Greetings,

Just a few days ago I installed the most recent CM 10.1 nightly, first 20130319 and now updated to 20130323. For the most part, my phone is working well, but I do not have any 3g data service nor have I had it since installing CM 10.1.

I have a Droid 3 XT862 being used in the US on Verizon's CDMA network and placing and receiving calls works. I *can* send and receive SMS as well, although in a test I did toay I sent very short 25 character text from my Droid 3 on the Verizon network to another Android device on the Sprint network and it arrived a mere 2h15m later.

I have read many messages on this forum and others, but either the problem addressed is too far removed or the ideas/changes suggested are offered with little explantion as to why, so I am unsure if making any of these changes would be a good idea. I did read through the build.prop on my device and it certainly appears that it is more or less configured and ready for CDMA usage. I have performed a *228 PRL update, but it did not appear to help. CM 10.1 makes available, unlike the stock ROM, a menu/page full of mobile network settings. I have tried to work with some of these settings, toggles, preferred network types, and so on, but again none of these changes seems to have had an effect on my 3g data connection.

Am I doing something wrong? Does anybody know how to fix this? Or perhaps it is a new/temporary bug in CM 10.1?

As for the operation of everything else under CM 10.1, I like it very much. It is a very big step up from before, when I was first using stock Android 2.3.4 followed by the Maverick ROM, which, while better, sure liked to crash/reboot when under memory pressure. I do have a few issues that I hope others might be able to help with:

* The hardware keyboard's ALT key does not appear to work anymore which rules out half the symbols on the keyboard, making it far less useful. I also cannot use it any longer with VX ConnectBot as some of the mappings do not seem to work. For example, the "OK" key used to work as a CTRL key. Maybe these are related? Any idea how to fix this?

* The backlight on the hard buttons and on the keyboard was, previously, triggered by a light sensor (I think). Now the backlight comes on when there is any tapping, swiping, or button/key activity. That's fine, except that the timeout for the light is extremely short, on the order of about two seconds. In a dark environment, this can be annoying.

* It's slow... my god is it slow! I think this is due almost entirely to a severe lack of free RAM on the device, but I don't know what to do about it. Some programs, like GMail, take forever to start, while many others are just very slow to use/respond. I see the "Not Responding" popup appear *much* more than ever before, but, as I know these apps are just slow and not dead, I always just tap on "wait" and go on with what I was doing.

I really don't think I have that much running in the background or foreground to use all of this RAM. I have replaced Trebuchet with NemusLauncher in hopes of freeing some memory. I have three widgets only: a clock/weather widget, the standard calendar widget, and the Google Voice inbox widget. In the background, besides whatever Android and CM run, I have Google Voice and imo (the instant messanger) running. I believe that is it. Is there *anything* I can do to improve the speed issue? I understand how Android handles memory, so it is clearly not about just increasing the "free RAM" value. That said, however, it seems that if there were fewer apps trying to use the limited memory then this would naturally be higher to begin with.

I have a decent collection of apps, but the number is much smaller than in the past and most all of them should remain dormant unless I actually run them... or so I believe.

Okay, so those are the issues. I could add battery life and the camera to that list, but I have read on the forum that, no thanks to Motorola, the camera is unlikely to be available anytime soon, and I have also read that the battery issues should be resolved soon.

So, um... please help! :) And great many thanks to all of the hard working devs who bring us better software and especially to those who help those of us with devices that are practically *new* and yet abandoned by the carriers. Extra kudos to those finding ways to work around locked bootloaders and proprietary binary blobs.

--John Gruenenfelder