[Q] Audible issues after root and CM13 - Galaxy S 5 Q&A, Help & Troubleshooting

Hi all,
I recently - all of five days ago if that - rooted, TWRPd and flashed the latest CM13 nightly onto my wife's Galaxy S5. Since then she is consistently getting some problem with audible where it claims "Cannot play this title". The only solution I've found is to clear cache and data for the app and set it up from scratch. This then temporarily makes Audible work again.
Does anyone else use Audible and confirm that this isn't the correct behaviour?
In terms of potential solutions, I don't want to mess too much with her phone and try different ROMs etc, so sticking with CM13 is preferable for now.
I might stick the same ROM onto my OPO and see if I can reproduce it there as a first step, but I'm curious if anyone has seen this behaviour and can help.
Thanks for any advice.

This is also happenin to me on my Zenfone 2 (ZE551ML) running cm13 official (13.0-20160423-NIGHTLY-Z00A)
I've been able to recover by turning off the "Storage" permission (Settings > Apps > Audible > Permissions) and then luanching a title from Audible and re-enabling the permission from Audible. This at least avoids me having to redownload the book.
Don't know how to stop it from occurring outright, it seems to happen after every cm upgrade, and then randomly thereafter.

Related

Sound randomly not working?

My sound will randomly stop working. This includes all sounds, such as the keyboard, selecting items on the homescreen, and watching movies or listening to music. A restart will usually solve the problem, but I have no idea what's causing it. Anyone else experiencing this or have a suggestion? Since a restart fixes it, I assume it is software related. I am running a fresh install of the most current EdenX ROM.
Anyone else?
I've flashed all the ROMs, used the unbricking procedure, wiped data and cache 1,000 times. Surely someone else is seeing this?
This has been happening to me as well, except that when my sound cuts out my Adam also emits a very loud static noise from the speakers. If I click things after that, it either makes the static noise or no noise at all. It has happened on every rom I've tried, including stock, and only a reboot will fix it. I emailed support and they asked me to send them a recording of the noise (I had offered to make them one to help them diagnose the issue).
I finally figured out what was causing this for me. I was restoring apps using Titanum Backup and the backup from my Android phone. There was something in there that didn't play well with the Adam, so it's not happening anymore since wiping everything and installing each app one by one.

[Q] Galaxy S4 In-Call sound issues, ROM issues, app issues

Not sure if this is the correct place to post this, but here goes...
Just got a Galaxy S4, and there are several very annoying quirks/problems that I hope someone can help me resolve.
I'm using stock Android 4.2.2
1) I have a 200mb data limit so that flies away in a blink of an eye unless data is restricted. There is a way to disable data, but not RESTRICT it. On CyanogenMod with my Galaxy S3 there is a way to still be able to download emails other things, but restrict all other background data. At least that is what the effect seems to be because my 200mb easily lasts me a month. On the stock Android with the S4 there doesn't seem to be an equivalent option at all. Am I wrong?
2)CyanogenMod has an option to boost in-call volume, which makes the thing so damn loud, I can hold the phone about 3-4 inches away from my ear and still hear clearly. Best of all the option STAYS. It never gets disabled unless I disable it. The stock Android on S4 also has a boost option, but it hardly has any effect at all, boosting volume only ever so slightly, and what's really aggravating, has to be enabled in-call every time a call is made. There is no way to make it "stay". Is there anything I'm missing?
3)I cannot apply a latest "Stable" version of CM to my S4. That is, it installs fine, but keeps saying "unfortunately android keyboard has stopped". So I cannot type anything. Is this a known issue?
4)I have mind to keep using the stock ROM, because I want to have some of those nice hover gestures, S-Health and few other things, but the problem with disabling data is very annoying, plus S-Voice keeps crashing all the time... What gives? IS there any way to fix S-Voice?
5)Finally are there any modified stock ROMs which have all the good stuff and none of the bad? ; ) And if not, are there any ROMS except for CM that you can recommend for the S4?
Thanks very much.

[Q] No audio during call - Nexus 4 CM11

Hi,
I have a Nexus 4 running CM11.
I am not getting any audio during calls. In the earpiece or speaker. Music, notifications, Skype, etc are working fine.
Tried using Soundabout, but that did not make any difference.
Sometimes when I boot the phone, I am getting audio in the first 3-4 calls that I make. But when I close the dialer and open it again, I don't get any audio
Thanks in advance!!
GandaBaccha said:
Hi,
I have a Nexus 4 running CM11.
I am not getting any audio during calls. In the earpiece or speaker. Music, notifications, Skype, etc are working fine.
Tried using Soundabout, but that did not make any difference.
Sometimes when I boot the phone, I am getting audio in the first 3-4 calls that I make. But when I close the dialer and open it again, I don't get any audio
Thanks in advance!!
Click to expand...
Click to collapse
I'm experiencing the same issue with my nexus4/CM11...
Not found the cause nor the solution yet :crying:
I just made an update from nightly 20141024 to 20141031 and this issue is still present.
Exactly the same problem on Nexus 4. Manifested in snapshot M11.
I've been having the same issue.
I'm trying different basebands now but still no luck.
I'm using CyanogenMod 11 11-20141009-UNOFFICIAL-mako with baseband 2.0.1.1701.03 and I don't have this issue.
Flash the latest radio, try a clean flash then try again. Stay with the stock CM kernel too !
I already have the latest baseband and I am using the official CM kernel. The issue started somewhere during last week's nightlies and it is very likely that even the upcoming M12 build has this issue on Nexus 4 devices.
Not a hardware problem
I wiped and flashed back to a factory 4.4.4 last night and the problem seems to be fixed. So at least we know it's not a hardware issue. I was also able to make calls through hangouts just fine.
I had already flashed the latest 1.03 radio as well as the original stock radio and most of the ones in between and that didn't work. Clearing data for the phone app didn't seem to do anything at all.
Try doing a clean install of the latest nightly or monthly and see if that works.
I bet that if you uninstall and reinstall the phone app that it would start working again.
I just created an issue on the bug tracker: https://jira.cyanogenmod.org/browse/NIGHTLIES-324
If you have any additional information please add them to the issue to improve the chances of a fast bug-fix.
still working
I knew I couldn't stay on stock very long.
Flashed 20141102 and in call audio is still working.
Did anyone try a clean install of the latest nightly?
Try to reset only the telephone app (com.android.phone) and reboot.
Worked for me.
EDIT: Doesn't work anymore.
Downgrade to google play services v6.5.86 fixes incall audio for me.
Code:
adb install -r -d Downloads/com.google.android.gms.apk
3563 KB/s (29005798 bytes in 7.949s)
pkg: /data/local/tmp/com.google.android.gms.apk
Success
@ ivanich:
thanks, my solution doesn't work since the google play service update.
Another solution should be to install the gapps again, but I didn't try it.
Greetings
https://jira.cyanogenmod.org/browse/CYAN-5728
This has been an issue for some time.
The evidence leads us to believe that google play services is the culprit at this time. But why does it plague only the Nexus 4's running CM?
(25 OCT) - When this issue was identified initially. The issue can be temporarily resolved by disabling wifi and restarting the phone. With WIFI off the phone will make and receive calls for at least 2 day without regressing(i personally tested this) as soon as you turn on the wifi, 1 - 4 calls in the audio is gone.
(10 NOV) - Two weeks passed since the initial reporting and the issue went away, assuming because google play was updated. At this time I was able to make and receive calls normally for a week or two. Then out of the blue, no audio. I disabled wifi and rebooted, the audio was back. The difference this time was the phone kept working normally for another two weeks.
(12 DEC) The issue has resurfaced, assuming google play was updated again and we are back to experiencing the issue with the initial levels of severity.
It looks like Google Play Services 6.5.87 will cause the issue. 6.5.86 works fine. 6.5.88 is unknown, 1 report says it doesnt.
Saml01 said:
https://jira.cyanogenmod.org/browse/CYAN-5728
This has been an issue for some time.
The evidence leads us to believe that google play services is the culprit at this time. But why does it plague only the Nexus 4's running CM?
(25 OCT) - When this issue was identified initially. The issue can be temporarily resolved by disabling wifi and restarting the phone. With WIFI off the phone will make and receive calls for at least 2 day without regressing(i personally tested this) as soon as you turn on the wifi, 1 - 4 calls in the audio is gone.
(10 NOV) - Two weeks passed since the initial reporting and the issue went away, assuming because google play was updated. At this time I was able to make and receive calls normally for a week or two. Then out of the blue, no audio. I disabled wifi and rebooted, the audio was back. The difference this time was the phone kept working normally for another two weeks.
(12 DEC) The issue has resurfaced, assuming google play was updated again and we are back to experiencing the issue with the initial levels of severity.
It looks like Google Play Services 6.5.87 will cause the issue. 6.5.86 works fine. 6.5.88 is unknown, 1 report says it doesnt.
Click to expand...
Click to collapse
6.5.88 and 6.5.94 are broken too .
ivanich said:
6.5.88 and 6.5.94 are broken too .
Click to expand...
Click to collapse
6.1.88 is broken for me aswell, even with the latest 1.04 radio version it doesnt work
ivanich said:
6.5.88 and 6.5.94 are broken too .
Click to expand...
Click to collapse
Actually I just installed 6.5.94 (over 6.5.87) and my in call audio is working, at least for now.
Reboot to recovery and clearing cache resolved issue for me.
Thanks,
turning wifi off helped.
How can I force google not to update the Google Play Services ?
It is not an regular app from the market.
I've tried to disallow all automatic updates, this doesn't help.
Greetings
Clearing cache
Rebooting into recovery and formatting the cache partition worked for me as well.

[Q] No mic/earpiece in calls

Situation
Bought Nexus 4 refurbished, works great except for this issue. Back speaker works great, Google Search works with mic (Ok Google). Updated via OTA all the way to 5.0. Am using phone on a carrier in Ecuador.
Problem
When making a phone call over the local carrier, call connects (you can see the counter on screen), music, if playing, pauses as it should. But no audio from the earpiece, and the other side does not hear anything from my side. Tried putting call on speaker, nothing. Tried with headphones, nothing. However, when making a Hangouts call over data, mic/earpiece work fine. To me, this means the hardware functions, so it must be software related. The phone sends SMS without issue, so it works with the local carrier. Also data works without any issue.
What I've done so far
Searched high and low, and it seems this is a somewhat common problem that some have fixed in many different ways. Please let me know if you know of another that I may have missed.
Downgrading to 4.4.4
Upgrading back to 5.0
Factory Reset
Flash 5.0 Factory image
Upgrade to 5.0.1
Flash complete 5.0.1 Factory image
Flashed latest CM11 nightly
Tried several "solutions" found on Google Group forum, such as pluging headphones in and out
Flashed Hybrid modem with included audio fix
Switched SIM cards
Installed SoundAbout, and tried many different options - redirecting Phone Audio, even changing options for Headset detection (thought the phone was confused, thinking the headphones were in)
Tested mic with recording apps and by recording videos, all work fine.
Installed PAC-ROM without Gapps to see if it was the Google Play Services issue
Disabled the CheckInService
I think I've tried more, but can't remember them all. It's been over a week, and can't answer or make phone calls.
Coming to my wits end, and it's extremely frustrating since it doesn't seem to be a hardware issue, and I hate giving up on something I can fix. Any suggestions?
(Edited and added a couple more tests to the list)
yep, you are not the only one with this issue, it started to plague users just recently, including me and from what i've learned so far it has got something to do with google play services.
however for me, flashing 5.0/5.0.1 resolved it (i only encountered it on CM4.4.4 )
here is another topic bout this. good luck
http://forum.xda-developers.com/nexus-4/help/audio-call-nexus-4-cm11-t2924589
ps. this thread i linked above acutally contains some solution/workaround involving disabling one of the google play services. just read through the whole thread
If this is really about Google Services, try installing a ROM without adding GApps. You can then state if they are really the culprit here.
I too had the exact same problem. I was on CM 4.4.4 nightlies. Moving to stock lollipop5.0 solved the problem.
Shooting Star Max said:
If this is really about Google Services, try installing a ROM without adding GApps. You can then state if they are really the culprit here.
Click to expand...
Click to collapse
I tried that too. I installed PAC-ROM, the latest nightly, without GAPPS. Booted fine, all seems to be working except sound in calls.
I also tried disabling the CheckIn Service, as was mentioned in the other thread, still no luck. So frustrating!!
I'll try them all again...
HijoProdigo,
+1 on flashing a 5.0 ROM.
Same thing happened to me a couple of weeks back. After messing with the phone for three days, flashing a Lollipop ROM solved the issue (I used CM12 unofficial nightlies)
BitteredBro said:
HijoProdigo,
+1 on flashing a 5.0 ROM.
Same thing happened to me a couple of weeks back. After messing with the phone for three days, flashing a Lollipop ROM solved the issue (I used CM12 unofficial nightlies)
Click to expand...
Click to collapse
I'll give it a try. I had tried with the official CM11, both with and without Gapps, but no luck.

SM-N900W8 & CM11 M12 bugs and issues :(

I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.
I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app

Categories

Resources