TLDR
If you are missing your visual voice mail tab for Project Fi and/or your USB OTG drive takes multiple inserts to get recognized then re-encrypt your phone and the problems should go away.
---
For a while now, I would notice every once in a while I would lose the visual voice mail tab in the phone app (phone service provided by Project Fi)
I got a clue as to the problem from this post:
https://productforums.google.com/forum/#!topic/nexus/s6DLAee-jwc
where a user suggests turning the phone off and removing/reinserting the SIM card tray. This did work, but seemed like more work than I wanted to do (I don't want to carry around a paper clip or SIM removal tool)
I then noticed that whenever my Visual Voicemail tab disappeared, the celular status said "No SIM card" instead of "No service"
It turns out much of the time I have my phone running in Airplane mode with WiFi enabled as this is the only way to reliably force the phone to use WiFi over cellular service on Project Fi.
When I reboot in airplane mode, upon reboot, the cell service status says "No SIM card" If I reboot in regular mode, it comes up with Project Fi as the service.
By chance, I noticed on my friend's phone, after reboot in Airplane mode, their phone said "No service" as opposed to the "No SIM card" I was seeing.
I examined the dmesg for the boot process on both units and noticed on his phone, it was recognizing the SIM card at boot. On my phone, the SIM card wasn't being recognized.
With that clue, I realized that instead of shutting the phone down and popping the SIM card, I could get Visual Voice Mail back by toggling airplane mode. This gets the SIM card recognized, before going back to airplane mode. Once the SIM card is recognized the Visual Voice Mail tab returns and is visible in the phone app.
So if you are missing the Visual Voice Mail tab, make sure your phone has recognized your SIM card and if not, toggle Airplane Mode to get it recognized.
Now as to why his phone recognized the SIM card at boot and mine did not, I realized a separate problem might be related.
When I first got my USB On The Go flash card reader, it would get recognized immediately upon inserting into the USB C port on the phone. However after a while it would only get recognized upon second insert. The first insert would do nothing.
After looking at the dmesg logs, it looked very similar to my SIM card not getting recognized at boot.
Knowing that this used to work on my phone, I figured I must have done something to cause the delayed recognition. After thinking about it, I realized while both phones were rooted, my phone was decrypted and his was not.
That turned out to be the issue. I don't know the specific cause, but I went back and flashed the stock boot.img and recovery.img then let the boot process re-encrypt my phone.
Now my SIM card is recognzied on reboot even if I rebooted in Airplane Mode. Thus my Visual Voicemail tab is always present.
Also my USB OnTheGo flash card reader is recognized immediately every time I insert.
There is probably some timing/timeout problem when the user partition is decrypted so the kernel gives up before recognizing some devices.
I flashed TWRP recovery and re-rooted the phone (resulting in a modified boot.img, disabling dm-verity and force encryption, via the systemless root install) and the SIM card is still recognized at boot, so the only change then was the re-encryption of my user partition and the resulting modification that would entail for the boot process (ie the problem wasn't originally caused by TWRP recovery or the modified boot.img from the systemless root install)
Also, I had previously done some encrypted vs decrypted performance comparisons and really could detect virtually no difference for regular usage, so fixing the Visual Voicemail and USB OTG insert issues were a good reason to stay encrypted.
Hope this helps someone else. These weren't major issues, but were nagging at me every once in a while when I encountered them.
Interesting, I also noticed my visual voicemail on tab disappearing. I have poor cell service in my home, like you, I turn on airplane mode and WiFi to force calls/text over the WiFi connection instead.
Related
Hey guys,
So I’m having a bit of a dilemma. Here's my situation, my Xoom had been updated to 4G already. My issue is that I can't diagnose when exactly a loss of data connectivity occurs when swapping sims with my Thunderbolt.
Here is what I’ve found so far.
-Upon receipt of Xoom back from Moto I,
1. Flashed recovery-Tiamat-R4c-100611-1150-cwm.img
2. Flashed Universal root method.
No problems with Wifi or Data until I attempted to swap Sim card with my Thunderbolt. Then complete loss of data and WiFi. I tried restarting and removing sim, Power cycling with Vol-up/Pwer with no results.
-From here I hard reset back to stock.
I then Reflashed recovery-Tiamat-R4c-100611-1150-cwm.img.
Root was still intact so I flashed Android Honeycomb 3.2.2 - Stock & Rooted, which put me at HLK42B. I had 3g/4g however no WiFi. At this point I tried sim swapping without powering down and after a force restart was successful in using the TB sim card. My Verizon updated to my unlimited plan and all on the Xoom home screen.
I however decided to try and fix WiFi so I without wiping flashed HLK42C provided by SemperAndroid. This restored all WiFi connectivity and 3g/4g remained intact. I also flashed the "Tachi" kernel and OC'd to 1.4. I experienced no outages of data all last night and today.
However this afternoon I attempted to swap my sim card and after a forced restart was met with no data connectivity but working WiFi. I power cycled several times with no result. I then powered down and pulled the sim, put in the Xoom sim and restarted with no results. However after approx 3-4 times of powering down and pulling the sim I received about 20 seconds of 1x connectivity and then a short while later I noticed I had 3g showing but when I went to connect to browser it disconnected and I received a page couldn’t be loaded.
I also tried to restore a backup I had to HLK42B but it did not restore any data.
So it appears that so far we can only swap sims successfully on HLK42B however we lose WiFi connectivity as a result. Anyone have any other findings to share?
Thanks for your time..
Dave
Update:
Alright some more trial and error. I'm can't completely confirm it yet but so far it really seems that the manner in which you swap the sim card is what might cause the loss of data.
Last night I reverted to a backup of HLK42B which didn't initially store data but after troubleshooting a few times I learned that putting the settings into CDMA only and restarting seemed to reattempt the activation to the network.
Anyways, after getting back data, I decided to swap in my TB sim again. This time I pulled the tray out waited about 15 seconds for the "Please insert sim card" popup and plugged my TB sim back in then restarted via the popup.
Viola, 4g connectivity, I had lost root due to restoring my backup of HLK42B so I flashed recovery and universal root and data checked ok. I then flashed HLK42C over HLK42B and still retained data while on the TB sim. Backed up and flashed Tachi kernel and still maintained data. I then pulled the sim tray in the same manner allowing 15 seconds or so and reinserted the Xoom sim and restarted via the popup. Again no issues with data connectivity.
My only issue I can see was the manner in which I pulled the sim card out initially yesterday. In an attempt to trick the system I pulled the Xoom sim and immediately popped in the TB sim without allowing the device to popup with the notification of "No sim card inserted" After that I experienced the loss of data..
Again these aren't backed up with any technically "real" proof, just trial and error.. If anyone has anything else to share please let me know..
Dave
You just picked the wrong time to swap cards. VZW was having connectivity problems yesterday.
Sent from my Xoom using Tapatalk
Hi all,
This is my case with the hope of getting any help or lead in order to solve my problem:
After a long research I bought an brand new LG D800 already sim unlocked in the US and brought it to my country (Costa Rica). I made sure the frequencies supported by the D800 are the ones used in my country. In fact 2 years ago I bought another phone that uses same frequencies and had had no problems ever.
As soon as getting in my country I placed the SIM card I'm using in my current phone into the G2 and it recognized the signal and connected to the operators network. I started to make and receive calls almost immediately, and also SMS' without issues. So I started to migrate all my data from the current phone into the G2. I used Titanium Backup for this, so I rooted first the phone using the guide I found here, and basically what I did is installed the apps from Google Play and then restored data using Titanium.
After the second day of use suddenly I found out that I wasn't able to make or receive calls since the phone lost connection to the operators network only allowing emergency calls but the signal bars were full (see scren capture). Sometimes when restarting the phone I get "Phone not allowed MM6" message just after the phone tries to connect to the operators network.
Went to the phone company offices and they tried to help me and made some simple tests, without changing anything inside, such as checking Android's network configurations, checking in their system to verify the IMEI wasn't blocked or reported (the IMEI is clean), also checked the sim configuration and after more than 45 minutes they were not able to find anything wrong in their system or with the phone itself. They also made a final test taking a working sim and put it into the G2 and gatting same emergency calls mode, and took my sim from the G2 and put it in another phone and that phone was able to make and receive calls. So they concluded that the phone has a "built-in" configuration or damage that impedes the phone to connect to the network. They finally suggested to ask the seller to apply the waranty, which is not a viable option since I'm not in the US anymore. This G2 is using the stock ROM (see screen captured).
I've been in close contact with the seller, and he had shown interest in this case but unfortunately hasn't been able to provide much support or help to solve the issue. He reports that he has contacted other buyers of this same phone, also sim unlocked by him, and they all are using their G2s normally. Didn't provide where their locations are tough.
My own conclusions here are that the G2 IMEI is not blocked by the phone company, that there is some kind of fault in the phone that when trying to connect to the network, the network doesn't "like" and rejects connection, althought it worked at the begining, and I'm not able to determine if the fault is software or it's in the hardware of the phone.
So I'm trying to understand what my options are at this moment:
Try to return the phone to the seller, or ask an LG representative in my country to change the unit. Which seems to be very difficult.
Reflash the unit with a stock ROM and reestablish the warranty. But being unsure if this will solve the issue.
Reflash the unit with a new ROM and loose the warranty, and again, being unsure the issue will be solved.
I'm really frustrated and at this moment and have no idea on what to do.
Any ideas or insight will be appreciated.
Thanks.
NOTE: I reinitialized the unit and lost any signal (see screenshots) but received update notifications from Google Play and was able to upload the screenshots into my Dropbox although no signal is shown in the status bar and no WiFi connection is established, only data connection thru APN (I Assume).
Go into status, what's IMEI say?
Sounds like EFS issues. I take it you didn't back it up after setting up on carrier and flashing?
Of so, you have some manual work to do with diag mode and a couple apps via pc.
Hi Steamer;
Under status I see 3 items:
1) Phone Number: shows"Unknown".
2) IMEI: shows the number printed on the box, on a sticker on phone's back.
3) IMEI SV: shows"03".
Where can I learn more about EFS issues? Are there tutorials?
As you say I haven't done any backup thing.
Sent from my LG-D800 using xda app-developers app
Steamer86 said:
Go into status, what's IMEI say?
Sounds like EFS issues. I take it you didn't back it up after setting up on carrier and flashing?
Of so, you have some manual work to do with diag mode and a couple apps via pc.
Click to expand...
Click to collapse
Hi again Steamer:
After reading quite a bit about EFS issues now I understand much better what you meant with your post.
And as you said I didn't back up efs folder, I even didn't flash any ROM yet in the unit. The only thing I did was a 'hard reset' to the unit using the Power + Vol. Down method, after having several 'com.android.phone' errors due to backing up data from Titanium.
The phone went to factory state, I put the sim card and everything went back to normal again, meaning that I was able to make and receive calls. Like 4 hours later the phone went to emergency calls only mode, and from then on I'm not able to take it out of that mode.
So I wonder if the efs folder could corrupt after that factory reset. Is it possible?
Thanks again and any light is greatly appreciated.
It is not in its own partition on this device, but in system. A hard reset shouldn't have caused corruption, but it is not impossible. Your IMEI is intact then, that is good. From what you said about it working partially, your EFS is most likely fine as well. There is a thread here to get files with custom recovery zip file, or you can use adb commands to do it yourself. I don't have guides off hand, but Google is your friend, just specified this phone in searches. Try a new SIM. Sounds more like SIM /carrier issue now as you are out of "activation". That is why emergency is popped and unknown number. The SIM itself may and most likely is bad(or carrier has an issue with your account), in turn it can't communicate with the server causing non activation on network search. Priority to SIM.
franz_cr said:
Hi again Steamer:
After reading quite a bit about EFS issues now I understand much better what you meant with your post.
And as you said I didn't back up efs folder, I even didn't flash any ROM yet in the unit. The only thing I did was a 'hard reset' to the unit using the Power + Vol. Down method, after having several 'com.android.phone' errors due to backing up data from Titanium.
The phone went to factory state, I put the sim card and everything went back to normal again, meaning that I was able to make and receive calls. Like 4 hours later the phone went to emergency calls only mode, and from then on I'm not able to take it out of that mode.
So I wonder if the efs folder could corrupt after that factory reset. Is it possible?
Thanks again and any light is greatly appreciated.
Click to expand...
Click to collapse
Hi i have similar issue with my LG G4 H818P dual sim... after factory reset i often face emergency calls only issue despite full signals... sometimes i able to make and receive calls but most of the time despite my sim registered on network and i get full signals when someone tries to call me he get message as my cell is off.... really annoyed and i flashed latest rom v10e but same issue. Same sim when i use in note 3 then no issue what so ever
Sent from my SM-N9005 using XDA Free mobile app
I had the same issues. Bought in Us using now in India. Go to settings..tethering&networks.. mobile networks... international data roaming and select standard data. Switch off and switch on your phone .
This will happen when you use, internet over gsm. If you disable internet or if your phone loses signal while switching between edge and 3g/4g data, this is tend to happen.
Similar Problem
I have an lg vs980 and I was using it with H2O wireless and later I changed to Simple Mobile. I'm living in Puerto Rico. The phone was working all right and, suddenly, one day it was always displaying 'emergency calls only'.
I did factory reset, then I reflashed stock lollipop and it was like nothing happened, keeps displaying 'emergency calls only'.
Then I found this post http://forum.xda-developers.com/show....php?t=2394689 and applied the patch but didn't seem to resolve the problem.
As a last resort I tried flashing cm 12.1 and before first boot applied the patch from the cited thread but no result, keeps displaying 'emergency calls only'.
Has anyone found a solution to this problem?
Hello all,
Got my G955N in my hands. Followed the threads here to get TWRP installed, used it to install Batman ROM, then used TWRP to flash the AT&T CSC as my provider is AT&T.
In my pull down menu I do have the option for WIFI calling, however whenever I hit it, it fails (seems I can't post pics, so here is the text I get: "Loading, this may take a few moments" then it blinks a few seconds in and repeats. Then it goes to "Please try to set up WIFI calling again later."
I know it's an issue with my phone specifically because my wife's AT&T iPhone7 has WIFI calling working fine (not an ISP issue at home) and I swapped her SIM into my phone and I still got the same error. So it's something with the phone and not likely an account level issue (although maybe? Who knows at this point?)
Also, when I enter the testing menu, I see that "Data Service: Disconnected" which I'm not sure is right? Also, VOLTE Provisioned is not selected, however each time I do select it, it immediately goes back to deselected the moment I navigate away from the testing menu. I can reselect it all day and it still goes back to deselected the moment I move out of the screen.
I've read until my eyes bleed and tried just about everything I could find to try and no joy.
Any ideas?
P.S. got pics if anyone wants me to email them to you for clarity. Guess I'm too new here to be allowed to post pics
To follow up:
Turns out it was an account based issue. Seems AT&T tries to verify the IMEI when attempting to use Wifi calling. So unless registered in the network, it isn't going to work.
And the kicker is, AT&T won't allow Wifi calling or other services with any phone they didn't sell. You can toss in your SIM and use calling, but they won't activate other features if you try to bring your own phone.
So I spent yesterday switching to T-mobile and am now fully functional with all the features of my phone working as they should. AT&T lost me as a customer.
It's pretty simple and the topic explains it almost fully.
I noticed a few months back that I wouldn't get any Data Connection on Project Fi and most of the time I'm on WiFi and took a while to notice.
I simply factory reset the phone and it came right back to working after I completed Setup...not sure if that had anything to do with it now, though.
I had a repeat, for the sake of full disclosure, I had just updated TWRP, updated busybox pro by uninstalling and updating and reinstalling busybox, and flashing SuperSU 2.82 Beta .zip
I'm not sure if it was broke before this or not, but it couldn't have been but for a few days I guess....
Resetting Network Settings, Factory Resetting via TWRP (Wipe) and the regular "Settings" route and even going into the diagnostics and switching the radio on and off while switching from LTE Only to WCDMA, GSM, switching everything on and off...desperately, and putting it back yeilds errors when trying to "Run Ping Test" every time....
Service lists as Connected....Activation after setup shows my phone number and "The Data Connection Should Be Active" like normal. Blowing the SIM slot out, "wiping off" the SIM card and putting it back in - nothing...
I don't know what else to try, I contacted google finally and think I may request a new SIM card but I doubt that is it since it read my phone number and "activated" the phone, and it can receive voice calls (ONLY)
What baseband are you using?
Do you know about the dialer codes? https://forum.xda-developers.com/nexus-6/general/project-fi-fi-dialer-codes-to-force-t3132393
I have also noticed that freezing or removing hangouts causes issues, especially with connecting to Sprint towers.
Hello XDA, I appreciate all you have done for me and my tech endeavors SO I found it necessary to post my results with the community.
Recently I was gifted a Note 8, told it was paid-off, not wanting to wait 3 days for Sprint to MAYBE unlock the bootloader, I set off to work around that by searching through these forums to find that the solution was not as simple as I'm used to.
Here's what I've done to gain access to WiFi again.
Note 8 had Oreo installed (and SIM card removed) I used Odin to flash VZW's Pie (using SamFirm to download, as SamMobile is painfully long). Everything finished installing, but before rebooting the final loading screen sorta stalled, then proceeded to boot. As you may know, it showed the Sprint logo (I panicked and held the down button to put device into safe mode, for control). Next, I decided to go through the Pie setup without allowing the device to access Wi-Fi or Data. Turn on airplane mode ASAP. After I got to the home screen, I stopped ALL automatic updates in settinga, opened developer options, running services, and cancelled everything that would let me, specifically: Chameleon, Sprint Hub, Sprint Voicemail, Sprint ID, RootPA, DRParser Mode, MTP Application, bootagent, Sprint OMADM, com.sec.phone (THIS ONE made the difference in ADB, I was actually able to communicate with my device, see the serial code and everything!, THIS is why I wanted to share with this genius community..and this next one, maybe?), com.samsung.android.smartswitchassistant, tethering automation, and security policy updates. Stop all of those processes, and force stop/disable/remove permissions from all of those (when switching device or WiFi on/off, monitor the running services for those & keep them shut off or they WILL help Sprint "seal the deal"). Make sure to disable/force stop "configuration update". After that I entered PhoneUtil by going to the dialer and pressing ##3424#, then switching the UART from PDA to CDMA MODEM.
Now, I turned on my WiFi (with airplane mode still on), and signed into my router, seen Sprint Hub trying to process a request, went to running services, shut it down & force stopped it, seems to stay off until the phone was restarted, at which point I shut it down.
Again, by doing all of this I was able to get ADB & Kingo Root (desktop) to fully recognize the device, I was able to access Wi-Fi & run "harmful" apps that could help use bruteforce our way past the bootloader lock. SO if there's anything I can do to help, please let me know.
Thanks again!