Related
Hey everyone, I looked around and didn't find anyone having my particular problem, but If I put this in the wrong place, or someone has already solved it, just let me know. Don't want to waste your time!
I got my DINC the day they came out in stores...the first one my local store sold in fact. It was working great, but I hated the bloatware and the fact that the Bluetooth stack was not up to date...couldn't connect with a new hands free speaker phone I just bought (Parrot mini-kit slim). I had occasional random reboots, but not too many. Once or twice a week maybe.
So when the unrevoked one-click came out I tried it. Worked great.
Then I started trying ROMs. With everything I've tried I get random reboots...a lot of them. Sometimes it reboots once and works fine for a couple hours. Other times, it will loop until I do a battery pull. When it loops it will sometimes make it all the way to the lock screen, sometimes it will only make it to the boot animation, and sometimes it won't get past the white HTC screen.
I've used a couple different nightly builds of CM6, with and without google apps. I've used Skyraider 1.8 and 1.9 with and without sense. I've tried "touch of photons". Same results and activity on all of them.
Last night I gave up and downgraded to unrooted 2.1 with sense...factory fresh. I reformatted my SD card with the phone, reformatted the phone storage, and I've done factory resets. It still isn't working right.
At this point, I'd be happy to get it back to pre-Unrevoked and just wait for the official OTA Froyo which is supposed to come out soon. Rooting and using a stable rom is fine with me too. I just need a phone that works consistently.
Any ideas? I'm pretty desperate.
sounds like you needed to return it and get a new one since it was doing random reboots from the day you bought it.
have you used any of the hydra kernels to try and OC it, the 1.15 OC would cause mine to reboot. a good stable rom that i tried was JagerRom, 1.7.4 is without sense, and chocolate is with sense. don't try the OTA one because that is for people who updated to the OTA leak and im going to assume you aren't one of thoes people. haha
http://incredibleroms.com/roms/jager/
hope this helps
Thanks Stroupified...
The weird thing is that the reboot issue wasn't that big of a deal before I rooted and started flashing roms. It happened, but not enough to be a problem.
Does the camera and camcorder work on Jager?
Does anyone know if there is something that could have gotten messed up with unrevoked or the roms I tried?
Is there another downgrade method I can use? I just installed the PB31IMG.zip you can find in a few places out there...is there a known reliable source for the downgrade zip?
If I can avoid fighting with Verizon on this I'd like to. I'm obviously outside my 30 days, and I don't want to wait a week or 2 or three or more for a new incredible (if I can convince them to get me one). I'm not even sure warranty or Asurion will do anything with this kind of a problem either...I fear I'm stuck with a $500 reboot roulette machine.
re
i have gone through 4 incredibles.
they all exhibited the same rebooting issues... completely stock with NO installed apps.
I have also tested the phones with 2 different batteries and with different sd cards and no sd cards installed.
I had done factory resets.
I get a ****ty cell connection where i live, -100 to -96 db.
Its looking more like a tower issue..
I also have had a reboot issue. I rooted the phone the day I got it and installed a senseless rom. It worked perfect the 1st day then started into a downward spiral of reboots till it went into a full boot loop. I did a nandroid back up of the original rom. No real issues since. Im still rooted and have only had one random reboot in about a week that I know of. I know the first issue was because of the rom but what causes the random reboots. Is it aloss of signal? Im a noob so Im just trying to get some insight.
Im on #2
I got my 2nd Incredible on Friday. Prior one would just get hotter and hotter (possibly due to signal issues) until it would enter a reboot loop. Hoping # 2 fares better.
johnsquared said:
Thanks Stroupified...
The weird thing is that the reboot issue wasn't that big of a deal before I rooted and started flashing roms. It happened, but not enough to be a problem.
Does the camera and camcorder work on Jager?
Click to expand...
Click to collapse
ya everything works in jager. but from what everyone else is saying it seems like it could be the signal (or lack there of) that's causing the reboots. have you tried the hybrid prl? it uses the verizon and altell towers instead of just the verizon ones. i haven't tried it because im in cali and there aren't any altell towers near me, but if your stuck with the phone you might as well give it a shot if you live in the supported areas. good luck man.
Link to PRL thread:
http://forum.xda-developers.com/showthread.php?t=723829
If you don't have problems with signal don't bother with the hybrid prl... it kills your data speeds because it switches you from Verizon data network to Sprints data in most areas. I know in the Carolinas phones randomly reboot a lot because thats Alltel country and phones don't work properly without the hybrid. But down south its mostly Verizon. Out west Texas/Ok is mostly Alltel.
But man honestly - I have the same issue on custom roms. My stock Sense rom does fine though. Sometimes I'll be on a custom rom typing a text and the keyboard just freezes and its over. lol nandroid time to me - I can't take the reboots but hate not having the features of newer software.
re
i have tried the hybrid prl and it did not help my rebooting issues.
i have also tried switching to the the cdma codec to -b the higher quality compression... with no luck in fixing the reboots.
I have also made sure there was not an issue with an app causing it, i have tested mine with a clean / factory reset with absolutely no apps installed.
I have had 100% good luck with the leaked ota update, the one upped the camera to 720p recording as well as a hand full of other fixes, and not once did my incredible reboot or crash.
I'm pretty confident that htc has fixed this issue for me, once they drop the 2.2 update that everybody seems to be speculating will be released in a handful of weeks.
Thanks for the input everyone, and I'm sorry others are having the same problem.
I went by my local Verizon store (actual Verizon store, not a 3rd part dealer) and told them my phone was rebooting repeatedly. They didn't even touch my phone...I was out of there in 5 minutes with a FedEx 2nd Day Air confirmation number for a new handset. And my wallet is intact also. I'm rarely impressed by Verizon's customer service, but this time...man... Between the new handset and the impending 2.2 update, I hope to be in good shape.
Me Too
johnsquared said:
Thanks for the input everyone, and I'm sorry others are having the same problem.
I went by my local Verizon store (actual Verizon store, not a 3rd part dealer) and told them my phone was rebooting repeatedly. They didn't even touch my phone...I was out of there in 5 minutes with a FedEx 2nd Day Air confirmation number for a new handset. And my wallet is intact also. I'm rarely impressed by Verizon's customer service, but this time...man... Between the new handset and the impending 2.2 update, I hope to be in good shape.
Click to expand...
Click to collapse
Same EXACT thing happened with me and telesales. No scripts, no hard reset, no task killer; NOTHING. Said "my phone gets hot and reboots" and they said (last Thurs), let's get you a replacement overnight so you can try the new one out of the weekend. No muss, no fuss. Got here 10:30AM the next day, and my evil super-heating 4-to-13-reboot-try prone phone is going back.
sprintrjm said:
i have gone through 4 incredibles.
they all exhibited the same rebooting issues... completely stock with NO installed apps.
I have also tested the phones with 2 different batteries and with different sd cards and no sd cards installed.
I had done factory resets.
I get a ****ty cell connection where i live, -100 to -96 db.
Its looking more like a tower issue..
Click to expand...
Click to collapse
I don't believe towers/signal would have any effect on shutting down or booting. Basically once you're on a current PRL, you really shouldn't even have to update it. Unless you're having that poor service deal where an Alltell/Vzw hybrid would benefit you.
I have a Galaxy Nexus on Sprint. I got it a couple days before the 4.0.4 update, and for those couple days, it worked great. Calls were coming and going, no browser issues, even the GPS sync'd up in seconds (I heard about the issues so I put it through some testing).
Fast forward a couple days and I get 4.0.4. First thing I notice is my web browsing slowing to a crawl, then eventually, just stops. I would click anything or go anywhere, and the progress bar will barely move and just stay put. This did not happen connected to WiFi, only 3G. I reboot my phone, and all is well for another few hours. I don't always use my phone at all times, so I don't know what causes it. I've had to reboot my phone twice yesterday because of this issue.
The next issue was the GPS. I was going somewhere with my wife and figured GPS'ing an address wouldn't be a problem. Well, after about 3 minutes I figured it was like the browsing issue and rebooted the phone hoping it would work again. Nope. We loaded the address up in my wife's Samsung Replenish and were on our way. The whole time my phone was trying to get a GPS lock after a fresh reboot. I even threw my phone on the dashboard so it had a clear view of the sky. The GPS never did sync after the 15 minutes or so it took to get there.
Today, I just discovered ANOTHER issue! I was talking on the phone to my doctor's office, when I heard a few clicks, then it hung up. I thought it was my doctor's office that tried to transfer me and goofed up. I try to call back and after a few rings, I get call cannot be completed as dialed. Still, I thought it was their end. I call again and the recording comes up and plays for about 5 seconds, then cuts out again. So I finally call on a landline and all was well. After I was off the phone, another call came in to my phone and I answered it after the second ring, and it cut out immediately. My wife tried calling later after that, with the same results. After calling again, I was able to hear her after about 5 seconds (I waited longer than that last time).
I'm coming from an EVO 3D (EVO 4G before that) and it had it's quirks, but at least I could hold a conversation and use the web browser reliably. Being basically a vanilla Google Android handset, I had high hopes that all my worries and woes would go away. Now? After being pro-Android since my Samsung Moment, I'm starting to think if I should get a damn iPhone. As much as I dislike Apple and what it stands for, at least their phones "just work".
Anybody have anything I can or should try? Should I just toss this phone on the shelf until Google figures out what they're doing with this handset?
sounds like sprint in your area is having problems.
i doubt it would matter if you had a iphone or not.
My wife isn't having ANY problems with her old PoS Replenish. A lot of friends of mine have Sprint and nobody is having problems that I've heard. As soon as I reboot it when I have browser problems, it works great again, until later.
Flash a custom rom.
Or if you don't want to have a custom rom then flash the factory image.
Maybe something went a bit arse-ways with the ota.
that shouldn't be happening, its not normal, 4.0.4 made the gnex better than it already was!
I did a factory reset and the first call I made was dropped. Guess I'll put a custom rom on it... I shouldn't have to though
might something with the radio if everyone else around is not having problems with sprint. factory reset is not the same as reflashing the 4.0.4 images. try and reflash the stock 4.0.4 images.
I'm on my second device, sprint swapped mine out because my data was just crawling, and I came from T-Mobile and they don't have fast 3G and it felt like I just switched to Dial-Up. They updated the device in-store to 4.0.4 and it was fine yesterday and this morning Pandora kept stopping and buffering. When I got to work I rebooted and ran a speed test and I was getting 1400-1700kbps and sub 400ms ping, which IMHO good considering I don't get great reception in our datacenter. Now 4 hours later I'm down to 100-330kbps and ping of 1000ms plus... even after reboot...
Probably Sprint-version-specific problem or hardware problem of your phone.
I use a GSM Nexus on tmobile and I know people that have the Verizon version. Everyone noticed significant improvement after going to 4.0.4.
I just updated to 4.1 and can't seem to get a network signal on any of the ROMs I have tried. Anyone else had this problem or found or know of a solution?
Thanks.
Rarazuh said:
I just updated to 4.1 and can't seem to get a network signal on any of the ROMs I have tried. Anyone else had this problem or found or know of a solution?
Thanks.
Click to expand...
Click to collapse
Was this an OTA uprade? If you did an manual upgrade, you should make a backup before going forward.
Are you sure you used the correct ROM? Cross-flashing between a Toro/Maguro/Toro+ will often have the phone but up but with the radios not working
did you check your apn?
I just bought this phone on Thursday and the bestbuy rep had the same problem on two different phones and had to call the Verizon help desk. She managed to get it working and of course my signal went in and out as soon as I left the parking lot. I went home and immediately rooted and flashed 4.1 and had the same issue. I was on the phone with tech support and they couldn't find the problem.
I then did a quick search online and found that this is a common issue. The problem is that when updating to 4.0.4 the galaxy nexus has a hard time with the 4g connection. It then drops to 3g and then it realizes 4g is available and switches back just to start this never ending cycle. This causes a signal to be held for seconds at a time before dropping completely until it switches to the other.
The temp fix is to disable LTE and run your phone on CDMA full time. This worked for me and I have constant signal everywhere. Eventually I know a patch will arrive so I'm content with 3g for the time being.
What puzzles me is how come this doesn't happen to everyone? Its a big enough issue that I found the solution within 3min of searching for a fix but not big enough for Verizon to be aware of.
Sent from my Galaxy Nexus using xda premium
mclaughlin47 said:
I just bought this phone on Thursday and the bestbuy rep had the same problem on two different phones and had to call the Verizon help desk. She managed to get it working and of course my signal went in and out as soon as I left the parking lot. I went home and immediately rooted and flashed 4.1 and had the same issue. I was on the phone with tech support and they couldn't find the problem.
I then did a quick search online and found that this is a common issue. The problem is that when updating to 4.0.4 the galaxy nexus has a hard time with the 4g connection. It then drops to 3g and then it realizes 4g is available and switches back just to start this never ending cycle. This causes a signal to be held for seconds at a time before dropping completely until it switches to the other.
The temp fix is to disable LTE and run your phone on CDMA full time. This worked for me and I have constant signal everywhere. Eventually I know a patch will arrive so I'm content with 3g for the time being.
What puzzles me is how come this doesn't happen to everyone? Its a big enough issue that I found the solution within 3min of searching for a fix but not big enough for Verizon to be aware of.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have the same issue. it burns your battery as well by switching back and forth. I used to leave my nexus uncharged at night and the sleep mode would allow it to only lose a a few percentages but now if i leave 4g on with 50 percent battery.. Its almost alway dead when I wake up
Sad to say I have the same experience
The story told by mclaughlin47 is almost exactly what happened with me. Even rooted and running BAMF Paradigm 2.1, I still have the same problem. If anyone knows of a way to fix this, please let us know.
I can't believe Verizon isn't aware of this problem. I actually had better battery life and signal with my Thunderbolt running Vicious ROM. I may just be returning mine if I don't hear of a solution soon.
Thanks for any help, cause this is ridiculous!
I am rooted now, but even on stock ICS I was getting a problem where my radios just die. Requires a reboot to fix. But when I was seeing it, they always looked fine. You don't know they died until you try to use data or make a call.
Do you still have your imei
Sent from my SCH-I535 using Tapatalk 2
I saw the same issue with ics and jb roms. Tried several radios but always dropped data and voice when using 4g. From what I've been reading, it's a hardware defect.
Mine also works great and stays connected all the time when I leave it in cdma mode. Went back to my rezound since 3g mode there at least still let's me use data while talking on the phone. I like showering in as much radiation as I can
tbguy said:
I saw the same issue with ics and jb roms. Tried several radios but always dropped data and voice when using 4g. From what I've been reading, it's a hardware defect.
Mine also works great and stays connected all the time when I leave it in cdma mode. Went back to my rezound since 3g mode there at least still let's me use data while talking on the phone. I like showering in as much radiation as I can
Click to expand...
Click to collapse
Reflash the radio and the cdma radio. Samsung and Verizon Wireless both claim that hardware defects are not known issues.
Which hardware revision do you have? (looks on the label on the back should be 11.11, 11.12, or 12.0.)
i have 12.01
will try reflashing the latest radios
tbguy said:
i have 12.01
will try reflashing the latest radios
Click to expand...
Click to collapse
just to check back, did it work?
unknownzero said:
just to check back, did it work?
Click to expand...
Click to collapse
Have the same exact issue...just upgraded to a jelly bean Rom and my data drops completely and I barely have a signal, did a super wipe (radio-rom-Gnapps)...and went to my old rom of ICS and I still have the same problem...but for the most part I barely have any type of signal and calls are dropping, called Verizon and they told me something about a switch, and that there is no problem in ur area....I just called last night, I'm gonna call back today...wish there was a solution ...also tried that 3G switch I just read earlier and I still have a poor signal
Any updates? I'm having the same problem
Hi,
I'm having the same issue. I've had my Nexus for about a month now and have had nothing but horrible signal issues, while my old Droid 2 gets fantastic signal.
I'm using the latest Bugless Beast 4.1.1 with the latest radios that were released today.
People have mentioned it being a hardware defect. I'm assuming I should just go back to stock ICS and go into Verizon and exchange it for a different Nexus?
It may very well be a hardware problem, but my thought was a SIM card problem for the reason that rebooting often does not solve the problem for me. I have a passcode on my SIM card, so if my phone doesn't ask me to enter the code then I can assume it doesn't see the card. This often happens when I encounter the loss of data problem and reboot, and I usually have to remove the SIM card and fiddle with it a bit and put it back in and then it reconnects.
So I went to the Verizon store to try and swap my SIM card and they wouldn't give me a new card, saying that it's a known software issue that Samsung has already attempted to fix twice and they are working on another OTA update. I obviously made a ruckus about how I'm paying for service I can't access and I want a different device, blah, blah, blah. Basically he was incredibly unhelpful.
I've been on ICS AOKP and recently switched over the CM10 JB and that's when the problems started for me, but I switched because some type of battery issue (it lasted about 3 hours for a few days) caused my phone to reset itself and erase everything so it seemed like a good time to upgrade. So I may have unique hardware issues going on but according to vzw it is software-based. I'm not sure if this is something that can/will be addressed in a new nightly if that's the case.
PEOPLE, IT'S NOT A HARDWARE PROBLEM! IT'S SIMPLY A RADIO.IMG PROBLEM! A LOT OF PEOPLE WHO IS ON ICS, BUT FLASHED LATEST RADIO ARE SUFFERING FROM THIS!
What you can do is just flash to a older radio image. Not that hard. Will this stop the OTA? Probably, but you can either flash the latest version back or just manually flash it.
Have a good day.
I got mine the first week of Aug at Best Buy. The first one I got had all the problems described above. Radios dropping out and dropping every call I made. I returned it the next day, and the sales guy told me he was 100% sure it wasn't the phone. I asked him to exchange the phone and the card because I couldn't use a phone that couldn't make calls. He did the exchange, and the second phone was actually worse. Most of the time, I could not even make a call. So, the next day I took that one back. They gave me a third one that worked great for a week, then I started getting a no SIM card error message. The phone would reboot and work again for about 3 hours, then repeat error message. I took the card out, wiped down all the contacts with a soft cloth, and I have had no problems since. Great reception, no dropped calls. Great phone. I don't know if it is hardware or software, but I would keep returning the phone until you get one that works!
Once again, what is the point of having a phone that can't make calls.
So, I got my Note3 last week as soon as I heard CM11 nightlies were officially available. I spent zero time with the stock ROM.
Everything installed perfectly the first time. CM11 ran nearly perfectly, especially considering it's a nightly and there are no stable releases or RCs, yet, etc.
On Thursday I spent a full day at my desk at work. I noticed that my phone rebooted in my pocket. I figured "hey, it's a nightly...I've seen far worse"....then I noticed almost every 2 hours it seemed to reboot again, sometimes more frequently. It never rebooted in the middle of me using it...only while in my pocket.
So, I figured "hey, no big deal. Another nightly or two and this should be ironed out." So I restored my stock backup on Friday after work. All weekend long, no problems whatsoever. I figured it must have been something wonky in the nightly CM11.
Then on Monday, while sitting at my desk, it happened again...and again....and again. Same exact circumstances. I figured maybe I borked something so I got a restore-to-stock and flashed it via Odin.
Well, long story short this continues to be a problem whenever I spend any significant time at my desk at work. It doesn't happen anywhere else so far. It happens with any ROM I throw at it. I've Googled around and it appears that I'm far from the only person experiencing this problem however I don't experience froot-loops like a lot of people. Just semi-random reboots.
Now, I'm pretty convinced that a different (or new) modem would take care of this. I had the GS2 on Sprint and we had a problem we referred to as "LOS" (Loss Of Service) which typically required a reboot...even on my bone-stock phone...it seems to happen with the same randomness. One thing I do know about sitting at my desk, my phone is constantly switching back and forth between H, H+, LTE, DC and occasionally E...Edge being the only thing that gets solid service about 1 wobbly bar.
That's my own theory. This isn't a deal breaker for me. It only happens at work and if I wait a few seconds my phone is back in commission without any intervention.
Anyone else have a similar experience, tips, ideas, theories...? I'm more curious than anything.
Perhaps a Wi-Fi issue?
krelvinaz said:
Perhaps a Wi-Fi issue?
Click to expand...
Click to collapse
I keep wifi off at all times, wifi scanning set to off. I have unlimited data and my 4G speeds outclass my (relatively very good) cable modem speeds at home and at work (I live and work a stones throw from the NOC...I mean...literally, across the street from both places). I would prefer wifi if it wasn't sketchier than my cell connection.
So, it's not that.
How many files on your microSD card? Notice I asked how many, not how much space taken up. Android's media-scanner service seems to have huge stability issues once you cross the 10,000 files threshold. If that's your case, delete some files and see if it still reboots. I had about 10k files, deleted down to 6.5k and no more random reboots for me.
I have the same issue, and I don't have a micro SD card in the slot. The phone will randomly restart, usually after unlocking the phone. I have disabled wifi-scanning, auto app updates, and factory reset device, but nothing helps. It didn't do this before the kit kat update. It only happens maybe once a day or every other day. It's not terrible, just annoying at times. I'm thinking its a software bug.
Also, i'm running everything stock at the moment.
I have been on Cyanogenmod nightlies since I got the phone...and in the past week or two it does not reboot randomly with either Cyanogen or AOKP. At all. Still does with TW, I haven't taken the KK update so I don't know if that will help or hurt....and unless I absolutely am required to I won't be taking that update ever.
Maybe some kind of interference, that's kinda odd that it's happening only at your desk. And on stock.....
Sent from my SM-N900T using XDA Premium 4 mobile app
We have two Note 4s in our house. One of them has the correct time, and the other one is suddenly off by 1:07. Both of the phones are set up exactly the same way:
Automatic Time Zone - Check
Automatic Date and Time - Check
Both of them show the time zone as GMT -6:00, Mountain Daylight Time
Both phones are running 4.4.4, N910VVRU1ANI1. I haven't taken any OTA updates on either phone.
I have installed nothing on either phone in at least a week.
I've tried rebooting the phone a couple of times, but it hasn't made any difference.
Both phones are sitting right next to one another, so they're on the same tower.
WiFi is on for both phones. Both phones have location with high accuracy turned on. I have tried shutting off wifi and location and rebooting, it made no difference.
I've run out of ideas. Anyone else have any ideas for me to try?
Thanks
Also tried battery pull and safe mode. The time is still off. I've noticed that when the phone boots, the clock will flash a couple of times and then set itself to 8:41am. It's now 10:03.
Never mind. Apparently this is a Verizon issue. I just rebooted the phone that wasn't having the problem, and it is now 8:49 on that phone. In the meantime, the one that was having the problem is now working correctly.
Whatever, Verizon. At least it's happening on my phone, instead of my wife's. I couldn't care less what time my phone says. I never even pay attention to it.
Ok, now it's happening on both of the phones on my account. It is 7:09am on 4/21, but my phone thinks that it's 5:58am on 4/20. Yesterday, my wife's phone was bouncing all over the place. After trying everything to fix this, I called Verizon. Because I'm not on Lollipop yet, they refused to help me. I mentioned that I always wait for a few months after an update comes out for any electronic device and that I've seen a lot of people with battery issues, and he said that there's an easy fix for the battery issues and that he couldn't help me any further until I do the update. Probably because he can't get to the next page in his script until he clicks the button that says that I have the latest updates installed. Ridiculous.
The so called easy fix for battery issues is wiping and restoring the phone. Unless I'm missing something, that's not an easy solution to anything. I've spent hours getting my phone where I want it. I don't want to start over again because Verizon can't put out a good update.
In any case, this isn't a PHONE issues, it has to be a service provider issue. Otherwise it wouldn't be happening on all phones on my account.
So I guess I get to have unreliable phones until the find and fix the actual issue on their own.
The issue is not the phones it is the tower. The phones on a CDMA network set the time be the tower that's why normally you don't have to worry about setting or updating the time on your phone unless the tower is screwed up. If you take the phone somewhere else where it can hit another tower it will most likely fix that. I do see something like this on my wifes tablet but that is because she turns off the LTE radio and only uses the WIFI so it can't synch.
I havent had any issues, but a guy here at school mentioned the same thing with his Verizon phone (not a note 4)
So maybe Verizon is having issues?
When I contacted Verizon this morning, that's what I told the guy. If it was only happening to one phone, then I could see how maybe something on the one phone was somehow screwing up the clock. But both phones? The Verizon rep asked me if I was on the latest update. I told him that I wasn't. He asked why and I told him that I never update anything when an update first comes out. I wait a couple of months. Plus I'd heard that there were battery issues with it. He refused to help me until I was updated. He actually laughed at me and told me that there was a simple fix for the battery issues - resetting and restoring the phone. Yea, that's so simple. Anyway, as I was walking out of the room, I caught sight of my network extender. That little box that has been plugged in and working just fine for over two years. The GPS light was flashing purple. I restarted it, waited for all lights to go blue, and then restarted the phones. The time has been perfect ever since.
So yup, it was the tower - the little tower in my house. That thing has been so reliable since I got it, that I forgot that it was even in the equation.
usmaak said:
When I contacted Verizon this morning, that's what I told the guy. If it was only happening to one phone, then I could see how maybe something on the one phone was somehow screwing up the clock. But both phones? The Verizon rep asked me if I was on the latest update. I told him that I wasn't. He asked why and I told him that I never update anything when an update first comes out. I wait a couple of months. Plus I'd heard that there were battery issues with it. He refused to help me until I was updated. He actually laughed at me and told me that there was a simple fix for the battery issues - resetting and restoring the phone. Yea, that's so simple. Anyway, as I was walking out of the room, I caught sight of my network extender. That little box that has been plugged in and working just fine for over two years. The GPS light was flashing purple. I restarted it, waited for all lights to go blue, and then restarted the phones. The time has been perfect ever since.
So yup, it was the tower - the little tower in my house. That thing has been so reliable since I got it, that I forgot that it was even in the equation.
Click to expand...
Click to collapse
Wow, what brand is the extender since it was so reliable?
KruseLudsMobile said:
Wow, what brand is the extender since it was so reliable?
Click to expand...
Click to collapse
It's this one:
http://www.verizonwireless.com/accessories/samsung-network-extender-scs-2u01/
It was a refurb, but I got it for free. When I first started with Verizon, I had all sorts of issues with dropped calls at home. They said that they could give me this, or I could cancel. Where I used to live, Verizon was the only real reliable choice, so I stuck with it and took the extender.