yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze General] dougc314:
More on my experiance

I went for a drive this afternoon, attempting to use Mapopolis an excellent but defunct road nav ap. It has always been the most robust on my 8125. It runs fine on the FUZE, but only with an external device. I assume there is something missing in the internal nav data stream, or something extra.

Both GPS test and Google Maps worked fine.

I used the terminal program to catch the strings coming from the 2 devices, the external device is a Parrot Bluetooth hands free kit with GPS. The parrot has the lat-lon and date-time sentences in its block but the internal device doesn't. That data is also in GPRMC however so Mapopolis should have gotten the info. The internal device is also putting out a non navigation string $PSTIS,*61 which is supposed to be proprietary sentence, probably is just and end of block indicator and Mapopolis should ignore. So this illustrates that debugging GPS nav problems can be quite complicated. Here my most robust winmo 5 software that works on the FUZE with external GPS devices from 1-3 years ago is barfing on the internal device data, probably not HTC's fault, the data set it provides is adequate for navigating.

parrot in dash GPS

GPRMC - GPS transit data

GPVTG - track made good, ground speed

GPGGA - GPS fix data

GPGSA - GPS DOP and active sats

GPGSV - GPS sats in view

GPGSV - "

GPGSV - "

GPGSV - "

GPGLL - lat lon

GPZDA - date time

internal

GPGSV - GPS sats in view

GPGSV - "

GPGSV - "

GPGGA - GPS fix data

GPVTG - track made good, ground speed

GPRMC - GPS transit data

GPGSA - GPS DOP and active sats

PSTIS - propietary data, probably end of block
[Touch Pro, Fuze General] pkirill:
I haven't had any trouble with the GPS on my Fuze except for the two day of HEAVY cloud cover we had. The first day I got it I installed Google Maps and had some fun watching it track me as I drove. I've since installed the Garmin XT software and it works like a charm as long as you can see some blue sky. I did run the Quick GPS business first if that makes a difference...
[Touch Pro, Fuze General] 10332007:
I was out and about today so ran some more tests on the GPS. Using default comm4 and 4800 GPS test would get a 3d lock then recycle into initializing GPS and searching for GPS unit.

Gave that 3 tries (it got a full lock very quickly) using the download of QuickGPS I had done a few days ago. Quit that and loaded the HTC GPS tool and got a full lock in less than 10 seconds from when I started the logging. Held solid so I left it running and went into Google Maps, once I turned on GPS through it full lock and maybe 0-1 second of lag from actual position which was great.

Worked very well, even when I was walking it was dead on where I was.

I did start up GPS test when I was walking down the stair well from my apartment to the outside, it picked up a few satellites in the open direction until I got out in the open. Once out in the open it picked up 16 and got a full lock. The unit doesnt seem to be super strong to gain a lock from a window or anything, but its pretty solid and works well once you get a few feet away from the building.

Google never went about 6 satellites today and usually has 8 - 10.
[Touch Pro, Fuze General] xawen:
Ok, has anyone whose Fuze was not properly finding a lock found a reliable (reproducible) solution?

I've been watching this thread since it started, but I'm at the point where I'm lost. I realize several lucky people have their GPS working out of the box with no issues. And some others have messed with ports and gotten it to work randomly by switching ports and such. But I'm talking about someone who had a problem, made a change, and now can use their GPS with no issues.

My phone worked with GPS exactly once. When it did, GPS Test, TomTom 7 and Google Maps all worked perfectly. Since then (and it's been several days) I have not been able to get a lock in any program. They all find the GPS with no problem, they just can't get a satellite lock. At best I can see three satellites (acording to GPS Test) after 10-15 minutes. It never improves from there.
[Touch Pro, Fuze General] 10332007:
Where are you standing with the phone when you try to get a lock? Are you updating QuickGPS information? (Dont have to do it every time but a few will help)

You should not need to change anything phone settting wise.

GPS test just needs to run Comm4, I have had the best luck on baud 4800. Same with HTC gps / Visual GPS.

If I am near a building I have found problems getting a lock.

What all have you changed if anything, and how are you attempting to gain a lock and where.

I had some problems at first until I went outside.
[Touch Pro, Fuze General] sooby77:
I had that happened to me once. I suggest turning off AGPS in the Control Panel, soft reset and try again, preferably outdoor. Good luck.
[Touch Pro, Fuze General] Phantisy:
I installed garmin the day I got my phone and it works fine. Never have and never will pay for att gps crap :)
[Touch Pro, Fuze General] Comp1demon:
OK whats the deal with the GPS on this phone.

I had a tilt runiing TT6 and it worked 100%. I would get a lock in 30seconds to 5 mins with no GPS update information.

I have Tom TOM 6 on a 2GB card in my Tilt (kaiser).

When I got my fuse I popped it out of the tilt put it in my Fuze and fired it up. After install NOTHING.

I got it to lock once....

I tried com 4 at 4800 with Other NMEA GPS reciever - thats what locked once.

I cannot replicate it, the time i got it to lock was in my kitchen - not even outside. Today i placed it on my bow window ledge and let it sit for 30 minutes and NOTHING! - I tried different baud rates for another 10 minutes each - even a fresh GPS download here and there.. Nothing works - I can't get a single lock. Even the GPS test gives me maybe one Sat - where in my TILT i would get minimum 7 sats

I do know that If I put the card back in my Tilt - I get an INTERNAL GPS option and that works 100% on my Tilt. The Raphael (fuze) only give me Other NMEA GPS reciever, Bluetooth and one other - anyways the point is that the INTENAL GPS option is gone when you use TT6 on the Fuze?

We really need a solution - I paid alot for this software and I don't want to have to return the Fuze cause the GPS don;t want to work right.

Any real 100% solutions that can be replacted that aren't super silly or involve 3+ steps to get it working each time??? Soft resets, using other apps and such to get your GPS program to work right (garmin, TT6/7 or GoogMaps) is not acceptable - but if there is a 100% temp solution that isn;t too rediculas, I would like to know what it is please..

Thanks
[Touch Pro, Fuze General] 10332007:
Have you tried going outside where the phone is in clear view of the whole sky, not inside on a window ledge?

Inside I cannot get a lock. Outside I start GPS test / HTC GPS what have you and get a lock, then google maps works without any problems.

You do not have to download QuickGPS every time, each download lasts for about a week as others have stated. The antenna in the Fuze might not be as good as in other models but it works just fine.
[Touch Pro, Fuze General] edj628:
this worked soooooo great, thank you so much, i was really getting frustrated with this
[Touch Pro, Fuze General] Comp1demon:
My window ledge the phone has a view of the entire Sky. The only difference between it and outside is just the glass. My tilt would get a dead lock in 15 seconds and i could be under my bed - standing infront (or sitting infront) of a wall of glass there should be no issue getting a lock - basicly tring to say - the GPS sucks... there is no way it should not get a lock where placed it. we need to figure out the issues with gps and solve them....
[Touch Pro, Fuze General] mindfrost82:
I can definitely say that the GPS antenna in the Fuze is not as strong as the Tilt...either that or we don't have a radio optimized for GPS yet.

Indoors I was lucky to get a lock with my Fuze (only happened a couple times). In my living room I could always get a lock with my Tilt.

In my car I got a lock within 10-15 secs on the Fuze, but it still wasn't as strong as the lock I got with my Tilt.

Garmin Mobile XT has some bars to show the GPS signal strength and with the Fuze I would only get 3-4 (it requires 3 to work). With the Tilt I always had 4-5 (usually 5) when outside.

I used it on my way to work, whith both Garmin and iGo8 and neither one of them lagged (I have aGPS off since I don't pay for ATT data). They seemed pretty accurate too.
[Touch Pro, Fuze General] AssassinsLament:
Well, all I know is there is definitely something wrong with the Fuze version of the GPS. We don't seem to be getting complaints from non Fuze (Touch Pro) owners, nor Sprint Touch Pro owners. And I'm assuming all three should have very similar if not the same exact hardware (for GPS). I know sprint's Touch Pro worked great. I owned one for a week, and I never had to "prime" it. All I ever did was run Google Maps and bam 20 seconds max for satellite locks.

Just keep complaining to ATT so they'll know about it and find a fix for it. It's definitely a hardware issue, as I've tried all sorts of roms and I've even cooked my own roms with drivers from diamond, from Touch Pro's (non Sprint because Sprint's is CDMA and the drivers didn't work right), and it made no difference.

I love the Fuze but this GPS issue is disheartening. So basically if I reset or power off and on my phone, I have to sit there for 10 - 20 minutes and run various software just to try to "prime" the GPS to work the way it should?

That isn't how it should work, is it?
[Touch Pro, Fuze General] adamantypants:
The fix that he posted works great. Fortunately for me, I have no frame of reference for GPS systems. I'm using Google maps and as soon as I have a view of the sky I lock on to a minimum of 9 satellites around my house, averaging 11. I get a lock on my location probably to within 5-10 feet of my actual location according to Google maps.
[Touch Pro, Fuze General] spaghetti_monster:
I went into my ATT store today because i couldnt lock any sat's. The guy was all ohh just take the batt out and try again. Did that locked 12 sats in under a min. Tryed again while i was driving same thing. Verry consistant with multiple trys in diff locations.

Its a temp fix because i get the problem again when it goes idle for a bit, but if i do the batt thing again it fixes it self. Ill try out the actual fix so i dont need to do the temp method again.
[Touch Pro, Fuze General] gelasmus:
Well, this issue is just sad.

Especially given the amount of time this device has been in ATT's hands for testing, etc.

It really is quite incompetent of both parties here for overlooking a feature that is listed right in your face on the front of the box.

I really would rather have gotten a Touch Pro straight from HTC, but this whole no US 3G band debacle on that unit that ATT forced on HTC, well it is just BS. I blame them both for this mess. HTC for cowering to ATT and ATT for just for being ATT.

But oh well, whatcha gonna do.

***** and moan.

Who knows, I may take this phone back if they don't address this issue quickly. First time I will have ever done that. But, I guess that is no real loss to them. What is one upset Fuze owner to all the legions of Iphone donkeys.

What sucks about that is that I actually like this phone a lot.

Whatever.
[Touch Pro, Fuze General] pkley:
Didn't read the whole thread, just the beginning and I'll add my .02...

Coming from a Tilt, the GPS is interesting. However, I did notice today while holding it up I finally got a lock, took maybe a minute or two (cold). I was using VisualGPS to verify my speedometer, set it on my thigh, looked down a minute later and it was 0mph - no signal. Picked it up flipped to the sig strength, bars came back up within 15 seconds. Put it on my leg, bars dropped.

Flipped it over (face down), left it on my leg for 20 seconds then quickly flipped it face up - good signal that quickly dropped.

I think it has issues getting GPS when it's face up!

However, I don't think this has any effect on the lag...
[Touch Pro, Fuze General] DeniaL:
That's just flat out retarded! Not saying it's not true, I just think it's dumb!

After more testing, i've found that getting a signal lock is not the hard part about this phone, it's KEEPING the damn signal lock. It just seems to drop off for 10-15 seconds for no damn reason, then BAM it's locked onto 9-11 sat's. How the hell can you go from NONE to 11...then back to NONE, then 9. Ok you get the point...my point is there has to be something in the ATT version that's conflicting with the GPS chip......there just has to be. It's the only thing that makes any sense!
[Touch Pro, Fuze General] jbedoya:
I install it, but not upgrade it, and Google, Garmin and Live Search only worked when Telenav (Not upgraded) was open.
[Touch Pro, Fuze General] jbedoya:
Before applying the sugestion on the first post of this thread, The GPS worked for me ONLY when have the telenav installed (but not upgraded) and running on the background. However, google, garmin and livesearch all of them lost the lock around evry 15-20 secs
[Touch Pro, Fuze General] jbedoya:
worked for me... but.

I used the procedure posted on the First post of this thread and worked fine for me. It takes to GPSTest about 60-120 seconds to get the fix. Bad news is that if I close my GPS applications for more than 5 mins, they can not regain the fix witouth the GPSTest.
[Touch Pro, Fuze General] starstreak:
Can't be the telenav. I did register it as we had a free 30day day trial. I canceled mine. And since then, I hard reset my phone without the bloat. So my Telenav isnt isntalled.

My GPS didn't have the "turning off and on" untill last night. I turned off agps, and I don't have that issue anymore. I still take forever to get a cold lock, but my tilt took a long time too. I do notice that the Fuze gets more sat locks than my Tilt. But seems to drop it all easier. Example, moving the phone from my hand (window height in my car) to my lap. I'll loose all gps depending where I am. My Tilt would loose some sats but still have a lock in that same area.
[Touch Pro, Fuze General] Blitz49:
From reading all this I still can't get my gps to work either. To the others that are getting it to work, did you guys installed a cooked rom or is it stock ATT rom?

Thanks
[Touch Pro, Fuze General] turbocycle:
Did you try to disable *BOTH* AGPS settings here:

Start -> Settings -> System Tab -> AGPS Settings

General Tab: Uncheck Enable AGPS

Privacy Tab: Uncheck Enable AGPS Location Information to Network Services

Once I did that, I could get a reliable fix and the lag is fine now.

FYI: I'm using a legal version of OCN8. GPS auto detected COM4 at 38400.
[Touch Pro, Fuze General] Fallon:
Ok, got Elite and ROM OS working with GPS Test Version 1.04 and figured out the quirks.

If I set it to use COM4 and start it up, it fails to find a GPS, if I set it to auto, exit, then restart it, it will find a GPS.

Get everything to work with no lag, but it often involves a lot of reboots and other fiddling around to get things working. TomTom 7.450 is working fine as well, although it's temperamental finding the GPS, and just as fiddly getting any signal at all once it finds the GPS.

Will try and figure out what I need to do to get things starting up nicely.

Devin Noel
[Touch Pro, Fuze General] wmm:
Yes. As far as I can tell, the AGPS settings are irrelevant to the performance I'm seeing. I've had almost instant fixes and cases where I give up after ten minutes without ever getting a fix, both with these enabled and with them disabled.

Unless... Hmm, is a change to the AGPS settings something that requires a soft reset to take effect? If so, then it's possible I wasn't actually using the setting I thought I was. I'll turn it off, do a soft reset, and see if I encounter the problem again.
[Touch Pro, Fuze General] allhalf425:
All I can say is that the GPS has been fairly reliable for me as long as it's clear skies and I'm outside. Initially, it was pretty much impossible for me to get a lock, either inside or outside, but it was also pretty cloudy and rainy. As soon as it cleared up, I could get a quick lock. I just returned my original Fuze for a new one, so I'll see how that one works out, but I think it's just that the GPS isn't very strong on the Fuze.
[Touch Pro, Fuze General] 10332007:
Mine is fully stock, took about 5 min to get a fix this morning after a reset, but it did its thing and now locks in under 10 seconds.
[Touch Pro, Fuze General] rvt1000:
I know everybody and their momma has put in their two cents so I might as well put in mine as well!

I did not activate telenav. I downloaded GMM and it wouldn't find GPS. So I downloaded gps test and started that first to turn on the gps receiver and wallah, gmm loaded my gps in 1 second flat. I will repost if things change but i remember my tilt sometimes needing gps test or visualgps to turn on the receiver. Now the real test will be reinstalling my inav and seeing if that will lock on as it was a pain on the tilt to get to work.

Will udpate if inav has isssues. Good luck!
[General Questions and Answers] LSGio:
i'd like this question to not be skipped by developers who aren't so familiar with the device im working with (Galaxy Xcover Pro) so i start out by saying it's an Exynos9611 device and most of the process described here is inspired by work done for the Galaxy A51, so if anyone solved this for the A51 it'll really help me.

I am trying to flash a custom dtbo image by modyfing the files in /arch/arm64/boot/dts/samsung and then combining them to a '.img' file with the mkdtboimg.py tool

to be honest, the difference in file size between my custom image and the stock one is huge but after comparing the dump from the aforementioned tool, they contain the same entries, so i guess the difference in size is a signature or some kind of padding, i also guess my assumption was correct because after flashing the dtbo.img in Odin, i got Error "public key used to sign data rejected.

dtbo: Error veryfing footer.

dtbo: Error veryfing vbmeta image: invalid vbmeta header."

now for some details and the actual questions :

i disabled a lot of vbmeta/proca/defex/RKP stuff and i run a customized Stock ROM with a custom super.img and boot.img partition

i was able to boot a custom kernel by doing the following steps

i disabled the avb flags in boot-fstab and in vendor-fstab and in boot-dt.img (fsmgr-flags) and i have a custom vbmeta.img that i made myself by taking the original descriptors and setting the verification flag to '1', if i set it to '2' - device doesn't boot

i replaced "skip_initramfs" with "want_initramfs" in kernel binary

P.S. - either nulled (256Bytes) vbmeta doesn't work for this device or i do something wrong

my questions are :

how can i disable dtbo vbmeta verification?

what is the difference between kernel-dt.img which is in kernel ramdisk and dtbo.img which is a seperate partition inside AP tar?

is there some easier way to disable avb/vbmeta verifications alltogether or is it always a tideous process?
[General Questions and Answers] MfmeheyitsmeIam:
Just ran into that same problem on my m62. Did you find a solution? Your wuestion was the only thing that showed when I googled the problem runnimg android 12
[OnePlus 8 Questions & Answers] shubbyshoes:
Hey yall, I really need some help.

So some back story:

I started using a oneplus 8 TMO version and wanted to unlock the bootloader to get android 12 and root the phone. So I went through the process of getting an unlock token and when I finally got it, unlocked my bootloader, flashed the global version of oxygen os, and got it updated to android 12. Everything was working great. So then I wanted to root the phone so I downloaded twrp, booted into fastboot, and tried flashing it. The phone then booted into the system even though I told it to boot into recovery. After about a minute or so it froze and rebooted into a kernal panic. I unfortunately do not have what it said and cant repeat the process, but it booted into recovery and I clicked reason for boot and it said something about the kernal. So after a reboot it then went into crash dump mode. So I had to use the msm download tool (unfortunately I only had the tmo msm version and thought I could just repeat the process because I had slow internet and didnt want to download the global msm tool) to get the phone working again. So booted into edl mode, reflashed the phone, and it booted up. The problem now is that I do not have an IMEI number. I have a wifi address, bt address, and everything else that makes me assume that the efs partition is still ok (but I dont know enough to debate that) but it does not recognize my sim card. The phone also freezed and restarts approximately every 30 seconds.

And now my problem and what I have tried:

Because I have no IMEI I cannot enable oem unlocking in developer settings, cant flash anything in the bootloader - including the unlock token - and can barely do anything in the system because it only stays on for small amounts of time. I have tried many imei write tools such as qualcomm smartphone write imei, readnwrite tool, fastboot imei writer, miracle box, and I think some others but none of them recognize my phone. Ive also tried the oneplus debloat and oem unlock script to try and bypass the setting but it didnt do anything. I have dialed *#801# and was able to enable engineering mode and diag toggle but it still didnt do anything for me. So I really dont know what to do any more. When in the bootloader or recovery the phone does not reboot, so I can stay there as long as I need. Any help on this would be greatly, greatly, greatly appreciated.
[OnePlus 8 Questions & Answers] Xryphon:
Have you tried using the MSMTool again?
[OnePlus 8 Questions & Answers] shubbyshoes:
Yeah unfortunately that hasn't worked... I've done it miltiple times with the T-Mobile one and can't use any other one because I don't have an unlocked bootloader... If I had a way to bypass the oem unlocking option in the settings then I might have a chance to fix it but don't know how to do that...
[OnePlus 8 Questions & Answers] gingerboy92:
try using this version of msmtool(i use MsmDownloadTool V4.0_Win7 on windows 10). it's a bit newer version(5.2.89) i extracted from OP9Pro file. replace the version from whichever unbrick file you download. worked for me. but don't upgrade to android 12 again, the same issue will happen
[OnePlus 8 Questions & Answers] shubbyshoes:
Thanks for the response! And I am so sorry but what do you mean by unbrick file? I just had to download the tmobile version of the msm tool. I mean to be fair it was uploaded by someone so they probably pre programmed it but I unfortunately dont have the knowledge for that. I am also using msmdownloadtool v4.0. Do you happen to have the links to what you are referring to?

Heres the link to the one that I have downloaded: https://xdaforums.com/t/op8-oos-tmo-55cb-unbrick-tool-to-restore-your-device-to-oxygenos.4093043/

Thanks!

EDIT: so once you said that I actually went to the link and there were various versions. So I tried another one and it didn't work but then tried one more and my IMEI was back! I have no idea why that happened but thanks for the idea! I was so happy.
[OnePlus 8 Questions & Answers] gingerboy92:
yeah, that's it. it's related to version of msmdownloadtool. some of them must have a newer version. i had the idea from someone else on this forum too. glad it helps. be careful not upgrade to android 12 for now. i think it's because of the way oos12 detects phone varient causing the modem to go crazy. not sure tho. would love to see someone figures it out
[OnePlus 8 Questions & Answers] Xryphon:
Yeah, OOS 12 messed up my phone for a bit until I was able to get OOS 11 back on both slots.
[OnePlus 8 Questions & Answers] hassaan786:
which worked for you?