Related
HI, I've been reading about the new Alltell update from HTC that was released a few days ago and the forums are buzzing with news of users who have actually gotten GPS to work on their touches.
I've attached here the 3 files needed to run the GPS on our phones but... alas cant tell you HOW to install them or where to install them. I too am looking for advice on how to proceed.
This is what I personally have been waiting for since I purchased my phone 6 months back so if we can get this working on the HTC Touches it would be GREAT.
(I was sick of reading through 30 pages over at PPCgeeks and here to see that no one actually said where to install the files or how to make the GPS antenna work once they are installed)
Google is your friend
Well that comment was contructive and... obvious. Thanks!
This threat was more for people being able to just come here and get the directions they need to active the GPS instead of read through like I said 30 some odd pages of information.
Those are not what you need.
1. Unlock with the new unlocker 2.31
2. Run Alltel update
3. Download the zip file from http://forum.xda-developers.com/showpost.php?p=1516102&postcount=3 and extract contents to your device.
4. Execute the 3 files located inside the newly extracted zip in order (they are named 1, 2, and 3).
5. Download the cab file from http://rapidshare.com/files/109911328/HTC_GPS_Enable_for_Titan_3.35.cab, copy to your device and execute.
6. Soft reset
That's it - you're done and GPS works.
Optionally, you may want to download/install QuickGPS, but Google Maps works without it.
does this work with Sprint devices as well?
Mm.... I just updated using the Alltel ROM, my download speeds are like 1400k and upload is around 120k.. phone seems to be a lot more responsive and battery life is seemingly better... I think I'll wait for an official Alltel GPS update!
Draiko said:
Google is your friend
Click to expand...
Click to collapse
Aaron McCarthy said:
Well that comment was contructive and... obvious. Thanks!
This threat was more for people being able to just come here and get the directions they need to active the GPS instead of read through like I said 30 some odd pages of information.
Click to expand...
Click to collapse
Check me if I am wrong, but I think that thread is for the Alltel ROM being released for the Titan / Mogul, not the Touch / Vogue.
boggsie said:
Check me if I am wrong, but I think that thread is for the Alltel ROM being released for the Titan / Mogul, not the Touch / Vogue.
Click to expand...
Click to collapse
Ok, you're wrong.
The Alltel rom has been released for the Vogue/Touch. It has now been successfully installed on Sprint devices as well with the help of the new 2.31 unlocker by cokeman.
And yes, RevA and GPS now both work on the Vogue just like the Titan!
What about the Verizon xv6900? I haven't heard anything regarding it..everything has been been about sprint/alltel..
Draiko said:
Google is your friend
Click to expand...
Click to collapse
dew.man said:
Ok, you're wrong.
Click to expand...
Click to collapse
I hate it when that happens!
Oh, wait ... I probably wasn't clear. All I was hoping to do is keep folks from following the link from Draiko. When I click on the "Google is your friend" link, it leads to a forum post in the Titan / Mogul thread over at PPCGeeks.
The first post in that thread, includes a link to a ROM, which when downloaded, has the following name:
RUU_TITAN_ALLTEL_WWE_3.35.671.9_RS_TITAN_03.37.20_Alltel_2.01_AM_PPST_Ship.exe
So, while Rev.A and GPS are now working for the Touch / Mougl, I am just trying to point out that the thread in the Titan / Mogul forum, which includes a link to the Titan / Mogul ROM, may not be as helpful as Draiko had intended.
Thanks for checking me dew.man.
Best regards,
-boggsie
Boggsie
This is the link you want for GPS and Rev A on the Touch
http://forum.ppcgeeks.com/showthread.php?t=24925
Not possible?
I have called htc four times seeing as how u sometimes get dif answers from dif reps, and all 4 four told me that the alltel touch did not have the gps HARDWARE in it to even attempt to unlock. They said sprint touch was the only one that had the hardware. 2 reps said alltel requested this just for price. Same thng frm an alltel tech too. The 6800 is the only gps/wifi hardware equipd htc @ alltel? is this true?
t.Kilgore86 said:
I have called htc four times seeing as how u sometimes get dif answers from dif reps, and all 4 four told me that the alltel touch did not have the gps HARDWARE in it to even attempt to unlock. They said sprint touch was the only one that had the hardware. 2 reps said alltel requested this just for price. Same thng frm an alltel tech too. The 6800 is the only gps/wifi hardware equipd htc @ alltel? is this true?
Click to expand...
Click to collapse
NO. They are the exact same hardware except for the casing.
I'm running the CDMA touch from Telus... basically my understanding is its the same thing as any other vogue. That said.. I've been steering clear away from putting any cooked roms or anything on my phone as I dont want to fry it. I thought that maybe all I had to do was bring those 3 files over onto my phone somewhere and then prestro... gps. Right now I connect via bluetooth to a gps receiever and use navigon and tom tom. Has anyone had anyluck using the internal GPS with these programs? I tend to just leave my reciever connected in my truck but for when I am walking around it would definatly be usefull to use the internal antenna.
Thanks!
t.Kilgore86 said:
I have called htc four times seeing as how u sometimes get dif answers from dif reps, and all 4 four told me that the alltel touch did not have the gps HARDWARE in it to even attempt to unlock. They said sprint touch was the only one that had the hardware. 2 reps said alltel requested this just for price. Same thng frm an alltel tech too. The 6800 is the only gps/wifi hardware equipd htc @ alltel? is this true?
Click to expand...
Click to collapse
The Chipset includes the aGPS chip. I think it's actually part of the processor. All the MSM 7500 and 7200 chipsets have the port to add WiFi hardware but it wasn't implemented in any of the Vogues. But all the Vogues, Telus, Sprint, Verizon, and Alltell are the same hardware wise.
now just gotta wait for a 6.1 rom with it all on it damn im picky LOL
Aaron McCarthy said:
I'm running the CDMA touch from Telus... basically my understanding is its the same thing as any other vogue. That said.. I've been steering clear away from putting any cooked roms or anything on my phone as I dont want to fry it. I thought that maybe all I had to do was bring those 3 files over onto my phone somewhere and then prestro... gps. Right now I connect via bluetooth to a gps receiever and use navigon and tom tom. Has anyone had anyluck using the internal GPS with these programs? I tend to just leave my reciever connected in my truck but for when I am walking around it would definatly be usefull to use the internal antenna.
Thanks!
Click to expand...
Click to collapse
You'd need to flash the Alltell rom because it updates your radio... ... ... but hopefully someone will come up with a more graceful option in the future.
guardianfox said:
You'd need to flash the Alltell rom because it updates your radio... ... ... but hopefully someone will come up with a more graceful option in the future.
Click to expand...
Click to collapse
Wouldn't it be somehow possible to extract only the radio update from that rom? Like 'un-cook' it heh
Install that, copy gps files, and that would be a quick solution.
Sprint GPS for Vogue/Touch is now available
http://forum.ppcgeeks.com/showthread.php?t=24979
mcmcghee0519 said:
What about the Verizon xv6900? I haven't heard anything regarding it..everything has been been about sprint/alltel..
Click to expand...
Click to collapse
Yep, just did the Alltell/Sprint update on my Verizon XV6900 this morning and everything works great. RevA, Windows Mobile 6.1, and GPS.
How for is the development for NAND for the Touch pro ? (thinking of buying one tomorrow)
Last time i checked it was no where near ready for end user. Its still being tested and better developed to make flashing easy as flashing a normal winmo rom.
robuser007 said:
How for is the development for NAND for the Touch pro ? (thinking of buying one tomorrow)
Click to expand...
Click to collapse
why would you buy a touch pro when the tilt2/touch pro 2 is already out ?
gmanfuzing said:
why would you buy a touch pro when the tilt2/touch pro 2 is already out ?
Click to expand...
Click to collapse
Becuase I found one on ebay for $45.
babijoee said:
Last time i checked it was no where near ready for end user. Its still being tested and better developed to make flashing easy as flashing a normal winmo rom.
Click to expand...
Click to collapse
If they're looking for testers I'm game. I'm no stranger to all that stuff coming from Vogue.
mrkite38 said:
Becuase I found one on ebay for $45.
Click to expand...
Click to collapse
hmm 45 dollars isn't bad then. Still i wish the tilt 2 was out when i got mine. its what the phone should've been like in the first place seeing as the processor isn't even better.
All nonsense aside, whats the status of nand support?
the0ne.john said:
All nonsense aside, whats the status of nand support?
Click to expand...
Click to collapse
See post #2.
babijoee said:
Last time i checked it was no where near ready for end user. Its still being tested and better developed to make flashing easy as flashing a normal winmo rom.
Click to expand...
Click to collapse
I kind of agree with this statement, there are still a lot of little things to iron out...
With that said, the Vogue also still has some issues to iron out, and there's been a NAND available for that device for quite some time now.
At first I agreed that Android on the TP/Fuze was not anywhere near ready for a NAND. Battery life was a big issue, but with these newest builds I'm getting pretty good uptimes without being tied to a charger. Mind you it's not as good as WinMo, but you can't really expect that considering it's running the OS off of an SD card - which to me seems like another good reason to start building a NAND, Android would probably enjoy much better battery life if it was running natively.
So is something else holding it back? We can calibrate the screen, audio seems to be working fairly consistently... I mean GPS would be nice, but I don't think that feature alone would keep devs from building a NAND. Heck, they still don't have the camera sorted out for the Vogue (although they do have GPS and BT, BT audio doesn't work for them either!)
I'm definitely not trying to be a troll, I'm just curious as to what is preventing a NAND, because I don't think where the Android project is on this device would be so bad for the typical "end-user" we have on these forums.
However, if the issue is actually figuring out the best way to flash a NAND to the device, that's a completely different matter. I was under the impression that the project status was holding it back from being converted to a NAND.
So for what it's worth (I'm sure not much ) I feel Android is ready to be flashed onto our phones. I know I would flash it, I've been using it full-time now for a couple of weeks!
arrrghhh said:
I kind of agree with this statement, there are still a lot of little things to iron out...
With that said, the Vogue also still has some issues to iron out, and there's been a NAND available for that device for quite some time now.
At first I agreed that Android on the TP/Fuze was not anywhere near ready for a NAND. Battery life was a big issue, but with these newest builds I'm getting pretty good uptimes without being tied to a charger. Mind you it's not as good as WinMo, but you can't really expect that considering it's running the OS off of an SD card - which to me seems like another good reason to start building a NAND, Android would probably enjoy much better battery life if it was running natively.
So is something else holding it back? We can calibrate the screen, audio seems to be working fairly consistently... I mean GPS would be nice, but I don't think that feature alone would keep devs from building a NAND. Heck, they still don't have the camera sorted out for the Vogue (although they do have GPS and BT, BT audio doesn't work for them either!)
I'm definitely not trying to be a troll, I'm just curious as to what is preventing a NAND, because I don't think where the Android project is on this device would be so bad for the typical "end-user" we have on these forums.
However, if the issue is actually figuring out the best way to flash a NAND to the device, that's a completely different matter. I was under the impression that the project status was holding it back from being converted to a NAND.
So for what it's worth (I'm sure not much ) I feel Android is ready to be flashed onto our phones. I know I would flash it, I've been using it full-time now for a couple of weeks!
Click to expand...
Click to collapse
Agreed - the only things I 'expect' to work reliably before flashing to nand are calls and data. Everything after that is gravy.
And bt audio works on cupcake and donut for vogue, but not on eclair. And the vogue's camera is just crap, regardless of os.
arrrghhh said:
I kind of agree with this statement, there are still a lot of little things to iron out...
With that said, the Vogue also still has some issues to iron out, and there's been a NAND available for that device for quite some time now.
At first I agreed that Android on the TP/Fuze was not anywhere near ready for a NAND. Battery life was a big issue, but with these newest builds I'm getting pretty good uptimes without being tied to a charger. Mind you it's not as good as WinMo, but you can't really expect that considering it's running the OS off of an SD card - which to me seems like another good reason to start building a NAND, Android would probably enjoy much better battery life if it was running natively.
So is something else holding it back? We can calibrate the screen, audio seems to be working fairly consistently... I mean GPS would be nice, but I don't think that feature alone would keep devs from building a NAND. Heck, they still don't have the camera sorted out for the Vogue (although they do have GPS and BT, BT audio doesn't work for them either!)
I'm definitely not trying to be a troll, I'm just curious as to what is preventing a NAND, because I don't think where the Android project is on this device would be so bad for the typical "end-user" we have on these forums.
However, if the issue is actually figuring out the best way to flash a NAND to the device, that's a completely different matter. I was under the impression that the project status was holding it back from being converted to a NAND.
So for what it's worth (I'm sure not much ) I feel Android is ready to be flashed onto our phones. I know I would flash it, I've been using it full-time now for a couple of weeks!
Click to expand...
Click to collapse
I agree. I've been a full time Android user for the last two and a half months . No complaints here.
any news?¿ will be an android rom some day? or we shouldn´t expect that
There is NAND launcher/support for HTC Kaiser. Is it that hard to port over build one for toouch pro?
volcan123 said:
There is NAND launcher/support for HTC Kaiser. Is it that hard to port over build one for toouch pro?
Click to expand...
Click to collapse
where can i found that?¿
thanks
EDIT: i have found this info:
http://forum.xda-developers.com/showthread.php?t=636024
http://forum.xda-developers.com/showthread.php?t=651861
we can learn from Vogue,it has opened source. http://androidhtc.git.sourceforge.net/git/gitweb-index.cgi
Guys, believe me, WHEN the team wants to make it a ROM for NAND they will do it easily.
So just wait.
up！
I agree. I've been a full time Android user
hope the ROM for NAND，flash it
rayman18 said:
where can i found that?¿
thanks
EDIT: i have found this info:
Click to expand...
Click to collapse
Yup, thats what I am talking about. I wonder if the chefs for XDANDROID know about this?
rayman18 said:
where can i found that?¿
thanks
EDIT: i have found this info:
http://forum.xda-developers.com/showthread.php?t=636024
http://forum.xda-developers.com/showthread.php?t=651861
Click to expand...
Click to collapse
These threads are about how USERS can put an NAND build on their phone..
Okay I'm going to tell you guys this just once.
First the developers have to get everything finished so that we don't need the few bits from WinMo we still do.
Then they can make a NAND build.
And BELIEVE me, they know how to do it. It just won't work at the current state of things.
And the XDAndroid team knows just as much about porting as the Vogue guys. The only difference is that we got more advanced phones and therefor it takes a LOT more time to make a port.
x2 right now the biggest thing is drivers. since there were never any drivers made for the touch pro/fuze for android, none exist.
since none exist, we must use winmo to initalize alot of the hardware that android uses.
once the drivers are sorted out (they are being worked on) and we don't need winmo to initalize everything for android, android can be moved to nand.
I know a lot of you out there are obviously updating to newer, cooked ROMs. This by far is the best bet when spending the kind of money we are on these phones. You get much more out of your new phone than it is capable of doing from the factory or retail store.
I want to instill in everyone's mind how truly important it is to check out the new radios available for the phone. It takes literally 5 minutes or less start to finish to flash a new radio. You won't lose your newly flashed ROM or any settings that I have found. So, please take notice to my advice. Below is the link for all the newly updated radios for our device. Check out a few of them and make some calls, use your gps. I believe you will be much happier with a new radio, because frankly the stock radios are garbage.
My call signal strength is maxed out in my home whereas it only had 2-3 bars before. My gps doesn't lag behind me anymore, and My Location works perfectly since flashing a new radio. So, try one out. It definitely can't hurt. Below is the link to the thread with all of the newer radios. ENJOY!!!
http://forum.xda-developers.com/showthread.php?t=549939
i never knew what the radios purpose was, i had a hunch i was something like what you described here but now that im sure id like to say thank you and ill definitely be changing my radio
outerdepth said:
I know a lot of you out there are obviously updating to newer, cooked ROMs. This by far is the best bet when spending the kind of money we are on these phones. You get much more out of your new phone than it is capable of doing from the factory or retail store.
I want to instill in everyone's mind how truly important it is to check out the new radios available for the phone. It takes literally 5 minutes or less start to finish to flash a new radio. You won't lose your newly flashed ROM or any settings that I have found. So, please take notice to my advice. Below is the link for all the newly updated radios for our device. Check out a few of them and make some calls, use your gps. I believe you will be much happier with a new radio, because frankly the stock radios are garbage.
My call signal strength is maxed out in my home whereas it only had 2-3 bars before. My gps doesn't lag behind me anymore, and My Location works perfectly since flashing a new radio. So, try one out. It definitely can't hurt. Below is the link to the thread with all of the newer radios. ENJOY!!!
http://forum.xda-developers.com/showthread.php?t=549939
Click to expand...
Click to collapse
You're TMO-US, right? Which radio did you use?
sixsevenco said:
You're TMO-US, right? Which radio did you use?
Click to expand...
Click to collapse
He mentioned in another thread that the radio he flashed to is the one ending in .57, and that's the one I'd suggest you start with. I happen to have it already because it's the one that comes with the stock T-mo 6.5 ROM...but if you've running any ROM's with a different radio, you'll want to give this one a shot. A few other T-mo users have reported good results with the .77 radio, but I'd still start with the .57 if you haven't already.
thanks outerdepth...
I have always figured I should update my radio, but never bothered/got around to it. Your post re-motivated me, so I updated from .25 to .77 and...
100% improvement!!
My gps accuracy used to be off by about a city block, which I attributed to the fact that 'oh well its a cel phone, what can I expect', now is accurate within a meter or two.
My data speeds are much improved, and I dunno if its my imagination or not, but calls even seem clearer and have a better sound quality to them.
Dont know about battery drain yet, but its not really important to me cause I'm a truck driver, so I can leave my phone plugged in most of the time in the truck
Thanks!!
So this might be a dumb question but are these radio updates official? They overwrite ROM so I'm kinda always wary to ever try this. I have the official HTC ROM from their website and I assume you can flash it back but I'm not sure.
The ROM will stay, all your contacts/text/etc will stay, and you SHOULD NOT have to worry about losing anything. You can use a program like SPB Back Up or Sprite back up if you are worried though.
Which radio to use on TP2 on Sprint?
Does my location and company plays any part on this issue of the radios?
I have a 6.5 AT&T Rom in Puerto Rico
kbradio said:
Which radio to use on TP2 on Sprint?
Click to expand...
Click to collapse
You want to head over here
http://forum.ppcgeeks.com/showthread.php?t=90342
I switched to VZW 1.88 and it is about the same as the PCS 2.32 in my area but I put a bunch of radios on my SD card in case I travel and have no bars so I can use this method to flash on the go.
EdAmsterdam said:
Does my location and company plays any part on this issue of the radios?
I have a 6.5 AT&T Rom in Puerto Rico
Click to expand...
Click to collapse
The thread about TP2 Radios tells you how to choose the ones that will work for you, just look for the ones that say AT&T and start there.
Furious911 said:
So this might be a dumb question but are these radio updates official? They overwrite ROM so I'm kinda always wary to ever try this. I have the official HTC ROM from their website and I assume you can flash it back but I'm not sure.
Click to expand...
Click to collapse
The radio-roms are "official". However, in order to flash one you have to first do the HardSPL, which isn't official....and may not be completely reversible, depending on what carrier-branded (if any) phone you have.
The only reason this SPL issue may matter is if you have to return for warranty return. If they swap the phone for you in a store then surely nobody in a store will know the difference...but if you have to send it to HTC then non-stock tampering may be evident.
That being said, it hasn't stopped me from taking full benefit of what this site has to offer and make full use of what is possible with my TP2.
Good advice for everyone.
Some of the newer cooked roms require a particular radio...or at least will work best with a particular radio. Before flashing any new rom, read to see if the chef suggests a certain one.
Tanks sirphunkee
Does my phone have to be unlocked to install a new radio as is the case with installing a new ROM?
gotvet said:
Does my phone have to be unlocked to install a new radio as is the case with installing a new ROM?
Click to expand...
Click to collapse
No, the security lock only prevents you from switching carriers. Shouldn't affect the radio.
And in any case the phone doesn't have to be unlocked to install a custom ROM, it has to have a different hard SPL.
There are a few threads on the various Froyo releases, their features bugs etc. but nothing that touches on Froyo's GPS issues specifically.
I'd like to know whether anyone has successfully changed the 'look ahead' behavior that all the Froyo firmwares come with so far.
For those who have not experienced, i.e. not YET noticed this 'feature', here is a brief description:
On Froyo the GPS is showing you exactly where you are even while driving at speed. There is no delay whatsoever. All is well while you are going in a straight line.
The problems begin when you either stop abruptly or take a sharp turn. It then takes the GPS up to a few seconds to come to terms with what just happened. I can only assume this is due to some software component 'smoothing' the path by making up positions, i.e. looking ahead.
I uninstalled JPH and JPK. GPS doesn't do me any good when I see myself still driving down the same road after I took a right turn 5 seconds ago. JM8 and a number of other Eclair firmwares do not suffer from this.
Has anyone successfully 'downgraded' the GPS component of Froyo? Is this even possible? Is there a way to disable the 'look ahead'.....somewhere hidden in settings or some hidden menu?
ewok666 said:
Has anyone successfully 'downgraded' the GPS component of Froyo? Is this even possible? Is there a way to disable the 'look ahead'.....somewhere hidden in settings or some hidden menu?
Click to expand...
Click to collapse
Did you turn on the "Use Sensor Aiding" feature? That's new in Froyo. Try turning that off. It's in the Location menu.
hardcore said:
Did you turn on the "Use Sensor Aiding" feature? That's new in Froyo. Try turning that off. It's in the Location menu.
Click to expand...
Click to collapse
Thanks. I thought I had that disabled. Is this on by default? I'll give that a try next time I load a Froyo firmware....if there was a quick way to nandroid back without an Odin restore, EFS fixup plus all the Voodoo conversions that would be sooner rather than later ;-)
ewok666 said:
Thanks. I thought I had that disabled. Is this on by default? I'll give that a try next time I load a Froyo firmware....if there was a quick way to nandroid back without an Odin restore, EFS fixup plus all the Voodoo conversions that would be sooner rather than later ;-)
Click to expand...
Click to collapse
The default is off
It greatly helps when it's on I think
Arkanius said:
The default is off
It greatly helps when it's on I think
Click to expand...
Click to collapse
Isn't it meant to aid while walking? I can see that this may be causing when driving.
Well, there is absolutely no reason this option to decrease performance.. At least shouldnt be, unless Samsung screwed something up as usual. (which actually may be the case)
I had mine set to "off" by default. There is next to no difference while driving.
xan said:
Well, there is absolutely no reason this option to decrease performance.. At least shouldnt be, unless Samsung screwed something up as usual. (which actually may be the case)
I had mine set to "off" by default. There is next to no difference while driving.
Click to expand...
Click to collapse
As I said in the OP, I've always had the issue that GPS took seconds to realize that I changed direction or suddenly stopped. I'm just guessing that something that is intended to help stabilize GPS at slow speeds (walking, swimming with the dog, etc.) might cause a similar effect while travelling in a car.
swimming with the dog? I shat bricks ;d
Anyway, yes that right. Since its like phone is calculating from the sensor (compass, g-sensor -> speculating here) reads the approximate direction and pace you are moving at. It *might* be a problem with g-sensor read, becouse I find it quite flaky (using gps testing utilities exposes its terrible lag and low sensitivity)
BTW is it better after disabling it?
xan said:
swimming with the dog? I shat bricks ;d
Anyway, yes that right. Since its like phone is calculating from the sensor (compass, g-sensor -> speculating here) reads the approximate direction and pace you are moving at. It *might* be a problem with g-sensor read, becouse I find it quite flaky (using gps testing utilities exposes its terrible lag and low sensitivity)
BTW is it better after disabling it?
Click to expand...
Click to collapse
Well, there was a guy in another thread who claimed his Galaxy GPS was spot on. To proof that he uploaded a track of his walk with the dog and it clearly went right through the river a couple of times........I thought THAT was hilarious! ;-)
I might flash Froyo once again and play with that setting......still hoping that the Galaxy CAN do acceptable GPS. :-|
i'm mostly happy with the gps software on JPK (compared to JM8 which was already better than "official")
but the lag you're speaking about is killing me. there's waaay too much delay. sure it makes nice recorded tracks, but using it you'll see its crap
going to try my track with aiding stuff off tomorrow although im not sure its going to help
Well i am using JPK and the MOTONAV is running......ok, but i got "GPS LOST SIGNAL" every 10 minutes and the map jump around, after 10 seconds it will find signal again and back on track. anoying.
I borrowed an iphone 4 to test that thing's GPS and compare it to the Galaxy.
I have attached the Horror kml track file. It's no better, if not worse, than the Froyo stuff. I certainly did NOT expect that!
The kml can be viewed with Google earth and other GPS programs.....
And for the record....I did drive ON the road at all times ;-)
There is a new trend obviously. The more expensive the phone, the more messed up the GPS. LOL
What a total fail for the high-end devices these days.
bilboa1 said:
i'm mostly happy with the gps software on JPK (compared to JM8 which was already better than "official")
but the lag you're speaking about is killing me. there's waaay too much delay. sure it makes nice recorded tracks, but using it you'll see its crap
going to try my track with aiding stuff off tomorrow although im not sure its going to help
Click to expand...
Click to collapse
did not help ;D
bilboa1 said:
did not help ;D
Click to expand...
Click to collapse
Bummer......
Maybe they looked at the iPhone and thought it was a great 'feature'.
Oh man, if 2.2 firmware didn't get the GPS issues resolved, then it's pretty much useless for me. I'm happy with the overall phone as it is, minus the GPS issues.
stan28 said:
Oh man, if 2.2 firmware didn't get the GPS issues resolved, then it's pretty much useless for me. I'm happy with the overall phone as it is, minus the GPS issues.
Click to expand...
Click to collapse
The GPS issues will NEVER be resolved - it's a hardware problem. You probably just won't ever get Samsung to admit it, now they try those lame "sensor aiding" dirty fixes, but that's just another proof that it's a hardware problem - why else would they spend time doing the sensor aiding?
EDIT: I hope Samsung proves me wrong
MoWa22 said:
The GPS issues will NEVER be resolved - it's a hardware problem. You probably just won't ever get Samsung to admit it, now they try those lame "sensor aiding" dirty fixes, but that's just another proof that it's a hardware problem - why else would they spend time doing the sensor aiding?
Click to expand...
Click to collapse
PROVE IT!!! You are presenting hypothesis as fact, and that might be acceptable in places such as Digg, but it is inappropriate on developer websites.
Also, how do you know that sensor aiding required much much work? After all, it's predictable polling from already working/predictable sensors, unlike GPS sensors which pick up a fuzzy idea of where you are, is affected by satellite coverage, etc.
Sensor aiding can assist even GOOD GPS receivers indoors, tunnels and in areas where signal can drop (heavy trees, huge skyscrapers). Yes, even on Garmin units, this can be handy. We all know that the faster you travel the greater inaccuracies which are incurred, and this can help reduce inaccuracies in those scenarios. There are plenty of reasons to implement this functionality, and not all point towards bad hardware. Samsung probably has a few groups of programmers being thrown at different problems, because programmers aren't scalable, and there is a limit to the number of developers which can work on a specific issue/bug/improvement.
andrewluecke said:
PROVE IT!!! You are presenting hypothesis as fact, and that might be acceptable in places such as Digg, but it is inappropriate on developer websites.
Click to expand...
Click to collapse
I can't prove it - but I can use my brains to put together the circumstantial evidence. Sorry if that isn't good enough for you.
MoWa22 said:
I can't prove it - but I can use my brains to put together the circumstantial evidence. Sorry if that isn't good enough for you.
Click to expand...
Click to collapse
You SAID "The GPS issues will NEVER be resolved - it's a hardware problem", and spreading random rumors like that makes XDA appear unprofessional, and benefits nobody. I've just simply noticed a recent trend towards guesses being slowly changed to fact here in XDA developers, and I'd like to try to reduce the frequency of that happening
It is 20 days since we report a problem with drops after update to 4.0.4 . I judge that it is already too long and we should already have a fix. Now when all customs roms are using a new base, people who have this problem are forced to use an old 4.0.2 because with 4.0.4 phone useless. I think it would be good to start ask Google for any official statement because it is embarrassing for me that that they have such approach to theirs flagship phone.
This thread https://code.google.com/p/android/issues/detail?id=28133 shows that Google has completely no respect to us because there is now prove information that they even try to fix the problem.
Whats a shame Google.
Maybe should we start inform all gadget sites about this behavior?
Hey kid, stop being such a drama queen.
This is not how software development works. It takes time to iron out bugs. It takes time to first find out what causes the bug and then fix the bug and then it takes three times longer than that to make sure that the bug does not cause other bugs in the system.
Let's not forget how long 4.0.4 took to arrive in the first place. They originally released 4.0.3 and then discovered some bugs. Fixing those bugs apparently caused issues in 4.0.4 that no one saw coming, this means that the bug is not easy to find and is difficult to test for. They are doing it as fast as they can.
And let's not forget that not all devices are even affected. I've been on 4.0.4 ever since it was released and I've not experienced a single data drop. So it does not happen with all devices and may be region or carrier-specific. This makes it even more difficult to test for.
you honestly think they are able to push another update to a fix in 20 days?
kara mustafa said:
I judge that it is already too long and we should already have a fix.
Click to expand...
Click to collapse
You seriously think 20 days is too long to identify the problem that doesn't affect all devices, develop a fix, test the fix, and push it out?
Just started noticing I have this problem.
I just reboot and it fixes, a hassle, but whatever. reboots pretty fast lol and only happens rarely
luftrofl said:
You seriously think 20 days is too long to identify the problem that doesn't affect all devices, develop a fix, test the fix, and push it out?
Click to expand...
Click to collapse
You don't, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.
adrynalyne said:
You do, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.
Click to expand...
Click to collapse
The radio seems fine since I tried stock 4.0.2 with the XXLA02 radio (from the 4.0.4 package) and everything worked wonderfully.
adrynalyne said:
You do, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.
Click to expand...
Click to collapse
I do?
Same problem here, have to reboot to fix it, any alternative suggestion?
Sent from my Galaxy Nexus using XDA
To be honest I think it does affect all devices. I say this because I was away on business when 404 came out. Where I was I was in a lot of cinder block buildings and frequently without full signal. I had hspa and umts during that time but it wasn't a 21 or 42 mbps area like where I live. I often dropped signal on 404 that I didn't when I had 403 there. Now, after coming home back to my area that has a better coverage and such, I've not had one drop in signal. I really think its dependent on the towers and saturation whether you have the problem or not. I would still like to see a fix from Google. In the process of gaining battery life, I think they messed up smart reflex in respect to how it powers the antenna.
Sent from my Galaxy Nexus using xda premium
luftrofl said:
I do?
Click to expand...
Click to collapse
Lol, he must have misunderstood you.
No, it was a typo and I corrected it.
I meant to say, apparently, you do not. As in, he believes it only takes 20 days to diagnose, text, and implement a fix, which is funny
No fix is diagnosed day 1.
There is time to needed to find the problem.
There is time needed to create a fix.
There is time needed to properly test it, else other bugs show up.
Developers do not work 7 days a week.
Not every Android developer will be assigned to the fix.
There is time needed to ramp up an OTA again in two flavors, ICL53FD_to_IMM76D, and IMM76D_to_whateverthebuildnamewillbe.
Jayrod1980 said:
To be honest I think it does affect all devices. I say this because I was away on business when 404 came out. Where I was I was in a lot of cinder block buildings and frequently without full signal. I had hspa and umts during that time but it wasn't a 21 or 42 mbps area like where I live. I often dropped signal on 404 that I didn't when I had 403 there. Now, after coming home back to my area that has a better coverage and such, I've not had one drop in signal. I really think its dependent on the towers and saturation whether you have the problem or not. I would still like to see a fix from Google. In the process of gaining battery life, I think they messed up smart reflex in respect to how it powers the antenna.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No it does not.
It does not affect CDMA devices, and I have found some GSM users on this forum it does not affect. Folks here just think that XDA is the hub of the world, and therefore if there is a large amount of issues being noted, it must be everyone. Because you know...everyone posts on XDA and other phone geek sites. I am not saying the bug isn't real, just that it isn't happening to EVERYONE.
Theshawty said:
The radio seems fine since I tried stock 4.0.2 with the XXLA02 radio (from the 4.0.4 package) and everything worked wonderfully.
Click to expand...
Click to collapse
It still could be the radios. There is a reason they change radios with each release.
For example, 4.0.4 by itself for CDMA users does not see a signal improvement. 4.0.4 radios on a 4.0.2 or 4.0.3 rom does not see signal improvements. However, 4.0.4 rom and 4.0.4 leaked radio firmware sees a signal improvement.
luftrofl said:
I do?
Click to expand...
Click to collapse
It was a typo, but you knew that.
Theshawty said:
Lol, he must have misunderstood you.
Click to expand...
Click to collapse
reading is difficult..
Some people have reported getting the IMM76I update starting about an hour ago, so for those with the issue, it may help you.
adrynalyne said:
You don't, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.
Click to expand...
Click to collapse
He was saying it with sarcasm. You should probably learn what that means before replying.
hotleadsingerguy said:
He was saying it with sarcasm. You should probably learn what that means before replying.
Click to expand...
Click to collapse
He wasn't being sarcastic. Nice try.
luftrofl said:
reading is difficult..
Click to expand...
Click to collapse
Sure is, considering I said several times it was a typo and you still didn't comprehend.