Database Info

No WIFI tethering running stock HTC Inspire Gingerbread ROM

I am running the stock version of Gingerbread on my phone and just noticed today that the WIFI tethering option is not working. I don't live in the US and my phone is SIM unlocked.
When I select the WIFI tethering option I get a message to contact AT&T to purchase a tethering plan, I guess they did this to prevent people in the US from doing it since it was possible to do it with the Froyo version by deleting the APN settings.
I downloaded a widget that let me do the tethering once but not anymore.
Has anyone found a workaround for this?

Yes. Quit using the att stock rom.
Sent from my Inspire 4G using XDA Premium App

apn
follow this and use the guide to get free wifi teather on your phone.
http://www.unigizmo.com/1696/steps-by-steps-guide-–-to-enable-data-tethering-on-htc-inspire-4g

That will only work for Froyo but not Gingerbread . The new ROM won't even let you use those APN settings
I guess I will have to go back to stock Froyo. I did rooted once and instaled Coredroid but had to many annoying issues. Oh well hopefully someone will find a fix that doesn't involved rooting and whatnot. But thanks anyways

I have the GB too and I can confirm the old workaround doesn't work around and more.
I'm hoping for a new way .... Does anyone know of a fix or a 3rd party app that will provide the same functionality?

I've never "rooted" a phone before. I have the HTC Inspire and I was hoping to.
Can I root the GB version that is already installed? There is a Wireless Tethering app that won't work and asks .... Is your device rooted?

Hi everyone,
So far I haven't found any fix for the WIFI tethering or an app available in the Android market that will bypass that. So I just went back to Stock Froyo using the official RUU from HTC
About rooting, yeah sounds a bit complicated but if you follow all the steps then you'll be fine. I was kinda scared when I attempted to root my phone. I used the hack kit or whatever was called and I worked, make a search and you will find the guide. Then I installed CoreDroid V7 but it had some annoying issues, no random reboots or force closes though. Then after a week of using that ROM I read about the GB official updated and I downloaded the RUU. I gotta say the phone got a bit faster but today I discovered the WIFI tethering thing and it is something I use, maybe not all the time but is a great tool when there is no WIFI available to connect your computer to the Internet.
I shall update to GB when someone finds a fix for that. Good luck you all

Something you can try. I don't know if it will still work but if you turn airplane mode on and all at&t signal is off then turn on your wifi and go to the market and search for wifi tether apps.
Sent from my Desire HD using XDA App

I did try that. What I did was to put the phone in AP mode and it would let me activate the tethering option but as soon as I enabled the mobile connection I would get the same message that I need to call bla bla.
But Froyo will do alright for me right now. I didn't see any noticeable changes in the GUI in comparison with GB but GB does manage the resources better and improves the battery life. Next time I'll get a phone that is not carrier branded LOL

Bobbypty, I am having the exact same problem and want to do what you did when you say "So I just went back to Stock Froyo using the official RUU from HTC."
Can you please point me in the right direction as to how to obtain Stock Froyo from HTC? I have been to their site and can't find it, and I've searched the forums here and elsewhere on the web and can't find anything specific to this. I would really appreciate your help since it sounds like you have done EXACTLY what I want to do!

What's up?
Here is the direct download for the RUU and this will install the stock 2.2 for the phone. You will need to install the HTC sync in order to run it. Just double clicked on the exe file and you shouldn't have any problems. Make sure your phone has 30%+ of battery.
http://www.filefactory.com/file/b50...60.19_26.06.04.06_M_release_166557_signed.exe
Or go here and the download link is there
http://forum.xda-developers.com/showthread.php?t=957692

bobbypty said:
What's up?
Here is the direct download for the RUU and this will install the stock 2.2 for the phone. You will need to install the HTC sync in order to run it. Just double clicked on the exe file and you shouldn't have any problems. Make sure your phone has 30%+ of battery.
http://www.filefactory.com/file/b50...60.19_26.06.04.06_M_release_166557_signed.exe
Or go here and the download link is there
http://forum.xda-developers.com/showthread.php?t=957692
Click to expand...
Click to collapse
Is that going to downgrade radio as well? Thanks in advance.

Yup.
Everything will go back to stock. Radio version 12.39.60.19H_26.06.04.06_M Android version 2.2.1

Hi everyone,
Seems that there is no fix for this right now since the ROM for this phone is branded by ATT unlike the Desire HD (Close sister to this phone) is a unbranded HTC ROM.
So pretty much the options we have is either to go back to stock Froyo or root the phone and then install a custom ROM that is based off the DHD Gingerbread ROM, I've been reading other forums and the custom ROMs based from the Inspire 4G will still have the WIFI tethering option blocked, so stay away from those. Make sure the ROM you are installing is based from the DHD. Try Coredroid, Cyanogenmod or whatever you like. Rooting this phone is not that complicated and I was able to do it with a little help.
Good luck with the rooting/flashing if you decide to go for that. Search for Ace Hack Kit for instructions.

I was able to get wireless tethering working on an AT&T gingerbread ROM, I modifed the apn xml before i flashed it, I modified APN Type to * for all of the AT&T / ATT/ medianet entries in the file (except for the mms apn that exists in there). I can upload my file when I get home or you can download my ROM from the rom thread (static nonsense) and grab it from /system/etc. Theres also an apn file in /system/framework/framework-res.apk inside the xml folder, Mine is more or less blank, so you may want to replace that file as well. Just a thought anyways

beerbaronstatic said:
I was able to get wireless tethering working on an AT&T gingerbread ROM, I modifed the apn xml before i flashed it, I modified APN Type to * for all of the AT&T / ATT/ medianet entries in the file (except for the mms apn that exists in there). I can upload my file when I get home or you can download my ROM from the rom thread (static nonsense) and grab it from /system/etc. Theres also an apn file in /system/framework/framework-res.apk inside the xml folder, Mine is more or less blank, so you may want to replace that file as well. Just a thought anyways
Click to expand...
Click to collapse
That's essentially what I did in InspirePhacopida and that works on my phone, but I was able to do it on my wife's stock phone by just adding an APN, so who knows?

Hi Gene and beerbaronstatic,
First of all thanks for the assistance.
I guess that for me to do that I'll have to flash the ROM via rooting and whatnot or did you modify a file within the RUU so I can just run that and flash it as if I was the regular ROM?
Regards
Robert

bobbypty said:
Hi Gene,
First of all thanks for the assistance.
I guess that for me to do that I'll have to flash the ROM via rooting and whatnot or did you modify a file within the RUU so I can just run that and flash it as if I was the regular ROM?
Regards
Robert
Click to expand...
Click to collapse
No. You can't modify an RUU zip. They are signed by HTC. If you modify one, or make an unsigned one from scratch, then you must have S-OFF so that the hboot loader ignores the signature (or lack thereof).

This is Gingerbread 2.3.3 on the Inspire NOT Froyo 2.2
Thanks anywho....

Yes. The WIFI tethering option WILL NOT work on the stock Gingerbread ROM of the HTC Inspire, this will only work with stock Froyo by manually setting the APN.
If you want to have the WIFI tethering option with GB, then you will have to root the phone to install a custom ROM based off the Desire HD which is the European version of the Inspire. Coredroid is the only one I've used so far but right now I went back to stock Froyo.

[Q] Downgrade to 2.2

Hi all,
I've been reading all the tutorials on how to downgrade my O3D to 2.2 but I'm having a hard time choosing what info I should follow. And everytime a find something, usualy I get the impression that its kind of a bumpy ride...
My O3D is locked to Vodafone Portugal, not rooted, everything stock and my data cable is the one that came with the phone.
I want to keep everything stock in 2.2.
Can you please point me to the safest way to do this?
Oh, and I only have Win 7 available for the process.
Thank you so much for the help!

The easiest and most comprehensive tutorial to do that is the one posted here:
http://forum.xda-developers.com/showthread.php?t=1540163 (Point 2)
If you will need additional info on the steps mentioned on the above tutorial, you can visit the two threads below:
http://forum.xda-developers.com/showthread.php?t=1287236
http://forum.xda-developers.com/showthread.php?t=1473781

Thank you.
It does appear to be the simplest I've seen.
Really hope not to ruin my phone...
Oh, and what rom do you recomend?

I can't recommend you a Froyo ROM because I used the tutorial only to flash Gingerbread ROMs. I flashed the 21D ROM almost 4 weeks ago and I got only one ghost call (that I'm aware of).
So I'm sticking with the 21D at the moment until LG releases a new ROM or until the ghost calls start occurring more often.

botson71 said:
I can't recommend you a Froyo ROM because I used the tutorial only to flash Gingerbread ROMs. I flashed the 21D ROM almost 4 weeks ago and I got only one ghost call (that I'm aware of).
So I'm sticking with the 21D at the moment until LG releases a new ROM or until the ghost calls start occurring more often.
Click to expand...
Click to collapse
Well, I have 20a on mine and it was running smoothly but then suddenly it started again with the GC. I'm kind of in the verge of trashing this peace of sh!t.
If I downgrade using this method, when (if ever) LG relleases a fix or a new rom, I will be able to update via the nromal LG process?

Yes, you can upgrade later with the normal LG process or the one you've used to downgrade to Froyo.
However, since you've only recently started experiencing ghost calls, I would suggest to make a factory reset/wipe first on your current ROM and wait few days to see if you still have issues. In my case, the factory rest helped a lot and haven't experienced ghost calls for the last 3 weeks.

botson71 said:
Yes, you can upgrade later with the normal LG process or the one you've used to downgrade to Froyo.
However, since you've only recently started experiencing ghost calls, I would suggest to make a factory reset/wipe first on your current ROM and wait few days to see if you still have issues. In my case, the factory rest helped a lot and haven't experienced ghost calls for the last 3 weeks.
Click to expand...
Click to collapse
No no, I'm experiencing GC since the update in dec 2011. I've done the factory reset with the wipes twice and it got better, but then the monster came back.

Just finished downgrading and it went like a charm.
Just had to wipe data afterwards because i've got stuck in boot loop.
And since I've installed a carrier free rom, its so much faster now... No Vodafone things loading. The boot is twice as quick as it was in 2.3.
Thank you so much for the help!
+1!

Everyting you need is on this page (http://www.acidhazardrom.com). And he also developing a great rom. Read in tools. Please thank me god luck
Sent from my LG-P920 using xda premium

Mouselik said:
Just finished downgrading and it went like a charm.
Just had to wipe data afterwards because i've got stuck in boot loop.
And since I've installed a carrier free rom, its so much faster now... No Vodafone things loading. The boot is twice as quick as it was in 2.3.
Thank you so much for the help!
+1!
Click to expand...
Click to collapse
Glad to know that everything went well without a hitch. Which version of the Froyo ROMs you installed?

botson71 said:
Glad to know that everything went well without a hitch. Which version of the Froyo ROMs you installed?
Click to expand...
Click to collapse
The v10k downloaded directly from the guide. And it made the phone faster in normal usage. The benchmarks show the same results however.
It must be the fact that it doesn't comes without all the Vodafone [email protected] on it.

Yes, Froyo could be in some cases faster than GB, for example some games. It's also more compatible with certain apps like video calling apps (Fring, Tango etc). The biggest issue however with the Froyo is the relatively higher battery consumption.
By the way, I just remembered that I saw some time ago another method to downgrade/upgrade stock ROMs which has the major advantage of being completely automatic. The post and the zip file is here and includes complete instructions.
http://forum.xda-developers.com/showpost.php?p=22189294&postcount=30
I haven't tried it myself but many other did and they said that it works very well. I know that you've downgraded successfully but I just post this for a future reference.

Mouselik said:
The v10k downloaded directly from the guide. And it made the phone faster in normal usage. The benchmarks show the same results however.
It must be the fact that it doesn't comes without all the Vodafone [email protected] on it.
Click to expand...
Click to collapse
froyo is faster after you haven't trun off your phone for days!
and
froyo can install and run "dead space" smoothly, but gingerbread can't.

[GUIDE] How to get v21y over the air on G2x

UPDATE 6-15-2012: i just wanted to update the beginning of this post to make it a little clearer, the original text is below
to get the v21y base band on your phone over the air, you have to go back to stock
to do this you need a stock rom, either your own backup or the one from this thread
http://forum.xda-developers.com/showthread.php?t=1248644 (the first and second link is a stock 2.3.3 nandroid which is a zip you extract on your pc and run flash.bat from inside that folder)
if you need the drivers, download the third link.
follow the steps in that thread, it works
if you have your own stock nandroid, just boot into ClockworkMod Recovery and restore it (after you backup whats on your phone now)
then reboot your phone
after restoring either your stock nandroid or the one from the post above, shut your phone off and remove the battery and use NVFlash to restore the stock recovery
http://forum.xda-developers.com/showthread.php?t=1056847
reboot your phone
now that you have your phone like it was from the beginning you can go to System Settings/About Phone and click on Software Update. this should pull down the updated Gingerbread version 2.3.4 and the new baseband v21y. IT WILL OVERWRITE YOUR PHONE AND WILL BE PLAIN STOCK
it takes a few minutes so be patient
once it is done and it rebooted your phone you will have to put ClockworkMod Recovery back on it using NVFlash. then you can flash other roms to your phone
please keep in mind that there is a bluetooth issue with both GB and ICS roms on this baseband and that only a few roms actually support v21y. Owain has written an update file that you flash to get support on any rom with v21y, supposedly it does work on any rom (GB or ICS) but i have not tested it, so read up and test if you want.
as of CM7 RC3 all CM7 builds support v21y
please thank the owners of the threads linked above, their methods worked flawlessly for me and i hope they work for you as well. this was a very easy way for me to get the new baseband. good luck!
original post------------------------------------------------------------------------
i was having a heck of a time trying to get the new baseband installed on my phone. i had all the stuff downloaded and all the instructions ready, had the KDZ file, the LG tool, everything...but i could not get anything to work
so what did work?
well using CWM Recovery i restored my stock backup i had made when i first got the phone (best to save this off the phone as well in a safe place) and then using NVFlash i put the stock recovery back on it
once that was done and i was booted back into stock you can go into the About Phone and choose Software Update (or whatever its called) and check for an update. it found one and proceeded to download a 30meg file. asked if i wanted to apply the update, installed it, and rebooted into a nice shiny new 2.3.4 GB setup with v21y and the new baseband installed!
the CM7 nightly build (June 3) is working great. getting ready to try a couple of others (Buru, EB, Genesis (although i was having a problem there, see that thread))
so its only been one day on it but so far calls are good, gps lock is fast, overall loving my phone even more than before!!

Great that the OTA worked for you, I left my phone stock the whole week it was mentioned about sending it and I checked the software update and it always told me the software update check failed/timed out lol
Sent from my LG-P999

I am extremely pleased with the update.
I had been running a rooted stock ROM + CWM Recovery. I had been dismissing the update notice for weeks now. Finally, earlier this week I flashed back the stock recovery and let the OTA proceed.
Current uptime: 67:59:06
I haven't gone a full day without either a random reboot or a sleep of death in a LONG time.

Did mine the other way not over the air. Then did the sound update. Also running CM7 and all has been fine.
Sent from my LG-P999 using xda premium

edekalil said:
Did mine the other way not over the air. Then did the sound update. Also running CM7 and all has been fine.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
which cm7 are you using? i had the last nightly june 3 and could not get mass storage to work

I just did this method too and its a lot easier
---------- Post added at 08:56 AM ---------- Previous post was at 08:51 AM ----------
edekalil said:
Did mine the other way not over the air. Then did the sound update. Also running CM7 and all has been fine.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
What is the sound update? I thought it was included in the new baseband and is it in the ota update? Thanks

lamdaman said:
I just did this method too and its a lot easier
---------- Post added at 08:56 AM ---------- Previous post was at 08:51 AM ----------
What is the sound update? I thought it was included in the new baseband and is it in the ota update? Thanks
Click to expand...
Click to collapse
there were a few people that got a bad motorbooting sound when making calls and lg released an update to the new bb but it was only for people who had the sound issue

its was hard
i swear it was hard trying get it to work but once i found me a stock rom i was all good from there

Can you test if the 6.3.12 nightly has working in call bluetooth?

Joe333x said:
Can you test if the 6.3.12 nightly has working in call bluetooth?
Click to expand...
Click to collapse
i dont believe it was, i just had that installed on my phone and coming to work today i tried to connect it to my car bluetooth and it would not connect. i have an ICS rom on my phone now, hope it works with that...i know it did on EB ICS

updated the first post

Reverted back to stock this morning and installed the OTA update...now i'm back on cm7 with no issues. Great suggestion on an easy way to get the March baseband.
Thanks!
Sent from my LG-P999 using Tapatalk 2

im trying to do this but when i check for updates it says connection failed ive been trying for 30 mins on and off wifi

adame09 said:
im trying to do this but when i check for updates it says connection failed ive been trying for 30 mins on and off wifi
Click to expand...
Click to collapse
Use the LG update tool
Sent from my LG-P999 using XDA

adame09 said:
im trying to do this but when i check for updates it says connection failed ive been trying for 30 mins on and off wifi
Click to expand...
Click to collapse
you are on stock rom AND stock recovery? data connections good otherwise?

A little clarification, if I may...
Could I just flash the stock 2.3.3 nandroid from this thread: http://forum.xda-developers.com/showthread.php?t=1048274 to bring myself back to "stock" then, using NVFlash that's already on my computer from when I first rooted my phone, flash it back to stock recovery? After that, try the OTA to get myself to 2.3.4 or, if that doesn't work, use the LG Updater tool? Then just root my phone again and go back to enjoying custom ROMs?
Seems like it would be easier and one step less if I get the nandroid from that thread rather than following the link in the OP and having to extract something on my computer.

partylikeaninjastar said:
A little clarification, if I may...
Could I just flash the stock 2.3.3 nandroid from this thread: http://forum.xda-developers.com/showthread.php?t=1048274 to bring myself back to "stock" then, using NVFlash that's already on my computer from when I first rooted my phone, flash it back to stock recovery? After that, try the OTA to get myself to 2.3.4 or, if that doesn't work, use the LG Updater tool? Then just root my phone again and go back to enjoying custom ROMs?
Seems like it would be easier and one step less if I get the nandroid from that thread rather than following the link in the OP and having to extract something on my computer.
Click to expand...
Click to collapse
yes that will work as well and whether you get a stock rom from the link i posted or the one you posted makes no difference this was just how i did it

Hey, thanks! I've been wanting to update my BB ever since it became compatible with the new ROMs, just haven't been able to set aside the time to be able to do that. Just wanted to make sure I had it right before I attempted.
Your steps sounded easy and straight forward; it just never hurts makes sure!
Thanks again, bro.

partylikeaninjastar said:
Hey, thanks! I've been wanting to update my BB ever since it became compatible with the new ROMs, just haven't been able to set aside the time to be able to do that. Just wanted to make sure I had it right before I attempted.
Your steps sounded easy and straight forward; it just never hurts makes sure!
Thanks again, bro.
Click to expand...
Click to collapse
you're welcome
there is a bluetooth issue with all roms and the new BB so if you use BT you might want to stick with the stock 2.3.4 that you will get with the upgrade. lots of devs are working on that issue so hopefully it wont be long

suggestions?
I followed the instructions in the first post, and now am back on the stock rom (21e, july 15 2011). However, when I go to try the software update, I get the following message: "current version is the latest version." Is there another way to get the new 21y baseband?

Is there a solution for the WiFi issue?

It's been some time since I posted the problem. I searched around and didn't find any new information, so I am just hoping I missed something, like a possible thread that has a fix.
I have no WiFi, have gone through the book trying to fix it, to no avail. HOWEVER, I left the phone un used for about a month, battery had died long ago. A few days ago, I grabbed and and just decided to give it another shot and install revolution hd on it. For whatever reason, it installed successfully and the WiFi was working perfectly. So I updated the 4ext and had notice that a new version of HD had come out, so I decided to update it, and well, back to square 0, WiFi no longer works. So I tried to back pedal and repeated the steps leading up to the WiFi working, Super Wipe with smart flash enable, reboot, installed HD with no smart flash. But this time it did not work. Strange that it worked before though, I wonder if it being out of battery for so long had something to do with it.

did you try to flash the boot.img of your rom?
also if you are S-ON when flashing a rom always enable smartflash

rzr86 said:
did you try to flash the boot.img of your rom?
also if you are S-ON when flashing a rom always enable smartflash
Click to expand...
Click to collapse
What he said.. if you're s-on always flash with smartflash
Sent from my HTC Sensation 4G

I too had the wifi issues for quite some time. After updating my kernel it got fixed.
Probably you could do the following:
1. If your HBOOT is S-ON, make sure you follow the above two posts while flashing ROM
2. Ensure that the latest firmware is being used.
2. Try changing the kernel (mine is faux 009b4 now).

I am S-OFF, like I said, I've tried everything.
Just seem odd that out of nowhere it flashed correctly, I should of just left it at that, maybe if I leave the battery inside the phone drained for a while I can repeat the successful flash.

F9zSlavik said:
I am S-OFF, like I said, I've tried everything.
Just seem odd that out of nowhere it flashed correctly, I should of just left it at that, maybe if I leave the battery inside the phone drained for a while I can repeat the successful flash.
Click to expand...
Click to collapse
well don't know if you have tried this but the last thing I can think of is to go back to stock ruu, if it still doesn't work it might be hardware related
Sent from my HTC Sensation 4G

I faced with same issue. I use ARHD 6.7.1 and i have no problems with wi-fi , but when I try to install sense 4.0 roms for sensation, I always have wi- fi problem.I live in Almaty and I use Beeline for mobile carrier, My device is Revolutionary S-OFF. I live in Almaty and I use Beeline for mobile carrier, and also I have one sim card for Turkey, AVEA, when I use Beeline wi-fi doesn't work but when I use Avea wi-fi works completely. I tried wifix manager. But I can't find solution :/

Same thing happened to me when I updated, go to tools in 4ext before flashing and enable smart flash, I'm pretty sure this will help
Sent from my HTC Sensation XE with Beats Audio Z715e using xda app-developers app

Updated: JB nav issue also on 100% stock ROMs

EDIT 3/16: After more detailed testing during the day today I withdraw all of the claims below. 100% stock via RUU 2.20 + OTA 3.18 still crashes, it just takes a lot longer on my phone. I am leaving the original text below intact for context.
------------------
It would appear that the JB nav issue some of us are plagued with is exclusively due to something devs are doing with their custom ROMs. Here is why...
I am one of the unlucky ppl who could not get Nav to work with JB. I have tried multiple custom ROMs, including stock rooted, and nav always crashes within two minutes. Today I RUU-ed back to 2.20, changed CID to AT&T, took the official OTA and played with Nav without a hickup for 30 mins. I then unlocked again, Super_CID-ed and flashed CleanROM 6 R2. Nav immediately went haywire with the same symptoms as before. I then went through the RUU and OTA process once again, and Nav purrs like a kitten.
Not sure what custom ROMs are doing to mess up things...but the above suggests that something common that devs use to root is interacting incorrectly with JB on some phones. We seem to be a minority of users, as busy as our devs are we may get no love.
At this point I will stick with AT&T true stock for a while, will just flash a custom recovery and debloat it to an extent with the TWRP file manager or just slim down update.zip.

Re: JB nav issue seems to be caused by custom ROMs
Well I can't agree.
I have been using and beta testing Viper for a long time and never have trouble with nav.
I did update all my firmware to JB stock but even before that I could not replicate the issue others are having.
Just my two cents.
Sent from my HTC One XL using Tapatalk 2

Did you try one of the stock 3.18 roms? Make sure it's odexed and has an unmodified kernel.
Personally I haven't had navigation issues on two phones using firmware from 1.85 and 2.20, on 3.17 and 3.18 based jb roms.

pablo11 said:
Well I can't agree.
I have been using and beta testing Viper for a long time and never have trouble with nav.
I did update all my firmware to JB stock but even before that I could not replicate the issue others are having.
Just my two cents.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
It is well documented that only some HTC phones suffer from this problem. It has been seen on the HOX, the EVO, even on some SG3s. This is what has made it so maddeningly frustrating. It affects a small fraction of the users, so the devs don't spend any time trying to address it. Not blaming the devs, they can't go after every small issue. However, for those of us unfortunate enough to have it it has been a PITA.
slippers67 said:
Did you try one of the stock 3.18 roms? Make sure it's odexed and has an unmodified kernel.
Personally I haven't had navigation issues on two phones using firmware from 1.85 and 2.20, on 3.17 and 3.18 based jb roms.
Click to expand...
Click to collapse
Yes, I tried AT&T stock rooted, no dice. The ONLY thing that has worked so far is 100% stock unrooted OTA.

Re: JB nav issue seems to be caused by custom ROMs
don't know much about it, but I have the issue and I am most puzzled why the app hasn't had an update with bug fix. It's been too long an issue for the official channels not to have been noticed. If it IS ONLY custom roms, I wouldn't be surprised of the official channels just ignored the bug.
I initially thought maybe HTC made a deal with Google too break nav so people would start paying for a subscription to the HTC nav app. But I just use waze now. It seems to find better routes anyway.
This post was created and transmitted completely in analog.

I thought we had already covered it .. isn't it some people have a little diff hardware then others I think one member suggested gyroscopes differentiations being the problem...but I've never had a problem with nav on any jb sense rom nor jb in general ... It shouldnt be caused by custom roms as that doesnt make sense

Re: JB nav issue seems to be caused by custom ROMs
It really would be nice to see a firmware upgrade pack for the hox. It seems we actually need it.
Sent from my HTC One X using xda premium

Groovy,
There are alot of variables here, so try to narrow them down. These are the steps I would try:
1. RUU back to 2.20.
2. Take the 3.18 OTA.
3. Verify that navigation works perfectly.
4. Fastboot flash a custom recovery (twrp or cwm). Reboot back into the rom.
5. Verify that navigation works perfectly.
6. In recovery, backup the boot partition.
7. Flash scott's stock 3.18 rom from http://forum.xda-developers.com/showthread.php?t=2181399
8. Verify that navigation is crashing. If navigation is crashing at this point, it can only point to the slight changes in scott's stock 3.18 rom, which include adding busybox, superuser, and /system read/write.
9. To circumvent /system read/write, go into recovery and restore *only* the boot partition that you backed up in step 6. This will put the stock kernel back on that doesn't have init.d support, and thus won't enable /system read/write.
10. Verify that navigation is working or not working. If it works, then we know it's the kernel.

slippers67 said:
Groovy,
There are alot of variables here, so try to narrow them down. These are the steps I would try:
Click to expand...
Click to collapse
I already did this and try to convey it in the OP but perhaps was not clear.
1. RUU back to 2.20.
2. Take the 3.18 OTA.
3. Verify that navigation works perfectly.
Click to expand...
Click to collapse
This was done
4. Fastboot flash a custom recovery (twrp or cwm). Reboot back into the rom.
5. Verify that navigation works perfectly.
Click to expand...
Click to collapse
This was was done. BTW, TWRP 2.2.0 no longer works with the new firmware, but 2.3.1 works.
6. In recovery, backup the boot partition.
7. Flash scott's stock 3.18 rom from http://forum.xda-developers.com/showthread.php?t=2181399
8. Verify that navigation is crashing. If navigation is crashing at this point, it can only point to the slight changes in scott's stock 3.18 rom, which include adding busybox, superuser, and /system read/write.
Click to expand...
Click to collapse
This was done. Nav starts crashing as soon as CR6 R2 is installed. I also see crashing with stock rooted and viper.
Note also that a version of busybox is present on stock.
9. To circumvent /system read/write, go into recovery and restore *only* the boot partition that you backed up in step 6. This will put the stock kernel back on that doesn't have init.d support, and thus won't enable /system read/write.
10. Verify that navigation is working or not working. If it works, then we know it's the kernel.
Click to expand...
Click to collapse
I will have to try this. Will get to it at some point today. However, there is an additional wrinkle. I debloated the AT&T ROM last night and am now seeing crashes again. Not sure if the original stability was a red herring, will have to redo the OTA and start all over again.

GroovyGeek said:
I already did this and try to convey it in the OP but perhaps was not clear.
This was done
This was was done. BTW, TWRP 2.2.0 no longer works with the new firmware, but 2.3.1 works.
This was done. Nav starts crashing as soon as CR6 R2 is installed. I also see crashing with stock rooted and viper.
Note also that a version of busybox is present on stock.
I will have to try this. Will get to it at some point today. However, there is an additional wrinkle. I debloated the AT&T ROM last night and am now seeing crashes again. Not sure if the original stability was a red herring, will have to redo the OTA and start all over again.
Click to expand...
Click to collapse
Don't use CR6.2. Use the stock 3.18 rom he released. Then restore the boot.img from the backup. At that point, the only difference will be the different recovery on your phone, as everything else will be the same as taking the OTA.

I've had the issue but only after updating to the latest ViperXL OTA.

After more detailed testing during the day today I withdraw all of the claims from the OP. 100% stock via RUU 2.20 + OTA 3.18 still crashes, it just takes a lot longer on my phone. I am leaving the original text of the OP intact for context, have added a comment at the top to indicate it is no longer relevant. I have now officially given up on JB and am going back to ICS. Google Nav is just too much of a convenience to mess around with replacements.

GroovyGeek said:
After more detailed testing during the day today I withdraw all of the claims from the OP. 100% stock via RUU 2.20 + OTA 3.18 still crashes, it just takes a lot longer on my phone. I am leaving the original text of the OP intact for context, have added a comment at the top to indicate it is no longer relevant. I have now officially given up on JB and am going back to ICS. Google Nav is just too much of a convenience to mess around with replacements.
Click to expand...
Click to collapse
Yikes! Maybe google/HTC will try to fix it now that it happens on stock.
Sent from my HTC One XL

ECEXCURSION said:
Yikes! Maybe google/HTC will try to fix it now that it happens on stock.
Sent from my HTC One XL
Click to expand...
Click to collapse
For a small subset of a nearly 2 year old phone? Good luck with that. Your best strategy may be to remove the relocked text, change the s-off text to s-on (without actually going back to s-on), change the Cid back, ruu 2.20, take the ota, then take it to an att store and insist that since the ota broke it it is their job to fix it for you. If you are lucky they will give you a refurb with 2.20. If you are not so lucky they will give you a refurb with JB and then you are stuck without root. Worst case they tell you to eff off. You then take the phone home and revert back to whatever you want (since you are in reality s-off). And before anyone claims that this is unethical, how ethical is it for att to screw a portion of their customers?

GroovyGeek said:
For a small subset of a nearly 2 year old phone? Good luck with that. Your best strategy may be to remove the relocked text, change the s-off text to s-on (without actually going back to s-on), change the Cid back, ruu 2.20, take the ota, then take it to an att store and insist that since the ota broke it it is their job to fix it for you. If you are lucky they will give you a refurb with 2.20. If you are not so lucky they will give you a refurb with JB and then you are stuck without root. Worst case they tell you to eff off. You then take the phone home and revert back to whatever you want (since you are in reality s-off). And before anyone claims that this is unethical, how ethical is it for att to screw a portion of their customers?
Click to expand...
Click to collapse
I'm confused. This phone was released 11 months ago. Announced 13 months ago.
10 months in the US, even.

Not sure why groovygeek thinks the phone was released so long ago... May 9th 2012 in the US.
Sent from my HTC One XL
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
For those with the nav crashing, are you charging the phone when this happens? Does it cash both ways?
Sent from my HTC One XL

I have two phones bought at the same time. One is stock unrooted and runs the OTA 3.18 with no google maps crashes. My phone as described in my sig has map crashes always. I haven't jumped around to many other JB roms besides Viper to this point because they all seemed to be having issues with the JB and Google Maps. Didn't have any crashes with ICS.

Just wanted to say that many one s owners are experiencing the same problem.
Sent from my HTC One XL