I installed this latest jellybean leak for my Verizon GS3.
Pairing is not a problem nor is auto connect. My problem is the audio is completely garbled and inaudible during voice phone calls from my car.
I have an Infinity G37.
I did not have any problems before I flashed this leak Prior to this, I had flashed CyanogenMod 10 unofficial nightly builds with no problems. Prior to this, I had also used the latest verizon release for ICS with no problems.
The phone (as currently flashed to the jellybean leak VRBLK1) pairs and works perfectly with my wife's BMW Z4.
I have reset, unpaired, cleared the cache, etc and I just cant get this to work. I have tried different radios with no luck. I have downloaded and tried different bluetooth fixes from the marketplace with no luck.
My only option is either flashing back to ICS, or CyanogenMod 10 unofficial, but I prefer not to do that because other than this problem, everything else is perfect.
I have searched the forums and am unable to get an older version of Bluetooth Share (Would like to replace 4.1.1 with 4.0.4) which i suspect may fix this problem.
Any suggestions will be greatly appreciated. I do a lot of calls in my vehicle and we have a hands free ordinance in our city.
Nothing?
Anyone? Anyone? Anyone?
You've got it: 4.1.1 issue. No idea on a fix, I'm back to ICS as a result. Isn't a modem issue it seems (unless interaction between JB builds and particular modems), seems to be a JB issue (reported across phones with lots of different vehicles).
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Termuellinator said:
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Click to expand...
Click to collapse
*push* nobody got any ideas? i would post it in the appropriate thread (especially since this rom is still only nightly) as a potential bug report, but as a new user i'm not able to :/
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Termuellinator said:
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Click to expand...
Click to collapse
The WiFi bug is a known issue since early August. It affects almost every Moto device (G, G 4G, X and defy?) it's reported several times to CM-s bug tracking system, but nobody cares... You can use custom kernels. Maybe they aren't affected.
I don't know anything about the BT bug.
i found some posts about people having the same kind of wifi-issue, but it is good to know, that the devs are aware and - kind of - working on it
the BT-thingy is driving me insane though...fiddled around a bit, stopping BT-Related processes etc...this somehow did something...my phone now connects and stays connected, i can make phone calls...but the contact list is incomplete - only 3 random contacts are displayed on the car system
haven't rebooted since then, i kind of fear that rebooting will bring back the issue :/
BT still working after reboot, so it seems my "fix" is permanent...must have something to do with deleting the BT-data/cache while process was killed i would think - in case someone else also encounters this problem
still can't acces all my contacts from Car-system though :/
Most nights roms have a lot of issues and it is pretty hard to stay aware all of bugs. Why don't you try something more stable like Pac Man RC or some. Sometimes a different kernel will help sometimes it's the opposite.
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Termuellinator said:
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Click to expand...
Click to collapse
All AOSP rom uses the CM device tree and kernel as a base, so the low level kernel bugs are the same.. Also the last "stable" CM for falcon is dated back to April, so you didn't lose anything with peregrine...
Just in case anyone encounters the same Issues:
with CARBON-KK-NIGHTLY-20140922-0414-peregrine the BT-Problems seem to be resolved, connection works and the contacts are accessible from the car.
WiFi still has problems with dhcp, but as stated, devs are aware of that :good:
bad news: flashed to CARBON-KK-NIGHTLY-20141103-0939-peregrine and the BT-issue is back as in the beginning - com.andoird.bluetooth stops working - but only following the first connect -.-
interestingly going back to my pre-flash-backup didn't resolve the issue (doesn't matter if i just restore or wipe prior to that...but after flashing/restoring the first connect works perfectly)...perhaps that leads to some ideas about the cause?
was just trying to get it to work like the other time by stopping/deleting data of com.andoird.bluetooth, but didn't work this time
ok, figured it out again, this time i'll post my steps in case anyone ever encounters similar issues (and for my future reference in case i encounter them again, too )
1) unpair
2)switch off bluetooth
3) stop com.android.bluetooth in "apps"
4) delete data of com.android.bluetooth
5) reboot
6) pair
7) unpair
8) delete data of com.android.bluetooth
9) pair
10) reboot
at least these are the steps i did and it seems to be working now, again
Hi
Was running on the CM 12.1 and no issues with wifi. Then I decided to update and went with the RR per below
http://forum.xda-developers.com/oneplus-one/development/rom-ressurrection-remix-m-t3270147
Did a clean install and loaded gapps and everything seemed ok but then had issues with Wifi dropping constantly. I tried google and changed channel on router to channel one and also tried app called Wifi Analyser but still the same issue.
Saw a fix for cm 12 in the below
http://forum.xda-developers.com/oneplus-one/general/fix-wifi-connectivity-issues-drops-t3070045
Not sure if same fix applies to 13 as it seems to be an issue with the CM 13 and not the ROM itself..??
Had to go back to CM12.1 and no wifi issues pity as was happy enough but no wifi is a showstopper. Posted in the RR thread but maybe this might be a CM13 issue so wondering if anyone knows any fixes for it as I may try again
Thanks
I have the same issue, need to turn off bluetooth, try it it may work for you also
First, I don't know much about custom ROMs or root processes in general. I rooted the phone myself, and installed the recovery/flashed the ROMs, but my knowledge is one step above basic, if that.
A couple of weeks ago I stopped being able to send MMS. I simply dealt with it. I don't send a whole lot of pictures. I finally called Sprint yesterday to address the issue, and the wizard on the other side of the line did some sort of magical spell which caused (I think, could've been coincidence) my 3G connection to stop functioning as well after a few reboots.
This is a Samsung Galaxy S3 for the Sprint network. I am currently running CyanogenMod 11 (AV 4.4.4) and have ClockWorkMod installed as my recovery. Fixes I have tried so far include:
- Reflashing all my ROMs
- Updating CM11
- Flashing CM12.1 instead of CM11
- Multiple hard/soft reboots
- TouchWiz MMS Fix
- FreedomPop APN adjustment
Nothing has worked so far. I am at the point where I am about to just purchase a new phone. If it matters, the verdict on the phone with Sprint was to take it to a store, which I did, but when they crack open an AOSP it seems they have no idea what they're doing.
Please help.
zmauls said:
First, I don't know much about custom ROMs or root processes in general. I rooted the phone myself, and installed the recovery/flashed the ROMs, but my knowledge is one step above basic, if that.
A couple of weeks ago I stopped being able to send MMS. I simply dealt with it. I don't send a whole lot of pictures. I finally called Sprint yesterday to address the issue, and the wizard on the other side of the line did some sort of magical spell which caused (I think, could've been coincidence) my 3G connection to stop functioning as well after a few reboots.
This is a Samsung Galaxy S3 for the Sprint network. I am currently running CyanogenMod 11 (AV 4.4.4) and have ClockWorkMod installed as my recovery. Fixes I have tried so far include:
- Reflashing all my ROMs
- Updating CM11
- Flashing CM12.1 instead of CM11
- Multiple hard/soft reboots
- TouchWiz MMS Fix
- FreedomPop APN adjustment
Nothing has worked so far. I am at the point where I am about to just purchase a new phone. If it matters, the verdict on the phone with Sprint was to take it to a store, which I did, but when they crack open an AOSP it seems they have no idea what they're doing.
Please help.
Click to expand...
Click to collapse
This issue has been resolved. I flashed over a rooted stock MK3 ROM with a custom modem which allowed me to update profile and PRL. Thank you.
Great that you solved the problem.
Flashed from CM13 to CM14 without issues. However, every nightly after 11/16 causes my phone to not send txt messages. Have tried different apps, checked carrier settings, re-flashed, etc. Any help would be appreciated.
I think the Beanstalk thread gives us the best perspective on the issue. Probably early issues that will eventually get fixed.
Which baseband? This behaviour smells a lot like some of the other weirdnesses I've seen when I've had an image installed which was expecting a baseband other than the one I had in play. When I tried CM14 had the latest official O-something or other for the SM-G900P SPR and like a lot of folks, GPS was just not functional at all. So... after wiping the everythings (literally everything except my ejected microSD card) and reinstalling CM13 through TWRP certain operations (like initializing GPS) were still taking a good 30-45 seconds to initialize which wasn't the case previously with the late October nightly I was using. ...another sign that something has gone off the rails with the modem-y parts, and that they might be in a tizzy about being talked to with the wrong API.
So... just to reset everything I wound up reflashing the O-something stock firmware I had, then letting it upgrade itself via the two OTA patches to PK1. (Don't worry, I find the idea of tolerating Sprint's Crazy-Town modifications laughable.) Updated the profile and the PRL for giggles, and then reflashed in TWRP, wiped the everythings again and sideloaded the same CM13 nightly and Gapps.
I've just gotten things squared back away with CM13 and haven't had a chance to circle back around to try CM14 again (because all that other stuff takes a few hours and makes testing conflict with things like, sleeping and eating) with the new baseband, but the pass through stock and it's updates sorted out the strange 30-45s glitches. If anyone's actually tried CM14 with a PK1 baseband it would probably be worth hearing if they've got GPS and cellular traffic working simultaneously.
Update: Sure enough, after upgrading to the PK1 baseband (via a reflash to stock) CM14.1 seems to be able to handle cellular data and voice calls, wifi, bluetooth and GPS. There was a bit of weirdness with Allo making a terrible sound instead of beeping, but all things considered it looks like it's stable enough to be a daily driver for the SM-G900P now.