Problem with choppy video playback - OnePlus 6 Questions & Answers

Hi everyone, looking for some help. Just got my OP6 and it upgraded to newest 9.02 and everything seemed to be working fine. I streamed something briefly on twitch.
I then went to mess around, unlocked bootloader, installed twrp to root, flashed Havox, didn't love it, then came back clean version of latest ROM using fastboot flash. I don't recall testing video while on Havoc, but now no matter how I try to play a video it is choppy and laggy (takes 10 seconds to stutter through a 4 second YouTube ad). Also affects playback of a video I recorded in gallery, browser (CNN) - basically all videos. Everything else with the phone seems completely normal.
Tried wiping YouTube cache, cache in recovery, factory reset, different kernel. No difference.
Anyone heard of this before? Seems the GPU should be fine if it worked initially. Any ideas what I need to flash to address the video playback?
Thanks much.

Update: from the hardware diagnostics it was able to play a music video without a problem so it seems like something happened when I was flashing. Suggestions on restoring it to stock? I'm looking at the MSM tools as the next step.

You can download preferred oos full zip of chioce,boot to twrp, flash oos, flash TWRP reboot recovery, flash oos and TWRP again, magisk, kernel and any other mods. If you moved to another ROM without wiping data, that would cause issues too. Backup data in TWRP (data only) and try booting after clearing data and see if that resolves the issue.

Related

[Q] Bootlooping - Anyway to save it without a wipe?

So, the tablets been working fine. It's been running some older version of CM10 unofficial from March of 2013. It would deep sleep every now and then and boot loop, but it's always come out of it. Now, this weekend while out of town, it deep sleeps, so I reboot it and it just boot loops now. I can get to recovery (TWRP) and I've tried re-flashing the zips for the rom and kernel, but I'm not getting any results. It hangs on the circling Cyanogen logo and just keeps spinning in circles. I've tried everything short of factory reset...
This thing was mainly used for games, and I really really don't want to lose the data if at all possible. Is there a way to get this thing to work without a wipe? Flash a different rom over top or something? Any help is appreciated.
Details:
TF101
CM10 Unofficial from March
Tim Kat Kernel 47b
TWRP 2.3.1.1
It is much appreciated! I'll be updating it once I get back into it and am able to back it up. Thank you!!
Hard to say what will fix it. I know a lot of KatKiss users have had data corruption issues during some random reboots and the fix is to turn FSYNC on (zip file in the KatKiss thread). I am not sure if that would fix this issue you had or not, but it has to be flashed before it gets corrupted.
Here is what I would do:
Since a dirty flash is not helping (wipe caches & system and reflash), make a backup of the DATA partition.
Wipe the data, system & caches.
Flash the ROM, kernel and GAPPS.
Boot up, login with your google account.
Go to the Play Store and grab Titanium Backup and the Pro Key.
You can then use TiBu Pro to restore from a Nandroid (it is in the menu under special backup/restore). It works for most all apps and games, but there may be some that do not work. Not much you can do about it.
Well, I'll give that whirl today. I actually have another back up app that I forgot what it's called. My Backup Pro I think? I use it on my DNA and it works well. Will probably just use that for the game data. I plan to get the KatKiss multi window rom after this fiasco is taken care of. Thanks for the tip!

[Q] "Android is Optimizing.." Issues - NEED HELP!

Hi Everyone,
I've been having some trouble getting custom ROMs to fully boot on my girlfriend's Galaxy Tab 2 (p3113). I was able to gain root access (I used this method: http://forum.xda-developers.com/showthread.php?t=2510669) and managed to install the latest CM rom, SlimRom, or OmniRom (with their respective Gapps).
However, I always run into the same problem: whenever I reboot from recovery (regardless of which rom was installed), android begins "optimizing" apps (presumably because I've cleared caches, including dalvik) and at the end, reports 2-3 process that have unexpectedly stopped, and reboots. I've done clean wipes with each install, and even tried re-downloading the roms, but nothing seems to work. Also, it doesn't seem like the stopped processes are consistent between roms. For example, the CM rom would report calendar and keyboard processes that have stopped, whereas Omnirom would report mediastorage and google search processes that have stopped.
Anyone have any ideas of what I can do to fix this?
It sounds like you are not doing a full wipe, I dont think it should be optimizing on a fresh clean install. Try factory reset, wipe cache/dalvik. And possibly system.(usually recomended)
Sent from my SGH-T889 using XDA Premium 4 mobile app
Thanks - that what I suspected as well, although I thought I was doing a full wipe (including /system) in TWRP, but maybe not?
Anyway, I somehow got it working last night after formatting /data and then flashing the last CM stable release (CM-10.1.3, p3110). Got the tablet to boot and setup and everything. Maybe there was something conflicting in the data folder, or that there was no more space on the internal SD. Guess I won't know now..
But I decided to flash the latest Omnirom instead, to get a 4.4 rom. Seems to be working fine now. Thanks for the reply!

Can't find anything in storage on factory image 5.0

I flashed the 5.0 factory image (just the bootloader and system parts, franco.Kernel and superSu, did a Factory Reset). When I try to access my data via the Photos app or ES explorer, I can't see anything. However, when I tried to send a pic via whatsapp, I could see my entire gallery there, as though the information still exists on the device.... This is especially weird because I was using an AOSP built Lollipop ROM for a couple of days and haven't encountered any issues whatsoever.
How can I solve this problem?
Same crap happened to me. I think something happened when dalvik was converted to art. It took me a while to figure it out but clean flash back to a dalvik 4.4.4 rom, I used dirty unicorns. Afterwards clean flash lollipop. Good luck.

I used a magisk module that modified some DRM and now NOTHING fixes it

The module that did this was "liboemcrypto disabler" and was advertised as allowing DRM content to be viewed in full HD despite my bootloader being unlocked. It immediately put me in a boot loop after installing. I removed the magisk module from recovery but I was stuck in a boot loopstill and ended up having to wipe. I've done a full wipe, I've fully erased and decrypted the phone with ALL IN ONE tool and then installed a new stock ROM via fastboot. I then used TWRP to wipe EVERYTHING and then used ALL IN ONE TOOL to erase the phone and then used MSM tools to reflash a stock ROM and start from scratch while also choosing to wipe all data in the process. Netflix not working has persisted through all of this, it seems this module has touched a drm file that is normally out of reach in the wiping process / it's not replaced when doing a clean install. Another odd thing is that throughout this whole process, Nova Launcher stayed installed throughout all of the wipes. Any time I try to open Netflix it either says I need to update and clicking okay brings me to the play store where it tells me Netflix is not compatible on my device. Sometimes I get other error messages but it's always the same, Netflix doesn't work. The odd thing is I got it working on Pie in the process of unlocking my tmobile bootloader with the Android 10 DP3 so I could root it. Netflix actually worked for a second while I was on Pie, up until I updated to Android 10. This leads me to believe that the drm Android 10 is using is different from Pie and upgrading put me back to relying on the ruined drm file. I've even tried installing and uninstalling the magisk module that screwed all of this up hoping it would replace the original drm file but I've had no luck. This is such an odd problem. I had no clue any magisk module had the power to give your phone problems that literally can't be fixed through full wipes and reinstalls. I've tried removing netflix from ADB and reinstalling the apk manually but there's still no luck. The other streaming services that normally rely on this DRM are fine. If anyone has the slightest idea of what to do here I'd love to hear it! Are all drm files the same for everyone? If I were to aquire the drm file that was replaced while installing this thing could that possibly fix it? The file that is modified is under /vendor/lib/ and is named "liboemcrypto.so"

Question Wierd camera issue after TWRP reset.

Good day all,
I've run into a bit of a problem and I'm starting to pull out my hair.
I have a A32 5G with stock OS thats rooted with TWRP.
And after fiddling a bit to much I now have problems with a few things including GPS etc and I want to factory reset so I can start fresh, But everytime when I wipe with TWRP and boot up again the stock camera app has a wierd issue, it crashes as soon as it goes into the video or any other mode although it does take photes. I've tried clearing the cache and data from the app as well as in TWRP. Also opencam works fine but I would much prefer the stock app to work.
Also when I restore my old backup with TWRP it works again but ofcourse the other bugs also come back too.
Any suggestions would be welcome. Thanks!
That's weird. my suggestion would be to clean flash via Odin whatever version your at.
then flash twrp and run multidisabler twice and format data...
financeledger said:
That's weird. my suggestion would be to clean flash via Odin whatever version your at.
then flash twrp and run multidisabler twice and format data...
Click to expand...
Click to collapse
You are the definition of awesome!! It worked! Many Many Thanks!
a_private_identity said:
You are the definition of awesome!! It worked! Many Many Thanks!
Click to expand...
Click to collapse
Im glad it worked !!
It was a software issue then probably some app broke the camera functionality.

Categories

Resources