I have Verizon GN rooted with latest CM9
set my google voice mail instead of carrier voice mail to play it from call log. Everything was working very well for couple months. However, few days ago stops working. It will show that I have a new voice mail in the call log, and it will show me from whom, but when i open it and hit play it will kick me out back to call log and wont play it!!!!
I was thinking maybe a bug from CM9!!! Can anyone check that for me on his device and confirm it?
I was searching for that problem before I decided to post this, but all what I find is about Sprint and I know it is something different from this one.
Regards,
Bassil
Its either only me, or no one uses google voice for the voice mail from call log except me
I'm having the same problem all of a sudden. I wonder if it's a new bug introduced in CM9 because it works on my old builds on my Nexus One but doesn't work on the Galaxy Nexus or my HTC One X running CM9.
My Google-fu indicates that it might be a codec error, but I don't see any recent changes that would account for this.
sassafras
It looks like it is crashing trying to load the variablespeed playback lib.
Still don't see any change in the CM9 repos that would cause this problem.
sassafras
sassafras_ said:
It looks like it is crashing trying to load the variablespeed playback
Click to expand...
Click to collapse
Exactly, this what is happening to me!!! It wasn't like this with the older versions of CM9. I guess either from the new builds or from Verizon disabled it!!!
Same here
Sent from my Galaxy Nexus
I don't think it's carrier side. I think it's a bug new since a recent build of CM9
I think it's from the Android build 4.0.4, not from cm9 because I changed from cm9 to another rom with same android 4.0.4 and having same problem.
bassil2022 said:
I think it's from the Android build 4.0.4, not from cm9 because I changed from cm9 to another rom with same android 4.0.4 and having same problem.
Click to expand...
Click to collapse
Which ROM? Are you sure it doesn't use the CM9 codebase?
sassafras
I've been told that Google voice replay from the dialer will fail on any linaro build. I think, but could be wrong, that the latest CM9 and AOKP both are now linaro. I'm using stock 4.0.4 and it works fine.
I experienced the same exact issue, also some m3 files wouldn't play.
I was running latest BlackIce which is cm9 based. Just flashed it Monday, reverted back to my nandroid and everything started working correctly. It must be something with the latest updates made on CM9.
Sent from a phone...
sassafras_ said:
Which ROM? Are you sure it doesn't use the CM9 codebase?
sassafras
Click to expand...
Click to collapse
AOKP
I switched to an old build by CM9, and now its working
I was already backed up. So I just restored. It was bulid 5/20
Pretty safe to say it's a CM9 bug, but still no idea what is actually causing it.
sassafras
sassafras_ said:
Pretty safe to say it's a CM9 bug, but still no idea what is actually causing it.
sassafras
Click to expand...
Click to collapse
It's pretty well established that it's a linaro issue.
Sent from my Galaxy Nexus using Tapatalk 2
The latest cm9 nightly (July 9) seems to have fixed this. It works for me now at least.
T-mobile gs2
Related
So I thought this might have been just me, or maybe just the ROM I was using but it appears to be more widespread than that. I've confirmed this on GummyNex, CM9 Kang (winner00), and AOKP. I've also confirmed this on my buddies GNex.
With the phone app open and looking at Recent Calls. Lock the screen, then unlock, the swipe the screen over to the dialer and attempt to dial numbers and in some instances it lags heavily. Other times it freezes completely and asks to Wait/Report/Close.
Anyone else having these issues? Any known fixes?
I mean, I could hit home, then re-open the dialer, but shoooooot.
Any help is appreciated.
-Ranks
I can't seem to replicate this bug on my gnex. Tried several times, but i can't get it to lag at all.
What Android version are you running? I'm on 4.0.2.
Bugless Beast ROM and no problem at all.
By any chance do these ROMs all have the modified dialer with T9 support? Than it's most likely a bug in the modified dialer.
What Android version are you running? I'm on 4.0.2.
Click to expand...
Click to collapse
4.0.3 in each instance
By any chance do these ROMs all have the modified dialer with T9 support? Than it's most likely a bug in the modified dialer.
Click to expand...
Click to collapse
Yes, all of them.
Running AOKP b23 now...
Turned off T9 in settings, rebooted. Works perfectly now with no delays. Thanks for the quick response and fix, it was driving me crazy.
I really like that functionality so I hope a remedy is released soon.
Cheers!
-Ranks
On the recent nightlies of CM10, people who called me said they were hearing an echo of themselves as they spoke. I reverted back to CM 10 form 08/15/12 and it has gone away. I was using CM 10 nightly from 08/24/12. Has any one else experienced this? I did also turn off the voice suppression but it still continued creating the echo. Do someone have a solution to this?
This is a universal issue. I'm on Verizon and there is lots of talk about this going on.. No fix yet. Seems to affect the builds after the first couple. Some have it some don't. Mine.. Comes and goes.. Annoys the mess out of my wife when I call her. Cyanogen stated back on 8/20 that he had a patch coming, but at this point nothing yet..
Some people are stating that the echo is probably a result of a defective phone. I really don't think so. If I flash cm 10 08/15 there is no echo, any latter rom gives me echo. I think it is some software glitch. someone needs to check what changed from cm 10 08/15 to the next update, which was cm10 08/18.
The 8/31 nightly has a fix. The S3 has an audio canceling chip it uses to detect yourself and cancel out so the echo isn't heard. It is currently not supported but they added support in the 8/31 build which should fix this issue.
I see that on the cm10-log. I can't wait till 08/31!:laugh::laugh::laugh:
I'm on stock rooted. It happens once in awhile. It has to do with cdma...not the phone. People on verizon will attest to this.
Sent from my SPH-L710 using xda premium
I can confirm this was fixed in nightly 31.
Sent from my Nexus 7 using Tapatalk 2
Restola said:
I can confirm this was fixed in nightly 31.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Problem still present on my tmobile s3 even with factor reset and 8/31 flash stock kernel :/
i too can confirmed this was fixed in 8/31 nightly. also, OP, why didn't you just search the cm10 thread for "echo" instead of starting a new thread about something that's already discussed in detail in the cm10 thread?
cnstarz said:
i too can confirmed this was fixed in 8/31 nightly. also, OP, why didn't you just search the cm10 thread for "echo" instead of starting a new thread about something that's already discussed in detail in the cm10 thread?
Click to expand...
Click to collapse
I did search for one but did not find one so I decided to just create one. Apologies if I stepped on anybody's toes.
This is not just on the S3. The S2 have this issue too. And not just the European version but all of em. Is the way Samsuck ****s with their phones.
Hi Guys,
anyone know a JB ROM that has this feature from CM 9 ?
Bluetooth Message Access Profile (MAP)
I know some SII JB Roms have this ported from CM9 but not sure about SIII.
Thanks,
Raul77 said:
Bluetooth Message Access Profile (MAP)
Click to expand...
Click to collapse
Try CM10... if it's not in there yet, it should be in AOKP
garyd9 said:
Try CM10... if it's not in there yet, it should be in AOKP
Click to expand...
Click to collapse
Thanks, i am actually on AOKP now, its 100% not there. Will try CM10. thanks.
CM10 has it (tried it a few days ago).
smelenchuk said:
CM10 has it (tried it a few days ago).
Click to expand...
Click to collapse
Just incase anyone is searching for this, this works GREAT on CM. thanks for all the suggestions
I am running CM10 M2 and cannot seem to find this featue. My ford sync says text unavailable.
JRust00 said:
I am running CM10 M2 and cannot seem to find this featue. My ford sync says text unavailable.
Click to expand...
Click to collapse
I switched back to AOKP 10/16, its working there now. sorry not on CM anymore.
I recall spotting a fix for MAP in the CM10 changelogs in the past day or two; I'm not sure what was broken or when, but presumably the break happened before M2.
If I get a chance I'll check if the latest nightlies still have MAP working.
smelenchuk said:
I recall spotting a fix for MAP in the CM10 changelogs in the past day or two; I'm not sure what was broken or when, but presumably the break happened before M2.
If I get a chance I'll check if the latest nightlies still have MAP working.
Click to expand...
Click to collapse
Is mail working with bluetooth map on CM10 oder aokp or just sms?
thanks.
Slim bean 4.2.1 stable release mentions MAP in their change log. Have not tried it yet though. Looking to find one that works with Dodge uconnect.
hatgirl223 said:
Slim bean 4.2.1 stable release mentions MAP in their change log. Have not tried it yet though. Looking to find one that works with Dodge uconnect.
Click to expand...
Click to collapse
As long as it supports MAP shouldnt be a problem. I´m still searching for a ROM/solution to read my mail on an BMW CIC entertaining system. Touchwiz does sms but no mail...
Cheers
Need to know for a little experiment I wanna try.
Sent from my SGH-I927 using xda premium
Pacman or cm10 both by dman who is in fact da man !
Sent from my SGH-I927 using xda app-developers app
They seem like there's too many problems with them.
Sent from my SGH-I927 using xda premium
There's a thread reporting current bugs.
Those bugs are still important but I can say that these ROMs already work very good.
Thanks to dman for original work and, lately, to spyke555 and kick who are really doing an excellent job (development was almost dead before they committed and i'm very thankful to them for what they are doing).
I've seen the current bug thread but it's for 4.2.2 I need 4.1.2
Sent from my SGH-I927 using xda premium
spitfire2425 said:
I've seen the current bug thread but it's for 4.2.2 I need 4.1.2
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
He already answered your question, the 4.1.2 weren't ever completed, they were abandoned... hence why the issues in those roms are still present.
Install PACRom 18.2 and then apply the fixes for keyboard etc. I think the fixes are in the litekernel thread. Put on the latest litekernel for 4.1 keyboard fix, lights fix and you'll have the best working 4.1.2.
Note - skype and bluetooth headset still won't work, pretty sure the camera issue with rotation is still present. I ran pacrom 18.2 for MONTHS without any issue except those listed and the wake lag.
I was trying to port something, not use it as a rom.
Sent from my SGH-I927 using xda premium
GPS and other features
Uhm is any STABLE release with:
GPS Working (most important)
MUSIC Working
Skype Working
Camera Working
Google Now Working (this seems to be an issue from all custom Roms)
Since I've seen most these features working but none on the same ROM all together
myxoh said:
Uhm is any STABLE release with:
GPS Working (most important)
MUSIC Working
Skype Working
Camera Working
Google Now Working (this seems to be an issue from all custom Roms)
Since I've seen most these features working but none on the same ROM all together
Click to expand...
Click to collapse
Not for version 4.1.2 (jellybean)
Only ICS 4.0.xxx ...
****, somebody needs to make a sticky for the most current stable rom .. this question keeps coming up over and over and over in every forum and many threads.
myxoh said:
GPS Working (most important)
Click to expand...
Click to collapse
GPS has always worked. Some of the technical data returned is invalid/bogus but Google Maps/Navigation is completely unaffected.
MUSIC Working
Click to expand...
Click to collapse
Again, it's always worked, so long as you don't have an app trying to record audio at the same time.
Skype Working
Click to expand...
Click to collapse
Skype works for text messages, but received audio in calls is corrupt. The core of the issue is audio playback breaks when an app opens the microphone. (Ironically, the microphone itself actually works fine, i.e. voice recognition has messed up audio cues but it does process what you say correctly.) Current hypothesis is it's a driver issue. Research is ongoing. This is a longstanding issue going all the way back to our very first JB kernels.
Camera Working
Click to expand...
Click to collapse
Current CM10.1 and derivatives have a fully working camera.
Google Now Working (this seems to be an issue from all custom Roms)
Click to expand...
Click to collapse
This is actually a known problem with Google Now itself, it depends on an instruction set the Tegra 2 doesn't have. The Galaxy R and the Galaxy Note 10.1 have the same problem, on ALL Jellybean ROMs, even official. Bug Google, not us.
There is a workaround: downgrade GNow to a working version (possibly by flashing old gapps), then disable "Hotword detection" in settings. Once that is turned off you can upgrade to the latest and it will still work.
Thanks for the reply
roothorick said:
GPS has always worked. Some of the technical data returned is invalid/bogus but Google Maps/Navigation is completely unaffected.
Again, it's always worked, so long as you don't have an app trying to record audio at the same time.
Skype works for text messages, but received audio in calls is corrupt. The core of the issue is audio playback breaks when an app opens the microphone. (Ironically, the microphone itself actually works fine, i.e. voice recognition has messed up audio cues but it does process what you say correctly.) Current hypothesis is it's a driver issue. Research is ongoing. This is a longstanding issue going all the way back to our very first JB kernels.
Current CM10.1 and derivatives have a fully working camera.
This is actually a known problem with Google Now itself, it depends on an instruction set the Tegra 2 doesn't have. The Galaxy R and the Galaxy Note 10.1 have the same problem, on ALL Jellybean ROMs, even official. Bug Google, not us.
There is a workaround: downgrade GNow to a working version (possibly by flashing old gapps), then disable "Hotword detection" in settings. Once that is turned off you can upgrade to the latest and it will still work.
Click to expand...
Click to collapse
Thanks for the reply but:
1) GPS was not locking for me until I changed the gps.conf file in MOST of the ROMs I've tested.
2) Music didn't work on one rom I tested (now and then the music player started lagging and it automatically stopped every few seconds for a few milliseconds)
3)Thanks for the Skype reply; I was hoping there was some version with this fixed but evidentely not.
4)Camera flips orientation in all the roms I've tested. HDR just worked in 1 of them. Camera actually crashed from time to time in one of them.
5)Oh, sad about the Google Now fact. It's actually one of the main reasons I wanted JB
The skype thing Can't be a hardware issue since I've used skype several times before rooting my device. The issue you are talking about happens on google voice sometimes; therefore I'm guessing you're right on thinking that the problem is on the driver.
I'm very interested in ROM building since I'm an app developer for android and a C++ programmer; yet I've been too lazy to check how it worked. Are the drivers we are using open source? or are we just messing with the conf files trying to get things fixed?
myxoh said:
Thanks for the reply but:
1) GPS was not locking for me until I changed the gps.conf file in MOST of the ROMs I've tested.
2) Music didn't work on one rom I tested (now and then the music player started lagging and it automatically stopped every few seconds for a few milliseconds)
3)Thanks for the Skype reply; I was hoping there was some version with this fixed but evidentely not.
4)Camera flips orientation in all the roms I've tested. HDR just worked in 1 of them. Camera actually crashed from time to time in one of them.
5)Oh, sad about the Google Now fact. It's actually one of the main reasons I wanted JB
The skype thing Can't be a hardware issue since I've used skype several times before rooting my device. The issue you are talking about happens on google voice sometimes; therefore I'm guessing you're right on thinking that the problem is on the driver.
I'm very interested in ROM building since I'm an app developer for android and a C++ programmer; yet I've been too lazy to check how it worked. Are the drivers we are using open source? or are we just messing with the conf files trying to get things fixed?
Click to expand...
Click to collapse
hi,
thread how to compile from source:
http://forum.xda-developers.com/showthread.php?t=2071542
AFAIK drivers are not open source if they were there wouldn't be so much problems with them. They are ported from other devices similar hw but with code for them.
any news about JB and bluetooth headset issue?
this is the only thing that's been holding me back so far
myxoh said:
Uhm is any STABLE release with:
(...)
Click to expand...
Click to collapse
Where to find this "Uhm"? It was not listed here: http://forum.xda-developers.com/showthread.php?t=1621350
AOSP - Reference - JLS36G
As requested by undarated in my Reference ROM for the Galaxy Nexus GSM (Maguro), I took on the challenge to make a build for Toro. This is as pure as Android gets, compiled straight from Googles AOSP repository. I added absolutely nothing to the build (apart from the binairy drivers), partly because I want it to be as pure as possible for now and partly because I'm not a developer by any means
You can see this as a Reference ROM, all other ROMS are essentially based on this.
First thing that striked me was its speed. This ROM flies on Maguro and Iḿ sure it does the same on Toro! Google did a great job with 4.3.1 and is still continiously updating the AOSP sources
DISCLAIMER: As I don't own the device I couldn't test this myself of course, but undarated tested a pre-test and it didn't kill his phone
Anyway, here the link, it's on Google Drive (builddate 2013/10/10):
https://docs.google.com/file/d/0BwNDN4ITQ7phYzEyRldQLXZCeEE/edit?usp=sharing
The 'official' GApps (Google Play Store, GMail, Google+, etc):
http://goo.im/gapps
You can also use the experimental GApps for Android 4.3 (thanks to BaNkS, follow his thread here):
http://www.androidfilehost.com/?a=show&w=files&flid=7775
As this ROM is so pure, it even comes unrooted, you can find Chainfire's latest SuperSU here:
http://download.chainfire.eu/supersu
Changes to the AOSP tree can be found here:
https://android-review.googlesource.com/#/q/status:merged,n,z
If it works well and there's a demand for it, I try to update it regularly
Have fun
Thanks, I came here just to look for something exactly like this. I'll let you know if it blows up my phone (Don't worry, I know how to recover it).
First thing I tried doesn't work. Its an issue with AOSP and Verizon (CDMA?). MMS won't send if you are connected to WIFI. The MMS needs to go through the 3G/4G towers and the switch to 3G/4G doesn't happen. You need to manually turn off WiFi for it to work.
rufflez2010 said:
Thanks, I came here just to look for something exactly like this. I'll let you know if it blows up my phone (Don't worry, I know how to recover it).
First thing I tried doesn't work. Its an issue with AOSP and Verizon (CDMA?). MMS won't send if you are connected to WIFI. The MMS needs to go through the 3G/4G towers and the switch to 3G/4G doesn't happen. You need to manually turn off WiFi for it to work.
Click to expand...
Click to collapse
Will this MMS fix work?https://db.tt/JXsuV6r8
♦ToroNex-Vanir
Sweet! Wanted a stock rom updated JLS36G instead of JWR66V.
rufflez2010 said:
Thanks, I came here just to look for something exactly like this. I'll let you know if it blows up my phone (Don't worry, I know how to recover it).
First thing I tried doesn't work. Its an issue with AOSP and Verizon (CDMA?). MMS won't send if you are connected to WIFI. The MMS needs to go through the 3G/4G towers and the switch to 3G/4G doesn't happen. You need to manually turn off WiFi for it to work.
Click to expand...
Click to collapse
Is this clean build affected by the 4.3 radio issue? Do you reconnect to Data? Do you have any 3/4G switching issues?
yawdapaah said:
Is this clean build affected by the 4.3 radio issue? Do you reconnect to Data? Do you have any 3/4G switching issues?
Click to expand...
Click to collapse
I was only on WiFi. I haven't left my apartment yet but I will tomorrow night. I went to paranoid android but I'm not sure I'm going to stay on it.
Sent from my Nexus 7 using Tapatalk 4
jorgen2009 said:
AOSP - Reference - JLS36G
As requested by undarated in my Reference ROM for the Galaxy Nexus GSM (Maguro), I took on the challenge to make a build for Toro. This is as pure as Android gets, compiled straight from Googles AOSP repository. I added absolutely nothing to the build (apart from the binairy drivers), partly because I want it to be as pure as possible for now and partly because I'm not a developer by any means
You can see this as a Reference ROM, all other ROMS are essentially based on this.
First thing that striked me was its speed. This ROM flies on Maguro and Iḿ sure it does the same on Toro! Google did a great job with 4.3 and is still continiously updating the AOSP sources
DISCLAIMER: As I don't own the device I couldn't test this myself of course, but undarated tested a pre-test and it didn't kill his phone
Anyway, here the link, it's on Google Drive (builddate 2013/10/07):
https://docs.google.com/file/d/0BwNDN4ITQ7phOEFxa00tUDVCTHM/edit?usp=sharing
Experimental GApps for Android 4.3 (thanks to BaNkS, follow his thread here):
http://www.androidfilehost.com/?a=show&w=files&flid=7775
or the official GApps:
http://goo.im/gapps
As this ROM is so pure, it even comes unrooted, you can find Chainfire's latest SuperSU here:
http://download.chainfire.eu/supersu
Changes to the AOSP tree can be found here:
https://android-review.googlesource.com/#/q/status:merged,n,z
If it works well and there's a demand for it, I try to update it regularly
Have fun
Click to expand...
Click to collapse
Hey I see you made it over. I'm about to download and test it again myself.
yawdapaah said:
Is this clean build affected by the 4.3 radio issue? Do you reconnect to Data? Do you have any 3/4G switching issues?
Click to expand...
Click to collapse
Bump
Not to sound like a Debbie Downer here, but is there any reason why we shouldn't expect this ROM to have the same issues affecting every other 4.3 ROM for the VZW Gnex? I mean, I'm still going to flash it... but still. (BTW, I'm not being facetious, I really would love it if this ROM wasn't plagued with the data handoff issues other ROMS are struggling with.)
jaredsleboeuf said:
Not to sound like a Debbie Downer here, but is there any reason why we shouldn't expect this ROM to have the same issues affecting every other 4.3 ROM for the VZW Gnex? I mean, I'm still going to flash it... but still. (BTW, I'm not being facetious, I really would love it if this ROM wasn't plagued with the data handoff issues other ROMS are struggling with.)
Click to expand...
Click to collapse
Same good ol' data handoff issues apply here.
Sent from my Galaxy Nexus using Tapatalk 4
parkson said:
Same good ol' data handoff issues apply here.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
I'm sorry guys, but I can't do much here. This is way out of my expertise, even from all Toro experts themselves if I understand it correctly.
What I can do, is give you a new build. Google just released Android 4.3.1 on AOSP (JLS36I) and I build a fresh build. See OP for the link.
It seems the PA Gapps don't work (for Maguro at least). I tested my Maguro build with the 'official' Gapps and that does work however.
Let's hope this build fixes the known problems
jorgen2009 said:
I'm sorry guys, but I can't do much here. This is way out of my expertise, even from all Toro experts themselves if I understand it correctly.
What I can do, is give you a new build. Google just released Android 4.3.1 on AOSP (JLS36I) and I build a fresh build. See OP for the link.
It seems the PA Gapps don't work (for Maguro at least). I tested my Maguro build with the 'official' Gapps and that does work however.
Let's hope this build fixes the known problems
Click to expand...
Click to collapse
BAM!!!!!! 3g/4g handoff works and airplane mode works perfect coming back out. HECK YES!!!!!!
Flashed the new build with banks gapps working great thanks
Sent from my AOSP on Toro using XDA Premium 4 mobile app
Baby_Phil said:
Flashed the new build with banks gapps working great thanks
Sent from my AOSP on Toro using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Banks gapps?
yawdapaah said:
Banks gapps?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2012857
Sent from my AOSP on Toro using XDA Premium 4 mobile app
Not a huge issue, but the carrier text in the notification shade is "T-CDMA64" or something like that.
ironfisted said:
BAM!!!!!! 3g/4g handoff works and airplane mode works perfect coming back out. HECK YES!!!!!!
Click to expand...
Click to collapse
Any issues now that you tested for a day or two? Anyone else to confirm that 4.3.1 may have fixed hand-off issues?
someotherguy said:
Any issues now that you tested for a day or two? Anyone else to confirm that 4.3.1 may have fixed hand-off issues?
Click to expand...
Click to collapse
Still working great for me
Sent from my Galaxy Nexus using Tapatalk 4
I can confirm myself that data handoff issues are not there for me anymore. I'm running a testing build of Shiny ROM on 4.3.1 and all handoffs worked as flawlessly as 4.2.2. No grey bars, and quick switching. I did run this one last night and had no issues either. Glad we finally have working data again!!!
someotherguy said:
Any issues now that you tested for a day or two? Anyone else to confirm that 4.3.1 may have fixed hand-off issues?
Click to expand...
Click to collapse
I'm not seeming to have any data drop issues with handoff... 4.3.1 is running really nice. What are you guys using for kernel though in 4.3+? I'm still on stock but need color controls.