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
I've got an annoying problem on my Desire. The mobile network (GSM/WCDMA, not data) drops when my screen blanks.
It's been doing it a lot today when on a call, I can talk for 30 seconds or so (that's what my screen timeout is set at) and then when the screen blanks, the mobile signal drops to nothing from a full signal.
If I up the screen timeout to 'stay on' then I don't have the problem, so it's definitely something to do with the screen blanking.
I'm running a rooted Desire with RCMixS Ace S 2.36.405.8 WWE Release base, 2.3.3.
Any help would be really appreciated.
Searched rom corresponding thread?
I experienced similar problem when I was on AOSP ROM and flashed Sense RIL. If you did not change the RIL that's included in RCMix I'd recommend flashing the latest radio. This could solve you problem.
I decided to revert my Desire to the stock RUU, and the problem still exists.
At least I can now send it back to HTC, and as it's still within it's first year, I'm not very hopeful that they'll sort out a FOC repair or replacement.
Hi, I was wondering if anybody has come up with a fix for AOSP roms for Bluetooth yet. Sense roms connect to my bluetooth stereo perfectly, but none of the AOSP roms (Cyanogen, ect.) can connect consistently.
The very odd issue is that yesterday I thought I came up with a solution, so I flashed CM7 on and tested. It worked. However I couldn't connect to the market because I forgot to install the gapps addon, so I did, and didn't think twice until last night when going to work, and bluetooth wouldn't work again. It seemed like the gapps addon broke bluetooth, but it could have been some unknown external factor. I can test this later today to see if the gapps addon does in fact kill it somehow.
Can anybody shine light on the bluetooth issues and maybe enlighten me as to a fix if there is one?
Not one response? That's disappointing. I was doing some testing with CM7 today and I could not reproduce the bluetooth breakage that I have experienced every other time. I was trying to isolate what was causing the issue by lashing the rom, then booting, testing, then flashing the RIL, booting, testing, then flashing the gapps package, booting, testing, then re-installing all apps one at a time from titanium backup (the same as I did before) and nothing broke it. Over a full day now and bluetooth is rock solid.
This poses a problem because I don't know WHY it is working. The only variable I actually changed is booting after each thing I flashed. This still will not change issues with any other AOSP roms even if the solution is to flash each separately, because the rest come with gapps installed, and they are broken both before and after a RIL flash.
Also to further convolute things, I started the day testing LeeDroid. Bluetooth would not connect. This is a rom that should have connected just fine.
Hi mrcandyman,
I too have noticed that a lot of AOSP roms have (imho) severe BT problems, mainly with connection to earpieces in my case (voice dialling). I have tried AOSP roms on both my desire and sgs2 and had the same problems on both. Flashing back to rooted stock roms has always cured my problems with BT. I am not a dev or programmer so have no idea what or where the problem lies only that stock roms I've tried don't have BT problems and AOSP do.
feeling your pain,
Night....
Right, I only just started modding my phone - mainly because I thought it would fix this horrible static noise that started when the phones battery died on Saturday morning.
I was running 2.50 firmware with 2.3.3 android on a Vodafone branded DHD.
I have since unbranded the phone and installed a stock 1.32 firmware ROM running 2.2 android.
It then removed the static noise which was fine, I was however not liking the basic ROM so I moved on and installed Cyanogen which again worked fine with no static.
I wasn't too keen on Cyanogen as it missed a lot of songs from my library which is the second reason I have the phone so I thought I'd try CoreDroid but as I have installed that it has reawakened my static sound issue and has upped the firmware baseline.
I can just take it back to stock 1.32 and the sound issue will go, however I am just wondering if anyone would have a reason as to why the issue is there or if I can fix it with some other software/firmware without losing the nice ROM?
Thanks.
Radio issue maybe
I flashed the radio and it didn't make any difference, I am back on 26.03.02.26_M
I did try both 26.13.04.19_M and 26.11.04.21_M and neither made a difference.
I can use the same radio on 1.32 firmware and the static isn't there.
Edit: The static occurs on all sound out of the phone - system noises, music, calls etc...
Right, now gone back to 1.32 firmware and although the sound issue doesn't occur when playing music and in general system sounds, the sound is still there when making calls which I didn't notice before.
Phone could well be shagged.
I am just asking if anyone has seen or heard this issue before? I have some googling around "static noise" "fuzzy noise" etc but not managed to pull anything up.
I was due a new phone anyway but was planning on going on a cheaper phone deal but it looks like I will have another expensive contract. Really weird.
Most probably a hardware issue.......
Sent from my HTC Desire HD using xda premium
Hi,
Can anyone please verify whether their built in FM Radio randomly stops by itself after having it on for 40-50 mins plus? When I say 'stops' the radio broadcast stops, but the app itself is still on and at this point to get it back you have to turn the Radio app off and back on again. If you try to scan to another channel the screen just displays 'Scanning' but nothing ever happens and then I cannot even turn off the app - at this point you have to reboot the phone; even killing it from the task manager does not get it back.
I never had this prior the current software (1.29.401.11 - Stock ROM) but then again I am not sure if I did listen to the radio longer then 50 mins before....
Things I have tried are resetting the phone and also rooting and installing Android Revolutions but the problem is still there. I have now gone back to Stock ROM in case I need to send it back (however I did unlock the bootloader so might not even get HTC to honor the warranty at this stage and if that happens I am just going to sell it and get a GS3 - despite that I prefer HTC over Samsung).
So any replies will be of great help to decide how to move forward.
Thank you.
J
This is because of multitasking "feature" that HOX got from HTC. process is getting killed after some time, i got this same problem in my HOX.
Report it to tech support, so maybe they will fix it in next update.
Adam
Thanks for that - yup that seems about right - I did not realise the HTC multi-tasking feature would even come into play since the phone is plugged into a power source when the radio would cut off. I have now had it on continously for over 80 mins - how? Well, every so often I would go into the application so I guess the phone doesn't get a chance to see it as an idle process and kill it off!
I haven't noticed this feature doing the same with their music app so I am guessing they have some level of control over it - quite annoying that they don't treat the FM radio the same way as their music app...HTC quietly (not) so brilliant