What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[ROM] [KEXEC] JB ROMS For Droid 3 [03/06: BT/SPEAKERPHONE FIX]

Maybe I missed something in an earlier post. I thought I read that cameras were working in this build. I tried this rom today and found the following not working:
- no cameras whatsoever
- no wifi (says is on but is not)
- no bt
- play store crash, even after reflash of gapps

Is this consistent with what others have been experiencing?
 
Maybe I missed something in an earlier post. I thought I read that cameras were working in this build. I tried this rom today and found the following not working:
- no cameras whatsoever
- no wifi (says is on but is not)
- no bt
- play store crash, even after reflash of gapps

Is this consistent with what others have been experiencing?

I believe cameras have been a no go all along.
Wifi worked for me fine
Not sure on BT as I don't use it
No issues with the Play store for me. What gapps are you using??

Sent from my DROID3 using Tapatalk 2
 
Maybe I missed something in an earlier post. I thought I read that cameras were working in this build. I tried this rom today and found the following not working:
- no cameras whatsoever
- no wifi (says is on but is not)
- no bt
- play store crash, even after reflash of gapps

Is this consistent with what others have been experiencing?
  • Camera is a known issue.
  • WiFi is funny. If you're doing MAC address filtering you may be running into what I did. The MAC address is changed by this code. I don't know how or why. (Not that MAC address spoofing is particularly difficult, I just don't understand why this code is doing it.) For reference, my MAC address was changed from stock to d4:94:a1:f2:58:d2. I'm curious if everybody gets the same thing or it's random. I am consistently getting this MAC address, however.
  • My bluetooth works fine. Try clearing cache or defaulting the phone. Might need to re-pair.
  • Never had a problem with play store. Might want to try reloading it from a backup. Again, might need to clear cache or default the phone.
I also occasionally lose functionality with the slider keyboard. A reboot resolves it. I think that's a known issue as well.

Good luck.
 
Thanks for the quick responses. I suppose another question is what gapps "should" I be using and where should I get them? I reflashed gapps from March ( gapps-ics-20120317-signed.zip) which I have been using with the cm9 rom and that didn't work. I also dl'd the most recent from goo.im and that didn't work either. For each, playstore opens but immediately fc's.
 
Last edited:
Thanks for the quick responses. I suppose another question is what gapps "should" I be using and where should I get them? I reflashed gapps from March ( gapps-ics-20120317-signed.zip) which I have been using with the cm9 rom and that didn't work. I also dl'd the most recent from goo.im and that didn't work either. For each, playstore opens but immediately fc's.

I'm using gapps-ics-20120429-signed.zip

Grabbed it from Directory index · styled with h5ai
 
These are the gapps I've been using for a while with no issues on any ICS build.

ICS_MOTO_4.0.4_GAPPS_02_17_2012.zip

Can't remember where I got them though

Sent from my DROID3 using Tapatalk 2
 
Installed this morning. Seems fine. My phone still gets into a reboot loop when it's plugged in to a charger, but now when I unplug it the stock image boots. I probably have something else weird going on.

The something else weird going on is I'm an idiot who can't follow directions. Needed to go back to unsafe and install there. And probably would have helped to have a copy of the .apk that wasn't corrupt.

Working great now. And the new flash screen is cute.
 
Is there any (approx)planned release date for final version of this ROM? :greendroid:
While I do not speak for the developer, my industry experience would indicate that while the ROM is still in "Alpha" you probably shouldn't expect an answer. When it gets to "Beta" you'll be closer. (Unless these ROMs are always in Alpha then I don't know squat.)
 
While I do not speak for the developer, my industry experience would indicate that while the ROM is still in "Alpha" you probably shouldn't expect an answer. When it gets to "Beta" you'll be closer. (Unless these ROMs are always in Alpha then I don't know squat.)

Most ROMs go Alpha/Beta/RC/Final. Its rare for anyone other than testers to get the ALpha builds, so credit to Hashcode for letting us all enjoy some ICS.

And yes, until it gets to AT LEAST beta, don't expect ETA projections. (and as a rule you should never ask for one anyways :p)
 
Back
Top