Bluetooth phonebook download slowing down. Reset bluetooth without a hard reset? - Touch Pro CDMA

I'm pairing my Touch Pro with a 2010 Kia Forte. Every time the phone connects, the car downloads the phonebook. After every call, the car decides to download the phonebook again. It's an annoying feature because you cannot issue any commands to the car to make any more phone calls until the phonebook is completely downloaded.
It's not a big deal initially, because the download only takes maybe 20-30 seconds. The problem is that over the course of time, that download gets longer and longer and having to wait 5, 10, eventually 15 minutes between making calls is a pain.
I'm on my second Touch Pro which I have owned for about 6 weeks now and I'm up to a 2 or 3 minute download. My previous phone showed all these same problems. Deleting the pairing on the phone and car and recreating it do not fix anything. Turning off Bluetooth and soft resetting the device does not help either. The only solution I have found that works is a complete hard reset of the phone and then recreate the pairing.
Does anybody know of a cache I can clear or a way to restore Bluetooth back to it's original state or any other solution beyond a hard reset? Having to hard reset the phone every couple months and get it back the way I like it is getting to be a pain.

I had the same issue with my Kia Sorrento. Sort of. While it would only need to download once each time i got in and turned the key, it was ungodly slow. I have have a Touch Pro (Raph800) on alltel/verizon. After upgrading to wm6.5 the process only takes about 30 seconds now. I am not sure, but make sure you have beam turned on. It was on by default after the upgrade and i just left it that way. Now its done before I get out of the driveway.

I have a feeling the cache getting full is the one in the car and not in th phone... See if there is any way to clean that.

The only thing I can do in the car is completely delete the pairing. This does not help the issue, because it is still slow when I create the pairing again. When I got the car brand new off the lot, the dealership said they've never noticed a phone sync so slow. The phone was a couple months old at that point and I just assumed that's the way it was meant to be. It wasn't until the Touch Pro started to develop keyboard issues and I decided to do a hard reset that I found out the sync time could be remarkably improved. I'm now on my second Touch Pro because of that loose keyboard cable which seems common to the model. This new phone would sync quickly when it was brand new right out of the box. I thought maybe I would be lucky this time and not experience the same issues, but this one is back to syncing slow again. The car just says "Downloading Phonebook" for about 5 minutes after connecting, and after any call. If I dial a contact on my phone it will go through the car system, or if I receive a call it will generally show the caller ID on the car's screen. I just can't voice dial any calls until that phonebook is completely downloaded, which defeats one of the main points of having a hands free system. I've tried also deleting the partnership in activesync to take off all the data off the phone and then recreate that it to see if maybe the data on the phone is somehow the culprit, but that hasn't helped either.
I should mention that I am running the stock WM 6.1 that came with the phone. I have a feeling that like Thelgord, WM 6.5 might speed things up. The only thing is I'm concerned this keyboard will give out on me too and I've been hesitant to attempt any upgrades while the unit is still under warranty. It's using a non-branded stock rom, because it comes from a local cellphone company as opposed to any of the big name carriers, and i haven't seen anything out there for WM6.1 that isn't branded as carrier-specific if I need to return this back to a stock rom someday. If I knew that 6.5 would solve my problem, I would do it anyways as fixing the keyboard on my own looks pretty simple.
I've also never flashed a phone before, so I'm worried that I will immediately brick it. All the tutorials seem to be assuming your phone is from one of the major carriers.

Similar issues..different phone
I'm a noob so I'm attempting to follow the rules, feel free to correct me if this is the wrong place to post this question.
I have a 2011 Kia Sorrento (which I love) and I cannot seem to get my unrooted HTC Glacier (MyTouch 4G on T-Mobile) to properly pair. Address book issues, Will not play pandora or spotify through speakers (though spotify thinks it is doing it properly) Cannot actually make a phone call EVER. I love my car and really want this feature to work. My DH's Rooted Phone (Same model as mine, were purchased together) works just fine. (He thinks this is the best car ever for riding shotgun...I want my radio back...)
HTC Glacier
Software version 2.2.1
App version 5.3.7
T-Mobile

Related

Bricked Hermes. Anyone have it go like this?

First I should mention my 8525 was a referb and I had it for about 3.5 months.
first thing I noticed it that it would drop cennection with my wifi. I thought (and still think) it was likely do to my older belkin wifi router. Did notice this with other connections.
them my software would do strange things... One app would suddenly open when using another or the app I was using would suddenly close.
On ocasion I would miss a call and get a voice mail with out ever hearing the phone ring. At first I thought maybe I waspressing a button sendinf call to voive mail by accident as the phone was in it case. Thi started to happen more frequntly. THen I noticed that my phone was losing all reception, some time for a few seconds sometime for much longer. I then on ocasion after a reset it wou sho "No GSM", another soft reset would usually cure this. But it becase more prevalent.Tried to flash to the official AT&T rom to get the latest radio, but still would lose reception. well, flashed between Official AT&T rom and vp3G a few time but now I get "No GSM" all the time.
Do you thing it fixable? Perhaps it's a redio hardware issue. I would think ir it's software it would right after a flash. Mine seem to pregressivly gottem worse. Make me think it was hardware going bad.
Lesson learned: Stay away from Referbs and their 30 day warrenty.
Final solution: Gota new accout and a 8925 (Tilt) from newegg. Arrives today!
Oih dude.. Good Luck with that brick..
WIKI FTW!
forgot to mention one other issue i was having. I had two AOL e-mail accounts set up and have had about 4 occasions where they would just disapera. I tried to set them up again but it would tell me "that name is already in use". This happended prior to it going to hell in a handbasket (and even after when I was relegated to using wifi only).
Good new is I revieved my Kaiser yesterday and it rocks. It runs so much better even witht the defult AT&T bloatware ROM. But now I'm a little afraid to flash a new ROM, One bitten twice shy!

HD2 stuck at logo boot up!

Every time I reset or turn on my fone after shutting down, it will stuck at the logo boot up. It wasn't like that when I first bought the fone. Now it's getting worse and worse since the issue happens so frequently.
I have to take out the battery and put it back, then wait for about 3 to 5 mn before I turn the phone on.Then it would boot up as usual.
Is there anyone facing the same issue as I am? Any suggestion guys?
Are you experiencing excessive heat when this occurs? Also, can you give more info such as: does this happen only after recent charging or does it ever happen when the phone has been turned off for a long time? Was there any recent apps you installed or ROM changes when this started happening? Was there any potential damage done to the phone -dropped it, got it wet, or microwaved
When you say frequently, does that mean every time you restart? every other time? every five times?
Lastly, do you have any other issues/symptoms other than freezing at startup? Does the phone ever freeze during normal use?
i'd suggest you do a hard reset of your phone (hold down both vol up and vol down keys while powering on/resetting). that should fix the problem. if the problem still persists, it's probably some hardware faults.
Me too
My HD2 just started doing this too. It was fine for 7 weeks I have owned it. However, as described in this by OP, when doing soft reset would it would also get stuck on bootup logo. I'd have to remove the battery for a few minutes before it would bootup.
However, my HD2 also crashes and upon reboot then get stuck on bootup logo. It appears to crashes randomly eg not with any particular program or action.
I figured it was software issue so did hard reset. This worked fine. After hard reset the only software I loaded were Total Commander and Cookie Editor.
After Cookie Editor install I did soft reset and it got stuck on bootup logo. : (
So I did another hard reset but it hung up again upon reboot on bootup logo.
This appears to be a hardware issue. But has anyone else had same issue?
T-Mobile HD2
Stock ROM
Purchased July 6 2010 from Expansys
yes i am experiencing the same problem and i have uploded a video on youtube showing this! Yes my phone heats up when this happens..
Hi. I got this problem for quite sometime and am so used to taking out and putting back and taking out and putting back the batt.
But now I have another prob: my ringtone suddenly went soft and I now have to keep myself alert all the time to see if there's any incoming call or SMS.
I would like to do a hard reset but the question is: will it set my phone back to the stock ROM or still retain the updated version - 1.66.707.1?
Thanks in advance.
Stormrider75 said:
Hi. I got this problem for quite sometime and am so used to taking out and putting back and taking out and putting back the batt.
But now I have another prob: my ringtone suddenly went soft and I now have to keep myself alert all the time to see if there's any incoming call or SMS.
I would like to do a hard reset but the question is: will it set my phone back to the stock ROM or still retain the updated version - 1.66.707.1?
Thanks in advance.
Click to expand...
Click to collapse
It will retain whatever rom you are using
Htc Hd2 vodafone UK
HD2 issue
After some more searching it appears this is not uncommon for HD2. Its not clear to me if it is specific to T-Mobile HD2 or HD2 in general.
It appears to be a hardware issue. Although that is not 100% clear either. I find it hard to distinguish what some people report as 'freezing' which i believe is different to the issue described in this post which is 'hanging up' or 'getting stuck' on boot up screen - in my case it is the T-Mobile 'stick together' pink and white screen/logo.
(The 'freezing' issue that i believe is different to this 'getting stuck on bootup logo' issue appeared to have been resolved iwth new T-Mobile ROM - and I never experienced it on my HD2).
The resolution for getting stuck on bootup screen issue described here appears to have been to exchange HD2 (although some people exchanged up to 6 times and keep getting same issue!)
I think it is important to note that my HD2 performed fine for 7 weeks with lots of soft resets, hard resets, and lots of software installs (though no ROM reflashing) but within last week or so, start crashing randomly, then upon reboot get stuck on bootup screen/logo. This also became more frequent as time progressed. After doing hard reboot, the issue is now acute, eg it gets stuck on every reboot, and crashes more often.
This leads me to think some hardware has failed or degraded and is getting worse, maybe a connection/soldering etc?
However, is there any possibility that a ROM could 'degrade'? Can a ROM have a setting that is modifiable? (I know it is 'read only memory' but is it really?)
Anyways, love to hear from others on this issue.
Same problem here. Bought my HD2 in june. Cooked my own rom with Chucky's kitchen. Flashed different radios, hard resets, task 29 etc. Absolutely no problem. Worked fine for several weeks. But sometime it begun to freeze, auto resets, stuck at boot logo. It was getting worse. Even flashing stock rom it hungs at boot logo.
Now my HD2 is out for repair. Now waiting for returning. Hope they will change the motherboard.
several people have had their motherboards replaced and that has seemed to fix it for them. You'll probably have to fight with htc or your carrier, but should be able to get it replaced.
Hi guys. Another question:
I'm considering doing a hard reset. How do I store my messages before doing it? I can't seem to locate the folder that keeps all my messages.
TIA.
HD2 is an odd one
Thanks for replies. I really don't want to send it in .. but it will probably be the only way to resolve the issue. It will cost me courier there and back, and $20 'triage' fee .. total cost to me will be ~$100 just to have them look at it. Price of doing business I guess.
Anyways, I realized that one of my issues was that it was crashing when syncing. A little digging reveals that HTC Sense does something to all contacts when syncing first time putting a bit of html in contact notes field (weird but it is true .. its their way of reminding you bought an HTC phone?) So once I got it up and running, I disabled Sense and syncing went fine, no crashing.
(Btw, Sense also appears to do something with SMS msgs too so if you have lots it crashes on due to this reason too).
However, even with plain Jane MS today screen (eg not using Sense) it still crashed once on sync and again when listening to radio. Both times had to remove battery for few minutes before it would reboot without getting stuck at bootup logo.
But so far it seemed to be working 'better' without using Sense.
So, I re-enabled Sense to see what would happen and over a day it has crashed twice. I am going to see how it behaves for few days before sending it in as RMA repair.
Still, important point is that it was ok for 7 weeks, and then started crashing, more and more, even after hard reset, though some of issues may have been due to Sense (which is reported by many users).
It is still not a 'normal' thing for a $700 consumer device to have such erratic behaviour. So, given others have exchanged crashing handsets for new handset that has no issues points to underlying hardware issues as suggested above eg motherboard.
As comparison I also have HTC Diamond 2 which has been rock solid for 2 years of continuous use even with lots of software install, tweaking, reg hacks, etc.
Stormrider75 said:
Hi guys. Another question:
I'm considering doing a hard reset. How do I store my messages before doing it? I can't seem to locate the folder that keeps all my messages.
TIA.
Click to expand...
Click to collapse
I don't text a lot so i just hard reset without saving .. but do a quick search on on XDA for SMS backup or PIM backup .. during my searches I am sure i have seen a couple of utilities that do what you want.
genoki said:
I don't text a lot so i just hard reset without saving .. but do a quick search on on XDA for SMS backup or PIM backup .. during my searches I am sure i have seen a couple of utilities that do what you want.
Click to expand...
Click to collapse
Thanks. Btw I read before we can actually 'disable' Sense.
How do we do that?
Sense - go to Today
Go to Start - Settings
- iI you see the black HTC Settings (has 'Personalize' on top of items) then go to Menu and select 'All Settings' (this will show Windows Mobile's Settings. HTC Sense 'Settings' doesn't everything Windows Mobile Settings has or shows it differently)
- Select 'Today'
- Select the 'Items' tab in Today
- Check 'Windows Default' and click OK in top right.
This will 'swap' out HTC Sense 'today' with Windows Mobile standard Today screen and voila you will have 'disabled' HTC Sense and you are back to using Microsoft's Windows Mobile 6.5 version of Sense (not anywhere near as useful or neat-o to look at but hey they are pretty happy with it )
genoki said:
However, even with plain Jane MS today screen (eg not using Sense) it still crashed once on sync and again when listening to radio. Both times had to remove battery for few minutes before it would reboot without getting stuck at bootup logo.
But so far it seemed to be working 'better' without using Sense.
So, I re-enabled Sense to see what would happen and over a day it has crashed twice. I am going to see how it behaves for few days before sending it in as RMA repair.
Click to expand...
Click to collapse
Just by disabling Sense is not going to make it work. I had this problem with my HD2 also and without using Sense it seemed to be working (there were fewer crashes), but only for few days. My HD2 was getting worse day by day - it was not crashing only if it was not touched (it was crashing just cycling between Sense tabs or by initiating a call).
At repair center they told me (after three weeks of waiting) that the motherboard must to be changed.
Is it possible to damage it by flashing custom ROMs?
For me, this problem appeared after just one month of usage. I was flashed some custom ROMs.
Now, I have a new HD2 but I'm affraid to flash a custom ROM (at least in the near future).
I have my HD2 back. Took me 2 weeks, the repair center changed the motherboard and got an new IMEI.
Now all is working, no more stuck at bootlogo.
But i'm on stock rom (1.66) with 2.07 radio. No way to run Android with this radio. Hmm...
axman79 said:
Is it possible to damage it by flashing custom ROMs?
For me, this problem appeared after just one month of usage. I was flashed some custom ROMs.
Now, I have a new HD2 but I'm affraid to flash a custom ROM (at least in the near future).
Click to expand...
Click to collapse
I'm afraid as well to flash any custom rom now. For Android i need to HSPL and flash a 2.08 radio or greater to use it. But i'm stick on stock rom for sure.
I want to know as well if it possible to damage it by flashing customs roms ?
As i stated earlier, i flashed plenty of roms, doing task 29 etc., in the end stuck on bootlogo.
Thanks for the feedback on your repairs axman79 and Kalip. Btw, aside from courier cost there and back, did you have to pay the $30 'triage' fee or whatever they call it? Also, did they challenge your observations at all or did they just replace motherboard without question?
Yah, disabling Sense hasn't stopped my HD2 from crashing eith. Without using Sense it crashed several times while using Opera and more than a few times while syncing over the past three days. Also, it still gets stuck on reboot often, requiring battery to be removed for few minutes before rebooting.
So, guess I will send my HD2 in for RMA repair too (and wait for up to 3 weeks) and hope I get a functioning device in return.
Interesting though I didn't flash my HD2 but it went from 'good' to 'bad' in similar way that your two HD2's. From reading other posts around here on XDA and elsewhere it appears that HD2 motherboards fail with surprising frequency and for variety of reasons.
Would be nice to know if HD2 motherboards are unusually delicate and something physically breaks, or if there is some electrical operation, eg charging it on USB or unusual combination of button pushes that shorts something out?
The fact that battery has to be removed for few minutes in order to get thing to reboot hints that something requires charge to dissipate eg a component somehow 'locks up' which causes crash, and needs to be discharged by removing battery?
genoki said:
Thanks for the feedback on your repairs axman79 and Kalip. Btw, aside from courier cost there and back, did you have to pay the $30 'triage' fee or whatever they call it? Also, did they challenge your observations at all or did they just replace motherboard without question?
Click to expand...
Click to collapse
Was flashing stock rom with stock SPL, was at the shop where i bought it and they send it. I told them it stucks at bootlogo. Repair center changed motherboard without any question. Cost me nothing.
genoki said:
Also, it still gets stuck on reboot often, requiring battery to be removed for few minutes before rebooting.
Click to expand...
Click to collapse
Ja ja, same here.
genoki said:
So, guess I will send my HD2 in for RMA repair too (and wait for up to 3 weeks) and hope I get a functioning device in return.
Click to expand...
Click to collapse
Yes you will, but dont forget to flash back stock rom regarding SPL !
genoki said:
Interesting though I didn't flash my HD2 but it went from 'good' to 'bad' in similar way that your two HD2's. From reading other posts around here on XDA and elsewhere it appears that HD2 motherboards fail with surprising frequency and for variety of reasons.
Would be nice to know if HD2 motherboards are unusually delicate and something physically breaks, or if there is some electrical operation, eg charging it on USB or unusual combination of button pushes that shorts something out?
The fact that battery has to be removed for few minutes in order to get thing to reboot hints that something requires charge to dissipate eg a component somehow 'locks up' which causes crash, and needs to be discharged by removing battery?
Click to expand...
Click to collapse
I want to know as well !
hey guys. I am so glad I found this post! I have exact same issues ith my HD2, it's driving me nuts.
I kept sort of log and described my problems in this post: http://forum.xda-developers.com/showthread.php?t=712729
I think I have to send my HD2 for replacement or repair.
Can you please tell me how can I get my phone fixed/replaced?
I got the US T-Mobile version, but I don't have account in T-Mobile. Can I deal directly with HTC? Where do I have to call to get RMA number etc.
I would greatly appreciate your help!
KML

[Q] HD2 turns off automatically!!!!!????

HELP!!!!!! My HD2 turns itself off automatically after about 15-30 minutes of running Android OS. I have HD2Froyo_V2.1.7z. Also installed HSPL3_PKG from XDA and Kumar's TMOUS C5 Premium V2.6. I solved my robot voice and no sound problem. Only thing left is getting it to actually stay on while running in Android. Any help would be greatly appreciated!!!!!!!!!!!!
Hi I have a similar problem. It happens only when I have the phone in my pocket.
My theory is that I press the shutdown button when held in the pocket and thereby turns off the phone. The best thing would have been if the feature was removed when it is in the locked position ... Do you think we have the same problem?
I'm running Duttys rom (v8) and radio 2.10.50.28_2 (HSPL 1.66)
No clue....?????
I am very new to the whole "hacking my phone" scene, if you will... I was pleased with myself for actually getting it to boot and run for a decent amount of time. My phone will just cut off (when im running Android OS), when it's in my hand, when im playing a game, when im doing just about anything in Android. It works perfectly fine in Windows, no probs what-so-ever. I had an issue with connecting to T-Mobile's 3G network, but i think i resolved that. For the most part everything works great, only prob is that the phone just resets on its own. Still very confused as to why..... HELP!!!!!!
I'm no expert on this either. Your problem sounded exactly like mine, just had to ask if it could be so in your case also.
You know what they're asking for technical support? Is the power cable in? Hehe, sometimes it can be very simple things that are wrong.
One thing that struck me was that perhaps you should look over the radio version. There are a few threads on XDA about different radio versions work with android.
Consider what I wrote at the beginning, I'm no expert
Alright. do this and it will work.
1. format your card with your phone to fat32. you need to do this. (yes again)
2. HPSL3 your phone, it seems that once you do it you wont have to do it again but this are the exact steps I did before getting the hd2 android for more than 72 hrs using 99% of the phone. (remember it is always better to have stock android)
3. I am using Chucky ROM but is HORRIBLE ugly and nasty. ROM your phone to Chucky rom or Miri Rom.
4. get Matt C Froyo version of android.
Install it. reboot. tap on CLRAD and then HRET and it will work.
I have an auto loader now it seems they all work but some are nicer. oh by the way you will use your SD card as it was th phones memory with this build, meaning the Windows version of the HD2 is safe for when Windows 7 gets a release and you decide to send to hell android as I will.
I was wondering if anyone found a solution yet for disabling all buttons except the unlock button.. this is the reason why I have been calling ppl without actually noticing I pressed keys while my phone was in my pocket. also it has shutdown few times. sucks because I miss calls that way.
HectiQ said:
I was wondering if anyone found a solution yet for disabling all buttons except the unlock button.. this is the reason why I have been calling ppl without actually noticing I pressed keys while my phone was in my pocket. also it has shutdown few times. sucks because I miss calls that way.
Click to expand...
Click to collapse
I would really like to have a solution to this also. The problem is that you get an option to switch to airplane mode or turn off the phone when you long press endbutton. Even if it is locked. I want to see that when you are only in unlocked mode, the shutdown menu shows. I really hope someone fixes this.
thanks for your help, i tried doing this but that didnt help, i flashed my rom with the energy rom and the lastest mdeejay froyo 3.4. Is there a way i can fix the phone shutting down itself? to turn it back on, i have to take the batter out and turn it back on all the time.
any help pls?
Hi, i seem to have the same problem, android works perfectly when all of a sudden with no reason my phone reboots to winmo. And it has nothing to do with pressing buttons. I have it on a desk and it shuts down. I have noticed that it varies from build to build. Mmce v2.0 would cut down every few seconds. Mdeejay's builds were the most stable, but had no camera. The one I'm using right now "bangster's 1.5" with camera shuts down 1-2 times per day. I can live with that for now. PS: I would like however to thank all the developers for their hard work.
Sent from my HTC HD2 using XDA App
Have you tried running a non-undervolted kernel? Both Hastarin and Michyprima offer non-undervolted alternatives.
http://forum.xda-developers.com/showthread.php?t=787588
Release r7.1 Alternative - as above but without Overclocking, Undervolting, or AXI. NOTE: requires nand_boot=0 in your startup.txt cmdline, see README.txt for details.
http://www.multiupload.com/23ADQU06GU
Click to expand...
Click to collapse
Brgds... /Tubgirl
hd2 turns off I have a solution
first off this isnt a software issue at all. with much time devoted to figuring out the problem with my hd2, it randomly shuts off whenever it wants...well its simply a hardware issue. but nothing to has to do with overheating or anything like that. the battery pins are very flimsy and loose connection to the battery itself very easily. use a piece of paper and make sure its the length of the battery. and fold the paper to create a wedge in the top of the phone and the battery. place the paper wedge halfway in front of the battery as you are putting it in the phone and then gently force the battery into to place. this will create a secure connection between the battery and the pins. i promise it'll work...its just to keep the battery from bouncing and loosing connection.
its just a poorly designed battery casing not being snug enough to hold a connection with the battery. let me know if you are confused on how to do it or anything.
I'm having similar issues and I'm almost sure it's overheating.
Install Hastarin's 7.7alt version kernel which isn't overclocked on startup. This will make your phone a lot cooler after booting. Then install SetCPU and current Widget.
run SetCPU and set a profile to clock down the CPU (245-400mhz) when the Temp is above 98 degrees and to give you an Audible beep
run Current widget and pay attention to the temp. then run something like angry birds that will heat up your phone.
If it crashes at a certain heat, set SetCPU lower.
Another method to diagnose is to run Angry Birds like normal and see how long you can play before it crashes, then put some ice cubes in a double plastic bag and hold it against the lower back of the phone while you play again (after reboot of course). See if you can play longer.
I'm trying to figure out if the HD2 is still under warranty because this is a huge hassle.
EDIT: Just got off the phone with HTC TmoUS repair division and the phone is still under warranty and will be repaired at no cost except one way shipping. I'm going to stress test it in WinMo to make sure they will be able to replicate the problem and I'll ship it tomorrow. I just need to find something that's as CPU intensive as Android.
Does anybody have a solution to this? None of these answers work.
Automatically reboots
I have similar problems with my T-Mobile HD2; it was fine when I first got it (I lined up before the store opened on the day it came out) and am not running Android. It will periodically turn off and go back on again for no reason. I read somewhere that old SIM cards could be a problem and was wondering whether this was the issue as my SIM is more than 10 years old.

[Q] Bluetooth stuck in call mode after connected to car

I've been searching around for a solution to this issue for a long time, but seems like I'm the only one suffering from it.
My Telus S3 works great with my 2005 Acura TL for a few weeks, and then suddenly, after I go into the car, the bluetooth will connect automatically, but the Handsfree Links system within the car will stuck, showing a "In Use" message on the HUD, as if I'm making a call. And the only voice commands available are: Transfer, Send, Go back, Cancel, none of the commands go anywhere, even the go back and cancel wouldn't do a thing, as well as the "Hang up" button on the steering wheel. It will stuck in that status for anywhere around 5-20 mins, and then it'll hang up by itself and everything works fine again, I can make phone calls and everything.
The only solution I found is to go into my phone and call someone, before the call even connected, I hang up, this will "reset" the call status, and it won't stuck anymore. But this is very annoying to do every time you entering your car...
Un-pairing, delete and re-pairing doesn't help either. As soon as I pair my phone to the car, it'll stuck. I tried my old Galaxy S on my car after this happens, it works like a charm. And before I got my S3, I've been using my S1 with my car for more than 2 years and never had a problem.
So this definitely seems like something is wrong with my S3, I talked to Telus support, they said they never heard of this problem before, and they suggest me to do a factory reset, but it'll be a pain to reinstall everything so I haven't tried it yet, just want to hear what you guys think first.
EDIT: sorry, just realized I posted on the wrong forum, please move this for me, thanks.
So nobody has this issue?
bump
Just found out my friend using a S2 is having a similar issue with his bluetooth handset, and yet there's nobody on xda-developers has this problem?
hmmmm....
Sent from my SGH-I747M using xda app-developers app
There's loads on XDA with issues with the bluetooth, it's the reason this will probably be my last Samsung phone as they simply can't get it to work reliably and the same issues keep cropping up on all their models.
kitch9 said:
There's loads on XDA with issues with the bluetooth, it's the reason this will probably be my last Samsung phone as they simply can't get it to work reliably and the same issues keep cropping up on all their models.
Click to expand...
Click to collapse
Yes i can see that, but it seems like people are having issue *pairing* the phone to the car, but my phone pairs with my car every single time, never had a problem with that, it's just after pairing, the car got stuck in call mode for 5-20mins..... :crying:

[Q] New Here: Seeking Help w/ Rebooting S4's.

Hello:
So, the bottom line up front is I need help solving a problem with my now third, new Verizon Samsung Galaxy S4--it keeps restarting on its own, at random times, but most often after I lock the screen.
To go in more depth, if you think you may know the solution: I purchased the S4 when it first came out, some time in 2013 (not sure specifically, but it was new) and it worked just fine for 13 months (1 month past the warranty of course); this was back in August, when I got the latest Android update pushed to my phone from Verizon (4.4.2). A couple of weeks later, I would occasionally get overheating warnings that would very quickly disappear (like within a few seconds), and then the device started restarting itself... I cannot predict when it will restart, it's random, but like I said above, it usually happens most right after I lock the screen by pressing the right side button once. I started looking around on the internet for a solution then, but only found a couple of videos from earlier in 2013 where people were having battery problems (Google search has been letting me down more and more as the years pass). One day while at work, I was listening to Pandora as I always have with the phone in my front pocket, as I always have. A few hours later when I got home, not having taken the phone out of my front pocket since those last few hours at work, I went to answer a text message I had received; when I unlocked the phone, the screen was black, except for a small bit of white showing through some cracks UNDER the LCD, UNDER the screen protector, INSIDE my Otterbox Defender... the phone appeared to be working still, but the screen and touch screen did not. At that point I was pretty damn irritated and tried to find answers for a week with no luck... I called Verizon, they sent me on a goose chase to Samsung, who sent me back to Verizon, who got me in a conference call with Samsung and then left the call, and then Samsung ultimately said I would need to pay for repairs to the phone... SO... I went back to Verizon who again said I would have to talk to Samsung, but instead I just settled to giving Asurion (my phone insurance through Verizon, whom I pay an extra $9 monthly) $99 as a deductible to get a replacement S4...
Two days later I receive a brand new S4... spend hours setting it up the way I had my prior one... wasting tons of my valueable time to do so and bandwidth from my Concast ISP and the data cap they've decided to give us... one week later, the phone starts restarting itself... and this one did it more often than my prior one... EVERYTHING is up to date, minus a good amount of useless bloatware apps I never use from Samsung, like "Watch On," which I ignore... but everything necessary, I update. So, I go back to Asurion, who quickly ships me a 3rd S4...
Two days later I receive that third, brand new S4... spend hours setting it up the way I had my prior one... and now, this one is also restarting itself randomly. Interestingly, when I visited family for Thanksgiving, it restarted itself over and over and over much more frequently than when I'm at my place... at my family's place, they have very poor reception, and my phone usually has to work more to try to get the signal... IDK what the deal is, but maybe that information can be helpful to y'all.
Other things to note:
1) When I check the "RAM manager" by holding down the home button and then choosing "Task Manager", the phone is always using at least 800MB of 1.77GB of RAM... even when I choose "Clear memory" and it tells me 30 something apps have been closed... it jumps right back up to 800-900MB of usage.
2) I've tried factory resets on all three phones; with the first one where the screen cracked inside, I hooked the phone up via HDMI... within a couple of days, the restarting begins.
3) With the first replacement I received, I could not sent text messages with the default messenger app... and shortly after trying, it would restart.
4) I have used the same SIM card with all three phones since the issue began, when I first got the 4.2.2 update... I do not suspect the SIM card is the problem, but I'm also not savy with the phone... I know my way around it, but I'm not in the know.
5) I thought maybe it started because of some apps I had been trying, so I had deleted them, and the problem still persists.
6) I constantly have a Pebble Bluetooth smart watch connected to the phone... I have since I got it last Spring (2014).
7) I have never rooted the S4, overclocked it, underclocked it, or modded it in anyway because I do not know how, and I was afraid of what could happen in the future with whatever ROM I did flash onto the device if Verizon tried to push an update to it... I just don't know anything about the whole process, and I'm assuming it requires a lot of know how and babysitting of the device... I just want it to work.
8) I've replaced the battery twice; it doesn't seem to be the problem.
9) I've cleared the cache through the boot manager thing gotten to by holding a combo of buttons on the device while it's rebooting... it did not help.
Edit: 10) Today while I was listening to Pandora in the car, the audio began to skip and scratch, and then it paused for a moment, and then the phone restarted itself.
11) I forgot to mention that the reboot process itself is very fast compared to a manual restart performed by me... the phone will go black, the Samsung color rings will show a second after that, the logo appears then, the screen flashes the red Verizon logo, and then the devices is ready to be used... it's less than 10 seconds.
I've been searching around on the internet for about two months now while dealing with the problem and I can't find anything useful. Does anyone here know what my issue is and how I can fix it? Is there a way to pull error logs / information from the S4 somehow to give to someone to diagnose, like DxDiags on PC? I don't know how to read that stuff myself, but I know it can be very useful... I just don't know how to find that info inside of these very locked down ****boxes we call smartphones...
I truly appreciate any help I can get--sorry I can't offer anything in return; if I can't find a solution, I'm just going to go to my backup phone from 2011 (Droid X), and I will definitely never purchase another Samsung device, especially after they blamed me as the cause of the problem without even seeing the phone...
Thanks.
The problem is with the NG6 software build, and "probably" not with your phone. Go to Settings>About Phone> and see what Baseband Version is on your phone. If the last 3 letters are NG6, that's probably the problem. There is a new OTA update (as of 12/1).....Baseband Version ending in NK1, which corrects the rebooting problem. Either install the new update, or go back to the NC5 baseband version and that should solve your problem. Both NK1 and NC5 can be rooted if you desire.

Categories

Resources