Database Info

[Q] In call volume muted and random network disconects

Hi all,
My front facing phone speaker seems to be permanently muted. Whenever I get or make a phone call no sounds come from the speaker on the top front of the phone. When I switch to speaker mode everything works fine. Also the phone randomly disconnects from the phone network then reconnects. I was originally running Cyanogenmod 10.0.0 during which everything was working fine. I then upgraded to a nightly using the built in cyanogen upgrader. For a time after this everything continued to work. Eventually these problems began. I again upgraded, using the built in upgrader to 10.1.0 RC1 then 10.1.0 RC2 which didn't seem to change anything. Finally I used recovery to wipe the cache and factory reset and flash 10.1.0 RC2 and the latest gapps package. This didn't help either. I then repeated that process except with the version 10.0.0 of cyanogenmod which also did not fix the problem. I'm not sure if these problems are actually related but they seemed to start at around the same time. I've never knowingly flashed a radio on this thing, I'm not sure if the in app upgrader does this or not. I was wondering if anyone had a good idea on what my next course of action should be or if they have had similar issues and have found a solution.
Thanks.

Meshelton said:
Hi all,
My front facing phone speaker seems to be permanently muted. Whenever I get or make a phone call no sounds come from the speaker on the top front of the phone. When I switch to speaker mode everything works fine. Also the phone randomly disconnects from the phone network then reconnects. I was originally running Cyanogenmod 10.0.0 during which everything was working fine. I then upgraded to a nightly using the built in cyanogen upgrader. For a time after this everything continued to work. Eventually these problems began. I again upgraded, using the built in upgrader to 10.1.0 RC1 then 10.1.0 RC2 which didn't seem to change anything. Finally I used recovery to wipe the cache and factory reset and flash 10.1.0 RC2 and the latest gapps package. This didn't help either. I then repeated that process except with the version 10.0.0 of cyanogenmod which also did not fix the problem. I'm not sure if these problems are actually related but they seemed to start at around the same time. I've never knowingly flashed a radio on this thing, I'm not sure if the in app upgrader does this or not. I was wondering if anyone had a good idea on what my next course of action should be or if they have had similar issues and have found a solution.
Thanks.
Click to expand...
Click to collapse
If you were happy with everything working WHY in the world did you upgrade to a Nightly? Nightly by definition is only for people who know what they're doing and are not afraid of the Night.
Anyway, there are like 6.0221413e+23 changes from cm 10.0.0 to 10.1 RC2. What can I say you did a dirty flash (upgrade!), and probably didn't back up.
So the first thing you should do is back up. NOW (go to CMW recovery and back up)
Download a better behaving nightly like the one JD1639 uploaded. get it from http://forum.xda-developers.com/showthread.php?t=2272261
Download the UCMC1 radio (assuming you're on at&t)
Download the gapps 20130301
Put them all on in one folder for easy access
goto the CWM recovery and get to work:
1-backup
2-cleanup: go to mounts and format data, cache, system (don't format the sdcard!!!) and don't reboot until everything is finished
3-clean dalvik cache from advanced
4-install in this order: RADIO file.zip (UCMC1)
5-CM ROM
6-gapps
7-go to Advanced Restore option, find you back up and restore the "DATA" portion ONLY
This should save you ... good luck,
Commodore 64

Thanks for the reply.
That seemed to fix the connectivity issue but not the sound issue. I guess that could just be a hardware thing. If it were a software issue is there anything else I should try?

Meshelton said:
Thanks for the reply.
That seemed to fix the connectivity issue but not the sound issue. I guess that could just be a hardware thing. If it were a software issue is there anything else I should try?
Click to expand...
Click to collapse
You know I don't think it is a hardware issue since it started after one of your updates. If you were on a ROM for while, and one morning you wokeup and the sound didn't work ... maybe. But i'm not convinced since also I remember around Feb-March there were some complains on sound not working after flashing to 4.2.2 version of the cm. Try flashing back to the stock UCMC1 ROM (absolute stock flashed with Odin not CMW) and then do a factory reset.

[Q] help plz. Data conection issues

Hello world
I have a 64gb oneplus One. I'll make it simple.
With CM 11S everything works perfectly
With oxygen OS everything works.
With cm 12s or any cyanogenmod based 12 por 12.1 i have connection problems. When i disconnect from a WiFi network, the OPO cant reconnect to data. It just shows an exclamation mark on the signal indicators.
The only way to make it work is to enable/disable airplane mode.
Ive tried every apn configuration from my provider.
Ive tried several módems
What else can i do? Its not a hardware issue because it works perfectly with the avobe mentioned.
Its annoying because i keep missing whatsapp msgs or stuff like that
Thanks un advance!

When switching between ROMs, did you always flashed the correct hardware for the given ROM?

Now i have cyanogen OS 12s. I flashed 11S vía fastboot and got all the OTAS

No SIM card issue after wrong GPS fix flash

Hi everyone!
I've made a big mess with my OPO... I try to explain:
1. I was running last euphoria build with CAF kernel once I discovered that "only GPS" mode was not working. (After a lot of googling now I understand that is a common OPO problem...)
2. I found a GPS fix from this link http://forum.xda-developers.com/moto-g/development/lollipop-5-0-x-euphoria-os-t3016005/page142
and I didn't notice that was for MotoG before flash it! Damn!
After flashing that fix my SIM function completly brokes, no carrier, no signal, no possibilities to set up the apn... Nothing at all...
3. Wiped system, data, cache and dalvin cache and than flashed last cm 12 (internal data not touched). No SIM function...
4. Wiped all again and flashed last cm 12 with CAF kernel (because I found it more stable than others) and than flashed modem firmware for OPO from this link http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516
5. Results: no SIM function again...
I don't know what to do right now guys... Please help me, currently I have a phone with no phone capabilities
Thanks!!!!

Ray.Smith said:
Hi everyone!
I've made a big mess with my OPO... I try to explain:
1. I was running last euphoria build with CAF kernel once I discovered that "only GPS" mode was not working. (After a lot of googling now I understand that is a common OPO problem...)
2. I found a GPS fix from this link http://forum.xda-developers.com/moto-g/development/lollipop-5-0-x-euphoria-os-t3016005/page142
and I didn't notice that was for MotoG before flash it! Damn!
After flashing that fix my SIM function completly brokes, no carrier, no signal, no possibilities to set up the apn... Nothing at all...
3. Wiped system, data, cache and dalvin cache and than flashed last cm 12 (internal data not touched). No SIM function...
4. Wiped all again and flashed last cm 12 with CAF kernel (because I found it more stable than others) and than flashed modem firmware for OPO from this link http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516
5. Results: no SIM function again...
I don't know what to do right now guys... Please help me, currently I have a phone with no phone capabilities
Thanks!!!!
Click to expand...
Click to collapse
You should flash your stock ROM do you can have a clean device again.. I'm probably sure that this would do the trick

Try to unzip the wrong GPSFix and read the script to see what it changes.

Thanks for the suggestions guys, right now I'm in vacation out of my country, so this is why I notice that without internet connection my GPS doesn't work and I've done this kind of mess trying to fix the problem.
l'll update you when I came back at home and I'll have a PC to better investigate the matter.
Happy new year!!!!

Bello Guys!
Just to let you know: as suggested, my problem is gone by flashing oxygen!
Than I've flashed my preferred ROM.
Thanks again!!

Do I need to flash anything other than just the ROM?

I recently rooted and flashed Sultan's MM ROM. I began to have network issues and this morning I saw No SIM Card error. Rebooting fixes it for a while, before it returns. I also see that the signal indicator drops to no bars a lot (used to have this on Lollipop too). I tried resetting APN settings. That didn't help much.
I flashed using TWRP 3.0.1. Could that be an issue? I see many threads saying that 2.8.6 was stable.
In this thread, the person said they had flashed CM Snapshot to address a similar error. Is that something I have to do? If so where can I find it? I am on TMo USA.
Or is there another fix?

Have you flashed latest modem?
http://blazingphoenix.in/mzo/ONE/Modems/

[CM14] Cell Signal can't connect, turns off immediatly after trying to reconnect

This is consistent across every CM14 ROM I've flashed. I am upgrading from CM13.
The signal bar at the top is blank as in "no service", it attempts to reconnect and show a signal for a split second but then goes back to "no service" again. When I remove my SIM card and reboot the problem simply vanishes, but of course I can't get LTE
Firmware: PCA
Recovery: TWRP 3.0.1.0
I have tried running the ROM stock with no data restore and I have tried flashing APN settings from this post.
I at first thought it was a CM14 bug but then I read that others had no problems with CM14 ROMs.

Assuming you actually have a SM-G900P (since a lot of people ignore that little detail) it's probably a matter of Cm14/14.1 doesn't appear to be wholly happy with anything other than the latest baseband, which is now PK1. To get it, just reflash to stock with Odin and then poke at the thing until it gets the two OTA updates that will bring you up to PK1. At that point if you like you can poke at the controls to update the PRL and Profile (just to be sure everything's good) and then let me suggest you make a call or two and/or send some SMSes to be sure you didn't mess something up when you tried to change the APN settings one almost never needs to touch, and then flash TWRP (or whatever recovery you use) right back in and sideload the Cm14.1 nightly and open-gapps for 7.1. Also, you will need to do a factory reset after upgrading to 14.1 or you'll get a wholly different set of misbehaviours out of the phone (trust me... I deliberately cut corners through multiple rounds of reflashing to find out what symptoms to look for). One of the more endearing failures can be no soft keyboard, nobody wants that.
I had a bunch of weirdness happening (including completely non-functional GPS) with CM14 a few days ago, and since the changelog doesn't seem to show anything addressing the screwy problems I had, it hints very strongly that people will need to update to PK1 before they can expect the device be reliable.
OH... and don't try and enable Adoptive Storage if it asks. The performance is abysmal for some reason (around 2Mb/s on a Class-10 card that otherwise hums along at 14Mb/s) and it will make any apps that are trying to use storage run like crap.

So people have it working on PK1? Has anyone had it working on PCA?
Edit: Odin restored PK1, it didnt want to boot after the reflash. I installed TWRP and restored a PCA Backup, updated PRL and profile. I flashed a cm14.1 ROM and still had the same issues.
It also didn't wipe my internal storage when I ran odin, which I remember it doing in the past.

Worked great on my S5 900P

Gracefully I got it to work on Resurrection Remix. Idk if it was the APNs or just more stable ROMs.
I booted RR stock w/o gapps, I went to enter in the APN settings using this site and it just magically worked after I entered in only the first line. It's hard to tell if it was because the ROM found out how to connect or if the first line of the APN settings triggered something.