Database Users

RIL disapperaring sometimes

Hi guys, I have to clear my mind on a problem:
I have a XT1562 european mono-SIM Moto X Play, and I've upgraded it to Marshmallow (the indian dual-SIM firmware) after unlocking the bootloader and flashed Squid kernel some weeks ago (and then updated to the last build, of course).
Sometimes I'm experiencing an annoying thing: after a reboot RIL dies, and on the best, on the next reboot it reappears; on the worst, after multiple reboots with no luck, I have to do a wipe cache to see it again.
I have root and Xposed (and so, also busybox).
Is anyone experiencing something similar?
There's a way to fix it that maybe I didn't find here on XDA?

Nobody?

have u tried flashing the modem for ur rom?

anks095 said:
have u tried flashing the modem for ur rom?
Click to expand...
Click to collapse
Yes.
But it's strange, because I see it's not modem fault or similar. I see it's something software related because sometimes when I reboot, I also have the stock wallpaper (the green material one).
Now I flashed Marshmallux rom with the exact configuration (apps, modules, etc) and for now all is ok.
But, I still wanna follow this thread because it's too strange and I want to see if someone will expose a pearl.

nplezka said:
Yes.
But it's strange, because I see it's not modem fault or similar. I see it's something software related because sometimes when I reboot, I also have the stock wallpaper (the green material one).
Now I flashed Marshmallux rom with the exact configuration (apps, modules, etc) and for now all is ok.
But, I still wanna follow this thread because it's too strange and I want to see if someone will expose a pearl.
Click to expand...
Click to collapse
Ok..good...but may be u can do a full wipe and then flash factory image and then check it out if the problem sill exist..if not then that should something with software with ur last OS.

anks095 said:
Ok..good...but may be u can do a full wipe and then flash factory image and then check it out if the problem sill exist..if not then that should something with software with ur last OS.
Click to expand...
Click to collapse
Hi guys, I'm back to inform you that I'm on Marshmallux and the problem is still the same. I get randomly "emergency calls only" until reboot (maybe).
I don't understand...

nplezka said:
Hi guys, I'm back to inform you that I'm on Marshmallux and the problem is still the same. I get randomly "emergency calls only" until reboot (maybe).
I don't understand...
Click to expand...
Click to collapse
I don't know if this is the same thing as you but I had "Emergency Calls Only" sporadically as well but it would come back either after a short period of time or after a reboot. I also had random reboots too (didn't matter which ROM I was on at the time).
I lived with this for a bit but then upgraded my SD card (it was old) and I haven't had either problem since.
My guess is that my SIM card might not've been seated properly in the little carrier and/or the SD card I had was mucking things up somehow. I wasn't using it as internal storage either.
Anyways, if you haven't tried this already, might be worth taking out your SIM card and re-seating it (and maybe give the contact part a careful wipe). If you still have the problem and you have an SD card remove it and see what happens. Good luck!

Hi guys! I'm here with news:
after several tests in these days, I discovered the problem was every module that can modify the systemUI.
I tried activating and disabling those modules one by one (I'm talking about GravityBox first, then little modules like Advanced Power Menu or a newer one called NeoPowerMenu), and I saw that without them, I had network at every reboot. The only exception in systemUI is SignalIconsAOSP (I really hate that big "4G" icon next to the signal indicator) and it works at every reboot I did. The other modules (like Xposed GEL Settings, Lolistat, YouTube AdAway) don't annoy the system.
So, I don't know, Moto seems dislike too much modifications on the UI or it's a strange bug. Maybe a bug.

Home button not working at all (tried several fixes)

(Edit 1) Found a fix already! Read post 2!!!
Hello there,
I've been having a OnePlus Two since 4 months already, and had like 2 or 3 home button not working issues.
They used to fixed by themselves after a couple of days of not working, but not this last time.
I tried already the reinstalling system (after formatting system via TWRP), clean it several times, hard reset (hold power button for more than 20 seconds), complete drain battery and fully charge it again, force stop fingerprint service, take out the tempered glass screen protector, and none of those solutions worked.
I here attach (copy the link, can't upload a video directly to this post) a video in which you can see that whenever I power on the screen (still locked), the home button works for several times, but as soon as I unlock it (pattern lock) it stops working. This makes me think that the problem is software, not hardware, but as I said before, already tried reinstalling OOS 3.0, wiping system, cache, data, internal storage, etc.
I compressed the video so it wouldnt be too big, but quality is good enough, just rise the volume so you can listen to the "vibration" that the home button produce.
Any help would be appreciated.
Sincerely,
Daniel Castro

Fix for the issue!
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro

I have the same problem
Tomorrow i'll try your method
I've posted a questione about this issue,
I think the One plus team should find a solution to this problem that afflict many users

Also, don't forget to rotate your phone 720 degrees, counter clock wise! ? hocus pocus....

DCastro555 said:
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
Click to expand...
Click to collapse
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk

these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.

LOL9988 said:
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It will erase everything, make a backup before starting the process.

faustin95 said:
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
Click to expand...
Click to collapse
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.

pitrus- said:
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
Click to expand...
Click to collapse
If it works, its worth a try . And yeah, but we are not in any OnePlus Forum, neither debating about if they are gonna do anything about their own issue, we are trying to fix what an irresponsable company wont.

can we make together an official request to one plus to give us an answer or explanation about this? a lot of users are facing this issue, it's not normal
This is my second opt I bought that this problem has happened
sorry for my english

I had also tried lot of things but home button is not responsive at all.. H2os,exodus,oxygen 2.1 ,3.0 same everywhere
---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------
Error is: when i open fingerprint setting
Enrollment not working try differnt finger or try again ... Nd fingerprint autotest not starting also

i've turned to stock i've updated to oxygen 3.0 bet and the button worked again

i think rooting installing twrp and installing different roms may be the cause of this issue

faustin95 said:
i think rooting installing twrp and installing different roms may be the cause of this issue
Click to expand...
Click to collapse
Unfortunately that is not the case, it's a hardware design bug.
However you can f-k up your finger scanner by damage your persistant-partition if you flash up and down between different ROM/bootloader revisions. But it's easily fixed by flashing the image file for that partition again.

pitrus- said:
Unfortunately that is not the case, it's a hardware design bug.
Click to expand...
Click to collapse
it's a driver issue

faustin95 said:
it's a driver issue
Click to expand...
Click to collapse
50/50 moisture sensitivity and driver issue.

Home button has been working fine for a year, installed 3.0.1 today and suddenly home button only works in OOS 3.0.1. No longer works in CM 13, yet works fine in OOS 3.0.1. Definitely a driver issue.
Tried installing OOS 2.2.1, wiping, then installing Grarak's CM 13 and home button refuses to work. Wiped system, data, cache, installed OOS 3.0.1 and home button works again. Tried wiping again and installed CM 13, home button stopped working. Wiped and reinstalled OOS 3.0.1, home button works again.

Odd thing, my phone will only work with CM13 roms and OOS 2.2.0 or less for fps and home button. Nothing will fix or ever work.

For me, the home button stopped working for a short while on Graraks, then it just jumped back to life again and I haven't had any more home button blackouts after that. If it's a driver issue, it's an extremely intermittent one.
The fingerprint scanner has stopped working from time to time at lockscreen, but this is acceptable for an official hackjobb supported scanner until official sources are released ?

Need Help with this!
Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks! I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet so literally dont know why it happened.
Thanks,
Max

New problem with Fingerprints

So I've been searching all the internet regarding my problem and found none to have my problem.
I was using popwiz rom and after a while my fingerprint sensor stopped working with the error "An error has occureed with the fingerprint sensor. If this message appears repeatedly, restart your device."
Because I needed my G900FQ, I ignored the issue for a while. Found S7 insanity which has a fingerprint bug and forgot about the problem.
Yesterday wanted to check out official MM for my S5, and had to reflash stock lollipop. Then I remembered my fingerprint problem so I tried to set it up. I kept getting that nasty error, tried deleting cache, tried deleting data with Titanium. Reflashed stock 2 times again, nothing worked. Until I was ready to give up and go to bed. Then it suddenly started working. Managed to set it up and activate fingerprint unlock.
Now is the bummer!
I CAN UNLOCK with fingerprint if waiting about 3 seconds after turning screen on.
I CANNOT ADD FINGER through settings, I get the nasty error message.
Tried to enter factory tests and under NormalScan button says Version 0.0.0.0 and in SensorInfo says Ready and stays that way.
I tried to enter factory tests very fast after unlocking with fingerprint and I got, only once and for a brief moment, the right Version and SensorInfo, and Normal Scan showed data and graph.
Now I will try to install official MM firmware with Odin.
Anyone has any ideas to what the cause may be ? And maybe a solution ?
Thanks in advance
L.E. I installed official MM firmware and now fingerprint sensor works when unlocking and adding fingers, but when I try to unlock my phone while it is connected to a power source I get the nasty error message again and prompts me for my backup password. Any advice would be deeply appreciated.

Flash a stock ROM and factory reset?

It seems you did not read the whole thread before suggesting me this...
I did that many times. Lollipop and MM official stock... Its like the sensor is not responding in some situations , but in other situations it does. And this seems to be pretty random..
*Detection* said:
Flash a stock ROM and factory reset?
Click to expand...
Click to collapse

laurent.siku said:
It seems you did not read the whole thread before suggesting me this...
I did that many times. Lollipop and MM official stock... Its like the sensor is not responding in some situations , but in other situations it does. And this seems to be pretty random..
Click to expand...
Click to collapse
It seems you don't even know what you typed, nowhere in your OP did you mention factory resetting and then flashing a stock ROM
Only that you flashed stock ROMs, flashing stock ROMs does nothing to reset anything and will leave behind bugs from the previous ROM if the issue is with an app / data etc
Before getting clever, read what you type

It's obvious that by flashing a stock rom over a custom one will leave bugs. Did full wipe (system, data, cache&dalvik, even phone internal sd) before flashing stock, every time. Thanks anyway..
*Detection* said:
It seems you don't even know what you typed, nowhere in your OP did you mention factory resetting and then flashing a stock ROM
Only that you flashed stock ROMs, flashing stock ROMs does nothing to reset anything and will leave behind bugs from the previous ROM if the issue is with an app / data etc
Before getting clever, read what you type
Click to expand...
Click to collapse

Well maybe next time add that fairly important info to your main post, instead of hoping everyone is psychic, and then throwing a hissy fit when they suggest something you have not stated you already tried.

Some drivers/files missing when flashing through TWRP?

Hello, noob here.
I have a serious doubt after having had a replacement for the screen of my phone.
After receiving it, I noticed it was not an original replacement and there was a curious problem: whenever I powered on the phone the display showed very (seriously, VERY) yellowish. It didn't fix until I turned off the screen and turned it on again.
I decided to flash a ROM trying to solve it, but nothing was fixed. Until I flashed Oreo with MiFlash. Whenever I returned to Nougat with MiFlash the yellow screen appeared again.
These days I followed the procedure of flashing Nougat through MiFlash and then flashing LOS 15.1, the yellow screen remained. But if I flashed first Oreo (MiFlash) and then LOS, that problem did not exist.
So, my question is, is there something we are missing when we flash ROMs through TWRP or some other method (fastboot with @JamFlux tool for example) and not MiFlash?
Sorry for making the post so long, but I felt I had to explain everything in detail.

Your display might have some problems.
Roms shouldn't effect it in general. I would suggest you try voidkernel and play with KCAL settings.

alkesh95 said:
Your display might have some problems.
Roms shouldn't effect it in general. I would suggest you try voidkernel and play with KCAL settings.
Click to expand...
Click to collapse
No, sorry if I did not explain it well. ROMs do not change the display settings. What makes a difference is flashing ROMs through recovery or tools here in XDA (display remains yellow if I come from the Nougat November release) and flashing OTAs through MiFlash (display is not yellow anymore after flashing any Oreo OTA)

pabloespe02 said:
No, sorry if I did not explain it well. ROMs do not change the display settings. What makes a difference is flashing ROMs through recovery or tools here in XDA (display remains yellow if I come from the Nougat November release) and flashing OTAs through MiFlash (display is not yellow anymore after flashing any Oreo OTA)
Click to expand...
Click to collapse
That is a weird issue but its possible.
Sorry i couldn't help you much. As this falls out of my knowledge. Maybe someone else might look into it.

Issue with screen positioning

Just got my OP8 Pro last week and everything was fine until a few days ago. I noticed my screen size is off. It's almost as if it's shrunk. Everything from the top of the screen has dropped about 1mm, so that the camera hole is wrong and the notification bar is below where it should be. I've looked at the dpi, scaling, etc but can't for the life of me find what's changed. Any help would be greatly appreciated.

Did you touch any configurations before that ?
Go to Display > Advanced > Front Camera Display Area and try the option 'hide the front camera' and then go back to 'show the front camera'
see if it fixes the bug.

MoodlePro said:
Did you touch any configurations before that ?
Go to Display > Advanced > Front Camera Display Area and try the option 'hide the front camera' and then go back to 'show the front camera'
see if it fixes the bug.
Click to expand...
Click to collapse
I only set up my phone. I had previously tried switching the front camera display area when I first noticed it was wrong, but it didn't help. Regardless of what settings I use there's always a 1mm or so black area above the status bar.

BRANDENDEUCE said:
I only set up my phone. I had previously tried switching the front camera display area when I first noticed it was wrong, but it didn't help. Regardless of what settings I use there's always a 1mm or so black area above the status bar.
Click to expand...
Click to collapse
It looks like a launcher related problem.
Are you using a custom one of just stock? You could try clearing cache for the launcher in settings - apps and then reboot your phone.
Tell us how it goes.
You might also check your DPI settings (
https://www.reddit.com/r/OnePlus8Pro/comments/jh1x9e
)

Also, if you can take a picture or a screenshot (if it shows) i would highly appreciat it.

MoodlePro said:
Also, if you can take a picture or a screenshot (if it shows) i would highly appreciat it.
Click to expand...
Click to collapse
Using nova or oneplus launcher, it's both the same. I'll see if I can find an extra camera because screenshot doesn't show it

MoodlePro said:
Also, if you can take a picture or a screenshot (if it shows) i would highly appreciat it.
Click to expand...
Click to collapse
Hope this helps.

BRANDENDEUCE said:
Hope this helps.
Click to expand...
Click to collapse
If you're able to do so, clear the cache for both launchers
Update me as always.

MoodlePro said:
If you're able to do so, clear the cache for both launchers
Update me as always.
Click to expand...
Click to collapse
Same as before. I had tried wiping the cache in twrp and it didn't help. I'm trying to get the full zip for the current rom to dirty flash. I'm assuming that will fix the problem, but I can't find anyone who's got it yet.

BRANDENDEUCE said:
Same as before. I had tried wiping the cache in twrp and it didn't help. I'm trying to get the full zip for the current rom to dirty flash. I'm assuming that will fix the problem, but I can't find anyone who's got it yet.
Click to expand...
Click to collapse
it looks like you are not using stock oos or at least some modifications or UI Apps. Some of these apps/mods should be your problem. You are the first on on here reporting this issue so its very likely some of the apps you are using.
I would reset my phone and test every app alone if the issue comes back. Or maybe just deactivate all of them, restart and look what happens.
Stock roms:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Just in case:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

xtcislove said:
it looks like you are not using stock oos or at least some modifications or UI Apps. Some of these apps/mods should be your problem. You are the first on on here reporting this issue so its very likely some of the apps you are using.
I would reset my phone and test every app alone if the issue comes back. Or maybe just deactivate all of them, restart and look what happens.
Stock roms:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Just in case:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
I'm using Oxygen OS 11.0.10.10.IN11AA that I updated right after initial setup. Bootloader unlocked and rooted, swift installer for theming. I've in uninstalled the swift mods and it stays the same. I have some magisk modules, but they were active initially before the issue arose. I did look at the thread for the OOS version, but the newest available is for the last version. As soon as I get my hands on the full zip I'll start from scratch and find out what is causing the issue.

BRANDENDEUCE said:
Just got my OP8 Pro last week and everything was fine until a few days ago. I noticed my screen size is off. It's almost as if it's shrunk. Everything from the top of the screen has dropped about 1mm, so that the camera hole is wrong and the notification bar is below where it should be. I've looked at the dpi, scaling, etc but can't for the life of me find what's changed. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I think after all you've tried I would just MSM back then start over.
Hopefully it's just a very weird glitch although my guess is pointing towards hardware and an alignment issue with the screen..was the device new? Or 2nd hand?
If it's the latter then I'd be having a word, obviously after the MSM wipe, you'll be required to unlock the bootloader again and re-root
It's definitely odd.
If the wipe fails then there may be a calibration tool that enables you to bump the alignment of the screen up a bit, I'm sure dpi changes should have an effect (may need a reboot between changes)
Also change from QHD to FHD, I run in FHD and everything has always scaled really well.

So, the latest update was finally released and I dirty flashed it after disabling all my magisk modules and swift theming, but the issue was still there. I factory reset from twrp and it fixed the problem. All swift theming and modules (viper, Dolby digital, acca, oos call recording) are reinstalled with zero problems. The only thing that I can think of that caused it is an app I used to show battery levels around the camera hole, because everything else is the same. It had to have changed something that even after uninstalling and dirty flashing it didn't revert.

BRANDENDEUCE said:
So, the latest update was finally released and I dirty flashed it after disabling all my magisk modules and swift theming, but the issue was still there. I factory reset from twrp and it fixed the problem. All swift theming and modules (viper, Dolby digital, acca, oos call recording) are reinstalled with zero problems. The only thing that I can think of that caused it is an app I used to show battery levels around the camera hole, because everything else is the same. It had to have changed something that even after uninstalling and dirty flashing it didn't revert.
Click to expand...
Click to collapse
Nice one..