Develop Bugs

[Q] Scratchy music

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.

Bluetooth Only Connects ONCE!

This annoying problem popped out of nowhere I can think of.
Originally running AOKP #37. Since then I've tried all version of AOKP back to M5, wiping, formatting /system, CM9, faux123 16m, 17m, 18 b3. Each ROM the same problem.
I can connect to a media device once, either the car of speakers then a reboot is needed to [play] media again. The phone does show it being connected to the car but it's phone only.
If music is playing, through the phones speaker, and a call is placed the music plays [with] the call.
I've restored to AOKP b34 which seems to work, and totally wiped the phone to factory 4.02 which also seemed to work. Wiped flashed b37 back and was fine for a day.
I'm lost. It's annoying having to reboot at every 7-Eleven, gas station or Starbucks.

rinse and repeat? try a different rom? different kernel?

I rinsed and repeated constantly over the last week.
It's with all the ROMS I tried except for returning to stock, I think, I didn't keep it more than half a day and with AOKP b34 restored.
Oh, I had the "hybrid" radios, I've since installed 4.0.2 radios, 4.0.4 radios and am back to 4.02 thanks to returning to factory.
This is a VZ Galaxy Nexus.

I think I found my issue finally. I think a few more tests will confirm it's the MIUI permissions mod.

I've found the Bluetooth on the GN a bit buggy too. Though i manage to live with it.
When connecting to bluetooth devices i usually get the device to do the connection. If that doesnt work i just toggle Airplane mode on and off, and then it's working again.
If I manually turn off bluetooth it will end up hanging when turning on again.
After i switched to CM9 I think bluetooth overall is working a little better (might be placebo effect though).

The problem is definitely the MIUI permission mod.
Reinstalled it today and the issue returned immediately.
The stock Bluetooth system actually worked pretty good. from Nexus WAS controllable from the car stereo to an extent.

VZW Nexus, Jelly Bean, and weird headset issues?

So I've had a VZW Nexus for about 5 months, flashed all kinds of custom ICS stuff on it, never had problems.
When Jelly Bean ROMs come out I flash one built from AOSP, works great, after a while an updated version of the ROM hits Goo.IM, I dirty flash+GApps, and suddenly after a few days my phone seems to be stuck in headset mode, not allowing me to use the mic or make calls without using speakerphone mode.
Do full system wipe, factory reset of radios/system/bootloader back to IMM76K, the issue is still there at first boot, hmm, must not be a software issue then.
I Google, this seems like a known hardware issue with the headphone jack, get a replacement from Verizon, it works fine, no problem.
Until I flash an AOSP JB ROM on this working phone, then, just like before, after dirty flashing a JB AOSP ROM upgrade, a day or so later I get the exact same issue, and again full wipes/factory resets don't fix it.
Verizon sends me a new one. This time, I'm staying on IMM76K.
This seems fishy to me, the odds of getting this kind of hardware failure on two different phones after the same sequence of events and there being no relation is astronomically high.
Again, not running any OC's or anything weird. Never dropped the phone. Don't use it in humid environments. Don't even use actual headsets. Used the first phone for months with no issues. Tried SIM/battery pulls. The AOSP JB ROM in question is used by many without this issue, though I have found what seems to be a few more instances of this that have happened after JB upgrades via Google.
Any explanations? Is there a weird bug in AOSP that's frying stuff? Doesn't seem likely or even possible, but then why?

Could my phone be degrading somehow?

I've been having the strangest issues lately.
I'm running task's AOKP with ktoonsez's kernel. For the past month or so I've been getting random home button lag, wakeup stuttering, and general stuttery animations.
And I've recently discovered that I absolutely cannot use my phone at all while it is playing audio. If I perform ANY sort of action, music will stutter really badly (unlocking the device, turning off the screen, opening a folder on my homescreen, opening an app, clicking something within an app, literally almost ANY action that involves tapping the screen will cause a stutter). Happening on both Underwear and ktoonsez kernels, even on stock settings.
I've tried clean wiping many times (at least 5 times in the past 3 days) and clean wipes tend to fix the issues initially, but things gradually get sluggish again after a few days. I've tried ktoonsez's kernel on straight up stock settings, and I've tried task's Underwear kernel on stock settings, and I still get these things.
Now, I see no one else in any of the threads having issues like this. So I really don't think I can blame the ROM or kernel.
So is my phone just all of a sudden hating custom ROMs and kernels? Is my processor caving or something? I can't think of any other good reasons why my phone and only my phone is buckling under the latest ROM releases. I've tested my SD card and speeds are what they should be.
Do I need to literally purge my phone, return to bone stock firmware, and start over? I'm not sure how else I can 100% determine whether it's my phone acting up or something software/firmware related. But I'm wary also of issues with jumping from 4.2 to 4.1 and back.
This is all just kinda frustrating. I'd just like to know whether it's possible that my phone is simply deteriorating before me in some form or fashion. Could the flash memory be acting up? Could the GPU be problematic? I really have no idea.

MdX MaxX said:
I've been having the strangest issues lately.
I'm running task's AOKP with ktoonsez's kernel. For the past month or so I've been getting random home button lag, wakeup stuttering, and general stuttery animations.
And I've recently discovered that I absolutely cannot use my phone at all while it is playing audio. If I perform ANY sort of action, music will stutter really badly (unlocking the device, turning off the screen, opening a folder on my homescreen, opening an app, clicking something within an app, literally almost ANY action that involves tapping the screen will cause a stutter). Happening on both Underwear and ktoonsez kernels, even on stock settings.
I've tried clean wiping many times (at least 5 times in the past 3 days) and clean wipes tend to fix the issues initially, but things gradually get sluggish again after a few days. I've tried ktoonsez's kernel on straight up stock settings, and I've tried task's Underwear kernel on stock settings, and I still get these things.
Now, I see no one else in any of the threads having issues like this. So I really don't think I can blame the ROM or kernel.
So is my phone just all of a sudden hating custom ROMs and kernels? Is my processor caving or something? I can't think of any other good reasons why my phone and only my phone is buckling under the latest ROM releases. I've tested my SD card and speeds are what they should be.
Do I need to literally purge my phone, return to bone stock firmware, and start over? I'm not sure how else I can 100% determine whether it's my phone acting up or something software/firmware related. But I'm wary also of issues with jumping from 4.2 to 4.1 and back.
This is all just kinda frustrating. I'd just like to know whether it's possible that my phone is simply deteriorating before me in some form or fashion. Could the flash memory be acting up? Could the GPU be problematic? I really have no idea.
Click to expand...
Click to collapse
downgrading your phone shouldn't be a problem at all.
download stock, wipe clean, flash through odin.

MdX MaxX said:
I've been having the strangest issues lately.
I'm running task's AOKP with ktoonsez's kernel. For the past month or so I've been getting random home button lag, wakeup stuttering, and general stuttery animations.
And I've recently discovered that I absolutely cannot use my phone at all while it is playing audio. If I perform ANY sort of action, music will stutter really badly (unlocking the device, turning off the screen, opening a folder on my homescreen, opening an app, clicking something within an app, literally almost ANY action that involves tapping the screen will cause a stutter). Happening on both Underwear and ktoonsez kernels, even on stock settings.
I've tried clean wiping many times (at least 5 times in the past 3 days) and clean wipes tend to fix the issues initially, but things gradually get sluggish again after a few days. I've tried ktoonsez's kernel on straight up stock settings, and I've tried task's Underwear kernel on stock settings, and I still get these things.
Now, I see no one else in any of the threads having issues like this. So I really don't think I can blame the ROM or kernel.
So is my phone just all of a sudden hating custom ROMs and kernels? Is my processor caving or something? I can't think of any other good reasons why my phone and only my phone is buckling under the latest ROM releases. I've tested my SD card and speeds are what they should be.
Do I need to literally purge my phone, return to bone stock firmware, and start over? I'm not sure how else I can 100% determine whether it's my phone acting up or something software/firmware related. But I'm wary also of issues with jumping from 4.2 to 4.1 and back.
This is all just kinda frustrating. I'd just like to know whether it's possible that my phone is simply deteriorating before me in some form or fashion. Could the flash memory be acting up? Could the GPU be problematic? I really have no idea.
Click to expand...
Click to collapse
Try a full wipe and a clean flash first without ktoonz kernel. I know some phones just can't run it without issues.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I've noticed AOKP's rom and Task's AOKP can sometimes have issues like these, even when doing a full wipe/clean install when coming from anything other than stock. Once you go back to stock, wipe and reflash, I think you'll be alright. When I flash aokp that way, it's usually such a good running rom I have to talk myself into even considering putting anything else on my phone

So. I decided to wipe, flash back to bone stock 4.1.1 through Odin, re-root (root-injected tar method), re-install TWRP, wipe, and re-install AOKP fresh (no ktoonsez kernel).
On the fresh install, I logged into Google, downloaded Play Music, and started playing an MP3. Aaaaand...the stuttering is still there. Music still stutters essentially every time I touch something on the screen.
And every few transition animations is still choppy.
What to do now?
I suppose I'll re-download AOKP to see whether I got a bad download, but I doubt it. EDIT: Nope, same hash.
My phone just doesn't seem to like the latest AOKP builds very much...
I'll play around with it some more.

Just go to recovery, wipe cache n dalvik, and you should be good
Sent from my SAMSUNG-SGH-I747 using xda premium

did you see if the problem persists while on stock?
sent from my i747 with xda-premium

Did you get the same lag and abrupt behaviour when using a different music player app?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I would try a different music player and perhaps even a 4.1.2 aokp instead of the latest 4.2. This would help narrow down/eliminate the issue

I also have this stutters in any rom/kernel i test. micro stutters here and there, when a few weeks ago there was none. all of a sudden stutters and lags on drawer and opening applications. antuntu benchs show the same results so i dont get it.

for future reference: benchmarks don't matter here. there are a few who use them to show how good their phone is, what really matters is real world performance.
if it's happening with everything including stock, I'd gander that it's a hardware issue and you should try for a warranty exchange.
sent from my i747 with xda-premium

Or just flash another ROM
Sent from an ATM machine

Help with CM11 no sound on calls

Hello,
First I apologize for opening a new thread instead of posting in the CM11 thread, but till now I don't have write privileges there.
I recently unlocked and permrooted my Desire HD then installed Mustaavalkosta's CM11, but as a newbie, I have some issues I require assistance with. To note that I did an extensive reading before I did any rooting and installing a new rom.
1- I find myself not hearing anything during calls. It's sort of like my internal speaker got muted somehow after installing CM11. I tried multiple apps to no avail. I read somewhere that if u fail to flash the boot.img in the rom u might get this issue, but thing is I did flash the boot.img after I installed the rom and the recovery and wiped the cache. I can hear the calls with the external speaker turned on and with the headphone, so I think it's not a hardware issue but a software one. Any fix to this?
2- After each restart, the UI somehow resets itself. I mean many of the settings and widgets I use either get reset or vanish like the sleep option in seetings for example (I put the screen to turn off after a 1 min and it resets to 15 sec after each reboot which is annoying as hell). Also, many apps like Dolphin and GoSMSPro shortcuts vanish from the home screen after each reboot, while whatsapp for example doesn't. I'm not able to figure why some app shortcuts vanish while others don't.
3- I tried to use ART instead of dalvik, but yet again after each reboot, dalvik is back. So effectively, I can't benefit from ART.
4- other minor bugs which I will not mention for now till I solve the 3 main ones.
If someone can provide some assistance (mainly for the first issue which is the major one), I will be very grateful. It's becoming increasingly annoying and embarrassing to turn the speaker on every time I receive a call, bc most of the times I am in a room with other individuals or in a meeting, and I am forced to have them hear the conversations bc not always I can excuse myself.

No one has any input on this?

After wiping data, dalvik cache, android secure, etc... and reinstalling the stock rooted 2.3.5 Rom, I still had the same internal speaker issue on calls. The heaphone icon was on even though there were no headphones plugged. I installed 2 widgets (togggleheadset 2 and headphone fix) and the issue was fixed. To note I had this problem back on my unrooted stock Desire HD before I rooted it and upgraded to CM11 BR3 thinking the new rom will fix this problem.
So after I made the calls work on Gingerbread stock rooted rom, I did a clean wipe once more and installed CM11 BR4. The problem reemerged. And the 2 widgets couldn't be redownloaded bc they are not compatible with kitkat. The other issues mentioned in the OP disappeared, only the incall volume issue remained.
I need to mention that many Desire HD owners have had this problem on their Froyo and Gingerbread stock builds, and usually the 2 widgets I mentioned above helped fix the issue. On 4.4.2, it seems some android users have complained of in-speaker audio volume being very low, so maybe this worsens the issue I had instead of fixing it.
I'm leaning to think that it's mostly a software/code issue, otherwise why would the widgets fix the problem on an earlier version if it's hardware related? hence, there could be a workaround for it on Kitkat if someone knowledgeable cares to look at it. Maybe the code turns off the internal speaker or lowers the volume so much it becomes unhearable. The headphone and external speaker are just fine, I can hear the other person in the call without any problem. It's when I rely on the internal speaker that I hear nothing.
Hope someone can offer some assistance here.