Database Info

No sound on touch screen

Have the Thunderbolt set up for making sound when touching screen. The screen will work as it should and then without reason it will get very soft and sometimes completely stop making any sound. Checked all my settings and they are as they should be. I also have the Sensation and the screen is set up the same way and it works properly. Is there something I'm overlooking or is this another bug?? Any help would be welcomed. Running stock Thunderbolt.
Thanks,

restart phone and go from there
Sent from my ADR6400L using XDA App

vinnyjr said:
Have the Thunderbolt set up for making sound when touching screen. The screen will work as it should and then without reason it will get very soft and sometimes completely stop making any sound. Checked all my settings and they are as they should be. I also have the Sensation and the screen is set up the same way and it works properly. Is there something I'm overlooking or is this another bug?? Any help would be welcomed. Running stock Thunderbolt.
Thanks,
Click to expand...
Click to collapse
It's a bug of some kind. I've had it since the day I bought my TBolt(Launch Day). I think the reason its not heard about much is because most users don't use the screen sound option and also because a lot of users here and at AC root and flash custom roms.
I'm still running launch day software because it just works for me for the way i use my device.... this being the only bug that affects me. I rooted and flashed this rom:
http://forum.xda-developers.com/showthread.php?t=1013577
and the issue went away so if it really bothers you I would go that direction. I assume other custom roms fix it as well but I cannot comment as the above is the only rom I flashed before going back stock and un-rooting.

Thanks for your input, checked other sites and found other people with same issue. Going to root this thing anyways and I'm sure the new Rom will fix the issue. Might check out the one you downloaded, looks pretty fast.
Thanks again.

[Q] The Shyest Little Phone

My phone seems to be shy. The volume on notifications and rings is so quiet as to not disturb an ants slumber.
I have cranked the sliders that (supposedly control) this setting within the sound menu all the way to the top. At that level the sound is about 1/4 of what it used to be.
Does anyone have any idea what I may have done? I am using infused 1.5.3 with the default kernel and modem. Perhaps the speaker has gone to pot...but I wonder if there is some software solutions I might try.
Thanks for your consideration.

Hmm... Could be that your speaker decided to randomly go out... Never had that happened before, so I don't know what to say. :/
Sent from the big bad Infuse. :3

You could try flashing to stock and see if the problem persists. If it does, your speaker may have blown or something. Haven't seen anyone else report an issue like this.

gtg465x said:
You could try flashing to stock and see if the problem persists. If it does, your speaker may have blown or something. Haven't seen anyone else report an issue like this.
Click to expand...
Click to collapse
I was on another thread a while ago and i had seen that someone had thos issue after rebooting several times at stock it finaly started to work
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

The problem seems to stem from something in the VooDoo controls. If I chug the analog gain thingy all the way up...it works as expected.
IDK why. I know VooDoo is only supposed to affect headphone usage. Three trials can't be wrong though. (or maybe they can...either way its persistent)

[Q] Loud static in call

I've been reading up on this and I'm to the point where I'm contemplating having Verizon send me a nightmare... I mean refurbished device.
How many people are having loud static in calls (randomly)? I'm not talking about a bad signal or something that's only happened to you once. I'm saying a straight up 90% of your calls your ear drum is about to explode because the static just suddenly pops up and is 5x louder than the conversation you're having with the person on the other line.
If you're experiencing this, have you been able to fix it?
I read/tried
-New radio
-New 4G SIM card
-Min CPU to 200mhz
-and more that I cant even remember off the top of my head
Basically I'm trying to see if people are experiencing this across the board, or if I might get lucky with a refurb from Verizon (as this is my absolute LAST resort, seeing as I've never received a working Verizon refurb).

I too have this problem. No solution yet.

Yeap, known issue with the phone. I recently contacted Vzw about the issue and they told me that Samsung knows about the issue and there currently isn't a fix available.
They offered me a completely different replacement device.

I voted no. I have heard it before, but it's not a common occurance, and I haven't had it at all in the last two or three leaks.

Never once had it
Sent from my SCH-I510 using xda premium

I have it. I'm currently on humble 5.0. Although its not as often as other gb leaks, it does happen. I find it to occur when screen dimms during call or if I pull the phone away from my ear and the screen turns on. The only setup the static noise did not occur is stock froyo.
I think many of us with this issue are waiting for the official update. If the static noise continues then I will contact Verizon for a replacement.
Oh and this charge is a refurbished phone that was exchanged for my crappy fascinate.
Sent from my SCH-I510 using XDA App

I had never thought of the screen turning off being the issue. My Touchpad has an issue with sound when the screen goes off. Hrmm... Maybe something to force the screen to stay on would resolve it.

I've narrowed this problem down.
Using GB Roms prior to EP4 this always happened, even with EE4 Radio. It also happened with EP4 radio but EP1/2/3 Base.
Therefore the problem is isolated to the EP1/2/3 base software.
I then isolated it to the dialer application itself. The fault occurs in Dialertabactivity or phone.apk.
If you pull the phone.apk or dialertabactivity.apk from stock EP4, this will go away for most phones.

Hmm want to see if anyone else has tried this.

Umm if you do this you will not be able to dial and utilize the phone. So yeah it will get rid of static because you won't be able to make a call hahab
cmdrfrog said:
I've narrowed this problem down.
Using GB Roms prior to EP4 this always happened, even with EE4 Radio. It also happened with EP4 radio but EP1/2/3 Base.
Therefore the problem is isolated to the EP1/2/3 base software.
I then isolated it to the dialer application itself. The fault occurs in Dialertabactivity or phone.apk.
If you pull the phone.apk or dialertabactivity.apk from stock EP4, this will go away for most phones.
Click to expand...
Click to collapse
Sent from my SCH-I510 using XDA App

Incorrect. You can push the ep4 versions of the apks using adb and it will work. I've tested.
Sent from my SCH-I510 using Tapatalk

I think there must be a bunch of defective phones out there doing this. I have never once had this happen to me, but I do way more texting than actual talking on the phone.
The business owner where I work is the exact opposite however. He is one of those guys who walks around with his phone constantly glued to his ear (he has 4 Gorilla batteries) & it has never happened to him either.
I asked him about it yesterday & he had no clue what I was even talking about.
~John

What I've noticed isnt so much a blaring of static as the other person im talking to sounding like they are trying to talk through a muffled microphone. Something like they have the microphone on their phone wrapped in a sweater and they are trying to talk through it. I cant understand half of the people I talk to.

I had this problem but the recent leaked OTA update: http://forum.xda-developers.com/showthread.php?t=1364298 fixed it for me. It's the first time anything gingerbread has been on my phone without the issue. A 15min call to my gf after the update produced a clean call with no deafening static/popping/crackling. I was worried for a second though cause she started unwrapping xmas decorations that were wrapped in tissue paper. There's a full odin of the EP4D release here: http://forum.xda-developers.com/showthread.php?t=1365376 should resolve the issue for those not running stock EE4 (though I haven't tested this yet, if you do use it report back if it works).

Also check out this thread for not only a cwm version of the OTA ep4d but also a modem updater file that can patch your modems to EP4D - they just need to be EE4 prior to flashing.

So I used the odin of the debloated/deodexed/rooted ep4d (the one I posted in my original response above, created by danalo) last night, first call I make today I get the static.

Sucks!!
mhemu said:
So I used the odin of the debloated/deodexed/rooted ep4d (the one I posted in my original response above, created by danalo) last night, first call I make today I get the static.
Click to expand...
Click to collapse
Sent from my SCH-I510 using XDA App

I went back to stock, going to see if the over the air works. So far the only resolution is to go back to stock and the manually run the update to ep4d.
Sent from my SCH-I510 using XDA App

mhemu said:
I went back to stock, going to see if the over the air works. So far the only resolution is to go back to stock and the manually run the update to ep4d.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
So, got the static after going to stock and doing the manual update...wtf. Decided to go back to stock and see if the OTA was ready...it was...got static...wtf.
Looks like I will be getting in touch with Verizon and see what my options are, sounds like some other people with the issue have had verizon admit there's an issue and have been compensated. I won't go into the details of what others have done, but I will say I don't plan on giving them more money than I already did for this phone. I'll report back when I have a resolution.

Ya its allot better but definitely still there. I was really hopping this would get fixed and at first it seemed good but after a few calls I got the static. I'm not sure what to do with it now. I've gone back to completely stock and took the update and it's still there.
Sent from my SCH-I510 using xda premium

Reboot issue with JB 4.1.2 vzw newest update on Razr HD

Hey so after a few days of the new update running OK I started having random reboots! I noticed on a few other sites people complaining about the same issue of reboots multiple times of the day! Just wanted to let everyone know a possible solution to the issue! I have went through multiple FDR's and did come to the conclusion that the random reboots for my phone were associated with a new update to the chrome browser and were easily fixed by uninstalling new update and telling it not to automatically update so hope this helps anyone who may be having the same issues!!!
Well so much for that after trying everything its back to rebooting again? I love my phone but seriously considering putting it against a wall!!!

xgshortbus25 said:
Hey so after a few days of the new update running OK I started having random reboots! I noticed on a few other sites people complaining about the same issue of reboots multiple times of the day! Just wanted to let everyone know a possible solution to the issue! I have went through multiple FDR's and did come to the conclusion that the random reboots for my phone were associated with a new update to the chrome browser and were easily fixed by uninstalling new update and telling it not to automatically update so hope this helps anyone who may be having the same issues!!!
Well so much for that after trying everything its back to rebooting again? I love my phone but seriously considering putting it against a wall!!!
Click to expand...
Click to collapse
Never had that issue with the new update. Try doing a factory reset or try the new fast boot files to start fresh. Not sure why chrome would be an issue.try the chrome beta version but I suspect chrome had nothing to do with the reboot just a bad initial update.
Sent from my DROID RAZR HD using Tapatalk 2

Fixed!! I hope!!!
Finally broke down done a fast boot to the new files all is working seems OK anyway know in a day or 2!!!

xgshortbus25 said:
Finally broke down done a fast boot to the new files all is working seems OK anyway know in a day or 2!!!
Click to expand...
Click to collapse
My Wife's phone is doing the Random Reboot thing since the 4.1.2 update as well. I did a Factory Reset on it and it still does the same thing.
I suspect an application is doing it? Because I put the phone in Safe Mode and it never rebooted while in Safe Mode.
But I have No Idea of how to tell which app is doing it, other than to uninstall a random app after every reboot to find out which one it is.
But I would like to try this fast boot option? I know how to get the phone into fastboot, but which files are you redoing? What exactly are your doing ?

Have the same problem. I have done:
SBF 4.1.2
FDR
WIPE
Even tried running a parallel rom with safestrap (bakatang)
The chrome thing did not work
Keeps freezing. Seems the problem is way worse when having the phone play some music.
I am just about unlocking the thing and SBFing back to 4.1.1 but not really interested into unlocking the bootloader. That would be the last choice for me.
If someone knows of some way to fix this, please help, this used to be a great phone...

No problem here with the sfr rom... used for over 1 month now and no problem and my system is always fast...
Sent from my XT925 using xda premium

I've been running some tests for about a week now since I got my RAZR and the results are interesting... I've had lockups and reboots multiple times a day, most often while doing something involving sound i.e. listening to music or playing a game or video. I've tried stock and custom 4.1.2 ROMs and custom 4.2.2 ROMs and it persists so I'm inclined to say its either bad audio software or faulty audio chips. This is everything I've done:
1. turning off sounds (keeping phone on vibrate/silent) pretty much eliminates the random lockups/reboots I got from receiving multiple texts or calls at once. I noticed if I bombarded the phone and made it ring a lot it gave the same results as listening to music but if its just a text or email or call here and there during regular use it the phone works fine.
2. Listening to music, either streamed or local from phone/SD storage and through headphones or speaker, would cause skips and audio cutting out. After a few minutes of this the phone will lock up completely and reboot itself. Strangely enough it happened only rarely or not at all while streaming music via bluetooth to a stereo.
3. I don't think its anything kernel related or if it is its not causing visible errors or wake locks. My battery seems to be just fine through all this.
4. I have tried multiple music/video players, put my SD card with music in another phone and the music plays fine, stock ROMs with nothing disabled/removed still has the issue, custom ROMs debloated and modified also have the issue. I think I've just about covered every base I can as an end user to track down what's causing it but I'm open to suggestions.
I have a replacement scheduled so I will see if that fixes it, I have seen this problem reported quite a few times all over the interwebz but there are also a lot of people not having the issue either so idk. If there are any Devs or anyone skilled in android-fu that can read logcats I will be more than willing to get those for you. Sorry for the essay everyone lol
tl;dr Like others I have freezes and reboots from what seems to me to be an audio software/hardware problem, either built in or from the 4.1.2 update
Sent from my DROID RAZR HD using Tapatalk 2

I am almost sure is kernel related bc I did not have problems in the 4.1.1 sw.
If someone that has an unlocked bootloader could install 4.1.1 from an sbf and tell if the problems are gone, would be great!
here is the sbfs: http://sbf.droid-developers.org/vanquish/list.php
here is the bl unlocker: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
u have to be rooted here: http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit-412/?pid=244281#entry244281
I am not doing that bc I do not use custom roms so dont want to unlock BL. If someone has, this could help much. It is different from using safestrap, because safestrap uses the same kernel, from what I read.

barbaroja said:
I am almost sure is kernel related bc I did not have problems in the 4.1.1 sw.
If someone that has an unlocked bootloader could install 4.1.1 from an sbf and tell if the problems are gone, would be great!
here is the sbfs: http://sbf.droid-developers.org/vanquish/list.php
here is the bl unlocker: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
u have to be rooted here: http://www.droidrzr.com/index.php/t...roid-root-exploit-412/?pid=244281#entry244281
I am not doing that bc I do not use custom roms so dont want to unlock BL. If someone has, this could help much. It is different from using safestrap, because safestrap uses the same kernel, from what I read.
Click to expand...
Click to collapse
I have seen reports that the problem persists even on 4.1.1 but I am unlocked and rooted on stock 4.1.2 so if I get time I can give it a try
Sent from my DROID RAZR HD using Tapatalk 2

anoninja118 said:
I have seen reports that the problem persists even on 4.1.1 but I am unlocked and rooted on stock 4.1.2 so if I get time I can give it a try
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
When I was at 4.1.1 phone was near perfect.
If you are unlocked, please do check. I am debating whether to unlock or not just bc of this. Today it has resetted at least a good 20 times or so.
Thanks for helping!!! Waiting for your results!!!!

barbaroja said:
When I was at 4.1.1 phone was near perfect.
If you are unlocked, please do check. I am debating whether to unlock or not just bc of this. Today it has resetted at least a good 20 times or so.
Thanks for helping!!! Waiting for your results!!!!
Click to expand...
Click to collapse
one solution that has worked for me is silencing the phone or putting it on vibrate and I haven't had a freeze or reboot in almost 2 days... the problem seems to me to be related to audio/sound and not listening to music or watching videos along with silencing ringtones has put a stop to it which kind of confirms my suspicions... I will try and flash back when I can but it'll need a day or 2 of field testing to confirm if its a solution
Sent from my DROID RAZR HD using Tapatalk 2

I can confirm that audio stuff just does worse to the phone. However, I have not had your luck when silencing. Keeps rebooting no matter what. Please let us know when you do.

barbaroja said:
I can confirm that audio stuff just does worse to the phone. However, I have not had your luck when silencing. Keeps rebooting no matter what. Please let us know when you do.
Click to expand...
Click to collapse
looks like a negative on the SBF, tried to restore 4.1.1 and it failed halfway through the flash, now won't turn on... working on reviving it... I really need to replace this thing as its been nothing but a PITA since I got it
old school post from my Thunderbolt via Tapatalk

wow that sucks. I recall reading somewhere that you could actually downgrade your software version if you have an unlocked bootloader.what is the error you are getting? Tried using RAZR utility 1.1? Won't it turn on at all? Maybe a discharged battery? Hope we can solve it

barbaroja said:
wow that sucks. I recall reading somewhere that you could actually downgrade your software version if you have an unlocked bootloader.what is the error you are getting? Tried using RAZR utility 1.1? Won't it turn on at all? Maybe a discharged battery? Hope we can solve it
Click to expand...
Click to collapse
got it revived with Mattlgroff's new 1.2 utility, was able to force it to fastboot mode... the problem seemed to be some kind of partition error, I tried redownloading the sbf files thinking it was a bad file and got the same error so idk what it is since I'm on stock unrooted 4.1.2. My bootloader is already irreversibly unlocked so that won't be a problem lol but I am a n00b to RSD Lite and Moto devices so I'll tinker with it more when I get some free time
edit: I did have a Maxx HD way back at launch for a month or so running stock 4.1.1 and it ran perfectly, so my idea is its kernel/codec/software related. Hopefully a custom ROM (or hell even stock) with Hashcodes Qcom kernel will fix the issue we're having
Sent from my DROID RAZR HD using Tapatalk 2

I talked with vzw service, the assistant said that 2% of the phones were having this issue, wich for this kind of technology is a pretty big number of phones. Suuggested to send it to Motorola but since its rooted its almost sure not to be replaced by them. What is strange is that not everyone is having this issue. I would be almost sure Motorola is going to release a fix for this, but would not count days. Getting kind of frustrated with this phone I used to like so much. Thinking of going the htc route bc this is getting unbearable.

Any news in this? Anyone tried a new ROM that could solve this? Or even a fix?
... or just everyone had another phone lying aroud...

barbaroja said:
Any news in this? Anyone tried a new ROM that could solve this? Or even a fix?
... or just everyone had another phone lying aroud...
Click to expand...
Click to collapse
My wife & I both have this phone and still are constantly being rebooted. This is even after the software update. I have been wiped, factory reset, and everything possible, but I've not called for a replacement yet. Normally I havea worse luck with those.
Wife used to love this phone, now she hates it and hates we changed from AT&T to Verizon since we have no backup Verizon phones. At least we could take the sim out and go to the iPhone that's floating around the house when the phone went to pot before. Makes me really hate suggesting that we go back to Moto phones since that's all that I've used on Verizon.
Wonder if big red will get the new HTC One....

Tried flashing the MR-4 sbf, but did not solve the issue.
Sent from my GT-I9100 using Tapatalk 2

barbaroja said:
Tried flashing the MR-4 sbf, but did not solve the issue.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
If an sbf didn't solve it then it's a hardware problem.you guys are definitely in the minority with this reboot issue.go get a warranty replacement.this phone and moto in general are solid phones.
sent from my xt926 RAZR maxx hd

Audio Lollipop bug

So after a few weeks of using Digital highs GPE Lollipop build I ended up having this issue where my bottom speaker will just stop functioning entirely and I'd have to reboot to fix it, I decided this was a software issue and not a hardware issue so I flashed a new ROM, Liquid smooth. Now my issue is less annoying but still unbearably frustrating, instead of a reboot required, when I listen to music or higher pitched songs it will just give out again but I can fix it by killing my music app and restarting it. I believe this has to do with lollipop and isn't related to my phones speakers being broken but what do you guys think? I'm frustrated as hell about this.

S1L3nTShaDoWz said:
So after a few weeks of using Digital highs GPE Lollipop build I ended up having this issue where my bottom speaker will just stop functioning entirely and I'd have to reboot to fix it, I decided this was a software issue and not a hardware issue so I flashed a new ROM, Liquid smooth. Now my issue is less annoying but still unbearably frustrating, instead of a reboot required, when I listen to music or higher pitched songs it will just give out again but I can fix it by killing my music app and restarting it. I believe this has to do with lollipop and isn't related to my phones speakers being broken but what do you guys think? I'm frustrated as hell about this.
Click to expand...
Click to collapse
just a thought have you tried reverting to a 4.4.4 rom to see if it fixes it? just to be sure it is not a hardware problem, i am curious how you came to the conclusion that it was not a hardware problem. if you think this because restarting the app or phone fixes it you may be mislead, could be the amp or some circuit is cutting out and then resetting have seen this in other types of amps. i could be completely off about this but it is something to consider.
if you were running 4.4.4 before and did not have the issue then that would be my suggestion. and if you find out that it is definitely software then you might want to try re installing the latest firmware again if you have not already tried this.

Azag Thoth said:
just a thought have you tried reverting to a 4.4.4 rom to see if it fixes it? just to be sure it is not a hardware problem, i am curious how you came to the conclusion that it was not a hardware problem. if you think this because restarting the app or phone fixes it you may be mislead, could be the amp or some circuit is cutting out and then resetting have seen this in other types of amps. i could be completely off about this but it is something to consider.
if you were running 4.4.4 before and did not have the issue then that would be my suggestion. and if you find out that it is definitely software then you might want to try re installing the latest firmware again if you have not already tried this.
Click to expand...
Click to collapse
First off thanks for the reply, secondly, I haven't tried converting and it only started happening a month after Lollipop use so perhaps you're right and I was wrong to jump to the conclusion. However I only thought this because using a dif ROM the issue changed from reboot required to fix it to simply restarting the app im using. Leads me to believe it is ROM related. And I'll fix my MultiROM n boot up the old 4.4.2 rom i have n see if it works properly in a bit. Will report back when I'm done.

S1L3nTShaDoWz said:
First off thanks for the reply, secondly, I haven't tried converting and it only started happening a month after Lollipop use so perhaps you're right and I was wrong to jump to the conclusion. However I only thought this because using a dif ROM the issue changed from reboot required to fix it to simply restarting the app im using. Leads me to believe it is ROM related. And I'll fix my MultiROM n boot up the old 4.4.2 rom i have n see if it works properly in a bit. Will report back when I'm done.
Click to expand...
Click to collapse
No problem, I understand how frustrating these things can be and i seen you had no replies thought I might share my thoughts.
You may be correct about it being The Rom, since after the change of rom changed what it took to reset it. Only thing that bothers me is why did it take a month before the problem surfaced, unless you added some other app that is somehow causing the problem.
Have you tried putting phone in safe mode and see if problem persists, if not it a app or something you have installed after that first month.