I'm running my own unofficial lineageos nightly builds on my Moto G4 xt1625 (athene) and something broke between yesterday and today. I'm fine waiting till next week to see if it shakes itself out, but I figured maybe if I mentioned it here somebody important might see it.
With yesterday's build I am able to make calls, get 4g data, etc. With today's build the phone says "no sim" and if I open the sim properties in configuration the phone app crashes.
Looking at https://www.cmxlog.com/14.1/athene I'm not sure what commit would be the problem. I don't have the dual-sim variant, maybe the commit dealing with dual sims broke single sims?
It is connected to the caf merge that happened yesterday. A lot of things are broken including developer settings.
sim issue is probably selinux related.
Thanks for the response. Now I know what to watch for in the commit logs. I'll stick with yesterday's backup for now. Have a great day.
I see some commits this morning that looks like they'll take care of it.
Thanks again.
Related
Hi,
I'm using an Oneplus 2 since 2015. About 6 months ago or so, I started to work with nicesoni_ash's unofficial Resurrection Remix ROM. (I had a version from july, 5.8.3) I loved it since the beginning but since two weeks, my simcard started showing problems. I had network drops every so often, but I could live with that. But now my whole simcard fails and everytime I grab my phone, I have to enter my PIN before I can use my fingerprint scanner. The phone has to search for a network which can take up to 5 minutes and when it finally has a connection, it drops whenever I try to make a call or something. All in all, it's horrible.
I've tried to flash OOS3.5.8., tried to update to a newer ROM (5.8.4), tried to update to the newest ROM and my latest attempt has been to flash a completely different ROM, Cosmic OS2.1. But even with my newest ROM, my simcard fails every. single. time.
The OP2 is a duosim phone, so i have a second sim running to check whether it was my simcard. The second one has less problems, but I almost never use that one. But even then, it fails every so often.
Do any of you know what could be the problem? I really can't figure it out anymore...
Thanks in advance!
Sounds like a Hardware failure to me... did you try both SIM slots? Otherwise search google for how to clean your internal sim pins/ try to add some layers (like 1 or 2) of tape to the sim (obviously not to the side where the connectors are) so there is a bit more pressure to the pins (= better contact between sim/pins)
OK, I need to go over some background before it makes any sense to ask a detailed question.
I've been running crDroid 8.1 on a Verizon Galaxy S5 (CID 15) since year. It had an odd tendency to not recognize the SIM card about half the time you boot it up, and every now and then it will "forget" there's a SIM card -- from what I've read, this is a known problem with S5's running the newer ROM's. I did try getting the SIM card replaced at the Verizon store, but it did not help whatsoever.
The phone has been having slowly-increasing hardware problems that cause to slow down and hang up whenever it is working hard, but I really like the S5, so I've bought two more used CID 15's from different sellers on eBay (both of whom have come across as honest in all the emails and things they've done). One of them came with crDroid pre-installed and the other with LineageOS pre-installed. I immediately reflashed the crDroid one to the latest Resurrection Remix, and with the other I waited a while before replacing the LOS with RR. However, in both cases, I have only been able to get each one to recognize the old S5's SIM card just once -- every other time I've rebooted the phones, and the dozen or so times I've reflashed the ROM's, it just comes up with an empty triangle. One of the new S5's, the one that had LOS installed, the time it worked was probably the first time I booted it up with the SIM card inserted (with LOS still installed), and I actually made a phone call with it to test it -- but since then, nothing. The other S5 took a lot of tries (mostly with RR installed) to get it to work, and oddly enough it finally worked one time immediately after I flashed the modem to the latest revision (just for the sake of trying anything and everything that might help), but in that case, it showed reception only for a few minutes, and reverted to an empty triangle while it was restoring my settings/apps from Google's cloud -- since then, it has not worked.
I also tried taking the phone to the Verizon store and having them transfer my line from the SIM card from my old S5 to a SIM card that was included with one of the S5's I recently got. The new SIM card works just as well as the old one -- which is to say, about half the time on the old S5, and only once on the two new S5's.
Since the two phones have been mysteriously not working, I've been trying all sorts of things to see if anything will help -- including installing LOS, and even tried installing the old crDroid 8.1 on one of the new S5's (because, hey, it is still working on the old one that is having hardware problems). My next experiment will be to back up the old phone and install RR on it to see if the old S5 keeps reception with the new ROM installed with the same procedure as the new S5's.
I'm really struggling with this -- at this point, I think the only thing left to do is to appeal to the entire S5 community and ask for them to list every conceivable reason a SIM card would not work in two S5's but still work half the time in a third S5.
Have a look at the below thread. I would try the preferred network suggestion and then try the TWRP EFS backup/restore if that does not work.
https://forum.xda-developers.com/verizon-galaxy-s5/help/g900v-service-lineage-16-15-1-install-t3917039
I am at wits end. Here's how my situation has unfolded:
- Was running OOS 10.3.2 international, bootloader locked stock on a T-Mobile 6T (been running solid since 9.0.11 MSM hack early last year, updated progressively as the "System Updates" have appeared)
- No customization or tweaks
- Starting late last week, phone has been (seemingly) randomly crashing to black screen, then to spinning dots, like its booting
- I have to Vol up + power to turn off, then reboot
- I captured a logcat of the crash, which may be useful to someone, I just see the system handling a notification, then a system level ANR happens, taking out the core system processes?
I have tried:
- Google/OP backup -> factory reset -> restore account, apps, calls, sms and settings -->> still crashing
- OP backup -> factory reset -> add as fresh account, restore OP bu apps, calls, sms and settings -->> still crashing
- OP backup -> MSM downgrade to 9.0.11 -> unlock bootloader -> install TWRP, Magisk, TWRP install 10.3.2 international -> fresh account, restore SMS messages, etc
After the last attempt, ran all morning without crashing (yay!), proceeded to utter the words to my son ,"hey, fixed my phone, no crashes!", phone crashes 5 minutes later
Then I thought, "well I just signed in to Firefox sync, maybe that's it??", uninstall Firefox. Hour later, crashes during a phone call.
Okay, then thought maybe its something goofy with stock kernel? Install Omega kernel. Crashes 2 hours later on another phone call.
It also seems to crash fairly consistently in my pocket, and I have noticed "Pocket Mode" does not work (overlay doesn't appear when covering proximity sense; sensor works, tested with an app)
Am I experiencing a flaking mobo or some other hardware issue? Please tell me no, I am at 16 months with this phone, so factory warranty is out (and 6 months to go on my payment plan/offer).
Before I try LOS 17.1 (and probably still get crashes :silly, thought I'd try asking for insight here. I have tried googling for similar issues and searching forum threads, but no dice. Thanks!
Well, I have an update here. I turned off "Pocket Mode" last night for giggles, and lo and behold, I have 20 hours up time with no crashes. Proximity sensor works, took several calls today and screen turns off when covering it. Also put phone in pocket regularly to test, no crashing.
Hopefully this helps anyone else with this strange issue. Kind of sucks that I am going to potentially butt call people, but, less pocket time these days while we're all stuck at home (COVID-19 "stay at home", for those reading this post years from now wondering what the heck I'm talking about).
Sad news, random reboots persist. Going to try LOS to rule out OOS (which I can't see it being since others would be complaining too). Hopefully its not hardware, but maybe I jacked my phone up by dropping it one too many times. We'll see.
hondoslack said:
Sad news, random reboots persist. Going to try LOS to rule out OOS (which I can't see it being since others would be complaining too). Hopefully its not hardware, but maybe I jacked my phone up by dropping it one too many times. We'll see.
Click to expand...
Click to collapse
LOS 17.1, random reboots persist . Thinking my phone is toast...
hondoslack said:
LOS 17.1, random reboots persist . Thinking my phone is toast...
Click to expand...
Click to collapse
Try this port rom from op7..
Working great ..easy to install and super stable
https://forum.xda-developers.com/oneplus-6t/development/rom-oneplus7-beta-2-t3971383
have the same exact proble mwith my sons onepus 6t tmobil version, it was ported over to oneplus 6t international version, so we could use it one att.. I done system hardware test and it shows no problem.. I too was thinking of installing lineage os, but I'm lost.. anyone chime in on good tutorial...
sderaps said:
have the same exact proble mwith my sons onepus 6t tmobil version, it was ported over to oneplus 6t international version, so we could use it one att.. I done system hardware test and it shows no problem.. I too was thinking of installing lineage os, but I'm lost.. anyone chime in on good tutorial...
Click to expand...
Click to collapse
Unfortunately I've pretty much confirmed mine was a bad motherboard. I bought a used one off eBay, and installed it yesterday. Phone is running so much better, no more crashes, and proximity sensor is working properly again.
If you want to give LOS 17.1 a shot, here's a good place to start: https://forum.xda-developers.com/oneplus-6t/how-to/guide-installing-lineage-t4075955
I found it mostly a frustrating ROM, as fingerprint and face unlock don't work. Call me lame, but I absolutely love picking my phone up, looking at it, and having access immediately. Then there's all the apps that hook into the fingerprint for quickly unlocking that you can no longer leverage (the unlock part, not the app). Anyway, up to you.
Since I upgraded my op to 10.3.2, my proximity sensor IS not working.
So I've had my OP6T for several months now and I've really enjoyed it and been impressed with it.
For the majority of the time I've used AEX as my custom rom. I always pick a rom with signature spoofing support so I can use microg. Also, my service provider is Verizon.
I finally decided after several months with AEX as my daily driver, I wanted a rom that is more up to date but I'm not really ready to update from 9 to 10. So I decided to flash The Skydragon rom. I flashed it super easy but could not make calls nor send texts. The entire time I used AEX, it made calls and sent SMS/MMS just fine. After I installed Skydragon I called Verizon and spent 2 hours on the phone with various tech specialists and in the end they said from their end everything looked like it should be working. They never got it making calls and sending/receiving texts.
It said out of service in the settings. I ended up switching back to AEX and as soon as I did, it began working properly again. I even tried to make calls and texts on my OP6T when it was 100% stock and it will not work
I wonder if it's because I was on AEX when I originally called Verizon last year and set it up? Am I correct in assuming that, each time I flash a different rom, my phone will appear to Verizon as a brand new phone? I couldn't get it to work on stock nor Skydragon but when I switch back to AEX it works as it's supposed to.
TRexombo said:
AEX it works as it's supposed to.
Click to expand...
Click to collapse
When you tried the other ROMs, were they unmodified?
OP6T works only with Verizon's LTE network, from what I saw online.
It may matter if your phone is international/unbranded, etc., and if the ROMs are for the appropriate version of phone.
pbergonzi said:
When you tried the other ROMs, were they unmodified?
OP6T works only with Verizon's LTE network, from what I saw online.
It may matter if your phone is international/unbranded, etc., and if the ROMs are for the appropriate version of phone.
Click to expand...
Click to collapse
My phone is international/unbranded. I'm not sure if the Roms were unmodified. I know AEX works and when I tried Skydragon I worked on it for close to 2 days trying to make it work. One of the options within the Skydragon settings was that I can choose the exact network to use. I chose LTE. After choosing LTE, in the settings it shows my phone number and my provider as Verizon but it says out of service under service state. The Verizon representatives told me on their end it shows that I am CDMAless and they did not have a solution.
I noticed in the Skydragon thread that some people were successful in getting their OP6T to work with Verizon but at least one other XDA member said he had no service.
Also, as I was in the process of switching back to AEX, I first went back to stock and booted up in stock and tried to make calls /send texts and it would not allow me to until I reflashed AEX.
What a nuisance. Since you're so familiar with flashing ROMs, maybe try some others, but I would first go back to stock again--completely back to stock, even if it means lowering your android version.
But follow the instructions very carefully--you may be in brick territory going back. I'd download the MSMTool just in case.
Good luck with whatever you do, if you don't stay on AEX.
I'm considering trying Lineage given the odd quirks I'm seeing with my rooted Oxygen.
What will I lose or gain by switching from Oxygen to Lineage?
Personally I like youtube vanced and, viper which I get from nolimits 12.0, I also like the native call record. So in my case, I stick to oos.
scorpio76r said:
Personally I like youtube vanced and, viper which I get from nolimits 12.0, I also like the native call record. So in my case, I stick to oos.
Click to expand...
Click to collapse
Thanks for the response. If I could resolve two quirks with OOS, I'd be happy to stay.
1. SMS/MMS database wiped at every restart. (Or is it the messages were never committed to system database?)
2. EcoBee & August use the same API or third party library to add smart home devices. They fail while all other vendors works fine. I had to add devices using a different unrooted phone.
#2 is annoying. #1 is a bigger deal.
kamiller42 said:
Thanks for the response. If I could resolve two quirks with OOS, I'd be happy to stay.
1. SMS/MMS database wiped at every restart. (Or is it the messages were never committed to system database?)
2. EcoBee & August use the same API or third party library to add smart home devices. They fail while all other vendors works fine. I had to add devices using a different unrooted phone.
#2 is annoying. #1 is a bigger deal.
Click to expand...
Click to collapse
I went from OOS to LineageOS 18.1. While I love LineageOS, I am having problems with all my calls going to Real Time Text mode after a hardware answer. I have Verizon as my carrier and this might be the issue. I cannot say for sure. There is no Google on my phone and I get along just fine without them. If I can solve this issue it would otherwise be almost perfect. My 2 cents.
joeliberty said:
I went from OOS to LineageOS 18.1. While I love LineageOS, I am having problems with all my calls going to Real Time Text mode after a hardware answer. I have Verizon as my carrier and this might be the issue. I cannot say for sure. There is no Google on my phone and I get along just fine without them. If I can solve this issue it would otherwise be almost perfect. My 2 cents.
Click to expand...
Click to collapse
I have Verizon too and same thing happens. It's a known issue with most Android 11 ROMs on this phone, except for one or two, who's developers found a workaround.
911 calls don't work either which is a bigger deal.
flyoffacliff said:
I have Verizon too and same thing happens. It's a known issue with most Android 11 ROMs on this phone, except for one or two, who's developers found a workaround.
911 calls don't work either which is a bigger deal.
Click to expand...
Click to collapse
Holy cow....thanks for the tip off. You don't dial 911 unless it's an emergency so I never knew. That would be complete NO NO and if I were LineageOS I would have a BIG warning to Verizon users NOT to use this. I went back to Android 10, HavocOS. Only issue I have is with MMS, but QKSMS is work around for it. I am going to place a test call to 911 now just to be sure. Thanks again.
flyoffacliff said:
I have Verizon too and same thing happens. It's a known issue with most Android 11 ROMs on this phone, except for one or two, who's developers found a workaround.
911 calls don't work either which is a bigger de
flyoffacliff said:
I have Verizon too and same thing happens. It's a known issue with most Android 11 ROMs on this phone, except for one or two, who's developers found a workaround.
911 calls don't work either which is a bigger deal.
Click to expand...
Click to collapse
Which ROM's found a work around???
Click to expand...
Click to collapse
Pixen OS, but it's no longer supported and gave me battery issues. I think Jaguar OS has it fixed too. Not sure about pixel experience.
joeliberty said:
Holy cow....thanks for the tip off. You don't dial 911 unless it's an emergency so I never knew. That would be complete NO NO and if I were LineageOS I would have a BIG warning to Verizon users NOT to use this. I went back to Android 10, HavocOS. Only issue I have is with MMS, but QKSMS is work around for it. I am going to place a test call to 911 now just to be sure. Thanks again.
Click to expand...
Click to collapse
No problem, it could just be me but I think it's maybe related to the rtt issue. You should be fine on Android 10 based ROMs.