Major OS/touch screen freezing - Unroot, return device, etc.? - OnePlus 7 Pro Questions & Answers

Got a new OP7 Pro. Nice hardware for sure. I unlocked boot loader, installed TWRP recovery, Magisk, but using standard factory ROM/kernel (OOS 9.5.8). I am experiencing severe screen freeze issues. It is like all touch inputs are ignored or screen is frozen for up to 10 seconds at a time. The phone is pretty well unusable as this gets in to a loop of unfreezing perhaps for a few seconds or a minute but then right back to frozen. Crazy...
Some times I can go an hour or so with out it happening but once it sets in it seems to recur frequently . Rebooting helps as does wiping dalvik/cache, but it always seems to come back. Does not appear to happen when booting to safe mode, which leads me to believe it is an incompatible app but the app would have to be doing some crazy stuff to screw up the entire phone/screen/touch input this much. Just can't find the trigger or a fix.
I've got many options. All my (relatively Android noob) buddies (some are very good programmers though) insist I should unroot and remove TWRP and get back completely to stock. I could try those sequentially. I can also return the phone and replace it since it is brand new. Oneplus suggested this rather than providing any help or real tech support.
I've googled around a lot and have found some (appears to be infrequent) folks who ocassionally loose touch access in a corner of the OP7 Pro screen. Neither this nor the "ghost touch" are the same as my issue.
Hoping to get some good advice here from some Android gurus. Thanks in advance.

Bump, no one??

swamp2 said:
Bump, no one??
Click to expand...
Click to collapse
Update the firmware.

dynospectrum said:
Update the firmware.
Click to expand...
Click to collapse
Thanks, but just random tech support advice? Or do you have a reason to believe there is something particularly relevant in the 9.5.10 release?

9.5.7 or 9.5.8 had random screen touch issues Anna .10 hot fixes more bugs that they introduced to .9
If I were you, I'd update and get on the current firmware. I'd also backup all your data on the phone and do a factory reset after the updated then if it still is having issues return it for hardware defect. It makes no difference to do this as you have to perform the data wipe before returning it anyway.

Eric214 said:
9.5.7 or 9.5.8 had random screen touch issues Anna .10 hot fixes more bugs that they introduced to .9
If I were you, I'd update and get on the current firmware. I'd also backup all your data on the phone and do a factory reset after the updated then if it still is having issues return it for hardware defect. It makes no difference to do this as you have to perform the data wipe before returning it anyway.
Click to expand...
Click to collapse
Thanks, things are looking free of this issue so far on .10!

Issue is back, greatly improved but back. This phone is driving me nuts. Must be incompatible with some app...

Removed root, removed twrp, locked boot loader and clean flashed 9.5.10. Screen freezing completely gone for around 24 hours. Also have only installed essential apps. Sure would like both TWRP and Magisk back, but undecided. I seem to be the only person with this particular problem... Additional advice appreciated.

I'm getting the same problem even on .10 version.
I had to unroot and lock the bootloader again.
I thought I'm the only one who is facing this issue.

Any more updates on this? Was it an app causing it?

I have OnePlus 7 Pro for a few weeks already, but I started use 7 Pro as my primary device from last weekend and since that time I have experienced the identical problem.
Renovate ROM, stock kernel, xposed

shank19 said:
I'm getting the same problem even on .10 version.
I had to unroot and lock the bootloader again.
I thought I'm the only one who is facing this issue.
Click to expand...
Click to collapse
Wow, I'm not alone! Can't decide if I want to do a warranty return and try an entirely new phone. We just can't be the only folks with TWRP and Magisk on this device. It seems like a software problem but odd that more are not experiencing. I'm hesitant to even try Magisk for fear of a long difficult full wipe without a good TWRP backup.
Edit: I should have done better testing but pretty sure unroot by full Magisk removal did not fix the issue.

Honestly if it's not a hardware defect the one thing I think that it could be is accidental touches. Are you using a case on your phone? Does it get any better if you lay your phone flat and only touch the screen with your finger?
When I first got my s9+ which was my first curved screen phone I had this same issue and thought it was hardware related, but when put a case on it the issue completely stopped and I realized I had been touching the curved screen with my palm while holding the phone.
I don't really see how unlocking the bootloader, magisk, or twrp could be responsible as I haven't had any issues with any of them, but you could try custom kernels or roms if you want to try everything before you return the phone, but I think that would be really grasping as straws.
It could be a Magisk module as I've had issues where installing and deleting the modules cause me to have random reboots even with all the modules uninstalled, id try wiping data, and flashing fresh oos 9.5.10 to both slots.

I just uploaded a video of that issue, sorry for the quality (Xiaomi Mi A2 Lite).

Weird issue. Glad I'm not seeing it on my International 9.5.19.

This is definitely not an issue you're going to resolve by just installing a few apps and waiting to see if they affect the performance. I am interested to see what the logcats (actually, logs in general) say at the moment the phone freezes. If anyone can provide these it would be a great insight for sure.

Unroot, lock bootloader, wipe, factory 9.5.10, problem completely gone. Good and bad, prefer root...

I've only encountered this issue while using Facebook messenger.

I tried to deactivate xposed and magisk modules but the problem persisted - it seems it just started to appear less frequently but not fixed.
I am on the Havoc ROM for more than two days and touch screen issue is gone.

Chrono Leggionaire said:
I tried to deactivate xposed and magisk modules but the problem persisted - it seems it just started to appear less frequently but not fixed.
I am on the Havoc ROM for more than two days and touch screen issue is gone.
Click to expand...
Click to collapse
Strange, one common denominator is an unlocked bootloader. Do you also have TWRP?

Related

Problem with my OnePlus One's Screen!

Hi there,
(Im opening a new thread as the old one was completely off the topic of the original post)
So on CM11S, my phone screen was working fine. After the CM12S update, my phones screen sometimes doesn't respond correctly when I go to unlock my phone with the unlock pattern. (The timing of the update and the problem occurring may just be coincidence) Its as if holding your finger on the screen isn't registered as staying on the screen, its like the phone thinks I am lifting my finger off and reapplying it very quickly, I cant draw my unlock pattern and unlock my phone. It also affects the 'swipe down' I must do to get the unlock pattern prompt.
If I restart my phone, it usually fixes the problem. Although in the past few days, it has started happening more frequently and sometimes restarting the phone doesn't solve the issue. It is becoming more of a frustration now because of how frequently I have to restart my phone just to unlock it.
I first believed that using a glass screen protector was the problem, I thought the glass was causing ghost touches, so I removed my glass protector and replaced it with a film protector, at first it seemed that this was the problem, but I have just encountered the problem again. I'm not sure if its a hardware or a software issue, because restarting the device is fixing the problem most of the time, but its also switching off all power to the digitizer during a reboot so I cant tell what is the culprit.
I've opened a support ticket with OnePlus but it says it can be up to 10 days before I get a reply, I figured I'd post here too to see if anyone else has had similar issues or even found a fix.
Thanks in advance!
I had the same problem
I was having the same issue, although I never updated to CM12S. Instead, this happened to me when running Exodus Lollipop ROM and the SlimLP ROM. Since then, I have switched to Paranoid Android Alpha2 and have not had the issue recur in the last few days running PA. So to me it seems like a software glitch in many of the Lollipop ROMs. Try PA if you like and see if it's fixed.
welcome to ghost touch
google "oneplus one ghost touch" and join the hundreds of other known cases
I had a feeling this was the ghost touch issue, but my phone hasn't really had actual ghost touches, its just that most of screen stops working. I've got a few videos of it happening. First the screen goes a bit unresponsive, then after a short while, about 1/3 of the screen is completely unresponsive, I switched on show touches in development options and you can see that from the middle to the bottom of the screen there is no response unless I use the very edge on the right side, then it works, its like it has a dead spot. If I reboot my phone, that usually fixes the problem for a while, sometimes up to a whole day, but the problem comes back with time.
I was given a patch by the OnePlus automated support message, and it says my case has been forwarded to a specialist. I have just applied the patch which has rolled me back to CM11, I'm guessing it did more than just that, but the patch and notes don't really explain what it does. Either way, I'm in the process of receiving OTA updates so I can get back on CO12 so I can hopefully restore my data with my ADB backup (never done this before, not rooted my One yet)
Has anyone had any success with this patch?
Thanks
EDIT: So my ADB Backup isn't restoring on my phone. I am using Holo Backup (formerly Simple ADB Backup) and when I chose restore and select the backup, it just show the output for the help command from ADB and then doesnt appear to do anything else. Are there any manual commands to restore my backup or have I done something wrong?
Try going back to cm11s and then check...
Sent from Android (a google product)
Hi there,
So heres an update, I applied the first patch and it rolled me back to CM11S and the issue was still present on CM11S, I then got OTA's back up to CO12 and the issue still happens. I have turned off the off screen gestures and the ambient wakeup thing. It doesn't happen as often but when it happens, 2 restarts are needed to get it running smooth again.
My support ticket with OnePlus has gone quiet and I don't really know what my next step is? I have heard there is a second patch but I couldn't backup properly last time with ADB so I don't know if I want to go through all of the wiping and reupdating again when people report the 2nd patch is also ineffective.
Does anyone have any suggestions? I feel a bit cheated now knowing that my phone has what I can tell to be a manufacturing defect / hardware issue.
Another update here.
So after a week of silence from the OnePlus tech support, I have a new person handling my ticket and he has told me that I need to apply another display patch. I'm guessing this is the 2nd patch and not this final patch which was mentioned by Carl on Facebook.
Either way, I ran into a problem applying the 1st patch, I couldn't make a proper backup of my phone before I did the patch. I used SimpleADBBackup which I thought would work well but it took a very long time to create the backup and then when I applied the backup back onto my newly flashed phone, It missed many apps, only did app data for a few apps and didn't take any of my pictures or SD storage, so all my SMS and Call log backups were also lost. I would like to take a proper backup this time but I don't know how to do it? I don't trust this ADB backup method, even on the Simple ADB Backup program, it admits that ADB backups are hacky and untested.
I have been trying to use Helium but for some reason, my phone wont get past connecting it to the computer companion app, I have all phone drivers and ADB drivers installed correctly, but helium on the android side cant seem to see the computer app, the computer side of the app says that helium is enabled, but on my phone it is stuck on "waiting for the helium desktop app".
I feel like I'm having the worst luck with this phone, and its frustrating because I really like this phone and this flaw is really getting in the way of using this phone, I counted 8 restarts in one day due to the screen not working.
I hope someone can help me out, I don't want to fully wipe my phone again and I cant seem to back anything up correctly!
One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?
naghtan said:
One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?
Click to expand...
Click to collapse
I'm not sure if a full solution has been found yet. I read on Facebook that they are working with Synaptics to make a final patch which should solve the issue.
I've given up on trying to backup my phone without root, it just seems impossible to do right. I've just applied the 2nd display patch and got my phone running again, I think I may stay on CM11 and just forget lollipop until this issue gets resolved. I'm pretty sure last time I was on KitKat, the issues were there still but it may be less frequent, who knows?!
Do I have a better chance of seeing this screen issue less on KitKat or should I just update to CO12 for the 3rd time?
Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.
donk165 said:
Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.
Click to expand...
Click to collapse
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/
vickykolari said:
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/
Click to expand...
Click to collapse
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.
I write with the assistance for 10 posts at today and I declare them to STOP sending me those bug non fixing ROMS/ZIPS...
I will replace by myself the screen (they don't change it in warranty because I've on the frame some dents... )
It's a clear HW issue, on any software, if the display degrade to a "fail stage" you wan't come back never to a total solve situation.
I loved my Oneplus, but they buy some batches of too cheap display, and after some month, I see clearly the results.
donk165 said:
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.
Click to expand...
Click to collapse
I wish you all the luck mate..
vickykolari said:
I wish you all the luck mate..
Click to expand...
Click to collapse
Thanks man,
It went well, I have been issued an RMA and will be sending it back soon. Just waiting on the postage label.
Ive just received my new OnePlus One today, very chuffed as it hasn't cost me anything. RMA and Support with OnePlus may be a bit slow but at least they do the right things!
To anyone facing screen issues, create a support ticket and persist with it, it should pay off!
Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk
anugrah n3xu5 said:
Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.
donk165 said:
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.
Click to expand...
Click to collapse
Congrats! Enjoy the beast
Sent from my A0001 using Tapatalk

Set up phone without encryption?

Got my 32gb unlocked A9 a few days ago. Wondering, without modifying anything (unlocking bootloader, custom recovery, rooting, ect) is it possible to run this phone without encryption? My 3rd Gen Moto G feels faster than this. I find the general lag, and sometimes even freezing, a nuisance (especially during read/write), and have no need for the encryption. Is there an option somewhere to disable it? Maybe some different steps during factory setup (i.e. opting out of pin/fingerprint)? I'd like to have the phone decrypted, but would still like to use the fingerprint to wake/unlock the phone.
My phone is on the latest firmware, and I've already tried a factory reset, this is why I'm assuming the performance hit is the encryption.
Example of one of the stutters I notice is going between the home screen and the recents screen. Anyone else get this? Maybe something got screwy during the 20 (/s) firmware updates when I got it?
Edit: Also thought I'd mention that I'm also getting random reboots.
rouyal said:
Got my 32gb unlocked A9 a few days ago. Wondering, without modifying anything (unlocking bootloader, custom recovery, rooting, ect) is it possible to run this phone without encryption? My 3rd Gen Moto G feels faster than this. I find the general lag, and sometimes even freezing, a nuisance (especially during read/write), and have no need for the encryption. Is there an option somewhere to disable it? Maybe some different steps during factory setup (i.e. opting out of pin/fingerprint)? I'd like to have the phone decrypted, but would still like to use the fingerprint to wake/unlock the phone.
My phone is on the latest firmware, and I've already tried a factory reset, this is why I'm assuming the performance hit is the encryption.
Example of one of the stutters I notice is going between the home screen and the recents screen. Anyone else get this? Maybe something got screwy during the 20 (/s) firmware updates when I got it?
Edit: Also thought I'd mention that I'm also getting random reboots.
Click to expand...
Click to collapse
AFAIK it is not possible without TWRP. I have reflashed the whole system and tried if it stays decrypted without setting up fingerprint, but it does not.
I have had some lags as you described, it got better with usage, there are some micro lags, but I got used to it. It is smooth in general. I have also had one reboot in the first few days, but not ever since. Give it a little time.
Sent from my HTC One A9 using XDA Free mobile app
I downloaded the 1.7gb file from HTC and used that to reflash(?) the phone. I can tell some things are different in the UI than when it went through the chain of updates, and seems faster too. Might be placebo. I'm still waiting to see if I get a reboot. Reboots were happening about every 12 hrs.
rouyal said:
I downloaded the 1.7gb file from HTC and used that to reflash(?) the phone. I can tell some things are different in the UI than when it went through the chain of updates, and seems faster too. Might be placebo. I'm still waiting to see if I get a reboot. Reboots were happening about every 12 hrs.
Click to expand...
Click to collapse
Yeah, I did the same too. I felt the phone became more laggy, after updating OTA, so I thought reinstalling the latest firmware might be the best idea. I'm not saying it is perfect, as it is not, multitasking can be really sh*tty sometimes (I have the 2Gb version though), but it is usable, and generally fast and smooth.

Pixel Oreo - Major issues with Calls

I just updated to Oreo via OTA and the phone worked great for a day. After that, I couldn't make calls and people couldn't call me. My phone would randomly reboot or get stuck on the G logo.
I wiped and reinstalled Oreo, and now the same thing is happening. Plus I see this weird 'colourful static' after trying to make a call, before my phone just shuts off. I tried safe mode and the same thing happens.
Currently in an urgent situation where I need my phone to be functioning, hoping someone here can help.
Thanks
I am having exactly the same issues since the Oreo OTA. If I reboot the phone, the issues go away for a while, but eventually it's back to problems where I'm unable to make/receive calls, screen is flickering (even that colored static you mentioned), lag when unlocking the phone, etc.
Have you found out anything?
erc. said:
I am having exactly the same issues since the Oreo OTA. If I reboot the phone, the issues go away for a while, but eventually it's back to problems where I'm unable to make/receive calls, screen is flickering (even that colored static you mentioned), lag when unlocking the phone, etc.
Have you found out anything?
Click to expand...
Click to collapse
I have no such problems. I am running stock. It is running really smooth. I also have september security update. Unfortunately, only thing I can suggest is factory reset.
rohitece06 said:
I have no such problems. I am running stock. It is running really smooth. I also have september security update. Unfortunately, only thing I can suggest is factory reset.
Click to expand...
Click to collapse
I am also running stock, never rooted, never unlocked the bootlader, also running the september security update. I have factory reset, and I have even run into the issues while using the phone in Safe Mode. There are a number of people with similar issues leaving feedback on Google's issue tracker, but I was hoping to find someone who maybe has found a solution.
erc. said:
I am also running stock, never rooted, never unlocked the bootlader, also running the september security update. I have factory reset, and I have even run into the issues while using the phone in Safe Mode. There are a number of people with similar issues leaving feedback on Google's issue tracker, but I was hoping to find someone who maybe has found a solution.
Click to expand...
Click to collapse
I am sorry to hear that man! I hope you/google figures it out.... may be try flashing the factory image manually.
I'm having the same issues and verizon Chat support told me they are having issues with the OS upgrade and the Pixel. Did the factory reset and everything else. Replacement phone coming now. If it's the Oreo OS, I bet it's going to have the same problem... This is a major problem, as I am a single Dad and have a long drive to get my daughter - do they really want me to text while I drive instead of calling?? This is Day 5 of this issue and 4 trips to their stores.... ugh. Suggestions?
Update
Just wanted to post an update. After factory resetting a few times the problem persisted. I sent it back to my wireless carrier and they sent it to Google. In the meantime I had a loaner phone from my carrier. Google sent back a refirb (it was practically new with new screen and camera), and the issue hasn't come back in the new phone. My suggestion is to send back to your carrier to get a replacement. Good luck!
i am on stock too (from google store), oreo update and have exactly the same problem, it also occurs with "ok google".
after reboot, calls and "Ok google" work perfect so the mic is okay. but sooon after it just stops working and i got randoom reboots.
same is happening in "safe mode"
i did factory reset via android and id did not help.
now i tried a factory reset via boot menu and will check it out.

OP6 woes. Seeking advice.

Hello fellow OP6 users. I am a long time lurker and beneficiary of these forums but I have an issue that I wanted to run by anyone as I am at a bit of a loss presently.
Specifically, I run a TWRP'd/magisk'd OP6 on OxygenOS 5.11. I jumped the gun a flashed the official from these forums as OS 5.9 was giving me fits and the battery drain seemed off the charts. Fast forward to today, I am in 5.11 and am experiencing all kinds of little bugs (random reboots, auto brightness not working, proximity sensor faulty, device wont wake - must be rebooted). The issues themselves seem random and inconsistent but are issues nonetheless.
My options are to nandroid to pre 5.9/5.11, go back to stock, RMA device (bought warranty) etc. but I am wondering if either A, anyone else is facing similar issues or B, you might read this and share an opinion or recommendation. It feels like a software issue but then again, I'm not an expert.
Thanks in advance for any feedback. Be well.
i would titanium backup your apps and then do a oneplus switch app backup and then try to do a fresh install of the latest firmware and then only restore the normal apps and install the system apps manually
xCoolBreezex said:
Hello fellow OP6 users. I am a long time lurker and beneficiary of these forums but I have an issue that I wanted to run by anyone as I am at a bit of a loss presently.
Specifically, I run a TWRP'd/magisk'd OP6 on OxygenOS 5.11. I jumped the gun a flashed the official from these forums as OS 5.9 was giving me fits and the battery drain seemed off the charts. Fast forward to today, I am in 5.11 and am experiencing all kinds of little bugs (random reboots, auto brightness not working, proximity sensor faulty, device wont wake - must be rebooted). The issues themselves seem random and inconsistent but are issues nonetheless.
My options are to nandroid to pre 5.9/5.11, go back to stock, RMA device (bought warranty) etc. but I am wondering if either A, anyone else is facing similar issues or B, you might read this and share an opinion or recommendation. It feels like a software issue but then again, I'm not an expert.
Thanks in advance for any feedback. Be well.
Click to expand...
Click to collapse
I feel like you should flash stock rom (not restore) and wipe all but internal, keep it stock and see if you have the bugs. After some time you might miss root, then you root and apply one mod a the time so you can see what actually makes the bugs you are facing occur.
I agree with @whizeguy but I would take the 'start over' a step further. I was hosed a month back and a wipe did not fix me... I had to 'format' . . . the data in recovery. Please read up on what twrp 'format' does. It will clobber your saved stuff on your phone. And the official version of twrp will not mtp the files back onto your phone from your pc. You will need to use the un-official twrp here.
https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
.
And you can forget about mtp and fastboot flash the latest rom following this link's instruction.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Excellent suggestions. I will investigate. Thanks guys.
Yeah, I agree with all the above. This is one of those situations that calls for a full wipe and fresh reinstall.

Constant reboots and freezes

Hello, two months ago I got my 12gb oneplus 8t.
And recently been getting constant freezes and reboots. These normally happen when unlocking the phone and when I have some backround apps running like strava (but there are times, when there is basically nothing running in the backround). Out of all freezes only 1-5% are reboots. Out of all unlocks, 10-20% are freezes. What could be causing them? What's interesting that they started happening in 2020/12/10, when messenger servers were broken.
I tried to do a factory reset, but that didn't help.
My phone isn't rooted, I have yt vanced and I bought that phone from ali. I know a weird place to buy, but the price diferance was almost 200eur. But it isn't the "global version", where they ship a china rom oneplus to the EU, open the box and install the global rom.
Edit: I forgot to mention I am running the latest version of Oxgyen (the freezes didn't stop after the latest update). Am I the only one with these problems? Should I install lineage OS? As I quite like the launcher.
Tomasltboom said:
Hello, two months ago I got my 12gb oneplus 8t.
And recently been getting constant freezes and reboots. These normally happen when unlocking the phone and when I have some backround apps running like strava (but there are times, when there is basically nothing running in the backround). Out of all freezes only 1-5% are reboots. Out of all unlocks, 10-20% are freezes. What could be causing them? What's interesting that they started happening in 2020/12/10, when messenger servers were broken.
I tried to do a factory reset, but that didn't help.
My phone isn't rooted, I have yt vanced and I bought that phone from ali. I know a weird place to buy, but the price diferance was almost 200eur. But it isn't the "global version", where they ship a china rom oneplus to the EU, open the box and install the global rom.
Edit: I forgot to mention I am running the latest version of Oxgyen (the freezes didn't stop after the latest update). Am I the only one with these problems? Should I install lineage OS? As I quite like the launcher.
Click to expand...
Click to collapse
If a factory reset didn't solve the problem, may be it is a ROM issue. Try downloading the ROM again from OnePlus website and do a clean installation.
I'm also having the OnePlus 8T and never had such issues. There are bugs like screen yellowing randomly and others, but no freezing/ rebooting problems.
Sridhar Ananthanarayanan said:
If a factory reset didn't solve the problem, may be it is a ROM issue. Try downloading the ROM again from OnePlus website and do a clean installation.
I'm also having the OnePlus 8T and never had such issues. There are bugs like screen yellowing randomly and others, but no freezing/ rebooting problems.
Click to expand...
Click to collapse
Ok, will try, thank you! I have the same yellowing screen issue, but as far I understand, it's somekind of bug with reading mode. (well I am just guessing). Because it happens only in google chrome.
Tomasltboom said:
Ok, will try, thank you! I have the same yellowing screen issue, but as far I understand, it's somekind of bug with reading mode. (well I am just guessing). Because it happens only in google chrome.
Click to expand...
Click to collapse
That yellowing in Chrome is a Chrome issue. You have to disable 'Dynamic Color Gamut' under chrome://flags/.
I'm talking of screen yellowing throughout the device. It happens at random and is present everywhere.
Sridhar Ananthanarayanan said:
That yellowing in Chrome is a Chrome issue. You have to disable 'Dynamic Color Gamut' under chrome://flags/.
I'm talking of screen yellowing throughout the device. It happens at random and is present everywhere.
Click to expand...
Click to collapse
Ah, okay, thank you. Well I don't have the yellowing issue then.

Categories

Resources