Random Extreme Lag on VZW GNex - Samsung Galaxy Nexus

So here's what I've discovered.
As of now, on stock 4.1.1, the phone runs smooth when audio is screwed up. The moment touch sounds work again (or the moment I install SoundAbout to fix it) it starts lagging like crazy. Is this a hardware thing? After switching roms, kernels, versions of Android, flashing stock and locking the bootloader nothing has worked.
_________________________________________________________________________________________________________
So I'm having this strange issue that I don't really see mentioned previously (based on my multiple searches)
My phone was running fine until I flashed Paranoid Android (The last Jellybean 4.1 Release). On this ROM i was getting some insane lag, sluggish performance. I'd swipe on the home screen and get a huge delay or the phone would read it as a long touch and bring up the wallpapers option. Opening folders and the app drawer had some serious slow downs. It was a real mess.
I assumed the phone just didn't play well with the ROM so I flashed over to Bugless Beast. The odd thing is that the problems persisted. I would get just as horrible performance and the same sluggish visual effects and stuff. Specifically I remember even the audio slowing down and being choppy (touch sounds) until they automatically disabled themselves and the ROM ran smooth for a bit but returned to the sluggishness again.
So last night I restored to stock flashing the stock image and relocking the bootloader. Rooted, unlocked, flashed recovery again and loaded up Bugless Beast and the issue is still happening. Even got my first random reboot on Bugless Beast today after it slowed down really bad. Now I've noticed that when touch sounds disable themselves so does media audio (while the ringer and notification sounds still work). This is pretty much why I'm convinced it's a software problem and not a hardware one.
Basically I just wanted to know if anyone's experienced something similar and found a way to fix it? Probably going to reflash to stock tonight
EDIT: Well it seems like the audio thing might be a hardware issue. SoundAbout fixed that but I don't see how my audio jack could have been damaged in between flashes.
EDIT 2: Current State:
- I tried flashing just the system img (multiple times) and the lag returned
- I just flashed a 4.2.1 ROM just to see what happened. Touch sounds are back which means my headphone jack fixed itself. Still EXTREMELY slow.
- And just like that headphone jack screwed AGAIN but no more lag? Any reason for these two things to be related?

Bump. Any help? Still happening, though not as common, when I flashed stock

Could it be a hardware problem? Though it would be odd for a hardware issue to show up after flashing a rom. How long have you had the phone before the issues started?

Have you tried the official 4.1.1 image?
If so, do problems go away?
If you are using ports you have to expect bugs.
Let us know
Sent from my Galaxy Nexus using xda premium

Try flashing just the system.img a few times in fast boot with a reboot boot loader between. I was having slow boot up and random performance issues on full stock until I flashed that partition with the stock image (3 Times to be precise). I no longer have the 5 minute wait for the Google logo to disappear, and overall much snappier. Apparently something was leftover from previous restores/downloaded OTA updates.
Sent from my Galaxy Nexus using xda premium

I'd suggest you stop messing around with multiple ROMs and start trying different kernels. Kernels will impact performance much more than any specific ROM will. Try either an updated version of leanKernel (assuming your sig is accurate) or a different kernel all together. Others have had luck with franco, trinity, etc, etc.

Had the same problem on my GSM GNex yesterday. Flashed a ROM combination (Xylon 4.2.1 + Lean Kernel 5.0) and had this lag.. everything would lag and FC.. tried a full wipe as well but didnt work..
Changed to another AOSP Rom (UDK 4.2.1 with linaro kernel) and its fine now..
Oh and i also changed recovery from 6.0.1.5 non-touch(that i flashed yesterday) to CWM 6.0.1.9 touch..
Not sure if this helps but thats what worked for me.. I suggest going back to a ROM that worked for you in the past.. and also try formatting your SD card and run the phone without putting back your data for a while..

@rlb81 - Starting to think it might be a hardware one but at this point I'm not sure of anything. Only had the device 3 months.
@tincbtrar - Yeah I flashed the official 4.1.1 image and the problems are still there. Ridiculously sluggish and the audio problems. In fact, on stock 4.1.1 I just had this issue where I'd turn the screen off, the animation would be really slow, and then I'd get a black screen and wouldn't be able to wake it up. Did a battery pull to boot it again and the same exact issue the second time it turned on.
@Winesnob - I'll be sure to give this a try. Thanks so much! This is a really odd issue and I've never experienced it on any of my previous android devices (Fascinate, Incredible, Thunderbolt, even the old HTC Vogue)
@Cilraaz - Currently just trying to get stock running properly so everything is locked right now. Can't remember but I'm pretty sure I tried the newer lean kernel when I flashed back to bugless.
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
Thanks so much to all of you guys. If you have any other input it'd be greatly appreciated.

+1 on try different kernels, my phone seems to love lean kernel. I switched to tiny kernel for a few days and every so often, a simple task like opening tapatalk would take up to 30 seconds, and everything would become unresponsive. Nothing but smoothness on lean, give some different kernels a try.
Sent from my Galaxy Nexus using Tapatalk 2

I tried Winesnob's method and I THOUGHT it worked. Was running smooth for a good amount of time and just now back to the really choppy mess it was before. In fact it just got frozen on the lock screen and went to a black screen again.
This is killing me. The headphone jack thing seems to be a hardware issue anyway so I emailed Wirefly about getting a replacement. I feel like they'll avoid that though and I'll be left with this.
Gonna try some other things tonight. Wish me luck
EDIT: The thing gets so choppy that notification sound get choppy and crackle. This is insane. I'm fully stock minus the unlocked bootloader right now
EDIT2: Flashed stock image and touch sounds came back. This is getting really weird. Lag is still here though. Really bad lag

Bumping again now that I've sort of pinpointed the issue. Lags with touch sounds enabled and headphone jack works / soundabout installed with touch sounds on.
Currently the phone's headphone jack is screwed up, I installed soundabout, disabled touch sound and no lag.

Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app

Ahh thanks for the heads up
Would it be wise for me to try going back to the ROM that started the problem? Maybe that'll do *something?

Again, from what I saw, everyone had some luck going back to the rom that caused the problem.
There's a tool in the developer thread called "super duper wipe" that seems to have fixed the lag for ones having the issue. I'm not sure how it works, but If you can take it apart and look at the zip, it may point someone in the right direction.
Sent from my Incredible 2 using xda app-developers app
---------- Post added at 12:23 AM ---------- Previous post was at 12:22 AM ----------
The dev thread in the DROID incredible 2 forums.
Sent from my Incredible 2 using xda app-developers app

SkinnyT said:
Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I took a look at that super duper wipe script...looks interesting but not necessary on our phone.
Im starting to think you may have a hardware issue if you cant flash stock images and get everything back to normal. Maybe a relock and then unlock?
i just did this cause I had a SIM card issue...and naturally it wiped my data completely.

solarpolitiks said:
...
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
...
Click to expand...
Click to collapse
turns out my lag problems weren't gone completely until i wiped /System before flash.. Alot of ROM's out there have a /system wipe script, but the one causing my FC's and lag didn't, so it was installing the new system files on top of the old ones and possibly causing a conflict.
it could the same for you

Yeah I've recently tried unlocking again, formatting system before a ROM flash and I still get lag. Now it's more that it will last a day without the lag and just magically come back the next day. Headphone/speaker issues still exist. Wirefly completely ignored my first email so I sent them another one. Hoping for the best.
Completely lost on what this could be

anyone see this thread?
http://forum.xda-developers.com/showthread.php?t=2029246
I have random lag on my vzw nexus and i think its io related and nothing to do with the kernel.
Sent from my Galaxy Nexus using Tapatalk 2

I'll check out that app but like I've mentioned. Lag seems to be coming from sound. After installing soundabout to get the speaker working again I get some nasty lag. Disable touch sounds and I have no lag. Disable the sound effects on twitter - no issues with the app. WireFly said I'm still under manufacturer warranty through my carrier and it sounds like I should be covered. If Verizon tries anything to get around that they'll be willing to do a three way call to make sure I get the replacement. I'll probably end up with a refurb but hopefully it'll beat this stupid issue.

Just stopping in to say thanks to everyone that tried to fix the issue but Verizon is sending out my replacement device today and I'll be sending this one with the faulty headphone jack back.
Problem solved!

Related

[Q] Caller Can't Hear Me

This has been happening on my Epic 4G for awhile now and it's really frustrating. I'm pretty sure this hasn't been happening the whole time I've owned the phone, but at this point it's hard to really remmber.
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Right now I'm slowly removing apps from my phone after every call this happens on - my goal is to determine if a particualr app is confusing my phone. I don't think it's the ROM or modem I'm using (Frozen 1.2, EC05) as I did a stock flash and flashed to those just recently and others aren't having the same problem. I DID restore some data so if I can't narrow down an app that's causing it, not restoring any data is my next option (but even more time consuming to figure out specifically which data is causing issues).
I'm pretty sure the phone hasn't always done this so I don't want to exchange the phone considering I don't have any other issues and I think this is software, not hardware related. Has anyone experienced anything similar to this?
Have you tried switching Roms, I have this same problem on EC05 when I moved to gingerbread it stopped happening.......
Do you voodoo installed?
Sent from my SPH-D700 using XDA App
I was having the same problem with EF02 and the EF02/EF10 modems. I switched back to the EC05 modem and haven't had the problem since (knocking on wood)...
Sent from my Transformer TF101 using Tapatalk
Try ee03 modem..
Sent from my SPH-D700 using Tapatalk
masaidjet said:
Have you tried switching Roms, I have this same problem on EC05 when I moved to gingerbread it stopped happening.......
Do you voodoo installed?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I do have Voodoo installed (since it comes with Frozen 1.2). I haven't tried switching ROMs yet but I have started looking again (I was pretty content with Frozen but if no one had a similar issue and changing the modem doesn't work then a ROM switch is my next try).
Thanks to others who suggested changing modems - I'm going to do that now and see if EE03 fixes this....*crosses fingers*
evancg said:
I do have Voodoo installed (since it comes with Frozen 1.2). I haven't tried switching ROMs yet but I have started looking again (I was pretty content with Frozen but if no one had a similar issue and changing the modem doesn't work then a ROM switch is my next try).
Thanks to others who suggested changing modems - I'm going to do that now and see if EE03 fixes this....*crosses fingers*
Click to expand...
Click to collapse
Go into you Voodoo sound settings and change recording setting to Original. Shoul fix your issue.
Sent from my SPH-D700 using XDA App
Sure you are not hitting the mute button by accident? Sounds dumb but I've done that before.
Blankrubber said:
Go into you Voodoo sound settings and change recording setting to Original. Shoul fix your issue.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I have the SAME EXACT PROBLEM and just like the OP it hasn't always been like that, did this work for you?
Sent from my rooted, suited, & booted Epic 4G kno dat!
I was having the same issues so I just applied this. People couldn't hear me on speakerphone at all...seriously. hopefully this helps. Thanks for the tip
Sent from my SPH-D700 using XDA App
evancg said:
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Click to expand...
Click to collapse
Yes! Mine started doing this a couple months ago, and I resolve it exactly the same way (though I have to hit the volume button once, either up or down, then toggle speaker on then off). It's definitely not the ROM because I've had it with both Froyo and GB ROMs. Unfortunately, I haven't found any other solution, yet. I'm hoping it will go away with official GB, but I have no real reason to think it will work. I'm going to play around with the Voodoo sound.
edonnelly said:
Yes! Mine started doing this a couple months ago, and I resolve it exactly the same way (though I have to hit the volume button once, either up or down, then toggle speaker on then off). It's definitely not the ROM because I've had it with both Froyo and GB ROMs. Unfortunately, I haven't found any other solution, yet. I'm hoping it will go away with official GB, but I have no real reason to think it will work. I'm going to play around with the Voodoo sound.
Click to expand...
Click to collapse
you guys shouldn't be having this problem make a backup then odin to ec05 stock and check if you still have the issue if you do just take it to sprint and show the tech your problem they should fix it or get you a replacement phone.
I have the same issue. I am completely stock. It usually happens 10 to 15 minutes into a phone call. I've already called sprint, taken it to a store but only reflashed the os, and I just recently spoke to someone on chat, who said the problem has been solved. If it happens again should I get a replacement phone?
Blankrubbers fix actually worked for me
Sent from my SPH-D700 using XDA App
steviee7 said:
you guys shouldn't be having this problem make a backup then odin to ec05 stock and check if you still have the issue if you do just take it to sprint and show the tech your problem they should fix it or get you a replacement phone.
Click to expand...
Click to collapse
I had this problem as well. I odinned stock and problem solved. Now I'm back on bonsai with no problems.
Edit: I just noticed that I don't have voodoo sound installed, I know that I used to, maybe deleting that solved my problem and not odinning back to stock.
Sent from my SPH-D700 using Tapatalk
evancg said:
This has been happening on my Epic 4G for awhile now and it's really frustrating. I'm pretty sure this hasn't been happening the whole time I've owned the phone, but at this point it's hard to really remmber.
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Right now I'm slowly removing apps from my phone after every call this happens on - my goal is to determine if a particualr app is confusing my phone. I don't think it's the ROM or modem I'm using (Frozen 1.2, EC05) as I did a stock flash and flashed to those just recently and others aren't having the same problem. I DID restore some data so if I can't narrow down an app that's causing it, not restoring any data is my next option (but even more time consuming to figure out specifically which data is causing issues).
I'm pretty sure the phone hasn't always done this so I don't want to exchange the phone considering I don't have any other issues and I think this is software, not hardware related. Has anyone experienced anything similar to this?
Click to expand...
Click to collapse
speak up i can't hear you
Sadly even after changing modems and making the adjustment in Voodoo Control I still have the same problem. Going to uninstall Voodoo all together and see if that resolves anything.
I just discovered that I'm having the same problem after I Odin'd back to stock EC05 for a different reason. So, EC05 and EC05 modem, and I'm having a problem that I didn't think I was having before I tried EF02.
Could something have been changed that going back to EC05/EC05 modem didn't resolve?
Sent from my Transformer TF101 using Tapatalk
evancg said:
Sadly even after changing modems and making the adjustment in Voodoo Control I still have the same problem. Going to uninstall Voodoo all together and see if that resolves anything.
Click to expand...
Click to collapse
This problem is not generated by Voodoo. I have a stock Epic (rooted) and have never had Voodoo installed on my device and I have intermittently had this problem in the past (haven't seen it for a while, though). My friend has an Epic (never rooted) and also has this problem.
About the only thing I've heard that people have said fixes this is to wipe cache and dalvik and then flash something using Odin. Stock or custom I don't think matters.
As others have noted, uninstalling Voodoo didn't fix it for me. I think what must be causing this is everytime I wipe and install a clean ROM I restore some data through TiBackup and SOMETHING I'm restoring is causing this. Guess I'll just have to wipe and be very careful about what I'm restoring.
This might be completely random, but by chance did other people that experience this problem happen to install NZBAir?

[Q] All sound randomly dropping in/out

For the longest time I was on stock rooted EK02. I recently took the plunge and wiped all and installed CM10, which I love. The only problem I've had is that *all* sound suddenly decides to just go away whenever it wants to (ring/notif tones, touch clicks, app sounds, everything except in-call audio). It might last 5 minutes, or it might last an hour, but it always comes back on its own, and a reboot does not fix it. I can't seem to trigger the problem with a certain app or a certain action, but for example, I will be sitting here playing Angry Birds Star Wars, and the sound will just drop out completely. A few levels later, it comes back on its own. I put the phone down, go do something else, and the entire phone has muted itself again. Frustrating...
I'm on CM10 beta2 nightly 20121108
Kernel version says 3.0.15-CM-g8e7ed92, which seems appropriate since it references CM and this is the first CM I've ever had on the phone. Should I try other kernels though? AFAIK, no one else has mentioned this particular audio problem in the CM10 discussion thread. At least I don't think this is related to the "low volume in some apps" issue.
HOWEVER, something interesting, the baseband/radio version says EK02. I guess I should update that to get better comm, but it couldn't be causing an intermittent muting issue, right? I guess I assumed incorrectly that a ROM installed after a wipe would have to include its own modem. Argh.
This is frustrating, as I said. Thanks for any help.
Wow. 5 days and no replies. Can't someone at least tell me what you think? I've never understood why I can ask a legitimate, polite, and descriptive question after searching the forums as much as possible, and it gets ignored, while someone else can post something completely redundant that barely forms a coherent sentence, yet it sparks a 10 page discussion... frustrating.
I am not exceedingly familiar with cm10 but I would bet it is not the modem causing that issue. I would be inclined to think you have intentionally and / or accidentally changed the "quiet hours" or setup some form of silent profile. Otherwise it was perhaps a bad flash, you did not wipe CLEANLY (IE. calkulins format all or odin a full wipe/restore rim first) or maybe not install with what many revs believe to be a CWM safe kernel???
---------- Post added at 11:24 PM ---------- Previous post was at 11:19 PM ----------
also do you have anything (pc or stereo) connected to Bluetooth with the phone nearby?
trmitche2 said:
Wow. 5 days and no replies. Can't someone at least tell me what you think? I've never understood why I can ask a legitimate, polite, and descriptive question after searching the forums as much as possible, and it gets ignored, while someone else can post something completely redundant that barely forms a coherent sentence, yet it sparks a 10 page discussion... frustrating.
Click to expand...
Click to collapse
Nobody knows the answer to your questions. This is not a common problem and as mentioned above the modem has nothing to do with it. My only suggestion would be to flash a stock release one click, not a leak, and go from there.
Agree with above and mainly because I borked my build... it was perfect and then I tried a gps fix flash. Can confirm now that wipe in CWM and calks format all does not do crap for aosp, jb, or the like. So long story short, yeah you gotta one click or my guess is best served to clean slate with a stock ROM and in consequently factory wipe and just stay there.....
Wow thanks for the replies guys! I was really getting discouraged there for a bit.
I don't think it's a quiet hours setting, because all sound is cutting in and out *every 5-10 minutes*,
I will use Calk's wipe and start from scratch as suggested.
Although unrelated, surely EK02 is not a recommended modem for CM10, right? I guess I made a naive assumption that a full wipe followed by CM10 install would replace my old modem. I'm just curious what kind of problems might be caused by using such an old modem, even though I know sound is not one of them.
Can anyone recommend a modem for this ROM from personal experience? I understand from the main beta2 thread that the FK modems break 3G...
Just flash a one click, it will wipe everything and install a new modem. I'm using fi27 modem with codename rom, works fine. My current install method is run one click update prl and profile and get gps lock then do the install process of the rom.
someguyatx said:
Just flash a one click, it will wipe everything and install a new modem. I'm using fi27 modem with codename rom, works fine. My current install method is run one click update prl and profile and get gps lock then do the install process of the rom.
Click to expand...
Click to collapse
Yes. Do this. Then. Format all is still a good idea if you choose to revert to a GB ROM like el29 and progress.
UPDATE: I fixed this.... accidentally. What fixed it is hard for me to believe or accept, but Iv'e confirmed it by being able to reproduce it. The problem was being caused by the FRIKKIN' FACEBOOK APP. :/ I uninstalled the FB app for a totally unrelated reason: battery drain pointed out in another post. I realized the next day that the sound had not cut out once since then, I re-installed FB, and the problem returned quite predictably: all sounds started cutting in and out every few minutes. Uninstalled FB again, and sound has been fine ever since. My best guess is that the sound was cutting out/in each time a background sync of FB occurred. So now my sound is perfect and my battery life is much better to boot. I never used that damn app anyway.
Unrelated, but for what it's worth, I never installed a new modem as discussed above. Still running EK02 with CM10 nightly from 11/28. Have no problems to speak of. I didn't leave it on purpose, (noob mistake, thought CM10 installation would replace it), but I don't see any reason to change it as long as everything seems perfect, unless anyone can tell me what types of problems it could cause. Any further thoughts welcomed, but thanks again to you guys who already gave me advice.
trmitche2 said:
UPDATE: I fixed this.... accidentally. What fixed it is hard for me to believe or accept, but Iv'e confirmed it by being able to reproduce it. The problem was being caused by the FRIKKIN' FACEBOOK APP. :/ I uninstalled the FB app for a totally unrelated reason: battery drain pointed out in another post. I realized the next day that the sound had not cut out once since then, I re-installed FB, and the problem returned quite predictably: all sounds started cutting in and out every few minutes. Uninstalled FB again, and sound has been fine ever since. My best guess is that the sound was cutting out/in each time a background sync of FB occurred. So now my sound is perfect and my battery life is much better to boot. I never used that damn app anyway.
Unrelated, but for what it's worth, I never installed a new modem as discussed above. Still running EK02 with CM10 nightly from 11/28. Have no problems to speak of. I didn't leave it on purpose, (noob mistake, thought CM10 installation would replace it), but I don't see any reason to change it as long as everything seems perfect, unless anyone can tell me what types of problems it could cause. Any further thoughts welcomed, but thanks again to you guys who already gave me advice.
Click to expand...
Click to collapse
None, modems are interchangeable between builds with the exception of the fk-- and newer modems, they only work with Touchwiz based JB roms. If your modem is performing well speed and call quality wise then there's no need to change. However you could always test other modems to see if you get any improvement in your location. If you choose to change modems you should be on a touchwiz rom so you can update prl and profile after the modem flash. Modems are a YMMV item each one interacts with different devices and locations differently so to find the best modem for you you just need to flash and test them out if you so choose
Sent from my hand to your eyes!
Samsung: Intercept, Galaxy S2, Galaxy S3, Galaxy Note 2, Nexus10
HTC: EVO4g, EVO 3d
LG: Optimus G, Nexus 4
Asus: Nexus7
Motorola: Photon
Amazon: Kindle Fire, Kindle Fire HD
We are legion, for we are many!
Thanks KoN! Extremely helpful post, as always. All other replies in this thread have been thanked as well. I learned a lot.
Still wish I knew how FB could make my sound cut in and out every few minutes, but if no one else has seen that issue, it must've been a quirk, so I imagine I'll never know. Moving on....

[Q] s3 stuttering/twitching

I have tried searching for this problem but I must be using the wrong terms... so sorry in advance if I missed a post that addressed this issue.
My sprint S3 does this twitchy/glitching thing on every touchwhiz based jellybean rom (does not do it on TW ICS ROMS) I have tried. It basically makes it nearly impossible to do sliding animations, IE it can actually get stuck and start flashing halfway between screens, or when pulling down the top menu, however you can open new programs just fine if you are already on the right screen for them. Luckily it does not do this all the time, but when it happens it keeps doing for 10 minutes or so and its annoying as hell.
I figured this must be a rare issue even though it effects both my wifes phone and mine, since I have never read anything about it, however I just got a new replacement phone and it does the exact same thing, even on dead stock TW JB ROM.
Oddly enough I discovered last night that if I turn on my screen filter app it stops completely, but it starts right back up when I turn off screen filter..... any ideas how to fix this?
Try grabbing cache clear from the play store and set it to run every 12 hours. It helped my phone a good bit.
Sent from my SPH-L710 using xda premium
No one else ever has this issue?
joelespinoza said:
No one else ever has this issue?
Click to expand...
Click to collapse
I had it dude, but it was just on the CleanBean ROM, it was annoying as hell!
So I changed the ROM, Its weird that its happening on a Stock ROM, any suspicious app?

Urgent and Serious issue with audio! HELP needed. please!

Guys, I have this one major issue with audio in my phone and its the rarest of the problems! The whole audio output stops completely. By completely, i mean even the receiver sound. completely dumb! cant hear anything if someone calls me. This has been occurring since a month or so. I am running on Cyanogenmod 11 M8. Even if i restart the phone its stays the same way. And all of sudden, randomly, the audio back again, working properly. when it goes dumb it stays like that for 5 6 hours. it happens quite often. this is throwing me off totally.
Device : Galaxy S3 SGH i747 - At&t
This problem happens:
1) when i am on call, suddenly it goes mute.
2) when the phone is kept idle for more than 3 4 hrs. So every morning its dumb when i wake up.
These are what I've tried and what I've found out:
1) I reverted back to stock 4.3 to check if its the problem with audio hardware. But in stock it worked perfectly and flawlessly. no issues there. SO its definitely got to do with cyanogenmod.
2) I flashed ktoonsez kernel on CM 11 M8, to check if its kernel problem. But its happening again. SO its not the problem with kernel.
3) I recently found out that if I wipe the cache from recovery, audio is back working. SO its definitely something in the cache thats messing with the audio. Some app may be.
this thread can be referred for more details on this issue:
http://forum.cyanogenmod.org/topic/81373-audio-stops-working-from-time-to-time/
and I dont know what else to do now. Ive tried uninstalling all the apps that access audio. But the problem still persists.
I really really need help fixing this one. PLEASE HELP.
s.vivekananda007 said:
Guys, I have this one major issue with audio in my phone and its the rarest of the problems! The whole audio output stops completely. By completely, i mean even the receiver sound. completely dumb! cant hear anything if someone calls me. This has been occurring since a month or so. I am running on Cyanogenmod 11 M8. Even if i restart the phone its stays the same way. And all of sudden, randomly, the audio back again, working properly. when it goes dumb it stays like that for 5 6 hours. it happens quite often. this is throwing me off totally.
Device : Galaxy S3 SGH i747 - At&t
This problem happens:
1) when i am on call, suddenly it goes mute.
2) when the phone is kept idle for more than 3 4 hrs. So every morning its dumb when i wake up.
These are what I've tried and what I've found out:
1) I reverted back to stock 4.3 to check if its the problem with audio hardware. But in stock it worked perfectly and flawlessly. no issues there. SO its definitely got to do with cyanogenmod.
2) I flashed ktoonsez kernel on CM 11 M8, to check if its kernel problem. But its happening again. SO its not the problem with kernel.
3) I recently found out that if I wipe the cache from recovery, audio is back working. SO its definitely something in the cache thats messing with the audio. Some app may be.
and I dont know what else to do now. Ive tried uninstalling all the apps that access audio. But the problem still persists.
I really really need help fixing this one. PLEASE HELP.
Click to expand...
Click to collapse
I've had that issue a month or two ago but haven't seen it on the latest ROMs. I'm not sure what causes it but I would suggest you flash another ROM if CM messes up with your sound (or another version of CM).
BWolf56 said:
I've had that issue a month or two ago but haven't seen it on the latest ROMs. I'm not sure what causes it but I would suggest you flash another ROM if CM messes up with your sound (or another version of CM).
Click to expand...
Click to collapse
Hi, Thanks for the response. I personally like CM and the extent of customization it offers. I actually dont mind switching cuz sound is bigger deal. Would you mind suggesting ROMs that are similar or comes closer to CM and also good at the same time? which ROM are you on?
s.vivekananda007 said:
Hi, Thanks for the response. I personally like CM and the extent of customization it offers. I actually dont mind switching cuz sound is bigger deal. Would you mind suggesting ROMs that are similar or comes closer to CM and also good at the same time? which ROM are you on?
Click to expand...
Click to collapse
I don't suggest ROM to avoid flaming but you can look in my sig
BWolf56 said:
I don't suggest ROM to avoid flaming but you can look in my sig
Click to expand...
Click to collapse
Hey it got fixed in the latest nightly ( cm-11-20140721-NIGHTLY ). I had put it in cyanogenmod forum, I guess they read the issue and fixed it. Audio is perfectly fine now! Feels so great to use cyanogenmod again.
Thank you cyanogenmod!
I have this issue too but it doesn't have to do with the audio disappearing; it's simply gone from the get-go after clean flashing a ROM.
As you've said, stock FW and ROM works fine, but anything custom will just totally break it. Seems to be a very isolated issue with the phone itself, I've searched all over for people with the same problem but could never find anything.
gsm22 said:
I have this issue too but it doesn't have to do with the audio disappearing; it's simply gone from the get-go after clean flashing a ROM.
As you've said, stock FW and ROM works fine, but anything custom will just totally break it. Seems to be a very isolated issue with the phone itself, I've searched all over for people with the same problem but could never find anything.
Click to expand...
Click to collapse
Oh. It used to happen to me once or twice. No audio when I install CM, after it boots the first time. I think you should check the new nightly of 7/23. Looks like its fixed. They've fixed a number of audio issues over the last few nightlies. And I've always preferred CM over any other roms, so I've no idea about why it isn't working on other roms.
s.vivekananda007 said:
Oh. It used to happen to me once or twice. No audio when I install CM, after it boots the first time. I think you should check the new nightly of 7/23. Looks like its fixed. They've fixed a number of audio issues over the last few nightlies. And I've always preferred CM over any other roms, so I've no idea about why it isn't working on other roms.
Click to expand...
Click to collapse
Thanks for the suggestion, I may as well give it a try since most everything else I've tried has had the same issue.
edit:
Clean flashed latest CM nightly, sound worked for around 2 minutes, then stopped when I plugged headphones in. Rebooted, got it to work via speakers again but then DSP manager force closed and left me without sound.
Rebooted into recovery, cleared cache, still no dice.
Going to try another clean flash to see if I can get sound to last a while longer.
edit 2: It seems to be screwed completely now, no sound after install + reboot.
Same logcat lines as in http://forum.xda-developers.com/galaxy-s3-att/help/audio-wide-custom-roms-t2825135

Screen Glitches,Stock Rooted S3.

I've been getting these glitches/artifacts/tearing on any 4.4+ rom on my T-mobile S3.
It's like the status bar will glitch down to the bottom of the screen.
I'm currently on a 4.3 stock rom (ENC2), It's been rooted with the samsung toolkit and has knox disabled (at least according to the app).
I've tried most current d2lte roms, PA, spirit, ACIP...ect.) and they all have it.
I know for a fact I'm missing something. I just can't remember what it is for the life of me. I know it has something to do with the bootloader/binary. I seem to remember when 4.4.1 came out there was something with the bootloader we had to do and no matter what I search nothing is coming up with the correct solution.
I'm hoping someone could tell me what i'm missing because it seems painfully obvious and I'm missing it, . I really don't enjoy using TW.
We don't ever mess with the bootloader or other parts of the base firmware, so maybe you're thinking of a different device?
When did it start? What was the last thing you did (flash)? Tbh, to me it sounds like a hardware problem. Maybe a connector got loosened, or some moisture/water damage, or even heat damage could cause what you are describing. Especially if its happening on every ROM.
Flash the stock NC2 firmware via Odin and factory reset. If it still happens after that its almost certainly hardware related.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Does it also happen with touchwiz?
So. I ran the knox removal thing from the samsung toolkit and now I don't see them on the latest CM nightly.
I have to test a few other roms but I don't know, it's somehow fixed, thank you for the responses.
Glad to hear it. Be careful with the toolkit though. It is not supported and has bricked devices.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
After giving it a few days the issue came back.
I've tested this on a stock nc2 touchwiz as well as your (doc) latest likewise release with no issues with the screen or anything.
For the non touchwiz I tried aicp latest 4.4.4, the latest cm11, the latest aospa weekly and a 4.3 AOKP release (milestone2).
The glitch issue wasnt in the cm release for a day or so then showed up, all others showed up instantly.
I also emergency recovered via kies. Then rerooted. I'm also using the latest twrp
Here is a logcat of the ROM I'm currently on, the 4.3 AOKP. I wish I had more of an understanding of logcats so i knew if I posted the right section.
http://pastebin.com/UyZFHriB
I was curious so I booted up a nandroid of aicp and then restored a backup of the boot from likewise. Results were minimal glitching but no connectivity at all. APNs didn't load and WiFi is broken. I'll post a video shortly of the screen.
The only thing that jumps out on that logcat is where you have this kind repeated several times in a row:
09-18 13:35:38.752 W/ActivityManager( *761): Permission denied: checkComponentPermission() owningUid=10060
But I honestly don't know what its referring to. But I will say that since it appears to be happening on every rom, even stock, it sounds more like a hardware issue. Display problems usually are to begin with, but almost any problem that persists across multiple ROMs and wipes can usually be blamed on a hardware malfunction.
Watch a disassembly video on youtube, then open it up and reseat all connectors. (Don't mess with the antenna. Its fragile and not related to the issue at hand.)
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
But I will say that since it appears to be happening on every rom, even stock, it sounds more like a hardware issue.
Click to expand...
Click to collapse
That's the odd thing, On both 4.3 and 4.4.2 versions of touchwiz I don't get the glitching. Only on AOSP based roms. I could just go stick with a touchwiz based rom and be done with it but my personal preference is not using touchwiz. I'm just confused as to what is actually causing this.
I'm guessing it has to have something to do with the bootloader and baseband.
I think i did forget to mention this is a "refurbished" warranty replacement, i regret that I don't recall which specific version it had as stock, I'd guess it has to be enc2?
Here is a poor quality video to show whats happening, on the home screen you see the glitching where the status bar glitches down to the bottom. I tried to get it to do what it sometimes does in both the MLB app as well as the reddit app but it decided not to be as noticeable this time.
http://youtu.be/ZsZL1Okio-A (sorry about the added music )
Just a side question, I couldn't seem to find a definitive answer, but was it ok to downgrade within the 4.3 bootloaders? I thought I remember reading that as long as you don't go from 4.3 to 4.1.2 it was fine.
Soryy I misunderstood before about it happening on stock. Have you tried any different kernels? I'd suspect that before bootloader. But since it's a refurb, there's just no telling for sure.
Once on 4.3 you cannot downgrade your firmware at all. You can flash older roms, but that's it.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

Categories

Resources