Develop Bugs

Extremely Weird Sound Glitch

I recently started using my AT&T Galaxy S3 again and wanted to make sure that everything was up-to-date on it. I did a clean install of everything and cleared my cache and dalvik first beforehand. I updated the following:
CyanogenMod to 11-20141112-SNAPSHOT-M12-d2lte
GApps to kk-20140606
Baseband Version to I747UCUEMJB
Now, seemingly randomly, all audio on my device will stop working; from Apollo, to YouTube, to system sounds and ringtones. Rebooting the phone solves this issue temporarily. However, when I plug my headphones in, that seems to be the catalyst for the issue. Once I have them seated into the jack, all sound then stops and will not resume, even if I remove them, until I reboot. Stranger still, is that if I am playing music and THEN plug in my headphones, it will continue to work as normal.
I had a stable nandroid backup of CM10 that I had been running for the longest time that I reverted to, but the problem persisted.
Somehow, it seems to be related to when I updated the baseband version. I originally flashed CM and GApps cleanly only to find I had no data connection. After some digging, it seemed that newer versions of CM were no compatible with the baseband I was using which is when I proceeded to get the latest one and flash it. All of these strange issues with audio started happening after that. I tried flashing a couple of older baseband versions, but that did not alleviate the problem.
Anybody have any suggestions? I am tearing my hair out trying to get to the bottom of this

NinjaBurg3r said:
...I updated the following:
CyanogenMod to 11-20141112-SNAPSHOT-M12-d2lte
GApps to kk-20140606
Baseband Version to I747UCUEMJB
....
Somehow, it seems to be related to when I updated the baseband version....
After some digging, it seemed that newer versions of CM were no compatible with the baseband I was using which is when I proceeded to get the latest one and flash it. All of these strange issues with audio started happening after that. I tried flashing a couple of older baseband versions, but that did not alleviate the problem.
Anybody have any suggestions? I am tearing my hair out trying to get to the bottom of this
Click to expand...
Click to collapse
What baseband (modem) and bootloader do you have on your phone? You say that you upgraded to MJB, but then later say that you flashed the latest baseband, which is NJ1 for the i747. Were you flashing only basebands or both bootloader and basebands?
What you should do next depends on the current bootloader and modem, and if they are the same version.
Once this device reaches the MJB bootloader you can no longer downgrade the bootloader with risking bricking the device. Once you reach either of the 4.4.2 bootloader and modem pairs you risk bricking the phone if the versions are not the same.
Check before going any further. Either use the Phone Info -- Samsung app from the Playstore, by vndnguyen. Or use terminal emulator commands. There is the chance that some of the flashing did not take and your phone is not at the version of either bootloader or baseband that you think it is.
Code:
getprop ro.bootloader
getprop | grep version.baseband

I had this same sound problem on multiple CM11 based KitKat ROMs. I don't recall whether it got fixed on KitKat or not; I've since switched to lollipop ROMs and haven't seen this problem since. You might try flashing a more recent CM11 nightly to see if the audio thing has been fixed. You'll find the most recent builds under d2att since the d2's have been de-unified.
If you choose to give lollipop a try you will probably need to get your firmware up to NE4 or NJ1. Early on some people were running lollipop on MJB, but I don't believe that is still the case.

CM13: Updating to newer Nightlies locks me out of my phone

For the last 2.5 weeks I have been unable to update to any of the newer Nightlies for Cyanogenmod 13 on my Asus Zenfone 2. After the update is finished my phone claims I am using the wrong password to try to access my phone. I am not using the wrong password, updating seems to change it for some reason. Because I am unable to access my phone I am forced to boot into TWRP and revert to the last build that was stable for me. So far I have only tried two newer builds, the most recent one as of this post (August 3rd) and another one last week (July 27th). Neither work, the build I currently run that works with my current lock screen password is July 17th.
Nightlies for my specific device.
I have done a bunch of forum and google searching and nobody else seems to have ever had a problem like this. I would try to report this as a bug to the CM team but bug reports aren't allowed for Nightlies.
Any help is greatly appreciated.

Edit: Fixed
I fixed the issue by disabling the lock screen, updating to the latest nightly, and re-enabling the lock screen.

Have you tried clean flash?

How to get from CM10 alpha to CM10.2 stable to CM13 nightly - some info and steps

[This isn't a request for help, I managed to muddle my way through it, but the info needed seems to be scattered and disjointed, so I thought I'd post it here for others.]
Started with a AT&T Galaxy S III phone running a beta version of CM10 (which could never get OTAs). Wanted to get to a stable or more recent version of CM. This phone is referred to as a SGH-i747 or d2att.
Trial and error:
1st Attempt - Flashed TWRP 3.0.2, flashed CM12.1 release, phone boots gets to starting applications and then dies (poweroff).
2nd Attempt - Flashed CM10.3.1 -> fails to flash ro.bootloader does not match expected values
3rd Attempt - Flashed CM10.1 -> fails to flash ro.bootloader does not match expected values
4th Attempt - Flashed CM10.0 -> Works
So, what's going on?
ro.bootloader is the baseband (cellular radio firmware). My phone had "I747UCDLK3", CM10.1 and require Jellybean compatible radio baseband... CM10.1 advise are trying to tell you that your baseband is too old (ro.bootloader is a misleading name for your baseband). In Android you can see your baseband under "About Phone" in settings, or by opening a terminal and typing "getprop ro.bootloader". In TWRP, you can open the terminal and type "getprop ro.bootloader" to get the value.
Fixing it:
I tried lots of different flashes until I found one that uses JOdin3 to flash the radio. The links for JOdin3 are all long dead, but someone mirrored the JAR files here: http://3of5.com/builds.casual-dev.com/files/JOdin3/. In any case, this got CM to see my baseband as I747UCALEM, however TWRP still saw my baseband as I747UCDLK3. This update was enough to get CM10.3.1 running with cellular signal (did not test calling).
Next thing was applying CM12.1, which flashed and started this time, however "Sim card is missing" was reported. CM12.1 + require still newer baseband firmware to work. I was able to find a list of baseband/radio firmwares here: http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772, the link there (https://www.androidfilehost.com/?w=files&flid=10522) allows you to download flashable packages. I flashed the I747UCUEMJB baseband/radio firmware and then reflashed CM13.0 nightly and Open GApps using TWRP so I could give the phone to my father.
With I747UCUEMJB, CM13 boots and recognizes the sim card. Once we are no longer roaming we'll test to see if further baseband firmware updates are necessary.

undetected sim, Unknown baseband, Rogers, d2can, cm14.1

I recently installed cm14.1 on a Rogers d2can phone and I got unknown baseband and sim card stopped working. I tried flashing different modems which made the situation worse as now even old cm11 roms show unknown baseband.
Can someone please tell me where I can download modem zip file that works for Rogers and for cm14.1?

I recommend flashing the latest KK stock ROM from sammobile.com which will restore your phone back to stock and ensure the bootloader and modem/baseband are matched. After flashing stock and confirming that the imei is correct, then flash twrp, cm14.1, and gapps.

I was downloading from sammobile.com very slow and the download was interrupted in the middle. I will try again later.
Is there a better site to download firmware from?

So I downloaded it and flashed using odin. Flashing took a while but it passed. The phone got stuck on bootloop though.
So I booted to stock recovery and performed a factory reset. Booted again. Now it works!
I'm going to stay on Touchwiz 4.4.2 for a while.

Glad you got it working.

I would not call "staying on Touchwiz 4.4.2", "working" more like opening yourself to a long list of known exploits.
Others are having the same issue (cyanogenmod is dead so I removed the link, hope LineageOS fixes the issue some day.)
Using the last good CM-13 build is probably the best for now.

sim not provision ed MM#2...... easiest fix ....please n thanks;;;;

We'll need more information in order to help solve the sim problem like model #, ROM, etc.

Upgrading Firmware + Modem

Currently my OP3 has LineageOS 15.1 with installed firmware and modem from Oxygen Open Beta 32. Is it really safe to upgrade firmware to the latest open beta (for now it's version 37), as it is suggested at official LOS 15.1 for OP3 thread? Won't be there a problems with, for example, device encryption, which might be changed in firmware packages?

Always updating my MODEM and Firmware and never had problems.

I did try to flash latest LOS 15.1 today with latest OB37 and had an Encryption Unsuccessful error and could not boot, asking me to Format. I actually do not know what was causing the error as I did not try to troubleshoot, but it was the first time I was trying to flash any rom with the latest OB37. Don't know if that means anything.
I always flash OB31, it has better battery drain than latter ones.