Develop Bugs

Dialer/phone FC every rom

So i have started encountering a problem in which about 3 minutes into a phone call my phone freezes and then ultimately turns off and only way to turn it back on is removing the battery and then power button.
I have had this problem on every rom starting on CM. After it happened on this rom i flashed juggs, beast, and da bomb (or whatever) and everyone it still happened. I wiped data, cache and delvik before every flash but this did not help.
I eventually just odin back to stock with the stock tar that is posted somewhere in this forum. This still has the problem. I found that it generally happens if i move from my ear and the screen turns on and then it wont turn back off and no menus are available (ak i cant get into dialer if i call bank or 800 number to input a number) and then it just completely freezes and turns off.
Any help with this would be great. I mean making phone calls is probably the most important part of a "phone" working. So i really need this to be fixed asap. thanks

jr8801 said:
So i have started encountering a problem in which about 3 minutes into a phone call my phone freezes and then ultimately turns off and only way to turn it back on is removing the battery and then power button.
I have had this problem on every rom starting on CM. After it happened on this rom i flashed juggs, beast, and da bomb (or whatever) and everyone it still happened. I wiped data, cache and delvik before every flash but this did not help.
I eventually just odin back to stock with the stock tar that is posted somewhere in this forum. This still has the problem. I found that it generally happens if i move from my ear and the screen turns on and then it wont turn back off and no menus are available (ak i cant get into dialer if i call bank or 800 number to input a number) and then it just completely freezes and turns off.
Any help with this would be great. I mean making phone calls is probably the most important part of a "phone" working. So i really need this to be fixed asap. thanks
Click to expand...
Click to collapse
Looks like it might be a kernal problem. Have you flashed back to the stock kernal? If not, I'd look there first

yeah i flashed stock kernal as well...problem still persist

uninstall Google+

no google + never have had it.

Have you tried flashing CM7 Alpha #2? I had that same problem with Alpha #1 release then flashed #2 fixed permissions. Then at first start up i rebooted with GPS on and voila! No more phone FC.

I started with Alpha #1 where the problem started flashed over #2 fixed permissions and same problem. thats when i started flashing the other roms to try to solve the problems but this hasnt helped. So i odin back to stock. flashed stock kernal and stock recovery. and i still have the problem.
What sucks is im just graduating college and im starting to receive calls from future employers and i cannot talk for more then 2 minutes before my phone decides to shut off.
So any other advice???

bump it up. Any help please...::
what it is doing now update: I click on a contact or type a number and press call and the screen turns black except the status bar. soft keys dont work, hard keys dont work. phone is a fail. people can still hear me and i can still hear them but the phone is unusable and i have to pull battery to get out of the black screen.
This was doing it on every rom and i have now put beastmod v2 4.0 still no luck :[

I just received my White GS2, finished the OTA update.
And yes, the dialer FC on me every single time once I push the hangup button.

Upgraded to Oreo yesterday, rebooting randomly...

As the title says, phone has randomly rebooted
... twice in the last few minutes, both times I had picture in picture going while sending a text...has anyone else experienced this? Also, the boot time is amazingly fast at least!
Chris

cswee1932 said:
As the title says, phone has randomly rebooted
... twice in the last few minutes, both times I had picture in picture going while sending a text...has anyone else experienced this? Also, the boot time is amazingly fast at least!
Chris
Click to expand...
Click to collapse
Did you do a wipe when you flashed or just update? If you just did an update, I would try to reinstall and let it wipe the device.

Yup. I'm experiencing this as well. Happened to me twice yesterday. Maybe try a factory reset?
Sent from my Pixel XL using Tapatalk

Having the same issue did a complete factory install with the stock image.
Then rooted not sure if that is causing my issues but, is anyone else stock not rooted having random reboots?

I've had 3 reboots since jumping on Oreo. Did my update the clean way through a factory reset and flashing a factory image. Stock, unrooted.

humdrum2009 said:
Having the same issue did a complete factory install with the stock image.
Then rooted not sure if that is causing my issues but, is anyone else stock not rooted having random reboots?
Click to expand...
Click to collapse
Stock, updated via ota... Having 5 to 6 reboots per hour. Google is sending a replacement phone.

Maybe you have to do a factory reset.

Reason why i havent upgraded. Still on a rock solid nougat until google fix all this problems. Maybe 8.1 or so. Seem like reboot is a common problem with the pixel,. All thread about orea theres someone talking about his reboot problem in many different sites.

jerryhou85 said:
Maybe you have to do a factory reset.
Click to expand...
Click to collapse
Did that too. It is even rebooting in safe mode after a factory reset Hence the return...

sandibhatt said:
Did that too. It is even rebooting in safe mode after a factory reset Hence the return...
Click to expand...
Click to collapse
That sounds much like a hardware failure... :crying:

I had random reboots too coming from DP4 to FInal. No more random reboots since I flashed the factory images

Is 8.0 the version that is the start of the new OS updating system? I wonder if the partitioning is getting all screwed up? I think I'll stay on 7.1.2 for a bit longer till this gets ironed out.
Sent from my Pixel XL using Tapatalk

Stock, bootloader unlocked, Oreo by OTA, and 1 random reboot and 1 random power off
Sent from my sailfish using XDA Labs

Not gonna upgrade to Oreo.
Is there such a way?

nabbed said:
Not gonna upgrade to Oreo.
Is there such a way?
Click to expand...
Click to collapse
Just don't download the OTA till they send out a patch. That's what I'm doing.
Sent from my Pixel XL using Tapatalk

when i first updated to oreo and rooted it, i ran into the rebooting issues some of you are experiencing. i think the root of my issue was busybox. i did a clean install of oreo again the other day and rooted, but didnt put busybox on the phone. phone ran fine for a day, so i tried giving busybox another go. the reboot issues came back. hope this helps

Mine only reboots randomly if I have YouTube picture in picture enabled once I disabled it I haven't had any reboots maybe try to disable that

Just did the update a couple hours ago and so far so good. Picture in picture works too. Stock, GPE on VZW, no root or anything.
Sent from my Pixel XL using Tapatalk

Guys, anyone still getting random on persistent reboots on Oreo with Pixel (XL)? I'm doing my second factory reset atm and monitoring these two threads on buganiser - 1, 2. Basically people started getting reboots after upgrading to Oreo and one notable common thing is: 'Sense Key : Hardware Error [current]' which Google reps assigned to the threads read as hardware issue (probably with Toshiba's memory chips being prone to overflow/overload (?)). They haven't answered my question why is it only happening on Oreo though. I REALLY don't want to go through the warranty process again only to get a device with the same problem as I still believe it can be fixed in 8.1. Is there anyone who had similar issues that got fixed with the 8.1 Beta? Cheers!

I'm experiencing the random reboots too.
Oct. 8.0, Magisk, Root
I almost missed an alarm due to this, so I think I may go back to Nougat. Not only does it reboot, but it gets stuck in the boot screen. If I hold Power and reboot, it comes up though.

Nexus 5x randomly restarting

Hello! I am going to describe my issue with 2 years old nexus 5x which is restarting randomly.
It all started a couple of days ago when my phone started to ask me to enter PIN code. That happened randomly. After entering the code my phone worked completely ok.
But yesterday it started restarting on its own. The restart happened once, than I suddenly got a message before loading screen saying: "Your device is corrupt. It can not be trusted and may not work properly".
Today my Nexus restarted around 10 times. These restarts do not depand on phone usage, since it is restarting randomly (when charging, when not charging, when using it, when screen is off).
I decided to clear cache partition factory reset it and update apps. Unfortunately that did not help, since my phone is restarting even more frequently. Normally it freezes for 5 seconds and than restarts. Sometimes I still get the message: "Your device is corrupt...", but not always.
My Nexus has not been modified (it is not rooted and it is running android 8.1 with november security patch). Also apps have been installed only from play store and not from unknown sources.
I would really need your help. Has anybody experienced any similar issues or does anybody know what could cause the restarting?
Thank you in advance.

@tic_tac7: probably it's a conveniant variant of BLOD. So save everything important on another storage immediately.
This message comes from bootloader. Because the reboots happen also during standby, it's imo useless to flash a kernel which lets the big core sleep, but that's a misty guess. Nevertheless you could try the latest ABC-Oreo (needs TWRP by ADB) without anything more for testing. If reboots are going on > bin.

rp158 said:
@tic_tac7: probably it's a conveniant variant of BLOD. So save everything important on another storage immediately.
This message comes from bootloader. Because the reboots happen also during standby, it's imo useless to flash a kernel which lets the big core sleep, but that's a misty guess. Nevertheless you could try the latest ABC-Oreo (needs TWRP by ADB) without anything more for testing. If reboots are going on > bin.
Click to expand...
Click to collapse
Thank you for your response. Is installing a custom rom the only possible soultion?

No. It's no solution. It's a vague trial.

tic_tac7 said:
Thank you for your response. Is installing a custom rom the only possible soultion?
Click to expand...
Click to collapse
If you are original owner of phone for up to 30 months, go here and let LG fix (or attempt to) the phone. Mine required two repairs. If you are not in the US, check with LG support in your country.

Touch screen on 5T randomly stops responding

I've been having this issue where the touchscreen on my OP 5T will be working just fine but the next second just turn unresponsive to any touch, and no amount of rebooting fixes it.
So far, I've tried using the unbricking tool and restored it to OOS 5.1.3, wiped everything off the phone and tried the latest OOS 9.0.1, and even some custom ROMs like Pixel Experience, both the official Oreo version and some unofficial Pie versions.
I even tried installing custom kernels like the blu-spark kernel and the π kernel.
But here's the thing, all of these work right after making the change but the touchscreen stops working a day later. I'm still on the fence if this is a hardware or a software issue, because (do please correct me if I am wrong) a hardware issue would be if it was totally unresponsive and not work fine after installing a new ROM/kernel, which is not the case here, leading me to assume it has to be something in the software related?

gasburger said:
I've been having this issue where the touchscreen on my OP 5T will be working just fine but the next second just turn unresponsive to any touch, and no amount of rebooting fixes it.
So far, I've tried using the unbricking tool and restored it to OOS 5.1.3, wiped everything off the phone and tried the latest OOS 9.0.1, and even some custom ROMs like Pixel Experience, both the official Oreo version and some unofficial Pie versions.
I even tried installing custom kernels like the blu-spark kernel and the π kernel.
But here's the thing, all of these work right after making the change but the touchscreen stops working a day later. I'm still on the fence if this is a hardware or a software issue, because (do please correct me if I am wrong) a hardware issue would be if it was totally unresponsive and not work fine after installing a new ROM/kernel, which is not the case here, leading me to assume it has to be something in the software related?
Click to expand...
Click to collapse
Same problem. Did you solve this problem?

Has anyone found a permanent solution to this? Or at least a reason? My op 5t also stops responding randomly to the touch. This is really bad.

I also have this problem as well. It seems that many users have this issue. OnePlus should take a close look at it

I have been having this issue for more than 6 months. The problem came after one update during android Oreo if not mistaken (Which update i can't remember)
For my phone, the screen will be unresponsive during the below occasions:
1. After rebooting the phone, touchscreen is unresponsive for up to a minute
2. When browsing pictures in gallery
3. When taking picture using portrait mode
4. When google play is updating apps
5. When google photo is backing up photos.
I am also doubting if is a hardware or software issue, because it only happened in some occasion previously for my case. Tried wipe and install stable/open beta a few times, same thing.
After the latest open beta update, it got even worst, other than the above occasions, the screen start to stop working randomly (be it watching a youtube video or using chrome), its getting annoying as i need to restart my phone a few times a day.
I saw alot of people having this issue, but has yet to raise concern of OnePlus.

I've recently had the same problem, I was still running Lineage 15.1 and had not updated my firmware in months because the official builds switched to 16, then suddenly 2 weeks ago the touch screen stops responding while I was actually using it. Reboots didn't help, clearing cache and flashing lineage didn't help. In the end I somehow got it to work again by flashing the last open beta - but even then it didn't work right after flashing it, I had to leave it over night then it mysteriously started responding again in the morning.
I've just had it happen again and I have tried removing the screen protector and completely discharging the battery as some people on the oneplus forum have reported this helps, but it did not work for me. I really can't be bothered going through the whole process of re-flashing open beta then flashing back to lineage and installing all my apps an restoring my data again, but the only other option at this point is to try take it apart to check the screen is still connected to the motherboard properly....

solution
I also faced this problem, then i tried to degrade it to android oreo, and somehow i never faced touch issue, i think this is a bug in android pie,

karyy said:
I also faced this problem, then i tried to degrade it to android oreo, and somehow i never faced touch issue, i think this is a bug in android pie,
Click to expand...
Click to collapse
I'm not sure about that, the first time I had the issue appear I was still running oreo, as I mentioned, I hadn't updated anything in months due to the lineage nightlies switching to Pie.... That said, certainly seems like most people who have reported it mentioned upgrading to Pie

Facing same issue..
I have a similar issue too..
It started several months ago, when the screen used to randomly stop working, a quick hard reboot usually solved the issue.
But about a month ago, the screen stopped responding altogether and any amount of reboot did not work. So too the device to Oneplus service, there they flashed it to 9.0.7, and the screen started working again, and continued working for a few more hours, until it stopped responding again.
Tried flashing several times using the unbricking tool, but all efforts in vain.
Finally after a month or so, I bought a new phone, and today I just wanted to see if anything has changed on OP5T, and to my surprise, the touch screen started working again.
So this time I enabled USB Debugging, permanently enabled OTG, so that even if the screen stops working, I can use an external keyboard/mouse.
But OP5T is no longer my primary device, and hence I have moved on to a different manufacturer, as I saw absolutely no point in buying another Oneplus and god knows what will happen a year down the line...

Has anyone found a solution to this? I am facing the same problem with my oneplus 5T.

chandle-stick said:
Has anyone found a solution to this? I am facing the same problem with my oneplus 5T.
Click to expand...
Click to collapse
I had the problem. Had to send it back to OnePlus. They replaced the cpu under warrenty. Call 0neplus.

i have this problem on LineageOS 16, in stock is good

k-ninja said:
I'm not sure about that, the first time I had the issue appear I was still running oreo, as I mentioned, I hadn't updated anything in months due to the lineage nightlies switching to Pie.... That said, certainly seems like most people who have reported it mentioned upgrading to Pie
Click to expand...
Click to collapse
I was just searching this issue online. I'm currently facing it as well.
Rebooting the phone makes it go away. I face this issue while charging the phone via official dash charger.
I'm running stock Oxygen OS 5.1.7 running Oreo 8.1.0. I faced this issue 6-8 months ago as well. I cleared 7gb free space in my phone then it started working fine then. My device is 64GB variant. I never updated to Android Pie.
This is a major problem in OnePlus 5 and 5t. I've seen many posts on both XDA and official oneplus forums but found no guaranteed solution so far. I was thinking of flashing custom kernel but then saw here that people are still facing this issue in custom ROMs.

I thought I had solved the problem by installing the RenderZenith kernel, which someone on the oneplus forums recommended in the thread there dealing with this issue... but it has resurfaced after a couple of months without issue. Rebooting does not fix the issue for me, I have to flash a stock firmware, and sometimes reboot a few times, before the touchscreen starts working again. I tried installing CarbonROM instead of Lineage to see if that made a difference but it lasted about a day before the problem reoccurred. I am now going to try a Q-based ROM (probably Carbon) to see if that makes any difference, but I am not hopeful. I have even had the issue occur once while I was still running stock 9.0.9 and had not yet got to reflashing a custom ROM, had to do a full wipe and reinstall the stock ROM again to get it working.
I'm about ready to throw this phone in the bin and buy something new - only problem is I don't know what. Certainly not going to waste money on another oneplus after this debacle but there aren't many other options that are good for custom ROMs. Too bad OOS is such insecure trash and Oneplus as a company cant be trusted, otherwise I might at least see how I go running stock for a while.

k-ninja said:
I thought I had solved the problem by installing the RenderZenith kernel, which someone on the oneplus forums recommended in the thread there dealing with this issue... but it has resurfaced after a couple of months without issue. Rebooting does not fix the issue for me, I have to flash a stock firmware, and sometimes reboot a few times, before the touchscreen starts working again. I tried installing CarbonROM instead of Lineage to see if that made a difference but it lasted about a day before the problem reoccurred. I am now going to try a Q-based ROM (probably Carbon) to see if that makes any difference, but I am not hopeful. I have even had the issue occur once while I was still running stock 9.0.9 and had not yet got to reflashing a custom ROM, had to do a full wipe and reinstall the stock ROM again to get it working.
I'm about ready to throw this phone in the bin and buy something new - only problem is I don't know what. Certainly not going to waste money on another oneplus after this debacle but there aren't many other options that are good for custom ROMs. Too bad OOS is such insecure trash and Oneplus as a company cant be trusted, otherwise I might at least see how I go running stock for a while.
Click to expand...
Click to collapse
Have you tried Affinity kernel? Saw a post here. But it is for OnePlus 5
https://forum.xda-developers.com/showpost.php?p=79256461&postcount=95

archz2 said:
Have you tried Affinity kernel? Saw a post here. But it is for OnePlus 5
https://forum.xda-developers.com/showpost.php?p=79256461&postcount=95
Click to expand...
Click to collapse
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....

k-ninja said:
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
Click to expand...
Click to collapse
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
---------- Post added at 08:23 PM ---------- Previous post was at 07:57 PM ----------
k-ninja said:
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
Click to expand...
Click to collapse
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk

archz2 said:
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
---------- Post added at 08:23 PM ---------- Previous post was at 07:57 PM ----------
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I'm not running OOS now, but I have had the issue occur while I was. I am just re-flashing OOS to get the touchscreen to work again, but actually I can't even get the setup wizard to work once the phone boots (hangs on the "just a sec" screen), so I am usually flashing another custom ROM once the screen works again. I managed to get to about 6 hours of normal usage last night before the screen stopped responding again - after fighting with the phone all day and most times not getting much past installing magisk modules.
I am starting to think the problem is related to either Magisk, or the riru kernel hooking modules necessary for Xprivacylua (which is mandatory to install IMO) - I had been using the YAHFA module mostly but yesterday I tried Sandhook to see if it made any difference - that was when I managed to get to 6 hours instead of 30 minutes, but it was also when I went back to Magisk 19.3 instead of installing 20.2. Now that I think back, I am wondering if it was upgrading Magisk from 19.x to 20.x that made the issue resurface after a couple of months without it.... Can't remember for certain, but it seems like the most plausible explanation. I tried flashing Magisk uninstaller this time when the screen stopped, but it didn't help - only reflashing back to stock works (sometimes it even takes a few goes). Whatever the problem is, it seems like it is tripping some hardware related switch which only gets reset when installing stock FW.
the other thought I had was that perhaps the hooking framework is getting in the way - like it intercepts the screen touches before they are processed, but it bugs out for some reason and they never get passed on to the OS. I don't know enough about how it works honestly, or any idea how to go about debugging such a weird problem, so no way to look into it.
Anyway, to answer you other question - I never had the problem with OOS 5.1.7, I have never run stock OOS on my phone, but the first time I had the problem was with Lineage 15.1 Oreo 8.1.0. I can't remember if at that time I was running stock xposed or edxposed.
I'm close to my wits end here. IF the problem turns out to be magisk related, it's pretty much new phone time - I doubt even if I logged a bug report it will get looked at any time soon much less resovled, and I simply refuse to run an android phone without xprivacylua.

k-ninja said:
Anyway, to answer you other question - I never had the problem with OOS 5.1.7, I have never run stock OOS on my phone, but the first time I had the problem was with Lineage 15.1 Oreo 8.1.0. I can't remember if at that time I was running stock xposed or edxposed.
Click to expand...
Click to collapse
Edexposed is for Pie ROMS as there's been no development for Pie from official developer for xposed. Chances are you were running xposed only on Oreo 8.1.0.
Today I flashed Franco Kernel on my phone, been running smooth so far. I used to get non-responsiveness while dash charging specifically. Let's see how it goes. Will keep you updated.

Bugger it... I managed to get to 4 days or so after flashing back to LOS 16.1 / Magisk 19.3 / Edxposed YAFHA / Franco kernel, but it has just crapped out on me again.
This time I has tried a slowly-slowly approach, at first running just the stock OS and apps for a few hours, then gradually started installing magisk, riru, edexposed, then finally xprivacylua - Didn't have any problems up to there. Then I installed pico gapps, and used the Play store to do a fresh install of Mobius Final Fantasy instead of restoring from Titanium backup (this game is actually the only real reason I need gapps at all :-/). Mobius is a PITA because its like a 5Gb download, so it takes a long time to reinstall rather than restore from TB. Anyway it seemed like it was working ok for a few days after the fresh install but I just picked up the phone as couldn't unlock it. I have noticed that often the problem does occur while I am playing the game and I have wondered if there is something about it which makes it more likely to trigger, but it can't be the only thing as it happens even during the setup wizard sometimes.... bloody infuriating.
Anyway... not sure what to do now. Really CBF going through the back-to-stock dance again. Meh.

Zuk Z2 Plus Touch Freeze

Hello Guys! I recently started to notice a very odd issue on my zuk z2 plus. I currently am running AospExtended ROM V6.4 (Android 9, Pie) with magisk installed. But this problem started before magisk was installed.
What happens is when i unlock my phone, after a mere 2 seconds, the touch absolutely freezes. I mean the screen is on, hardware buttons (U touch, Power & Volume Rocker) work, and i can even receive notifications, which means the phone is working, but the screen is not? If I turn off the device (Not Power Off, Just a tap of the power button) and unlock again, the touch resumes, but only for 2 seconds. This can be done infinitely. Reboots, shutdowns, forced power off, recovery etc all seem to go in vain, though some lucky reboots can save the day. Also, if I unlock the phone and then open google in a flash and start typing anything, it sometimes works and the touch resumes. This issue also persists in Safe Mode. ​
My issue is also very similar to the one seen here :
Video (Not By Me) : https://www.youtube.com/watch?v=JdMbbML9ECg
Forum : https://forum.xda-developers.com/lenovo-zuk-z2/help/touch-issue-t3708645
Keep in mind that I faced the same issue on my previous rom, Resurrection Remix v6.0 Oreo. I can always provide additional information if anyone wants. If anyone has faced the same issue, or has the fix to this, please do tell me as it is very difficult to manage.

Did you change something in root partition. I had the same issue in msm xtended when i deleted some app from system but after dirty flash it was solved.

bisht ankur said:
Did you change something in root partition. I had the same issue in msm xtended when i deleted some app from system but after dirty flash it was solved.
Click to expand...
Click to collapse
No, I did not do anything, also, the issue persists in safe mode too, so that means no 3rd party app is causing it.

Jodh5634 said:
No, I did not do anything, also, the issue persists in safe mode too, so that means no 3rd party app is causing it.
Click to expand...
Click to collapse
It could be a rom issue, try posting it on rom thread. Sorry i may be of no help.

have you tried to QFIL to latest zui and observe if the issue persist in zui as well??

Same problem here. Never rooted my z2, don't even have twrp installed. Always have been on 2.5.104 ST rom.
Really frustrating issue caused by Lenovo. Will ever avoid any Lenovo devices in future.

****
Same problems happening with mine too
I think that my hardware problem but now i guess its every one problem slowly

As a matter of update:
I got my z2 repaired locally. Service diagnosed short-circuit failure of the sensor. Nasty /really wanted to use another word here/ production quality by lenovo. Cost me around $60.