yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] Jokenr:
after trying install cyanogenmod my phone doesn t work ... i try to install it with twrp and when it boot up appears the classic logo cyanogenmod an then a image blue with teamwin an restart for infinit ... when i try to connect to odin don t connect and say usb device not recognized or device may not be working properly... i want so much that phone back ....someone can help me ?
[Samsung Galaxy S7 Edge Questions and Answers] bulutbeyaz:
I want to see only new text messages not previous unreaded messages in the lock screen. Is it possible to do that? When I get a message all of the previous unreded messages shown with new messege its really frusturating.
[Essential Phone Guides, News, & Discussion] Scrappy1:
Here's what I've found related to slow scrolling jitter and the touchscreen. When you first open an app, the very first couple slow scrolling swipes produce very smooth screen animation. It will then get jittery but if you exit the app, then reopen, the smoothness will return. Do this experiment in Contacts app to see what I mean.

Now I found this app called "Touch MultiTest" which reads out the touchscreen sample rate as you move your finger on the screen. When you first open it and do a swipe, you see smooth tracking and a solid sample rate reported greater than 120 Hz. However after a couple swipes the dot response becomes jittery and sample rate drops to something around 100 Hz. Closing and reopening the app gets you back to 120 Hz.

So I think this proves the hardware and software touch loop can produce smooth motion, and it's really sampling at 120 Hz. The big question is what exactly degrades after a couple swipes. In the best case it's some driver or software buffer / interrupt handling that degrades. In the worst case it's related to low level hardware issues. I'm hopeful it's software related. By the way somehow Chrome browser always scrolls smoothly with slow swipes. What is Chrome doing differently than all other apps? Just filtering?
[Essential Phone Guides, News, & Discussion] Charkatak:
Have you tried contacting Essential or possibly using their beta feedback form to tell them about your theory/findings?
[Essential Phone Guides, News, & Discussion] ChronoReverse:
Our screens sample at 60Hz. We already know this from the AMA's on Reddit. The test app you're using is inaccurate if it reads 120Hz or even 100Hz.

60Hz sampling in of itself shouldn't be a problem either since iPhones (except for the newest ones) sample at 60Hz and everyone knows how smooth they are.

Hopefully there's not some other hardware flaw and it's just Essential's software.
[Essential Phone Guides, News, & Discussion] Scrappy1:
I don't put much stock in the AMA response since its so vague and nonspecific and could be referring to screen refresh rate (60 Hz) either intentionally or accidentally.

If new iPads and iPhones sample at 120 Hz, it's entirely possible essential panel is sampling at 120 Hz.
[Essential Phone Guides, News, & Discussion] ChronoReverse:
Try using Touchscreen Benchmark to test and you'll be able to verify the actual samples per second. As a point of comparison, the Galaxy S4 samples at 90Hz and the Shield tablet does a whopping 180Hz!

In any case, it's easy to see that it's not refreshing at 100Hz or 120Hz simply by looking at the number of touch samples that actually appear on the screen. Try it on a faster phone and you can see the higher density of touch responses.

Furthermore, you can't reliably discern the sample rate in the first second so trusting the app saying it's 120Hz and dips to 100Hz is even less reliable than the AMA.
[Essential Phone Guides, News, & Discussion] Scrappy1:
I invite anyone to do my test and decide for themselves or measure and produce new data. That's what I'm going for here. Not regurgitation of bland statements.
[Essential Phone Guides, News, & Discussion] ChronoReverse:
I just invited you to use a different test instead of relying on one that doesn't spit out reasonable numbers.

Does it make more sense that the Essential potentially is using a 120Hz touchscreen which Essential won't confirm despite it being a feather in their caps (since even iPhones only got 120Hz recently) or does it make more sense that Essential is using a slower than average (for Android) panel which their software isn't filtering out as well as Apple's software does? Which is more likely to cause jitter and touch latency?
[Essential Phone Guides, News, & Discussion] rignfool:
It's actually that your misunderstanding terminology...

Your mistaking sample rate and refresh rate...

Refresh rate is how many times per second? the screen is redrawn...

Sample rate is how many times per second? the screen reads touches...
[Essential Phone Guides, News, & Discussion] LNJ:
No way you can tell the difference between 120hz vs 100hz.
[Essential Phone Guides, News, & Discussion] ChronoReverse:
No, I'm referring to the touchscreen. Obviously the Essential LCD only refreshes at 60Hz (only the Razer and iPad Pro refreshes at 120Hz) but the touchscreen also samples at 60Hz which is common for lower end Androids (90Hz and 120Hz are the other common sampling rates found in Android devices).

The new iPhone X's OLED still refreshes at 60Hz but has a 120Hz sampling touchscreen which is higher than the 60Hz it used to be in other iOS devices (except for the iPad Pro). I also mentioned the Shield tablet sampling at 180Hz and there's no mobile device with a screen refresh that fast either.
[Essential Phone Guides, News, & Discussion] Scrappy1:
The drop to 100 Hz after a couple of seconds is "indicative of the problem", not that a 100 Hz rate would not be smooth in a properly designed device. Something comes unhinged at the point we see the drop to 100 Hz. Could be touch buffer / event que is not being serviced fast enough due to low level driver or hardware. Also could be some piece of software in critical path starts consuming more time than allowed, leading to non uniform response. Could be actual stuttering of hardware.

When you exit and then restart an app, the touch event pipleline is flushed, so things are fixed again for a couple of seconds.
[Essential Phone Guides, News, & Discussion] mhajii210:
YouTube app

I have noticed that if you launch the camera and then open the YouTube app or whatever you're using where you can see the touch scrolling jitters, the touch scrolling is nice and smooth. Then after some time it comes back. The touch scrolling in Chrome is perfect and I wish it was the same everywhere. For some reason the YouTube app performs the worst for me. Chrome must have received an update a while back since I used to get bad touch scrolling on that too. The thing that worries me is some claim touch scrolling is perfectly smooth on their device. Hopefully that's a case of them not noticing it and not a case of actual hardware differences.
[Essential Phone Guides, News, & Discussion] Scrappy1:
Cool tip! I hadn't noticed that. Opening camera then switching to contacts had me scrolling smooth for many minutes. However after a few rounds of tests it lost the magic. I could no longer use camera open first to produce the smooth scrolling. So there are several factors at play here and this could use more investigation. Most of all though this gives me hope the issue can be totally fixed in software.
[Essential Phone Guides, News, & Discussion] Scrappy1:
I'm starting to think the thing that goes bad and causes choppiness is the rendering pipeline. I enabled "Profile GPU Rendering" and then did a screen capture after scrolling my battery stats in settings for both 1) good condition just after launching settings when scrolling is smooth and 2) bad condition that kicks in after a few seconds when things get choppy. The bad condition shows vastly inflated rendering time which blows the 60 FPS (green line) budget. The largest increase is in red (command issue), but EVERYTHING is inflated in the bad condition. What could cause this?

The captures of the good and bad conditions are attached.
[Essential Phone Guides, News, & Discussion] Scrappy1:
Turns out the reason the rendering pipeline starts taking so long is due to the application thread moving from high performance CPU cluster to the low performance CPU cluster. Using the paid version of System Monitor I opened a floating window of CPU load and freq. I then again opened battery settings and scrolled around in the good and bad state. I can see the CPU load is on the high performance cluster right away (5-8) and those guys are running at 2.4 GHz. Hence everything is smooth. When the jitters set in, the load has moved to low performance cluster (1-4) and they are running much lower clock rate < 1 GHz. I do believe this is probably fairly normal android behavior, but it's obviously tied to the slow scrolling jitters for us. It could be a subtle governor or big.LITTLE thread scheduling issue somehow playing into touch screen weirdness I suppose.

The two captures attached show the issue. One was captured right after launching battery settings when things are smooth and CPUs 5-8 are screaming. Other was captured after things went jittery, and here you can see CPU load that was on 5-8 has moved to 1-4, and clock frequency is much lower. (Hovers between 300 - 1000 Mhz)
[Essential Phone Guides, News, & Discussion] rignfool:
Let's try this

[MENTION=5169465]DespairFactor[/MENTION]
[Essential Phone Guides, News, & Discussion] mhajii210:
GPU governor

Well I can tell you it's not all because of the CPU performance since setting GPU governor to performance on Oreo beta 2 completely gets rid of the touch screen jitters for me. I'm running Oreo beta 2, Rey.R3 Kernel and Magisk 15.2. Using EX Kernel Manager to set GPU governor to performance, I have eliminated the touch scrolling microstutters. Try it out for yourself and see! I also set CPU governor to conservative to compensate for the slightly increased battery usage. Phone is blazing now. https://xdaforums.com/essential-phone/development/kernel-rey-kernel-t3723601 is the link to the kernel.
[Essential Phone Guides, News, & Discussion] Scrappy1:
Thanks for your input! I would go down the root and tweaks path if I didn't have to use my phone for work with the Google device policy and all. Hoping for some jitter improvement in next official stock update.
[Essential Phone Guides, News, & Discussion] DespairFactor:
I think we can move the touchscreen to it's own workqueue, but not sure if it'll handle this.
[Essential Phone Guides, News, & Discussion] Hung0702:
Post a video. In all likelihood, it's just placebo effect. I've heard time and time again people claiming that that the slow-scrolling stutter is gone. It's never once been proven. Here's a side-by-side comparison vs the Pixel XL.
[Essential Phone Guides, News, & Discussion] mhajii210:
https://www.reddit.com/r/essential/comments/7pemou/the_touch_latency_issue_may_be_related_to_the/

See that link for more information. It's VERY difficult to capture the microstutters on video. I honestly can't see that much of a difference on the video you posted. You'd have to try it out for yourself and test. Changing the GPU governor setting has dramatically improved the touch scrolling on my device. Others are finding that out too. See the Reddit link I posted and read for yourself.
[Essential Phone Guides, News, & Discussion] Hung0702:
If you earnestly feel this way, then your testimony is unreliable. The video I posted isn't even a great example, but it's still quite obvious.
[Essential Phone Guides, News, & Discussion] mhajii210:
The good news is the final Oreo build is supposed to include panel / digitizer software improvements. If you don't care to root, I would honestly just wait a little while longer. At least for me personally, I know that if Essential doesn't address it to my liking, I know what to tweak to improve the touch performance on my own. This was the only reason I rooted my device... to test different GPU governor settings.
[Essential Phone Guides, News, & Discussion] Tech_Savvy:
Look it this.... https://www.reddit.com/r/essential/comments/7pemou/the_touch_latency_issue_may_be_related_to_the/
[Essential Phone Guides, News, & Discussion] i killed tupac:
I think it's hardware too. The panels on the ones I had were not flat. They were wavy, like lumpy adhesive. Just a little bit, you could see it in light reflections. Kind of like the screen was ..5 mm too long so it wrinkled. That bending has to to cause some issues.

Play yours in the light and I bet you that your screen is not flat.
[Essential Phone Guides, News, & Discussion] reverenddak:
My girlfriend has a Pixel XL (v1), and I see NO difference in touch screen response. But I'm OLD, and some of you younger folks may VERY WELL see a stutter or difference. So I'm not going to *declare* that there isn't a problem, but I will say that the problem isn't as big as some may think.

FYI, professional baseball hitters can see the stitches on a fastball. You can write a number on a ball, and throw it, and a professional athlete can read it, while the average person would see a blur.
[Essential Phone Guides, News, & Discussion] Airwolf79:
LMAO, yeah and professional groomers can see fleas on a dog's ass from 100 yards. Please don't take me seriously.

It is possible that not every device experiences this though, but the majority of us do notice the lag and it drives some of us crazy. I just don't get how they could mess this up. Hell, my HTC Evo had better touch response back in 2010.
[Essential Phone Guides, News, & Discussion] reverenddak:
I don't doubt that it exists, and I can _maybe_ see it? But it's not so severe that its a deal breaker. It doesn't bother me one bit, and I bet the *majority* doesn't even notice it.
[Essential Phone Guides, News, & Discussion] mhajii210:
I would have to agree with you. The majority probably could care less and probably doesn't even notice. I wish I was part of that crowd but I have bad OCD with this kind of stuff and I unfortunately noticed it right away. I've been tolerating it and waiting for Essential to finally address it. Now we'll have to wait until Oreo 8.1 release. Who knows when that will happen. It's definitely a minor issue, it's just some people are more sensitive to it than others.
[Essential Phone Guides, News, & Discussion] Rahuuler:
No way I would have done a benchmark test to see the compatibility of the phone. And I think 120Hz is the standard frequency for screening response.
[Xiaomi Mi Max Questions & Answers] barro32:
I accidentally ordered a Mi Max 2 screen from Aliexpress, it's probably going to take a few weeks to arrive so not sure if I should wait and try to see if it fits or just order the right screen.

Anyone know if the Mi Max 2 screen will work with my Mi Max 1??
[JAMin, XDA Neo, S200 ROM Development] ycimpir:
Solution changed !

Please read message nr.15 on the next page..

Old solution from me..

- Run any Registry Editor..

- Go to this key listed below

- Change dword value 1 --> 0 in SMSAvailable

HKEY_CURRENT_USER\Software\Microsoft\Inbox\Settings

SMSAvailable = 0 (dword)

Regards :D
[JAMin, XDA Neo, S200 ROM Development] euro_silvertop:
whenever i do this the new message alert tone is also disabled. i don't know why but the sound tone settings is unchanged. :confused:
[JAMin, XDA Neo, S200 ROM Development] a2525:
yaya.i also face same problem .anyone noe how to solve it.pls help
[JAMin, XDA Neo, S200 ROM Development] Sam Trevi:
wow, you've discovered something that the whole forum knew from ages...:rolleyes:
[JAMin, XDA Neo, S200 ROM Development] ziadah:
I got the same problem
[JAMin, XDA Neo, S200 ROM Development] ziadah:
If you have already done this :

"HKEY_CURRENT_USER\Software\Microsoft\Inbox\Settings\SMSAvailable

Change dword value from 1 to 0 "

you will have to turn back the SMSAvailable dword from 0 to 1 (its orgiginal alue)

then

create a folder named OEM in HKEY_CURRENT_USER\Software\Microsoft\Inbox\Settings

Then in the new named OEM folder, create a DWORD key called

SMSInboxThreadingDisabled

with a value of 1

and this works, I tried it!
[JAMin, XDA Neo, S200 ROM Development] alien6:
FINALLY !

it really works - without disabling sms sound

thank you, I've been waiting for it for so long
[JAMin, XDA Neo, S200 ROM Development] JOKERz:
let me try it :)

yupz it workz thankz alotz!!
[JAMin, XDA Neo, S200 ROM Development] zoghal:
very very tnx
[JAMin, XDA Neo, S200 ROM Development] rondol1:
@ ziadah:

This is realy good information. We should sticky it some how.
[JAMin, XDA Neo, S200 ROM Development] Sam Trevi:
Now thats what I call something great!
[JAMin, XDA Neo, S200 ROM Development] zoghal:
oh

i changed, but sms sound is disabled

plz help me
[JAMin, XDA Neo, S200 ROM Development] rondol1:
How did you do that? DON'T use the regsetting described in the FIRST post, but try the one in post SIX (6).
[JAMin, XDA Neo, S200 ROM Development] d1srupt3r:
The post6 and it works but the vibrate has gone when receiving new sms even though I put a check in the Sounds & Notifications?

PS:

I found the fix.

Please follow this step.

You shouldn't follow the step 1 in post 6 of this thread which is changing the value of HKEY_CURRENT_USER\Software\Microsoft\Inbox\Settin gs\SMSAvailable into 0, it should be remained as its default which is 1.
[JAMin, XDA Neo, S200 ROM Development] a2525:
using tis cab tat i make
[JAMin, XDA Neo, S200 ROM Development] euro_silvertop:
thanks! this helped a lot.
[JAMin, XDA Neo, S200 ROM Development] rondol1:
That is exactly what it says, you have to read carefully when you fool around with your regsettings:
[JAMin, XDA Neo, S200 ROM Development] scorpion_hmto:
great !!!! thanks
[JAMin, XDA Neo, S200 ROM Development] alien6:
Just delete the first message in this topic to avoid confusing users

or write there's better method (then that previously known) few posts later
[JAMin, XDA Neo, S200 ROM Development] rondol1:
I agree, but it has to be done by the topic-starter...
[JAMin, XDA Neo, S200 ROM Development] New User:
thaaaanks alot,,,
[JAMin, XDA Neo, S200 ROM Development] varanusvincent:
use this two cabs.

first disable threading message

second enable sms notification
[JAMin, XDA Neo, S200 ROM Development] PPC-Warrior:
===============

CONFIRMED TO WORK ON THE NEW HTC DIAMOND

===============

I was stupid enough to create the entry under HKLM instead of HKCU.

But it works now! Great find! Thanks!
[JAMin, XDA Neo, S200 ROM Development] mahesham22:
This worked for me

This solution worked for me great, i m so glad, I can create folders, move massage to other folder and even foreword them..
[JAMin, XDA Neo, S200 ROM Development] Tecchie1:
Now, say if I wanted to ENABLE conversation view on a 8125, how would I go about doing that? Because I like the Conversation View..... so does my wife, we have two 8125's, one is ATT, the other is T-Mobile, both are unlocked and flashed to WM6.1 Rom

Thanks guys!!!!
[JAMin, XDA Neo, S200 ROM Development] vindybaba:
Cannot read conversation

Hi,

I am new to this forum. I have an Imate PDAL. I flashed the rom provided on this site to 6.1 and it is awesome. Just that I booked some tickets and got an sms for the same. My mobile was treating that sms as a conversation now, and I wasnt able to read anything when I opened the message. So basically conversation view seems to not be working. I will use this to disable that feature. Any idea how to make it work?
[JAMin, XDA Neo, S200 ROM Development] vindybaba:
How to make conversation work

Hi,

Now, with this registry settings, my conversation view is disabled and I am able to read my sms. That is good. But how do I make my conversation view work. if I just change the registry the conversation view gets enabled, but when I click on a conversation, They textkeypad comes and I am not able to see anything in the threaded conversation. I have flashed my cellphone with the 6.1 ROM provided by Cell Smith in the same forum.

original - windows mobile 5 imate pdal

new flashed ROM. I like this 6.1 - can anyone help me get the conversation to work?
[K3 Note Q&A, Help & Troubleshooting] Rockstar.garvit:
here's what happend

I have flashed Unofficial RR rom . It was charging regularly.

Then i flashed renice kernel.

Sometimes Phone was charging relatively slowly but then it fixes by itself .

Until recently it was occurring more and more.

NOW it charges verrrrry slowly 7 8 hours and not reaching 100%, still at 60%!!

So i decided to flash Ultimate kernel to see if anything happends..

no luck

I think somehow the kernal changed the charging voltage. or It may be that battery needs to be replaced..

How do i diagnose what the problem is ??

p.s. I have tried calibrating battery multiple times both by app and manually. Also tried multiple chargers and charging cable. Even tried to charge via pc.
[K3 Note Q&A, Help & Troubleshooting] Clintopuli:
Mr RR 5.8.3 is having very slow charging what can I do plz give me an answer....
[K3 Note Q&A, Help & Troubleshooting] :
Provide a log cat or flash new ROM some times system uses too much bettery try any latest ROM it should be fine
[K3 Note Q&A, Help & Troubleshooting] LLoTE:
If the rom was not charging above 60% you should just restart the phone with a charger on and it will just jump to a 100 it's not calibrated well calibration apps don't work
[K3 Note Q&A, Help & Troubleshooting] swapswapswap:
Same problem.....after the first charge after fresh flash....takes me around 10-12 hours to full charge even with a proper dock and cable.....if I use the device while charging then the charge gradually decreases...

Help plox....
[K3 Note Q&A, Help & Troubleshooting] :
Which ROM ?try changing kernel there are some pretty bad slow kernal
[K3 Note Q&A, Help & Troubleshooting] swapswapswap:
Resurrecrion remix 5.8.4........I also tried 4 different kernels....ultimate overclocked,ultimate,renice,lightning over clocked............ultimate over clocked seemed to work fine but after some days the same problem started since then none of the kernels worked....
[K3 Note Q&A, Help & Troubleshooting] :
I know that's the problem of the ROM I also experienced the same problem on that ROM change it to dot os with venom kernel 3 hour of screen on time while playing pubg mobile and if you want you can push it to 4to 5hour (venom kernel has built in fast charging 2 to 3 hour max from 0) if you didn't enable fast charging 4 hour max good luck
[Huawei Mate 10  Questions & Answers] salespalace:
Hi guys,

If I rebrand my chinese variant of the mate 10 6gb 128gb version to the EU c432 variant, will the 6gb ram and 128gb storage still be usable?

Thanks for heads up
[Huawei Mate 10  Questions & Answers] gm007:
Sure.
[Huawei Mate 10  Questions & Answers] salespalace:
cheers, rebranding was quick, much quicker than anticipated.
[Huawei Mate 10  Questions & Answers] tsiglas:
I want to rebrand too my china versio mate 10 to European version...can you tell as what procedure you follow to rebranding????thanks
[General Questions and Answers] romeoDXD:
First of all my phone is j700f Globe version here in philiplinesthen i tried to install any kind of custom rom through TWRP based on my phone like enigma, xperience Os etc. I download everything and follow the steps correctly but it stuck in bootloop Guys please help What should i do thanks in advance :good: :)
[General Questions and Answers] Gabzz054:
Hey guys, I need a little help. First apologize my english. So.. To my problem..

I have Video DownloadHelper in Firefox (on notebook) and I use it to find full url of streaming video and then use the url in vlc player. And my problem is that I need an android app, which can do the same like Video DownloadHelper (show me full url adress of streaming video). The addons doesn't work in firefox in my phone so I'm looking for some app which can do it. Any ideas??

Thank you for replies :)

Have a nice day :)
[General Questions and Answers] pdppdp:
Try via browser.
[General Questions and Answers] Gabzz054:
Can you be more specific? When I copy the browser url, it wont play because it is no full url which I can get only in firefox using that app but I need something in my phone. Got it? :)
[Moto G5 Plus Themes, Apps, and Mods] chitshiv:
Trevolve Bootanimation For Android

Mod Edit​