Hello,
I have a Nabi 2S that was just recently updated to the 'blue morpho' update. Post update, we have discovered that our Nabi 2S will only play notification sounds and audio through the headset. There is zero music/audio from any game or video through the speakers. I have performed two factory resets on this Nabi 2S as a last ditch effort to restore speaker volume to no avail. I have also cleaned out the headphone jack with compressed air to ensure that there wasn't a hair or lint causing a short circuit. We recently called Nabi tech support for troubleshooting assistance and were basically brushed off to a 'Nabi repair center' (we were supposed to receive a list of repair centers yesterday and have not yet) due to the Nabi 2S being out of warranty. THIS ISSUE DID NOT OCCUR BEFORE THE BLUE MORPHO OTA UPDATE! In addition it does not appear that Nabi will be providing an update to the Nabi2/2S to resolve this issue any time soon.
Do a Google search for Nabi 2 no sound and you will see this to be a more than a one off occurance. One of the recommended 'fixes' provided through Nabi was to install an app SoundAbout from the Play Store...what?!?! I have to use a third party app for something that should work natively and did prior to the blue morpho update?
To be clear...this Nabi 2S will only play any audio through headphones...there's no way I'm letting my 2 and 5 year old children use headphones for YouTube Kids or game audio.
According to Android LogCat, audio is being routed to headphones when headphones are plugged in but audio will not route back to speakers once the headphones are unplugged. Kinda odd considering if you go to Settings - Sound and Notifications you can select a Notification and it plays through the speakers fine.
From my Nabi 2S Settings - About Device.
Model - SNB02-NV7A
Edition - SNB02-NV7A-US
Android version - 4.4.2
Kernel version - 3.1.10 11/7/2014
Build number - KOT49H_N2S-KK442_02_00_141107_273
Product version 2.0-release keys
Would anyone know a real resolution to this audio issue other than...
A-using a third party app
B-paying to have Nabi or a 'repair center' perform a clean factory flash of the ROM
C-selling this thing on Ebay for parts only/broken with a less than stellar seller write up
Thank you for any information you can provide. If there's any additional information, logs, or files from the Nabi 2S I can provide please let me know.
Related
Okay so this is the most bizarre problem I have ever had with my phone. I am running stock 4.4.2 on a D6503 Z2 on AT&T's network. Rooted and running xposed.
Ear buds in questions are skull candy inked 2 (yeah I know they're a crap brand)
So on to the actual problem at hand:
This morning my ear buds just randomly stopped working when plugged in; outputting the sound through the external speakers instead. Found a temporary work around by switching the text to speech output from Google to Pico TTS. Ear buds worked again and the phone was recognizing that ear buds were plugged in, but sound switched to external speakers when the phone went to sleep or got a notification. A soft reboot seemed to fix this if I also changed the TTS output. That worked for about two hours and then TTS trick ceased working for me.
Once I got home, I tested other headphones and there is no issue with any of the three pairs I tried. Here is where it gets weird though, the skullcandy ear buds work just fine on everything else! I tried it on my Z1 tablet and my old HTC one x. Working fine. I am waiting for my boyfriend to come home to test on his phone because he also owns the D6503 Z2. so I will likely come back and edit to see if the problem is reproduced on that hardware.
The only things that have been done to it recently (last night) is a sizable (5 gigs or so) photo transfer off my phone to my desktop to free up some space and I downloaded an app called timely. Uninstalled timely to see if maybe that was the issue but no dice. Also updated a ton of my existing apps last night (amazon, battery widget reborn, cat alone, es file, google keep,hulu, light flow, netflix, swype, twitter, snapchat, uber, videostream, and youtube) Not sure if that is relevant but can't hurt to include as much info as possible.
What the heck is going on here?
Info
mcw3118 said:
Okay so this is the most bizarre problem I have ever had with my phone. I am running stock 4.4.2 on a D6503 Z2 on AT&T's network. Rooted and running xposed.
Ear buds in questions are skull candy inked 2 (yeah I know they're a crap brand)
So on to the actual problem at hand:
This morning my ear buds just randomly stopped working when plugged in; outputting the sound through the external speakers instead. Found a temporary work around by switching the text to speech output from Google to Pico TTS. Ear buds worked again and the phone was recognizing that ear buds were plugged in, but sound switched to external speakers when the phone went to sleep or got a notification. A soft reboot seemed to fix this if I also changed the TTS output. That worked for about two hours and then TTS trick ceased working for me.
Once I got home, I tested other headphones and there is no issue with any of the three pairs I tried. Here is where it gets weird though, the skullcandy ear buds work just fine on everything else! I tried it on my Z1 tablet and my old HTC one x. Working fine. I am waiting for my boyfriend to come home to test on his phone because he also owns the D6503 Z2. so I will likely come back and edit to see if the problem is reproduced on that hardware.
The only things that have been done to it recently (last night) is a sizable (5 gigs or so) photo transfer off my phone to my desktop to free up some space and I downloaded an app called timely. Uninstalled timely to see if maybe that was the issue but no dice. Also updated a ton of my existing apps last night (amazon, battery widget reborn, cat alone, es file, google keep,hulu, light flow, netflix, swype, twitter, snapchat, uber, videostream, and youtube) Not sure if that is relevant but can't hurt to include as much info as possible.
What the heck is going on here?
Click to expand...
Click to collapse
to understand correctly what is issue u should first remove all 3rd party tools and customization
and then test ur device
when ur phone don't work with other device it means there 2 way communication that should be compatible on both sides.
what is ur headset?
:good:
Geeks Empire said:
to understand correctly what is issue u should first remove all 3rd party tools and customization
and then test ur device
when ur phone don't work with other device it means there 2 way communication that should be compatible on both sides.
what is ur headset?
:good:
Click to expand...
Click to collapse
skull candy inked 2.
The same problem is replicated on my boyfriends z2 that is running stock + xposed so i'm thinking its something with xposed. I'm not concerned enough to uninstall all of that one by one to see whats doing it i'll probably just get new headphones.
I am having an issue with my Nexus 5 and I can't make out what the fault is (before you shout that I am in the wrong place, please read to the end. My conclusion is not phone based. Nor is my question)
My mic does not work when I make or receive a call normally so the person I am talking to cannot hear me. If I switch to speakerphone the mic work well and I can be heard on the otherside.
I have done pretty much everything - root, unroot, flash stock, change build.prop, go from ART to Dalvik, go back to kitkat from lollipop and back again etc. etc.
I have googled extensively and it could be one of these:
1. Noise cancellation microphone
2. Earphone jack that doesn't recognise when the earphones are removed
3. A hardware malfunction.
The thing is that I have tested all of these.
1. Covering the noise cancellation mic or fiddling with the build.prop makes no difference
2. I have tried to turn off the headphones while they were in using an app from the play store. Didn't solve the problem
3. Installed a noise meter app and when I blow /tap straight on the grill were the mic is house, there is recognition. Also tested using Google voice search. Also recognised some words. Finally, if i make a call and put the phone in speaker mode the person on the other side hears me loud and clear. So not the hardware (I don't think).
I google some more and noticed that a number of phones have this issue not just the Nexus 5. For example the
** the OnePlus One (https://forums.oneplus.net/threads/m...m.91832/page-3),
** the Moto G (http://www.androidpure.com/how-to-fi...on-the-moto-g/),
** the HTC One X (http://forum.xda-developers.com/show....php?t=2283990),
** the LG Optimus (http://forum.xda-developers.com/show....php?t=2461432),
** the Xperia Z (http://talk.sonymobile.com/t5/Xperi...hone-not-working-well-during-call/td-p/596943),
** LG G2 (http://forum.xda-developers.com/showthread.php?t=2628310 ),
** Nexus 5 (http://forums.androidcentral.com/google-nexus-5/332164-nexus-5-microphone-issue.html ),
** Nexus 4 (https://code.google.com/p/android/issues/detail?id=43416 ),
And probably many more...
So, could this be a broader problem with Android software itself? A universal bug? A virus? I have too many questions.
Hopefully somebody brilliant from this forum will see this and apply their genius minds. And fix what has hitherto been unfixable. Now there is a challenge - fix the unfixable.
No takers for this problem?
I'd like to know the answer to this as well.
I'm trying to reinstall Lollipop from Google images to see if that fixes it, but I did the same things you did and found the same things.
I think it's software, too.
And now Moto X 2013 also have this!
May be its new feature from Google?
I ended up with what I thought was a broken earpiece speaker: During calls, I could not hear anything through my earpiece, but putting the call to speakerphone worked.
Also, all media palyback was mute (youtube, VLC, audiobook player ...). Headphones continued to work. I played around with all the audio settings, nothing.
So I assumed a broken earpiece and ordered a new one. I took my MI5 apart and replaced the earpiece, but nothing changed: Earpiece stayed silent, headphones and speaker worked.
By that, I already factory reseted and flashed new LOS builds and firmwares back and forth. No change.
Yesterday I came up with the idea to write an app that routes all audio to my surround speaker ... I researched the Playstore to check if anything like that already existed, and I came up with an app called SoundAbout which I used to route all audio to the speaker instead of the earpiece.
So far so good.
But even better: I configured it to route all media sounds from "let app decide" to "earpiece", and to my surprise it worked!
Setting it back to "let app decide", I dont hear anything: The setting "earpiece" makes it working again.
My question is: The issue is clearly software related, somehow I managed to break my audio routing, which survives flashing new builds and even factory resets as far as I can tell.
I am on official LOS 20170425, 7.4.14 firmware, official su addon. No custom kernel, no magisk or any battery saving trickery ...
Does anyone have an idea what I can check to fix my audio routing again? Anyone experienced something similar? I will buy that SoundAbout app because it just saved me from buying a new MI5/MI5s/MI6, but I would still like to understand how I managed to break my audio routing like this. The fact that it survivd factory resets makes me think it might be firmware related (I am using the ones from here: https://forum.xda-developers.com/mi-5/development/tool-flashable-firmware-twrp-easy-t3474898) ...
Ok, after several months, I finally figured it out.
It was not a firmware issue after all, but hardware: My 3.5mm audio headphone jack was blocked, meaning the trigger for detecting a headphone was jammed.
The phone constantly thought a headphone was inserted, and so switched to headphone mode, trying to play all sounds and media to the headphone audio port where nothing was present.
Thats the reason why e.g. SoundAbout was a working workaround: It simply ignores the headphone-inserted-trigger and forces all audio to speaker or earpiece.
I found out about the b,ocked trigger with another tool that simply shows if a headphone was inserted or not, and that tool constantly showed that something was inserted.
Unfortunately you cannot get a replacement headphone-jack for the MI5 (redmi and mi4s are available, but no mi5 for some reason), only the whole mainboard for 140$. But I took my MI5 apart anywayto see if I can get that trigger unstuck (tried a small needle and qtip before, but didnt work). I could not get it unstuck, and instead removed the whole headphone jack from my MI5 mainboard, meaning I actually broke a small piece of my mainboard out ... but it worked nontheless: Now that the audio port is gone, my phone no longer thinks a headphone is present, and all audio issues are gone.
Now that I removed the audio port I obvously can no longer use my headphones, so I ordered an usb-type-c-to-audio-adapter for 5$ (after checking that xiaomi usb-type-c headphones cost 50$, which I consider waaaayy too expensive).
So, if anyone has a similar problem where it looks like your phone doesnt play any audio, check out "headset toggle" from the play store to see if the headphone-trigger is broken.
Prior to OTA updating my S9+ from O to P, sound output was beautiful from the time I purchased the phone last year. Specifically, sub-bass was some of the best I'd ever heard. Unfortunately, after updating (about 3 weeks ago), looks like sub-bass is non-functional. I've noticed this on ALL bluetooth devices I've played it on (my car, 3-4 different current model headsets/earpods etc which all support BT 1.4).
I've tried the following, with no luck:
1) 10 band EQs. Mid bass and upper bass changes DO reflect in the output, but changing the sub-bass slider has zero effect
2) Tried sub-bass apps that previously did a masterful job on Oreo, but literally zero effect. I could hear mid and upper bass being amplified, but the sound result is muffled garbage thanks to no sub-bass change.
3) Force stopped and disallowed system permissions for Samsung's Soundalive service, and then played with EQs and sub-bass booster apps again. No change.
4) Tried the above with all available bluetooth codecs in developer options (i.e. aptx etc). Same output quality
I haven't yet tried with a wired headset (mainly because I don't have one anymore ) , but I plan to as soon as I can find the Samsung ones that came with the phone.
There's been zero physical damage to the phone from the time I purchased it, just fyi, and as mentioned, the output difference was clear from the moment I updated to Pie. I also did a full factory reset a couple of days ago just in case any old apps were causing interference with DSP, and unfortunately the same result.
Has anyone else experienced the same after updating to Pie from Oreo (Verizon or not)?
I have the same problem.
Did you have found the solution?
I flashed back to 8.0 and notice the sound quality is better.
Hey everyone
A couple of days ago EMUI prompted that a new update with some system settings changed arrived and required a reboot. After that, mysterious things started to happen...
For whatever reason, SOME sound apps (audible, google podcasts) are now having a terrible sound through bluetooth - it has a metallic echo which resembles an empty room effect. While OTHER apps (probably that play music, such as yandex music) do not experience that. I've tried my car audio and Bose QC35 with the exact same result =( I'm baffled as to what is going on and how to fix it. I've tried switchin between codecs in realtime but that didn't change anything.
I would appreciate any ideas, really don't want to do hard reset....
Build number: 9.1.0.326(C10E3R1P13patch01)
Nic quality
Nic quality bluetooth sound speaker
Just to update here: my issue has been resolved with 9.1.0.350