I have a Kindle Fire Hd 8.9 and just installed CM11. Now I find that many of my apps and games do not make sound as they are supposed to. Also, my notifications do not make sound. Although YouTube does work as far as audio is concerned.
Is this issue a CyanogenMod thing, or can I fix it by myself?
Thanks!
Did you get this fixed?
I've been on a bunch of CM11 builds and have never had audio issues (apart from the occasional stuttering that was fixed in one of the recent builds). Did you check the md5 for the rom you downloaded? Was it a dirty flash over a previous rom?
If you're still having the same problems, I would just factory wipe and reflash.
Ken
Pokeroo said:
Did you get this fixed?
I've been on a bunch of CM11 builds and have never had audio issues (apart from the occasional stuttering that was fixed in one of the recent builds). Did you check the md5 for the rom you downloaded? Was it a dirty flash over a previous rom?
If you're still having the same problems, I would just factory wipe and reflash.
Ken
Click to expand...
Click to collapse
sorry for the late reply. It could have been a dirty flash. When I updated to a newer build, the issue went away. So it's all good!
Related
This is a question regarding Twa_Priv's 4.1.2 10/13 updated ROM.
1,) Does a TRRS headset (headphones with mic) work now? I know that lots of devs were working on getting the mic to work with jellybean, I just don't know if it has gotten around to working on the newly updated ROM
3.) I have had trouble with Amazon appstore not recognizing my KF as a kindle since the last ROM where I clean installed from scratch, so it won't let me install kindle-specific apps. Has anyone had this problem, and does anyone know a way to get around this?
4.) One more issue. I think that this is just a personal problem somehow. I have been having trouble restoring backups. I use Twrp 2.2.2.1 and it seems to create backups fine, it just wont restore them. I haven't tested out if it works with the last 3 builds, because then I have to start from scratch again if it doesn't work, and that takes a lot of time... I had twrp originally then switched to CWM because I thought I had to for an app, then discovered that I REALLY like TWRP better, so reflashed it, and it hasn't worked since then. Any pointers?
thanks
Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks
Could have been a bad flash / download
Did you check the md5sum?
leftcranium said:
Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks
Click to expand...
Click to collapse
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.
topherk said:
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.
Click to expand...
Click to collapse
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.
leftcranium said:
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.
Click to expand...
Click to collapse
Yeah, a full system wipe might be the ticket. Let us know if that works.
I'm Back Baby
I tried a system wipe and a rooted stock rom. This didn't work. I then tried the LJ7_Stock_with_count_reset16 rom and my sound was ok. I cleaned out the mic hole with a pin and bam sound was like normal. I'm now back on TPRGS3.14 and everything is good. I think I had 2 issues but possibly only 1. messed up mic from multiple flashes and crap in the mic hole. I guess checking for a physical problem even as small as a mic debris is an easy first step.
thanks for the suggestions
Like the title says, on every 5.1 ROM I keep getting random reboots. They happen indiscriminately, with no clear reason at all. Other people report no issues at all. On 5.0.2 I have no issues at all. I have no idea what causes it could be or no knowledge on how to diagnose it...I want to use 5.1, but if this keeps happening I don't think I can ?.
I've not had any issues with random reboots, been running euphoria rom (updating with each new build) and glitch kernel for weeks with no issues.
Assuming you're doing clean flashes, with no extra mods, and not restoring system data, yes? Its even possible that restoring app data from backups can cause weird things to occur at times. If you haven't yet, wipe everything and clean flash, restore apps only from play store, and see if it still happens.
Otherwise, maybe a specific app is causing problems? You could try and grab some logs to narrow down the cause, but I know that's very tough to do if the issue is intermittent and seemingly random. Still it is the only way to tell for sure what's happening.
Here's a guide on how to grab the different logs if that helps at all: http://forum.xda-developers.com/showthread.php?t=1520508 .
LucentBirch said:
Like the title says, on every 5.1 ROM I keep getting random reboots. They happen indiscriminately, with no clear reason at all. Other people report no issues at all. On 5.0.2 I have no issues at all. I have no idea what causes it could be or no knowledge on how to diagnose it...I want to use 5.1, but if this keeps happening I don't think I can ?.
Click to expand...
Click to collapse
The random reboots are caused by outdated 5.0.2 binaries, if you update to 5.1 it should mend it random reboots. Also if your ROM developer might or will update the ROM to 5.1 with the updated binaries!
Killah1994 said:
The random reboots are caused by outdated 5.0.2 binaries, if you update to 5.1 it should mend it random reboots. Also if your ROM developer might or will update the ROM to 5.1 with the updated binaries!
Click to expand...
Click to collapse
Well I know for a while that some 5.1 roms were using the 5. 0. 2 binaries because the 5.1 weren't released yet... And they never really said whether or not they updated the binaries or if they were even released...I updated my tablet to a 5.1 R_5 this morning and it hasn't rebooted all day...so maybe they have?
LucentBirch said:
Well I know for a while that some 5.1 roms were using the 5. 0. 2 binaries because the 5.1 weren't released yet... And they never really said whether or not they updated the binaries or if they were even released...I updated my tablet to a 5.1 R_5 this morning and it hasn't rebooted all day...so maybe they have?
Click to expand...
Click to collapse
5.1 binaries and factory image for this device were just rolled out today. This may indeed resolve your issues, but give the custom rom devs some time to catch up, they'll need to grab the latest source and post new builds for the latest binaries to be included.
Same thing here
I excitedly loaded up the 5.1 build on my 2013 wireless today. SAME ISSUE. I can't do anything .
I didn't wipe the device when I upgraded. I was rooted - unrooted / flashed / rooted using the Nexus Root Tooklit as I have since Jelly Bean. I used the option to use NO WIPE MODE to try and keep my apps intact.
Any help appreciated.
mrdrumsc said:
I excitedly loaded up the 5.1 build on my 2013 wireless today. SAME ISSUE. I can't do anything .
I didn't wipe the device when I upgraded. I was rooted - unrooted / flashed / rooted using the Nexus Root Tooklit as I have since Jelly Bean. I used the option to use NO WIPE MODE to try and keep my apps intact.
Any help appreciated.
Click to expand...
Click to collapse
in that case you should try wiping then flash the 5.1 factory image and see if it works.
PrizmaticSmoke said:
5.1 binaries and factory image for this device were just rolled out today. This may indeed resolve your issues, but give the custom rom devs some time to catch up, they'll need to grab the latest source and post new builds for the latest binaries to be included.
Click to expand...
Click to collapse
cm12.1. rebooted once today while using chrome.
Reboots better!
I concur with the messages I've been seeing. After several app updates over the weekend, culminating in some Chrome updates, the tablet seems stable. I haven't re-rooted it yet.
I wonder if something has to do with the "notification crash" error listed in the changelog for 5.1.1.
Either way, looking forward to 5.1.1!
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Oyongx said:
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Click to expand...
Click to collapse
I'd try using the latest wild kernel.
g0at1 said:
I'd try using the latest wild kernel.
Click to expand...
Click to collapse
well i think i did try wild kernel with cm12.1 latest nightlies. The issue gotten worse. More random reboot occured.
Currently on slimLP with his zerkernel v1.7. I thought this one is perfect, but then out of nowhere the random reboot occured again. It's not as frequent as before but still happen.
Right now I'm using Mokee with wild kernel and everything is going well.
Oyongx said:
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Click to expand...
Click to collapse
Random rebooting is a common issue with all the cm 12.1 based ROM for lg ogp. The cm12. 1 in my opinion was never fully stabilized even by the time the devs were starting to switched to the newer hardwares. If you keep the number of apps you unstated to minimum, you may be able to keep random rebooting down, but this just my observation. I thought the latest bliss pop 4.03 had the rebooting issues sloved, but it rather just had the occurrence down to where it's less. But there are other issues such as the device getting extremely hot, which in turn causes shutdown. To the point where I give up on using LP once again on this device, and move back to kk. The kk may be an older rom, but at least it's stable. With the LP, I think issues with it unable to find the sim card, GPU issues that cause screen to flicker and blackout, all are never fully fixed. Rather, those issues were patched and rigged to make the rom run, but not smooth enough where you see issues such as rebooting and overheating.
Sent from my LG-E980 using XDA-Developers mobile app
hawkwind212 said:
Random rebooting is a common issue with all the cm 12.1 based ROM for lg ogp. The cm12. 1 in my opinion was never fully stabilized even by the time the devs were starting to switched to the newer hardwares. If you keep the number of apps you unstated to minimum, you may be able to keep random rebooting down, but this just my observation. I thought the latest bliss pop 4.03 had the rebooting issues sloved, but it rather just had the occurrence down to where it's less. But there are other issues such as the device getting extremely hot, which in turn causes shutdown. To the point where I give up on using LP once again on this device, and move back to kk. The kk may be an older rom, but at least it's stable. With the LP, I think issues with it unable to find the sim card, GPU issues that cause screen to flicker and blackout, all are never fully fixed. Rather, those issues were patched and rigged to make the rom run, but not smooth enough where you see issues such as rebooting and overheating.
Sent from my LG-E980 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, i think the issue are only on cyanogen based ROM. When i use the lolipop such as Super Mini V6.5 by henrypham91 and lgviet team, it's all good. Deep sleep normaly, no sound delay when game on 2D graphics, and all. But then again, it's noticeably slower if you compare against CM head to head. I really love CM or AOSP based rom because they are so fast.
g0at1 said:
Right now I'm using Mokee with wild kernel and everything is going well.
Click to expand...
Click to collapse
Never heard about Mokee. I'll look maybe and try that. Thanks Edit: it is an AOSP based rom! Might try that. Hopefully my phone survive lol
Oyongx said:
Never heard about Mokee. I'll look maybe and try that. Thanks Edit: it is an AOSP based rom! Might try that. Hopefully my phone survive lol
Click to expand...
Click to collapse
Mokee is a Chinese CM based rom.
g0at1 said:
Mokee is a Chinese CM based rom.
Click to expand...
Click to collapse
The download link seems invalid. I don't understand chinese but on the downlaod the url there's an error 404 written. :silly:
Oyongx said:
The download link seems invalid. I don't understand chinese but on the downlaod the url there's an error 404 written. :silly:
Click to expand...
Click to collapse
Their website has an English version. There should be a British flag on the upper right side. Then download their history zip which is a kind of final release.
Does anyone experience loud beep from bottom speaker after ending the call? I have no idea how it started, but I can't seem to find the culprit and it's very annoying. I saw some posts that it might be snapchat related, but I don't use it and don't have it installed. I'm on RR 8.1 with aroma gapps. Thanks for suggestions.
I'm on RR 7.1 and don't have the issue.
Someone on the RR 8.1 thread was complaining about it but that was probably you.
What have you tried so far to resolve the issue?
I would start by dirty flashing the ROM again.
CZ Eddie said:
I'm on RR 7.1 and don't have the issue.
Someone on the RR 8.1 thread was complaining about it but that was probably you.
What have you tried so far to resolve the issue?
I would start by dirty flashing the ROM again.
Click to expand...
Click to collapse
I dirty flashed official RR 8.1 and still the same issue. I guess I'll have to do a clean flash and check when it happens. It started happening sometime after I restored my apps via TB. Wish there was a fix so I could avoid the trouble.
Thanks though.