Jibberish and noisey rendering in Google photos and chrome randomly turns black - Xiaomi Mi Mix 2 Questions & Answers

I recently went through a disaster of switching to AOSP 9.0 custom ROM and when I tried to revert, I got my encryption password messed up by the recovery.
Restored everything to stock and then just rooted with magisk.
Phone, now is acting crazy. I've done 2 factory resets (literally lost 3+GB worth of photos and documents due to encryption lockout).
In Google photos I see my things backed up just fine but they appear jibberish and noisey on my phone's screen. They are fine otherwise if I explore my backup on PC. (Some rendering issues maybe?)
Secondly, Google chrome randomly turns into black screen while the webpage is alive (playing audio/video etc).
I need to resolve this issue. I'm currently on MIUI 10 8.12.27 beta. I didn't have any issue previously on 8.10.22 ROM before all the custom ROM and encryption fiasco.
Anybody has a clue how to resolve these issues?
Also, device randomly jumps to lockscreen while I'm in the interface (doesn't do so when I'm playing a game)
There are no artifacts or abnormal behavior while playing games. Only for 2D render.
See attachment to have an idea

Related

[Q] Stuck at startup screen and CM 10 question

I was using Energy ROM (dated June 2012) and my KF suddenly locked up. I rebooted the KF and it stuck at the color tiles for at least 10 minutes before I gave up and restarted it, which didn't help. I then flash it with the latest Energy ROM and the problem won't go away and I used the complete wipe option. I also tried out Alien ROM and Hashcode's CM 10 ROM. While both of them would boot fine, I have problem with internet videos in browser. Particularly, the video control bar would pop up and down as soon as I nudge the KF. This was happening when I'm using Dolphin and the default browser. Is there a way to fix it?
What recovery are you using? Version? Not that it really matters. I'm just curious why Energy wouldn't work after a complete wipe.
To fix the problem you have with videos, simply turn your rotation off.
I believe TWRP is 2.2.2.1 and latest FFF bootloader retrieved from KFU. If I turn off rotation, wouldn't the display be stuck at 1 orientation?
LOL. Rotate your device, THEN turn rotation off. The rotation is pretty sensitive and when the media player detects a slight amount of rotation, it acts up.
OK I'm dumb =). I noticed that in the default browser, it doesn't suffer from the annoying video controls popping up and down. However, Dolphin still does so I assume it's Dolphin's problem. I'm using iPad as user agent otherwise the sites will try to get me to install Flash.
However, my original problem with Energy ROM baffles me. A few months back, I notice it was gradually slowing down and getting less responsive and completely dropping WiFi connections. So I reformat and reinstall it and it ran until I notice the same problem until it locked up for good. What kind of problem is preventing the ROM from running properly even after a full wipe install?
Energy ROM hasn't been updated in months and is pretty much dead in the water. The 3.0 kernel for the Kindle Fire has been updated many times since Energy was last active here.

[Q] Otter1 Unstable Across Roms

There may be no help for me on this, but I have a real tolerance for punishment.
I am having a frustrating time with my Kindle (Otter1). After updating to CM10.1, I started having weird problems: No browser is stable (Browser, Chrome, Maxthon, UC, Dolphin, FF, Opera). Any page more complicated than Wikipedia with crash the browser regularly - completely removed from memory, goes back to home screen. If I have a live wallpaper, it will then disappear after the browser crashes. Most of the time, it will crash on flipup or down, but sometimes it just seems to give up on its own and commit suicide.
I started trying different ROMs thinking that maybe CM10.1 just had some weirdness. I have been through Kang, Hellfire, AOKP, and Carbon. All exhibit the same behavior. I have wiped, wiped, wiped, wiped. Including formatting SD and started from a pristine device. The result? Browser self immolation. I have looked at each ROMs readmes. I have waited 10 minutes, 20 minutes, even 30 minutes in a fit of pique and patience.
I have also install a build.prop editor and turned HW acceleration off. I have reduced the number of simultaneous graphic events and I have reduced flip velocity. None made a difference.
I have TWRP and FFF. the latest ROM is Hellfire 8/13. I also have a desperate need for advice! Any suggestions?
Help!
I think this is just the work of a low mem device really man. I have alot of the same issues. Im hopping KK will give us some better performance though.

Phone Randomly Crashing

I am currently running the latest build of the PacMan rom for my Sprint S3, but my problem didnt start there. As over the course of a few weeks my phone has been randomly crashing while running build 7 of Slimkat. It started crashing when i wanted to take a picture with the AOSP camera (when i hit the camera button and then it would shut off). Then it progressed to just crashing trying to use accuweather, or even when the screen was auto-rotating in my SMS app. So finally i just backed up my important bits and made a clean wipe into Wicked X 8.0 TW rom (because i'm on Ting and TW roms initially work on their network and wanted to export, or to just copy down the settings of, the APN xml to use in AOSP roms). After playing around with that for 20 minutes, i didn't experience any fc's or reboots. Though i did not use the camera in that time (i forgot to check). To which i then wiped it into PacMan rom that im at now. Which at the moment seems fine to do everything, except it will shut off if i want to OPEN the camera (doesn't let me use it at all). Plus i did have it crash once rotating with the play store up...
So im kinda lost, i wonder if this is just an issue with the camera in the rom, or if it might be a bigger issue with the phone itself. As ive been having the same random error's with two roms and i dont see anyone having FC's with pacman rom with the camera.
more testing done
So i have also attempted to odin completely back to stock and i have a stock rooted rom with nothing touched. The sudden shut-offs still happen and occur randomly. I installed logcat and what seems to be throwing error's is the accelerometer. Plus at first when i flash a new rom it seems to work ok with no problems for the first day, then suddenly start showing symptoms the next. Plus ive had it shut off during bootup too while going through the sprint 4g animation screen. Though i have not had it die on me in recovery, so thats a thing.... Plus it will rotate no problem half the time, and then ive seen it die rotating to use my keyboard.
So at this point i feel like its actually a hardware option. If it is the accelerometer, is it easy to fix (i guess re solder the connections if they're broke?)? or should i just try and replace the main board?

Question Random System Crash When Connecting to an External Display

So I play a lot of games on my phone, whether it's an emulator, xCloud, Minecraft, or something else, I usually prefer to connect my device to my TV to more comfortably play. However recently I've been running into a bug on my OnePlus 9 Pro. (T-Mobile Version unfortunately). Here is where I'm at, every time I plug my phone into a TV, it freezes and crashes. Just like that. It worked for a while and then randomly stopped (I hadn't downloaded anything new or updated anything yet). I did download the newest firmware and still experienced the crash. I have switched the resolution, adjusted the frame rate, turned off Desktop Mode, and even did a factory reset. Still crashing at this point. Has anyone experienced this and figured out a cause or a fix? I am already on my second device from T-Mobile for this issue (exact same experience) so any help is appreciated.

Phone became literally slow

I was just playing a game and while it was downloading some updates, the phone suddenly became like this.
WP_20200531_11_44_47_Pro.mp4
MP4 File
1drv.ms
I've already tried restarting, shutting down, and factory reset but the phone is still this unbearably slow.
Any idea on what's causing this? I'm assuming this is a hardware issue since factory reset didn't fix it, right?
I also see a rainbow pixel static noise when unlocking the phone like the one mentioned here:
https://www.reddit.com/r/mobilerepair/comments/aqjnzr
Link to the actual image:
https://imgur.com/a/kHyq63p
And also when I boot the phone, the phone will slowly display the oxygen os circle animation but there are already notification sounds.
Full experience
Your browser is not able to display this video.

Categories

Resources