Develop Bugs

Is streaming/internet radio working on your Desire? (issue with wireless N patch?)

It's not working properly on mine, ever since I moved up to FroYo a couple of weeks ago.
Streaming works fine over 3G but if I use it on wi-fi, with the screen switched off, the music starts stuttering and eventually skips.
Thought it was an issue with the rom I was using, but I've tried three different ones (including one of the new ones from this afternoon) and I'm seeing the same issue.
Wi-fi policy is set to never sleep so it can't be that.
Could somebody test it out and let me know?
NB
It only happens on wi-fi
It only happens when the screen has been off for one-two minutes

Update, in the off-chance that somebody, somewhere has actually bothered to read this...
Flashed back to 2.1 and the issue was gone. Back to 2.2 and the issue is there again.
edited to remove pointless speculation. solution is on page 2.

why would you call HTC support, surely thats a job for the last.fm development team to work out.

Because I don't think it's an issue with last.fm. It apparently works fine on non-Sense phones, and even works fine with the earlier versions of HTC Sense.
Last.fm has permission to keep the phone awake, and it does so over 3G but not over wi-fi.
It doesn't really make sense unless the newer version of Sense is throttling the wi-fi when it goes into sleep mode and is not allowing last.fm to keep the phone awake.
Can't really verify that though... I might try to find another app that uses the wi-fi connection and see if it exhibits the same behaviour when the screen is off.
edit: just checked with the speedtest.net app and switching the screen off freezes the download in its tracks. Resumes again when you switch the screen back on.

Phone/Wifi sleep issue while not plugged in
Hi, I can confirm that this is happening to me with XiiaLive in an identical way.
- 3G streaming works ok
- Wifi + screen on works ok
- Wifi + screen off BUT plugged into AC works ok
- Wifi + screen off => drops the connection after a couple of minutes
I went mad yesterday trying to make xiia work, but then realized that this could be the case and found this post and another one on Modaco (http://android.modaco.com/content/h...s-possibly-a-request-for-the-next-modaco-rom/)
So you actually saved me the time of testing it in other roms, but anyway, which rom have you got ? I have ieftm one.
I can save you the time to test it with other streaming services, I've tried them all hehe.
It could be a phone sleep issue, rather that a wifi sleep.

Well, like I said above, my guess is that the newer version of sense is throttling the wi-fi to save battery life when the phone is idle. The wi-fi is still working but it's capped at a lower speed.
You can test this by installing tunewiki and trying out a few radio streams. 96kbps works perfectly, 128kbps is ok but stutters a little at times. Then when you go up to 192kbps (which I think is the quality last.fm streams at) it can't keep up anymore and the tracks skip.
re:roms - I was on ieftm, am currently on modaco and was on modaco r5 and r6 before that. All of them have the same issue and all are based on the FroYo/Sense roms.

Hm, it´s working just fine for me. Listening to it right now with display turned off, no problem here.
Using the original Froyo on a debranded Desire...

What do you mean by original FroYo? As in vanilla?
From what I can tell it's only happening on Sense roms.

My statement was a little misleading. I was referring to the normal OTA update...

Sibbi said:
My statement was a little misleading. I was referring to the normal OTA update...
Click to expand...
Click to collapse
Hmm. And it's on wi-fi and it's not plugged in to the mains?
Weird. I can't replicate this on any FroYo + Sense rom. I haven't tried an unrooted 2.2 rom, though.
Be good if we could get somebody else on an OTA 2.2 rom to confirm this.

tuatha said:
Hmm. And it's on wi-fi and it's not plugged in to the mains?
Weird. I can't replicate this on any FroYo + Sense rom. I haven't tried an unrooted 2.2 rom, though.
Be good if we could get somebody else on an OTA 2.2 rom to confirm this.
Click to expand...
Click to collapse
Nope, neither on 3G, nor plugged in... Used last.fm quite a lot in the past days and never experienced your troubles. It only runs on Wifi and mostly unplugged.

Very odd. Thanks anyway.
Maybe this is unique to rooted roms, then.
edit: all the roms I've used have had the wi-fi n patch, now that I think about it. Will see if I can find one that's unmodified.

That's a nice finding (about throttling speed). About n patch: it had problems from day one (and I don't need it), but I can't recall if the version of ieftm I installed has it. Any way to check it, or do you know if it was included from the start ?

Fixed. Did a full wipe and installed a rom that didn't have the wireless n patch. Problem gone.
Sibbi, thanks for posting. Wouldn't have occurred to me otherwise.
Anybody else experiencing an issue with streaming radio/podcasts over wi-fi while the screen is idle, you can grab a rom without the wireless n patch here:
http://android.modaco.com/content/h...-froyo-pre-rooted-no-hboot-with-radio-deodex/
Pick one of the 'with radio' roms. Odexed or deodexed doesn't matter. Make sure to do a full wipe first.

Nice ! Any way to remove the n patch without changing rom ?

Don't know. It could be as simple as extracting the rom and removing the patch, but I couldn't say.
If we could find out where exactly the N patch is and what it's called, I'd be willing to try it out.
You'd still have to wipe and reinstall though

I'll try to find the original n patch and see what changes in regards to modaco original rom

forum.xda-developers.com/showthread.php?t=707873&highlight=Wireless+patch
This was for 2.1, but it might just be the same hack ? It's a small hex edit and a file substitution (kernel module if I'm not mistaken). Will try it tomorrow if nobody does it in the meantime, too drunk right now ...

I'd be a bit wary of that tbh. I don't know enough to go messing around with it. Especially not at two in the morning, when I should already be in bed.
I did find this part interesting:
"Also in theory WiFi n will most prob drain more battery than WiFi g but in my zip's there is k newer firmware which is suppose to help in battery drain."
I wonder if the improvement to battery drain that he's talking about involved throttling down the wi-fi connection when the phone was idle?! Hmm.

Probably, will mess with it tomorrow after a sleep and a nandroid

[Q] Problems with headphone volume after froyo update

This is a post I found after searching for my issue regarding headphones volume problems. I couldn't find anything anywhere on the XDA Forums. Please see my response at the bottom, and any help would be gratefully appreciated.
Ok so I went ahead and upgraded my mobile with the OTA update that has showing on my mobile. I wanted to upgrade ASAP due to the fact that I have run out of space for apps on the internal memory and this upgrade will resolve it (apps can be moved to the SD card).
However I think I may have jumped the gun as now whenever I use headphones the volume is stuck at max and even when the phone software says the volume is silent it’s still blasting out! Unfortunately spotify doesn’t have an internal volume control at all so it’s a no go there too.
I’ve had a search on Google and it looks like people are not experiencing the exact same issue, however there are a lot with issues with the volume in some way or another.
Hopefully this will be fixed pretty quickly as it now makes the phone unusable as a media player and I have to go back to using my iPod.
UPDATE: After searching for a resolution to this and not coming across anything much I managed to find someone saying recessed headphone jacks are quite problematic. The Desire doesn’t actually have a recessed jack but I do use a silicon case that makes the jack a bit recessed. This has not been a problem before, but I thought I’d give it a go without the case. Low and behold the volume buttons seemed to be working fine. I thought this was a bit strange so out the case back on and what’s even stranger is that is still worked fine. Now I have no idea why this happened and to me it seems a bit strange that this would even cause it in the first place (I would assume that it would be lower in volume or only one channel). Unless of course I came across a bug that has a 1 in 1,000,000 chance of hitting. Anyway I’m glad it’s working now!!
My reply:
Hi, I'm having the exact same problem after doing the froyo update. I too searched everywhere but found nothing until now. Unfortunately removing my case doesn't resolve the issue. I thought it may have been ROM related issue, but after trying several different ones the problem still exists. The strange thing is this has only started happening over the last week but I've had froyo for 4 weeks now! Can anyone out there help me ???

I had the exact same issue on the OpenDesire ROM after I flashed a file. The headphone volume was deafening every time it was on with no way to turn it down. But my issue clearly started when I flashed the DSP Manager file floating around. When I switched back to a clean ROM, the issue was no longer there.
I also experienced the issue when I moved between ROMs and updates of ROMs without full wipes. Even when I moved from stock T-Mobile to stock HTC, I experienced the issue. The resolve was simply doing a full wipe.
On HTC 2.2 I don't have this issue at all, thankfully.
-----------------------------------
- HTC Desire via XDA App -

Now you come to mention it I did the DSM Flash Zip about a week ago after flashing LeeDrOiD V2.1a, so it looks like thats the cause. Is there a quick way around this ? i.e. uninstalling the DSM flash or will I have to Full Wipe? Many thanks BTW

[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.

[Q] Sound Issues

i have been having issues with no sound coming from the LG nitro , all of a sudden it cut out yesterday and have hard reset numerous times and 1 out of 4 or 5 reboots the sound comes in but if you power off then on the sound disappears .. this is a stock phone with only root , anybody have any ideas or similiar issues ?

This is not any kind of development related topic but I'd suggest that you bring it in for repair or replacement as that sounds like a hardware issue. Maybe try flashing another rom.
Sent from my LG-P930 using XDA App

moved to general

I had a similar issue and ended up returning the phone to bell for a new one.
Here is the long story just in case it helps some one. Like all good Android users I started by rooting my phone, installing ROM Manager and making a nandroid backup. Once this was done I ran rooted stock for a few days. All was well.
Then I started to debloat my phone. After which everything seamed good. Then installed and played with RAM Manager and SD Speed Increase. TBH i did not notice any particular increase in speed on my phone but that might be due to the following issue.
After all this I decided to run a few test by using the phone into the ground. Added a bluetooth headset, while using navigation and making several calls. It was all running very well until I rebooted. Once rebooted whenever I connect my bluetooth headset I was no longer able to make calls. The phone dialer would completely lag out until I de-activated bluetooth. The the 10 or so test calls I tried making would all go through at once. This wasn't the end of the word for me so I continued to use the phone as everything else was working fine. The things started degrading by which time I was on the new CM9 nightly build. The phone had started being really sluggish. I finally decided to return my phone after it would no longer play any sound and whenever it called to any sound related function would lag out and/or reboot. The same behavior happen in stock, cm9 and NO! NO! ROMs. I tried flashing a few roms in a last ditch effort.
I could be wrong by my conclusion is that the audio portion of the snapdargon chip fried and since these phone are basically just 1 chip the phone simply degraded from there.
I would like to know of anyone else has had similar issue or if I just got a lemon and also your take on the cause of the issue.
Hope this can help someone.
Thanks!
Edit: Returned my phone for a new one and I've been flashing CM9 since the first release and no issues. I'm actually really happy with the replacement and would recommend the phone as long as you don't get a lemon ;-)

[Q] What did I do now?

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?)