Database Info

[Q] Intermittent "No SIM Card-Emergency Calls Only"

Alright everyone, I've Googled my brains out (not in a dirty way) and haven't found any real resolution to the above issue. I've tried all the usual suspects; replacing the SIM Card, cleaning the SIM Card, adding tape to the back side of the card to ensure good contact, replacing SIM/MicroSD PCB Board, fresh Wipe of ROMs and Radios, etc. None of those things have had any real results except replacing the PCB-it seems to be less frequently occurring with the new SIM tray. Does anyone have any other ideas? I'm willing to try just about anything.
Thanks in advance.

mrfeuss said:
Alright everyone, I've Googled my brains out (not in a dirty way) and haven't found any real resolution to the above issue. I've tried all the usual suspects; replacing the SIM Card, cleaning the SIM Card, adding tape to the back side of the card to ensure good contact, replacing SIM/MicroSD PCB Board, fresh Wipe of ROMs and Radios, etc. None of those things have had any real results except replacing the PCB-it seems to be less frequently occurring with the new SIM tray. Does anyone have any other ideas? I'm willing to try just about anything.
Thanks in advance.
Click to expand...
Click to collapse
How often does this happen?
It only happens to me when I have to change the network mode. I've rarely seen it other except for maybe when my phone finds an LTE signal.
Otherwise, it could be the antennas. My mom once dropped her Samsung Focus and the antennas got screwed up.

Hangampalli said:
How often does this happen?
It only happens to me when I have to change the network mode. I've rarely seen it other except for maybe when my phone finds an LTE signal.
Otherwise, it could be the antennas. My mom once dropped her Samsung Focus and the antennas got screwed up.
Click to expand...
Click to collapse
Sometimes it'll happen through several reboots within a few minutes. It'll also happen when my phone is sitting, untouched, on my desk. There shouldn't be any network mode switching if my phone isn't moving.

mrfeuss said:
Sometimes it'll happen through several reboots within a few minutes. It'll also happen when my phone is sitting, untouched, on my desk. There shouldn't be any network mode switching if my phone isn't moving.
Click to expand...
Click to collapse
The only thing I can think of is to flash back to Stock AT&T software and see what happens. If you still have the same problem, it's most likely an antenna issue and you might be better off buying a new phone.

Time to return to stock and see what happens. Ugh, what an annoying issue.
EDIT: After returning to stock and installing TWRP I ran the stock UCMC1 software for a little while without incident. While I was setting up CM I got the dreaded "No SIM-Emergency Calls Only" message. I'm at a loss here. I guess it might just be time to start shopping for a new phone.
EDIT: I'm going to try running *SHUDDERS* stock Samsung/AT&T software for a few days to see if the problem persists. I'm pretty skeptical that this is a software issue, though, since I haven't seen too many people reporting this issue.

Good effort
Given all your efforts in eliminating various variables, I'm starting to believe Hangampalli is probably right and it might be a Hardware issue.
But it is a simple observation to stay on a solid stock ROM like the recent UCMC1 (original att version) for a couple of days and see what happens.
You remind me of myself with my Samsung Galaxy S (Captivate) random shutdowns last year. I chewed up all the threads at XDA back to back and tried anything, and it still did it ... but we all know when to quit.
Cheers to your efforts:good:
I727-UCMC1-CM10.1

Well after about 20 minutes into running the phone on UCMC1 Stock my phone came up with the same stupid error. I'm going to see if AT&T is willing to do anything for me since I just got this phone as a replacement in October. But if not, I guess I'll be phone shopping. :-/ Such a shame because I really love this phone and its community of users and devs.

mrfeuss said:
Well after about 20 minutes into running the phone on UCMC1 Stock my phone came up with the same stupid error. I'm going to see if AT&T is willing to do anything for me since I just got this phone as a replacement in October. But if not, I guess I'll be phone shopping. :-/ Such a shame because I really love this phone and its community of users and devs.
Click to expand...
Click to collapse
its the phone, is it still under warranty

I got the phone as a replacement from AT&T (bad headphone jack, last time) in about October. I'm going to try to see if they'll replace it for me. Fingers crossed.

Ya I have had this same problem. Changing ROMs fixed it for me though.
Sent from my SAMSUNG-SGH-I727 using xda premium

AT&T apparently warranties their replacement devices for 90 days or until the end of the original device's warranty, whichever is longer.
What does that mean for me? I'm boned. I guess I'm stuck with my iPhone until I buy a new phone. It's going to be hard leaving this great community of Developers and Users and shedding such a great device.

Humm... I wonder if I have the same problem, is there any tests you can do to see if it is the sim card tray or something like the attenna ? I seem to have service sometimes, not all the time.

Screen Flickering

I've read a few threads on the screen Flickering and there doesn't seem to be any resolution .
I'm on my 3rd tablet now (thanks best buy accident damage warranty!) And this one is flickering worse lately than ever. I updated to the latest firmware, yesterday only to boot up to horrible bouts of flickering during the setup screens.
The odd thing is, there seem to be no consistency to it. Some days it's so had I can't even use the thing, other days it doesn't happen at all. I use the tablet every day for notes or PDF viewing. I've used it with no magnetic cover (totally naked) and with the cover.. doesn't seem to change the occurrences.
I've turned overlays on/off force gpu render on/off.. nothing seems to fix it. Sometimes changing the overlay will reduce the flickering other times it doesn't affect it at all.
I hate to say it, but if I can't resolve it, I'm going to be forced to move to the surface 3.
I'm an electrical engineer and I've done as much trouble shooting as I can think to do.. but I've come up empty handed.
Anyone else have these problems? Has anyone found a definitive fix?

I sent mine back 3 times. The first was a reset. Thanks for wasting my time. The second was a motherboard and that didn’t do it. The third time they did a motherboard, digitizer, and usb port. It's finally stable and back to normal. After 5 trips back, the BB warranty triggers a new unit. Check if it triggers a refund.

I get it occasionally, so far I'm able to resolve it by booting into custom recovery (TWRP) and clearing dalvic to allow all apps to rebuild. Sometimes this resolves it for a few days, sometimes a couple of weeks. Its a repeatable "fix" that makes me question if the issue is related to memory or trim or something like that. Kind of reminds me of how with the first generation nexus 7s one would see slow downs after a while and filing storage with fake data then deleting it would improve performance for a while.

I'm definitely not a tender user of the device. I go back and forth between multiple ROM's and kernels on a daily basis testing what is testable, and unfortunately also what is not. Anyway, even though mine was bought as refurbished on eBay, I have never had any issues like the ones you describe. More specifically, I have never had any issues what-so-ever, that was not created due to my own ignorance. To me the device seems indestructible.
Besides, I would hate to be in the place of my device, or I would definitely have turned schizophrenic. Should I feel bad about pushing it through all this?

Because we're trying to figure out if it's related to a specific device type, which one do you have? P900, 905, 907A or another?

ShadowLea said:
Because we're trying to figure out if it's related to a specific device type, which one do you have? P900, 905, 907A or another?
Click to expand...
Click to collapse
P900 wifi. Us version bought at best buy.
Today the tablet has been rock solid, I have literally done nothing between when it was flickering like mad and now.
I wonder if it might be related to some kid of data transfer. either over wifi, or when data is written or read from storage or SD card. I've take then SD card out to eliminate that as the problem.

Mine was P900 from BB

Issue lies with the screen.
This happened with me I sent it back to Samsung, 3 times. They seem to have finally got it right. They replaced the battery and then the display screen. Now it appears to be working I will let you know after a month if it is still good. They also told me that they will not replace the device even though I bought it and the issue was right from the start. Not even 6 months old. When working the device is excellent.

Ah, so now we know for sure the battery is replaceable. That's good news. Maybe someday our batteries will no longer hold a charge and we can replace it. Now for a good video on tear down and what tools to use to do that and where to get a replacement battery. I know it's early for most of us but someday......we will have to replace that battery. I'm one of those that keep my toys (computers/laptops/tablets/phones,) for many years.

Mine is running like new since last service. Getting the BB Geek Squad warranty has paid for itself already. I get 2 years on anything over $500.

Mine is a p900. I purchased from samsung website. Mine has been doing it fresh out of box. So bummed.

Ive had my 12.2 since march and it recently started flickering. It seems to tuen of the screen for a millisecond especially when lots of refreshes happen. Like scrolling a pdf. A few days back it was bad. Now it has gotten better and I havent noticed anything.

{Diemex} said:
Ive had my 12.2 since march and it recently started flickering. It seems to tuen of the screen for a millisecond especially when lots of refreshes happen. Like scrolling a pdf. A few days back it was bad. Now it has gotten better and I havent noticed anything.
Click to expand...
Click to collapse
My P900 has just begun flickering exactly as you describe. So I should just be patient and hope it goes away by itself?

I'm flickering again. Turning the screen brighter is what triggers it for me. Returning to stock just to get it back and have it flicker again to hit the magic 5 returns may be what I have to do.

https://youtu.be/CvxbVft69Kg
I just followed this guide. Its been a week now, not had any flickering since I did it.

Manya3084 said:
I just followed this guide. Its been a week now, not had any flickering since I did it.
Click to expand...
Click to collapse
Lifting the motherboard only temporary close the gaps of cracked battery connector. The permanent fix need to do: re solder the battery connector.
Look closely under magnified glass or microscope , you'll see the cracked solders. You can test by pushing the connector slightly, a bad one will move easily or lift off from its solder joints.
This video was removed from the poster after I pointed out his guessing solution. Flickering screen has nothing to do with LCD connector on the motherboard.
Lifting mother board actually you're applying pressure on the battery connector from rear cover.

I have had my P900 sent to Samsung service twice without having the screen flicker fixed. I thought this was a known problem and that Samsung themselves should be aware of it? Maybe I should supply some XDA links next time...
Skickat från min SM-P900 via Tapatalk

bluebirch said:
I have had my P900 sent to Samsung service twice without having the screen flicker fixed. I thought this was a known problem and that Samsung themselves should be aware of it? Maybe I should supply some XDA links next time...
Skickat från min SM-P900 via Tapatalk
Click to expand...
Click to collapse
Depend on where you send for service, they know how to fix it now. Service Centers actually are contractors provide services for Samsung and others, the fact that most people don't know.
http://forum.xda-developers.com/showpost.php?p=59573206&postcount=100
It Works. Battery connector replaced. Smoooooth
After 2 visits to Samsung , my unit finally works fine.
Motherboard and LCD were changed first time. But issue persisted.
Second time, battery connector was replaced. Since then it has worked very very smoothly.

Beut said:
Depend on where you send for service, they know how to fix it now. Service Centers actually are contractors provide services for Samsung and others, the fact that most people don't know.
http://forum.xda-developers.com/showpost.php?p=59573206&postcount=100
It Works. Battery connector replaced. Smoooooth
After 2 visits to Samsung , my unit finally works fine.
Motherboard and LCD were changed first time. But issue persisted.
Second time, battery connector was replaced. Since then it has worked very very smoothly.
Click to expand...
Click to collapse
Thanks, missed that other thread. Next time, I'll send them an en explicit request to replace the battery comnector, and refer to those two threads.
Stefan
Tapatalked on some kind of Samsung tablet

Repeated Micro-SD Mounting Notification Issue - Potential Fix

Alright friends. The Micro-SD notification issue that a startling number of people have been having. I have also been suffering this issue and did not want to believe it was hardware based. I have believed since the beginning, that this is an issue with doze settings killing power to the internal SD slot. I managed to track down what I believe to be the offending service that doze is messing with. Follow the instructions below to fix this:
1. Go into system settings and select 'battery'
2. From the battery settings, select 'battery usage', and within battery usage, select 'more' at the top right of your screen
3. Select 'optimize battery usage' within 'more', and switch the drop down in the next screen from 'apps not optimized', to 'all apps'.
4. Locate the 'External Storage' service, and set the slider next to it into the off position. This keeps doze from messing with this.
5. Make sure 'External Storage' shows up in the list of apps that are not optimized now - Profit
I have been using this for the last 24 hours and have had absolutely zero SD mounting/unmounting notifications outside of the required one when you reboot your device. I really hope this works as well for everyone else in here as it worked for me.
Please let me know if this setting works for everyone else in the thread below this OP.
MODS: Please pardon if I have placed this thread in the wrong section. I didn't see anything else related to a solution in any of the other selections, so I figured I would share these steps which seem to be working for me.
Thanks all.
PS: I do not know if it matters or not, but I advise a format of the SD card as well through the storage settings on your device. I did that after following the above steps as well.

This might also be applied to alarm apps to fix problems with them failing to go off.
Sent from my SM-G935T using XDA-Developers mobile app

Tried this before bed last night. Didn't format sdcard though, dont see what that would do. Anyway, woke up this mornin to an sd card notification :/ one thing i did notice though, instead of the screen slooowly fading on when turned on, it instantly turns on now. So it's definitely affecting something.

Worth a shot. Nice find!

I disabled battery optimization weeks ago and still got the SD card notifications. This isn't the issue. I'm 99% convinced this is a hardware issue.
In regards to alarm apps. Yes turn off battery optimization for them.
Sent from my SM-G935T using Tapatalk

Thanks for the feedback guys! Yes. I did receive a notification over the night while I was sleeping as well. The notification that happens over night is the only one I am receiving now though. I definitely consider this an improvement. I can live with one a day (not including if you reboot the device). I was getting the SD ejection/reconnect notification no less than 10-15 times an hour or so before this. I suspect that the external storage still goes into a low power mode or something when the phone is left in a state of prolonged inactivity such as during the night while we are sleeping. I am not sure if there is anything that we can do about that particular problem from our end though. I am admittedly not savvy enough to dig into the code.
I suspect that wonky/overly aggressive doze/optimization settings are to blame for a few issues that people are having with this device. I have noticed that the optimization settings are a bit of a mess. Go through and see what else y'all can figure out as well by tweaking these things. Feel free to keep the thread going with those findings.
I wonder if this is just how doze treats external storage....I wouldn't know. I have been a primary Nexus user for a while before the S7 Edge (still have a 6P as well) and as you know. There isn't any external storage in that line to 'optimize'...Lol

jrwingate6 said:
I disabled battery optimization weeks ago and still got the SD card notifications. This isn't the issue. I'm 99% convinced this is a hardware issue.
In regards to alarm apps. Yes turn off battery optimization for them.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Interesting.....did you also turn optimization off for SystemUI as well? I have noticed a marked improvement by disabling optimization for both SystemUI and External Storage. I have what seems to be one of those problematic Vietnamese originated models.
I have a replacement coming in the mail and I will test both for a few days before sending one back to T-Mobile

For any in here who were interested about a follow-up. I have since received and switched out my devices. My new device is now 24 hours in, and not a single SD notification, excepting the one at the time of device reboot.
@jrwingate6 might be correct about the hardware thing.
I haven't messed with optimization settings either on this one. It just works.
I did still notice a marked improvement with the optimization settings tweaks on the device that was having the issues though

This is without a doubt 100% hardware related. I advise anyone having this issue to replace the device ASAP.

LuigiBull23 said:
This is without a doubt 100% hardware related. I advise anyone having this issue to replace the device ASAP.
Click to expand...
Click to collapse
I totally agree with you after my experience between my device purchased on release day, and the one I have now.

I got an early release too and was the first to make a post on this issue and no one knew what I was talking about. Long story short, I had to get a replacement and have not had that issue with this new phone

LuigiBull23 said:
This is without a doubt 100% hardware related. I advise anyone having this issue to replace the device ASAP.
Click to expand...
Click to collapse
lol i even taped the crap out of the sd card, and it got worse
---------- Post added at 11:12 AM ---------- Previous post was at 11:10 AM ----------
so how exactly did we come up with doze being the issue?
---------- Post added at 11:33 AM ---------- Previous post was at 11:12 AM ----------
went ahead and asked for replacement on live chat. have had s6 replaced once before never said anything about $5 exchange fee till now

It can be a faulty SD card or a non Samsung one that isn't playing nice with the S7 Edge.
My fiancée and I both have the S7 Edge and we both have the Evo+ (64gb from Samsung) and we DO NOT get any SD card notifications other than when we reboot our phones.
Sent from my SM-G935T using XDA-Developers mobile app

I'll add this to the mix:
S7 edge silver on vzw. Have been getting the notification a dozen times a day.
So I put lots of music on the SD and set it to continuously shuffle through (with the volume all the way down). Not once during the play has the notification shown up. Also hasn't shown up while transferring massive files onto this SanDisk 200GB.
If I actually eject the SD during playback, PowerAmp stops playback and doesn't resume when the card is reinserted. So I know the notification is not from the card being physically disconnected in the slot, because the music plays for hours on end in shuffle.
This supports the doze theory because the active read would keep the storage manager from sleeping.
So to make this a hardware problem, we need a hardware defect where the card is repeatedly identified as being inserted, but only when data is not being transferred to/from the card.
However, this does not explain reports of replacement phones not having the notification issue. Unless those users are configuring the replacement differently than the original.
Anecdotally, has anyone seen the S7 trigger a card notification while read/write to the SD was executing?
Sent from my SM-G935V using XDA-Developers mobile app

I do not have my s7 edge until mid week but did you guys try going into app info for the SD card mounting app or service and turning off notifications?
Sent from my LG-D851 using XDA Free mobile app

Richieboy67 said:
I do not have my s7 edge until mid week but did you guys try going into app info for the SD card mounting app or service and turning off notifications?
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah dude. That doesn't work this time around. The notifications still happen. The only way I found to get a marked improvement on this matter (outside of an outright exchange) is to turn off the doze setting for External Storage. This seems to dramatically improve things, but not make it perfect. I gave up the good fight about a week ago or so and had a replacement shipped to me. I haven't had a single issue with the SD notification since in the new device, and my setup is exactly identical to my original device. The only difference is that I haven't had to mess with the doze settings.

the only fix. tell your customer rep you have unmounting/mounting issues and you have done factory reset/ clear cache. tried 2 or 3 different SD card or tried SD card on another phone and it works. have them replace the phone and done. had tmobile replace my phone, fastest ever. got it in 2 days and i live in hawaii! 2 days usually means 4 or 5. but no SD card notification for 3 days now. only get it on restard

I used to only get it on reboot and now it's 2-3 times a day. Wonder if it's just the sim tray? I'd rather shell out a few bucks for one than buy a whole new screen protector and dbrand skin. Lol
Sent Via My Samsung S7 Edge

I posted earlier (above) trying to explain why this could be a software problem, but it isn't. It's hardware. Swapped out the S7 edge at the about 12 day mark with VZW and got a new phone. SD notification only on restart now. Rep asked if the phone was losing the SIM as well.
Anyone noticed also that the new posts of SD problems stopped about two weeks ago? Because they fixed it after the initial run.
Sent from my SM-G935V using XDA-Developers mobile app

I just ordered a replacement because of this issue, it does seem like i am having slight network performance issues as well. We shall see.

Sooooooo many problems since nougat update!

Well this really sucks. I've been telling people for a long time that my G5 has been the best phone I've ever had...a true powerhouse. Then came the Nougat update. Since then it's been nothing but problems. I called Verizon, LG (useless), and Google. All said 'try a factory data reset, that should fix everything'. Yeah, right. So after the Ohhhhhhh-so-painful FDR, I still have all the same problems. When plugging in the oem or third party fast chargers (I have two of each), the notifications will simultaneously say "slow charging" and either "charging" or "fast charging" at the same time. Unplugging and reconnecting will fix it every time. Also, I'm getting ghost images when changing screens...I can still see a shadow of the previous screen which eventually fades away. These are both just minor annoyances, but still weren't there before. But also, my NAV appears to have a hard time keeping track of where I am. More annoying. But the biggie is that I can no longer use any of my many Bluetooth headsets for phone calls. You just can't have a Bluetooth conversation anymore. Streaming audio is fine. But calls aren't doable. That's a problem. Since I already tried an FDR to no avail, Verizon is going to send me a new phone. All I can say is if it comes with Marshmallow, I'm leaving it that way. Any benefits that Nougat brought are far outweighed by the problems. I'll wait until they fix it, maybe then. Anybody else been so plagued by this update?
D Dave

I have the same problem.. I have to charge and re-start the phone to make the phone "charging" otherwise it is intermittently connected and disconnected.. I've done factory reset and didn't work out also.. I guess getting a new replacement from T-mobile is the option here.

I got the new phone that Verizon overnighted to me and got it all set up. It thankfully came loaded with marshmallow and is working fine, but keeps prompting me to install Nougat. I'm going to keep postponing the update for now to give them a chance to work the bugs out. Is there anybody out there who has installed the update on their Verizon G5 without any problems after?

I have the charging issue as well and it started with 7.0.

You should report it. They won't fix something if only a couple people report the problem. They sent me a new phone and I've managed to defer the 7.0 update for over a week now. It prompts me everyday, but I just say later! I'll wait awhile to see if they fix it. The unbearable Bluetooth call quality was just totally unacceptable.

Nougat?
My G5 is still on Marshmallow, and does not see that there is any update to Nougat available. So what are you all talking about?

What carrier are you with? I'm on Verizon, so maybe not all carriers have it yet. Or maybe you're one of the lucky ones who wasn't randomly chosen to be a guinea pig and find all the bugs and glitches. ☺

I'm on Verizon.
This is a Verizon LG G5 forum. Are those posting here WRT Nougat posting in the wrong place?

Dangerous Dave said:
Is there anybody out there who has installed the update on their Verizon G5 without any problems after?
Click to expand...
Click to collapse
Me, totally problem free. No problems of any kind but it did fix one bug, I had an app that wouldn't run in Marshmallow and it's back working normally again with Nougat, who knows why?

jpradley said:
I'm on Verizon.
This is a Verizon LG G5 forum. Are those posting here WRT Nougat posting in the wrong place?
Click to expand...
Click to collapse
Try to keep up.

I have the G5 on Verizon and am fully updated. The only problem I've had is with storage space. 85% full and I'm lagging frequently. I've deleted as much as I can, to no avail. I can't seem to get anything successfully moved to the SD card, so I'm not sure of its purpose.

I´ve got exactly the same problems and more.... What did you do to fix them in the meantime?
To add another problem, my fingerscanner isn't working 9 out of 10 times.
It became an annoying piece of ****! Please help to get my awesome phone back.
Greetz from the Netherlands

I've had other bluetooth issues... I have to restart bluetooth nearly every day to get it to connect to my devices, it's as if the bluetooth apk is hanging up in the background.
That said... My phone updated to 27A this morning, so I guess I'll find out in the next few days if I have the same problem, lol

Well the 27A update must literally be ONLY the security patch. It didn't fix the bluetooth issues...

Seriously this update has been the worst. I too am experiencing the power cable issue. I'd say 7 out of 10 times it tells me it's slow charging. Simply reseating the cable fixes it every time. The most frustrating part for me is Facebook and Twitter. With the first Nougat update the Facebook app began to bug out. At least once a day it randomly crashes, even when i'm not actively on it, and begins a crash loop that won't stop until I restart the phone. that usually fixes it. I'd say every other week I've had to straight up re-install the FB app to fix the crash loop. and now after the recent update that was pushed the twitter app keeps failing to load some images. Most tweeted images show up fine but profile/banner images will not. Again fixed with a restart. This is really quite frustrating. I don't understand what they did to break Nougat so badly. My friends Pixel hasn't had any of these issues. I'm getting so fed up with my G5. I love it but it just so damn locked down and now this. It really makes me wary of getting another LG phone

Well, it's been over three months since I started this thread. The problems after the Nougat update were just unacceptable, so Verizon sent me a new phone loaded with Marshmallow. I've been deferring the update every day for three months. Last night I accidentally tapped the wrong spot on my screen and it installed the damn Nougat update. I've had the update less than 24 hours now, so haven't tried everything. But I can tell you they haven't fixed the problem with the slow charge/fast charge, as it came back IMMEDIATELY after the update. I called Verizon today to ask why the hell LG couldn't fix that issue in three months time! Verizon called LG for me and inquired if there was a fix. LG said if I send the phone back to them, they'll fix the corrupted files and send it back to me. Really?!? Both my G5s experienced the same problem immediately after the update and they couldn't fix the issue in the download in three months time? Douchebags. Now I have to decide which is a bigger pain in the a$$, having to unplug and replug my phone every time I want to charge it...you know...until I get a new phone, or format it, send it back to them for however many weeks it takes them to (theoretically) fix it, and rebuild it when I get it back. Why, oh why, wouldn't they implement the fix they already have, instead of pushing out flawed software, then making me send my phone in to them to fix. Grrrrrrrr!

Dangerous Dave said:
Now I have to decide which is a bigger pain in the a$$, having to unplug and replug my phone every time I want to charge it...you know...until I get a new phone, or format it, send it back to them for however many weeks it takes them to (theoretically) fix it, and rebuild it when I get it back. Why, oh why, wouldn't they implement the fix they already have, instead of pushing out flawed software, then making me send my phone in to them to fix. Grrrrrrrr!
Click to expand...
Click to collapse
Unfortunately don't have anything helpful for you, other than to say, you're not alone, and I similarly got sufficiently pissed with this bug today to see if there was a solution yet.
Pretty sure you answered your own question though: they don't actually have a fix because LG has likely stopped developing new releases for the G5 in anticipation of the G6 release. They want you to send it back to them for the "fix" because it's a pain in the ass and transfers the opportunity cost onto you, which hopefully (in their eyes) means they can do absolutely nothing.
I'm just.... beyond frustrated with this ****ing phone. I really wish that I would have limped by on my old HTC M8 until the V20 came out, even with its barely-chargeable battery. At this rate, I would have been better off with a pixel or internal-battery phone for that matter. There is just seemingly no end of software and hardware issues with this phone, and LG's piss-poor customer service gives you almost no recourse for any of them

Hi. G5 VS987 Owner here with a build date of 10/2016 so I've managed to survive the bootloop issues that plagued a great number of us thus far.
My theory is: LG has no clue on how to push an OTA update.
My question(s) are: How many of you updated with the OTA?
And how many updated via LG Bridge or some other flashable method?
I'm wondering what if any difference knowing this makes because while this phone has honestly been the best/fastest/bug free phone I've ever used...the update nagscreen has me wanting to choke the [email protected]!%# out of it. It just won't go away.
I really wanted the Note 7 before they blew up...What to do guys?
---------- Post added at 02:43 AM ---------- Previous post was at 02:41 AM ----------
Another thing...is there a way to flash back to MM if this update really goes south?

I updated to Nougat OTA with no problems except the power cord which I fixed.
Here's how I did it:
DISCLAIMER! I KNOW this has nothing to do with the problem and cannot possibly fix it but... it did fix it for me so give it a try, OK?
1. When you get the slow charging message look at the power cord, turn it around and plug it in the other way, see if that helps. Once you've determined that plugging the power cord in one way reduces the frequency of the error just keep on doing it that way and in a couple of days the problem will be gone!
I know, I know, but try it, what can it hurt?

Well, interesting update here. Verizon said I could send it back to LG to have corrupt files replaced. I decided that neither option, living with the problem or shipping the phone back to LG, was acceptable. I called Verizon back and told them so, asking for a replacement and hoping it would come with MM. They just sent me a replacement, and it came with Nougat already on board. But would you believe this phone works perfectly! I mean, it rocks! I have NONE Of the problems I had with the last two phones after the OTA update. So maybe the OTA really is a piece of crap. But I gotta say, it's nice to love my phone again.

Question Sim recognition issue

Owned the phone for about a month now. Phone was working perfectly fine for the majority of this time. I use 2 different sims and they were both working smoothly until recently.
A few days ago, I woke up and the phone wouldn't recognize the Sim cards anymore. I took out the Sim tray, cleaned the Sim cards and the tray as thoroughly as I could and they both started working again. A few days later, I restarted my phone and both of the Sims stopped working again.
This time nothing I would do would solve the matter, so for the next few days the phone wouldn't recognize either Sim. I have unlocked the bootloader and rooted, factory reset it and updated it none of which seems to solve the issue.
I use this phone for gaming so last night to my surprise one of the Sims started working (sim was in for a couple of days) and all connectivity was perfectly fine - I tried putting in my other Sim as well but again the phone wouldn't recognize them anymore. Tried putting in only one card on the Sim 1 slot but it made no difference. I don't understand what the issue could be.

Do you have a converted CN version or did you buy a global version? (just curious, as far as I know only CN -> WW versions faced this issue and I would like to know if this is a coincidence or an issue with these versions. But I could be wrong as well)
Nevertheless I would make use of warranty and send it back to Asus to get it repaired.

Yeah it's CN version > WW ROM. It's absurd how randomly it was hit with this issue. Again, the phone was reading a sim card perfectly fine out of the blue last night, then when I took out the Sim tray to insert another card, went back to square one and wouldn't recognize either.

I know.. If you had searched this forum or the rog reddit you would have noticed there are multiple topics like yours and all people explained the very same. Seems totally random.. sometimes it works, sometimes not. Unfortunately no one was ever able to post an accurate answer of why this is the case or how to fix it. At least there is none here, on reddit or the zentalk forums.
Since all device so far were CN -> WW version I don't know any successful case. Asus mostly rejects the support and redirects people to their sellers but those mostly refuse to do something. (they probably know that issue and it's cheaper to do nothing)
I wish you best of luck. Maybe you could try to contact Asus and report the outcome so we finally have a documented successful repair.
Edit: as said, that's only my knowledge, maybe there is a fix and someone found a way but they either didn't publish it or they posted it in a not so well known forum.

I wonder if the connections that touch the SIM are poorly designed. If it is such a widespread issue that randomly seems to come and go, it could be similar to the issue I had with the Kunai 3.
The pins on the side are designed to give a little when sliding the controller off and on the mount or charger. After moving them between the mount and charger twice, some pins fell off and others never popped back into place so they could make a connection. It turns out they never secured the pins well enough to handle it.

Hello, I had a similar issue.
My sim-cards wouldnt be recognized, sometimes only one of them, sometimes both. Additionally, my fingerprint-sensor wasnt working too. By checking pictures of a disassembled phone I could locate the problem inside. It has a connector on the lower end of the phone, which is for sim and FP-sensor. I can definitely and easily come loose.
Quick and dirty fix for me, was pressing with controlled but quite some force on the lower end of the LED-Rog logo while the phone laying flat on the table. I used my thumb, pushed and restarted the phone to check. Didnt work, pushed a bit harder and restarted again until it worked. The back glass has some flex to it, to make it possible to push the connector back in. Still, be careful to not break it, if you try it yourself.
When I found that solution, I've sent it in on warranty for proper fixing with this Information to ASUS. They replaced allegedly the mainboard. But I actually think, they just fixed the connector in place, because bending the phone to a certain degree "unfixed" it in my case again. I dont know, if its the same issue you have, but if it is, hope it helps everyone.

r0me5 said:
Hello, I had a similar issue.
My sim-cards wouldnt be recognized, sometimes only one of them, sometimes both. Additionally, my fingerprint-sensor wasnt working too. By checking pictures of a disassembled phone I could locate the problem inside. It has a connector on the lower end of the phone, which is for sim and FP-sensor. I can definitely and easily come loose.
Quick and dirty fix for me, was pressing with controlled but quite some force on the lower end of the LED-Rog logo while the phone laying flat on the table. I used my thumb, pushed and restarted the phone to check. Didnt work, pushed a bit harder and restarted again until it worked. The back glass has some flex to it, to make it possible to push the connector back in. Still, be careful to not break it, if you try it yourself.
When I found that solution, I've sent it in on warranty for proper fixing with this Information to ASUS. They replaced allegedly the mainboard. But I actually think, they just fixed the connector in place, because bending the phone to a certain degree "unfixed" it in my case again. I dont know, if its the same issue you have, but if it is, hope it helps everyone.
Click to expand...
Click to collapse
Good tip and glad it worked - this could help a few out there. Perhaps ASUS should have included some instructions explaining how to press/bend the device back in order when it happens ...

I had the same issue and quickly found a fix. I bought a OnePlus 9 Pro and relegated this glitchy piece of junk to my desk drawer. Good riddance.

nickdagriff said:
I had the same issue and quickly found a fix. I bought a OnePlus 9 Pro and relegated this glitchy piece of junk to my desk drawer. Good riddance.
Click to expand...
Click to collapse
Paying over $2,000 for a OnePlus 9 Pro seems like an expensive solution, but I am glad it worked out for you. Best of luck over there.

r0me5 said:
Hello, I had a similar issue.
My sim-cards wouldnt be recognized, sometimes only one of them, sometimes both. Additionally, my fingerprint-sensor wasnt working too. By checking pictures of a disassembled phone I could locate the problem inside. It has a connector on the lower end of the phone, which is for sim and FP-sensor. I can definitely and easily come loose.
Quick and dirty fix for me, was pressing with controlled but quite some force on the lower end of the LED-Rog logo while the phone laying flat on the table. I used my thumb, pushed and restarted the phone to check. Didnt work, pushed a bit harder and restarted again until it worked. The back glass has some flex to it, to make it possible to push the connector back in. Still, be careful to not break it, if you try it yourself.
When I found that solution, I've sent it in on warranty for proper fixing with this Information to ASUS. They replaced allegedly the mainboard. But I actually think, they just fixed the connector in place, because bending the phone to a certain degree "unfixed" it in my case again. I dont know, if its the same issue you have, but if it is, hope it helps everyone.
Click to expand...
Click to collapse
Works like a charm here! Congratz!

Omg worked here too, now I have a Poco F3 AND a revived ROG Phone 5...

.

You are the mvp. I love this phone and using it for almost a year. Suddenly sim no longer detected. I tried everything, unlocked bootloader, update firmware. Hour and hours of trying to revive it. I even called Asus and they said to call the Chinese warranty support. Then finally came across this thread. Pressed down hard on the lower end of the logo of the phone on its back. Restarted and now it's detecting the sim again. Thank you so much