yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10+ Guides, News, & Discussion] cvat:
Guys, before you reply with any feedback, please read the following post and links in full. It would also help if you posted details of your device like the following, which is mine:

Summary: An intermittent stutter or lag (most notably during fullscreen 4K HDR playback, in my case) which only goes away when you activate certain screen recorder applications like Game Tools or AZ Screen Recorder.

Below is a list of posts that highlight this problem that I and a few others are experiencing. The common denominator here is the use of a screen recorder, which removes any present stutter or lag.

https://xdaforums.com/s10-plus/help/lag-stutter-overall-choppy-t3914381

https://www.reddit.com/r/galaxys10/comments/btwfbl/anyone_experiencing_stuttering_or_frame_drops_on/

https://www.reddit.com/r/galaxys10/comments/b79cw3/is_snapdragon_really_that_much_worse_than_exynos/

https://www.reddit.com/r/galaxys10/comments/b4nftn/snapdragon_s10_laggy_on_4k_youtube_playback/ (video evidence of problem)

The following two are from myself. My problem is that all 4K HDR content (could extend to other formats also but I need to do more testing) is stuttering or dropping frames. Screen recorder on and boom - it's smooth.

https://www.reddit.com/r/galaxys10/comments/ch172q/snapdragon_owners_does_this_type_of_video_play/

https://xdaforums.com/s10-plus/help/sm-g9750-video-playback-throttled-t3950757

The lag returns as soon as you deactivate screen recording, which suggests that this is either a bug with the CPU or GPU not being optimized or boosting its frequencies properly, leading to these stutters.

I've put Snapdragon in the title as these posts all appear to be from Snapdragon owners, whether it's the US or HK variant. I don't recall ever having this issue as a last generation S9 Exynos owner. If you are an S10/+/e Exynos owner and encountering this issue, you could still try using your phone normally, with a screen recorder active and then without, to see if there is any performance gain (as crazy as it sounds, it might actually make a difference).

Below is a test I'm using to demonstrate my problem. It involves installing apps (namely YouTube Vanced and either one of two screen recorders I've tested it with), so it's not the most convenient. If I find a better method, I will update the post accordingly.

If you are not experiencing any such issues with your device, then congratulations, you have passed the test! Thanks for taking some of your time to provide valuable feedback :good:

Any non-constructive comments will be ignored and reported.
[Samsung Galaxy S10+ Guides, News, & Discussion] okbakaka:
Yes and the solution is? To turn on video recording all the time ???????
[Samsung Galaxy S10+ Guides, News, & Discussion] cvat:
Well if you have a better solution then I'm all ears? I left a similar post in the Q&A section and didn't receive a single reply. So I thought I'd post it here instead since it's more active.

We're still in the "Guides, News, & Discussion" forum, right? And technically this could even be a guide since I posted a solution, no matter how useless it may be ;)
[Samsung Galaxy S10+ Guides, News, & Discussion] Limeybastard:
What resolution are playing those videos at?

I played the Peru 4k 60 [MENTION=921577]1080P[/MENTION] one on youtube and it was great. Then played the same on Vance 1440 [MENTION=7825661]60fps[/MENTION] and it was same smoothness.
[Samsung Galaxy S10+ Guides, News, & Discussion] citytrader:
I didn't experience that lag in my Exynos...
[Samsung Galaxy S10+ Guides, News, & Discussion] cvat:
2160p@60fps is where I experience constant stutter. You will need to override resolution checks in Vanced to watch at that resolution: Tap the account icon in the upper right. Go to settings, Vanced settings, Video settings and then toggle Resolution Checks to ON. Refresh and restart the app.

Don't forget to try it with the screen recorder on please, to compare if playback is smoother.

Just realized you're on Exynos, so the issue might not pertain to you, though there's a chance I might be wrong in that regard. Thanks for testing though - more feedback is always welcome :good:
[Samsung Galaxy S10+ Guides, News, & Discussion] Limeybastard:
I'm not on exynos. I dont have any game tools or screen recorders on my device.
[Samsung Galaxy S10+ Guides, News, & Discussion] cvat:
Lizard brain saw the GB flag and assumed you were an Exynos owner - my mistake! So you debloated your phone huh? Is something like Nice Shot or AZ Screen Recorder an option?

Here's a link for anyone wanting to download and test locally:

https://mega.nz/#!HvJx0AJA!giPtSteTVSF4lhBsC--J1CLCWqX5IFTJmWjiL8nHOw4

or

http://www.mediafire.com/file/dzndenwhk6ddboc/COSTA_RICA_IN_4K_60fps_HDR_%28ULTRA_HD%29.mp4/file

You will also need a screen recorder of some sort though, that's the most important step. Here's a few:

https://play.google.com/store/apps/details?id=com.hecorat.screenrecorder.free&hl=en_GB

https://www.apkmirror.com/apk/samsung-electronics-co-ltd/nice-shot/

https://www.apkmirror.com/apk/samsung-electronics-co-ltd/samsung-game-launcher/

update: Nice Shot doesn't work for this test.

Appreciate anyone else willing to try, of your own volition of course. Doing this purely to raise awareness on the issue and gather feedback.
[Samsung Galaxy S10+ Guides, News, & Discussion] Limeybastard:
I just tested this using the supplied download links for the actual video and AZ screen recorder.

In all honesty I couldn't see any difference between the video running with or without the screen recorder recording it. They both looked smooth. I was using the default video player to watch the downloaded video.
[Samsung Galaxy S10+ Guides, News, & Discussion] Limeybastard:
It was the circled video player. View attachment 4797789
[Samsung Galaxy S10+ Guides, News, & Discussion] cvat:
That looks like the Samsung video player, but no matter since the problem persists across other players too. MX Player in HW decoding seems to be the worst performing one for me.

Did you watch in landscape fullscreened? I keep forgetting to add that detail. If it was the same regardless, then I guess that removes the US Snapdragon from the equation. But thanks for taking the time to test, much appreciated :good: People probably think I'm bullshitting but once I find a concrete way to show what I'm experiencing, I will update this thread.

So far I've only had confirmation of this problem from two (yes, only two but it's still something!) other people, and they also happen to be owners of the HK S10+ variant like myself. If there are any other HK owners out there, I could really do with your feedback on this too!
[Samsung Galaxy S10+ Guides, News, & Discussion] Limeybastard:
Yes , I watched it in landscape mode, even compared the first few scenes where the camera pans etc with screen recorder on and off, couldn't tell the difference.

Maybe you could film the issue with a camera for us to see ?
[Samsung Galaxy S10+ Guides, News, & Discussion] Swimguy14:
Mx player with hardware decoding is no problem, smooth as butter. Snapdragon U1.

What does YouTube report with nerd stats turned on for the dropped frames line?

No offense but your premise is flawed at best. All you have done is made a subjective claim backed up by no legitimate measurable evidence..

Having people install screen recorders and play videos is not 'testing' anything..

Best of luck
[Samsung Galaxy S10+ Guides, News, & Discussion] cvat:
That's been tried by someone already but the thing with these cross-comparisons is that they aren't conclusive enough for some people. For me it's crystal clear because I already know what to look for.

Here, this link was in the OP: https://www.reddit.com/r/galaxys10/comments/b4nftn/snapdragon_s10_laggy_on_4k_youtube_playback/

One on the left is HK S10+, Exynos S9+ on the right. Make sure it's in 1080p@60fps so it's as clear as possible.

The most obvious thing is that the scrolling is laggy on the HK model, but if you look closely, the video is stuttering too (look at the zooming out shot at the beginning). Exynos is completely smooth.

Stuttering video is a big no-no for me, really should not be happening on a phone of this spec.
[Samsung Galaxy S10+ Guides, News, & Discussion] cvat:
Okay fair enough my test isn't the most thought out, but if you have any better suggestions on how to demonstrate the problem, you're more than welcome to provide them.

Stats for nerds doesn't show dropped frames, so it's likely that any FPS monitoring software would be useless too.

No it's not a subjective claim because if you read through the post and links in full, you would see a number of people confirming the problem. Doesn't matter how few, it's still an issue that shouldn't be ignored.

And one of the links has evidence in the form of video comparison: https://www.reddit.com/r/galaxys10/comments/b4nftn/snapdragon_s10_laggy_on_4k_youtube_playback/ please watch it @ 1080p60 on something larger than a phone screen.

The one thing I should've probably clarified is that I'm on the HK S10+, but those links indicate that US variants have a similar issue too. If yours doesn't have it, then cool, you're good to go :good:
[Samsung Galaxy S10+ Guides, News, & Discussion] Limeybastard:
So now we're talking about the scrolling when the video is played minimized like the reddit video? Yes mines like the same laggy. But the video itself full screen is ok.
[Samsung Galaxy S10+ Guides, News, & Discussion] cvat:
Not the scrolling specifically because that's related to the problem. For me the scrolling is laggy AND the video stutters. Are you sure the video is completely smooth? It might seem so but on mine there are frame drops present - even if it's very minor, there should be none at all.

It's best to compare with another capable device side-by-side with your own eyes, as no video recording will be able to demonstrate this clearly enough. There's also a chance that some people aren't sensitive enough to stutters and might not even be able to perceive them (I'm not saying you are, this could genuinely not be happening on your device).

And even if the video doesn't appear to be stuttering to you, shouldn't the laggy scrolling be enough cause for concern? A last gen phone is running smoother and that's not acceptable. Don't settle for mediocrity guys.

edit: before anyone questions the absence of screen recording in that video, the person who uploaded it has another post on reddit where he mentions it fixing the problem.
[Samsung Galaxy S10+ Guides, News, & Discussion] Limeybastard:
Watching it at 1440p on native YouTube app it seems the scrolling is smooth. But on Vanced [MENTION=7862454]214[/MENTION]0 not so smooth scrolling. Probably the Vanced app or cpu etc binning on the snapdragon.
[Samsung Galaxy S10+ Guides, News, & Discussion] cvat:
I don't think it's the app or hardware because once I turn on the screen recorder, playback is perfect (landscape). I'm no expert on this but a logical guess means there's a frequency boost while the recorder is active, removing the stutters.

If I could find a less ****ty workaround that does the same, I would be okay with it, but there isn't :mad:
[Samsung Galaxy S10+ Guides, News, & Discussion] sruel3216:
No lag here. My phone has been flawless. SD
[Google Pixel Questions & Answers] maverick6664:
Hi,

I have once rooted my google pixel, but I changed my mind, and decided to unroot it and lock the bootloader.

I chose "lock" in the twrp menu, and I entered an endless loop.

Now the bootloader is locked and won't boot. The phone just splashes the initial screen and off, a few seconds after that, splashes the screen, and off,.....repeatedly. It looks like as soon as the initial "GOOGLE" screen appears, the phone resets itself.

I turned on with the volume down button on, and connect to the desktop computer (I use linux with adb and fastboot installed which work perfectly) and enter "fastboot flashing unlock", but it returns

$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.009s

I also tried to enter recovery mode, but it began to splash initial screen on and off again.

How can I recover from this situation?

Thanks in advance!

edit:

"fastboot flash recovery twrp-3.3.0-0-sailfish.img" now returns like this.

$ fastboot flash recover twrp-3*img
Sending 'recover' (31000 KB) OKAY [ 0.892s]
Writing 'recover' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.074s

edit2:

Looks like I unchecked "OEM UNLOCK" in Development Option and locked......can I recover from this?
[Google Pixel Questions & Answers] junglism93:
Have a search using "bricked pixel locked bootloader" and trawl through the threads it throws up for workarounds etc. Some people have had some success depending on what the device was running but it's usually a non recoverable scenario.
[Google Pixel Questions & Answers] maverick6664:
Thanks. I'll give it a try. I'm almost abandoning.....
[Google Pixel Questions & Answers] maverick6664:
I tried it now. Most of the procedures were fine, but the important parts (write .img) failed. I attach the logfile. I abandoned....
[Google Pixel Questions & Answers] matusala:
I am on Android Q beta 5 now and i do not have that option in the development options at all.

I also have Nexus 3, 4 & 5 and i played so much with them i can't even remember. Never had any problems. I have repartitioned them, changed mac addresses and many things but they never bricked. Do i have to worry about google pixel when i'll unlock bootloader? I got it about 3-4 days ago. I thought they are as cool to play with as Nexus 4 & 5 were. Is it not right?
[Google Pixel Questions & Answers] maverick6664:
I've learned. "Don't root. Don't unlock bootloader."
[Google Pixel Questions & Answers] junglism93:
[MENTION=6098003]matusala[/MENTION] you can unlock the bootloader and flash stuff as you did on the nexus line of devices. I'm on Q beta 5 with bl unlocked, I've had lineage running on it for a while and also had magisk etc installed. The key with these pixel A/B slot devices is that your system must be 100% stock before relocking the bootloader. If it is not It will end up bricked as you will no longer have a working boot image or recovery as they are in the same partition. The rule is to never relock the bootloader unless you are 100% sure that your system is 100% back to full stock.

I certainly won't be re locking my bootloader, ever!
[Google Pixel Questions & Answers] matusala:
[MENTION=7191465]junglism93[/MENTION] How did you unlock on Q beta 5? There is no "OEM UNLOCK" option in Development Options in here. Do i have to just run fastboot flashing unlock and that's it?

I know this pixel A/B slot thing. My router has exactly same layout and when i flash system on it i get to choose where to flash. I can have different version in A/B slot of my router. Is on google pixel the same? Do you have to choose which slot to flash? Can you have custom rom on A slot and full stock rom on B slot?
[Google Pixel Questions & Answers] junglism93:
I unlocked my bootloader back on stock pie, i have it on mine but it's greyed out as already unlocked so no idea on that one! My knowledge on A/B slot ain't great, it's just what I've read on here re the pixel bricking scenario so I didn't do the same when I unlocked my bootloader etc. I doubt running a separate ROM on each slot works as when you perform an update it will write to slot a or b (the slot you aren't using) and then hop onto the updated slot upon reboot, alsoif the update borks you can roll back to the previous slot and still have a working system.

That's about as far as my knowledge of it goes mate
[Google Pixel Questions & Answers] TENN3R:
Leaving the bootloader unlocked doesn't void the warranty or things like that, also it's a life saviour if *anything* goes wrong, even with official updates. Why not leaving that on?

The lesson here is not "don't root" or "don't unlock the bootloader", cause with an unlocked bootloader you can recover from pretty any kind of software malfunction.

Unfortunately, with a locked bootloader I've never seen anyone succesfully recover the device, cause you cannot send commands.
[Google Pixel Questions & Answers] maverick6664:
Hmmm......correction.

I would say:

"Root with caution. Otherwise don't root."

Rooting doesn't necessarily cause a trouble. Usually it helps. But my Google Pixel used to show alert screen message upon every boot. It's a bit messy.
[Google Pixel Questions & Answers] matusala:
[MENTION=6223007]TENN3R[/MENTION] I have Android Q beta 5 on my pixel and i can't unlock bootloader. OEM unlock is not in my developer options menu. How can i unlock it's bootloader?

I tried unlocking and now i see that option in developer options, but it's greyed out and i can't press it. What can i do.

It seems these pixel phones are garbage compared to nexus line. Those were so much better!
[Google Pixel Questions & Answers] TENN3R:
I think I read somewhere in the android beta subreddit that is a Q beta related problem, and in Pie should work.

How did you unlock it since it wasn't there? Is the toggle grayed out in "off" position or "on"? Cause if it's enabled than you're ok
[Google Pixel Questions & Answers] matusala:
I followed this guide and it worked. It unlocked my bootloader. https://xdaforums.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030

Now option is greyed out again in "off" position but it says "Bootloader already unlocked"

Maybe i got verizon model but in cell-unlocked state, because seller had written that it's unlocked. He meant provider lock of course.
[Google Pixel Questions & Answers] junglism93:
[MENTION=6098003]matusala[/MENTION] Happy days mate, have fun and remember the first rule of pixel club 'Never re lock the bootloader'
[Google Pixel Questions & Answers] maverick6664:
Good luck [MENTION=6098003]matusala[/MENTION] from me also, and don't give in the first "Don't keep bootloader unlocked' alert screen!! Otherwise you might fall into a bad luck "bricked pixel" like me!
[Google Pixel Questions & Answers] matusala:
[MENTION=7191465]junglism93[/MENTION] [MENTION=8489563]maverick6664[/MENTION]

Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.

P.S.

To check if pixel is verizon version

Download terminal emulator and run

getprop ro.boot.cid

if result is "VZW__001" then it's verizon. My pixel is verizon.
[Google Pixel Questions & Answers] maverick6664:
Nice to hear that. It was a good lesson to me. I have two xperia's (after google pixel dies, I bought one.) Somehow xperia's are not re-lockable. It is also mentioned in Sony Xperia forum. I guess it must be a warning from Sony. :laugh:
[Google Pixel Questions & Answers] maverick6664:
But reading this page, relocking by "adb oem lock" looks safe. At least this is a google's page. Google is responsible for it. And you can avoid the annoying boot message.:laugh:

BTW, "adb oem lock" doesn't work with xperia. Sony seems to like leaving their products unlocked.
[Google Pixel Questions & Answers] matusala:
Do not post things like this cause someone can read and believe you :D Relocking bootloader on verison first gen pixels and on any other gen pixels with not 100% stock image = BRICKED PIXEL :( Do not ever relock your bootloader in any case. Just do not. I asked question to get rid of this warning screen if it can't be done so be it.
[Google Pixel Questions & Answers] maverick6664:
oh, sorry....
[8125, K-JAM, P4300, MDA Vario General] sdnatlst:
hi people.

on odd occasions, getting more and more often, usually once out of three texts this happens.

ill open the screen and as soon as i start typing the screen will get lines down it, become unresponsive and eventually just go white, i just turn the screen on and off and its working again?

this happens with all apps, on different occasions, but as i say usually its once out of 3 times i open it now :(.

sometimes this does it when the xda is closed! although this is more of a rare occurance.

thanks in advance people!.

by the way im running WM6.
[8125, K-JAM, P4300, MDA Vario General] rudolph16:
Hello,

(sry my englisch is not so good)

i have the same problem and a little solution. the flex cable is connected with the keyboard. if you open the keyboard the flex cable is very tight and straight. there are a loose. beecause of this i take a little saw and cut 2cm from the keyboard. the solution is that the cable has more freedom to move up and down. i know, it's difficult to understand. tomorrow i make a photo.

BUT: this method i danger! no gurantee!

Regards rudolph
[8125, K-JAM, P4300, MDA Vario General] atulhyd:
Had the same problem some time back but in reverse. My Wizard would work ok with the keyboard open and vice-versa. Problem is with the ribbon cable connected to the keyboard. Had to get it replaced to resolve. Working great since the cable was changed.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] AccioWombat8705:
I just wanted to know what the approximate image size in MB turns out to be when clicking a photo to help me determine if I should go for the 128 gb or 256 gb version.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] KramYY:
About 11-13 mb
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] AccioWombat8705:
Great, thanks.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] learnerz:
around 20mb
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] archeuscaine:
Hello guys

i have 6/ 128 k 20 pro phone it came to me unlocked and i installed trwp and magisk to it. Took backup and tried to install 10.3.3 globab stable rom but some how i deleted systeam file and coudnt restore either i got backup files whit me but dont know why it gave me error

at this point phone stuck whit fastboot mode no mather what i do trwp cant reacable to nothing happens when i press power and volume up button

as a solution flashing a stock rom whit miflash came in my mind mi flash recoqnises my phone but i dont have any rom to flash whit it if i am not wrong there are three type of roms recovery + fastboot + stock firmware

can anyone could help me to get some rom to flash please? or anything else to solve my problem like i said phone was unlocked its 6/128 model and i got TWRP-3.3.1-0529-REDMI_K20PRO-CN-wzsx150 backup of my phone
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] NXxR:
hey, use miflash, be careful about locking the boot... if you don't want to DON'T LOCK on miflash.

in this link there's plenty of ROM's, choose one for fastboot https://xdaforums.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647

You can also follow the tutorial on that page to install via miflash.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] archeuscaine:
hello guys here i am again :D

got my phone at boot loop again it was unlocked and i tried to install trwp something ****ed up now my phone goes to fastboot mode i tried to install rom whit miflash tool pc detects phone and flash tool works but after many minutes nothing happens my phone is raphelin model india variant

K20 pro 6/128 and i used 64 bit and 32 bit miflashes nothing happens just fastboot mode what can i do any ideas instead of opening phone and shortcut it

here is a ss of miflash tool still waiting but nothing happens
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Antidote03:
dude use latest miflash and select clean all

load it flash it after some time it will show you success with green and it will reboot automatically

if it didnt reboot to recovery actually ( stock recovery ) and perform wipe data

it will solve ur problem
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] bhupesh0143:
my mobile k20 pro stuck in fastboot mode after twrp flash
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Watson96:
Flash vbmeta via terminal.