BT issues in the Past Week for Anyone else? - LG V30 Questions & Answers

Looking to see if anyone else has had BT issues in the past week-ish? I'll get some cutting out of the audio. It seems to happen no matter which app I'm streaming from or what device I'm streaming to. Also, I'm not sure if it is related but I've noticed some weirdness with my Fitbit Syncing too since roughly about the same time. (Some of the data is making it across to my phone because another app gives me credit for the steps taken but none of the info shows up in the Fitbit app and I can't get the time on the tracker to update. May 12th seems to be the last official sync.)
I responded to a post in the Tmo Oreo thread that I'm not really sure that it is related to the Oreo update. I did the update right when the OTA came out then went on a road trip. It didn't happen the first couple of days. I initially thought it was thermal cut out since I was driving a lot at the time and it was pretty hot out. But it still happened when I was driving at night when it was cooler. Then I was thinking it might be my car's BT but it's also happening as I sit here at my desk connected to a pair of BT headphones that were also reliable before my trip.
So it's looking like some sort of update did it but I'm at a loss as to which one so I thought I'd see if anyone else was having the same issues. Although, after a little looking around, I think the Fitbit stuff may just be Fitbit's issue.

CHH2 said:
Looking to see if anyone else has had BT issues in the past week-ish? I'll get some cutting out of the audio. It seems to happen no matter which app I'm streaming from or what device I'm streaming to. Also, I'm not sure if it is related but I've noticed some weirdness with my Fitbit Syncing too since roughly about the same time. (Some of the data is making it across to my phone because another app gives me credit for the steps taken but none of the info shows up in the Fitbit app and I can't get the time on the tracker to update. May 12th seems to be the last official sync.)
I responded to a post in the Tmo Oreo thread that I'm not really sure that it is related to the Oreo update. I did the update right when the OTA came out then went on a road trip. It didn't happen the first couple of days. I initially thought it was thermal cut out since I was driving a lot at the time and it was pretty hot out. But it still happened when I was driving at night when it was cooler. Then I was thinking it might be my car's BT but it's also happening as I sit here at my desk connected to a pair of BT headphones that were also reliable before my trip.
So it's looking like some sort of update did it but I'm at a loss as to which one so I thought I'd see if anyone else was having the same issues. Although, after a little looking around, I think the Fitbit stuff may just be Fitbit's issue.
Click to expand...
Click to collapse
This was one of the reasons the Oreo update was halted.

R800x_user said:
This was one of the reasons the Oreo update was halted.
Click to expand...
Click to collapse
As I said, this doesn't seem to be Oreo related. Just as oddly as it started, it has stopped. So it doesn't seem to be related to any visible front end update, OS or app. Looks like it is somewhere in a background update. (And I don't have any my apps set to auto update.)

FWIW, the only communication update that I can recollect at this point in time that is causing a ton of problems for mobile device users is the Bluetooth 5 that came out with Oreo 8.0. It is a bonifide mess. The version that came out with Oreo 8.1 was supposed to fix these issues, but I don't know that this actually happened. For the most part, manufacturer updates that are released for devices, such as BT Headphones, will try to incorporate a workaround or fixaround for the deficiencies in the underlying software, such as Bluetooth. But there is only so much that a manufacturer can do to circumvent the fundamental issues in an application such as Bluetooth. After all the promises and hype, the basic consensus is that Bluetooth 5 practical improvements are basically in range and some bandwidth. But it is also pretty well accepted, by now, that Bluetooth 5 is largely a mess right now, and not only for headphones, but pretty much about everything that you try to pair your phone to.

Related

Eclipse and bluetooth possible issue.

hello, I am running the current public release at the time of this post(v1.1). I have a Jabra SP700 bluetooth FM speaker for my car. I am uncertain if this is a fault of the rom or the hardware of my bluetooth speaker. I am leaning more towards the bluetooth but I figured I would ask the community.
I play music through this to my car stereo. Frequently the bluetooth drops the audio connection at random times. The phone and speaker say the X2 is connected, but the audio ceases. Within a minute the sound will play through the phone speaker not the bluetooth. Then the bluetooth will say "disconnected" and begin searching to reconnect. My X2 will state the bluetooth is still connected. In order for me to get the phone connected, I need to power off the bluetooth then disable and reenable bluetooth on the X2.
I believe this has happened with previous versions, ive been using eclipse since it started. Although I cannot remember if it works correctly with the bluetooth bone stock.
I am leaning towards the bluetooth since the bluetooth is about 2 years old now...but I was wondering if anybody used a similar bluetooth piece and experienced similar issues. Thanks!!
Ok guys. Let's try this thread over.
Anyone want to help this gentleman? We're not going to argue or derail. If you can't help this guy, don't respond.
OP, search while you wait for an answer.
There is a known issue with the bluetooth function on 1.1
I had heard people saying that with the newest ((1.2rc3)) that the issue had been fixed.
I don't use bluetooth do I cannot confirm but that might be the issue
I didn't think that older BTdevices would become "obsolete" . I thought any newer phones that support bluetooth would encompass all older BTdevices not exclude them. I can see an older phone not connecting to newer bluetooth but not older bluetooth not connect to newer phone.
Nitro tweeted that the new eclipse final should be out tomorrow. Hr has known about the bluetooth bug for a while so I am sure it was a priority fix.
It is possible tho that there is something faulty with your bluetooth device. Have you tried contacting the manufacturers of it to see if that is a known problem with that device? They may be able to help troubleshoot it also.
Thanks ash. As usual you are helpful and nice the speaker is way out of warranty. Ive owned it for 2 years. The battery os startong to go too. I never doubted the compatibility of the speaker...just the performance. It has acted odd in the past. I did not notice an issue initially with the X2. Since it started acting up i was pretty sure it was the bluetooth just showing its age and starting to malfunction. Well at least i do not have to buy anothee speaker just yet
Sent from my DROID X2 using XDA App
Thanks
Even if it is out pf warranty they may be the type of company who is willing to repair or help with problems just to keep your loyalty to their products. Who knows you may be able to talk them into a rebate on new product or a coupon or something . Might be worth a shot. Just be site you tell them you promote the product to people you know and in forums you post in. I have been looking for either a wired or bluetooth speaker for my x2 and not sure what to go with. . I saw one in the VZW store I
that looked nice but $199 is a bit steep for a speaker for me lol
And it seems like any other speaker I find (wired or bluetooth) is labeled do I ipod /iphone etc... im thinking the wired would work okay((headphones jack type)) but am not willing to shell out the 50$ that ill only get back in store credit for opened electronic in a store I barely shop at lol. Im sure ill find something sometime and ur post introduced me to a different one to look into. Curious if new eclipse final will fix your problems. Good luck.
Its odd that it will work for a while and then cut off. Wonder if it may be the "receiver " in the device not working correctly. Maybe something wiggled loose. Might be worth taking it apart((if possible) and checking where things connect to each other it giving it a wipe down and clean it up. Maybe dirt is interfering with something inside due to its age.
Or IT'S ALL YOUR FAULT. YOU USED IT TO MUCH FOR WHAT IT WAS DESIGNED FOR AND IT IS DEAD NOW ...lol j/k...im sure something can be done to fix it if it isn't eclipse that is causing the problem. ..its just a matter of is it worth the time to fix or buy a new one..
It is all my fault!!!! Haha. Well that is an idea....maybe i will try. If i can make a suggestion, the droid roadster is pretty cool. Works well and is user friendly! I tested it for a while and liked it.
Sent from my DROID X2 using XDA App
I have a bluetooth earpiece that I use with my old Razr and it works fine with my DX2 so I don't think age has much to do with compatibility. Wear and tear probably plays more of a factor.
I do pair my DX2 with my Touchpad (WebOS, not when booted in CM7) and I can make calls great on the TP but because the default bluetooth.dun is missing from Eclipse I can send sms with my TP. Not an issue but something to consider if you are shopping and comparing specs to see if you nifty new devices will work with your phone. The devs pull out the blur and bloat because that is what we want but it can change how devices talk to each other.
I have a set of moto rokr hd headphones that I use all the time and I have had this exact same issue with eclipse. The phone still says it has a connection but no audio is playing through my headphones. The only way to correct the issue is to turn off the headphones and turn off bluetooth on the phone and restart them both. It will happen completely at random times. Sometimes I will use them for a couple hours before it hours, but sometimes only 15 min. Its def eclipse, I don't think moto headphones have a compatability issue with a moto phone

Need some help, or this has to go back

I travel a lot, and I'm a minimalist. In other words, I'll travel for a week and take a paper lunch bag as my carry-on with hopes that I can get by with wearing the same outfit the entire week. I don't like carrying a full Navigation system and use my phone. This isn't an 'iPhone lovefest' because honestly, I hate everything about Apple, but I never had problems like this on my iPhone.
My problem though is the GPS. I'm on my third phone because of the GPS. The first phone would never get a lock on GPS. I could be sitting outside with a GPS satellite dedicated to me directly above me, and it would still say "Searching for Satellite". That phone went back and I took on another one.
Second phone had a problem where every now and then it would work, then stop working and never start working again until I rebooted the phone and even then it was questionable if it would start working again.
I just got my third phone a couple days ago. I did a stock root w/ no bootloaders, used Entropy's 11/13 Kernel, then threw on UnNamed ROM. This morning, I started up my car to drive somewhere and decided to test the GPS/Navigation. It took it a couple minutes to find the Satellite, then all seemed to be working ok. Then 20 minutes later it dropped the Satellite and it spent the next 40 minutes of my drive into the office saying "Searching for Satellite" no matter what I did.
This is really important to me as is the ability to tether when I want to (hence the reason I want a phone I can Root). So what can I do. At the moment, I've (In my head, so I could be wrong) narrowed it down to a couple things that could be wrong.
1. It's the ROM that's the problem. Though unlikely, it is a factor and it's me messing with the way the phone was designed and distributed.
2. It's the GPS in general. Seems like 95% of the people on here aren't having problems at all. There does seem to be 5% that seem to be having the same problems I am.
3. My region has crappy Satellite Coverage. Doubtful since my iPhone worked fine, and unless Apple did something amazing like put in an entire dedicated Satellite network to work with Jailbroke iPhones then this kinds of negates this though.
4. My cars are interferring. While this is entirely a possibility (I never do think to test this out in the open not in a car, so i can't say for sure) if it is the problem, then the device goes back as it's much cheaper to get a new device than to replace 2 cars. Again, though, my iPhone never had a problem doing this in these cars.
I love the phone, the speed, the Android OS etc... I don't want to go back to an iPhone because I"ll shoot myself. I just want to be able to have GPS work on this as it's the only hold up on the device. Any help anyone can do?
Take it back then. Honestly you say you have tried 3 different phones and all 3 are broken. I call bull****.
Never had a problem with it.
Sent from my SAMSUNG-SGH-I777 using XDA App
You didn't mention if you've tried in ANY of the three (3) phones if the GPS worked before rooting?? I'm not saying it's the rooting that's causing the problem, but I'm still running stock on my SGSII and have had no issues with GPS? Not saying it's not possible but three phones is kinda stretching it a bit to all have the same issue.
Yes, I know you took it back to STOCK rom with #3 but who knows if the STOCK ROM is really *STOCK*, you should try a new phone #4 stock without ROOT for at least a day or two to determine if it is a DESIGN/HARDWARE issue rule that out first and then try from there... If this still happens with STOCK phone, you may have to switch to another phone (iphone or otherwise)...
Good Luck!
I just took it back to stock and was going to go outside to see if it had problems finding service. Though as mentioned in many other threads on here, it's not so much it finding you when you're standing still. It's when you're driving the streets of Atlanta that things get crazy.
stalked_r/t said:
I just took it back to stock and was going to go outside to see if it had problems finding service. Though as mentioned in many other threads on here, it's not so much it finding you when you're standing still. It's when you're driving the streets of Atlanta that things get crazy.
Click to expand...
Click to collapse
Hi Stalk,
Keep in STOCK mode and drive around with it and see if this is still an issue then... Also if you have an aluminum case, this has been a known issue where the TARGUS (SP?) korean made BEAUTIFUL/GORGEOUS case affected the GPS antennae. Try it stock no case on the dash away from DIRECT sunslight and begin troubleshooting there...
UNFORTUNATELY it may boil down to Stock and working GPS or ROOT with Tethering... You ***MIGHT*** not be able to do both...
Good Luck...
If you JUST root, it shouldn't affect GPS - but test without rooting first.
And I agree - if you've got a metal case, DITCH IT.
So far, my experience is that the GPS chipset is almost as good as any standalone GPS chipset I've used - Sirf StarIII, MTKv2, STM Cartesio (the latter being the chipset in my Garmin Oregon, the former being chipsets in various Bluetooth dataloggers I've used for hiking). Actually, the GPS in this phone beats the StarIII and is around on par with the Cartesio. So far nothing I've ever used can touch an MTKv2 though.
I'm used to phones having crappy awful GPS chipsets - this is the first device I would ever consider using for geocaching on its own.
Thanks for the replies. I did test just now on the way to and from lunch with stock everything. I do have a case that's part aluminum (Case-Mate). I didn't try it without the case. didn't even think it could affect this.
Running a stock setup, I attempted to get navigation to my lunch location The drive was about 6 miles each way. When I left the office, I started Navigation. It never found a satellite enroute to the restaurant. I never stopped it during lunch from looking, though I was in a building, so i didn't expect it to find anything. On the way home, same status. Searching for satellites. I'm torn. I want this phone bad, love the Dev support, and there's nothing coming from AT&T that makes me want to use an old Blackberry to wait for. I also don't know what I can do to test this further.
On the way home, I'm going to do something very simple. I'm going to wipe the phone. I'm going to skip all steps of the initial setup, just have service and that's it. I'll start navigation and have it direct me home. If it doesn't work, I'll look at my options. If it works, then I know it's an app that's causing the problem.
Unless someone else can think of something for me to try. I wish this just worked like I know it can.
Ok. So an update. Wiped phone, not even associated with Google, Removed my 32 gig SD card for the heck of it, removed the case. Started nav and INSANTLY inside a building it had me pinpointed and was directing me to the next turn point to get home.
Here's the case I have: http://www.case-mate.com/Samsung-Ga...rsion-Barely-There-Brushed-Aluminum-Cases.asp
In one of the reviews, this is said:
As much as I wanted to love this case, I couldn't. I've used many Case Mate products before and I am just disappointed in them for the lack of quality of this case. There is a noticeable issue with the case fitting the bezel on the top right corner of the phone. The lip of the case fails to properly wrap around the front bezel. There is also the connectivity problems that come with this case. GPS has especially weakened with this case on. Other than that, I like the quality material that this case is built out of and feels very sturdy. Unfortunately though as of this writing, this is really the only choice for a decent case for this phone on the market. Time will tell if better choices come about.
Click to expand...
Click to collapse
I'm going to keep this setup through tomorrow, then root the phone if there's no difference in performance and all is well. If that works fine for 2 days, I'll throw the Kernel on and throw UnNamed on. If that works, I'll throw the case on and see what happens. I now feel like this could be the problem. Thanks for the thoughts guys. I'll continue my abuse of the "THANKS" button and thank you all.
ride home was flawless. If ride to work tomorrow is flawless, I'll root and flash.
Entropy512 said:
If you JUST root, it shouldn't affect GPS - but test without rooting first.
And I agree - if you've got a metal case, DITCH IT.
So far, my experience is that the GPS chipset is almost as good as any standalone GPS chipset I've used - Sirf StarIII, MTKv2, STM Cartesio (the latter being the chipset in my Garmin Oregon, the former being chipsets in various Bluetooth dataloggers I've used for hiking). Actually, the GPS in this phone beats the StarIII and is around on par with the Cartesio. So far nothing I've ever used can touch an MTKv2 though.
I'm used to phones having crappy awful GPS chipsets - this is the first device I would ever consider using for geocaching on its own.
Click to expand...
Click to collapse
I haven't gotten enough free time to log the NMEA output, but I don't think our "SirfSTAR IV" chipset is actually even using DGPS/WAAS. Which makes the accuracy it get's even more impressive. The chip definitely supports WAAS, but who knows exactly how the implementation is done between Android & Samsung...
I've also owned a SirfStar III based Bluetooth GPS, a MTK-based GPS (also the best I've found), and several phones with dedicated and integrated GPS chipsets. Have to agree our GS2 is one of the best. I can't exactly wander around the house and have it track my every movement like my Bluetooth pucks can (also having a large ceramic patch antenna helps a bit no doubt), but my GS2 locks fast, and stays locked. What else can you want from a GPS?
Might be worth it to look into WAAS either way though. On any standalone GPS unit, WAAS is the difference between 15-30 meter accuracy, and 3-5 meter (or better) accuracy. That is unless you have a military GPS unit, and the appropriate keys to receive the high accuracy P(Y)/M signals...
If you want to get a good idea of how the GPS is doing, this app will show you the strength of your GPS lock:
https://market.android.com/details?id=com.eclipsim.gpsstatus2
Also, upon further research, the NMEA output is reporting that WAAS/DGPS is not in use.
Example: "$GPGGA,222520.000,4218.460926,N,07111.901869,W,1,06,1.2,77.1,M,-33.8,M,,*53"
Where the bold "1" should be 2, and the null field right before the checksum "*53" should be the age of the DGPS/WAAS info if it were in use.
The chipset in our phones (http://www.csr.com/products/35/sirfstariv-gsd4e) clearly states that it supports WAAS. And since the choice of DGPS or not is solely in the hands of the chip and software (wiring/antenna connection/configuration is irrelevant) perhaps there is a way to enable the DGPS mode? If so, I'm sure we would all see MUCH better position and accuracy information.
WAAS probably requires modifications to the host processing binary (SIRFHost)
BTW, our chip is a GSD4t, not 4e.
I was having problems with my gps losing its lock for the longest time, i got a replacement phone and it started doing it again AFTER root. Im thinking some app might be causing the issue. I read somewhere that ROM Manager can cause issues. I deleted it and so far my gps has been working. I am really baffled on to what can be causing it.
stalked_r/t said:
ride home was flawless. If ride to work tomorrow is flawless, I'll root and flash.
Click to expand...
Click to collapse
Its the case man. Great looking case, but kills the cell signal and terrible GPS. Mine went back after 3 days.
Sent from my SAMSUNG-SGH-I777 using XDA App
Yep. Ride into work today lost signal once. After letting it sit for a couple minutes, I rebooted. After reboot it worked flawlessly. Definitely the case at this point. Putting Root/Kernel/ROM on it today and seeing how the drive home is. If it's good, then the case can be tossed and I'll find a different one.
Entropy512 said:
WAAS probably requires modifications to the host processing binary (SIRFHost)
BTW, our chip is a GSD4t, not 4e.
Click to expand...
Click to collapse
Good catch. Interesting. Haven't checked out the sources, but I'm assuming all the GPS binaries are blobs? And source is not available?
Always wondered why mobile phones never have WAAS support... course then again, if the hardware was developed in Korea, that would make a little bit of sense. Seeing as there isn't WAAS coverage there, although I do believe there is an alternate DGPS solution for Asia.

HTC Amaze Bluetooth Truth

1.) Has anyone with the "Bluetooth Problem" rooted their phone and found that it fixed the BT issue.
2.) Did the first OTA cause the BT problem on the Amaze.
I bought my HTC Amaze in January 2012. I didn't have my access to my Plantronic headsets at the time. Before I was able to test the Bluetooth on my Amaze, the first OTA came out. I did the update and all was good. Then my headsets came in and I tried them all (3 total -Voyager Pro HD and Explorer.) The range with the Voyager and Explorer was about 1-2 Ft. I basically had to hold the handset next to the Bluetooth headset. The Explorer had a better reception, but both headsets were distorted with the sound of static and would drop connection with a mere turn of the head. After ICS I now get about 8-10 Ft. with lots of static at anything over 3 feet.
My HD2 running CyanogenMod 7 still gets 30 ft. line of sight. And 15-20 through doors and walls.... I guess I'm spoiled.
Thanks for any answers guys.
Nope. Mine works. I have a jawbone prime. No issues with connection.
Sent From My HTC Amaze 4G Via Someone's Room
Maybe there's an issue with your BT antenna? It could be something as similar to the wifi fix (where you add a small piece of aluminum foil to the back of your case where the antenna is).
I have spent alot of time on the T-mo forum in the last few months. For the most part there seems to be a BT issue with at least "some" of the phones. When I updated to ICS the BT did without question get better. Not great.. but marked improvement. The fact that ICS made it better, along with a few posters stating that their phones BT worked fine prior to the first OTA but went bad after the update, led me to believe that the problem may be software related ...ergo the first OTA. The other people that are having this problem also saw a difference when they too updated to ICS.
One update "allegedly" messed up BT on the phone (some anyway) and another made the BT problem better. Strange....
hasoon2000 and kered424 are you guys running stock ROMs? I haven't rooted a custom ROM up to this point because I wasn't sure if it would actually fix the problem. That is why I was seeking a confimation or denial that rooting the phone would fix the problem. My dilemma is returning the phone. I have not unlocked the phone...but I did do the "Leaked ICS." But that is off topic...
I've been running stock for the longest time, but recently switched to NRG's stock-look rom. I've never had an issue with bluetooth (gb, ics, or nrg). When I was running stock, I was rooted, but I doubt rooting will fix your problem.
kered424 said:
I've been running stock for the longest time, but recently switched to NRG's stock-look rom. I've never had an issue with bluetooth (gb, ics, or nrg). When I was running stock, I was rooted, but I doubt rooting will fix your problem.
Click to expand...
Click to collapse
Thanks for you reply kered424.
I guess what I am really looking for is someone that actually recognized they had the problem and notice a change when rooting a custom ROM onto the phone. I may not find that person here...most people here root without need. I'm all about rooting...I have an HD2 that I still root (my digitizer just went out.) I just do not want to go through the hassle of rooting only to find out that it was the hardware and not the software. I would not even post about this and root the phone...if it were not for the marked impovement when I updated to "Leaked ICS."
It leaves me going: "Hardware?..software?...hardware?...software?"
From your description, it sounds like hardware. Have you tried the aluminum foil trick? That's the only thing I can think of.
Solution to Amaze 4G Bluetooth Issues. Possibly.
I've been reading XDA forums and modding my phones for years and now and at last I may actually have a contribution to make.
Alright all of you suffering with this enormous Bluetooth problem on the Amaze 4G that HTC pretty much refuses to acknowledge or address.
I too purchased an Amaze a couple months ago and was quite satisfied with its overall performance. That is until I received a Bluetooth ipad game controller and set of S9-HD Bluetooth headphones for my birthday. Then the nightmare began. Constant signal loss. If I were trying to text someone the sound would cut out on every key press. The ipad game controller would lose connection before getting through level one on Metal Slug Three played with NEO.emu (an awesome app by the way for its support of that controller). The in call signal quality was terrible and this was after trying multiple headsets. I read about a foil trick to correct this problem but never once found a tutorial on how to do it and the Bluetooth antenna prongs often spoke of were never actually pointed out anywhere. I looked all night for a diagram that would indicate which ones they are. I am guessing the they are the ones on the upper left. Not the top two immediately above the camera. If I am mistaken please make haste to correct me as it will determine the solution I detail. I had to guess I could find no real confirmation of this as they are both top left. Would someone send me a picture of the actual phone with the backing taken off and indicate which leads are to the Bluetooth antenna? As soon as I can confirm this I will post the fix.
I design and repair custom PC's in my free time for the elderly, disabled, and low income and I used that background to do a little experimenting the result was two more 4G bars in my basement and the the headset cutting out once during a three paragraph text. In game sounds were flawless and in call performance was perfect without a single cut out of signal.
As soon as someone discloses where those actual Bluetooth prongs are. I will post the how to and materials needed to perform this very successful solution. Not a 100% but 90% which is certainly better than the 20% us Amaze users have been putting up with.
I'd also like to thank all the developers for all knowledge and effort that goes into making all the cool enhancements and themes I had on my old HD2 and am now leaning how to apply on the Amaze. Hours of fun. You are all very much appreciated and Keep people like me learning new things.
Oh, I am running NRG's latest Aug 6, 2012 ICS Themed ROM release for the Amaze, Stock Kernel, 4EXT (the best!) S-ON, (Bricked my first Amaze with S-OFF).
As soon as I get confirmation of the antenna location and do a little more testing I will post the fix right here (next week or two). I don't want to look like an idiot or give misinformation if I have it incorrect or cause any damagage to anyones phone.
You are right...I could not find anything showing a diagram or pic of where the antenna is/are located. Hopefully somone will provide you with something. Have tried emailing HTC and outright asking for a diagram?
BlackeyedBandit said:
I've been reading XDA forums and modding my phones for years and now and at last I may actually have a contribution to make.
Alright all of you suffering with this enormous Bluetooth problem on the Amaze 4G that HTC pretty much refuses to acknowledge or address.
I too purchased an Amaze a couple months ago and was quite satisfied with its overall performance. That is until I received a Bluetooth ipad game controller and set of S9-HD Bluetooth headphones for my birthday. Then the nightmare began. Constant signal loss. If I were trying to text someone the sound would cut out on every key press. The ipad game controller would lose connection before getting through level one on Metal Slug Three played with NEO.emu (an awesome app by the way for its support of that controller). The in call signal quality was terrible and this was after trying multiple headsets. I read about a foil trick to correct this problem but never once found a tutorial on how to do it and the Bluetooth antenna prongs often spoke of were never actually pointed out anywhere. I looked all night for a diagram that would indicate which ones they are. I am guessing the they are the ones on the upper left. Not the top two immediately above the camera. If I am mistaken please make haste to correct me as it will determine the solution I detail. I had to guess I could find no real confirmation of this as they are both top left. Would someone send me a picture of the actual phone with the backing taken off and indicate which leads are to the Bluetooth antenna? As soon as I can confirm this I will post the fix.
I design and repair custom PC's in my free time for the elderly, disabled, and low income and I used that background to do a little experimenting the result was two more 4G bars in my basement and the the headset cutting out once during a three paragraph text. In game sounds were flawless and in call performance was perfect without a single cut out of signal.
As soon as someone discloses where those actual Bluetooth prongs are. I will post the how to and materials needed to perform this very successful solution. Not a 100% but 90% which is certainly better than the 20% us Amaze users have been putting up with.
I'd also like to thank all the developers for all knowledge and effort that goes into making all the cool enhancements and themes I had on my old HD2 and am now leaning how to apply on the Amaze. Hours of fun. You are all very much appreciated and Keep people like me learning new things.
Oh, I am running NRG's latest Aug 6, 2012 ICS Themed ROM release for the Amaze, Stock Kernel, 4EXT (the best!) S-ON, (Bricked my first Amaze with S-OFF).
As soon as I get confirmation of the antenna location and do a little more testing I will post the fix right here (next week or two). I don't want to look like an idiot or give misinformation if I have it incorrect or cause any damagage to anyones phone.
Click to expand...
Click to collapse
Still Still No Adequate Solution to Amaze 4G Bluetooth Issues.
badgerdave said:
You are right...I could not find anything showing a diagram or pic of where the antenna is/are located. Hopefully somone will provide you with something. Have tried emailing HTC and outright asking for a diagram?
Click to expand...
Click to collapse
Me too. I asked them for a service manual as I am a PC technician to let me figure it out but just like Toshiba laptops. Not a chance.
Update: Unfortunately my Bluetooth antenna mod/fix seems to only have solved the connectivity issue indoors as my headset still cuts out every few seconds outside and drops calls like crazy. I feel as though we've all been suckered by HTC as they will neither let us exchange for a smartphone that works properly or provide a solution to those of us who purchased this factory defective off the shelf phone.
I will still continue my efforts to find a way to enhance the antenna but I will probably never buy anything from HTC again seeing as how they've chosen to not deal with and dodge this widespread problem. T-mobile is no longer selling the Amaze that was the Sales person's response when I told them they were selling a defective product today at one of their stores, However, on the T-mobile website they are giving them away for free with new contracts. Those poor unfortunates that take them up on that offer who know no better.
I am going to demand a refund from either T-mobile or HTC but I doubt I will get one.
The salesman at T-mobile said "Nothing beats a wired headset." jerk!
Again I am sorry for jumping the gun but I was certain I had made a significant breakthrough in solving the Bluetooth problem on the Amaze.
BlackeyedBandit: I once read that the very first OTA is what messed up the Bluetooth on the Amaze. Unfortunately I am unable to comfirm this, or deny it. When I purchased my Amaze in Janaury 2012 my BT devices were being shipped to me. Before these devices got to me, my Amaze prompted me to do an update. I did it. When my BT devices arrived none of them had a range of more than 1-3 Ft. without static and/or terminated BT connection. When the ICS update came out the range increased to about 8-10 Ft.
I want to revert back the ROM that was first released to see if in fact it is better. But....I don't want to go through all those changes to find out it doesn't work any better. My phone is still completely stock...because I want to be able to return it soon. I love the phone and only want the BT to work in a manner that I have become accustomed to with HTC products. And to get the video stereo sound quality fixed too.
This is my second HTC device. The first was the HD2. It was a nightmare with WinMo 6.5 on it. I returned that thing 5 times and never got one that worked right. I eventually...with the help of xda members and others, learned the art of rooting. Once I got that down and rooted Andriod onto it, I was in love. I thought that even with all it's faults, HTC made an awesome device. I just needed to figure out how to "tune it up."
So I believed that the Amaze would be super awesome and looked forward to getting it. I feel let down because BT is a must for me. I'm not sure I will buy another HTC product either. This is the second time I have been burned.
BlackeyedBandit said:
Me too. I asked them for a service manual as I am a PC technician to let me figure it out but just like Toshiba laptops. Not a chance.
Update: Unfortunately my Bluetooth antenna mod/fix seems to only have solved the connectivity issue indoors as my headset still cuts out every few seconds outside and drops calls like crazy. I feel as though we've all been suckered by HTC as they will neither let us exchange for a smartphone that works properly or provide a solution to those of us who purchased this factory defective off the shelf phone.
I will still continue my efforts to find a way to enhance the antenna but I will probably never buy anything from HTC again seeing as how they've chosen to not deal with and dodge this widespread problem. T-mobile is no longer selling the Amaze that was the Sales person's response when I told them they were selling a defective product today at one of their stores, However, on the T-mobile website they are giving them away for free with new contracts. Those poor unfortunates that take them up on that offer who know no better.
I am going to demand a refund from either T-mobile or HTC but I doubt I will get one.
The salesman at T-mobile said "Nothing beats a wired headset." jerk!
Again I am sorry for jumping the gun but I was certain I had made a significant breakthrough in solving the Bluetooth problem on the Amaze.
Click to expand...
Click to collapse
This Piece of S was offered as a replacement to FIVE HTC Sensations, followed by a Samsung Galaxy S Blaze?, followed by THREE HTC Amazes...all in 11 months. WiFi doesn't work right. Bluetooth is practically useless on the Amaze, and worse when combined with WiFi. I've used it with three different high-end Bluetooth devices (Plantronics (best-I forget the name), Samsung's best, and the Motorola Sliver Elite. All work find with friends' phones when I've tried to troubleshoot. I've used several WiFi routers, access points, repeaters,etc...still the signals fluctuate, the sound warbles, and the calls get disconnected.
I have LITERALLY spent 49:25 hours on the phone with T-Mobile, and 16:30 hours on the phone with HTC. There has been no resolution. T-Mobile...offered...me...the option (get this...) to pay MORE money and get a different phone. I've spent countless hours on websites (I'm a software developer and systems integrator, so I know my way around) and was unable to get anything working. I've had to hold the phone...in my hand...about 1-2ft from my Bluetooth devices to get them to work at all.
The device is FULL of known issues. Bluetooth & WiFi being the only ones about which I care.
I've also gone back to the T-Mobile store twice (which dialing 611 or the 800-number tells you not to do...but after the HTC Sensation, and then the HTC Amaze issues, I had to choice but to go to the face-to-face supervisors and beg for help.) The first supervisor left T-Mobile and the second one "Jodi" was INCREDIBLY rude to me.
T-Mobile's 611/800-number "customer service" has three times not documented anything - and I was on the phone for 1:30 hours/each.
notperse said:
This Piece of S was offered as a replacement to FIVE HTC Sensations, followed by a Samsung Galaxy S Blaze?, followed by THREE HTC Amazes...all in 11 months. WiFi doesn't work right. Bluetooth is practically useless on the Amaze, and worse when combined with WiFi. I've used it with three different high-end Bluetooth devices (Plantronics (best-I forget the name), Samsung's best, and the Motorola Sliver Elite. All work find with friends' phones when I've tried to troubleshoot. I've used several WiFi routers, access points, repeaters,etc...still the signals fluctuate, the sound warbles, and the calls get disconnected.
I have LITERALLY spent 49:25 hours on the phone with T-Mobile, and 16:30 hours on the phone with HTC. There has been no resolution. T-Mobile...offered...me...the option (get this...) to pay MORE money and get a different phone. I've spent countless hours on websites (I'm a software developer and systems integrator, so I know my way around) and was unable to get anything working. I've had to hold the phone...in my hand...about 1-2ft from my Bluetooth devices to get them to work at all.
The device is FULL of known issues. Bluetooth & WiFi being the only ones about which I care.
I've also gone back to the T-Mobile store twice (which dialing 611 or the 800-number tells you not to do...but after the HTC Sensation, and then the HTC Amaze issues, I had to choice but to go to the face-to-face supervisors and beg for help.) The first supervisor left T-Mobile and the second one "Jodi" was INCREDIBLY rude to me.
T-Mobile's 611/800-number "customer service" has three times not documented anything - and I was on the phone for 1:30 hours/each.
Click to expand...
Click to collapse
Bro I think you have been extremely unlucky with the amaze. Although it does have some issues (capacitative light bleed, camera flash bleed, lower battery life than one would like, and slow development) most of these have been overcome to a great extent. If you are using a case you will have WiFi issues and possibly Bluetooth (I had WiFi issues with cover on, no BT issues) but that's fixible with a silver cigarette foil (or gold as well Iguess) placed in the battery back cover right beside the camera hole in the cover.
BlackeyedBandit said:
I've been reading XDA forums and modding my phones for years and now and at last I may actually have a contribution to make.
Alright all of you suffering with this enormous Bluetooth problem on the Amaze 4G that HTC pretty much refuses to acknowledge or address.
I too purchased an Amaze a couple months ago and was quite satisfied with its overall performance. That is until I received a Bluetooth ipad game controller and set of S9-HD Bluetooth headphones for my birthday. Then the nightmare began. Constant signal loss. If I were trying to text someone the sound would cut out on every key press. The ipad game controller would lose connection before getting through level one on Metal Slug Three played with NEO.emu (an awesome app by the way for its support of that controller). The in call signal quality was terrible and this was after trying multiple headsets. I read about a foil trick to correct this problem but never once found a tutorial on how to do it and the Bluetooth antenna prongs often spoke of were never actually pointed out anywhere. I looked all night for a diagram that would indicate which ones they are. I am guessing the they are the ones on the upper left. Not the top two immediately above the camera. If I am mistaken please make haste to correct me as it will determine the solution I detail. I had to guess I could find no real confirmation of this as they are both top left. Would someone send me a picture of the actual phone with the backing taken off and indicate which leads are to the Bluetooth antenna? As soon as I can confirm this I will post the fix.
I design and repair custom PC's in my free time for the elderly, disabled, and low income and I used that background to do a little experimenting the result was two more 4G bars in my basement and the the headset cutting out once during a three paragraph text. In game sounds were flawless and in call performance was perfect without a single cut out of signal.
As soon as someone discloses where those actual Bluetooth prongs are. I will post the how to and materials needed to perform this very successful solution. Not a 100% but 90% which is certainly better than the 20% us Amaze users have been putting up with.
I'd also like to thank all the developers for all knowledge and effort that goes into making all the cool enhancements and themes I had on my old HD2 and am now leaning how to apply on the Amaze. Hours of fun. You are all very much appreciated and Keep people like me learning new things.
Oh, I am running NRG's latest Aug 6, 2012 ICS Themed ROM release for the Amaze, Stock Kernel, 4EXT (the best!) S-ON, (Bricked my first Amaze with S-OFF).
As soon as I get confirmation of the antenna location and do a little more testing I will post the fix right here (next week or two). I don't want to look like an idiot or give misinformation if I have it incorrect or cause any damagage to anyones phone.
Click to expand...
Click to collapse
I too have the bluetooth connectivity issues. The only reference I could find to an "aluminum foil fix" was actually wifi antenna related. However, the thumbnail image is in this post by darll, 15th November 2011: (Wifi signal affected by phone case) in the Amaze 4g General forum.
BT MAC addresss
hasoon2000 said:
Nope. Mine works. I have a jawbone prime. No issues with connection.
Sent From My HTC Amaze 4G Via Someone's Room
Click to expand...
Click to collapse
Where does the bluetooth get it's MAC address from? (the one under settings/ about/hardware info/ bluetooth address)
chevycowboyusa said:
Where does the bluetooth get it's MAC address from? (the one under settings/ about/hardware info/ bluetooth address)
Click to expand...
Click to collapse
I think it is on the chip, but I'm not certain. It could also be programmed into the part of the phone firmware that is not touched when flashing.
I also want to report that I've had no issues with BT connectivity, and I have connected with about 8 headsets / handsfree over the past year.
My Amaze can get into a problem state with the BT, where the phone does not acknowledge a change in BT from off to on or vice versa. When this happens the phone starts to overheat, and I have to power completely down, and then power on again - at which point it will show the actual BT status. I've been on NRG almost from the start, so I don't know if this is a hardware issue or a ROM issue. I haven't had it happen in a while - I'm now more careful about turning on the BT (the problem seemed to happen when I was accidentally hitting the switch twice). Since I know how to avoid it, I haven't pursued any fixes.
Have you tried replacing the back cover? That seems like the most probable fix.
bluetooth
bluetooth problems?!
Hi, I have a rooted and s-off amaze with nightmare rom. everything is working but bluetooth. I can turn it on and switch to visibility but the problem is it can not find any devices and also it can not be found by others. I flashed some kernels but it did not work. please if u know a kernel that fixes bluetooth i can try it. thanks
BT
artur-x said:
bluetooth problems?!
Hi, I have a rooted and s-off amaze with nightmare rom. everything is working but bluetooth. I can turn it on and switch to visibility but the problem is it can not find any devices and also it can not be found by others. I flashed some kernels but it did not work. please if u know a kernel that fixes bluetooth i can try it. thanks
Click to expand...
Click to collapse
This have anything to do with it?:
http://forum.xda-developers.com/showpost.php?p=54112028&postcount=6

Liquid ICS 9/9/12 Bluetooth issue

HI all,
I can't post in the Dev section yet so I will ask here. I installed this ROM last night and it all went well except for today in the car while testing bluetooth I have no audio unless I switch the source away from Bluetooth and back (say, set it to Speaker then back to BT). I did a full wipe again and re-loaded the ROM and still have the same problem. I am using the .19 radio if that makes a difference and my car has the older (2008) Ford Sync system (2.1).
Is anyone else having a similar issue?
rpoitras said:
HI all,
I can't post in the Dev section yet so I will ask here. I installed this ROM last night and it all went well except for today in the car while testing bluetooth I have no audio unless I switch the source away from Bluetooth and back (say, set it to Speaker then back to BT). I did a full wipe again and re-loaded the ROM and still have the same problem. I am using the .19 radio if that makes a difference and my car has the older (2008) Ford Sync system (2.1).
Is anyone else having a similar issue?
Click to expand...
Click to collapse
This seems to happen quite a bit. It's a semi known issue from a number of cusom ROMs. Have never seen a solid fix for it except what you just described. Some people have this problem and need to competely turn it off and back on to get it to work! If it truely is a dealbreaker for you (it shouldn't be...not that big of a glitch), best bet is to stick to a ROM closer to the original tbolt software.
Its not that its a dealbreaker but it kind of defeats the purpose of using handsfree in the car when I would have to pick the phone up and switch BT inputs to get it working. I had a low Bluetooth volume problem with a rom before which was fixed with, I think, a different radio but I never had this one before. I noticed someone else posted the problem in the official thread so hopefully comes out if it. Thanks.
So this happens every time u get a call, or only every time you connect to the car?
I haven't received any calls yet while connected to BT but it happened when making calls and it seems once I do the toggle to get things working then it "sticks" and works thereafter. I haven't tried reconnecting while in the car to see if the fix would stick afterwards but this morning when I got into my car I tried making a call and it worked great first time and I know I rebooted the phone multiple times last night with doing backups of the rom, etc. Maybe it somehow worked itself out or maybe it's just an intermittent thing. I didn't change anything since the install.

AT&T HOX+ 1.19.502.1 Update... What's been your experience?

Alright, so I recently decided to upgrade my AT&T HTC ONE X+'s firmware to the latest 1.19.502.1 update. Ever since I got this phone, I've never really been 100% happy with it, so as soon as I saw an official update being rolled out I jumped at the chance! I re-flashed the original recovery, re-locked the bootloader and ran the HTC RUU pc executable, effectively putting my phone in a 100% stock state and fully updated.
So far I can say that the phone experiences less general app crashes than before. The Bluetooth Call audio quality issue is 100% fixed. It would also seem like the Google contacts syncing issue is gone too. AT&T Address Book app now works (I don't like it, I don't actively use it, but at least now it's a functioning app). And Power management & Battery life seemed to have improved ever so slightly.
On the other hand, the phone does seem a bit slower (apps take longer to load, some phone functions take a little bit longer to react, stuff like that). The distorted streaming via Bluetooth (A2DP) bug (not the same issue as the call audio) is still un-addressed. I've always experienced random Bluetooth connection interruptions, and with the update this hasn't changed. Another thing I was hopeful they would fix with the update and they didn't is the Automatic Time Zone option in the Date & Time settings menu (It will often not recognize my time zone - GMT -4:00 - forcing me to set it manually... no big deal, but still a bug none the less). There were no GUI/UI changes or improvements whatsoever. Also, I like to use Nova Launcher Prime, and for whatever reason I've found myself pressing the "back" button to exit some apps and it would return me to the Sense home instead of the Nova Launcher home (which is set as my default launcher). That last one is no big deal, but thought I should mention it just in case.
What about you guys? What has been your experience with it? Did you update OTA or through the RUU? Share your experiences here!
the only thing i needed from the update was fixing BT A2DP audio. Like you said, it is still broken. Highly disappointed. Hopefully a ROM will fix it soon.
The update broke a bunch of apps for me. Chrome, Google Search, and Google Drive no longer work, they crash on startup.
Other people have similar complaints, here: forums.att.com/t5/Android-Discussion-and-Support/HTC-One-X-update/td-p/3469653
This is a stock phone. So far the phone is pretty unusable without those apps.
Really annoying. AT&T hasn't said anything about it yet. Maybe I should contact HTC directly?
badtlc said:
the only thing i needed from the update was fixing BT A2DP audio. Like you said, it is still broken. Highly disappointed. Hopefully a ROM will fix it soon.
Click to expand...
Click to collapse
I hear ya!
djgh said:
The update broke a bunch of apps for me. Chrome, Google Search, and Google Drive no longer work, they crash on startup.
Other people have similar complaints, here: forums.att.com/t5/Android-Discussion-and-Support/HTC-One-X-update/td-p/3469653
This is a stock phone. So far the phone is pretty unusable without those apps.
Really annoying. AT&T hasn't said anything about it yet. Maybe I should contact HTC directly?
Click to expand...
Click to collapse
You can try to contact HTC directly, but from what I've read around in the forums, they aren't much help. Allow me to suggest you try running the RUU on your phone (you can download it from http://www.htc.com/us/support/news.aspx?p_id=529&p_name=htc-one-x-plus-att ). It'll fully wipe it, so make a backup of all your important stuff (contacts if they aren't cloud synced, pictures, Angry Birds scores, etc) and then run the RUU. After the initial setup, re-download/install all your main apps and see how that goes. If you do get to do this, please post here if there was a difference in your phone's behavior. (Hope that helps)
I really honestly haven't had any issues with my phone since the OTA update... I still lag on playing a simple 2D game Drag Racing" but runs butter smooth when playing 3D games.. WTH?.. Really annoying to me... but then again, it lags even when I'm using my Nexus 7, yet runs lag-free and smooth on my Pantech Burst? Explain that one.. lol..
But all in all I've noticed a lot of small enhancements with the update. Now if they can just fix the game play of Drag Racing app.. lol..
I haven't noticed anything significant either way. If I didn't do the update myself, I don't think I would know there had been one. I do have to say that I never experienced problems playing music over BT, and I use it in my car, at home, and with BT earbuds. Maybe it's because I'm using PowerAmp.
pazzo02 said:
I haven't noticed anything significant either way. If I didn't do the update myself, I don't think I would know there had been one. I do have to say that I never experienced problems playing music over BT, and I use it in my car, at home, and with BT earbuds. Maybe it's because I'm using PowerAmp.
Click to expand...
Click to collapse
The problem is still there with poweramp. It is a bitpool setting for connection between the phone and BT speaker devices. Some people just don't hear it even though it is there. I have a few friends who are now on JB thanks to recent updates and they have the same issues but they don't seem to hear it. I can hear it plainly though. One of them I could get to hear it but he doesn't care and thinks it sounds good enough for him.
sledgeharvy said:
I really honestly haven't had any issues with my phone since the OTA update... I still lag on playing a simple 2D game Drag Racing" but runs butter smooth when playing 3D games.. WTH?.. Really annoying to me... but then again, it lags even when I'm using my Nexus 7, yet runs lag-free and smooth on my Pantech Burst? Explain that one.. lol..
But all in all I've noticed a lot of small enhancements with the update. Now if they can just fix the game play of Drag Racing app.. lol..
Click to expand...
Click to collapse
Well, I haven't tried that particular game, but try this and let me know if it works for you. Go to Settings\Developer Options\Advanced\Force GPU Rendering, and turn it on.
Disappointing feedback. I work from home and have a Plantronics Savi 700 series headset. My HOX+ is connected to the Savi via Bluetooth, and if I make/receive a call on my HOX+ the call skips/distorts for the first 5 seconds or so before stabilising. Is that a known issue?
EDIT: to clarify, I am not using the headset when making/receiving the call in my example.. it's merely just connected via Bluetooth at the time I use my cell phone.
callsignapollo said:
Disappointing feedback. I work from home and have a Plantronics Savi 700 series headset. My HOX+ is connected to the Savi via Bluetooth, and if I make/receive a call on my HOX+ the call skips/distorts for the first 5 seconds or so before stabilising. Is that a known issue?
EDIT: to clarify, I am not using the headset when making/receiving the call in my example.. it's merely just connected via Bluetooth at the time I use my cell phone.
Click to expand...
Click to collapse
That hasn't been my experience receiving calls (although making them, the first ring does sound louder and coarser than the rest) but there have been some posts here on the forum from people describing a similar issue (since way before the update). Apparently it's either an inconsistent issue, a bug that only affected a few handsets, or an accessory hardware specific issue (eg. compatibility issue with specific bluetooth devices).
badtlc said:
the only thing i needed from the update was fixing BT A2DP audio. Like you said, it is still broken. Highly disappointed. Hopefully a ROM will fix it soon.
Click to expand...
Click to collapse
When u say BT audio A2DP that to ke means audio controls over BT. Well this has always worked from the start for me on stock and now custom roms. Now if I use a "wired" headset then no, audio controls do not work. All I can do is deal with phone calls and play/pause music. Cannot turn volume up or down or change tracks while using a wired headset. This from my understanding is a "hardware" issue. Now as far as actual BT is concerned, every aspect has worked perfect for me since Steve007 has fixed it for us. Also it has been claimed the new ATT update fixes this BT audio quality issue to an even higher degree than what Steve did so ultimate BT fix now on new ATT update.
So what is the BT audio problem now still not working?
Sent from my HTC One X+ using Tapatalk 2
deeznuts said:
When u say BT audio A2DP that to ke means audio controls over BT. Well this has always worked from the start for me on stock and now custom roms. Now if I use a "wired" headset then no, audio controls do not work. All I can do is deal with phone calls and play/pause music. Cannot turn volume up or down or change tracks while using a wired headset. This from my understanding is a "hardware" issue. Now as far as actual BT is concerned, every aspect has worked perfect for me since Steve007 has fixed it for us. Also it has been claimed the new ATT update fixes this BT audio quality issue to an even higher degree than what Steve did so ultimate BT fix now on new ATT update.
So what is the BT audio problem now still not working?
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
What you're referring to are Media and Call control over bluetooth (First part of your statement) and Bluetooth Call Audio specifically (second part of your statement. This is what Steve007's fix addresses and the new update fixes). The bug badtlc and I mentioned is specifically when streaming Music or Video Audio through bluetooth (basically any type or audio that isn't phone call related). The audio streams just fine, but with a nasty distortion in the high frequencies. Many people just don't seem to mind the distorted sound because they just don't seem to identify it. If you compare the Bluetooth audio quality vs the direct audio quality (like with an Aux cable) you will hear a noticeable difference.
bluetooth volume level issue after upgrade
I've been having the issue of too low volume on bluetooth calls in my car since the upgrade to 1.19.502.1 I used the RUU from HTC site to do the upgrade and reinstalled everything. I have to literally turn up the bluetooth volume all the way up in my car and the people on the other end complain that I'm not loud enough. Did anyone else notice anything like this?
The first time I did the OTA on a stock, locked, not rooted HOX+ I noticed some improvments, I'm not really sure might have been placebo effect, but it did break my Wi-Fi. It would stay stuck on "Turning on Wi-Fi" the slider would be slid to the on side, but say off and be grey and unaccessable. Well I had to get it replaced under warranty, the headset speaker was dead too but that happened before the update, and it came with 1.15 and I want to know how common of a problem my experience was I know of at least a couple people who have had the same thing and I'm not sure I want to try the update again on this one and have to go through replacing it again.
i dont see any updated
i am using ATT HTC onex+ on pay as you go service, my phone never saw any updates, tried to change date as many have suggested, tried *#*#checkin#*#*, tried to look up for update manually from settings, but none seem to work, my phone is in stock condition with no root/unlock etc.
any ideas?
bhavik_ht said:
i am using ATT HTC onex+ on pay as you go service, my phone never saw any updates, tried to change date as many have suggested, tried *#*#checkin#*#*, tried to look up for update manually from settings, but none seem to work, my phone is in stock condition with no root/unlock etc.
any ideas?
Click to expand...
Click to collapse
Download the update directly from the HTC website.
badtlc said:
Download the update directly from the HTC website.
Click to expand...
Click to collapse
i could, but wouldn't that wipe the phone off? i'll have to re-install everything back. such a pain on 64gb phone
bhavik_ht said:
i could, but wouldn't that wipe the phone off? i'll have to re-install everything back. such a pain on 64gb phone
Click to expand...
Click to collapse
The official updates from HTC never wipe anything from the device. They just UpDate the OS. There might brake an app and very rarely, but that's just when changing the SW version, due to app incompatibility with the new OS vers. That's just my experience with HTC over the last few years and the last few devices.
Best of luck.
Pushu.X
Sent from my HTC One X+ using Tapatalk 2
pushu.x said:
The official updates from HTC never wipe anything from the device. They just UpDate the OS. There might brake an app and very rarely, but that's just when changing the SW version, due to app incompatibility with the new OS vers. That's just my experience with HTC over the last few years and the last few devices.
Best of luck.
Pushu.X
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
can you point me to where/how can i download and apply the update?
i just saw the article below, it had link for full ROM for download, thought it will wipe the current content. correct me if i am wrong.
androidpolice.com/2013/04/16/att-one-x-updated-to-v1-19-502-1-with-bug-fixes-galore-full-rom-download-available/

Categories

Resources