Related
I have an HTC HD2 and I'm on T-mobile. What I've noticed is that my phone doesn't ring sometimes and then I'll just get a voicemail notification (if voicemail was left). It's an intermittent issue, I've tested it several times from another line.
Does anybody know what the issue is? I did a search on Google and there seems to be a lot of the same issues others are having across other networks and other versions of the HTC but, haven't found a solution.
Thanks
i had never heard of this issue until yesterday, when my phone simply did not ring, then i got a txt asking why i didnt answer. very confusing. only seemed to happen once. i have done a lot of tweaks, so maybe ive changed something i shouldnt have. if it helps im using a generic, unbraded, factory unlocked HD2, with CleanEX DsE 3.5 and radio 2.11. have you tried re-flashing the ROM and seeing if that helps?
interestingly, i have noticed that my signal can be irratic at times, often just dropping for no reason, then coming back about 30 seconds later. i live in a full signal area, so i know thats not a problem. also my data connection will 'freeze' at times, where it shows its connected, but nothing is able to use it, i have to disconnect and reconnect, and this may take 2 or 3 attempts before it connects and is usable. have you experienced the same issues?
matthewharmon102 said:
i had never heard of this issue until yesterday, when my phone simply did not ring, then i got a txt asking why i didnt answer. very confusing. only seemed to happen once. i have done a lot of tweaks, so maybe ive changed something i shouldnt have. if it helps im using a generic, unbraded, factory unlocked HD2, with CleanEX DsE 3.5 and radio 2.11. have you tried re-flashing the ROM and seeing if that helps?
interestingly, i have noticed that my signal can be irratic at times, often just dropping for no reason, then coming back about 30 seconds later. i live in a full signal area, so i know thats not a problem. also my data connection will 'freeze' at times, where it shows its connected, but nothing is able to use it, i have to disconnect and reconnect, and this may take 2 or 3 attempts before it connects and is usable. have you experienced the same issues?
Click to expand...
Click to collapse
I haven't tried flashing the ROM, I've been hesitant on doing that since I feel like I might mess something up. I'm not sure how to either. I have SPB backup, so I would hope if I messed something up then I would be able to easily restore it.
I haven't really noticed any dropping, my call qualities have been good. I've tried to dial a number before and it might drop right then while it's trying to make the call. So, I'll redial the number but, once I'm connected I haven't noticed any issues with calls dropping.
Data connection has been working pretty good as well, I've been using the wifi quite a bit and not really had any issues. I don't have a data plan setup with T-Mobile so I just use the wifi. I don't know if using the actual data connection would give different results than using the wifi.
flashing a rom is really easy it's all autoinstall, just have to read carefully / look at the video's, there A LOT of them out there.
HectiQ said:
flashing a rom is really easy it's all autoinstall, just have to read carefully / look at the video's, there A LOT of them out there.
Click to expand...
Click to collapse
updating the rom may help, as it will also update the radio drivers. what i would suggest, if you dont have much experience in flashing a ROM is to have a look on the official HTC support site. on there it will give you a list of updates avalible for your phone. download the latest ROM for your phone (for me, this is WWE 1.66 with radio 2.06) and install that. any data on an sd card will remain intacted, but sync you phone with outlook and backup stuff like contacts, messages etc before you do it. i personally use microsoft myphone to do all that.
flashing the ROM with an official one is very straight forward, and as quoted above, its all auto install on the phone, and there are about 3 or 4 steps that you need to do PC side (this is all explained in the update program you download). i would give that a go and see if things improve, you will also gain improved performance, new features and better battery life with newer ROMs, so its worth doing
custom roms are a bit more tricky to install, but often offer more features and improvements over stock roms. if you need help with this have a search on the forums, there are lots of guides and help on how to flash with a custom rom
matthewharmon102 said:
updating the rom may help, as it will also update the radio drivers. what i would suggest, if you dont have much experience in flashing a ROM is to have a look on the official HTC support site. on there it will give you a list of updates avalible for your phone. download the latest ROM for your phone (for me, this is WWE 1.66 with radio 2.06) and install that. any data on an sd card will remain intacted, but sync you phone with outlook and backup stuff like contacts, messages etc before you do it. i personally use microsoft myphone to do all that.
flashing the ROM with an official one is very straight forward, and as quoted above, its all auto install on the phone, and there are about 3 or 4 steps that you need to do PC side (this is all explained in the update program you download). i would give that a go and see if things improve, you will also gain improved performance, new features and better battery life with newer ROMs, so its worth doing
custom roms are a bit more tricky to install, but often offer more features and improvements over stock roms. if you need help with this have a search on the forums, there are lots of guides and help on how to flash with a custom rom
Click to expand...
Click to collapse
I have a T-Mobile HTC HD2 (U.S.) and I went to the HTC site and on the download page for the ROM update it has ROM Version: 1.66.707.1. When I check the ROM version on my phone it is: 2.10.531.1.1 (82076) WWE
Also it says on there - Note: This update is not intended for use on T-Mobile(US) HTC HD2, and doing so may have undesired side effects.
So, I suppose I'll have to start looking into the custom ROM's.
ubaidabcd said:
I have a T-Mobile HTC HD2 (U.S.) and I went to the HTC site and on the download page for the ROM update it has ROM Version: 1.66.707.1. When I check the ROM version on my phone it is: 2.10.531.1.1 (82076) WWE
Also it says on there - Note: This update is not intended for use on T-Mobile(US) HTC HD2, and doing so may have undesired side effects.
So, I suppose I'll have to start looking into the custom ROM's.
Click to expand...
Click to collapse
good job you didnt flash that, the 'undesired side effect' of flashing that official rom (or any other non tmous official rom) on your tmous phone would have been a permanently dead phone.
im not sure about tmous roms, maybe have a look on the t-mobile us support site and see if anything is listed there. if you want to look at custom roms the first thing you will need to do is get hspl (the latest version is hspl3, which i believe is compatible with tmous). if you search on the forums you can find the official thread. this removes the security checks and allows you to install custom roms. after that you will need to choose a radio version. again search on the forum and find the latest one compatible with your hd2 (there is an official radio thread which i would look at). this normally comes with an updater program included, but if not, search for 'custom ruu' and follow the instructions on the thread. finally you need to pick a custom rom. there are literally 100s to choose from, with different features, looks, apps and even some android builds. personally, i use cleanex dse because of its speed and stability. im not sure if this is tmous compatible, so check on the rom threads.
alternativly, you could have a hardware fault with your phone, which will be repaired under warrenty, so you could go down this route. personally, i would do this first and see if things improve, as although custom roms can be uninstalled and the steps can be reversed, the warrenty is voided by using hspl and installing custom roms.
still have the problem? Might not need a hard reset. Try this solution here:
(LINK)
One of your programs might have deleted the "Volatile" folder, so
no Volatile folder => no WMPlayer => no MP3 playback => no ringtone.
Re-creating an empty "\Application Data\Volatile" folder usually brings it all back.
If it fixes the problem temporarily and recurs again, you might have to change the temp folder as outlined in the link above, or just install that CAB.
Hope this helps. If this solves your problem, please edit/add [solved] to your title.
atlaswing said:
still have the problem? Might not need a hard reset. Try this solution here:
(LINK)
One of your programs might have deleted the "Volatile" folder, so
no Volatile folder => no WMPlayer => no MP3 playback => no ringtone.
Re-creating an empty "\Application Data\Volatile" folder usually brings it all back.
If it fixes the problem temporarily and recurs again, you might have to change the temp folder as outlined in the link above, or just install that CAB.
Hope this helps. If this solves your problem, please edit/add [solved] to your title.
Click to expand...
Click to collapse
I did what u said and installed the cab but still the same problem. Doesn't ring sometimes
Plz if anyone had this problem and knows how to solve it, I'll be so thankful if you help me. It has been irritating me for a month :S
Same here...and its flooded in the net....still no solution..check this out and if anything comes to you...do pls let me know...
http://forum.xda-developers.com/showthread.php?t=850280
I have the same problem. Sometimes incoming call does't ring, altough the phone vibrates. I'm using an european HD2 with the original 1.48 rom. I didn't found the reason... the changed tweak... the influencing application installed. It seems happening randomly, I can get a call without incoming call ring and after a few minutes I can get a second call from the same caller with a normal ring.
Hi all,
I am new to android so please forgive me if i am unclear about my question.
I've also digged for answers but came up with nothing.
Anyway I was hoping someone could help me with the new radio 47.63.35.21U_7.16.35.11.
Ever since i've upgraded to 7.16, i've lost the abilities to:
1. connect to mobile network
2. able to detect and lock on to any satellites.
Downgrading to the original radio didn't solve those issues...
I am currently using Gene Poole's Liberated hfr005b and it's awesome! Battery acting like it should.
My satellite problem is very similar to klbmth in this post
http://forum.xda-developers.com/showpost.php?p=12477387&postcount=25
and as for my mobile network i've tried changing settings as instructed by lateral18 in this post
http://forum.xda-developers.com/showpost.php?p=14117740&postcount=556
i did my hard reset/wipe dalvik/format system before i flashed my aria with hfr005b and the new radio.img...
does anyone have similar problems to my situation??
Thanks in advance!
Do you have an AT&T-branded Aria? If so, I'd suggest running the RUU from here: http://www.megaupload.com/?d=9D9NGT6J
This will restore your phone back to the factory default (including reverting the radio back to the original state).
You can do this without losing any settings by doing this:
1) Make a Nandroid backup.
2) Run the RUU to revert your phone back to factory defaults and (hopefully) fix the radio problem. Important: Do not use the RUU from HTC's website. If you do you won't be able to root afterward. Use the one in the link above.
3) Make sure everything is working again (mobile connection and GPS).
4) Use Unrevoked again to reinstall Clockwork on the phone.
5) Once you have Clockwork installed, do a Nandroid restore. Nandroid does not back up the radio image so you should be back just like you were except with a working radio image.
Also I'd strongly suggest not installing any radio updates in the future.
Hi drumist!
thanks for the quick reply!!!
yes i do have AT&T branded Aria and i'll definitly try out your suggestion.
i flashed the new radio because it was said to "fast lock to sats" and so on... which seemed nice to have
i had no idea it would have such an effect on my aria (when it is fine with everyone else)...
however i was wondering, if not too much trouble, could you please elaborate why updating radio is not a good idea?
mkuo said:
however i was wondering, if not too much trouble, could you please elaborate why updating radio is not a good idea?
Click to expand...
Click to collapse
Well, basically it's one of the few risky things you can install on your phone. When you install a ROM, there's basically no risk involved because even if the installation fails, you can just get back into Clockwork and install another one or try again. There's no risk of permanent damage.
Installing a radio image through Clockworkmod, however, is somewhat risky. Ideally nothing goes wrong and it works fine. However if something DOES go wrong, it's possible to permanently brick your phone in the process.
There's nothing specifically bad about updating the radio -- if it works then it's no big deal. But since it seems like something did go wrong on your phone when you installed the radio, you're lucky that the phone is still working at all.
I doubt you would even notice any difference between the two radio versions anyway. The differences appear to be very minor.
drumist said:
Do you have an AT&T-branded Aria? If so, I'd suggest running the RUU from here: http://www.megaupload.com/?d=9D9NGT6J
Also I'd strongly suggest not installing any radio updates in the future.
Click to expand...
Click to collapse
Having just bricked my phone with messing with radio images, I couldn't agree with you more.
T
thanks for the quick explanation drumist!
and sorry to hear tedkunich's aria was bricked from flashing radio image... that sucks
just to report back:
GPS is working fine again! found sats within seconds and got a few fixes within half a min...
mobile network, on the other hand, isn't... i think it has to do with Gene's ROM... because when i restored a previous backup (fr008) i can connect (WCDAM) right away...
anyway i am more than grateful already... and i'll do more digging on the mobile network issue...
thanks again!
I am in the USA on ATT.
I think the gingerbread radio is the cause of my Slacker radio problems. It didn't do it before. It seems that sometimes when there is a cell tower change Slacker stops and I lose the bluetooth connection to my Ford Sync. Seems to happen at the same places. I want to try another radio. (Pandora does it also; but not as often)
Questions:
1) which radio do you suggest I try (can I go back to Froyo one and if so where may I find it?)
2) I am unlocked/rooted and running a basically stock gingerbread. Do I need to find a flashable zip and use CWM or can I use RSD to flash the radio? (I definitely don't want to hard brick the phone and I keep seeing about not flashing back but I don't think this applies to radios)
Thanks!!
An option:
Personally, I would just deal with it because I wouldn't want to risk my toy...but...
there is an update, albeit, hacked radio that not only should be more reliable, but I've also found to get better reception, and use less battery.
The installation process is described here:
http://www.droidmatters.com/news/breaking-motorola-atrix-4g-gets-hsupa-not-from-att/
It should work for you since I tried it on my gingerbread and it worked, but my gingerbread was not OTA so I don't know what will happen for you.
TRY AT YOUR OWN RISK
Thanks!
The 1.87 was the radio I was looking for. I am a little bit nervous about using rsd to flash the radio (nervous like a bad girl in church but from what I have read it isn't a problem since I am not trying to flash a whole build. Later on when I get my courage up I will try it.
Thanks again,
Ron
update
Flashed the radio to my gingerbread ota (unlocked and rooted) using rsd lite 5.0 and no problems or hard bricking!!! I will try the radio out for awhile and perhaps it will fix my problem. I was on pins and needles while it was rebooting. If I need to go back to the current radio I have a zip that can be installed with cwm..
Thanks again,
Ron
Before you reply - let me lay a story for ya!
I bought a bran new TBolt off of my friend. I was using a fascinate up to that point and never had any issues. I loved my fassy - it was fast, reliable, and everything worked well.
Now onto the TBolt - I got the SOFF, rooted, got recovery, and got a few Roms. It is still working fine. What's the issue?
Well, I posted this on this forum and other forums more than once, but I can never seem to get an answer. After a few ROMS - Infected, Vicious, ThunderShed - I get a splash screen, or if it does boot it freezes as soon as it accesses the radio components. I have CM7.1 on it right now, ran liquid, vicious miui and other roms. Most roms do work in fact without any problems - but the few that I heard are amazing - do not.
What I have done:
Made sure my recovery is upgraded: I have tried latest CWM, EXT, CWM Touch, and the other one that was popular - all updated and did not work.
Always make sure to wipe: I always format all partitions. I have even used the Superwipe script as well, but to no avail.
I have installed a stock rom, wiped and then installed: Someone said that would work - it did not.
Double, no - triple checked my roms': Checked the MD5 sum of all ROMS and Recoveries.
Different Radios: My phone came with newest radios, and I downgraded, upgraded, and nothing.
Now, I do not mean to sound picky - but I am not happy with the TBolt at all. It works at half the quality that I had from my fassy. Wifi errors out sometime, Tether errors out sometime, it lags some of the time, and most of all - no ICS. Liquid worked well, but the touchscreen wouldn't respond during some games - not that I use it for gaming much anymore - but the idea remains.
It sounds like you are trying all of the right things, so unfortunately I don't really have anything helpful to offer. Just curious though, If you were happier with the fascinate, why stop using it? Did it break?
As far as your issues, I have found CM 7 based ROMs (or any roms not based off of sense builds) to be less reliable and have more "glitches" than sense roms. That certainly could explain some of your gripes with the TB. Have you been able to install any Sense roms other than stock?
I have long since settled on Chingy's gingeritis rom as the most reliable and feature filled, but obviously that opinion differs depending on who you talk to.
To answer your question first: I started using the TBolt because it was 4G and that was important for me at the time (I was a student and had no reliable internet). Things have changed now and I am most likely going to change back sooner than later.
I haven't tried many Sense roms. Which would be the most reliable and recommended?
I know you said you tried downgrading your radios and that your phone came with the newest ones flashed but if you haven't already done so, check this out.
http://forum.xda-developers.com/showthread.php?t=1048128
and here is the radio I've been using with no problems:
gu1dry said:
From the 2.11.605.3 RUU:
CDMA: 1.48.00.0906
md5: c6a5a9eee78e0f33267fa80ced3c49b8
LTE: 0.01.78.0906
md5: 6f33809cf2253c38a3c6bb970f030eee
Click to expand...
Click to collapse
One thing with switching to a AOSP rom from a sense based rom is that you have to use very specific radios. this page will help you find the exact radios you need to use for the rom you are running.
I am running Thundershed 1.6 with these:
http://forum.xda-developers.com/showthread.php?t=1605557
newest leaked radios and they work fine for me.
I use...
I use these with no problems.
Rom: http://forum.xda-developers.com/showthread.php?t=1409703
I use the 605.19 Radios.. http://forum.xda-developers.com/showthread.php?t=1605557
Flashed this kernel.. http://rootzwiki.com/topic/603-kern...minimalistic-kernel-620-6312-camcorder-fixed/
Click the "v6.2.0dev13 - Fixed camcorder again." link at the bottom.
I am running the kernel in "normal" mode.
No issues that I know of but I am still a noob with a post count of 2...
Alright. Thx for the help guys - for the time being I am back to the fascinate, but I will try your suggestions.
One thing I am also trying is the using the "non-semsung" micro sd card in the TBOLT.
I will report back after this weekend with the results.
So my girlfriend's EVO 4G LTE is a bit of.. well, I'm gonna say bastard. I'm not new when it comes to rooting devices but I've never had to deal with one that fought me so much.
I've been through this adventure many times with it, and it gets more complicated each time. Here is what's happened with it so far.
It was stock, and it was terrible. It lagged so much, despite factory resets, that apps like google maps were completely unusable. It got no battery life AT ALL, and was generally freeze-happy and miserable.
So then I s-off'd it and after learning all its quirks, installed recovery and CM 11.2 (I think? It's been a year)
This worked great! For.. a few days. The phone worked, we went on vacation to a roaming area where Sprint had no coverage. We come back, and only the data works, texts and calls do not, and the phone acts like it's not activated. Yay. All attempts to get it activated are met with failure, much to the confusion of the poor sprint person on the line. The phone just will not take, at all. (damn lack of real sim cards..) We tried recovering back to a backup from twrp of the stock firmware but that won't work either? It wouldn't register with sprint even on the backed up version of stock sense. The phone seemed dead at this point. Bricked radio?
So we give up. We bring it to the sprint store, and they do some magic to it, and its back to stock, slow and terrible, but functional. We don't touch it until about three weeks ago.
But, my girlfriend is tired, again, of the terribleness, and asks me to try again. Okay, sure.
I install TWRP again, so far so good. The phone is still S-OFF from last time, which is nice. I go to install CM11.2 from the files used from last time (the MD5 does check out correct) But, the phone complains about not having a new enough bootloader. ???? (So I assume sprint downgraded the bootloader in the process of fixing it. somehow)
I forget the exact numbers, but we can't install CM11.2, only 10. or 10.whatever. the newest 10. Okay, fine. I gather a new set of cyanogen files, gapps, whatever, and flash all of that, so far so good.
This time it works, and stays working! Yay! So I thought.
As it turns out, its on a very old version of android (so old that it goes into a special usb file host mode when usb is plugged in) and more importantly, the camera is TERRIBLE. I've read that the evo 4g lte uses a special ImageSense chip to boost camera performance, and that cyanogen 10 does not support it. I can tell, because the camera is absolutely terrible. The battery life also is terrible, presumably because it lacks optimizations. It had way better battery life on CM11.2 when it worked. Other then that, its working just fine, but the camera is just unacceptable.
So, I want to know what to do from here. I see a few paths.
plan A:
update HBOOT to a newer version to allow the install of CM11.2
(how do I do that? I heard you have to use an RUU, but which RUU? I read that there is some touchscreen driver that is an issue depending on what version you run)
(Once I install the ruu is it business as usual, install twrp and then flash cyanogen like normal? Will it do the crazy not activation thing again? was that a fluke??)
plan B:
update HBOOT, but to a much newer one that allows the install of CM12 or whatever the newer ones are. Presumably updating past the touch screen driver issue and not allowing us to go back to an old version.
(once again, what do I need to do that? Is this advisable? I quite prefer the idea of running a newer version. So if this is the better idea, I will do it.)
I thank you greatly for your help. I'm not used to it being this complicated. I've read a lot of things about this phone and it seems very conflicting at times. I just want to get straightened out.
yeah, it's probably running like crap because the firmware is so out of date.
use this RUU http://forum.xda-developers.com/showthread.php?t=2653730
then re-flash twrp and another ROM if you want (i've been running cm12.1 for MONTHS) but she might be able to survive just like that. only fear would be staying vulnerable to security threats, but you've been living in that house this whole time anyway.
for a good while i was running this stock 4.3 with root and some xposed modules installed to get the cm functionality that i missed. but seriously, run the RUU, let it activate, then go under settings and update profile and PRL, fire up maps/navigation with GPS on so that it gets a good lock and its cache populated, then you should be good from there.
Thank you!
Can I use the same utility that I used to flash twrp (that one-click thing that seems to support a half million phones) or do I need something special? This sounds very easy to do. Almost too easy, given that the story of this phone's life is that the easiest thing I've ever done to it was take it completely apart to replace its battery.
never used the one-click stuff. flashing recovery via fastboot is simple enough.
get the adb tools, here's some easy instructions for that http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
get the latest twrp from here https://dl.twrp.me/jewel/
then follow these directions to flash twrp https://wiki.cyanogenmod.org/w/Install_CM_for_jewel#Installing_a_custom_recovery_using_fastboot
if not installing cm or any other rooted rom (you want to root stock) get supersu from here http://forum.xda-developers.com/showthread.php?t=1538053 and use the twrp installable zip
If you've gone through the trouble to S-Off, then fastboot flash the latest TWRP (3.0.2.0, I believe), which supports the new partition layout (extra 4gig of internal SD space).
From there, flash the official 651.4 developers version, go through the device setup which updates your PRL, then shut it down and reboot to TWRP and flash the latest CM12.1 and a proper gapps package (I use "stock", which is a bit much for some, but I like having everything available to me).
The one thing I do that most don't is to disable zRam and enable swap with my own script I wrote specifically for the external SD I formatted as vFat/ext4/swap.
After doing all this, I do not have the issues you seem to have, and the PRL seems to stay from the last install of stock Sense 5. Even with all the apps I have installed, it's still fairly snappy. Facebook/Messenger, and other memory hogging apps run smooth with no discernable lag, unless there's network issues.
YMMV, but look into using an app like "Ampre" to measure battery life and gauge if the battery is going bad or not.
Outside of that, there's not much left to do with these older devices that hasn't been done already.