Related
Ok, the longer the Test-Radio ROM 1.58.25.14 is around, the more people seem to suffer Bluetooth and/or FM-Radio hardware failures.
I know it's very unlikely to be connected, but what if it might is? What if, for example, the test Radio diverts too much power to the respective units and thus actively destroys them over time?
I don't even know if this is possible, I have no idea at all what a buggy Radio ROM could cause. But I want to know if there is a certain correlation and that's why I set up this poll to see how many people are affected. I try to find out if it might be a coincidence and all the defects are actually caused by weak hardware used by HTC. However, please vote in the respective category. Condition: please do not vote, if you don't use or only rarely use Bluetooth or FM-Radio, I only want votes of people which actively use Bluetooth or the FM-Radio every day and thus are seriously affected (or not).
If your unit breaks down after you voted, post a message in this thread, explaining how the situation changed for you.
Thanks
Maybe I don't answer your question as you request it but I can say following:
1. 1.58.25.14 is radio ROM this is true but it is radio rom for GSM only (as well I can understand).
2. I use bluetooth on my Polaris nearly all the time (4-12 hours a day) with headset and laptop.
3. I do not use FM receiver so can't tell anything.
my polaris stopped working after i´ve upgraded the radio rom to the 1.58.25.14 then i come back to the 1.58.25.14 but the message BT hardware problem apears....
andreyamaguti said:
my polaris stopped working after i´ve upgraded the radio rom to the 1.58.25.14 then i come back to the 1.58.25.14 but the message BT hardware problem apears....
Click to expand...
Click to collapse
like me !
Some details
I've got both units broken.
The FM-Radio had a weird behavior before getting broken:
Sometimes, when I started the FM-Radio application, it didn't tune in a single station. I was able to solve this apparent hang tapping "Scan _Save" in the context menu on the right. When it fineshed scanning, the radio appeared to be re-started and everything was smooth. It worked a few times, and I thought it was only a bug of the application itself related only to software.
As I said, it suddenly stopped working, and my workaround was also useless. At the same time, I noticed the bluetooth unit didn't respond as well. The device "tries" to activate the BT for a few seconds, and finally it remains off. Today, I observed a very strange thing: the blue LED that blinks when BT is on, was blinking like if the BT unit was turned on, but... it was not activated!
Since this afternoon, I didn't see the blue LED blinking again. Of course, the BT wasn't actually working, only the LED.
I have contacted the technical support to repair it...
*bump*
I'm on bepes .66 now with standard shipped Radio and Bluetooth is still working fine. I do have the switch-on glitch though: out of no reason Bluetooth obviously gets turned on as the the blue LED blinks for like half a minute during the boot phase. After the boot its turned off though and all is fine.
What do you mean with hardware failures? Not working, error messages, bad receiption...?
So far I didn't encounter any problems (bluetooth + radio with stock rom). I didn't vote cause I don't use it regulary. Only thing I can say is that radio receiption isn't as good as that of the Siemens SX1. I noticed it when I travelled by train. With the Polaris I couldn't listen to radio anymore.
Keep in mind that this poll's results will be skewed b/c ppl that don't have an issue with either Bluetooth or FM Radio are unlikely to even open this thread.
I have the same problem with bluetooth and radiofm.
I have original rom, radiofm stopped to find station and BT stopped to work.
when I click on bluetooth in the commManager appears the loading wheel and after few seconds go back to the off position!
I tried to hardreset, but is the same
ermeneleutico said:
I have the same problem with bluetooth and radiofm.
I have original rom, radiofm stopped to find station and BT stopped to work.
when I click on bluetooth in the commManager appears the loading wheel and after few seconds go back to the off position!
I tried to hardreset, but is the same
Click to expand...
Click to collapse
This is just the same that happens with my device!! I'm waiting for the repairing service to return it to me for the second time. They give you a report with the description of the problem they might find. I will tell you which problem they say...
I bet it is a hardware problem :S
Well more and more people seem to suffer FM-Radio and Bluetooth breakdowns. I gave up believing its any Radio ROM, it seems to be poor quality components. Qualcomm, what did you guys do...?! Psh...
Definetly seems to be crappy hardware. Check my thread about upgrading radio roms:
Reception Difficulties
I agree, there isn't a definable trend so it does point to a hardware issue. I haven't had any reception or bluetooth issues but now my camera doesn't work properly... plus add that to the poor build quality of this unit (rattling keys, sticky sounding screen, loose scroll pad, poor SD card cover and a double clicking d-pad), it's not what you'd expect from a 500€ device.
SuperJMN said:
This is just the same that happens with my device!! I'm waiting for the repairing service to return it to me for the second time. They give you a report with the description of the problem they might find. I will tell you which problem they say...
I bet it is a hardware problem :S
Click to expand...
Click to collapse
thank you!
do you think it's a good idea flash the rom? maybe there is a problem in the rom after some installation (gprs monitor? netframe?).
I would try but I don't want to come back again to the original rom for the repairing service.
some notes:
1) after the second hardreset for a while the bluetooth was working, then I restart the device and the BT was off!
2) with an hard reset not everithing is deleted, some information still in the memory (gprs monitor data, bluetooth device associated...)
SuperJMN said:
This is just the same that happens with my device!! I'm waiting for the repairing service to return it to me for the second time. They give you a report with the description of the problem they might find. I will tell you which problem they say...
I bet it is a hardware problem :S
Click to expand...
Click to collapse
thank you!
do you think it's a good idea flash the rom? maybe there is a problem in the rom after some installation (gprs monitor? netframe?).
I would try but I don't want to come back again to the original rom for the repairing service.
some notes:
1) after the second hardreset for a while the bluetooth was working, then I restart the device and the BT was off!
2) with an hard reset not everithing is deleted, some information still in the memory (gprs monitor data, bluetooth device associated...)
Hi everybody !
My Radio FM doesn't provide any sound anymore
I had a SFR's polaris and I flashed it with all the recents ROM : bepe, radio, etc...
MP3 are working great, radio found some stations, head-phones are plugged, but I can't hear something.
What's wrong ?
Do I re-flashed with any ROM ?
The Polaris-Radio is crap, it's of a very bad quality. Is it just the sound volume then? There is a thread somewhere which is supposed to contain a fix for volume/sound issues on french ROMs...
I posed the patch for volume of MP3.
My Radio FM haven't a bad sound, but no sound.
It's very hard, because I don't know what to do : reflashing from the start (bepe, ...) or try to find a radio fm cab, to try to re-install it
An idea is to flash another language version. For example, just for curiosity, flash udK's WM6.1 ROM in English (http://forum.xda-developers.com/showthread.php?t=386862) and test the fm radio... it could be that the volume limitation got baked in in all french ROM editions...
If it doesnt work on that ROM either, I dont know what to do and at that point I suppose sending it in for repair wouldnt be the worst thing to do...
I wonder how many returns they´ve had with this device??? It´s a real shame cause when everything works well it´s the best thing out there
Hi All,
I have a very strange uncommon problem with my Touch P3450 (Elf).
Everyday, I go to work using the same route. At two or three specific locations on the way, my phone become unresponsive (windows 4 color circle, 100% CPU) during 1 or 2 minutes.
During this time, everything is frozen (no way to interact with the phone, no music if I was listening to, and so on ..)
If I close every bit of custom programs installed on the phone (including today screen), I got the same problem.
If I toggle the radio off, then everything works and got no problem.
So, this problem is clearly related to the radio and happens when the cellid changes from one to another specific one that will cause these trouble.
Does anyone have any Idea on what's going on with this ?
Is this a known problem with my Radio version (03.07.90) ? (though I don't remember I had the problem at the beginnings)
How can I trace the problem ?
Is there any Radio Registry tweaks that may help ?
Thanks a lot for you help.
Thomas
HTC 3450 Elf
Original unbranded ROM
ROM Version 2.20.406.1B FRE
ROM Date 10/02/07
Radio version 03.07.90
Protocol 4.1.13.51
I am huge fan of Dutty's ROM. Had v 1.7 1.9 2.1 2.3 and 2.6. Everything was always working smoothly and nice.
Last weekend I updated to V3 and then where wi-fi problem started.
It is like this right now:
When I set to Best Battery or to a "middle" position, the wi-fi basically does not work AT ALL. When I switch to Best Performance the wi-fi works but like 30% of speed and quality of previous versions.
At first I thought it was the radio rom, which during long process of updating in accordance to THIS guide took downgraded to 1.09.something. So I updated the radio to the newest 1.14.something but the problem is still the same.
Everything else works great but wi-fi works like 30% of its power;( WHAT IS WRONG? Has anyone experienced it before?
Of course I could try use Best Performance but then battery is sucked like crazy!;(
Thank you for help!
Cant help on your issue but mine works great on Duttys new rom
IrfanSEAT said:
Cant help on your issue but mine works great on Duttys new rom
Click to expand...
Click to collapse
glad to hear this ,dude but rather looking for someone who has the same problem
I dont have this issue either. Perhaps a hard reset might be your best option
ASK768 said:
I dont have this issue either. Perhaps a hard reset might be your best option
Click to expand...
Click to collapse
you think? I did HR after the rom update.... One is not enough these days?
OK, will give it a try...
i didnt do any hardreset and its working fine
reflashed, double HR and.... it helped
I still have NO IDEA what was the cause firstplace.
Thanks for help!
I didn't try this ROM yet. But, I'd like to have a try on Dutty's ROM! I will report if I will have caught this problem in the future. Sorry, cannot help you this time.
And why don't you report this at Dutty thread instead opening a new one????
I am using Dutty's V3 Rom and has no problem with the WiFi issue as stated.
More WiFi Fixes & Problems ?!!
Please excuse me if this is the wrong place to post this, but whenever I hear WiFi problem my ears perk up.
I have been experencing WiFi connectivity problems for while now; my HD would try to connect to an AP and after a ltte while of watching the "connecting" animation, the device would just quit with a warning message that it could not connect with the current settings..bla.bla.bla... even after it had connected to the same hotspot afew hours before.
Well, after installing Dutty's V2.9 (Highly recommended!) ROM the WiFi issues disappeared for 5 days. Mind you with my HD this is a record usually WiFi only works for a whole day at most, so I am guessing anyone experiencing problems with WiFi and Dutty's ROMS has a problem that might not be related to the ROM itself, as in my case the ROM actually "fixed" the problem, if only for a while.
By the way, I have just flashed the new (1.14) radio and the WiFi problem still persists;nevertheless I will keep testing anithing new that comes along and posting my results here.
I was celebrating too soon(((
After double HR I had to reset once more - had issuescwith ActiveSync.
Anyway I HR once again and the problem back again. The wifi actually does not work at all or work very slowly
Since not only me experience this problem I guess it is not the radio problem but the rom itself.
What is even more strange, I was able to resolve it once because it already worked one... the problem is I don't remember what EXACTLY I did to restore perfect wifi functionality.(
Sorry this is a bit off topic but where do I find the best battery setting, I have had a look under setting->power bu can only adjust the backlight.
Thanks
Sully
Have you tried upgrading to newer SPL ?
I have recently upgraded from 1.14 SPL to 1.56 HSPL and from 1.19.XX rom to 1.56.405.1(HTC official ROM UK WWE) - what is more imp here is there is also an radio update in this RUU - i guess from 1.09.XX to 1.13.25.24. Hope this solves your problem.
Keep posting your progress
Hi, I love Android on my HD2. But everytime I install a new build, the same problem is occouring everytime. And I hope that when I install a new ROM the problem will go away, this is not the case.
the problem is this, when I put the phone in lock for a short or long period of time, the phone freezes, and I have to remove the battery and restart in order to get it working again. Now, I have been trying Gingerbread, but the problem still occoured.
I am using NAND to install BTW. Also, I was told to use SETCPU to fix this issue, and set the dropbox to 'smartass' I have done this, and the problem does not go away.
Any ideas? If you can find a solution I will give you loads of thanks!
I sometimes have a slight freeze upon waking phone and cant slide unlocker but its only for a few seconds and fine after that.
Try task29 and then reflash magdlr/rom etc see if it helps in your situation.
Also what apps are you installing each time you install rom, Something may be causing issue on your phone.
The problem is not that the touch screen frozen, but that the phone will not wake, sometimes it has the blinking green LED at the top of the device.
Thanks.
TheATHEiST said:
Also what apps are you installing each time you install rom, Something may be causing issue on your phone.
Click to expand...
Click to collapse
I install TypoClock And SetCPU. Also, some marketplace apps like quadrant and advanced taskiller.
Bumpety-bump-bump.
Anyone have a solution?
D:
i take it you've also upgraded your radio version as well? when i first fiddled around with android i had the famous sod or sleep of death..wherein the device wouldn't wake up. i ugraded the radio to 2.15 and that fixed the problem. haven't had a freeze ever since.
I have the same problem. Dose any one have a solution for it?
I dose have a solution, as stated before, upgrade your radio.
Ya sounds like an outdated radio. Upgrade to 2.12.50 or 2.15.50
Robson said:
i take it you've also upgraded your radio version as well? when i first fiddled around with android i had the famous sod or sleep of death..wherein the device wouldn't wake up. i ugraded the radio to 2.15 and that fixed the problem. haven't had a freeze ever since.
Click to expand...
Click to collapse
Thanks
Upgrade the radio. It worked for me
Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you
mohammedmazher said:
Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you
Click to expand...
Click to collapse
I am facing this only when battery is bellow 15%. If this is the case then just charge it before it goes to 15%.
If that's not the case then you can try installl MAGLDR v1.3
Do you have this issue in Froyo or Gingerbread ROMs? or in both? What version of CWM are you using?
I have the same problem on MIUI since after approximately 1.3.18 (cutover from Froyo to Gingerbread). Also have this problem on CME DHD2 Compact.
It is also an issue if someone tries to call me.
Sometimes, if I try waking the phone from sleep (power button) and it hits the black screen, and I wait long enough, it will wake. But again, the only real fix I know is pulling the battery.
I am running MAGLDR 1.13
Also, another fix that works sometimes is plugging in the phone into a power source e.g. laptop USB port
It's something about light sensor, when you put your screen into a strong light it would be turn "unblack" again. I don't know how to fix it, is this a problem with this hardware because it's broken or my version of LEO doesn't support NAND full functionaly.
Begging for answer!
i know about my poor english
I have this problem too.. running latest Hyperdroid rom by pongster (magdlr version) and it's driving me crazy. Sometimes phone wakes up normally after a call like it shoud, sometimes is stuck with black screen for few minutes, hours even (although i can't wait that long so i pull out battery)..
Back on WinMo everything worked normally, so it's not an hardware issue with proximity/light/whatever sensors
Is there any fix out yet? I googled and searched this forum a lot and haven't found nothing much helpful, ony a couple of threads with bunch of people with same problem like me. An option for disableing those sensors would be just as good, i've tried few apps for keeping the screen awake and none of them actually worked..
Any help is appreciated.. thanks in advance.
Bump!
Anyone? :/
I have the same issue - running Gingerbread, MAGLDR 1.13
Very annoying cause everything else works super.
Temporary solution i use is to use headset / handsfree. Then there is no problem.
So experts on XDA, we are begging for a fix for this!
I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127
I have had the same thing happen to me but only around 2 or 3 times in a about 3 months of usage. Had it on both CM7 and MIUI Gingerbread ROMs regardless of battery percentage.
MAGLDR 1.13
Some users experience this using SetCPU
if you have a profile for screenoff and it's set to the lowest frequency, try to set the frequency to something above 500 MHz.
If you have smartass set as governor, then even setting the frequency to it's highest (without OC) during screenoff wouldn't change anything in battery performance, but the device will wake up faster.
Your setup works for me as well - until we`ll see a fix for it this will do
Quiethinker said:
I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127
Click to expand...
Click to collapse
Yup, this worked for my setup to - thanks!
hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?
xanthrax said:
hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?
Click to expand...
Click to collapse
(install then enable each one):
Click to expand...
Click to collapse
Incearca Sanity app, cauta pe Market, mie aceste doua nu mo ajutat
with me is so but only if I navigation (Navigon) and to have someone call me and then left the screen black and I can not make
try to change the kernel. that works for me
hey guys! i found the solution goin through the market!
download an app called "Sanity" theres a free version in the regular android market.
go to the settings > general > check "Reverse Proximity" (This will give you some warning about not using it if you DONT have a buggy proximity sensor). Check it anyways. Then go back to preferences then click "Proximity" scroll down and uncheck Turn off screen and leave leave the Turn on screen checked. this will force your phone to stay on during calls so that it never has to go through the proximity phase of calls this no more black screens. Hope this was helpful ^_^
Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .
papaganz said:
Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .
Click to expand...
Click to collapse
I also try with WinMobile and the problem was still there ...
I think the sensor is broken ....
I will bring my phone to service ... and when i take it back I will tell you whether it is repaired
Solution
I had the same problem with Android roms on my HD2. I saw in an other thread a member (z-o-r-r-o-, thanks btw) wrote "just clean dust on the screen, where sensor is situated". This looked like a joke to me, but it's not. On a review of the phone I found the place of the proximity sensor. This is on the top of your screen next to the speaker, on the left if you look at the screen. I just took off the protection layer of the screen and cleand the sensor and the problem was solved. So I cut of a bit from the protection layer so that the sensors arn't touched by anything.
I think the problem is that this sensor is much more sensitive with android roms.
Hope this works for you to.