Related
When I turn on Bluetooth on XDA IIs, I got this error message :
"The bluetooth radio radio failed to turn on due to insufficient driver memory available. You must perform a normal reset before you can turn on the bluetooth radio."
Anyone can advise how to resolve this ? Soft reset does not cure the problem. Thanks.
have you upgraded to bluetooth stack version 3900 ???
if you have then im fresh outta ideas, if you havent find this at our FTP site,
ftp://xda-developers.com/
login and password = xda
got the same problem when i installed one of the bluetooth upgrades on its own. then i installed the new rom and everything was fine. not sure where the connection is but thought id share my problem
Problem solved.
By the way, what is the latest version of ROM for XDA2s, and where to get it from ?
Thanks.
So I was wrong.
After upgrading the BT upgrade, things was OK yesterday. But this morning i got the same error again.
Went to ftp://xda-developers.com/ as suggested, can anyone mentioned the filename of the ROM mentioned by thakkergaurav above ?
Thanks.
The latest ROM is 1.40
You can find it here: http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel
Hmmm..... :?
This BT issue is really getting to be NOT FUNNY! :evil:
Running the new ROM 1.40 and BT 3900 I'm now getting the "no sound" problem on the handset and caller cannot hear me on a HS801!
I use the turn on/turn off BT trick or soft re-set and the handset is OK for a couple of hours but the HS801 still does not work even though its OK with my old PocketPC,a nokia and a Motorola V3!
Is there any consistancy with this problem? It seems the different ROMs, Radio Stacks and BT versions are being effected.
Well, emailed the tech support, and all they can say was ...
"There is a ROM upgrade in development which is in the final stages.
We request your patience as we are trying to release the upgrade as soon as possible."
And that was 2 weeks ago.
even my bluetooth is upgraded to 3900,
i get the same error message also..
i cannot believe a 96mb memory is still not enough
i never get this kinda nonsense when i was using the 5450 ipaq
my today plugins was all over the screen and I had never encountered low memory...
I had the same problem but I have a Harrier not a BA so I thought it was related to that and you BA guys wouldn't get it.
Anyway, the solution on the harrier was to
-turn flight mode on
-soft reset
-turn bluetooth on
-turn flight mode off
Hope this helps
Here is a possible solution from wiki:
The ExSenetoR wrote:
Delete Run_BTTrayCE_10.lnk from your Windows\Startup folder and soft reset. Now you wont have the BT icon on the tray bar, but you wont have the no sound problem. If you still need bluetooth you can start it from the Windows directory as BTTrayCE.lnk.
Have fun.
Click to expand...
Click to collapse
Have not tried this myself, but I believe others have had success with it. You may want to save the file somewhere else, in case you want to reinstate it later...
Hope this helps
Chris
I posted this in another thread.
It really does look like a combo of the 1.40 ROM and 1.12 Radio Stack that is causing this problem (in this case, anyway. See sig). After trolling various forums, it seems that both BT build 3900 and 3500 are having the same issues.
IMHO it seems that the Blue Angel is trying to send the call to my HS801 even when BT is not activated.
Has anyone had a good look at the current radio stack? I've tried contacting Broadcom (BT chipset supplier) but it has been 3 weeks with no answer.
I've done the Run_BTTrayCE_10.lnk workaround but this is only a bandaid and I don't really have enough experience to attempt to cook the ROM. Any ideas?
I have a Motorola HS801 as well and I can receive calls just fine but when I make calls the other party can't hear me. I'm giving up on the HS801 - it's a cheapie anyway and I don't know of anyone else who's got it working either. Running BT3900
Hi all,
I just received my HTC s620 last week. I tried is to install Route 66 that came with it.
The application quits after selecting the appropriate map. I found out that Route 66 does work when I hard-reset the phone and install it. Then it works.
But when I turn on my GPS-receiver (Fortuna Clip-On) and then start the application it hangs. The only thing I can do is turn the phone off and on.
I already tried the latest patch/update, but nothing works. I've contacted Route 66 but I haven't heard anything et.
Can anyone help?
Thanks a lot!
Bugs74
i am using route66 with no problems. maybe try re-installing and contacting your supplier. have u tried overclocikng your dash . it may halp.
cudo
How do I overclock my device? And can overclocking destroy the device?
hi, as far as i know it is not 'dangerous' if you are over clocking within certin levels. 230 i guess is ok and it really makes a difference.
go to this website http://surrealnetworks.com/mpx/DashApps.htm
and download PowerControl+OMAP. there are instructions there
and report back !
cudo
I know I'm bringing up an old thread, but I'm having the same issue with my route 66 and I can't figure out what is wrong with it. After a few days of using it, it will just begin to quit as soon as it opens. I can't uninstall and reinstall it, because it will do the same thing. The ONLY thing that seems to work is a hard reset, which is not a viable solution. At first I thought it may be a memory issue but it doesn't launch with 21-22megs free even after a soft reset.
And yes I am running OMAP+ Power Control now just to see if that would help but no luck. It must be writing to some file or the registry some info that is making it quit each time.
Funkydude are you still in WM5 ?
nope. I'm using WM6.
edit: I think an update to 7.0.3489 may have fixed the problem.
All, I have route 66 working ok with WM6 on my Dash/S620 but initially I had all sorts of problems with the application crashing. Route 66 support will not help as the application is not designed for WM6 (so they told me recently) so it's down to us to sort out issues and find workarounds.
On another forum, I found a thread that suggested that having some/lots of SMS text messages impacted the application. I thought it was rubbish too but after I deleted my SMS messages and the messages in deleted items folder, the app worked ok. I could not believe it but it really has helped.
To use route 66 I make sure I have closed all other apps down using Oxios (or task manager if you don't want to use Oxios) and also delete all SMS. After that, it works fine.
It seems unreal I know but it really did help me out!
Cheers
Jonathan
It's true!!
fudger said:
It seems unreal I know but it really did help me out!
Click to expand...
Click to collapse
Hi all!!
I had trouble with Route66: it didn't start!
But after deleting all my SMS it work!! It's strange, but true!!
I had similar problems. I just uninstalled it and went with the MUCH cheaper and much more stable smart2go. I highly recommend this gps application.
All,
I've just upgraded from WM5 to WM6 with HTC Home RevROM, which is excellent, however, I have this strange issue.
First, I paired my laptop through Internet Sharing over a Bluetooth PAN - works perfectly.
Second, I paired my Jabra BT2020 earpiece.
As soon as the Jabra was paired, the list of devices under Settings->Bluetooth->Devices was empty. Not even the words "Add new device" is present........
I have checked, and I can still continue to use my laptop through Internet Sharing, and I can also use my Jabra earpiece to take phone calls.
Switching the phone off/on and Soft Resets do not solve this problem. Only a hard reset will solve it - but then of course I have to re-enter everything - which I have done, only to have the problem re-occur, hence it is repeatable.
Has anyone else seen this issue and could help me with a solution. I have searched the forum (and Google) to no avail.
Many thanks,
BrianP6
BrianP6 said:
All,
I've just upgraded from WM5 to WM6 with HTC Home RevROM, which is excellent, however, I have this strange issue.
First, I paired my laptop through Internet Sharing over a Bluetooth PAN - works perfectly.
Second, I paired my Jabra BT2020 earpiece.
As soon as the Jabra was paired, the list of devices under Settings->Bluetooth->Devices was empty. Not even the words "Add new device" is present........
I have checked, and I can still continue to use my laptop through Internet Sharing, and I can also use my Jabra earpiece to take phone calls.
Switching the phone off/on and Soft Resets do not solve this problem. Only a hard reset will solve it - but then of course I have to re-enter everything - which I have done, only to have the problem re-occur, hence it is repeatable.
Has anyone else seen this issue and could help me with a solution. I have searched the forum (and Google) to no avail.
Many thanks,
BrianP6
Click to expand...
Click to collapse
Hey man, Unfortunatly this is a bug with my current kitchen, I believe he is using parts of it for making roms. I'm working to fix it soon in my kitchens.
Peace,
Josh
Thanks for the quick reply Josh,
Do you have any ideas at the moment as to the cause? Is it the number of connections, type of connections....... so that I can avoid the bug cropping up.
Also is there a workaround that you're aware of....
oh, and nice work chef
Cheers,
Bri.
BrianP6 said:
Thanks for the quick reply Josh,
Do you have any ideas at the moment as to the cause? Is it the number of connections, type of connections....... so that I can avoid the bug cropping up.
Also is there a workaround that you're aware of....
oh, and nice work chef
Cheers,
Bri.
Click to expand...
Click to collapse
This bug appears only when 2 or more devices get paired.
I've been trying everything, even abusalza himself suggested some module replacement. i'm working on replacing drivers and certain folders in sys in my kitchen but still nothing yet... so far not yet, but it's fixable, i just gotta figure it out.
Thanks Josh,
I guess you'd know this anyway, but for completeness and for the benefit of the whole forum.........
Even though the paired devices are no longer shown in the Bluetooth Devices window, and you can no-longer use your HTC to pair more devices, then so long as you carefully initiate the pairing from the other device, it will be recognised, PINs will be requested and devices configured appropriately. I have just done:
Audi A4 in car kit
Laptop via Internet sharing
Jabra earpiece
None appear on the Devices window, but all (so far) appear to work perfectly.
Cheers,
Brian.
I have had a similar nagging problem with my Motorola S9 and Hermes 100/Cingular 8525. After a new flash, I can pair the headset and the phone relatively easily. During first pairing, I am *not* prompted for the headset's PIN. Over time, switching between phone and music functions becomes more unreliable. Icons disappear while the headset is in use. Discontinuing a call with the headset results in audio resuming through the external speaker instead of the headset, etc.
Eventually, out of the blue, the headset will fail to pair; and I will receive a prompt to enter the PIN number for the headset. I enter the PIN and the phone refuses to accept that it's the correct PIN. From that point on, I'm screwed until I reflash the phone. It never works properly anymore.
This has happened across multiple ROMS, including some of Josh's that I've tried. It happened again the day before yesterday with one of TAI_Sw's ROMS I'm currently using. In this case the profile in Bluetooth settings appeared to be corrupted. The profile no longer read "Motorola S9". Instead it showed a series of block characters (like unsupported fonts). I was able to delete the profile, and, after multiple resets (hard and soft) the phone finally redetected the headset and we went through the configuration wizard again. It's been mostly working well since then.
Has this happened to anyone else?
austinsmartie said:
Has this happened to anyone else?
Click to expand...
Click to collapse
Yep, I have experienced everything you mentioned at one time or another, even the square characters showing up in the device list.
I have gone all the way back to test Faria R32 ROM. It's amongst the best I've found for A2DP with the S9's along with some of PDACorners early ROM's. The drawback are that it doesn't have the 1% battery increase .dll cooked in and also still exhibits the "numbers for character during a call" bug.
It does have nearly 31 MB of memory free after fresh install though. (using 4MB pagepool - default is 6MB)
austinsmartie said:
I have had a similar nagging problem with my Motorola S9 and Hermes 100/Cingular 8525. After a new flash, I can pair the headset and the phone relatively easily. During first pairing, I am *not* prompted for the headset's PIN. Over time, switching between phone and music functions becomes more unreliable. Icons disappear while the headset is in use. Discontinuing a call with the headset results in audio resuming through the external speaker instead of the headset, etc.
Eventually, out of the blue, the headset will fail to pair; and I will receive a prompt to enter the PIN number for the headset. I enter the PIN and the phone refuses to accept that it's the correct PIN. From that point on, I'm screwed until I reflash the phone. It never works properly anymore.
This has happened across multiple ROMS, including some of Josh's that I've tried. It happened again the day before yesterday with one of TAI_Sw's ROMS I'm currently using. In this case the profile in Bluetooth settings appeared to be corrupted. The profile no longer read "Motorola S9". Instead it showed a series of block characters (like unsupported fonts). I was able to delete the profile, and, after multiple resets (hard and soft) the phone finally redetected the headset and we went through the configuration wizard again. It's been mostly working well since then.
Has this happened to anyone else?
Click to expand...
Click to collapse
It frustrated me enough that I started building my own rom!
I released one version here that I have been running for quite some time with no issues in the bluetooth at all.
I need to tweak it a bit more to make it "polished" but it is very useable and stable. I just wanted to run it for a while to see how it is going to act over a longer duration before I continue to fool with it, and I have been rather busy here lately.
Well, if you have a magic potion, please share with the community. And, by the way, this is the only device I pair to my Hermes; so this may be different from the problem Josh and others have described.
joshkoss said:
Hey man, Unfortunatly this is a bug with my current kitchen, I believe he is using parts of it for making roms. I'm working to fix it soon in my kitchens.
Peace,
Josh
Click to expand...
Click to collapse
i just installed your new v15 color(thanks very much for that release it looks great) and i definitely want to pair 2 devices with the phone. this has worked for me in whichever random wm6 rom i found on the web last year and i have been trying to find the right rom for me this week so my question: is this a random bug, is there a trick to doing it right or am i just plain sol?
Hmmm - doesn't happen on my ROMs...
The suspect things I'd be looking at in SYS are:
Bluetooth
Bth_A2DP
Bth_HID
Try replacing those folders with known good ones and see if the problem still happens...
austinsmartie said:
Well, if you have a magic potion, please share with the community. And, by the way, this is the only device I pair to my Hermes; so this may be different from the problem Josh and others have described.
Click to expand...
Click to collapse
No Magic potion! lol
I basically did what CRCinAU described. (His rom doesn't have the issue, and feels a bit faster than mine. But, I was looking to create "My perfect rom").
But I also replaced files in the redist folder with "bt" in their name, with files from a known working rom (anryl's 20755). Like I said I wanted to run the rom for a while, now I just need to go back and tweak and clean up some things in the rom before I make another release.
summary
stickybud said:
i just installed your new v15 color(thanks very much for that release it looks great) and i definitely want to pair 2 devices with the phone. this has worked for me in whichever random wm6 rom i found on the web last year and i have been trying to find the right rom for me this week so my question: is this a random bug, is there a trick to doing it right or am i just plain sol?
Click to expand...
Click to collapse
it is a really odd issue and seems to only affect the hermes... Here is the deal, Some chefs when porting sys grab the cplmain.dll to get the build number and keep some other items in their kitchen sys for stability purposes... I have noticed in my experience when porting, if the cplmain.dll does not match some other components with the same build number it will cause this issue. usually resist, shell, os, folders have been containing these sensitive items. so in short, if the issue is occuring cplmain.dll in redist folder does not match other components in your sys causign the conflict.
edit, and oh. i've tried replacing all bluetooth which had no effect.
So to fix this, the chef needs to report sys correctly and recook the rom.
Ok here's my problem:
I make custom dutch roms for the Rhodium (touch pro 2).
I use the latest XIP/SYS builds (28009 at this moment) and I use manila/sense 2.5
(Almost) everything works great!
I also own a pioneer car-entertainment set (avic f900bt) which has a built in parrot bluetooth carkit.
Pairing goes perfect and I can transfer my phonebook and make calls.
The problem is that when I recieve a call and try to hang up the system hangs and needs a reset. My TP2 also hangs for a while after such an event and then after minutes goes back to the today screen.
At first I thought it was my carkit, but my wife's samsung and my brother in law's blackberry work fine.
Then I tried my own phone with the latest OFFICIAL 6.5 rom (dutch) and it worked great.
So I started to trial and error with different adjusted roms. I got it all working with the newest XIP/SYS builds. But the problem seems to lie somewhere in manila 2.5. I even got it working in manila 2.1 without any bugs
But with 2.5 I get the problems above. And I forgot to mention another bug:
- When I make a call or recieve a call I do not see a 'red phone' button to hang up which I do see with other phone's or roms without manila 2.5. So I have to end a call on my HTC instead of my carkit. And when I try after recieving a call it hangs as described above.
After 2 weeks of flashing and trying I give up...
I use the OEM from the latest official dutch 6.5 rom so those drivers can not be the issue. As stated before...It's all pointing to manila 2.5. But after flashing disabling manila does not fix the problem. So it must be somewhere in the cooking proces (Ervius VK 1.82)
Please one of you supreme chefs help me out here because it's frustrating me now and I want to get it working as it should.
Thanks a milion in advance!!
EDIT: to the mods; I did not know where exactly to post this after the re-organisation. So please move if neccesary.
Almost 170 views and no comments??
Please fellow cooks...I'm desperate...
Well i do think you already have an answer.
But the actual non existing pressure you feel from users that always want the latest no matter how buggy it might be
When MS started to "Leak" builds beyond 20000 (But before 21054).
I also started noticing Bluetooth pairings going haywire and acting differently.
As i don't care that much about what most "Flashers" think and tend to believe that the choices i make concerning cooking a rom are probably more founded in what is right.
I tend to stick to stable OS Builds. It's the New Age XDA dilemma, either dish out unpredictable New Builds, or make a ROM that in the first place Suits you and has the functionality You need.
In this case that would be an older SYS.
I think that also because of TP2 has now switched to different Bluetooth Stack and 2.1+EDR isn't helping.
And it might be that MS is actually working on getting up to speed and changing their own BT Stack, so HTC will not need to turn to WidComm for the BT Stack.
I do believe that there are a few Senior Cheffs and some Non Cheffs do probably know which other parts (besides the Obviously named Bluetooth related SYStem parts), might be related to dealing with Bluetooth Pairing and such.
Whatever solution there might or might not be, don't hesitate to make it hybrid.
Use the old fashioned method of dividing and conquering.
(Get a good supply off Coffee)
Start with Stable Release Build SYS replace 50% test. (leaving all obviously Bluetooth related Packages from Stable Build)
Replace the Next 25% Test etc, you know the drill.
And hopefully isolate the Packages from SYS that have related Files to Bluetooth.
Luckily there's already enough SYS packages you can rule out like enterprise, entertainment, Office and such.
I know it's not a cut and dried answer, but hopefully i can "Je een hart onder de riem steken" that your up against this alone ATM.
But consider this, how many time do you have at hand, and is it worth it putting a lot of time into it, only finding out MS fixes it in a few "Leaked" Beta Builds.
Who knows maybe this Bump does get a few others on to this thread that has already tackled this problem.
(Da_G is the most likely, that i know that might know other Bluetooth dependencies inside the SYS)
Cheerz,
PS: don't forget to enjoy the snow a bit.
Pairing with Avic f900BT
I too have the exact same problems. The phone is straight out of the box.
Any easy ansewrs as yer?
Magic3091 said:
I too have the exact same problems. The phone is straight out of the box.
Any easy ansewrs as yer?
Click to expand...
Click to collapse
I got it working on mine using the attached cab
I have a TP2 which has been good as gold since I bought it about six months ago, but now trying to use GPS for the first time I cannot get a signal. Can anyone please assist?
TomTom 7 and Google Maps; Neither program is complaining that it cannot find GPS, it's just that GPS does not pick up any signal.
Under QuickGPS I've got everything ticked and agreed to! I've also manually updated it three times now.
Under "External GPS" settings I've tried COM4 and COM0 and baud rates 4800 and 9600. I'm now settled with COM4 and baud rate 4800 (with corresponding settings in TomTom) and I can confirm that the GPS device is certainly recognised, because if I change the settings or if I select a different GPS device in TomTom I get "No GPS device!", whereas with correct settings I get "Waiting for a valid GPS signal".
Likewise Google Maps sits for ever showing "Seeking GPS Satelites (0)...".
I've just come back from a day visiting friends in London. For half of the 45-minute journey there I had the phone sitting on the dashboard with TomTom open, and for the second half Google maps, and then the same again for the 45-minute journey home, and not once at any point did I pick up any satellite signal.
Can anyone please offer any suggestions?
Many thanks.
Could possibly be a bad GPS unit in your phone. There is an HTC GPS Tool available on the boards here that you can try and test with. I'll do a search for you in once sec.
One quick thing to double-check, in Settings | System | ABPS Settings > Make sure you've got the AGPS Service turned on.
ETA: Here's the thread where you can download the GPS Tool - http://forum.xda-developers.com/showthread.php?t=360477
I'd be very grateful, thanks.
ABPS Settings? What's that?! I have no such setting under Settings/System! (I'm running WM 6.5 pro)
GPS is new to me, and while clearly a nice little piece of kit the HTC GPS tool doesn't give any instructions! However, I've set it to my COM and baud rate and hit "Open" and there's a lot of action; under the "Satelite" tab I see changing red satellite points (between one and four and I'm still indoors) so I'm presuming this indicates that my GPS is functioning?
Could my issue therefore be something to do with my non-existant ABPS/AGPS Settings?
AidanBell said:
GPS is new to me, and while clearly a nice little piece of kit the HTC GPS tool doesn't give any instructions! However, I've set it to my COM and baud rate and hit "Open" and there's a lot of action; under the "Satelite" tab I see changing red satellite points (between one and four and I'm still indoors) so I'm presuming this indicates that my GPS is functioning?
Could my issue therefore be something to do with my non-existant ABPS/AGPS Settings?
Click to expand...
Click to collapse
"aGPS" = Assisted GPS, it uses more than just the satellite signals to help pinpoint your location quicker. The TP2 is capable of aGPS, but it's disabled by default. You'll need an app such as "Advanced Config" (attached below) to access and activate that setting. Once you have it installed, just open the app, and you'll see a "GPS" heading in the list of options, under that is the aGPS switch.
Much appreciated, thanks. In fact I already have "Advanced Config" installed, and all GPS options already activated, including AGPS.
Could you be so kind as to let me know whether you think, from the description in my last post, that my GPS is working? And if so, might you have any idea why it's therefore not speaking to either TomTom or Google maps?
AidanBell said:
Much appreciated, thanks. In fact I already have "Advanced Config" installed, and all GPS options already activated, including AGPS.
Could you be so kind as to let me know whether you think, from the description in my last post, that my GPS is working? And if so, might you have any idea why it's therefore not speaking to either TomTom or Google maps?
Click to expand...
Click to collapse
Without being able to lay eyeballs on it, it does sound like the GPS tool did indicate that you could at least locate some satellites, but I can't say for sure if you're locking/triangulating any...
There is one more setting that I've read has helped on some odd occassions, it's worth a try if nothing else. In the same GPS settings area where you changed the port and baud rate, the last tab should be "Access". On that tab is only one check box, for "Manage GPS Automatically...", and it's probably checked by default for you. Even though it sounds backwards, go ahead and uncheck that box, and see if it makes any difference in your ability to acquire sats. It may not, but it doesn't hurt anything.
Also...just to be sure...on the "hardware" tab there, do you have the "GPS hardware port" set to "none", yes?
Your other option, of course, is to load a different radio.
have you tried running quick gps?
I have also had problems with my GPS since flashing a new ROM, a reset seems to have sorted it out.
robh810 said:
I have also had problems with my GPS since flashing a new ROM, a reset seems to have sorted it out.
Click to expand...
Click to collapse
I presume you mean a full, cold reset? I've run several standard cleanups and warm resets, and yes, I've also run QuickGPS a number of times as well.
I was beginning to wonder myself whether it was to do with flashing the new ROM, although it was an official ROM (WM 6.5 Pro), Vodafone and Windows certified and downloaded through the Vodafone website, so it should have been thoroughly checked.
AidanBell said:
I presume you mean a full, cold reset? I've run several standard cleanups and warm resets, and yes, I've also run QuickGPS a number of times as well.
I was beginning to wonder myself whether it was to do with flashing the new ROM, although it was an official ROM (WM 6.5 Pro), Vodafone and Windows certified and downloaded through the Vodafone website, so it should have been thoroughly checked.
Click to expand...
Click to collapse
Yes, if you loaded a new official ROM, you most likely got a new radio with that ROM (offical ROMs include the radio, many aftermarket ones don't)...in that case Epoh is correct and you'll want to find out what radio was on your device with the previous ROM, and try flashing that same one (or one of the other available options) in place of whatever one the new ROM included.
Again, many thanks.
But I'm afraid you've lost me technically! I'm certainly PC literate and able to tweak and crack and play, but where my TP2 is concerned my knowledge is more limited. I'm afraid I would need instructions to guide me through the process you suggest. If anyone has the patience and kindness to provide some I'd be most grateful, otherwise it's a bit out of my "do it yourself" league.
AidanBell said:
Again, many thanks.
But I'm afraid you've lost me technically! I'm certainly PC literate and able to tweak and crack and play, but where my TP2 is concerned my knowledge is more limited. I'm afraid I would need instructions to guide me through the process you suggest. If anyone has the patience and kindness to provide some I'd be most grateful, otherwise it's a bit out of my "do it yourself" league.
Click to expand...
Click to collapse
Start > Settings > System > Device Info > Software Info
It will have your radio version there. I'm not sure which ROM you were using before, but you should be able to find what radio it was using. Then go to the ROM development forum and read about flashing your radio!
AidanBell said:
Again, many thanks.
But I'm afraid you've lost me technically! I'm certainly PC literate and able to tweak and crack and play, but where my TP2 is concerned my knowledge is more limited. I'm afraid I would need instructions to guide me through the process you suggest. If anyone has the patience and kindness to provide some I'd be most grateful, otherwise it's a bit out of my "do it yourself" league.
Click to expand...
Click to collapse
Flashing a radio is very similar to flashing a (custom) ROM, it just doesn't wipe everything, and it only replaces the radio (actually the set of drivers for all the radios in the phone). Different radios can improve your reception on any of them (3G, Bluetooth, GPS, etc), but you may have to try a couple to find the one that works best for you.
A list of available radios, and links to detailed instructions, are in THIS thread
Many thanks for the help. OK, I think I'm on the case, but here's what's still confusing me: The thread you've sent me to explains how to determine your ROM by going to the start menu, settings, etc. However what I need to know is what the ROM WAS before I updated to my current one, no? If I understand this correctly I am trying to return to the old radio that I had before I updated the ROM, yes? In which case, how do I know which radio to choose?
If it saves time, I can tell you that I am in England, my unit is a Vodafone HTC TP2, purchased in August last year.
AidanBell said:
Many thanks for the help. OK, I think I'm on the case, but here's what's still confusing me: The thread you've sent me to explains how to determine your ROM by going to the start menu, settings, etc. However what I need to know is what the ROM WAS before I updated to my current one, no? If I understand this correctly I am trying to return to the old radio that I had before I updated the ROM, yes? In which case, how do I know which radio to choose?
If it saves time, I can tell you that I am in England, my unit is a Vodafone HTC TP2, purchased in August last year.
Click to expand...
Click to collapse
Correct, but if it uses the same radio then there is no need to flash a radio and you have a different problem, which is why I suggested checking to see if they use the same radio. If the ROMs use different radios, you can download the radio from your earlier ROM to see if it fixes GPS.
http://wiki.xda-developers.com/index.php?pagename=HTC_Rhodium/Shipped_Roms
I see! Cheers.
OK, my current ROM is 1.86.161.0 (67102) WWE, and radio 4.49.25.17 (09/25/09).
However ... since I have no idea what my ROM or radio were before I updated the ROM, how am I to know whether the radio is the same!?
AidanBell said:
I see! Cheers.
OK, my current ROM is 1.86.161.0 (67102) WWE, and radio 4.49.25.17 (09/25/09).
However ... since I have no idea what my ROM or radio were before I updated the ROM, how am I to know whether the radio is the same!?
Click to expand...
Click to collapse
that link has a list of known ROMs and the Radio they use.
AidanBell said:
I see! Cheers.
OK, my current ROM is 1.86.161.0 (67102) WWE, and radio 4.49.25.17 (09/25/09).
However ... since I have no idea what my ROM or radio were before I updated the ROM, how am I to know whether the radio is the same!?
Click to expand...
Click to collapse
On that list Burton linked for you, it shows that the originial shipped ROMs from Vodaphone (which I'm assuming is what was on yours previously) were version 1.14.161.6 (50207), with radio 3.44.25.27.