79 replies to this topic

[XE_Nerd]

Currently running the 17JUL2014 nightly release of CM11 for the RAZR HD and they corrected the popping issues with the sound and media over bluetooth is working for me as well with a quick test. Going to run it for a while and I'll post any issues I find if anyone is interested.

[XE_Nerd]

I think WiFi range is worse then earlier builds. When using ART first thing was power button wouldn't lock the phone changed back to dalvick after that. Only issues so far.

[ibolski]

GPS with the 7/17 build was fine. It worked for me using CoPIlot GPS (didn't try Google maps).

 

I'm now on 7/18 and so far things seem good other than WiFi and 4G signal are definitely weaker than stock KK, which is weaker than JB. Hopefully, they'll get that fixed.

 

On earlier builds, pairing my Jawbone Icon headset would cause the phone to seize up when attempting to make calls. 7/18 seems to be working pretty well.

 

WiFi still seems to cut out and the reconnect, even when the WiFi signal is pretty strong.

 

I was able to pair with BlueTooth, as I stated, but I noticed that when it initially happened, my WiFi connection was lost and then it connected back to the WiFi. Both WiFi and Bluetooth then worked fine together. Not sure if it was just another WiFi drop out or if it was caused by BlueTooth.

[XE_Nerd]

Tried to make a phone call today and microphone wouldn't work unless I was on speaker phone

[XE_Nerd]

Dirty flashed the 18JUL2014 nightly and that fixed the microphone issue I had. Still bad battery performance for me. Wifi seems to have improved slightly even before the dirty flash. Just very finicky I guess.

[XE_Nerd]

Yeah, they almost have this ROM sorted out, very smooth and so happy not to have popping noises, I wonder why moto put out such bad quality software lately...

[ibolski]

Yeah, they almost have this ROM sorted out, very smooth and so happy not to have popping noises, I wonder why moto put out such bad quality software lately...

The popping noise wasn't due to bad quality. Not all phones were affected, although with a poll I did on XDA, it seems to be 50/50 between those that had the noise and those that didn't.

 

Here's the commit in the source for CM that fixes the issues: 

Please Login or Register to see this Hidden Content

 

The developer that fixed this issue told me this is very similar to capacitors. Every component has some tolerance, e.g. capacitors of the same nominal value don't have the exact same capacity. So the popping noise may be very subtle on some devices, while it can be rather prominent on other ones.

 

It appears with KK, Motorola changed something in the code that is in the link I posted previously. For some reason, in KK, it affects some phones, which could be phones from a different manufacturing batch. So it's not so much a "bug" as something else.

 

However, the other issues, such as Blue Tooth, etc, is definitely an issue. I do know with the OTA soak test for the original KK release, this was brought up in the private Moto Soak Test forums, so it's sad that went ahead and released it anyways.

 

With the new soak test and upcoming OTA, apparently it's fixed for some, but not all. Also, the weaker WiFi and 4G signal has been reported as well. Again, I'm sure they'll just release this OTA as is, but hopefully, they'll get to work on fixing these issues.

 

At least they didn't snub everyone after the first KK release. I thought for sure that the initial KK release was it, no matter what the issues were, but Motorola went right to work to apply the 4.4.4 security fixes, but I'm also sure they released this OTA to re-patch the unlock bootloader exploit once it was found that they put the exploit back in with the KK update. So, I'm not sure if anything will come after this soak test since they patched the Towelroot and bootloader exploit.

[XE_Nerd]

The popping noise wasn't due to bad quality. Not all phones were affected, although with a poll I did on XDA, it seems to be 50/50 between those that had the noise and those that didn't.

 

Here's the commit in the source for CM that fixes the issues: 

Please Login or Register to see this Hidden Content

 

The developer that fixed this issue told me this is very similar to capacitors. Every component has some tolerance, e.g. capacitors of the same nominal value don't have the exact same capacity. So the popping noise may be very subtle on some devices, while it can be rather prominent on other ones.

 

It appears with KK, Motorola changed something in the code that is in the link I posted previously. For some reason, in KK, it affects some phones, which could be phones from a different manufacturing batch. So it's not so much a "bug" as something else.

 

However, the other issues, such as Blue Tooth, etc, is definitely an issue. I do know with the OTA soak test for the original KK release, this was brought up in the private Moto Soak Test forums, so it's sad that went ahead and released it anyways.

 

With the new soak test and upcoming OTA, apparently it's fixed for some, but not all. Also, the weaker WiFi and 4G signal has been reported as well. Again, I'm sure they'll just release this OTA as is, but hopefully, they'll get to work on fixing these issues.

 

At least they didn't snub everyone after the first KK release. I thought for sure that the initial KK release was it, no matter what the issues were, but Motorola went right to work to apply the 4.4.4 security fixes, but I'm also sure they released this OTA to re-patch the unlock bootloader exploit once it was found that they put the exploit back in with the KK update. So, I'm not sure if anything will come after this soak test since they patched the Towelroot and bootloader exploit.

 

Thanks for so much information. I hope they sort some things out before they roll out the update to everyone. I hope google figures out the kernel killing my battery... at this rate it's going to reduce the life of my phones battery significantly. 

[XE_Nerd]

Running the 22Jul2014 nightly. Has been quite stable all day. WiFi is even par with stock kk, have been running art a few hours without issue

[XE_Nerd]

Haven't tried it, but I've disabled Google search in an effort to save battery

[basixs]

I can indeed confirm that there is a problem with the internal mic, it will work fine until the device is switched to speaker phone then the internal mic no longer works at all (not even sound recorder).  A reboot seems to fix the issue so it must be something with the audio routing (possibly the internal mic is never un-muted).  I only had (or maybe just noticed) this issue after doing the first OTA update, initial load was from completely wiped device.

 

 

 

I've noticed that if I use any of the Music apps and then try Google Voice Search, it says that voice search is temporarily unavailable. Same deal using the stock ROM though. 

I have never noticed this issue but when docked I cannot use the internal mic at all (both Stock and all ROMs).  I wonder if it's related...

 

 

 

I have never experienced the popping issue but I see a couple of people that say their GPS is working fine for them.  It's not for me, on either device; GPS signal is never locked.   Wiping and downloading A-GPS data does nothing, editing GPS.conf does nothing, ( even tried grabbing the GPS.conf file from Stock), reloaded ROM (both clean and dirty over Stock) and no difference.    It's truly maddening...  Does anyone have any advice?  No GPS is kind of a deal breaker for me.

[ibolski]

I can indeed confirm that there is a problem with the internal mic, it will work fine until the device is switched to speaker phone then the internal mic no longer works at all (not even sound recorder).  A reboot seems to fix the issue so it must be something with the audio routing (possibly the internal mic is never un-muted).  I only had (or maybe just noticed) this issue after doing the first OTA update, initial load was from completely wiped device.

 

 

 

I have never noticed this issue but when docked I cannot use the internal mic at all (both Stock and all ROMs).  I wonder if it's related...

 

 

 

I have never experienced the popping issue but I see a couple of people that say their GPS is working fine for them.  It's not for me, on either device; GPS signal is never locked.   Wiping and downloading A-GPS data does nothing, editing GPS.conf does nothing, ( even tried grabbing the GPS.conf file from Stock), reloaded ROM (both clean and dirty over Stock) and no difference.    It's truly maddening...  Does anyone have any advice?  No GPS is kind of a deal breaker for me.

 

Did you attempt to flash back to stock, activate and then obtain a GPS lock there first? Trying to flash back with the same ROM doesn't help.

 

You need to flash back to stock, obtain GPS lock then flash back to CM11.

[racer580]

I just went from stock rom to the 7/24 nightly and I am still having the phone issue. Made a call, microphone worked great. Switched to speaker in that call, that worked. Switched back to microphone off speaker and the other person can't hear me. Speaker continues to work but regular microphone doesn't at all.

 

I seem to also have this issue, however its not always a result of turning speaker phone on and off. Sometimes its just random and the other person can't here me as soon as the call connects. Has anyone had any luck fixing this issue? Running the 7/29 nightly, but this has been an issue for me since the original cm11 flash of the 7/10ish nightly I believe.  

[basixs]

Did you attempt to flash back to stock, activate and then obtain a GPS lock there first? Trying to flash back with the same ROM doesn't help.

 

You need to flash back to stock, obtain GPS lock then flash back to CM11.

Thanks ibolski!.  That is definitely the issue.  I have seen this tip but was following a guide that did not mention it.  I guess it's pretty important.

[ibolski]

Just to let everyone know why you must flash back to stock to fix GPS, kabaldan on XDA (who works on the CM sources but not for XT926 since he doesn't have one) explains why this is necessary:

 

 

There's a GPS engine lock (security feature) implemented by Moto.
When you enable GPS on stock firmware, GPS engine becomes unlocked and GPS requests can be answered by modem (via QMI interface). When you disable GPS on stock, the engine becomes locked and any GPS requests will be silently ignored.

GPS HAL libraries used in CM11 moto_msm8960 builds for kk bootloader are not able to unlock the engine.

If you've had GPS disabled on stock firmware before you flashed a custom ROM, the engine stays locked and GPS won't work for you.

 

[XE_Nerd]

Thanks. I've always used GPS on my phone and always leave it enabled so just happened not to run into this issue.