I have mytouch 1.2 and flashed CM 5.0.7 and noticed when somebody called me I couldn't hear them, except on speaker phone. I tried everything, wiped out factory reset and audio wouldn't work. I went to the experimental 5.0.8 and audio still not working, unless I'm on speaker phone.
So I booted up in Amon's recovery and wiped everything out again and then put in the fender rooted image and thought that would work, but still no audio and speaker wasn't even working.
So I'm back to 5.0.8 that only calls with speaker work and nothing else seems to work. I tried youtube just now and no audio as well.
No clue on what to try next? Oh I did try a MT3G1.2 audio driver that was posted with CM 5.0.7 and nothing changed.
*********************
Update
Started from step one before loading ROMS and redid everything and now audio is working.
Related
Hi folks,
I tried out the MIUI ROM and liked it, but for various reasons, I wanted to go back to CMod again. So, I restored my NAND backup of my CM6 install. When I did this, I noticed that Bluetooth was no longer working correctly, i.e. it would pair successfully with my radio, but it failed to connect to it.
When I restored my MIUI backup, bluetooth worked again.
I cleared every cache known to man and once more returned to my CM backup, but once again my Bluetooth failed to work.
In the end, the only thing that seemed to fix the problem was wipe all the settings (again) and flash the latest CM nightlies (very nice btw!). After this, all was well.
I am attaching a logcat file if anybody is interested in the Bluetooth output. My totally uniformed suspicion is that it had something to do with the way MIUI uses the Bluetooth stack to get the radio working, but I'm sure somebody out there knows better than I do.
anyone experience this? flashed cm nightly worked fine, flashed a kernel no sound, wiped everything start from scratch, tried different roms, no sound
working now, weird
My friend had this issue. He had to get anew evo
I'd like to share my experience solving some basic problems with my nexus 4 running cm11, and 10.2
I had problems with the video freezing when shooting video
I wanted to improve the sound quality because I stream google premium and couldn't find a solution until recently
And had a rebooting problem in the end which I solved.
My nexus 4 worked perfectly running cm until I did the 4.3 update in november. After that the video would freeze when I was shooting. wouldn't happen all the time but would happen sometimes. I did everything, factory resets, reinstalling gapps, restoring the camera app, wiping data. Nothing worked. Even updating to cm 11 did nothing to change the situation. After having to go back to stock because of another problem I ran into -- installed Franco kenrnel on cm 11 and they aren't compatible -- I discovered that the video camera was still freezing. So I discovered it had nothing to do with cyanogenmod roms. Someone suggested flashing the separate photosphere gapp package along with the full gapps package and funny enough that solved the problem.
http://forum.xda-developers.com/showthread.php?t=2397942
I don't know if the recent updated photosphere gapp corrected a problem or what. But. Shooting Video now works.
I switched to omni rom because I wanted to use the franco kernel to adjust my sound settings, in my search for sound quality improvement but the omni rom was a real challenge and was plagued with bugs and wasn't for me. But stuck with it because of the franco kernel.
I then discovered that hells-core kernal did the same thing and works with cm11 so switched back to cm11 the stable snapshot version from last week and installed hells-core kernel. My phone started to reboot capriciously every 10 or 15 minutes and tried everything to correct that, eliminated data from apps, fixed permissions -- nothing worked, but finally decided to flash the latest cm nightly to see if the problem wasn't related to the version of the rom I was running .
When I flashed it, I wiped cache partition, delvik cache, and formated data , reflashed full gapp package plus the photosphere gapp. I didn't flash hells-core again. Maybe that was causing the reboots. I don't know. Everything now works perfectly. No more random reboots, the video camera seems to work fine, I discovered that the cm kernerl does have one volume gain adjustment and am now using viper4android effects equalizer that has gain control for both volume, bass and treble and everything is great. and my sound quality is probably as good as it will get on a nexus 4.
I spent an inordinate amount of time trying to resolve these problems so hope this is of some help to others.
After installing CyanogenMod 11 my phone worked great. Had better battery life. Performed faster. But then I wanted lollipop so I installed the Google play ROM since the bell s4 ROM wasn't out yet then finally went to liquidsmooth where I started encountering video playback problems on online content but all other sound worked fine. I tried going back to the stock ram then the USB cord broke halfway through and put my phone into a weird recovery mode that said use kies. Finally I put it into download mode and flashed it with another USB. I never tested audio but the WiFi wouldn't turn on so I tried flashing modem files only for it not to work. Finally I went back to CyanogenMod 11 but the dialer crashes when I try to call. The music crashes when I try to play it. YouTube videos won't load nor will Facebook. My phone is a mess.
(BTW my phone had a little android dude on the ground with his stomach open and a little red triangle with an exclamation mark in it when booted into recovery. Idk if that means anything)
Please help, how do I fix my phone?
Do you ever wipe before flashing?
As I am a new member I could not post on the Umi page.
I bought the Zero for my daughter last year. It had problems from the outset with soft keys, reboots and microphone not working. UMI would not refund or replace. OTA updates did not help. It was running Kitkat at the time. Installing Rootjoy and ROM R.50 V4 did work. I got soft keys back by editing the System/Build.prop file adding qemu.hw.mainkeys=0
A few weeks ago the keys disappeared and all sound: notifications, ring, music, Youtube. The headphone jack stopped working. Bluetooth for music does work. The phone rebooted at random.
I installed TWRP recovery and the ROM CM 12.1: no sound or keys.
I flashed individual partitions via Fastboot but could not change System or Recovery. I didn't try erasing first. ADB does not recognise the device.
On the assumption the sound drivers were included on the earlier UMI ROM's I tried ROM's from NeedRom and SPFlash but could not get it to work. Presumably because I had the wrong USB drivers. My pc runs Windows 7.
Back to RootJoy and I installed V3.10: no sound. Then one at a time the OTA updates 3.03 3.05 and 3.06 still no sound.
I then reinstalled the ROM R.50 V4. No sound. I added soft keys by editing Build.prop.
I tried changing the audio settings in Engineering Mode: nothing.
I tried the Soundabout app, ignoring in/out detection for the headset: nothing.
I tried canned air and a pick in the headphone socket: no fluff, no sound from the speaker.
I compared the Build.prop file with a reference I found on the web. They were almost identical apart from the name of the engineer, date and where the name of the device was recorded.
When I used TWRP to wipe and install the Cyanogen mod I used advanced wipe and also erased the internal storage. Was that a mistake?
Does anyone have any ideas, please?
Solved
It was a hardware problem.
I replaced the lower pcb and connector ribbon.
Where do you buy the pcb? In every store is out of stock