Related
I have a RAZR M that refuses to keep service on PagePlus after activating with their new sim card. I'm not sure it ever fully activated. I have no bars, no service, just a red circle. At times (usually within first 5 minutes of boot) it might show a couple bars or 4g, but I cannot make any calls. I get hopeful when I see the 4g symbol and might even receive a text but it suddenly drops to no service, red circle, as if the radio shut off.
A few months back I purchased a new Razr M XT907 on ebay. Wanted to flash it for Page Plus. I followed a guide several times, then tried following a similar guide but the settings would never "stick" long enough to be truly flashed. I got as far as activating with page plus (*228) and getting text and voice but this would last 2 minutes at a time max, and this is after my most successful of dozens of flash attempts. I then payed someone to remote flash it through my computer but it didn't fix the problem either. The hack involved flashing to stock 4.1.2, flashing to the previous radio that was 4.1.1, rooting, editing subscription value in SQLite, editing 4g value in BuildProp, and setting the phone to NV Only through DFS.
When I heard PagePlus was adopting 4G I flashed to stock 4.1.2 and waited until I could get a sim card. Went to a local dealer, got the sim card, they tried to activate it for me and my phone went through the same process it would in the past and tried to automatically dial *228. I assume when I flashed back to stock it didn't fully reset everything I had changed and was still in non-4G mode and trying to activate OTA. I've heard dialing *228 with a sim card in can damage it but I'm surprised the industry would allow that without safeguards or warnings. This is when I saw for the first time some actual GUI glitches on the phone which is lightly used and no hardware issues known. I have since reversed all the steps I remember taking to flash and manually unflash each individual setting, I have reflashed to stock multiple times. I have tried updating the PRL, I have tried flashing the 4.1.1 radio, 4.1.2 radio, and the newest radio (SM_BP_101032.021.32.80P) with no luck and minor differences. Now the only GUI glitches I get is when I turn the phone on and it tries to activate (through 4g/sim method) and says "this could take a few minutes" with an option to click "ok." This box flashes constantly and sometime makes the ok box impossible to click. One of the settings I messed with before was under ##PROGRAM under test, the service mode (CDMA/EVDO/LTE/WCDMA), (CDMA/EVDO), (CDMA/EVDO/LTE). But recently when viewing or changing this value I'll look back and it won't change, or it will arbitrarily change to just (CDMA/EVDO) and I'll set it to (CDMA/EVDO/LTE) then I come back it's set to (CDMA/EVDO/LTE/WCDMA) (default I believe). At times I cannot access the ##PROGRAM settings at all and I believe this has to do with a GSM mode or SPC issue.
Currently I'll get blue or gray 4g indicator for 30 seconds then it quickly switches to no bars with red circle. A couple times it has shown just a couple bars with no data indicator. Twice it has worked long enough to retrieve a couple texts. This seems similar to my earlier issue with trying to flash without 4g/sim. Even when the phone shows service I cannot get any phonecalls to dial out. At least once it failed and said "radio off." Indeed it's acting like the radio isn't on at all, randomly cuts in and out, and the majority of the time is no service no bars with the red circle.
I'm not sure if I corrupted a setting, never completely unflashed, or have an actual hardware issue. Interestingly my IMEI listed on the OS as well as dialing *#06# are the same, but the last digit is different (0) when reading the IMEI value in DFS. If anyone knows how to truly reset all the settings to default including those in SQLite, BuildProp, ##PROGRAM, and DFS then that would be incredible. Otherwise I may have a more difficult issue and don't know if my device is even sellable.
https://www.reddit.com/r/GooglePixel/comments/5b6twj/pixel_xl_intermittent_cell_and_gps_signal/
https://www.reddit.com/r/GooglePixel/comments/5bhltm/issue_with_dropping_lte_service_randomly/
Hello all,
I am currently attempting to troubleshoot/corroborate apparent issues with the mobile radio. My first device took six or seven attempts to activate, and then intermittently threw a no SIM error with what looks like a radio restart (no signal on any bands, cycle between No Service/Searching 4-5 times before reconnect.)
WiFi appears to be good, I'm only experiencing these drops while connected to LTE with no graceful fallback to 3g or even 1x. Drops are happening while stationary and in motion, frequently in areas where my signal is at least decent. The threads linked above both have users who appear to be having the same problem. Particularly strange is that there dose seem to be a location component, there are two spots in particular that seem to be more likely to cause the problem (though not every time.)
I've replaced the device once already in an attempt to resolve this, and while I initially thought that the issue was resolved, I did manage to catch another drop yesterday after running tests forcing the device in to 3g-only operation (the device performed just fine before, during, and for a few minutes directly after these tests.) Of note, I haven't managed to catch a 'No SIM' message on this replacement phone. I have been running an app to notify me of signal loss today, and of course it seems to be behaving now.
If you've experienced any similar issues, please reply and let me know if you've had luck resolving.
Yep this is what is happening allright.
I have two htc one M7s. My main phones.
Last evening, in a very strange shift from her norm, my woman asked to use MY phone to cruise the net.
Ok so she goes on and fifteen minutes later I get the phone back.
Suddenly, in the middle of refreshing a twitter or facebook, THE WI FI CONNECTION GOES DOWN.
I cant get the thing to reset after shutting it off. I have to go to the ROUTER , turn it off then on.
Five minutes later after ROUTER reboot, it is working again.
It is just the beginning of our story. I have a second phone also same make and model. It is midnight now, some four hours later, and as usual I turn off router before sleep.
I wake up, unplug other phone (not the one from last night) and, swap out the sim card to it (was in phone durring Wi Fi problem).
Now, I switch on the phone, and it comes up with LTE cuz Im on mobile. Then I get the normal "ok" from phone message (system communicating with mobile).
Heres where it gets strange. I get the 3G on top bar. Ok this NEVER happens.
One minute later it says LTE again.
Wtf is happening.
Not mentioning in this story little invisible forces kicked my left leg open as I was waking up. Angry *****es over Hillary.
Same LTE issue here. Just contacted Google Support and rebooted to safe mode. Let see if I have the same problem again tomorrow
chadwick359 said:
https://www.reddit.com/r/GooglePixel/comments/5b6twj/pixel_xl_intermittent_cell_and_gps_signal/
https://www.reddit.com/r/GooglePixel/comments/5bhltm/issue_with_dropping_lte_service_randomly/
Hello all,
I am currently attempting to troubleshoot/corroborate apparent issues with the mobile radio. My first device took six or seven attempts to activate, and then intermittently threw a no SIM error with what looks like a radio restart (no signal on any bands, cycle between No Service/Searching 4-5 times before reconnect.)
WiFi appears to be good, I'm only experiencing these drops while connected to LTE with no graceful fallback to 3g or even 1x. Drops are happening while stationary and in motion, frequently in areas where my signal is at least decent. The threads linked above both have users who appear to be having the same problem. Particularly strange is that there dose seem to be a location component, there are two spots in particular that seem to be more likely to cause the problem (though not every time.)
I've replaced the device once already in an attempt to resolve this, and while I initially thought that the issue was resolved, I did manage to catch another drop yesterday after running tests forcing the device in to 3g-only operation (the device performed just fine before, during, and for a few minutes directly after these tests.) Of note, I haven't managed to catch a 'No SIM' message on this replacement phone. I have been running an app to notify me of signal loss today, and of course it seems to be behaving now.
If you've experienced any similar issues, please reply and let me know if you've had luck resolving.
Click to expand...
Click to collapse
I've got a Black 32GB XL on Verizon (Verizon Model) and never have this problem. Any tips on reproducing it? I'd love to help test and see what I can come up with. Only time my phone says no-sim is for like 5ish seconds after boot. And I've only once seen the phone fall to 3g in an area with known strong LTE. My previous note 7 fell off LTE pretty often. Specially when jumping between towers. But my PXL rarely (Once) does.
This has been happening to me on my pixel xl 128gb since the day I got it. I reported it to Verizon and to google. Google said bad sim. Verizon replaced my sim and it didn't change a thing. I can usually get it to reconnect if I toggle cellular data on and off. Please let me know if anyone finds a solution.
This is known as hollow bar. And it happens to certain Nougat phones in certain areas.
SOLVED! - see post #7
This SM-N910V is rooted and had 3g but apparently I lost that when mucking around with things trying to get 4g. I've got other phones like a Galaxy S5 and Galaxy Note 5 both Verizon models that get 4g or 3g fine in this same location.
First odd thing I noticed on the Note 4 was a setting that popped up seemingly by itself while in 'More Networks' and 'Mobile Networks' that showed VZWInternet with a circle by that which was not yet checked so I tapped that and it turned green in the circle. I have never been able to see that option again. I don't think this caused the problem though. I've looked at apns-conf.xml in the /system/etc folder and can't see a problem there. I also tried replacing that with another one that is supposed to fix LTE mode. No luck so I put back the original. I wiped cache and reflashed a backup with TWRP which had been working on 3G but that didn't help - no 3g even. I did not wipe Dalvik/ART cache. I had been messing around in the 'Service Mode' menu with a bunch of different settings in an attempt to get 4g working but I'm fairly certain I got everything set back the way it was before I started. I noticed that one setting I had left different in the Service menu did not change back after flashing a restore with TWRP (full restore - all boxes checked). The one setting I left changed was the under the 'AS' protocol menu where I changed the Release version control to "LTE 3GPP REL 9" from LTE 3GPP REL 10". I know enough to be dangerous
Open to any suggestions - am wondering at the moment if I should have wiped the Dalvik/ART cache before the whole TWRP restore? At this point I'd be happy just to get 3g working again.
I also tried Dr. Ketan's LTE Enable. That didn't fix anything. Although I see MNC and MCC numbers in the apns-conf.xml file when I look at the SIM with a SIM info App I just see blanks in those spots on the SIM. Not sure if that's relevant - just giving as much info as I can here.
Did another restore with TWRP after wiping Dalvik/ART cache but that didn't fix it either. Strong cell signal but no 3G or 4G.
More info - I put the SIM card in another phone and it sees 3G at least.
It seems the "lost 3g or 4g" problem is very common and it seems I've looked through dozens of message threads here but I'm not finding any solutions. I'm looking at flashing the 'ltefix.zip' from this thread but it seemed to be for a custom ROM and I've just got the stock - more or less - 5.1.1.
Hmmm.... Been at this all day reading here, searching, trying everything but still no Mobile Data. Is this as elusive as rooting a Verizon Note 5? LOL - it was working at least on 3G. I'll take hints or even wild guesses at this point.
Okay - it finally flashed on me to do a restore of my EFS. Oddly I had done a full restore with TWRP which include EFS but that didn't fix the problem. That TWRP backup was done the same day I did an EFS backup using Dr. Ketan's IMEI tool for the Note 4. When I used the IMEI tool to restore the EFS backup I then had the 3G come back on. This is a 4G SIM so I still don't know why I'm not getting 4G but at least I got 3G back. I did have a hiccup using this IMEI tool which initially caused the phone to repeatedly shutdown after a minute or so and could not be restarted without pulling the battery. I believe it had to do with the 'Restore' button needing to be held down a certain amount of time instead of just a tap. I probably held, released too soon then held longer which I suspect caused a partial or damaged EFS restore. Be careful in how you use this tool or you may end up in that situation. I had to work very fast after a bootup to get it properly restored. After that it was stable again and had 3G.
Now if only I could figure out what it takes to get 4G.
..
I wasn't getting 4G for the longest time, checked the PRL in settings on my GFs phone and noticed my PRL ver was like 50 thousand something while hers was 15518. Got a new Sim card and all my issues went away, PSA do not use *228 programming...EVER.
..
..
acslam said:
Update/more info - I've continued to try and figure this out to no avail, although I got fed up with stock unrooted 5.1 and am now running modestrom v9 with a CQI2 base. And all of that install went fine, except for 4g of course.
I think this is worth mentioning as it might have something to do with the situation:
Way back in the beginning, I had gone through the entire unlock/root process, and everything actually worked fine the first time. This was right about the time the unlock became available, I bought the phone based specifically on that being possible, and got a brand new one at that time. Well, it was awesome for about 2 weeks, fully functional 4g and everything.
I had a very particular goal - I wanted this phone totally unlocked, but I was also very interested in the advanced/wifi calling that was supposedly coming out at that time - I was planning to move to a place with no vzw service and would be reliant on wifi for calls at home. Verizon wasn't clear about the fact that the wifi calling feature wasn't coming until MM, and this was before MM was released, so I was running a completely functional, 5.1.1 rom. I believe it was jasmine. So, under the impression that "advanced calling" would have given me wifi calling, I tried to enable it.
I cant recall if it was immediately, or a few hours after, but this is when the phone lost 4g for the first time. I immediately tried to deactivate the advanced calling feature on my line, but it didn't help. And nothing I could do would bring back 4g. I tried everything possible, and ultimately gave up and threw the phone in a drawer and went back to my note 3.
Fast forward several months, and my note 3 began to have issues with call audio, forcing me to use the 3g-only note 4 in order to actually handle day to day business. Again, I went through the processes of trying to fix 4g, with no success. Now by this time, MM had been released, I believe PD1 was the current firmware. I figured at this point it was time to just odin back to 5.1.1 and start everything over.
So I odin flashed the phone, and it booted into 5.1.1......with no 4g. Again I went through all the things I found here, no improvement. Finally, one day when the phone was bugging me about an OTA, I figured "what can it hurt at this point, its nearly useless without 4g anyhow."
And low and behold, the OTA update from verizon booted up and immediately jumped to 4g.
Now I felt I had a chance, a method that I'd finally proven could fix the problem. I left the phone in that state for a couple weeks, just to prove that it was holding. No problems during this time.
But I got sick of no root, and so I figured it was time to try and go through the steps again. And again, I lost the 4g connection. No big deal, just odin back to 5.1.1 and let it OTA like last time......
Except this time it didn't work. So I odin flashed back to 5.1 again, and let it try to OTA, again. I let the phone continually try to OTA all the way up to current, and flashed back to 5.1 at least 3 times to repeat the process in hopes it might fix something. No change at all. At this point I actually began to try and see if possibly Kies could help me here - maybe there was something related to the phones EFS? Which I don't understand very well btw - it was only through reading this thread that I began to research EFS and its significance. I also attempted to use some of the checkboxes in odin - the ones to erase all NAND and to clear EFS and rebuild it. Neither option made any difference. So I figured next logical step was to start playing around in service mode, which would require unlocking/rooting again......
And thats how I landed here. About an hour ago I got sick of the stock 5.1.1 and went through the whole root/unlock process and I'm currently running modestrom on CQI2 or whatever was just most recently posted. Every other part of the phone seems normal, but still no 4g. I can actually see the radio making an attempt to connect in the service mode - but I don't understand service mode menus well enough to interpret where the actual problem is. Upon boot the phone tries about 3 or 4 times to get an lte signal, during this time there is simply bars of signal, NO data indicator of any kind. Eventually, it gets frustrated and gives up, connecting to 3g and staying there. I realize now that when 3g drops, which is roughly every 10 minutes or so, its actually the phone attempting to establish LTE again. But still, I cannot make any sense of this.
Apologies for the giant post - I'm trying to put anything that could possibly be relevant info into one place here.
So........ anyone got any suggestions?
Click to expand...
Click to collapse
PM sent. Just to share a little of that here I think the first thing I would do is tell VZ you suspect your SIM card is bad and have them put in another one. Tell them it fell out when changing a battery, the dog ate it and by the time it came out you suspect it wasn't quite right anymore - LOL. I do think SIM's flake out sometimes and I know a bad one can prevent 4G from working. If you ever had an EFS backup from anything try restoring ONLY the EFS (if you use TWRP). No guarantees that will fix it but my best guesses at this point. Good luck.
..
I supect Verizon's doing this ...
acslam said:
I got a used stock note 4 to try and compare and see what I could be missing here....
Tried new sim card at least twice, unfortunately no dice, and the same card pops right into the spare note 4 and it wakes up on 4g just fine.......
EFS is something I probably should have been quick enough to dig in deeper on before this, as I don't have any backup of it....... however, I'm not seeing any other symptoms, I can see my imei fine, and every other function works. Is it possible that corrupted EFS can cause the loss of just one type of connection like that?
For giggles I tried a friends att sim, and no lte on that either.
Playing with the app LTE discovery, I can tell that the phone sees 4 different LTE towers just fine, showing db numbers exactly in line with the stock note 4 sitting right next to it, theres just something there under the surface thats stopping them from hooking up...... it stops trying after a couple minutes, rejects them all and connects to 3g.
I'm convinced its some kind of software thing, but I can't tell exactly where the failure is happening.....
I also odin flashed it back to stock bpa1, and still no dice. Is there a means to make an EFS backup without root? I want to see what happens if I try unlocking the other note 4 as well, but this time I want to have the backups......
Click to expand...
Click to collapse
I've been running on Emotion 7.1.1 for months with NO issues (well, some minor stuff, you know....)
Suddenly, two weeks ago I got a notice from Google that I had to sign in on my phone. Verrrryyy odd. At first I suspected some hack attempt, but my Account checked out fine. Having changed my password recently, I had to wait until I got home to login.
After I logged in, all ~appeared~ to be OK. Then I opened my Calendar. B L A N K. All ten years of appointments gone. I freaked out. I have two calendars, one for personal stuff, birthdays and the like, and another with my business appointments, INCLUDING FINANCIAL STATUS of the account. Gone.
Went online on my PC, signed into Gmail and switched to my calendar. Empty. Looked in Trash. Nothing. Vanished. Nada. Niet. There's a long story here about recovery efforts, troubleshooting, Googling, etc, suffice to say that TWO separate, redundant, backups had quietly failed, without the notifications they were supposed to send. I did manage to get from the first week in April back 10 years, but lost the whole summer. Thank YOU-KNOW-WHO that I'm good friends with all my clients.
Fast forward to last week. Suddenly I get 3G only from my Verizon account. Like you, I spent days on the boards, downloading ROMS, wiping, re-wiping, trying everything short of smoke signals to get it back. No joy. I did NOT go back to stock, I must thank you greatly, as that was my next road. Now i see it's a dead end. I will NOT give up my Nougat root just to get 4G.
Perhaps this is a bit conspiracy theory sounding, but I've become convinced that Verizon is playing some game, perhaps to force us to upgrade to a new phone. I learned long ago that corporations have no soul, and will do anything they like to increase profits. They exist for two reasons; to make money for their officers and to make money for their stockholders. Any other semblance of a "Product" or "Service" exist ONLY and SOLELY for that reason. Anyone who is a Yahoo or AOL member knows the level of intrusive ads and attempts to trick people into putting spyware in their machines under the guise of "protection" or "cleanup" programs has jumped to a new level of absurdity since Verizon sucked them up. "Oath" indeed. It's what is coming out of existing customer's mouths! M O N E Y H U N G R Y.
When I chatted at length with a Verizon Tech, she made it clear that she knew the answer was to upgrade to the latest stock (I never admitted to rooting, but she knew, we spoke "between the lines" a lot). She sent me a SIM card, but it., of course, didn't fix the problem, in fact it would not even initialize properly! I had to go back to the original SIM.
Now that we've found a way (after YEARS of trying) around their stupid block on rooting, they change the game. What person who is so into their phone as to root it, will put up with 3G? This is something Verizon is playing at, Sprint too from what I gather.
My only consolation is that I've got so many WiFi's nearly everywhere I go, and when I'm not near one, my Wife's Note 4 (not rooted, on latest update) works fine. I'm glad I decided not to root hers too.
Frankly, this really ticks me off. I have better things to do than spend days copying files, flashing and reloading data. Verizon knows that, and let me tell you, it won't be THEM who sees my money when I finally do upgrade.
Thanks again for saving me from the Stock route, you saved me hours of grief.
Peace out!
PuterPro
I have run into 4g issues with this as well and almost came to conclusion is a modem issue. I want to say but can not confirm that modems that are flashed are relative to bootloader on the device. Just something I've been pondering on as I had a unlocked bootloader device and flashed for wife to use with no root and recently unlocked again.
Sent from my SM-N910V using Tapatalk
I apologize in advance for the long read.
I recently activated Verizon service on a Note 4 that has been sitting unused since the Note 8 came out. The Note 4 is in perfect physical condition, with no scratches on the screen or body, and has been in a protective case since new. I did replace the battery in it prior to activation, as I expect for the life to have been deteriorated.
I did a factory reset and inserted my Verizon SIM card, and it worked perfectly. I installed my everyday apps and a few games on the phone, and I used it without any issue for about a week. During that time, it did install a couple of OTA updates, but I expected that since it had been "off service" for a few years.
After that first week, I put the SIM card back in my NOTE 8 for a couple of days, after which I went back to the Note 4. Initially, 4G data and cell service worked, but within the same day I started having service drops. If I was on the phone and a call dropped, it would show an error message saying "No SIM / SIM Error".
Her is what I have attempted so far:
First, I replaced the SIM with a new one. There was difference in the frequency of the random service drop.
When that did nothing, I assumed that one of the OTA updates from the prior week had done something to modem / radio. The phone was on 6.0.1 at that time. I unlocked the bootloader and installed TWRP, and first tried downgrading to stock 5.1.1, then to a "modified 5.1.1, then to CM 13, and now Lineage 15 (frequently factory reset / cache wipe. There has not been an improvement (or reduction) to the random service drop.
Yesterday, I happened to be on My Verizon online, and I had a message showing that Verizon no long had the information on my phone (IMEI), and requesting that I open a Chat Window to update my info. At this point, the Note 4 is still running the Lineage 15.1. The Verizon team member asked me for the IMEI, and when I looked under the settings, it said "None" under IMEI. In a quick search, I found a forum on Lineage 15.1 that said turning of the screen lock and rebooting the phone will reload the SIM and IMEI info. That worked, and I was able to view the IMEI and verify connection. I explained my issue with the Verizon support, and she said everything appeared to be good on her end. Over the course of 15 minutes, we tested my connection and it worked. About 30 minutes after that, it dropped service again.
Finally, here is where it is at now:
I start with no service. If I do nothing but restart the phone, it will show LTE service for 2 or 3 seconds, then nothing. If I remove and reinstall the SIM, I will get the same 2 or 3 seconds, then nothing. If I turn Airplane Mode on and off, that does not reconnect the service. If I change the lock screen security to "None" and restart the phone, there is no service, but if I set Screen Lock to "Swipe" and restart the phone, I will have LTE service for at least 30 - 45 minutes before it drops, sometimes a few hours. When it does drop, it does not come back on it's own. The only way I have found to get it back it to "Screen Lock - None, reboot, Screen Lock - swipe, reboot".
Will replacing the modem fix the problem? Is there a specific modem that I need to match up to the ROM? Thanks!
bife2003 said:
I apologize in advance for the long read.
I recently activated Verizon service on a Note 4 that has been sitting unused since the Note 8 came out. The Note 4 is in perfect physical condition, with no scratches on the screen or body, and has been in a protective case since new. I did replace the battery in it prior to activation, as I expect for the life to have been deteriorated.
I did a factory reset and inserted my Verizon SIM card, and it worked perfectly. I installed my everyday apps and a few games on the phone, and I used it without any issue for about a week. During that time, it did install a couple of OTA updates, but I expected that since it had been "off service" for a few years.
After that first week, I put the SIM card back in my NOTE 8 for a couple of days, after which I went back to the Note 4. Initially, 4G data and cell service worked, but within the same day I started having service drops. If I was on the phone and a call dropped, it would show an error message saying "No SIM / SIM Error".
Her is what I have attempted so far:
First, I replaced the SIM with a new one. There was difference in the frequency of the random service drop.
When that did nothing, I assumed that one of the OTA updates from the prior week had done something to modem / radio. The phone was on 6.0.1 at that time. I unlocked the bootloader and installed TWRP, and first tried downgrading to stock 5.1.1, then to a "modified 5.1.1, then to CM 13, and now Lineage 15 (frequently factory reset / cache wipe. There has not been an improvement (or reduction) to the random service drop.
Yesterday, I happened to be on My Verizon online, and I had a message showing that Verizon no long had the information on my phone (IMEI), and requesting that I open a Chat Window to update my info. At this point, the Note 4 is still running the Lineage 15.1. The Verizon team member asked me for the IMEI, and when I looked under the settings, it said "None" under IMEI. In a quick search, I found a forum on Lineage 15.1 that said turning of the screen lock and rebooting the phone will reload the SIM and IMEI info. That worked, and I was able to view the IMEI and verify connection. I explained my issue with the Verizon support, and she said everything appeared to be good on her end. Over the course of 15 minutes, we tested my connection and it worked. About 30 minutes after that, it dropped service again.
Finally, here is where it is at now:
I start with no service. If I do nothing but restart the phone, it will show LTE service for 2 or 3 seconds, then nothing. If I remove and reinstall the SIM, I will get the same 2 or 3 seconds, then nothing. If I turn Airplane Mode on and off, that does not reconnect the service. If I change the lock screen security to "None" and restart the phone, there is no service, but if I set Screen Lock to "Swipe" and restart the phone, I will have LTE service for at least 30 - 45 minutes before it drops, sometimes a few hours. When it does drop, it does not come back on it's own. The only way I have found to get it back it to "Screen Lock - None, reboot, Screen Lock - swipe, reboot".
Will replacing the modem fix the problem? Is there a specific modem that I need to match up to the ROM? Thanks!
Click to expand...
Click to collapse
I think you might be dealing with 2 separate issues. I'm kind of guessing about the first issue but the second is a common problem.
I think the original problem is that your sim card is not making a good contact in the sim slot. You could try putting a think piece of cardboard or something that will press the sim card to the sim slot contacts (maybe check to make sure that there isn't any dirt on the contacts but from the sound of it I'm guessing your phone is pretty clean).
The second problem is that all of the aosp roms have varying degrees of signal loss that occurs. Some people have a lot and some not as much, but everyone is affected in some way with what people have been referring to as "sim death".
My suggestion would be to run a stock or modified stock rom until you get your sim problem straightened out and then if you still want to switch to an aosp rom then at least you'll know that any further problems are just the normal sim death that occurs from time to time with those types of roms.
If you've already updated your bootloader to a 6.0.1 version you can flash the modified stock rom that I put together. I haven't had any signal/sim issues at all with that and no reports of it. Like I mentioned before though, the only caveat is that it needs to be on a bootloader that is at least CPD1 or newer. If it's not then your wifi won't work.
Rom link If you're interested.
kevintm78 said:
I think you might be dealing with 2 separate issues. I'm kind of guessing about the first issue but the second is a common problem.
I think the original problem is that your sim card is not making a good contact in the sim slot. You could try putting a think piece of cardboard or something that will press the sim card to the sim slot contacts (maybe check to make sure that there isn't any dirt on the contacts but from the sound of it I'm guessing your phone is pretty clean).
The second problem is that all of the aosp roms have varying degrees of signal loss that occurs. Some people have a lot and some not as much, but everyone is affected in some way with what people have been referring to as "sim death".
My suggestion would be to run a stock or modified stock rom until you get your sim problem straightened out and then if you still want to switch to an aosp rom then at least you'll know that any further problems are just the normal sim death that occurs from time to time with those types of roms.
If you've already updated your bootloader to a 6.0.1 version you can flash the modified stock rom that I put together. I haven't had any signal/sim issues at all with that and no reports of it. Like I mentioned before though, the only caveat is that it needs to be on a bootloader that is at least CPD1 or newer. If it's not then your wifi won't work.
Rom link If you're interested.
Click to expand...
Click to collapse
Thank you for the reply. I think that you may be onto something with both issues. After posting this question today, I did examine the SIM slot, and although all of the pins looked good, and no dust or debris was visible, the metal guide over the SIM did feel slightly loose from the card. I did put in a thin shim, and the significantly improved the time that the phone stays connected. If that was a true issue, along with the possibility of the ROM causing a separate cause, I am absolutely interested on going back to a stock (or modified stock) ROM. The only reason that I did what I did was an attempt to fix the connectivity issue.
Thanks for your help. I will give your ROM a try and let you know how it works.
Hi everyone, I'm having terrible time with my note 10+ after the update. Basically after leaving the phone for a couple of hours it disconnects from everything even though that it shows full service. When that happens I am not able make or receive call, cannot use internet at all I cannot even use the SMS. Activating the airplane works but as I said for a couple of hours. Also the process of activating the airplane mode takes like 30 secs or more. I've tried everything (resetting network settings, restart, changing the SIM, used different carrier and factory reset) none of them worked. Yesterday I went to the local samsung store and they said to me that they heard of this problem from 3-4 more owners and said that these problems are common between S10s and note10s which has updated to the Android 10 recently and It will be fixed with a software update but the samsung customer services says the otherwise they are saying that they do not know anything about these kind of problems with those phones. Does any of you guys having problems like that or is it just my phone?