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 an extremely annoying issue. I've seen some posts reporting this on various boards, but it seems most people throw a default answer out there that it's a hardware issue. I'll explain why I don't think that's the case.
The menu that comes up with you press the "menu" capacitive key has been popping up and down rapidly and repeatedly when I'm in a low signal area. This didn't start happening until after Samsung/Sprint fixed the LOS issue. I'm thinking it has something to do with the way they fixed it, which I don't have any technical or general knowledge of. Most of the time, the screen and keys will not be responsive unless I hit the power key to turn the screen off and turn it back on. It's even more annoying since it vibrates everytime the key is "pressed". I don't think this is simply a hardware issue as the only time this presents itself is the same times the LOS issue used to. I'm sure it's tied to that fix somehow.
Is anybody else having this issue? This may be a long shot, but I installed the LOS Checker zip, (I forgot which dev created it), and never uninstalled it, but I've upgraded many roms since then and don't think it would still be installed.
If any of you do have this issue, did you ever install that LOS Checker zip?
Rom= Blazer Rom EL29 v3.8
Kernel = rogue 1.4.1
Started happening to me recently as well. Im running Calks still on GB with ICS theme. I haven't paid attention to my signal when it happens but you are right, turning off the screen does stop it momentarily. I agree this may not be a hardware issue as well. I've just been bearing it because I plan on changing phones soon anyway.
Edit: It just started happening after this post. Signal was at 1 bar...
Epic-ly tapped from my Galaxy S II
Zoidpilot said:
Started happening to me recently as well. Im running Calks still on GB with ICS theme. I haven't paid attention to my signal when it happens but you are right, turning off the screen does stop it momentarily. I agree this may not be a hardware issue as well. I've just been bearing it because I plan on changing phones soon anyway.
Edit: It just started happening after this post. Signal was at 1 bar...
Epic-ly tapped from my Galaxy S II
Click to expand...
Click to collapse
Did you happen to install this? http://forum.xda-developers.com/showthread.php?t=1326569
Happens to me too. Menu button hitting itself at random times.
Sent from my SPH-D710 using xda premium
I have this same issue. I never realized it correlated with low signal. The issue cropped up 3 times today and each occurrence was with low signal. Good eye sir.
Do any of you undervolt or use a kernel that runs less than standard voltages?
My device is undervolted quite a bit and was wondering if it may be part of issue as i don't remember having this problem prior to that.
I am removing my undervolts and will report back if i still have this issue.
Sent from my SPH-D710 using Tapatalk
I'm on stock rooted. Always happens on different occasions. I just turn the screen on and off and usually it'll fix the problem
Sent from my SPH-D710 using xda premium
I was gonna post the same thing I just realized this morning that it always coincides with low signal
Sent from my SPH-D710 using xda premium
I think its a hardware issue. Im running the same setup on my replacement phone and haven't had the issue since.
I experienced this ever since I got the phone back in september but I didn't wise up until the 14 day period ended. there are two threads in the Q&A section concerning this, one that i started and another that i contributed to.
I would be trying to text and the menu button would pop up and i would accidently hit something on the menu that came up bc the button spazzes out randomly and consecutively and sometimes for a solid 5 seconds, but like the rest of you im sure, it wasnt confined to any single app so it was impossible to find one thing to blame. it would have to be something system-related or hardware-related (btw i did flash the LOS checker some time ago)
I believed the low signal theory for a while, as well as having a corrupted flash. but I experienced the spasms with full bars of service AND after a complete Odin restore to stock everything without restoring any of my past data whatsoever. thus I deferred to the "default" that it is hardware-related.
that was months ago.
I got so fed up with it, i decided to do anything to make it stop. So, I recently opened up my device and took everything apart and found that the water indicator just above the capacitive buttons had been activated. keep in mind I DID NOT EVER have any encounter with water. in fact, the other water indicators were perfectly undisturbed. this pissed me off because that means there might have been an accident or something while they were being manufactured that would have damaged the button - idk just another theory.
This is my main piece of evidence supporting my claim that it is hardware-related:
I ended up breaking the screen trying to separate the glass from the digitizer (stupid, I know bc theyre fused together) so I ended up buying a new screen/digitizer. put it in myself. i haven't had it since. I'm running the EXACT same set up as before I replaced my screen and its been about a week and no instances. I would be experiencing the sporadic menu button randomly, several times a day but it has completely disappeared.
i suggest to you all: bring it in to Sprint if you bought it from them or invest in a new screen off ebay if you bought it from a 3rd party seller (Amazon, wirefly, letstalk), i got my new screen for $65 shipped and it was in pristine condition. now im living a happily-ever-after ending
i'll keep a close eye on this thread to help you all with your endeavors/theories though
if any of you plan on opening up ur device, i suggest you do some homework so as not to destory your phone - its still an amazing device. or you can just ask in this thread and i can give tips to everyone
good luck!!
Thanks for all the updates.. I've noticed I'll sometimes get this error, but my phone will be showing full bars where I KNOW I have a poor signal.. for instance, my elevator at work..
Is there any sort of logging app I could run and go into an area I know this will happen to find out what's going on?
IsThisOneTaken said:
Thanks for all the updates.. I've noticed I'll sometimes get this error, but my phone will be showing full bars where I KNOW I have a poor signal.. for instance, my elevator at work..
Is there any sort of logging app I could run and go into an area I know this will happen to find out what's going on?
Click to expand...
Click to collapse
sometimes the signal bars are inaccurate (like you described). your true signal is found in settings>about phone>status>signal strength. 0-1 bars is really about -90 to -100 dBm
devs use logcats to analyze issues with the internals
http://forum.samdroid.net/f38/tutorial-how-get-logcat-example-check-battery-drain-2543/
I just checked a few other boards and it seems a number of people have confirmed it correlates wih low signal. There are a few people that keep popping up on multiple threads stating it's a hardware issue, only because a new screen fixed it. I would be fine with that logic if there weren't so many people stating it correlates with low signal. Also, it seems most people haven't really experienced this issue until after the LOS fix. Now, at the same times I used to have LOS issues, I now have this. I'm guessing it has something to do with internals and whatever they did to update it may be separate from modems or roms, since people have gone back to stock and still experienced this issue.
I haven't done a search, but is there an information source that states exactly what Samsung did to address the LOS issue?
I'm going to ODIN back to the original shipped EG30 package and test it out.. I never did OTA updates.. always through ODIN, etc. I'm going to see if I update through OTAs if anything is different. I'll report back.
I had experienced it since around the 1st week of october. i didnt have los fixed until i flashed chris41g's experimental kernels, not sure when all that was though. i was convinced it was related to signal too, but i would still happen on the highway/in public with 3 bars of 4g and ~50-60 dBm
would be interesting if you figure it out though
Yea I ODIN'd back to EG30 and now OTA'd to EL29.. no issues yet but we'll see tomorrow when I'm in elevators. After doing all this, I realized I probably need to do a full EEPROM reset and then go through this... don't really feel like doing that tonight though.
Im pretty sure this is in fact a samsung phone issue in general. I came over to sprint and the e4gt from verizon and the fascinate. I loved that phone, but it had this exact same issue. I have not in fact had it happen to me so far with the e4gt yet. I have a sneaking suspiscion that this issue goes hand in hand with undervolting, but thats just my own personaly theory.
Sent from my SPH-D710 using Tapatalk
Happens to me on the rare occasion as well. Might be an issue with the phone?
I called this one during the LOS era. It definitely occurs in low signal areas. I could never get LOS so I went into known dead spots and sure enough those random pop ups happened
Sent from my Nexus S 4G using xda premium
*Luke* said:
Im pretty sure this is in fact a samsung phone issue in general. I came over to sprint and the e4gt from verizon and the fascinate. I loved that phone, but it had this exact same issue. I have not in fact had it happen to me so far with the e4gt yet. I have a sneaking suspiscion that this issue goes hand in hand with undervolting, but thats just my own personaly theory.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I noticed there were a few other threads on Samsung devices with issues.... hmmm. Did you ever try limiting your underclocking to a higher clock speed? This may be a noob question but for the EG4T, is anything less than 800mhz considered underclocking?
JohnCorleone said:
I called this one during the LOS era. It definitely occurs in low signal areas. I could never get LOS so I went into known dead spots and sure enough those random pop ups happened
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I believe I remember seeing your post haha... I'll see what I can do if I mess around with clock speed.
So normally I run my phone on Wifi because it saves battery when i'm on my university campus all day. So last night I headed off campus and so I turned off WiFi, and it didn't want to connect to data. Just sat there (with full service) but no data connectivity. So I rebooted the phone. still no connection, turned on airplane mode and then back off, now it worked but only for about 3 minutes I had 4G with blue sync and everything, then it dropped off. I went out into a rural area and I kept having full signal but no 3G. So I thought it was the rom. I was running AOKP b25 (Team Kang) so I just updated to Milestone 4. Everything was going well in initial setup of the phone, I had 4G signal, then halfway through setup the 4G dropped off. So I turned on Wifi and got everything setup. Turned off Wifi and it hooked to 4G almost immediately. Then about 3 minutes later, it dropped again. So at this point i'm really hoping it's not my phone and it's Verizon. I've never had a single issue before (i've had the phone since December) with data not connecting like this. It just started last night, which made me think it was Verizon and maybe it had to do with the Solar Flares or something? Has anyone had a similar issue and have any idea of what I might try?
Hi
I was just about to post the same thing. I'm experiencing the same, Data and service keeps dropping, I just got the phone Wednesday and since then It's been doing it. It's very frustrating, and I'm also on Verizon.
Someone else experiencing the same? Could Verizon be the responsible here and not the phone?
And if it helps, i'm located in Norman, OK
JGeZau said:
Hi
I was just about to post the same thing. I'm experiencing the same, Data and service keeps dropping, I just got the phone Wednesday and since then It's been doing it. It's very frustrating, and I'm also on Verizon.
Someone else experiencing the same? Could Verizon be the responsible here and not the phone?
Click to expand...
Click to collapse
It's the phone, there's numerous threads about it (the Verizon version.) There's an expected software fix supposedly coming out this month sometime to fix it, that's all we know.
If it's the phone and an update will fix it, then why is it still doing it with a custom ROM? Do the custom ROMs not have the fix in place? I was under the impression that most of the things Verizon releases OTA to fix issues dont' happen in custom ROMS.
zacelliott said:
And if it helps, i'm located in Norman, OK
Click to expand...
Click to collapse
Hey, we are 4hr away from each other. I'm in Rogers AR
spencer88 said:
It's the phone, there's numerous threads about it (the Verizon version.) There's an expected software fix supposedly coming out this month sometime to fix it, that's all we know.
Click to expand...
Click to collapse
Thank you I'll start digging up in some other threads
zacelliott said:
If it's the phone and an update will fix it, then why is it still doing it with a custom ROM? Do the custom ROMs not have the fix in place? I was under the impression that most of the things Verizon releases OTA to fix issues dont' happen in custom ROMS.
Click to expand...
Click to collapse
Samsung is going to hopefully release a radio update that fixes it, which isn't found in custom rom's because it hasn't been released outside of samsung yet.
It's kinda weird though that this JUST happened last night suddenly, the signal has been flawless since I bought it so that's why I thought it was Verizon because I guess I figured if it was the phone it would have been doing it all along and not stop working all of a sudden.
It's the phone and a software update won't fix it. I've tried every radio out there, none solved the issue. I got the phone swapped over a week ago, it is still stock, and the issue hasn't returned. Theres an ongoing thread over at rootz about this.
I can't post the link but it's there. many members are reporting that replacing the device solves the issue.
this was verizon. it happened to me, went away by itself.
that being said, ive had the best handoffs using the 4.0.4 and 4.0.3 radios. try one of those, or a hybrid package.
I went to the Verizon store and they gave me a new SIM Card. Now it works!
willstilson said:
It's the phone and a software update won't fix it. I've tried every radio out there, none solved the issue. I got the phone swapped over a week ago, it is still stock, and the issue hasn't returned. Theres an ongoing thread over at rootz about this.
I can't post the link but it's there. many members are reporting that replacing the device solves the issue.
Click to expand...
Click to collapse
First of all you don't know what you're talking about. It may be a hardware issue it may be a software issue. There is no way to tell at this point. You are trying leaked radios, good job that proves nothing. If Samsung is aware of the issue and working on a new radio you haven't tried it yet. Sit back and relax until the update comes out. Then we can go from there.
SirVilhelm said:
First of all you don't know what you're talking about. It may be a hardware issue it may be a software issue. There is no way to tell at this point. You are trying leaked radios, good job that proves nothing. If Samsung is aware of the issue and working on a new radio you haven't tried it yet. Sit back and relax until the update comes out. Then we can go from there.
Click to expand...
Click to collapse
Wow dude, no need to get insulting. I was merely sharing my experience with a frustrated OP. If you want to blindly believe that there can't be anything wrong with certain devices, until the manufacturer comes out and says it, then more power to you. You are the consumer that ever manufacturer loves. Myself and many others over at Rootzwiki have found success by having our devices replaced. When I tell you that it is night and day difference, it is not a lie.
I agree with you about the leaked radios. If they don't work then it proves nothing. They are leaked and probably not finished. The reason I mentioned them in the first place is because many people tend to suggest trying them to solve signal issues. I was explaining that I have tried them and it did not work. What worked was swapping the defective phone.
So, I've had my phone for probably about a year or maybe longer, Rooted it when I first got it, came from an Eris...I flashed a few different ROMs then kinda settled and have been out of it for quite some time now...
But I'm back...and I've got a question, back when I was flashing ROMs often, I couldn't find one that wouldn't drop network connections while using wifi/wifi tether.
Has this issue been resolved? It didn't seem like it was ever a really big issue with most, before, so when I asked about it months ago, no one said much, but I'm hoping now, with newer releases of ROMs someone will have some more info on this issue?
Thanks in advance...
p.s.
currently I'm running TSM Bullet Vivow 1.4 and haven't flashed anything for a good 8 months and I'm gettin buggy and wanna upgrade to something fancy, fast and doesn't drop service...
You need to get a update of your firmware
I'm still a newb on a lot of stuff...how do I go about doing that?
Just google
Are you referring to a radio update? Last I checked, that wasn't the issue and I tried different radios with no results
Kamikaze - I experienced this as well on Bullet, is it while you are on the phone and the call drops out for a few seconds? I think it has to do with the modified boot.img that the port uses.
This is a list of what worked without connection issues for me.
- Unoffical CM9 by Aeroevan
- Nitsuj's stock port for our phone
- Mikrunny (I think but cant remember)
Yeah, it is a problem with ROMs that are ported. The only ROM this doesn't happen on for me is Justin's stock/stock-modified ROM.
I always found that all ported ROMs worked for me because I had the latest OEM radio. But, when I had the leaked ROM for the DINC2 it said to update a radio but I didn't and the WiFi and data signals kept over writing reach other.
So, its just a thing with the radio.
Sent from my Incredible 2 using xda app-developers app
My experience has been less than pleasant with my signal on my Inc2. I have been all over google trying to find a way to boost my signal for the Inc2. I have only had my Inc2 for a few months and just rooted a few weeks ago. Mine problem is not a result of having WiFi on/off, mine is just a week signal period (-95 dBm to -105 dBm). From what I found through my search is people modifying the back cover with foil/copper wire and tape, raising the cleaning the contacts for the antenna, which I have tried all of these as well. I am considering buying a new cover just to see if I can get a better signal as everything I have tried has failed to boost my signal. I have tried *22891 to update my PRL as well as toggling the settings from CDMA only PRL and CDMA/GSM PRL. If anyone finds the magic trick to boost signal strength I am open to other suggestions.
ThePhantom97 said:
My experience has been less than pleasant with my signal on my Inc2. I have been all over google trying to find a way to boost my signal for the Inc2. I have only had my Inc2 for a few months and just rooted a few weeks ago. Mine problem is not a result of having WiFi on/off, mine is just a week signal period (-95 dBm to -105 dBm). From what I found through my search is people modifying the back cover with foil/copper wire and tape, raising the cleaning the contacts for the antenna, which I have tried all of these as well. I am considering buying a new cover just to see if I can get a better signal as everything I have tried has failed to boost my signal. I have tried *22891 to update my PRL as well as toggling the settings from CDMA only PRL and CDMA/GSM PRL. If anyone finds the magic trick to boost signal strength I am open to other suggestions.
Click to expand...
Click to collapse
Are you s-off, and if so are you on a more recent radio?
I am s-off and I am on the 1.09.01.0312 radio.
ThePhantom97 said:
I am s-off and I am on the 1.09.01.0312 radio.
Click to expand...
Click to collapse
Then I don't have any advice for you. Do you get bad data speeds or drop calls, or is it just the numbers that bother you?
gtdtm said:
Then I don't have any advice for you. Do you get bad data speeds or drop calls, or is it just the numbers that bother you?
Click to expand...
Click to collapse
Data speeds are a bit slow but that is not really a problem as I connect to wifi most of the time. The major problem is I get grumbled voices a lot when the signal drops below -100 and I have to change rooms to continue the conversations, only a dropped call from time to time, but I get people telling me they tried to call me but my phone didn't ring and I think that is a result of the low signal strength. I think this is a hardware problem more so then a software/rom issue because a lot of people have an issue with low signal with the Inc2 I found searching on the Verizon forums. I do appreciate you taking time to inquire.
ThePhantom97 said:
My experience has been less than pleasant with my signal on my Inc2. I have been all over google trying to find a way to boost my signal for the Inc2. I have only had my Inc2 for a few months and just rooted a few weeks ago. Mine problem is not a result of having WiFi on/off, mine is just a week signal period (-95 dBm to -105 dBm). From what I found through my search is people modifying the back cover with foil/copper wire and tape, raising the cleaning the contacts for the antenna, which I have tried all of these as well. I am considering buying a new cover just to see if I can get a better signal as everything I have tried has failed to boost my signal. I have tried *22891 to update my PRL as well as toggling the settings from CDMA only PRL and CDMA/GSM PRL. If anyone finds the magic trick to boost signal strength I am open to other suggestions.
Click to expand...
Click to collapse
Looking for a lower number would prove challenging unless you are right next to a Verizon tower. I know this because at work we have one on premises and my signal goes to 40 to 60 dbm.
Of course, at home, my signal ranges from 85 to 105 dbm but experience no dropped calls.
Ever since I got my first verizon phone in 2001 the signal quality has mostly measured (on every phone) at approx 85 to 105.
And this is living in two metropolitan cities. I wouldnt give it that much thought unless you are dropping calls. Upgrading the radio is a good idea though as well as PRL after upgrading radio.
Edit: Just realized your post was answered. I would call Verizon and inform them of the call drops and ask them to log them. Could be your unit.
tincbtrar said:
Kamikaze - I experienced this as well on Bullet, is it while you are on the phone and the call drops out for a few seconds? I think it has to do with the modified boot.img that the port uses.
This is a list of what worked without connection issues for me.
- Unoffical CM9 by Aeroevan
- Nitsuj's stock port for our phone
- Mikrunny (I think but cant remember)
Click to expand...
Click to collapse
Which rom are you referring to exactly? Link to thread would be nice Thanks!
Yeah, just an update, nothing has cured the issue, updated both firmware and radio with the lastest leak ROM when it came out last month, then switched to different CM ROMs and those were horrible with the toggling of wifi hot spot signal and mobile network, so I went back to bullet and am just living with the random toggling off of wifi/network
I had been bouncing around on alot of the ICS rom's but couldn't seem to find one that this issue was gone. I think it is kernel related.
Since I want my phone to not have this issue I went back to GB for now which for me I didn't want to but this rom works just flawless for me.
GB Sense M 5.0.1 Ext4 Version w/ Drell's #21 Kernel w/ Sense 3 Patch v5.0
Was going to try cm7.2 next since I have always liked non-sense roms.
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