Related
Dear xda-developers members,
[skip the first paragraph to avoid useless chitchat]
I usually avoid posting in forums when I can't contribute to the soultion of a problem but rather ask questions. This is mostly due to me feeling stupid years on when I stumble upon my then pressing problems. Anyway:
I'm having problems with my X1, more specifically the GPS receiver. I know users have reported problems before, so I don't seem to be alone after all. Let's start out with a
Description of the problem:
No software I tried so far gets anywhere near to a fix using GPS. Google Maps reports it's searching but won't find anything, Chartcross "GPS Test" hangs on "Starting up GPS", TurboGPS sometimes displays a satellite in the very center and finally there's the "HTC GPS tool" which shows this:
The "satellites" change in rather fast succession. This can't be right, can it? So far I have not gotten any fix at all. This was the case from the very beginning (got it off ebay by the way, said to be used for about 2 months). The HTC Tool as well as TurboGPS echo some seemingly gibberish data ("$GPGSV,4,1,16,32,,,,31,,,,30,,,,29,,,*70" and counting down, less often "$GPVTG,,T,,M,,N,,K,N*2C" and things like that).
What I tried so far:
I tried multiple ROMs (R2A stock, R1A stock, 6.5 based, 6.1 based, very light ones, very heavy ones), basically all available Radio ROMs and yes, I switched off AGPS, I tried activating Bluetooth, not touching the backside as proposed by some, etc. It appears to be the X1a Version of the phone, if that is any help. COM-Ports have been switched, windows management of the device has been checked and unchecked, the baud rate has been changed to multiple values. Nothing.
I'd gladly supply you with any further information that might by useful. I think I don't need to stress how excruciatingly annoying this behaviour is. Exchanging the device is not really an option since a) I'll be in Canada in 17 days and I doubt my local dealer could fix this in the given time frame and b) I don't have the receipt - ebay, you see.
Best regards in hope of a solution...
do you try inside or outside ?
gps's generaly never get a signal inside
Nice one, but believe me, I tried outside. I tried on roofs. I tried in the streets. I tried with loads of free sky above my head. My stand alone GPS reciever (Garmin Geko 201) picks up many (at least 5) satellites in less than one minute.
@Tikurion
"The HTC Tool as well as TurboGPS echo some seemingly gibberish data ("$GPGSV,4,1,16,32,,,,31,,,,30,,,,29,,,*70" and counting down, less often "$GPVTG,,T,,M,,N,,K,N*2C" and things like that)"
Not gibberish actually, but NMEA GPS data flows, so your receiver is aquiring some data. Google NMEA if you want to understand these data sentences better.
No fix ? I have only 2 suggestions here;
1) try on hard reset with no AGPS (of course), updated QuickGPS data and a clear outdoors "line of sight"
2) the more recent radio ROM's (eg 1.11.25.76 or 1.14.25.55) do give very quick and accurate fixes if conditions in 1) above are there
ianl8888: I said seemingly, right ? What I meant was: I know it's not actually gibberish. But how do you explain me receiving the exact same values even if I'm in a cellar with absolutely no possibility of receiving anything?
I will yet again try another hard reset, although this then would be number... 15 I believe XD. AGPS is turned off already and radio rom is 1.14.25.55 at the moment. We'll see.
Thank you so far of course. Your help's always invaluable .
I dunno if it helps or not, but i had a similar problem. I found that no software could actually get a gps signal from the unit...it was like the software wasn't actually able to control/turn on the gps or something. the weird thing was that i noticed the "on the road" panel was able to get data. So, i tried running TT6 with the on the road panel running, and it worked. so then i launched google with on the road panel working, and it worked. to this day, if i want to run a gps dependent software, i must start on the road panel first. kind of weird but it works. I'm waiting for R3 to see if the problem goes away or not.
Ian
I tried what ianl8888 suggested multiple times - to no avail.
Also completelyhis: Thanks, but the On-the-Road Panel doesn't pick up anything either. Won't change status after "Determining current location".
tikurion said:
I tried what ianl8888 suggested multiple times - to no avail.
Click to expand...
Click to collapse
Looks like warranty time - seems your GPS antenna may be disconnected (poor or dry solder joint) ??
Unhappily, a not all that infrequent issue with PDA's. I once spent several weeks figuring out how to dis-assemble an Eten X500, re-solder the offending joint and then re-assemble the thing. It was way out of warranty, of course.
my problem with touch HD is similar... all sats bunched on top..
i went for servicing
Well, after temporarily bricking my X1 (tried to reinstall original SPL for service the wrong way) and solving that by using the Service Updater-thingie I sent to support, hoping they will be nice with me, despite not sending the warranty card or the receipt.
Use A-GPS .. for me it even worked inside my house... ( no my house is not a box of 50cm by 50cm.. but one big farm
something that has been bugging me a bit lately is that when it comes to downloading or anything other than general phone calls, my phone signal does not seem to be as strong as it used to be.
i used to get H all the time for my phone signal. then i went to a different rom and it changed to 3G. (which i think is normal?)
but now it mostly seems to be sitting on just G.
the only things that have changed has been the rom (currently using enomther's the official), the recovery (ra's 1.2.1 or something) and the spl (1.33.2004 engineering).
i thought the signal would be affected more by changes to the radio. is that right? or does the rom and the spl also have an affect?
no comments?
I really don't know, and maybe other members don't know, hence the no comments.
If it's sitting on G, did you check if the "Always use 2G Networks" is enabled? But you could also take a look inside the framework (unzip it) of the rom and check what icons they have. Perhaps there is that slight possibility that they don't have icons for 3G! I don't know! (I highly doubt that would help though lol) I think radio has an effect on things like GPS but yeah. Not too sure about the reception but to be honest, I dont think a rom affects reception.
I would recommend a speed test though!
I have noticed that my HTC Touch HD consistently shows heights incorrectly - about 50m too high where I live. After some research I have identified that the NMEA message GGA contains 0 in field 11 (Geoid separation) which should contain the difference between the ellipsoid height and mean sea level height. In my Mio A701 this field contains 50.5, which explains the 50m error on the HTC.
Despite searching this forum I have been unable to find any reports of this problem. Has anyone else experienced it?
What gps chipset does the HTC Touch HD use? My copy of Sirftech does not work on it, so perhaps it is not the Sirf ?
Is there any way to correct this error?
Thanks for any information
Edit
The problem has been solved thanks to the GpsModDriver which performs this correction (amongst other things), and which can be found at http://forum.xda-developers.com/showthread.php?t=571266.
rpettipher said:
What gps chipset does the HTC Touch HD use? My copy of Sirftech does not work on it, so perhaps it is not the Sirf ?
Is there any way to correct this error?
Click to expand...
Click to collapse
It uses the Qualcomm GPSone receiver, this isn't a discrete component as a SiRF chip would be, but is integrated into the 7201A chipset
Sounds like you need to try to flash a few different radios.
GPS height error
Thanks for the information about the chipset.
Because of that I found a small program (MyGPS) which is largely based on an MS SDK demonstration, and that gives the correct height !!
As I understand it, please correct me if I am wrong, that program uses the MS SDK primitives to get information from the GPS without going through the NMEA messages (?). If it can get the correct answer then the GPS must be working, but the NMEA messages, and the programs using them (ozi explorer, visualgps ...) are wrong.
It would be very helpful if someone could confirm that they do see non-zero values in field 11 of the GGA NMEA message (between the two Ms) on an HTC Touch HD.
(One easy way to see the messages is to use the log feature of visualgps).
Thanks for your help
Actually, I noticed it, and I programmed a soft-coded separation correction into the program GPSVP: http://code.google.com/p/gpsvp/
Not many chipsets have the separation. To date, I had none in my hands, other than when using a 'real' garmin connected via a cable to my PC.
Additionally, I have encountered no program that does the correction, other than gpsVP, in which I programmed that myself. I shall check that MyGPS, if it is correct, but I am sceptical, I do not believe that MS would strip the info from the chipset, nor do I believe MS has a softcoded correction.
I guess I could write some sort of serial loopback to insert the logic into other programs, but I am far to busy.
EDIT: just so you know: I only programmed this very small part into gpsVP, the rest is done by others.
GPS height error
Thanks for the reply cybermaus, unfortunately I am not sure what you are saying.
What did you notice ? Zero in field 11 of the GGA message?
Are you suggesting that most chipsets put 0 in field 11?
This is certainly not the case with my Mio A701 with the Sirftech chip, which puts 50.5 into that field and gives me accurate altitude values.
It seems (I am still learning) that there are two ways to get the information from the gps, either parsing the NMEA messages or using the MS API.
In my case it seems that the first way fails and the second works.
Which does your program use, and how have you made the correction?
Thanks (in advance) for your patience with these questions.
Well, yes, I am saying that the devices I encountered, all gave 0 in that field, except actual Garmin handhelds connected by serial. Also, I learned from reading in the internet, that many other people noticed the same. But that does not mean there are none. I believe any real Sirf III will do it correct, but I have a Sirf II dongle witch also does it wrong.
It even turns out there are a few devices, that put 0 in that field, but already subtract the correct separation from the geoid height, so you should not correct the value yourself.
The geoid separation is stable, and well known, you can look up the value for every coordinate on the internet. Also it varies only with a few meters per degree in the steepest places. The steepest separation is west of the mountains range of Peru. The biggest separation is a 100 mtr hole in the sea south of India.
What I did was program a hardcoded matrix with 10 degree resolution (to keep it small) with the correct geoid separation value. The program than takes your coordinates, and *interpolates* these in the matrix, to find your separation. I found it will yield the correct value within 1.5 mtrs, which is well within the GPS precision.
Also, if my program finds there is already a separation value in the field, it will *not* apply the correction, because it knows the chipset behaves properly.
If you want more details, browse the source to gpsVP. Unfortunately, you will not be able to use it for other programs if you are not a programmer or do not have access to the source of those other programs.
As I said, if I have some time, I will check out the MS API you mentioned, there is indeed a new API data structure in WM 6.1 and above, I played with it, but I did not check it for this parameter specifically. However, I am skeptical. I find it more likely the programmer from MyGPS did something similar as myself.
As to your Mio A701. Good. I said I did not encounter any other than the dedicated GPS handhelds from Garmin, but that does not mean there are none. To be quite honest, I only held 5 or so non-Garmins, so who knows.
I think the problem is not widely recognized because most people use GPS in 2D, for navigation. This 3D is more for people doing hiking, with programs like gpsVP or Ozi. Pilots and paragliders may have a 3D GPS, but know better than using it for altitude (I am a paraglider myself)
BTW: Ozi also does not correct the value, I checked.
GPS height error
Thanks again for the comprehensive reply.
I am surprised that you say that most GPSs give incorrect altitudes due to the missing geoid separation field, since I have seen a lot of discussion about this problem, mostly several years old, so I assumed that any modern chipset would have it sorted. I am also surprised that no-one with an HTC Touch HD (for instance) has complained about it.
Do you have an HTC Touch HD, and are therefore confirming that this model is faulty? That is - the NMEA message GGA field 9 gives height above ellipsoid and field 11 is 0.
I would still appreciate input from any other HTC Touch HD owner on the values in these fields.
As you say, and as I have seen, ozi explorer does not do a manual correction in the way you do. It does not need to when the NMEA messages are correct since field 9 is specified to contain height above MSL.
It does, however, have an option to subtract the geoid separation field from the value in field 9 to correct for the (other faulty) case where field 9 contains the height above ellipsoid and field 11 gives the geoid separation. If I use this option on the HTC it changes nothing, since field 11 is 0, but on the Mio it then gives me heights 50m too low (as would be expected).
I will now try your program.
Well, this not just my program, I only supplied 1% of the code, it just happens to be this particular part.
Anyway, yes, I do have a Touch HD. And yes, I am talking about the GGA message fields. One with altitude according to WGS84 ellipsoid, and one with the separation of said ellipsoid from the actual geoid according to the '96 model. Probably indeed fields 9 and 11, though I have not looked at the code for a few months, but it sounds about right.
Your MIO has a real Sirf III chipset. I would have expect that to work, because my Garmin also has a Sirf III in it. But as stated, I have a dongle with Sirf II, and that did not have the correction. Neither did the other dongles I have, but granted, they are all a bit aged and budget quality. Maybe my experiences are a non representative sample
But I confirm the Touch HD is faulty, and I suspect other HTC's and many other brands & models with non-dedicated chips. These do not have a real GSM chip, but a generic secondary ARM cpu shared with the GSM radio function and other radio functions like WiFi, UMTS, Bluetooth and probably even FM.
----
The way I understand it, the original GPS specifications did not have the separation specification. In '84, they simply did not realize that a simple mathematical ellipsoid model for earth and earth gravity was so incorrect.
It was only after the launch of the GSM network that they started to realize that there were so many fluctuations in the local gravity of the earth, which causes this effect, that they came up with the new '96 numerical geoid, rather than the mathematical '84 ellipsoid. Or something like that.
Of course, if HTC wanted, they could program the similar correction into the radio chip firmware, it is simple and small code. And it is 14 years after the fact. But I think they simply do not see the need.
----
If you start to use gpsVP, and you go hiking off-road, please note I find it best to use with GARMIN vector maps. I can also downloads Bing and Google raster maps, but those are not good in off-road data, though the satellite view is sometimes nice.
All in all, the program is a bit 'coarse' in its use. If you understand what it does (vector maps and preloaded cache for raster maps), it has value, but you will not be able to impress friends who are used to the smooth Google map application.
GPS height error
Thanks again cybermaus.
I tried the gpsvp program, both in the htc and the Mio. On both machines I got a correct altitude and a value of 51 for the geoid separation field, which compares well with the 50.5 which appears in the GGA messages on the Mio, so it looks as if your calculation works well.
I tried changing the value of the Geoid separation parameter in the setup options, trying auto, always and never, and in all cases got exactly the same results for altitude and geoid separation, so I am a bit puzzled. Does the setup option change anything, or does one have to do something else to activate it?
Well, the setup part of it is not complete yet, I think it is essentially always auto. Need to find the time and motivation to complete the coding. Log a case in the gpsVP website please.
I do not have much to contribute, but yes, living in Switzerland and hiking in the mountains I have also noticed that the altitude was wrong.
I first thought it was the inherent imprecision of the GPS, but then remarked that it was systematically off by several tens of meters.
I was also surprised that nobody complained, now I know that I am not alone.
I wish that programs like Ozi could apply the correction, or at least allow entering a fixed offset.
Thanks to cybermaus for explaining it.
Will give a try at gpspv.
GPS height error
Thanks marder.
Could you try running visualgps with the log activated, then look at the log file for the message $GPGGA? If the 11th field, between the two Ms, is always 0 then it proves the point.
I remain very surprised at the lack of complaints about this, if it is such a common problem.
But why would people complain? Or even notice?
The height error is absolute, but in differential measurements, it still works well. In other words, if you have a height, and you walk up a hill, it will give you a higher height (most of the time, and within margin of error). And most people are not aware of their absolute altitude anyway. Lets face it, if you live in Moscow, and the device tells you you are at 200mtrs, why would you distrust it?
I only noticed because I live at sea-level (Holland). You only noticed because you live in an area with above average separation, and got annoyed with two devices giving you 2 different values. And marder probably scratched his head when encountering these "xxxx above sea" markers which you get when hicking in the mountains. He would not encounter such markers in the city he lives.
Face it, if you had not had you Mio, would you have noticed? Or be able to confirm it?
Of course, once we know, we think it is unacceptable. Thats human nature, myself included.
But there are other people who did see it. Searching for keywords geoid and gps shows this thread, and the program appears also to have a fixed geoid position.
Like I said before, did you try different radios? As this affects the functions of the GPS. I had this problem too but flashing to the latest radio cleared it right up, along with making the gps now lock on with a strong signal within 8 seconds. Going through the complicated route of coding things to fix it is a bit pointless when others have fixed it before you. I'm not saying it will definitely clear it up for you, but taking 20mins to try a few radios is probably worth your time.
Oh and a good way to tell if it's accurate or not, for anyone else wondering, is to check on google earth for the "elevation".
GPS height error
cybermaus, I expect you are right - people do not notice.
I certainly did notice, independently of the Mio, by comparing the heights marked beside the autoroute that I use with those displayed by the HTC.
But you are right in that without the experience of the Mio I might well have assumed that it was due to some inherent inaccuracy in the GPS system and not searched further (and not found the thread at http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=10915 where this is all explained).
stuntdouble, thanks for the input. I assume that flashing new radios is trivial for you, but somewhat more traumatic for people like me, aware that a problem during the process can end with a dead phone. Could you perhaps tell me
1. Does it actually correct the problem i.e. does the NMEA message $GPGGA give a non-zero value in field 11?
2. Do I lose all my programs and data in the process
3. Which of these many radios do you recommend
4. Where do I find it/them
5. Are you sure it will work on my phone (which is apparently of Malaysian origin)?
6. What is the procedure?
Sorry for the interrogation but this is not as easy for me as it is for you.
For information I have:
ROM version 1.18.707.3 (23358) WWE
ROM date 12/10/08
Radio version 1.09.25.14
Protocol version 52.49a.25.26U
rpettipher said:
stuntdouble, thanks for the input. I assume that flashing new radios is trivial for you, but somewhat more traumatic for people like me, aware that a problem during the process can end with a dead phone. Could you perhaps tell me
1. Does it actually correct the problem i.e. does the NMEA message $GPGGA give a non-zero value in field 11?
2. Do I lose all my programs and data in the process
3. Which of these many radios do you recommend
4. Where do I find it/them
5. Are you sure it will work on my phone (which is apparently of Malaysian origin)?
6. What is the procedure?
Sorry for the interrogation but this is not as easy for me as it is for you.
Click to expand...
Click to collapse
1. Yes. All seemingly corrected.
2. No programs are touched as long as it's a successful flash. Radio is separate from the rest of the device's memory. Just backup your device with Sprite Backup or SPB Backup before you try it, in case you do need to do a hard reset. This way you can get your device back to exactly the way it was before.
3. The one in my sig fixed mine. However every device is different so you would need to find the best radio for your own device. I'd start with the latest and work backwards though if I were you.
4. Get them here.
5. If it doesn't work, it doesn't work. You can always re-flash your old radio if you wish. However I suggest you ask in the radio thread before trying, which radio would be best for your operator. There will be plenty of people who will know this and have tried it before you have I'm sure. The radio info is based on your operator and not on country of origin for the phone.
6. Easy procedure is in link above.
I'm not guaranteeing this will fix your problem, but it really is easy to do and well worth attempting as like I said it fixed it easily for me. It also increased battery life dramatically, and the faster gps fix like I mentioned before.
I understand that it may seem difficult on first read. I felt that way too when I first tried it. But it really is very simple and I was wondering what I was scared of after I tried it. Just follow the instructions in that thread carefully and there won't be any problems. If you use windows vista/7 then make sure you run as admin if you are flashing via the pc. Good luck.
Sorry guys.
I have followed most of the radio updates, and never noticed this being fixed. I have to admit, I never checked since I updated to 1.17 radio, so I checked just now, and it still reports 0 meters separation and at 43 meters altitude (at the coastline of Holland...) So for clarity, I logged out the NMEA messages, and all $GPGGA mssages give 43.5,M,0,M for field 9 through 12. On the latest 1.17 radio.
While theoretically possible they fix it in the radio, it still has not been done, not even at 1.17. I guess you either have the luck of living in a region where geoid and ellipsoid are very close to each other, and/or you are not aware of your true absolute altitude.
GPS height error
Thanks guys now I am confused.
I suppose we need to know what "seemingly corrected" means.
Has stuntdouble actually seen the NMEA messages with the correct data?
Rom update
I do not know about taking "20mins to try a few radios" - I have spent several times that amount just reading some of the information relating to flashing!!
But then I am a slow reader.
Following the links I eventually found what is apparently the 1.17 radio rom on a support page of the HTC site.
I am puzzled to see that it is described as for South Africa only, and concerned to see that it says it is only for ROM version less than or equal to 1.14.421.5. when my ROM is 1.18.707.3.
Should I be concerned and should I also be concerned about the caution when starting the program that it will destroy all the information on my phone?
Just being cautious, especially as I do not know what improvements if any I will see.
My phone(s) are both Telstra HD2's that I've SPL'd and flashed with the standard WWE ROM from HTC as well as the latest Artemis ROM's. This behavior happens regardless of ROM.
Here's what happens: When the phone is linked via Bluetooth to either a PhoneLabs Dock-N-Talk or Xlink Bluetooth phone gateway, the HD2's will occasionally Freeze/Lock-Up after a call is ended. The lock-up is so profound that the only way to revive the phone is to remove the battery, re-insert it, and turn the phone back on.
No matter what buttons are pressed, the screen shows only the call in progress display, frozen and no amount of pressing or tapping revives the phone. At first I thought it was a PhoneLabs Dock-N-Talk issue, so I bought an Xlink box which performs the same function as the Dock-N-Talk. As expected, the phone still occasionally locks up with The Xlink box same as the Dock-N-Talk.
Unlike other lock-up threads, the problem is NOT that the phone "locks" itself but rather that the phone Freezes/Locks-Up like a crashed Windows computer. The only difference is that instead of the ever popular "blue screen of death", I have the call in progress screen, frozen on the LCD.
Both HD2's are doing the same thing so I'm fairly convinced it's not just a defective phone unless it is an endemic issue to this design.
I'd appreciate any suggestions from anyone with experience with such a problem.
Thanks
what kind of radio do you have on your phone sir, and can you give your rom version as well. What you might want to try is going down to a rom base of 2.07 or something as well as radio, you might not like the performance but some radios are very incompatible with some bluetooth sets.
Also another idea is running Andriod and seeing if it occurs under that environment, this could tell you some ideas of what the cause is since both OS us the same radio file.
Luckych
Possible Resolution
I may have stumbled on a possible resolution to my problem.
Since I was not convinced it was a Radio/ROM issue, I re-flashed the HD2 with a fresh task 29 and 045 Artemis ROM. What I did NOT do this time is add any applications like memory cleaner, CHT, etc. which appear to work fine by themselves but I strongly suspect that all of them combined are a great toxic soup recipe.
As suspected, no crashes yet in the last 24 hours. Little by little I will be adding them one at a time to see which one is the offender but I strongly suspect it may be one that is related to a tweak that's gone rogue.
I will post results as I discover tem.
I dualboot android SD (Jaguarlani) and WP7. I hadnt used WP7 for a month now, and i've got an old 7740 rom of YUKI Back to the future. Now, while I was on, the phone started shedding battery life and getting hot. Within 40 minutes of minimal use it had used up 20% of the battery.
I'm using a 2.12 radio ( the recomennded one) and booting via magldr, Which rom should I flash to eliminate this issue And i've tried most fixes, which do not work.
I've got an europeian HD2 from italy.
I really like wp7, I really do, but I cannot use it with such horrible battery life, even SD android had 8 hours of fairly heavy use battery life. I imagine running it properly off nand will increase that.
Mine gets fairly hot and used battery like crazy when I watched videos or listen to music for an extended period of time as well.
However, I've been running DFT UltraFruit, for my daily phone, since it came out and my battery life has really improved.. 10-13 hours normal use, and it doesn't get as hot as it used too.
I'm in the US on t-mobile, using the most current radio... I'm not sure how much help that is, but that's my experience.
It's not that kind of issue, It gets extremely hot (think 50 to 60 C) when idling or using the internet for less then 10 minutes.
The thing is that the only place it gets hot is the 3g modem( I think ) which leads me to think that the issue is software - based.
keller112 said:
It's not that kind of issue, It gets extremely hot (think 50 to 60 C) when idling or using the internet for less then 10 minutes.
The thing is that the only place it gets hot is the 3g modem( I think ) which leads me to think that the issue is software - based.
Click to expand...
Click to collapse
60c would burn your hand, if you can hold it, then it isnt that hot, if its down the bottom then it could also be wifi, all the gubbins are down that way
give ultrafruit a try, there is a huge difference in battery life, meaning that something isnt drawing as much power.
It might also be worth considering changing your radios, hard and soft, dispite common believe a newer radio doesnt mean a better one, usually carriers change radios based on their local settings in that market, so settings that might be good for one person might be terrible for another.
a very basic and over simplified, incorrect and generally a bit shoddy example might be that in your area the network is setup with settings that means your phone is trying double time to keep a connection, where as the same settings on my phone in my location might mean the phone doesnt need to try so hard because of my networks settings.... does that make sense?
dazza9075 said:
60c would burn your hand, if you can hold it, then it isnt that hot, if its down the bottom then it could also be wifi, all the gubbins are down that way
give ultrafruit a try, there is a huge difference in battery life, meaning that something isnt drawing as much power.
It might also be worth considering changing your radios, hard and soft, dispite common believe a newer radio doesnt mean a better one, usually carriers change radios based on their local settings in that market, so settings that might be good for one person might be terrible for another.
a very basic and over simplified, incorrect and generally a bit shoddy example might be that in your area the network is setup with settings that means your phone is trying double time to keep a connection, where as the same settings on my phone in my location might mean the phone doesnt need to try so hard because of my networks settings.... does that make sense?
Click to expand...
Click to collapse
I will definetly try this new ultrafruit. How would I go about changing the soft radios though? The hard radio works really well on android and consumes barely any power, so I doubt that's the issue, I'm thinking more of a WP7-centric problem which points to softradio.
Other then that I do not have wi-fi on and I disabled 3g too, it still gets hot, and I wasnt exaggarating too much, it's in the range of barely being touchable, I would compare it to touching a hot-water run radiator that's been turned all the way up.
I live in bulgaria, and that's probably the core of the issue. However I have never switched softradios before, could you give me general directions, please?
keller112 said:
I will definetly try this new ultrafruit. How would I go about changing the soft radios though? The hard radio works really well on android and consumes barely any power, so I doubt that's the issue, I'm thinking more of a WP7-centric problem which points to softradio.
Other then that I do not have wi-fi on and I disabled 3g too, it still gets hot, and I wasnt exaggarating too much, it's in the range of barely being touchable, I would compare it to touching a hot-water run radiator that's been turned all the way up.
I live in bulgaria, and that's probably the core of the issue. However I have never switched softradios before, could you give me general directions, please?
Click to expand...
Click to collapse
The software radio seems to be an invention of WP7, or at least thats the first we knew of it
The down side is you cant just flash a new radio like you can do with a hardware radio (Tri colour bootloader>plug in PC> install using the custom RRU)
To change the software radio you need to flash it with the initial ROM, meaning you can only change it when you wipe the whole device.
If you download a WP7 ROM, and then look at the files you will see a data.zip file. In that you will see a whole bunch of part files, the one you want is part 0
delete it within winrar, then add the part 0 from a different radio to the data.zip, using winrar again.
give me a few min and ill find you a list of all the radios
edit
http://www.multiupload.co.uk/BT6BI9FFDP
dazza9075 said:
The software radio seems to be an invention of WP7, or at least thats the first we knew of it
The down side is you cant just flash a new radio like you can do with a hardware radio (Tri colour bootloader>plug in PC> install using the custom RRU)
To change the software radio you need to flash it with the initial ROM, meaning you can only change it when you wipe the whole device.
If you download a WP7 ROM, and then look at the files you will see a data.zip file. In that you will see a whole bunch of part files, the one you want is part 0
delete it within winrar, then add the part 0 from a different radio to the data.zip, using winrar again.
give me a few min and ill find you a list of all the radios
edit
http://www.multiupload.co.uk/BT6BI9FFDP
Click to expand...
Click to collapse
That link is barely alive, only rapidshare has it still up, thanks for the guidelines.
Haha, Yuki made it....his been gone awhile lol
Sent from my HD7 using XDA Windows Phone 7 App
Same issue
Please, I need help too,
My phone is getting hot since a while.
This after I fully charged my battery.
:S Any hack infos?
Alright, got pdaimatejam's rom up and running, so far the battery life is good so far, gonna play a movie (akira) when it finishes transcoding (._.)
Any MKV or avi drivers for WP7?
So far though, with the 5.71 radio I havent gotten online, meaning no internet. Phone is functioning though.
Am I going to need to reflash again with an older radio?
Update: this rom is freaking sweet, battery is really really stable!
Update 2: Radio is using 3g networks without providing internet connection, the battery drain is still faster then android, but it's within 1 hour. Other then that the screen and sensors dont draw as much power so it's pretty decent right now.