395 replies to this topic

[mhale_85]

106 has actually resolved a great many issues with my D2 disconnecting and reconnecting from the network. I have awful reception at my desk at work and have to park underground. Whenever I lost my data connection (and the bars/3G indicator turns white) my phone would not reconnect unless I put it in Airplane mode and took it back out.

Though I've only had build 106 for one day, so far so good. The phone seems to be much more stable when losing and regaining data.

Still waiting for Live Wallpapers to function properly and a few other minor hiccups to be resolved. Has anyone noticed that a good number of their apps aren't displayed in the "My Apps" section of Android Market?

Edited by mhale_85, 15 October 2011 - 01:52 AM.

[onecallednick]

@mhale, yes my fiancee's d2 had the same issue with apps in the market not showing up. They do show up eventually though.  Any word on when we get the stable build?

[ZehASiegel]

I don't know if it's a problem with my computer or not, but I'm still having trouble connecting my phone via USB. it'll detect the phone, but it won't let me access the SD card. And even though I'm on 106, this problem still remains (I've been updating via DropBox). Any known fixes?

[Tyler Wayne]

I'm having issues with CyanogenMod connecting via USB, too. I don't know what the problem is, but I'll share my workaround:  ClockworkMod Recovery's "Mount as USB" option. Boot into ClockworkMod Recovery, and find its option to do this. For some reason, it works even though CyanogenMod has trouble with it.

Good luck! And thanks to all the devs for the great work! I really appreciate it.

[ZehASiegel]

I tried ClockworkMod's Mount as USB and it didn't work. It might be my computer for all i know...
Thanks anyways!

[livErD69]

FWIW sometimes my usb doesn't work on the first plug in, but usually unplugging and replugging fixes it.  My usb port is a little worn so I just chalked it up to that.  Could be an issue though for all I know...  Also if you haven't done a clear cache partition since the re-wrote the usb it may be a good idea.  Pretty sure the devs re-wrote the usb in the early 90s of nightlies, switching it from moto usb to cyanogen usb.  Hopefully this helps someone.

I also had issues with apps not showing in my apps in the market.  However I later found that since I had multiple gmail accounts set up, the market was reading my school email as my account (which I have no apps under) instead of my personal gmail account which has all my apps.  Picking accounts (in market) from the options and then picking my personal account always fixes the problem immediately.

Either way I still think my phone is a million times more reliable since canning motoblur... and these are only nightlies.  LOL.

Edited by livErD69, 17 October 2011 - 03:11 AM.

[b00sted415]

So I think I'm screwed. I used EZ root for my gf's droid 2 global to root the device. I then went ahead and installed the latest nightly which at the time was nightly 98. Everything worked fine except that the device was stuck in hands free mode. So the device can not make phone calls or receive phone calls. Says (No service)!!!! ugh!!!!...  I tried everything re install, re flash, wipe, wipe dalvik cache, wipe battery etc. This all happened on Thursday. Thursday night and friday I tried every method I possibly could. Yesterday and today I tried to revert back to stock using SPF method with no luck. I keep getting errors attempting to use RSD lite. Every time I wipe the data using stock recovery and clockworkMod when I reboot cyanogenMod keeps popping up as if I haven't wiped nothing!!! At this point I'm not sure what my options are anyone out there having trouble going back to stock? I've tried every nightly to see if the (no service) problem goes away but nothing. At this point I'll install any other ROM to get the phone working.

[Phoible]

This is Cyanogenmod for the Droid 2, and not the Droid2 Global. So you aren't going to be able to install it successfully on your device (I'm pretty sure there is a separate build for the D2G). Are you sure that you have the right SBF?

[mdmadph]

b00sted415, on 17 October 2011 - 04:22 AM, said:

So I think I'm screwed. I used EZ root for my gf's droid 2 global to root the device. I then went ahead and installed the latest nightly which at the time was nightly 98. Everything worked fine except that the device was stuck in hands free mode. So the device can not make phone calls or receive phone calls. Says (No service)!!!! ugh!!!!...  I tried everything re install, re flash, wipe, wipe dalvik cache, wipe battery etc. This all happened on Thursday. Thursday night and friday I tried every method I possibly could. Yesterday and today I tried to revert back to stock using SPF method with no luck. I keep getting errors attempting to use RSD lite. Every time I wipe the data using stock recovery and clockworkMod when I reboot cyanogenMod keeps popping up as if I haven't wiped nothing!!! At this point I'm not sure what my options are anyone out there having trouble going back to stock? I've tried every nightly to see if the (no service) problem goes away but nothing. At this point I'll install any other ROM to get the phone working.

First of all, I hope you get it fixed.  Second of all, never, ever root and flash someone else's phone.    It's their phone -- they need it and may depend on it, and if you screw it up, they'll blame you.

Also -- do animated wallpapers not working for anyone else?  Have _never_ had them working on the Droid2 (at least the ones that come with CM).  A leaked animated wallpaper for the Verizon Vigor worked, but that's it.  The rest of them just show a black screen, with no messages in logcat or anything.

Edited by mdmadph, 17 October 2011 - 04:11 PM.

[misterivanovich]

Currently on nightly 108, though I had this problem with 105 and 103 as well (only nightlies I've used).

The Google Music app (headphone icon, not speaker) is force closing every time I try to actually play a song. It opens the app properly, displays all artists/songs as it should, and immediately after I choose a song to listen to, it closes. I have tried uninstalling the app, reinstalling from the market, and clearing both dalvik and cache after reinstalling... Still nothing. Any ideas?

edit: the problem has since just... Stopped. I was fiddling with Root Explorer to put new notifications and ringtones on my phone, but that's the only noteable thing that I did. I can't imagine that actually fixed anything, but... It works now, so I'm happy! I AM still seeing a lot of issues with the USB connection though, same as everyone else. I'll be testing 110 once it downloads and installs though! :]

Edited by misterivanovich, 18 October 2011 - 02:45 PM.

[pmhesse]

Has anyone tried launching voice dialer with a bluetooth headset? I've been running nightlies for a week. When I use my bluetooth headset (a Jawbone 2) and press the "dial/action" button, the voice dialer launches, says "speak now", then says "goodbye". On the screen you see the voice dialer come up while it says "speak now", then the screen says "Failure / Connection to Bluetooth Device Lost" and sounds a tone (like a busy signal) before going away. Any ideas? Has anyone else tried dialing using bluetooth?

[mdmadph]

pmhesse, on 17 October 2011 - 05:49 PM, said:

Has anyone tried launching voice dialer with a bluetooth headset? I've been running nightlies for a week. When I use my bluetooth headset (a Jawbone 2) and press the "dial/action" button, the voice dialer launches, says "speak now", then says "goodbye". On the screen you see the voice dialer come up while it says "speak now", then the screen says "Failure / Connection to Bluetooth Device Lost" and sounds a tone (like a busy signal) before going away. Any ideas? Has anyone else tried dialing using bluetooth?

Don't have a bluetooth headset, but I'll give my 106 install a test with a Ford Sync system.  I think it might be similiar.

[b00sted415]

mdmadph, on 17 October 2011 - 02:59 PM, said:

First of all, I hope you get it fixed.  Second of all, never, ever root and flash someone else's phone.    It's their phone -- they need it and may depend on it, and if you screw it up, they'll blame you.

Also -- do animated wallpapers not working for anyone else?  Have _never_ had them working on the Droid2 (at least the ones that come with CM).  A leaked animated wallpaper for the Verizon Vigor worked, but that's it.  The rest of them just show a black screen, with no messages in logcat or anything.

Back to square 1 latest nightly installed with device stuck on airplane mode lol!!! At least I can say the device is not bricked . My gf wanted her device rooted so she can tether that's why I rooted her phone. ugh now to try and do more research...

[flyguydip]

PLEASE SOMEONE RELEASE A STABLE BUILD OF 7.1 FOR DROID 2!!!!

[jasonw]

Build 108 working very well for me!

[flyguydip]

Nightly build might be working fine, but the droid 2 is on the list of supported 7.1 devices. Not only isn't there a stable release of 7.1, but not even stable 7, 6, 5, 4...

http://www.cyanogenm...od-7-1-released

What a tease!

[AbsoluteZero]

flyguydip, on 18 October 2011 - 01:24 PM, said:

Nightly build might be working fine, but the droid 2 is on the list of supported 7.1 devices. Not only isn't there a stable release of 7.1, but not even stable 7, 6, 5, 4...

http://www.cyanogenm...od-7-1-released

What a tease!

There was a problem with the build on a few Moto devices that is being looked into. BTW, there wouldn't be a stable 7, 6, 5, 4, etc since D2 wasn't supported at the time of those releases.

[jsmuli2]

I have only one problem so far that I care about - when I use the CM7 custom power-widget on my homescreen - the flashlight part seems to stop working after one or two uses.  I have to delete the widget and re-add it to get it to work again.

So far, the only work around is to just have each individual power option on my home screen, but since I have 5 that I require - and the CM7 widget can have 5 in a row and only take up 4 columns-worth, this would be great to get fixed - if not, no big deal.

In either case - thank you guys so much for all the hard work you do!

b00sted415, on 17 October 2011 - 08:07 PM, said:

Back to square 1 latest nightly installed with device stuck on airplane mode lol!!! At least I can say the device is not bricked . My gf wanted her device rooted so she can tether that's why I rooted her phone. ugh now to try and do more research...

If she has Verizon - the tethering will be monitored and they might charge her.  You can still get her phone to tether without root - like with PDAnet or something similar.

[odd1]

As far as tethering is concerned, my droid 2 works fine with wifi tethering v2.0.7 but my mother's droid x would only work after applying the black hat patch and using the latest beta of wifi tethering.

The black hat patch can be applied to the droid 2 and verizon will never know you are tethering.

Edited by odd1, 18 October 2011 - 09:42 PM.

[omniuni]

I am currently using Nightly 108. This seems to be a really great release, and so far my battery life is good, connectivity is steady, performance is good, and bluetooth seems to be working again.

I am, however, having problems with the live wallpapers; they just don't work at all. Any ideas folks?

Now, on to the Alt-Lock key. I believe part of the problem is that Android does not support an Alt-Lock key; I see a caps-lock listed under the modifiers, but not an alt-lock. I think the simplest solution would be to simply have the alt-lock key send two "alt" key signals, but this would act oddly in some cases. That said, the keyboard driver doesn't look particularly complicated (http://www.kandroid....oard_input.html) but I can't find anywhere that lists the action for the caps-lock key. I suspect that it would be as simple as modifying the driver so that when it receives the keycode for the alt-lock key, it does whatever the caps-lock key does, but with alt instead. Any idea where this code is located?

EDIT:
Scan codes for Alt-Lock and Microphone Keys...
Alt-Lock key gives scancode 125
Microphone Key gives scancode 167

Edited by omniuni, 18 October 2011 - 10:12 PM.