Related
I just wanted to share something that I found the hard way.
The Mute is NOT working if you are using Bluetooth with a CM7 based ROM.
I actually am using EB 2.4 ROM and I was listening to a conference call with my Bluetooth headset with the Mute selected on the phone when I got an e-mail from a colleague telling me to mute my phone
This issue is already listed in the cyanogenmod project page as issue# 4439.
I just wanted to let people know of this bug and hopefully be saved from some embarrassing moments.
UPDATE:
The issue happens in all CM based ROMs that I have tested so far, including the beta ICS CM9 ROMs
J-C.Martin said:
I just wanted to share something that I found the hard way.
The Mute is NOT working if you are using Bluetooth with a CM7 based ROM.
I actually am using EB 2.4 ROM and I was listening to a conference call with my Bluetooth headset with the Mute selected on the phone when I got an e-mail from a colleague telling me to mute my phone
This issue is already listed in the cyanogenmod project page as issue# 4439.
I just wanted to let people know of this bug and hopefully be saved from some embarrassing moments.
Click to expand...
Click to collapse
Interestingly enough it does not work in CM9 either. Tried the build, love it but hate the missing mute function.
mansa_noob said:
Interestingly enough it does not work in CM9 either. Tried the build, love it but hate the missing mute function.
Click to expand...
Click to collapse
That's too bad. I was hoping it would've been fixed on CM9.
Oh well. Just need to keep being careful and using the mute feature of the conference itself, instead of the phone.
BTW if you don't have an issue downgrading you can go to 2.3.3 and the problem goes away.
A BT connect problem may arise (as for me) but still worth a shot.
Sent from my LG-P999 using XDA App
J-C.Martin said:
I just wanted to share something that I found the hard way.
The Mute is NOT working if you are using Bluetooth with a CM7 based ROM.
I actually am using EB 2.4 ROM and I was listening to a conference call with my Bluetooth headset with the Mute selected on the phone when I got an e-mail from a colleague telling me to mute my phone
This issue is already listed in the cyanogenmod project page as issue# 4439.
I just wanted to let people know of this bug and hopefully be saved from some embarrassing moments.
Click to expand...
Click to collapse
I think I remember something about the CM team saying bluetooth will never fully work, they had to do a workaround just to get bluetooth headsets working in the first place. Also, you should update your Eaglesblood build, 2.8 has some nice new things.
IRASadPanda said:
I think I remember something about the CM team saying bluetooth will never fully work, they had to do a workaround just to get bluetooth headsets working in the first place. Also, you should update your Eaglesblood build, 2.8 has some nice new things.
Click to expand...
Click to collapse
That's too bad. I was hoping to hop on the ics as soon as this issue got fixed .
Sent from my LG-P999 using XDA
Ping... CM7 issue #4439 is marked as fixed. If you have the bandwidth please try and spread the word if fixed.
This is great news but my wife broke her Amaze 4G and is currently using my G2X so I am phone < and hence can't try myself :crying:.
mansa_noob said:
Ping... CM7 issue #4439 is marked as fixed. If you have the bandwidth please try and spread the word if fixed.
This is great news but my wife broke her Amaze 4G and is currently using my G2X so I am phone < and hence can't try myself :crying:.
Click to expand...
Click to collapse
I've seen the new status, I've not tested yet because I'm not sure if I need the new baseband with CM7.2 or not....
I'm affraid of trying to install the new baseband and mess up my current ROMs.
Thanks for following this issue.
Mute when on Bluetooth still not working
I am a very new and mostly very happy CM7 user with an LG G2X that was in desperate need of getting off of the stock ROM. I did the installation last night and just found out the hard way that my mute button does not work when I'm on my bluetooth headset. I came across this thread when searching for a remedy.
I'm not sure if my exhibiting the bug confirms that it still exists, or if there are other files/etc. that I need to upgrade or swap out. (i.e. radio, etc.) that did not come with my download last night.
My details:
Android 2.3.7
Baseband M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
Kernel 2.6.32.55-cyanogenmod [email protected]) )
Mod version CyanogenMod-7.2.0-p999
Build date Fri Jun 15 19:45:03 PDT 2012
Build number GWK74
Any advice/assistance would be greatly appreciated! Thanks!
wolfe42 said:
I am a very new and mostly very happy CM7 user with an LG G2X that was in desperate need of getting off of the stock ROM. I did the installation last night and just found out the hard way that my mute button does not work when I'm on my bluetooth headset. I came across this thread when searching for a remedy.
I'm not sure if my exhibiting the bug confirms that it still exists, or if there are other files/etc. that I need to upgrade or swap out. (i.e. radio, etc.) that did not come with my download last night.
My details:
Android 2.3.7
Baseband M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
Kernel 2.6.32.55-cyanogenmod [email protected]) )
Mod version CyanogenMod-7.2.0-p999
Build date Fri Jun 15 19:45:03 PDT 2012
Build number GWK74
Any advice/assistance would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
7.2 stable: the problem still exists.
Sent from my LG-P999 using xda app-developers app
Ive never seen anywhere where it stated tht bluetooth did work correctly on CM7 roms.
On a BT note, I'm typing this with an Apple BT Keyboard paired to my G2x, go figure...lol
What works and what don't!
Sent from my pimped LG G2x temasek build 135.1 w/Trinity Kernel --The Best G2x GB Solution
Any resolution in sight?
mansa_noob said:
7.2 stable: the problem still exists.
Click to expand...
Click to collapse
Thanks for confirming. Any resolution in sight or work-around to get it to work right?
wolfe42 said:
Thanks for confirming. Any resolution in sight or work-around to get it to work right?
Click to expand...
Click to collapse
Yeah. Before v21y I was running Weapon and now running stock 2.3.4.
Bluetooth mute is more important for me than a ROM
Sent from my LG-P999 using xda app-developers app
Actually just found out that blueant Bluetooth headsets can be muted by holding vol+ and vol- for 3 seconds... go figure.
You may want to check your headset manual too.
Sent from my LG-P999 using xda app-developers app
Hi guys,
Since about a month, my Nexus S sometimes (often) does not allow me to answer the phone when it rings : I can see the caller, I have the buttons to answer, the screen is animated as intented, but the phone does not accept any input from me, as if the "touch" part of the screen were desactivated.
I have to lock and unlock it to be available to answer.
I have this phone since may, and it happens since about a month
I had this issue with MIUI ans ICS (kwiboo v3, with franco kernel)
I've experienced this on nscollab as well. Running latest Glados kernel, if that helps. Not annoying enough to get me to change though.
Sent from my Nexus S using Tapatalk
Having that problem too on stock rom!
Have to turn off and on the phone to answer a call...
BillWieGates? said:
Having that problem too on stock rom!
Have to turn off and on the phone to answer a call...
Click to expand...
Click to collapse
confirm: push power button 2 times
Happend to me on Oxygen ROM with Franco kernel and on CM9 ICS.
uansari1 said:
I've experienced this on nscollab as well. Running latest Glados kernel, if that helps. Not annoying enough to get me to change though.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
No, it does not bother me so much, but if I take time to answer, I may miss a call...
Just have discovered that this has been already posted several times to the Android Issue database:
code.google.com/p/android/issues/detail?id=13853 (Jan 8, 2011)
code.google.com/p/android/issues/detail?id=18377 (Jul 10, 2011)
code.google.com/p/android/issues/detail?id=18454 (Jul 12, 2011)
To give it some priority, you should "star" the issue (without posting simple "me-too" messages).
Hope it will get fixed, as it is quite annoying... maybe with ICS!
I still have the issue with official ICS.
An answer has been posted on one of the tickets :
Starting to suspect static electricity.
The unresponsive areas of the display usually works fine after a "close-steamy-breath". Like the one you do before wiping the display clean. Another thing that works on my Nexus S (both 2.3.x & 4.0.3) is to wait without touching the display for 6+ seconds.
Click to expand...
Click to collapse
I'm not really conviced, since everything works just with a lock/unlock, but I'm not a specalist...
Installed the most recent nightly Jellybean for Verizon. Seems stable but I notice what seems to be degraded sound quality on phone calls. Anyone else having that issue?
Can someone more experienced recommend a better (or preferred build)?
Thanks,
Stormer1981 said:
Installed the most recent nightly Jellybean for Verizon. Seems stable but I notice what seems to be degraded sound quality on phone calls. Anyone else having that issue?
Can someone more experienced recommend a better (or preferred build)?
Thanks,
Click to expand...
Click to collapse
You can't expect nightly builds to be stable- they will and do have issues with various things.
The vast majority, if not every single AOSP ROM for the SGS3 uses all of (or a good chunk) of CyanogenMod's code, which is why you see so many of the same bugs between builds that are rarely fixed until someone submits to CyanogenMod's Gerrit.
I can't comment on your specific issue, just posting some food for thought.
A lot of people have posted about echoes or low volume on the CM10 builds. I don't make many phone calls so I don't know if this affects every phone running CM10. But I'm sure it does to various extents. They will work it out in the coming weeks as they work toward a stable build.
Sent from my SCH-I535 using Tapatalk 2
the echo seems to be gone in the 8/31 build
use this thread to ask questions about it
http://forum.xda-developers.com/showthread.php?t=1840414&page=140
Preferred Build
Is there a stable build other than the nightlies? If so where would I find it?
Stormer1981 said:
Is there a stable build other than the nightlies? If so where would I find it?
Click to expand...
Click to collapse
I'd check the development forum or the nightly thread.
Sent from my Galaxy S III
ripken204 said:
the echo seems to be gone in the 8/31 build
use this thread to ask questions about it
http://forum.xda-developers.com/showthread.php?t=1840414&page=140
Click to expand...
Click to collapse
Agreed
Sent from my SCH-I535 using Tapatalk 2
No echo here. I just flashed to the 9/1/2012 nightly from stock.
Did you try playing with the call settings? I have noise suppression enabled and voice privacy disabled.
I actually have a similar problem (can't post on official thread yet).
I have trouble with my headset volume.
If i plug it in DURING a call, I cant hear anything and can't do anything to adjust the volume.
If i plug it in BEFORE a call, it's fine.
Any clues as to whats going on or any suggestions on how to fix it?
Paranoid android Sept 2nd build seems to work nice, i think it works better than the CM10 builds even though its based off it. You can also mess around with tablet mode!
Let's get the echo fixed and the roaming issue fixed and the forum will flock to these roms. Till then I would beware.
Sent from my SCH-I535 using xda premium
I just flashed CM10 09/04 nightly and I am still getting the 3 second In call delay, I am still getting echo on speaker phone and I am still getting my voice navigation only say " in a half mile" Nothing else, No one seems to even mention this in the official CM10 forms. and No its not a half mile from my house to the end of my street , its like less than 1000 ft. Everything else seems to work good but the delay and the echo are very annoying so I am going back to the build that worked best for me cm10 08/22
Defragger51 said:
I just flashed CM10 09/04 nightly and I am still getting the 3 second In call delay, I am still getting echo on speaker phone and I am still getting my voice navigation only say " in a half mile" Nothing else, No one seems to even mention this in the official CM10 forms. and No its not a half mile from my house to the end of my street , its like less than 1000 ft. Everything else seems to work good but the delay and the echo are very annoying so I am going back to the build that worked best for me cm10 08/22
Click to expand...
Click to collapse
Same results here for 904. The other forum mentions that an unofficial build has the incoming call delay fixed, though, so I'm hoping the fix shows up when the official 905 ROM comes out.
Headphones with mic not working
I'm running the 9/2 build and when I plug the stock headphones with mic into the phone I cannot talk or hear phone calls through it. No issue with music. Screen flickers when using keyboard (Swiftkey). Volume control in call doesn't seem to work. There is also a 5 second delay when I answer a call to when I can hear the other person or they can hear me. Same delay with speaker phone.
At least the damn echo is gone though :good:
Can anyone confirm whether or not the dock audio is working on recent CM10 builds? I've tried searching the thread and have done everything short of just flashing it to see.
Thanks for your replies!
The dock audio was still not working for me on the CM10 from 9/5.
landtuna said:
The dock audio was still not working for me on the CM10 from 9/5.
Click to expand...
Click to collapse
You are correct. Just tried it myself. This is the main thing holding me back from CM10. I'm going to attempt to add it in myself. We'll see what happens.
9/5 build seems to be very solid. No data issues or call issues. Cannot comment o no the dock audio though. Make sure you aren't doing dirty flashes, there have been tons of issues with dirty flashing.
Sent from my SCH-I535 using xda app-developers app
This is why I switched to ParanoidAndroid. It is Jellybean and far more stable than the current CM10. If you want Jellybean right now~ I highly recommend PA. If you really like CM, still, try PA~ it will help you wait for the official CM10 release. I actually don't see a need to go CM10 tbh. PA is wonderful.
Krystalmyth said:
This is why I switched to ParanoidAndroid. It is Jellybean and far more stable than the current CM10. If you want Jellybean right now~ I highly recommend PA. If you really like CM, still, try PA~ it will help you wait for the official CM10 release. I actually don't see a need to go CM10 tbh. PA is wonderful.
Click to expand...
Click to collapse
I'm going to give PA a try... I am still having serious issues with CM10, hope they will be fixed with PA
I have an occasional issue where my phone is dialing a number but I cannot hear the ringing, and once it connects there is no sound either way.
Sometimes if I reboot the phone will work again - but other times I need to reboot several times before it seems to start working again.
Obviously this is a huge problem as I use this phone for business...any suggestions on how I can diagnose this?
lirong said:
I have an occasional issue where my phone is dialing a number but I cannot hear the ringing, and once it connects there is no sound either way.
Sometimes if I reboot the phone will work again - but other times I need to reboot several times before it seems to start working again.
Obviously this is a huge problem as I use this phone for business...any suggestions on how I can diagnose this?
Click to expand...
Click to collapse
Which version of which build are you using? There was a well-documented (and very annoying) bug in CM for a while that affected in-call audio. This has been addressed in more recent builds and seems to have been eliminated. A little more information will make it easier to help you.
mrfeuss said:
Which version of which build are you using? There was a well-documented (and very annoying) bug in CM for a while that affected in-call audio. This has been addressed in more recent builds and seems to have been eliminated. A little more information will make it easier to help you.
Click to expand...
Click to collapse
Thanks...sorry for that ommission.
I am using vincom's Superlite CM10.
lirong said:
Thanks...sorry for that ommission.
I am using vincom's Superlite CM10.
Click to expand...
Click to collapse
I've had this problem with all kinds of roms (stock, custom, aosp, etc). Sometimes it happened more often sometimes less. I've even had this happen to me on three different phones (SE x8, i9100 and i727r). Most often it happens with CM7, CM9 and CM10. But it did and does also happen with official roms. I'm on the Rogers JB now and it still happens, but relatively rare. This has been discussed before and with no result. Apparantly this is a common android issue..
Same issue talked about here:
http://forum.xda-developers.com/showthread.php?t=2164921
http://forum.xda-developers.com/showthread.php?t=2168656
I had such problem too and hadn't found the reason.
Anyway, after I flashed UXUMA7 radio, I haven't experienced it any more.
I just had this issue today. I've been running cm 10.1 m snapshot since Friday using the phone no problems. Last hour of work my wife calls no audio during call. I then wiped the cache partition and devik cache nothing. Came home did a full wipe and now its fine. I don't know don't know what happened. I think I may find a different ROM if this happens again
Sent from my Nexus 7 using xda app-developers app
livefree79 said:
I just had this issue today. I've been running cm 10.1 m snapshot since Friday using the phone no problems. Last hour of work my wife calls no audio during call. I then wiped the cache partition and devik cache nothing. Came home did a full wipe and now its fine. I don't know don't know what happened. I think I may find a different ROM if this happens again
Click to expand...
Click to collapse
The last m release that I know of (I haven't been on straight CM for a few weeks) was released before a commit that fixed the no in-call audio bug. I'd read through the thread and look to see which nightly has been the most stable, if I were you. If you do decide to switch to another ROM I can personally vouch for Sons of Android or Slim Bean (onlychevys has an unofficial build out).
I have since switched to Embryo and, so far (hope I didnt just jinx myself) I have not experienced this issue.
lirong said:
I have since switched to Embryo and, so far (hope I didnt just jinx myself) I have not experienced this issue.
Click to expand...
Click to collapse
Embryo is tw, doesn't have the issue
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I am building this for my general use and thought it would be nice to share. Just to be clear I am not developing anything just making the builds. I dirty flashed over CM12.1 and flashed the latest GAPPS with no problems. Please do not report problems as this is a nightly build and unofficial.
Official builds are out and can be found here...
https://download.cyanogenmod.org/?device=d850
I used the 6.0 micro build gapps from here
http://opengapps.org/
SupaAvenger79 said:
I am building this for my general use and thought it would be nice to share. Just to be clear I am not developing anything just making the builds. I dirty flashed over CM12.1 and flashed the latest GAPPS with no problems. Please do not report problems as this is a nightly build and unofficial.
I used the 6.0 micro build gapps from here
http://opengapps.org/
Nightly Build available here..
https://drive.google.com/folderview?id=0B4rZYkaJF5V0Z3RlR08yclZiVUE&usp=sharing
Click to expand...
Click to collapse
Thanks for sharing!
What is your experience so far with GPS locking & using Google Maps navigation?
crash4fun said:
Thanks for sharing!
What is your experience so far with GPS locking & using Google Maps navigation?
Click to expand...
Click to collapse
It's broke on my end. It can get a position lock but does not seem to track for driving directions. Another bug I discovered was trying to take a picture in a text message and the camera only showing 1 to 2 frames per second, but the regular camera works fine so I assume it has something to do with the text message app. I still use it as a daily driver don't use the driving directions often. I will keep posting the builds as I make them and let you know when that bug is fixed.
[Thanks! Will definitely follow this until CM puts out an official build. Couple other guys that were building unofficial seem to have stopped for the time.
SupaAvenger79 said:
It's broke on my end. It can get a position lock but does not seem to track for driving directions. Another bug I discovered was trying to take a picture in a text message and the camera only showing 1 to 2 frames per second, but the regular camera works fine so I assume it has something to do with the text message app. I still use it as a daily driver don't use the driving directions often. I will keep posting the builds as I make them and let you know when that bug is fixed.
Click to expand...
Click to collapse
Ah, yes it appears to get a lock for me as well, but then won't navigate. I've tried messing with gps.conf in several different manners but no luck.
I'm about to abandon the G3 because there is no official CM support. This is where Cyanogenmod is getting bad press - they claim to offer an alternative OS with the latest updates, but some phones are just left in the dust because no one wants to be the maintainer. Best Buy has started selling the 6P - may head over and pick this up!
Please post a link to the kernel source of the kernel included in your build as per GPLv2 and XDA requirements.
Thanks! And thanks for your contributions.
KennyG123 said:
Please post a link to the kernel source of the kernel included in your build as per GPLv2 and XDA requirements.
Thanks! And thanks for your contributions.
Click to expand...
Click to collapse
Sure thing
https://github.com/CyanogenMod/android_kernel_lge_g3
Still using this everyday but, as I'm sure you noticed, charging has been majorly borked since 12/23. Hope you keep this up and I'll be watching CM changelogs for a fix. GPS would be nice too!
scsgoal31 said:
Still using this everyday but, as I'm sure you noticed, charging has been majorly borked since 12/23. Hope you keep this up and I'll be watching CM changelogs for a fix. GPS would be nice too!
Click to expand...
Click to collapse
Yeah I am hoping the problems are not D850 specific or we will never see a fix. I will keep posting builds semi nightly until CyanogenMod starts posting an official build or until I get a new phone in August. I really think this is still a good phone and wonder why the community went to hell on this one.
Have a Happy New Year everyone.
I've been using CM13 for almost a month and its been great. However I only just got an SD card for Christmas. Now, I'm assuming moving apps to the SD card has changed since it let's you format as internal storage now. However that doesn't work for me. Does anyone know how to move apps to the SD card without formatting it as internal storage?
How did you build this? I've managed to build CM13 for the D850 too, but the result was the phone freezing at the LG bootup logo. Your build seems to work perfectly fine.
slabity said:
How did you build this? I've managed to build CM13 for the D850 too, but the result was the phone freezing at the LG bootup logo. Your build seems to work perfectly fine.
Click to expand...
Click to collapse
Ummm well I don't know what you did wrong, but here are the resources I used...
Dependencies for the build were grabbed from this site
https://source.android.com/source/initializing.html
Then I made a local manifest to include proprietary drivers from https://github.com/TheMuppets along with the branch for the D850 out of cyanogenmod github. Hope that gives you some clues on what went wrong.
SupaAvenger79 said:
Ummm well I don't know what you did wrong, but here are the resources I used...
Dependencies for the build were grabbed from this site
Then I made a local manifest to include proprietary drivers from TheMuppets along with the branch for the D850 out of cyanogenmod github. Hope that gives you some clues on what went wrong.
Click to expand...
Click to collapse
Strange. That's exactly what I did too.
I'll give it another shot and see what's going on. I'd like to take a crack at fixing some of the bugs.
Looks like tonight's build will fix the power charging issues. Yay!
Just posted the the 12/29 build and GPS is fixed we can now find our nearest Hardee's with ease. Thanks @invisiblek
is anyone else experiencing data loss constantly? I have to disable/re-enable data to get it to connect, otherwise I get (!) instead of (LTE). I haven't seen anyone else complain about this and yet it still hasn't been fixed on the 12/31/15 build. D850 stock CM kernel on T-Mobile, only one APN on my list. it happens on any CM13-based ROM.
also this new kernel makes my phone near flawless. it feels much more like a nexus. however it is still shutting down the phone when it overheats, hence when you first install the rom and it creates the cache, it will power off once the setup starts.
Sent from my LG-D850 using Tapatalk
xVermicide said:
is anyone else experiencing data loss constantly? I have to disable/re-enable data to get it to connect, otherwise I get (!) instead of (LTE). I haven't seen anyone else complain about this and yet it still hasn't been fixed on the 12/31/15 build. D850 stock CM kernel on T-Mobile, only one APN on my list. it happens on any CM13-based ROM.
also this new kernel makes my phone near flawless. it feels much more like a nexus. however it is still shutting down the phone when it overheats, hence when you first install the rom and it creates the cache, it will power off once the setup starts.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
I had data problems too on Tmo, a quick APN adjustment fixed it:
https://support.t-mobile.com/thread/95900?start=0&tstart=0
thanks, I applied the changes so I'll see if I have anymore problems. if not then this 13 is my new daily driver.
Sent from my LG-D850 using Tapatalk
Just flashed, great so far! Thanks OP!
Sent from my LG-D850 using Tapatalk