Related
Not sure if this should go in the CM Q&A since it is CM9 not CM7.
I'm using the unoffical CM9 ROM (I would post in that section, but it doesn't allow first time posters in a dev thread). I just wanted to know if anyone else is experieceing issues with google voices' visual voicemail not working in the dialer. It's a new feature in ICS. I can click play next to the missed call and it goes to the right screen, but it either is not playing the message or its got no audio. Probably just a bug, just wasn't sure if it is a common one amongst CM9 roms.
Thanks
Yea it doesn't work for me either. But it has never worked for me in any of ics. Not sure if it will work in GB.
Sent from my Inspire 4G
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
http://www.cyanogenmod.com/blog/cyanogenmod-10-m1
Something we have learned over the past few months is that if you don’t release, someone else will do it for you. Since we are open-source, we absolutely encourage it! Unfortunately, the quality of unofficial builds can vary, and we are serious about quality. Of course nightlies are always available, but we realized that having something that is a bit more stable on a more frequent basis is important. Starting now, we are rolling out our M-Series releases. M-Series builds will be done at the beginning of every month. We did a soft freeze of the codebase for the last week, blocking new features in order to stabilize. Our plan is to continue this (assuming that the response is good) up until stable release, and onward.
We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
M-Series builds will be available under the EXPERIMENTAL tag. The filename will include the date stamp as well as the M version. These builds should be stable enough for daily use, and we encourage feedback and bug reports.
Tonight’s M1 build is available for these devices:
Galaxy Nexus GSM (maguro)
Galaxy Nexus VZW (toro)
Galaxy Nexus Sprint (toroplus)
Galaxy S2 GT-I9100G (i9100g)
Galaxy S (galaxysmtd)
Galaxy S B (galaxysbmtd)
Captivate (captivatemtd)
Galaxy S3 Sprint (d2spr)
Galaxy S3 VZW (d2vzw)
Galaxy S3 AT&T (d2att)
Galaxy S3 TMO (d2tmo)
Galaxy S3 US Cellular (d2usc)
Nexus S (crespo)
Nexus S 4G (crespo4g)
Galaxy Note AT&T (quincyatt)
Google Nexus 7 (grouper)
Sony Xperia Acro S (hikari)
Sony Xperia S (nozomi)
In standard CM style, we will continue to add devices as time goes on up until our stable release.
Head over to Get.CM to grab the latest build for your device. Installation instructions and other documentation can always be found at the CM Wiki and help is always close at hand over on our official forums.
Happy flashing!
http://get.cm/?device=&type=nightly
Downloading now.
GS3
This is interesting, will try. I do wonder if this differs much from other available builds we have except now it will be frozen for a month. Presumably those cleanups have already appeared in other builds? Maybe someone more knowledgeable about how that works can say. I do think it's a good idea.
Sent from my SCH-I535 using Tapatalk 2
Hmm. Interesting and I think it's a great idea but looking at the builds the experimental M1 and the latest nightly look to be the same size. Maybe it's supposed to be this way?
Sent from my SCH-I535 using Tapatalk 2
niv3d said:
Hmm. Interesting and I think it's a great idea but looking at the builds the experimental M1 and the latest nightly look to be the same size. Maybe it's supposed to be this way?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, maybe they tweaked a few things and said that's that.
GS3
blestsol said:
Yeah, maybe they tweaked a few things and said that's that.
GS3
Click to expand...
Click to collapse
PLEASE DELETE
Well unfortunately I can't run AOSP as a stable DD until the RIL is fixed :/ I know it's being worked on. But I'm constantly in a 3/4G area
EDIT: I am so incredibly sorry that this post got under someone's skin and "cluttered" a thread.
Sent from my SCH-I535 using Tapatalk 2
thanks for the linkage, updated OP in Official Cm thread although I feel someone should branch off a M1 discussion thread as it will very greatly from the Official Nightly and the UnOfficial Nightly builds.
http://forum.xda-developers.com/showthread.php?t=1840414
If someone cares to maintain the M1 thread and starts it let me know and I will link to it from the Nightly thread
niv3d said:
Well unfortunately I can't run AOSP as a stable DD until the RIL is fixed :/ I know it's being worked on. But I'm constantly in a 3/4G area
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
We dont need to hear you whine about how your area sucks. Please refrain from cluttering threads, all I ask.
tonu42 said:
We dont need to hear you whine about how your area sucks. Please refrain from cluttering threads, all I ask.
Click to expand...
Click to collapse
Can you refrain from tossing napalm at the dude? Peaceful little discussion thread.
GS3
tonu42 said:
We dont need to hear you whine about how your area sucks. Please refrain from cluttering threads, all I ask.
Click to expand...
Click to collapse
EDIT: Never mind I have better things to do with my time
Sent from my SCH-I535 using Tapatalk 2
Anyone know how to get the volume of either the monthly or nightly releases to work?
I don't mean the regular volume, I mean when recording video the volume is almost non-existent. It's very frustrating and I can't seem to find a fix, every AOSP ROM I've tried here is the same story as far as that.
I can record fine on a TW ROM so I know it's not a hardware problem.
Anyone else try the m1 yet? Any other issues besides data and volume while video recording? I've been waiting for a release candidate but it looks like this is the closest thing for a while so I wanna flash but still nervous cause I'm a noob ):
exoteric said:
Anyone else try the m1 yet? Any other issues besides data and volume while video recording? I've been waiting for a release candidate but it looks like this is the closest thing for a while so I wanna flash but still nervous cause I'm a noob ):
Click to expand...
Click to collapse
havent had data issues myself, volume while recording? i guess audio is kinda quiet while playing back videos, but i dont use it so im stocked that the "take image while recording" feature works
niv3d said:
PLEASE DELETE
Well unfortunately I can't run AOSP as a stable DD until the RIL is fixed :/ I know it's being worked on. But I'm constantly in a 3/4G area
EDIT: I am so incredibly sorry that this post got under someone's skin and "cluttered" a thread.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for talking about the 3g issue, I appreciate the roms everyone is making and modding but I think they need to tone down the mods that are trivial and concentrate on more major bugs. So ya I'd prefer fixing dropping 3g every 5 minutes to fixing a blue tooth bug that only happens when the third moon of Jupiter lines up with Plutos dark side of the planet during a tornado. Can't wait to try this rom
Sent from my Galaxy S III
M series build fixed the speakerphone echoing problem for me
CM10 M1
Flashed CM10 M1 3 days ago, came from Synergy 1.7 ICS ROM and have the latest radio VRLG1. Did a clean wipe and restored Apps w/Data using Titanium Backup.
All seems to working fantastic, great speed and smoothness to this ROM, battery life seem as good as stock or Synergy. Haven't noticed any data issues, volume on phone calls is good.
Minor issues, after flashing had to reboot twice to get past data activiation, and Trebuchet seem to have a little problem and kept closing. Load Nova as my launcher (it was my launcher on Synergy) and have had no issues since.
Yea I mentioned in official release thread my impressions but in case anyone is following this..I've had excellent experience. No real errors to speak of. It's a true stable build for me. Love it.
Hi all,
I am tying to figure why my particular bluetooth device just refuses to work with CM10. (BluAnt S4)
I have tried all different versions of CM10 here, as well as the vincom's audio bluetooth fix, to no avail.
Since I have to use it in my car, because of the laws around here, I would like to know anyone else has a working fix for this.
My same device works very well with my girlfriends nexus s CM10 setup.
I get it to ring when I call, but cannot talk/listen to the other party, and they cant hear me. It does show that it is connected, and paired.
I keep reverting back to my backup of CM9 for my daily driver.
Thanks
Heeter
Heeter said:
Hi all,
I am tying to figure why my particular bluetooth device just refuses to work with CM10. (BluAnt S4)
I have tried all different versions of CM10 here, as well as the vincom's audio bluetooth fix, to no avail.
Since I have to use it in my car, because of the laws around here, I would like to know anyone else has a working fix for this.
My same device works very well with my girlfriends nexus s CM10 setup.
I get it to ring when I call, but cannot talk/listen to the other party, and they cant hear me. It does show that it is connected, and paired.
I keep reverting back to my backup of CM9 for my daily driver.
Thanks
Heeter
Click to expand...
Click to collapse
Had the same issue, moved on to AOKP though that's not a resolve to CM10 but it's a fix for me since car BT is practically essential.
Thanks for that, which aokp based ROM do you use?
Heeter
Sent from my SAMSUNG-SGH-I727 using xda premium
Does any other BT device work?
Did you try the 9/18 cm10 unofficial nightly? The 9/18 nightly works flawlessly.
When you flash are you formatting system? I always format system on nightly as things seem to work better\
here is the link to the 9/18 build http://builds.redpepperracing.com/u...tory=rpr&PHPSESSID=4d6a6fgjqn8d05c0nt03qmjpg0
jb apps http://builds.redpepperracing.com/u...tory=rpr&PHPSESSID=4d6a6fgjqn8d05c0nt03qmjpg0
I had official CM9 stable and yes confirm BT does work.
As for my current AOKP I was using the one post by R4INS, I found out last night there was an update see http://goo.im/devs/R4INS (the latest Sep-14-2), I haven't tried the BT on that update yet though I can confirm Sep 9 version worked link http://forum.xda-developers.com/showthread.php?t=1831858. On Sep 9 you will still need to flash policy conf. fix posted by vincom to fix the music output in car, but the BT phone talk always worked without any issues.
***edit*** officially confirmed sep 14 update BT didn't work, in reverting to sep 9
I do not have access to any other BT device at this time. I did a completely fresh install of cm10 nightly 9/18 and later. BT never worked. I have just installed AOKP (ortheus) and my BT is now working.
Heeter
Sent from my SGH-I727 using xda premium
Heeter said:
Hi all,
I am tying to figure why my particular bluetooth device just refuses to work with CM10. (BluAnt S4)
I have tried all different versions of CM10 here, as well as the vincom's audio bluetooth fix, to no avail.
Since I have to use it in my car, because of the laws around here, I would like to know anyone else has a working fix for this.
My same device works very well with my girlfriends nexus s CM10 setup.
I get it to ring when I call, but cannot talk/listen to the other party, and they cant hear me. It does show that it is connected, and paired.
I keep reverting back to my backup of CM9 for my daily driver.
Thanks
Heeter
Click to expand...
Click to collapse
CM has been having this problem since CM7. And it has been reported over and over in their issue tracker. But nobody at the CM team can take it and just fix it.
Vincom uploaded a fix for his Support lite Rom. Here ya go & for all others that need it.
http://d-h.st/pC1
Be sure to thank him!
Sent from my ASUS Transformer Pad TF300T running 4.1 [email protected]_V01
I got my first BT working with AOKP, so I am going to stick with this one for now,
Heeter
Sent from my SGH-I727 using xda premium
Not sure if I have just been picking the right ones but I've never had a Bluetooth/Wifi issue with any ROM I've used...
Right now I'm running Superlite JB without gapps which I would think would have the least support and most issues but it's running really well.
Works flawlessly with my car's BT.
Hi All,
On my Verizon Samsung Galaxy S3 I cannot get anyone to hear me when I do a Video Call with the new Google Hangouts...
Anyone else have this issue or a Solution?
adrianvfx said:
Hi All,
On my Verizon Samsung Galaxy S3 I cannot get anyone to hear me when I do a Video Call with the new Google Hangouts...
Anyone else have this issue or a Solution?
Click to expand...
Click to collapse
Identical problem here, s3, d2tmo, 10.1 stable
My girl had that problem she just fix it by adjusting the settings
clean Rom/xda powerd by zero-lemon & tweaked out!!
Hulk0069 said:
My girl had that problem she just fix it by adjusting the settings
clean Rom/xda powerd by zero-lemon & tweaked out!!
Click to expand...
Click to collapse
I've looked at all the settings, which ones did she adjust?
bump.....
Let us know!
I want this issue narrowed down. Let's please post current rom that the bug is present on, any rom that it is working on, and any possible fixes (other than adjusting settings!?! ).
So far I've read reports throughout the aosp threads that the audio is broken on the receiving side of the call (the person you called cannot hear you, but you can hear them). This is known to be the case on liquid, carbon, and rootbox.
I'm currently running liquid 2.4 and can confirm the bug is present. I currently do not have a fix, nor have I heard of one.
Sent from my Nexus 7 using Tapatalk HD
annoyingduck said:
I want this issue narrowed down. Let's please post current rom that the bug is present on, any rom that it is working on, and any possible fixes (other than adjusting settings!?! ).
So far I've read reports throughout the aosp threads that the audio is broken on the receiving side of the call (the person you called cannot hear you, but you can hear them). This is known to be the case on liquid, carbon, and rootbox.
I'm currently running liquid 2.4 and can confirm the bug is present. I currently do not have a fix, nor have I heard of one.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I was using Liquid Rom as well!
I read somewhere(cannot remmber where) but any AOSP based ROM will not work.
Currently only Touchwiz(TW) Roms work.
So I had to flash a TW Rom, and confirms it works!
Anyone else have a working AOSP ROM?
adrianvfx said:
I was using Liquid Rom as well!
I read somewhere(cannot remmber where) but any AOSP based ROM will not work.
Currently only Touchwiz(TW) Roms work.
So I had to flash a TW Rom, and confirms it works!
Anyone else have a working AOSP ROM?
Click to expand...
Click to collapse
That's good info, I had no idea it was working on tw. I would assume by this point then that the big gun devs in aosp are aware of this, and hopefully are working on a fix...?
Sent from my Nexus 7 using Tapatalk HD
Using omega rom v44.4 jb 4.2.1
Tried hangouts with no issues,just hoping for updates like making the vid interchangeable not the switching of front back cam but the layout on set of video calk and make it adjustable.
But everything else is awesome..lovin it
Sent from my GT-I9300 using xda premium
JDroid Freak said:
Using omega rom v44.4 jb 4.2.1
Tried hangouts with no issues,just hoping for updates like making the vid interchangeable not the switching of front back cam but the layout on set of video calk and make it adjustable.
But everything else is awesome..lovin it
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
This is the Verizon s3 section, your running the international.
annoyingduck said:
This is the Verizon s3 section, your running the international.
Click to expand...
Click to collapse
Even if he is running INIT. It should be fine. The problem is universal for all S3's it seems...
I really hope someone knows of a fix!
adrianvfx said:
Even if he is running INIT. It should be fine. The problem is universal for all S3's it seems...
I really hope someone knows of a fix!
Click to expand...
Click to collapse
Again, great info. Didn't know it was across the board on all S3's.
Same problem here, both myself and my friend are having problems on our rooted AT&T SIII's running custom roms
I am running RootBox Nightly 20130514 on Verizon S3. I was absolute that my girlfriend was doing something wrong when she kept telling me she couldn't hear me. Glad to see I was wrong and there is an actual issue. Has anyone seen a fix for this posted? I guess I could flash over to a TW ROM. I haven't had TW since my phone came out of the retail box...
Glad this issue is being reported and seen by many.
No fix still
I went ahead and put back TW. Using Cleanrom now. Google hangouts works just fine. BUT I miss 4.2.2 and AOSP
Same issue here, using LiquidRom 2.3.2 and KT747 5/9 kernel
Looks like this will be fixed in tomorrow morning's nightly.
Restola said:
Looks like this will be fixed in tomorrow morning's nightly.
Click to expand...
Click to collapse
This was fxed with liquid smooth?
Not yet
Sent from my Nexus 7 using Tapatalk HD
Slim bean build 6 changelog says they fixed the Hangouts issue (haven't had a chance to test myself yet).