I finally decided to root/s-off/ROM last week, and after following the many excellent guides around I got to a place where I liked the features and speed of the ROM I settled on (Incredible 2 HD 4.something).
Here's a breakdown of what I passed through to downgrade/s-off/root/recovery/ROM:
Friday
Downgraded from 2.3.4/Hboot0.98. Successful.
Installed CWR, su, busybox. All well.
Boot once into stock VZW GB 2.3.3.
Grab full nandroid backup of "stock" 2.3.3 as a failsafe.
Back to CWR 5.0.2.0. Installed CM7 / gapps. All still well. I wanted Sense back, so hunted for a good candidate ROM.
Settled on Incredible 2 HD from themikmik.com
Initial flash acted like I wasn't rooted (CWR .zip install said (bad) when I selected the ZIP. md5sum is perfect, so it's not a bad copy. Battery pull later and a few full wipes, install is fine.
Saturday
Inc2HD ROM is really sluggish so I decide to nuke it from orbit and start over again.
I grab the Super Wipe script and run.
Reinstall DInc2HD ROM.
Rom is very responsive, acting much better.
Start reinstalling all my apps again.
Deal with the stupid problem of sms messages from VZW (http://www.droid-life.com/2011/06/2...age-from-vzwnmn-here-is-how-to-stop-them/]fix detailed here[/URL]).
Receive and place several calls as normal throughout the day.
Gradually reinstall apps only as I need them. Keeps down the clutter
Sunday
Receive and place several calls as normal throughout the day.
Gradually reinstall more apps only as I need them.
Getting to a good state with apps re-authed and reinstalled. Decide to grab another nandroid checkpoint backup.
Backup is fine, resume normal daily use.
Monday (today)
[*]Alarm goes off as intended (yay - I have 'Clock' back after being missing on my phone since 2.3.3!)
[*]Listen to some spotify paired to my car on the drive into work
[*]Colleague calls me .. and I can't hear him. I figure it's a bad connection so I call him back. Still can't hear him through the earpiece. As a quick test I switch to speakerphone, I can now hear him.
I figured this was a one-time thing, but start test calls to DInc2 from my desk.
Damn - earpiece isn't passing any audio. Speakerphone toggle gets me audio, as does plugging in my 3.5mm earphones.
I then test other apps I know I can toggle to playback through earpiece, and no dice (Google Voice, etc). All I can hear is a very very faint buzz while a call or playback should be coming from the earpiece. When I hang up, the faint buzz in the earpiece goes dead again.
Made sure bluetooth radio was off to rule out pairing to other devices (though I haven't re-paired since wiping anyway). No wifi radio on either. All alone with the mobile network radio.
Now I know I've done a lot to the phone over the weekend, but I can't find any common cause of what might have happened between the last good call I placed on Sunday evening and today (Monday). Phone sat all night charging on my nightstand. No physical damage or anything like that.
Thinking this may be a ROM or app issue, I bounce back to my known-good snapshot of the 2.3.3 stock ROM. Problem persists - crap.
To further rule out, I full wipe and install CM7.1.0.1 from scratch just to get another baseline. Still no earpiece audio - getting frustrated!
Whatever it is, it isn't exhibiting signs of being a ROM or app issue because it persists full wipes (wipe/cache clear/dalvik wipe, and another pass even with the super-wipe script).
Yes, I've checked basics like making sure In-Call Volume is not muted. I've also installed Audio Manager to make sure there's not some lurking audio volume problem. All sliders maxed before, during and after test calls.
Uninstalled any audio-related app to attempt to remove any hold on audio output. But recall here - it's following across ROMs and wipes, so this is just busy work.
Logic says then that either
I hit some rare bug?
The process of mucking around with recoveries, ROMs, and other lower-level items has flipped a bit somewhere that will persist full user-space wipes/partitions/formats.
it's faulty hardware (which I have a hard time believing, but stranger things have happened!) This would just have to be horrible timing.
Searches on here and other sites don't bring up too much for the Incredible 2 and this kind of earpiece issue. There's a passing mention of a "silent audio bug" here, but doesn't seem relevant (nor much detail given).
I've grabbed output 'c:\> adb logcat -v time -b radio > alogcat.radio.txt' while making a call and switching between earpiece (default) and speakerphone. No really good clues there. Changes in logging verbosity didn't show too much of interest. I'll pastebin it after I scrub my phone number out if anyone's interested.
So after the wall of text ... anyone have any ideas?
I'm in it to win it with this, so I'm not unrooting and warrantying this pig I'm due for a new phone but there's nothing I want other than to just have my DInc2 back working.
I'm off to keep searching. Wondering if there are other debug-level tools/switches via adb that'd let me poke at devices, but I'm guessing those interfaces may not be as readily exposed as I'd like.
Thanks in advance all.
tl;dr - Incredible 2 earpiece randomly stopped working, but speakerphone and headphones still output phone call audio fine. Follows across wipes/ROM installs. LOLWTFBBQ?
I hate to say it, but your earpiece is probably broken... U may have smashed it with your keys in your pocket (did that on og dinc)...
Sent from my Incredible 2 using xda premium
If speakerphone and headphones work, but you cannot get sound at all from the earpiece then that would lead to me to be hardware issue... Electronics break man.. unfortunately.. and when you try to think that there is nooo way possible that you could've broken it, that's usually when you do.
Sent from my Incredible 2 using xda premium
faehsemc said:
If speakerphone and headphones work, but you cannot get sound at all from the earpiece then that would lead to me to be hardware issue... Electronics break man.. unfortunately.. and when you try to think that there is nooo way possible that you could've broken it, that's usually when you do.
Click to expand...
Click to collapse
Fair enough. I hadn't ruled out full-on hardware failure I just found it to be the least-likely of the candidates.
I had to replace the speaker in my original Incredible, so I figure it can't be too much tougher to do in this one. I'm going to exhaust some other troubleshooting first (my wife has a functional stock DInc2 that I want to compare some logcat output from, see if anything stands out when making a standard voice call).
I'm always careful to change ONE thing at a time then test to make sure my variables are where I expect them to be, so this one threw me. I'll post back with results, and hopefully get my earpiece back .
OK, I ordered a replacement earpiece and replaced it. This did not fix the audio. I tested both the original earpiece and the new earpiece before installation by using a low speaker-level source and confirmed that BOTH actually work fine and produce sound as expected.
While the phone was disassembled, I made sure all contact points were good for the earpiece. This isn't a physical problem.
So, this takes me back into the software/firmware/radio arena.
And more specifically, in order to persist all wipes and reinstalls, this has to be something below.
I'm going to use adb to flash a radio (I think there's one newer than the one I have installed, something.622? Not down at bootloader to check right now).
If this doesn't do it, anyone want to buy a DInc2 for parts and dev?
The newest radio is .1111 before that .722
Sent from my Incredible 2 using xda premium
Good call on the 1.09.01.1111 firmware. I found and flashed that instead of .722.
No effect unfortunately.
So next I'm thinking that perhaps whatever kernel I brought with me from the first ROM flash could have jacked something up in terms of audio modules or packages. It's a long shot, but I'm going to grab something like nc2_2.6.35.14#21-2.3.4.zip (non-AOSP) and flash that.
Now that I have ruled out actual hardware failure, I'm just too stubborn to give up on this .. open to productive ideas on things to check, methods to troubleshoot or rule out, etc. TIA.
What about Tue hardware connection from the speaker to phone itself? I don't know much of the board on the phone so I can't give you ideas of where to test, but if you can see where the leads go I would say follow it
Sent from my Incredible 2 using xda premium
Right. I disassembled the phone again late last night and traced back to the extent I could follow. I didn't find anything glaringly obvious or bad.
Also of note, if I'm in a super-quiet room and keep the earpiece near me with no call in progress, I hear literally nothing. As soon as a call is initiated, I hear a very faint "sputtering" sound from the earpiece (original or new earpiece), which means the symptom here clearly impacts either speaker.
So something upstream from it ... whatever pathway sends audio to this device isn't getting instantiated properly? That'd make me look to the kernel or driver to understand what pathway does work when routing audio output to the rear speaker that doesn't properly route it to the earpiece for the same call.
Recapping for my own sanity:
- Physical causes == none seen, mostly ruled out via disassembly and inspection, earpiece replacement with known-good part and known-good reassembly.
- Radio == upgrade to .722, .1111 and back to .622, no change.
- ROM == not likely culprit (problem persists any ROM replacement)
Can't fight off the nagging feeling that the act of starting down the road to S-Off + su + rooting did something here.
Given that there are guides to un-rooting (don't think you can un-S-off per se though, right) I may give that a shot since this phone is essentially a guinea pig now. Going to see how far down this rabbit hole I can go.
While I'm stewing on that does anyone have links to android filesystem reference material? I'm thinking the high-level relation between things like bootloader, recovery partition, user-space filesystem and on which levels I can address these with tools like adb. I want to try to understand if some bit could have been flipped at a layer lower than what flashing a ROM or kernel can recover, but perhaps higher than a baseband radio flash. Knowing where all these live and how they interrelate sounds interesting to me. Then I can form a better working theory on what could cause the stupid problem I'm having and if it's plausible to be in software/firmware somewhere.
There is an unrooting guide on YouTube. I find it hard to believe its software, but I work on a radar weapon system that has proven me wrong many times... But if you have flashed multiple roms then the kernel would've been reflashed atleast once and if you are doing a full boot and system wipe, whatever drivers previously installed would have been overwritten... I'm leading to believe there is a shorted componant on your board and because the voltage is so low on these, there moght not be any visual evidence. Unless u have schematics of what voltage is applied where, there isn't a way to test most of them. Especially if the gates are set to be low when applied, vice highs. I would s-on factory reset and of that doesn't work, its hardware
Sent from my Incredible 2 using xda premium
Agreed. I work with enterprise hardware/storage/cluster systems, so I'm driven by nature to root cause this silly thing - but yeah, occam's razor seems to say here that it's just a really stupid coincidence that some random component failed just at the time I began making other changes. And I can't let it go
This is even more frustrating to me because I always make a point to introduce only one change at a time then test the outcome!
After poking through the SDK/reference guide about AudioManager, I was reminded that GV has access to the earpiece audio path. While I could just make test calls in/out, this saves me from burning minutes in the process.
As a quick-and-dirty workaround (for anyone who may stumble on this in the future), you can use Google Voice to act as an internal earpiece playback test tool.
Install and then go to settings and tell it to play back via the earpiece by default and not the speaker. Then (assuming you have voicemails to play), attempt playback. You can toggle between the two audio outs in a much quicker way than I've seen in any other app. Works close enough for me to serve as a test tool as I make discrete changes as I go through troubleshooting.
Maybe there are other media playback apps that'd offer a toggle to the earpiece for playback (but why?), though I didn't look. Seems like the AudioManager reference guide implied that the earpiece was a more "protected" audio path than the speaker (but that's likely just for actual carrier network voice calls).
Cheers,
I'm really getting a kick troubleshooting.. I've been recruiting for a year and a half now.. miss working on gear.. one and a half years left and back to my ship... Can't wait
Sent from my Incredible 2 using xda premium
I actually doubt it's your ROMs --- I'm running latest unmodified vz gingerbread and all of a sudden about 5 days ago I could no longer get earpiece to function - my only guess is something shorted out because of an off-market USB charger that I got 3 of for 7 dollars off Amazon...
Anyways, I had the same sorta flutter that you seem to hear when on a call and there should be sound... and otherwise silence when silence is expected... anyways I replaced it with a brand new earpiece and EXACT same issue is happening still.
Not sure whats up but this may be the world telling me to use my Bluetooth headset more anyways... I'll post if I find anything that fixes it, but I ain't gonna hold my breath given how few ppl seem to be experiencing this issue.
Good luck
Related
Even after uninstalling it with titanium backup,root explorer and native android in menu it keeps popping up in notification bar with these ill-effects:
It closes out any apps or programs I was using!
It automatically puts me on speaker when I make or receive calls
Screen orientation cannot be disabled
Screen lock cannot be disabled
Volume is lowered when playing music
stays at the same volume and cannot be adjusted.
Some suggestions were to disable automatic startup and bluetooth in Car Home's menus when it pops up, I did not see such option. Now the menu does not pop up anymore, only the steering wheel icon pops up in notification bar to let me know its here to make my day a living hell again. Everyday, Every Hour, Every minute. I've done full wipe,cache,dalvik, and reinstall of cm6 6.1.2 and it just wont GO AWAY! Please HELP!
I have the same thing. silly thing keeps poping up. trying somethings if i get it to stop ill let you know. let me know if you get it to stop
Go into a roms zip file, find carhome apk, delete it and wipe and flash. I'm not sure if this will work since I don't know if you have to change the code too
A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo.
Or use Root Explorer and go to /system/app and delete it there. I never used it anyway.
I had that same problem on that rom
I found 2 carhome apk's in my system apps. I deleted both but then had fc's.
So I'm curious off you find a solution
Swyped from a galaxy far far away......
thanks i tried that did not work. just done got a older nan backup and put it ok it seems ok for now.
thanks m8
car home is a virus
i tried. i lookd into the roms, cm7 rc1 n rc2 n none of them have it. i figured if i delete the car home apk off gapps.hdpi.zip file it would work.. since thats the only other place its located in. nothing. it still pops up. i being dealing with thins for the last week. i did everythin. clean factory wipe, went from cm7 to cm6 in all the versions available. n nothing. car home still pops up.
other known issues that i think might be connected;
calls are answered with speaker on.
when usb is connected, the notification does not give you the option to mount sd (only in cm7 rc1 n rc2)
robenever said:
i tried. i lookd into the roms, cm7 rc1 n rc2 n none of them have it. i figured if i delete the car home apk off gapps.hdpi.zip file it would work.. since thats the only other place its located in. nothing. it still pops up. i being dealing with thins for the last week. i did everythin. clean factory wipe, went from cm7 to cm6 in all the versions available. n nothing. car home still pops up.
other known issues that i think might be connected;
calls are answered with speaker on.
when usb is connected, the notification does not give you the option to mount sd (only in cm7 rc1 n rc2)
Click to expand...
Click to collapse
gapps.hdpi.zip? WTF? Quit running your own GApps. Wipe everything, get RC2, flash 20110307 GApps and go from there. Solves all problems.
Not sure if this will help you much but I had this same problem once and ended up unrooting my phone and even then it did it so I went into a sprint store and they replaced it free of charge.
crakerjaks said:
Even after uninstalling it with titanium backup,root explorer and native android in menu it keeps popping up in notification bar with these ill-effects:
It closes out any apps or programs I was using!
It automatically puts me on speaker when I make or receive calls
Screen orientation cannot be disabled
Screen lock cannot be disabled
Volume is lowered when playing music
stays at the same volume and cannot be adjusted.
Some suggestions were to disable automatic startup and bluetooth in Car Home's menus when it pops up, I did not see such option. Now the menu does not pop up anymore, only the steering wheel icon pops up in notification bar to let me know its here to make my day a living hell again. Everyday, Every Hour, Every minute. I've done full wipe,cache,dalvik, and reinstall of cm6 6.1.2 and it just wont GO AWAY! Please HELP!
Click to expand...
Click to collapse
i flashed to Sense then updated PRL, then Profile. Then i flashed back to CM6 its bn working eversince
i rather make my own gapps n take my chances than just sit here n do nothing. however, i am working unrooting my phone and rerooting it again. if that doesnt work.. then its back to the sprint store
I did a full wipe and reflashed CM7 RC2 along with the gapps that came with it, and so far no problems *knocks on wood*.
I had this problem and found that the culprit was pocket lint lodged in the phone's usb port--grounding out one or more pins.
I read a post about a guy who made his own car dock cable by grounding pin4, auto-triggering car home, like the real evo car dock, whenever he connected his cable.
I got thinking and grabbed out my jewlers loupe and saw some crud at the base of the usb jack. With the battery removed I got a slender sewing needle and bent the tip slightly with a plires to make an "r" shaped hook.
I gently scraped around the bottom and edges of the usb jack on the phone with the needle and pulled out a years worth of greazy lint crud that literally wedged against the pins, no doubt grounding out one or more of them, thus kicking up the car dock shenanigans. Seriously, a lot of lint.
Once the dock issue showed up, prior to cleaning the jack, the car home app showed up EVery time i plugged in usb.
I havent seen car home nonsense at all since cleaning out the jack.
prior to cleaning i called sprint having read about others doing the same. Without much hassle they sent me a warranty refurb (with 2.3.3 installed) to replace mine,
With a clean jack, i can send them back the refurb and keep mine as is.
hope this helps
So cleaning the USB jack solved the Car Dock app nonsense, that app is no longer popping up. However at present the phone is still defaulting to Speaker Phone ON for outgoing and incoming calls.. Will try reflashing etc later on to see if it has an effect
slackard said:
So cleaning the USB jack solved the Car Dock app nonsense, that app is no longer popping up. However at present the phone is still defaulting to Speaker Phone ON for outgoing and incoming calls.. Will try reflashing etc later on to see if it has an effect
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1107759
A story of how I fixed this problem over a month ago. Refer to post 5.
It's actually a hardware issue. There is a circuit on the EVO board that is fried. Of course sprint won't acknowledge this but have seen it happen on other phones.
Sent from my PC36100 using XDA App
tnerb123 said:
It's actually a hardware issue. There is a circuit on the EVO board that is fried. Of course sprint won't acknowledge this but have seen it happen on other phones.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My circuit board fried, then fixed itself?
I would be interested in where you got this information from.
Sprint does acknowledge this. I have the same issue and thought i solved it by cleaning the USB jack--not so.
I was just in the sprint store the other day with my faulty phone and after some digging the tech found a bug report titiled something like "speaker phone always on" in their bug database. Recommendations in that bug report were to clean usb leads and if that doesnt solve, replace the phone.
Sprint offered to replace mine without too much hassle and shipped a refurb overnight, but the new phone came with gingnerbread and is therefore unrootable (at the time of this post), so i started looking for another solution--to disalbe the dock features entirely.
I came across the app NoDock, which loads a kernel module that interupts communication between the dock sensor and the OS, preventing the dock & speakerphone shenanigans.
I dug around in adb shell a bit and found the kernel module being loaded by the NoDock app.
Its located in /data/data/com.nothize.free.nodock/files/ and titled "nodockm_2_6_37_4_cyanogenmod_01388_g0374804.ko"
I was able to load this module by hand as SU in adb shell with the following:
#su
#insmod /data/data/com.nothize.free.nodock/files/nodockm_2_6_37_4_cyanogenmod_01388_g0374804.ko
I will work on moving this module out of the NoDock app directory and see if i can get it to load on-boot without needing the timelimited APK. No offense to the app's author, just not interested in a pay to play 'app' that loads simply loads a kernel module that can be loaded with a simple script etc or by hand.
I already sent the gingerbread phone back to sprint and will stick with this solution for the time being.
Hope this helps anyone with similar problems.
Well you're not offending me, you're just thinking in a different way than I'm and (if) you haven't leave any destructive comments about it.
What the app worth is really the kernel module.......the app interface however, provides settings that may serve other use cases.
I wrote the kernel module myself, but not ripped off from anything else, so you cannot say that you are not willing to pay for just the "app" that loads the kernel module. In fact, you're paying the novel ideas and the novel kernel module too that took most of the time for the research to make it works for various phones including S2. You can read more if you have visited my website. So if you got the knowledge and skills, as I've already documented how I am doing this, you should be able to write your own kernel module.
The free trial app was a free app a long time ago......until I felt offending by some "free version users". They emailed me for support, they left silly comments, complains and complains out of a reason. I lost my hope to them while the paid users have so much better quality.
And you're lucky to extract the old free trial version....IIRC, the expire has been introduced to the kernel module too since some version.
slackard said:
No offense to the app's author, just not interested in a pay to play 'app' that loads simply loads a kernel module that can be loaded with a simple script etc or by hand.
Click to expand...
Click to collapse
I had the same issue. Turned out that my issue wasn't a piece of pocket lint in the USB jack (which DOES cause the same issue)....instead it was a bent pin in my charger. I bought a new charger for $3 on Ebay and I have never had the issue since then. Common sense tells you that if you've gone through all avenues of software issues and the problem is still recurring then you need to start looking at physical aspects of the phone. In this case, the device that triggers car home automatically......aka the USB port and anything connected to it.
Having severely scratchy, distorted music audio that usually starts after a few hours of regular use of stock music player, Doubletwist and Pandora. Also happens when automatically going back to music after answering an incoming call through my BT mono. Really strange. And when it kicks in, even my notification tones begin to sound scratchy (but oddly my ringtone sounds fine). A reboot fully corrects the issue... for a while, at least... but that's a pain and drops my battery between ~2% - 8% each time.
I clean my cache automatically daily. Thought it was a rouge app and monitored for a while through SP, but still coming up empty. And of course, I've changed up my ringtones with the thought that my regular one was blowing my speakers (I'm a child of the 80's and lost my hearing to death metal concerts in my youth, so I have to have my ringer just a notch above blaring )
Tried Timat's (same issue), now back on Sav's kernal. Tried full wipe & Calks format, flashed back to Sense, a fresh download of the ROM I'm using, did all this twice. Tried to disable stagefright in the build.prop using GScript so I could re-able when necessary (didn't work either).
Has anyone come across this? Many thanks.
jedijackie said:
Having severely scratchy, distorted music audio that usually starts after a few hours of regular use of stock music player, Doubletwist and Pandora. Also happens when automatically going back to music after answering an incoming call through my BT mono. Really strange. And when it kicks in, even my notification tones begin to sound scratchy (but oddly my ringtone sounds fine). A reboot fully corrects the issue... for a while, at least... but that's a pain and drops my battery between ~2% - 8% each time.
I clean my cache automatically daily. Thought it was a rouge app and monitored for a while through SP, but still coming up empty. And of course, I've changed up my ringtones with the thought that my regular one was blowing my speakers (I'm a child of the 80's and lost my hearing to death metal concerts in my youth, so I have to have my ringer just a notch above blaring )
Tried Timat's (same issue), now back on Sav's kernal. Tried full wipe & Calks format, flashed back to Sense, a fresh download of the ROM I'm using, did all this twice. Tried to disable stagefright in the build.prop using GScript so I could re-able when necessary (didn't work either).
Has anyone come across this? Many thanks.
Click to expand...
Click to collapse
Well, you've tried everything I would've suggested...tried different kernels, flashed backed to sense, performed a full wipe, etc. I would think that flashing back to stock would've alleviated the issue if it was software related. Perhaps your speaker is starting to fail? I've seen many people reporting needing to replace the speaker. However, it is indeed odd that its intermittent, you'd think that if the speaker was failing, it'd be consistent, and a reboot wouldn't clear it up. Odd, but I don't know what else to suggest. Have you tried tweaking the settings using DSP manager at all? If all fails, and being on stock sense doesn't fix it, I'd unroot and have it looked at by Sprint probably.
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
jedijackie said:
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
Click to expand...
Click to collapse
You definitely seemed to try just about everything but did you flash a Stock RUU? I'd nandroid backup and flash it to see if the problem still exists, if you've tried that then you would only have one option left, take it to BB. Best of luck either way.
Huh... haven't tried a Stock RUU. Good call! I'll try now and report back. Thanks Blake.
jedijackie said:
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
Click to expand...
Click to collapse
You're welcome, sorry there isn't more I can suggest. As Blake said, run RUU to unroot, which I would do before you take it in anyways. (What I meant when I said "unroot and take it in). If its still out of wack then, take it in.
Sent from my PC36100 using XDA App
I attached the Stock rooted RUU but visiting HERE should return you to unrooted stock evo.
OK so this has been an issue for several months now and its gotten worse.
The ear speaker has been working intermittently and will usually not come on at all.
This seems specific to CM7 because flashing back to CM6 it works fine.
Problem is: Speaker works randomly, at first i thought it was hardware issue but every time a loud sound or voice was played through it would come on.
I would use a saved voicemail and play it a couple times and that would usually kick the speaker to work. But as of recently its doesnt come on at all, only when it wants to.
I have no idea if this would help, but using OSMonitor's log, whenever i tried to play a sound through the ear speaker it would always log audio_disable().
Sometimes reboot works, mostly it doesn't. Ive done clean wipes, fresh installs, and reverting back to previous nightlies and stables. it only has gotten worse with newer updates.
I've looked everywhere for an answer. I dont mind uploading a log, just dont no what to exactly copy for the speaker.
it happpened to me too.
Called tmobile.. pretended to run the test they told me to run.. they then agreen that it was broken internally, and sent me a replacement.
Then I un-rooted my phone, sent it to them, and life is good now
lol
do it..
any other ideas on whats causing this??any solutions besides the return?? ha
I dont know if this is a coincidence or not.. but my speaker died as soon as I flashed the Salsa Slide ROM.
I have had no issues previously.... and I am not trying to pin the blame, it just seems coincidental.
I do have a slide that I bought right at launch, so I dont know if that has anything to do with it...
Either way, I will be calling today to get it replaced because when I flashed back to NB-mod I still could not hear from the internal speaker.
So I am hoping someone with some real hardware/software knowledge can provide some input...
I recently received my warranty replacement unit because of unresponsive touch and phantom touches. My new unit seems to work perfectly, except now every 10 to 20 touches, the touch will register, but the touch sound "click" doesn't play (if I put my ear close to the speaker, I can hear the speaker activating though). Repeated touches (like repeatedly pressing back) won't reproduce the problem, but more random timing and touches (like in regular use or typing) will. I'm wondering if anyone thinks this is a hardware issue, or some component of the stock software that wouldn't have been overwritten between the update to JSS15Q, and then to JSS15R (it happens in all three versions).
Think I should go for another replacement? Or do you think I should root and unlock, and see if a full installation of a ROM fixes it. It's definitely a sign that something is wrong and it's annoying, I just can't figure out if it's software or hardware related. I'm definitely not going to just ignore it.
(SIDE STORY: When I called nexus help for my first unit, the guy was so helpful and took my word that I had already tried factory resets, and set me up for an RMA. My call on this unit, the woman told me to reboot and toggle touch sounds, and kind of rudely insisted that I was on 4.3 and that Build Version (e.g. JSS15R) had nothing to do with software!! :what: She then told me she'd send me an email with more troubleshooting steps, which never came. I had figured I'd wait for the email, so that I had her name for my next call. Totally unacceptable.)
You come off as just looking for a reason to complain at this point, there doesn't seem to be any real problem with your device other than you being overly picky
Sent from my HTC One using Tapatalk 4
You're completely right. I was so delighted when I managed to find something wrong with my new tablet...
Seriously? You come off as just a worthless ass of a poster at this point. The problem is there, and can be consistently reproduced. I press home and it clicks, and five seconds later I press home and it doesn't click. Your opinion on whether this is a "real problem" or me being overly "picky" is completely irrelevant. It is most certainly real and not normal, and indicates either some software or driver bug on my device, or a strange hardware malfunction. My previous unit (which had very real problems) did not have this problem.
I hope I speak for others here, when I tell you to **** off unless you have something worthwhile to contribute. Just because you don't think something is important, annoying, significant, etc. doesn't make it any less so for someone else.
Do you have this issue with SwiftKey?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Yeah. It's actually everywhere throughout the OS. System settings, stock launcher, Nova launcher, Swiftkey, AOSP keyboard, etc.
I have the opposite problem as you. When muted, every 20 or 30 taps I will get a 'pop' from the speakers, similar to the sound of plugging a guitar into an amp when it's on. Pretty bloody annoying, but I don't want to risk returning it for receiving a unit with worse problems.
GoneTomorrow said:
I have the opposite problem as you. When muted, every 20 or 30 taps I will get a 'pop' from the speakers, similar to the sound of plugging a guitar into an amp when it's on. Pretty bloody annoying, but I don't want to risk returning it for receiving a unit with worse problems.
Click to expand...
Click to collapse
Exactly my thoughts on going through another RMA. But I do feel that it's reasonable to expect a properly functioning tablet on our parts. What you're experiencing is strange. I can tell you that on my Optimus G, when muted, I can hear a faint speaker "activation". Sounds like maybe yours is a hardware issue. Are you stock, or have you tried flashing other ROMs?
Well, I installed CM10.2 last night, and the problem went away. Maybe you might want to try CM, or even just unlocking and reflashing stock JSS15R. You might get lucky with your popping noises.
FYI: I've seen this on multiple tablets (TF101, GTab, Nooks, 2012N7, 2013N7) with different customed ROMs.
So, I wouldn't blame it specially on the Tab. In fact, I see this issue less often on the 2013N7. It usually happens
after I just freshly loaded a new ROM.
spackmanbr said:
Well, I installed CM10.2 last night, and the problem went away. Maybe you might want to try CM, or even just unlocking and reflashing stock JSS15R. You might get lucky with your popping noises.
Click to expand...
Click to collapse
So a couple of nights ago, I decided to try disabling touch sounds in settings. Since doing that I haven't heard a single pop from the speakers. Looks like it was either the touch sounds 'leaking' or the speakers popping from being activated, which they do even when muted (the mute being software)
I'm quite happy with this fix, since the tablet is muted 99.5% of the time, and I don't care for the touch sounds anyway.
Hi Folk's,
Sorry to drag up an old post, but I've noticed my N7 shows this behaviour on KitKat as well.
It misses the touch sound if you pause for about 5 secs during input. Does it every time and it's very annoying. I've tried a couple of different KK roms and it does the same on all of them.
Just tried going back to CM10.2 (JB 4.3) and it works fine!
Does anyone know the cure for this, apart from going back to JB, please? Would really like to be running KK, but this bug is bugging me!
Thanks for any info.
Cheers
I have bought one nexus 7 2013 32gb recently and im experiente this strange beahvior ...im on lolipop 5.1.1! What i have to do to solucionate?
Petermira said:
I have bought one nexus 7 2013 32gb recently and im experiente this strange beahvior ...im on lolipop 5.1.1! What i have to do to solucionate?
Click to expand...
Click to collapse
@Petermira @Xi2or @spackmanbr
I have this same behavior on a stock 4.4.2 S3.
After 5 seconds, if I click anything UI (keyboard, Soft buttons, shortcuts, toggles) there is no sound. If I quickly click again and keep clicking, the sounds work as normal. It's definitely ROM related but is there a fix???
UPDATE: Issue does not happen with headphones plugged in. STRANGE!!!
UPDATE: Issue does not happen if I keep a song playing in Power Amp or similar.
Affected UI items include:
- keyboard
- shortcuts
- toggles
- capacitive buttons
- dialer pad
- etc.
Well before deciding to root, my phone was freezing when making a call. Sometimes the system would allow a conversation, then all of a sudden I would get a ringing sound followed by frozen software, I read, researched and tried not to bug any of you. I found possible issue with the proximity and light sensor. Also read on a reputable Android website, that Sprint had follied some of the PRLs OTA. So I decided to change the possible hardware flaws and Root. Low and behold it resolved the ringing that followed the freezing, but not the freezing. Was going good with Wicked Sensation 5.0, but could not stand the constant update request. That beloved Rom eventually did the same. So changed to 5 different roms and went from TWRP to Phils recovery since then. I am currently on Static 4.3, all roms worked great until I sent/recieved a call. As soon as I hit talk phone freezes and all audio ceases to function. Sometimes itll tease me after a dalvik wipe, but always after hitting "Talk," everything regarding S3 audio or sound, stops functioning.
Does anybody know about the issue I am describing? I switched the audio components so can this Handset Issue MB related? It is hard for me to rule out software due to the audio coming back after each newly installed rom. Before its demise, Audio sounds great. The audio disappears after a call. Just concerned about going to a Sprint repair center for the wait. If this is software related it highly likely my issues will come back. Not a pro, but well versed in the rooting process. As a ExSprint employee I went through all of Sam's rooted and never been stumped on a "Hardware vs Software" problem like this. If I find out its Knox Im taking a Google Nexus to record me throwin my S3 on the wall and sending it to Samsung....jk lol. (For reals though, the increasing challenges to root for every update pisses me off cause the Samsung always got better hardware then the others, but WTF Sammy?)