Related
Even when typing at normal medium speed I find the keyboard will completely ignore/miss a letter or two at fairly regular intervals. I've tried editing the registry to lower the initial delay value down all the way to 1ms, but the issue still occurs. Is there a known cause/fix for this? Thanks...
try either of the last two cabs found here
http://forum.xda-developers.com/showthread.php?t=604831
g2tl said:
try either of the last two cabs found here
http://forum.xda-developers.com/showthread.php?t=604831
Click to expand...
Click to collapse
Thanks.. I took a look and the issue I'm having seems to be a bit different from what those cabs address. Rather than oversensitivity or extra unintended keypresses, my screen/keyboard will semi-frequently (every 20th word or so) just momentarily become unresponsive and completely miss about two letters of keyboard input.
It's like the keyboard just locks up for about half a second and doesn't even display the little popup letters over the keys at all, and when it un-freezes it doesn't "catch up" or realize that two more letters were typed in the meantime. so if you were trying to type the word "keyboard" you would very likely end up with something like "keoard" as the two missing letters are just skipped completely.
Normally the sensitivity of keyboard and touchscreen in general is very very good and I only have to touch very lightly to get a response. 19 times out of 20 this is the case with typing on the keyboard no problem. Just every here and there semi-regularly a couple of letters will invariably get skipped, again without even displaying the popup boxes over the keys, and I'm not even typing particularly quickly either.
Are there any cabs for this issue..?
Just following up to my thread here from almost a year ago. I've tried multiple roms from XDA, as well as registry tweaks and fixes, and still cannot solve the problem. Does anyone NOT experience this problem, ever..? If you don't, could you please tell which ROM you're using, and what (if any) registry edits you've used?
It is completely impossible for me to type any medium-length sentence on my HD2 without at least a couple of letters/keystrokes being missed and ignored entirely. Every time. I'm willing to try anything but I desperatelty need help, as this one glitch renders an amazing high-end smartphone totally unusable for me...
What ROM are you using now? I am running the T-Mobile 3.14 ROM and I have similar priblem with my keyboard but not near as bad as you say you do. I have not tried tbe reviztry tweek hou mentioned previously in this thread.
T-Macgnolia said:
What ROM are you using now? I am running the T-Mobile 3.14 ROM and I have similar priblem with my keyboard but not near as bad as you say you do. I have not tried tbe reviztry tweek hou mentioned previously in this thread.
Click to expand...
Click to collapse
Currently I have Dutty's ROM installed but I've tried multiple other ones including Energy, Elegancia, Laurentius etc, and the problem is always there, so I don't think it's the fault of any of the ROMs. Either I just have a bad unit, or all HD2's do this to some extent and the vast majority of owners just consider it an acceptable quirk and don't bother complaining about it.
The touchscreen on my HD2 is extremely responsive and fast in all other scenarios, and even when typing most of the time, so I dont think it's defective per se. It just seems that with a good degree of regularity the phone/OS decides to completely "pause/freeze" for a half second or so before resuming normal operation. So brief an instant that it isn't noticeable under any other cirumstances except typing on the keyboard, where it's long enough to eat up anywhere between 1-3 keystrokes depending on entry speed.
It's really a shame, because the Leo is in many ways the most powerful, super awesome smartphone I've ever used, but because of this one utterly intolerable bug it sits on my shelf totally unused, currently in favour of my Sony Ericsson Aspen which is far less powerful, but at least reliably useable for typing.
I'd be willing to buy another HD2 if I really thought it was my specific unit that was responsibe, but right now I have no dependable way of knowing that.
Have you tried other keyboard applications?
I found this cab in my sd card.
I remember it worked in my Topaz.
Give it a try.
I will give the cab a shot tonight when I am back at home, thanks. I have indeed tried alternate keyboards such as Resco and a few others, with no change or improvement, so I don't think it's the HTC IME keyboard specifically at fault either. My guess is that the whole screen is becoming unresponsive for that half second or so, not only the keyboard. It's just that it's only noticeable/irritating enough to be an issue when typing, because I have to constantly stop and go back to re-enter letters that were ignored along the way. It's a real dealbreaker for me on an otherwise outstanding device.
Do I take it correctly that you yourself never, ever encounter this issue when typing on your own HD2? Again for the record, it's not a matter of my typing too lightning fast for the Leo to keep up with. Even typing at moderate/regular speed (2-3 letters per second) the missed key issue occurs regularly.
I tried the cab but no luck unfortunately... I really wish I knew whether it was a problem with my specific unit or a model-wide issue that just doesn't get mentioned that often.
Is there anyone reading this, who has an HD2, and does NOT ever encounter this issue of typed letters/keystrokes being missed? Is there anyone out there who can say that their HD2 catches every keypress, every time without fail?
If this is true and applies to you, please respond and let me know! If there are units out there that are totally free of this problem, then I will not give up hope, and will try to replace mine. But I need at least a confirmation or two that some human on the planet somewhere has an HD2 that does not experience this problem...!
I don't know if it the phone, the software or what ,but android keyboard seem to be slow. I have iphone before and any key i press when typing message is not miss. I now have hd2 running android and sometime i type a key it it got miss. Anyone have this experience or away to resolve this?
If it's the same thing I'm thinking about, then it's a Touchscreen problem. Happens when the bus which the TS is on gets gets flooded with commands and causes a temporary slow down. At least.. That's how I've come to understand it.
It's a work in-progress but it might never get solved.
I've noticed this too, mostly if I'm walking outside, turning off the gsensor & auto brightness usually helps,
Try downloading an app called "MySettings" from the market place, there's an option to put an icon in the notification bar to quickly change settings.
Just a possible short term solution till its sorted.
P.s.
This is the wrong section
I think it depends what keyboard you're using and what settings you have.
E.g. using TouchPal without prediction, my HD2 keyboard is as fast as an iPhone.
Using SwiftKey it's slower, but the prediction is very cool.
Using the Android keyboard it's pretty quick, but not quite iPhone quick.
It's worth trying a few to see what works best for you, but know that by using the right keyboard, it can be as quick as the iPhone.
Firstly hello to all my fellow Vega UK users!
For the price I think this device is great, but it does have it's issues.
Do any of you have the problem where the touch screen just seems to stop working? It'll kick in again soon enough, but it's frustrating as hell.
Also sometimes the task manager seems to appear by itself, but I can;t get it to appear when I need it?
I'm using Pauls Add-on ROM. (thanks Paul )
Logicalstep
I havn't had any major lag at all.
What do you mean by task manager? do you mean the one when you hold "home"?
I have found after a lot of use, with a lot of apps open that the system can lag. I guess this is due to system resources. Recommend installing ES Task Manager from the market to manage running tasks.
You mentioned the task manager appears by its self, do you mean the home screen selector? I found hitting the home button to many times makes this display.
Some users have reported issues with the touch system when the tablet is charging. Do these issues only appear when plugged in?
adfrad said:
Some users have reported issues with the touch system when the tablet is charging. Do these issues only appear when plugged in?
Click to expand...
Click to collapse
Yes believe so. due to non regulated power supply causes the screen to become over sensitive.
I get this issue too occasionally, vastly increased when plugged in, now and then when not.
I dont use the machine when its charging.
No real rhyme or reason to it occouring in my experience, id love to know of a cause, other than dirty screen.
Rgds
Lok
Yeah It's a bit of a strange one tbh.
Can;t say I have noticed the lag more when plugged in. I though the PSU was regulated, isn't it just a standard Switch mode PSU?
On the task manager, well obviously there is a task manager with Foryo and oon my Galaxy s I hold the hold button down and it appears, however there doesn;t appear to be a reliable way to do this on the Vega....or am I wrong?
Logicalstep
I never get any touch lag, but I'm not convinced "lag" is the word you want.
"lag" would indicate that the response is somewhat behind the touch action. Android versions below Gingerbread do suffer from that when the CPU is loaded but the Vega is better then most in that regard.
What it does suffer from a _lot_ it erroneous and missing touch events (especially when using a poorly smoothed PSU like the one provided) symptoms include:
1. Swipe gestures being terminated before you lift your finger.
2. Long press actions acting like multiple-presses.
3. (The most common for me) Finger up events failing to register (resulting is erroneous long-presses)
But none of these are "lag". I believe there are grounding problems in the Vega and thus how you hold the tablet and the humidity and static of the environment can change the reliability of the touch screen. It's been reported that having the Vega plugged into a desktop via USB increases the reliability of the display (at least when also charging) which lends credence to the idea that it's grounding related.
What I have noticed ín particular is that holding the tablet in landscape mode makes the keyboard ultra inaccurate. You must press much below the level you want. E.g., if you want to write a Q you hit the A key. It's a bit bothersome while writing...
I haven't experienced any lag, just a slight deadzone at the bottom of the screen and inaccurate keyboard typing. Nothing major. I also haven't really noticed the messed up screen sensitivity when charging that people have been going on about.
Sent from my HTC Desire using Tapatalk
CalumD said:
I haven't experienced any lag, just a slight deadzone at the bottom of the screen and inaccurate keyboard typing. Nothing major. I also haven't really noticed the messed up screen sensitivity when charging that people have been going on about.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Try this out:
http://android.modaco.com/content/advent-vega-vega-modaco-com/327198/screen-calibration-app/
HunteronX said:
Try this out:
http://android.modaco.com/content/advent-vega-vega-modaco-com/327198/screen-calibration-app/
Click to expand...
Click to collapse
I gave if a try, seems to have made typing on the Vega a whole lot better!
Sent from my HTC Desire using Tapatalk
Confirmed over at modaco and by myself also.
Not 100pc improvement but a 90pc. Another essential app.
Goodstuff.
Rgds
Lok
Iv seen lag when I first turn it on but it goes away in couple of minutes, if its on standby it never lags.... cmon honeycomb!!!!
Sent from my HTC Desire using XDA App
The performance pack really reduces start up lag issues btw.
I've seen the device lag sometimes but since i installed pauls peformance pack the lag has gone away making the device so much better.
Well for me the keyboard is still a major issue. Not lag really, but it appears to register my touches multiple times. Right now Im typing this reply on my tablet and I have to go back so many times to correct multiple characters, spaces etc. Its just taking so long and requires so much effort to write a simple message.. for browsing and apps I love it but for email its horrible..
dopeh said:
Well for me the keyboard is still a major issue. Not lag really, but it appears to register my touches multiple times. Right now Im typing this reply on my tablet and I have to go back so many times to correct multiple characters, spaces etc. Its just taking so long and requires so much effort to write a simple message.. for browsing and apps I love it but for email its horrible..
Click to expand...
Click to collapse
Have you tried cleaning your screen and then using the calibration program posted on modaco?
zzleezz said:
Have you tried cleaning your screen and then using the calibration program posted on modaco?
Click to expand...
Click to collapse
Just tried it but doesn't seem to make any difference..
dopeh said:
Just tried it but doesn't seem to make any difference..
Click to expand...
Click to collapse
OK just to be sure...
Is the power supply plugged in? (Screws up the calibration in my experience)
Are you touching the screen while it calibrates?
OK, so here's my problem. I recently returned my nexus 7 for a newer production date build because I had a horrible touch screen. I updated the new one and had missed touches/sticky keys but when I unlocked it to apply sfhub's fix it wiped everything and the problem is gone (maybe a bad upgrade install?) Every once in awhile it feels like it's still missing a touch. Like once every couple hours. I've noticed that the touch screen is very sensitive and if I move my finger a little bit while touching it registers as a swipe I guess. Is there a way to see if it's really not seeing the touch or registering as something different? There are no sticky keys whatsoever and multi-touch seems to work fine in a case or out. Does anyone else see this with theirs?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Enable developer options and see the touches
You can test/verify the touches by enabling the developer options on the Nexus.
To do this, go to settings, go down to "About tablet", and then down again to the build number. Tap the build number information ca. 5 times (5 to 10? after a few taps you will see an info sign about how many times you still have to tap), this enables the developer mode.
In the settings menu there should be now a new item, Developer options (just before the About tablet). In the developer options check the box named "Pointer location".
Now when you touch the screen, with one or more fingers, you can see a screen overlay with coordinates and axles showing where the device sees your touches.
I have the touchscreen problem with missing and sticky touches and pinch and twist problems, the whole menu. For example, using google maps or writing emails is a pain in the ass because of these touchscreen issues.
On my device once I enable the "show the pointer location" -feature, I can clearly see that the device registers the touches right, but it behaves differently from the touches.
According to this I see, at least on my device, this more as a software than a hardware problem, and it looks that the problem is maybe even on a higher API level, which is IMO a good thing, because it _might_ be fixed with a firmware update. The question is, why Google hasn't done this yet, as the issue has been there around the world for a while, and there have already been a couple of updates (Q & R, or even more?) which haven't fixed the problems.
It would be interesting to hear reports of other devices. Test and report!
May82 said:
OK, so here's my problem. I recently returned my nexus 7 for a newer production date build because I had a horrible touch screen. I updated the new one and had missed touches/sticky keys but when I unlocked it to apply sfhub's fix it wiped everything and the problem is gone (maybe a bad upgrade install?) Every once in awhile it feels like it's still missing a touch. Like once every couple hours. I've noticed that the touch screen is very sensitive and if I move my finger a little bit while touching it registers as a swipe I guess. Is there a way to see if it's really not seeing the touch or registering as something different? There are no sticky keys whatsoever and multi-touch seems to work fine in a case or out. Does anyone else see this with theirs?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try playing some heavy multitouch games. I'm playing Terraria. Requires fine motion. You'll notice anything in that game.
Sent from my Nexus 7 using XDA Premium 4 mobile app
kotivalo said:
You can test/verify the touches by enabling the developer options on the Nexus.
To do this, go to settings, go down to "About tablet", and then down again to the build number. Tap the build number information ca. 5 times (5 to 10? after a few taps you will see an info sign about how many times you still have to tap), this enables the developer mode.
In the settings menu there should be now a new item, Developer options (just before the About tablet). In the developer options check the box named "Pointer location".
Now when you touch the screen, with one or more fingers, you can see a screen overlay with coordinates and axles showing where the device sees your touches.
I have the touchscreen problem with missing and sticky touches and pinch and twist problems, the whole menu. For example, using google maps or writing emails is a pain in the ass because of these touchscreen issues.
On my device once I enable the "show the pointer location" -feature, I can clearly see that the device registers the touches right, but it behaves differently from the touches.
According to this I see, at least on my device, this more as a software than a hardware problem, and it looks that the problem is maybe even on a higher API level, which is IMO a good thing, because it _might_ be fixed with a firmware update. The question is, why Google hasn't done this yet, as the issue has been there around the world for a while, and there have already been a couple of updates (Q & R, or even more?) which haven't fixed the problems.
It would be interesting to hear reports of other devices. Test and report!
Click to expand...
Click to collapse
Yeah i feel the same too. I think the problem is software/drivers related than hardware and i dunno if there is a "perfect" device out there at all. I feel many casual users are simply not experiencing it. What i find odd is that, it always feels better after a reboot and things start to deteriorate from there. Almost like memory is not being released properly and there's some stucked process being stacked etc etc. Personally i find that eliminating the use of Chrome entirely has worked better for me. Am using only Dolphin now and it's been going very well so far.
The latest touchmark results shows there is a high latency in the Nexus 7 2013 model. It also indicates that it could be due to frequency of CPU polling for touches with a combination of other things in GPU too. IMO i think the high DPI on the screen and the handling of the quadcore processor might require some tweaking to get it perfect. There seems to be too much latencies and perhaps the missed touches / stuck touches are due to a combination of problems in the code with regards to touch events handling. Oh well, regardless i think they need a taskforce behind it to resolve it.
http://appglimpse.com/blog/touchmarks-ii-touchscreen-latencies-in-flagship-tablets/
lomonic said:
http://appglimpse.com/blog/touchmarks-ii-touchscreen-latencies-in-flagship-tablets/
Click to expand...
Click to collapse
Interesting!
lomonic said:
Yeah i feel the same too. I think the problem is software/drivers related than hardware and i dunno if there is a "perfect" device out there at all. I feel many casual users are simply not experiencing it. What i find odd is that, it always feels better after a reboot and things start to deteriorate from there. Almost like memory is not being released properly and there's some stucked process being stacked etc etc. Personally i find that eliminating the use of Chrome entirely has worked better for me. Am using only Dolphin now and it's been going very well so far.
The latest touchmark results shows there is a high latency in the Nexus 7 2013 model. It also indicates that it could be due to frequency of CPU polling for touches with a combination of other things in GPU too. IMO i think the high DPI on the screen and the handling of the quadcore processor might require some tweaking to get it perfect. There seems to be too much latencies and perhaps the missed touches / stuck touches are due to a combination of problems in the code with regards to touch events handling. Oh well, regardless i think they need a taskforce behind it to resolve it.
Click to expand...
Click to collapse
Thanks lomonic, an interesting link.
I had the former/original Nexus 7 (until my oldest daughter accidentally dropped it in May), and it had no touchscreen issues, at least nothing as bad compared to my new Nexus 7 (2013 model). Yes, it lagged sometimes, as does also my Nexus 4 (mostly noticeable when you slide down the notification menu or open the open applications list), but it had no similar problems with the precision of the touchscreen of the new Nexus 7.
I just tried to reboot the device and also noticed the touchscreen performing a bit better. Though, the problem came back in no time, and after a couple of minutes using Google Maps was the same mess as before. Twisting/rotating the map with two fingers results to pinching/zooming and the map centers somewhere else you want it to. Also in Chrome zooming and scrolling doesn't work as expected, and selecting text is also problematic. Using the keyboard might get you a sticky backspace, which is somewhat annoying. I can only imagine how it would be to try to play touchscreen intensive games, which demand fast and precise touches.
On my Nexus 4 I've also noticed that Chrome seems to slow the whole device, and for this reason I've also been using Dolphin for a while now (but I've yet not deleted Chrome, I just don't use it). Maybe I should dump the whole app from my phone. Also using Clean Master to clean up the memory from apps/processes helps for a while, but only for a while.
Google (or Asus) could verify if there's a sw patch on the way. I'm not a gamer, I mostly use the tablet for surfing and reading, but also these task are not a pleasure with the touchscreen issue. If this problem still persist after a month or so, I really think about returning the device (I bought it just a week ago).
Chrome is super slow.
I don't know why but the stock Android Browser is super fast and awesome. I've been using Next Browser since it is based on Stock Android Browser but the past 2 recent updates have really screwed it up where it is beyond usable. Once it gets resolved, Next is really awesome. It is like Stock on Steroids.
However, regarding touchscreen issues, DON'T GO LOOKING FOR PROBLEMS. If you aren't having issues, then just relax and enjoy your tablet. If your tablet was plagued with a quirky touchscreen driver, then you would notice it. If you can't notice any issues, then you don't have any issues.
Sure there are tests you can run but why bother? It is a software problem and will be fixed eventually. This is not the first Nexus with quirky touchscreen drivers. In fact almost all of my Nexus devices had quirky touchscreen issues out of the box. All were corrected within a few updates. Even the Nexus One had a physical hardware problem with crossing axis that was alleviated using some Google Magic.
May,
I have the exact same issue--but my missed touches are once every 5 minutes--quite annoying when typing an email or typing a password. I haven't unlocked the tablet yet to apply sfhub's fixes--will let you know how it goes.
player911 said:
Chrome is super slow.
I don't know why but the stock Android Browser is super fast and awesome. I've been using Next Browser since it is based on Stock Android Browser but the past 2 recent updates have really screwed it up where it is beyond usable. Once it gets resolved, Next is really awesome. It is like Stock on Steroids.
However, regarding touchscreen issues, DON'T GO LOOKING FOR PROBLEMS. If you aren't having issues, then just relax and enjoy your tablet. If your tablet was plagued with a quirky touchscreen driver, then you would notice it. If you can't notice any issues, then you don't have any issues.
Sure there are tests you can run but why bother? It is a software problem and will be fixed eventually. This is not the first Nexus with quirky touchscreen drivers. In fact almost all of my Nexus devices had quirky touchscreen issues out of the box. All were corrected within a few updates. Even the Nexus One had a physical hardware problem with crossing axis that was alleviated using some Google Magic.
Click to expand...
Click to collapse
Stock android is fast but how do you get it with stock rom? chrome replaces it in 4.3 isnt it? OR are you on a custom?
I think the reality is that many are having problems but do not know about it. They may just dismiss it as not being accurate with their own touches. Also for some users, it could likely be their first touch devices and have no prior experiences to compare with. When i've gotten this device, it was working well and all, but it just feels like typing aint that smooth and slowly over time, the problems starts to be more frequent.
There was an incident i had when after a few days of usage, i tried using it with it lying on the bed and it was going crazy - which never happened before. I picked it up (attempt to earth it) and lay it back down again but the results are the same. So i did a reboot with the system on the bed, and all the problems went away. So i'm not sure it has to do with the earthing factor which many are citing.
I think it is a combination of GPU/CPU/memory and touch related event handling factors that causes the problems to occur more frequently after extensive usage. There should be no reason for hardware to perform perfectly after a reboot only to fail over time.
Oh well, only time will tell when these problems would eventually be addressed.
lomonic said:
Stock android is fast but how do you get it with stock rom? chrome replaces it in 4.3 isnt it? OR are you on a custom?
Click to expand...
Click to collapse
I guess you mean the stock android browser. It may not be available as an app but it's still there as a WebView component available to developers. I guess Dolphin and many other 3rd party browsers are based on the WebView component or on the source code of it.
The problem with the so called stock browser and WebView is that is uses some legacy HTML and JS engine that has not been updated since 2010 or so. That is another crappy developer "feature" from Google that for 3rd party developers there's no "web browser" component that is based on some up to date rendering engine like Chrome's.
In the Themes and Apps thread, there is a method to allow you to install the stock Browser on a stock rom without being rooted.
Also using Sfhub ts10 gave me a 90% fix but it would still spaz out occasionally and would miss touches or click weird stuff. ts20 really fixed me up right. I can play games now and type with no errors.
ts10 is a really good fix, but ts20 really hit it home.
Hi,
I've noticed a UI lag when switching between apps or transitioning from an open app to home screen. This didn't happen in the Android 10 beta rom. Anybody have the same issue? I clean flashed the stable android 10.
I can confirm this issue in the stable release. But I would like to add that this lag was already in the beta release and is in my testing not app specific. I would clear the cache and make a reboot.
Go into developer options and disable the three animation types. Everything runs MUCH faster with them off.
Floridaplur said:
Go into developer options and disable the three animation types. Everything runs MUCH faster with them off.
Click to expand...
Click to collapse
I have, and while it does suppress animations, it actually feels less polished. And anyway, it does not resolve the UI lag which is really visible when using th app switcher. It's dropping below like 10fps. As if some gfx acceleration was disabled or the phone was completely overwhelmed
Anyone found a fix? I experience the lag every once in a while, though it's prevalent enough to be annoying.
I am having this literally every time i use the alt-tab like feature. Oneplus managed to **** up the one thing (butter smooth) Google has been bragging about for several versions ???
A simple fix would be toh format device once, as I have clean flashed and I don't face any lags
Dissable ram boost in system settings
fress said:
Dissable ram boost in system settings
Click to expand...
Click to collapse
I'm having random lag too. I'l try to disable RAM boost and is if it helps.
fress said:
Dissable ram boost in system settings
Click to expand...
Click to collapse
doesn't change a thing. (and am wondering it would. This feature is supposed to make smoothness (even) better, not worse)
Turn off auto brightness .. maybe it can help
I have been reading up on the A10 stable release posts and I saw a lot of people mentioning the issue that you are talking about here.
Many of them suggested a full format. So basically setting up your device as a new device.
I cannot confirm if this works for everyone but a lot of people are saying that after a fresh install they are not facing any issues.
All of the points mentioned above are just what I read from xda and op forum posts. I personally have not made the switch yet and probably wont be doing so soon.
Hey guys. I encountered the same problem on my Nokia 9. Not quite sure why this error doesn't get noticed by more people.
I think I fixed it for me though.
In my case it seemed that the OLED always on screen (which shows notifications and the time) was the problem in my case. It would always show that there are notifications even if there weren't any and that started adding up. So while the rest of my phone ran buttery smooth, the notification bar and lockscreen began looking like a Diashow. 2-5 fps sometimes. What I think is happening is that all these notifications are buggy and the always on screen can't get rid of them.
So my fix was turning that off and then restarting my phone. Since that everything runs smooth again.
If there is another thread I should post this to please tell me but I only found this one.
Hope it helped.
maxsak said:
Hey guys. I encountered the same problem on my Nokia 9. Not quite sure why this error doesn't get noticed by more people.
I think I fixed it for me though.
In my case it seemed that the OLED always on screen (which shows notifications and the time) was the problem in my case. It would always show that there are notifications even if there weren't any and that started adding up. So while the rest of my phone ran buttery smooth, the notification bar and lockscreen began looking like a Diashow. 2-5 fps sometimes. What I think is happening is that all these notifications are buggy and the always on screen can't get rid of them.
So my fix was turning that off and then restarting my phone. Since that everything runs smooth again.
If there is another thread I should post this to please tell me but I only found this one.
Hope it helped.
Click to expand...
Click to collapse
I think the issue is just : it's a ****show of awful coding, optimisation and non-existent testing. If manufacturers' programmers put in half the effort debugging their software we as "powerusers" at xda/reddit/... put twisting our brains in and out trying find correlating explanations and workarounds as to why we get UI lags or other absurd bugs (like 5GHz wifi not working anymore) on the 10th ****ing iteration of Android, we wouldn't have all of this. It all boils down to the general idea that because it is consumer grade product, quality check is just a non-subject. Apparent quality is just enough at product launch, and further updates (if they do get round to releasing them) can brake everything without manufacturers being held accountable.
The update showed up on my phone on the 25th, but, I'm NOT updating. 9 is too damn stable for me, & I don't see any "features" in 10 that will benefit me.
After reading all this i am not going to update to 10. Yet happy with 9.17.
Tmob unbranded dual sim op6t.
Narrowed down some parameters
I have the OnePlus 6, and have similar issues, that include swapping apps being slow, but not just the swapping of apps, any app that has typing in it, seems to DIE when I start typing. Maybe this is a google keyboard issue or something? I notice the issue most in the Microsoft Teams mobile app. It also tends to only happen when at least 2 apps are open, if it's on it's own, it seems to do fine.
This might just be coincidence but I went into dev settings and turned on "strict mode" and now I can't get it to lag like it previously did.
I just looked at my running services (dev options > running services) and saw that my Bluetooth was using 2.2GB of ram, and youtube was 1.7GB of that. I toggled bluetooth off, then back on and it reset this. I have not modified the strict mode setting above... still have not had any lag, will update this thread if I do get more lag.
MightySashiman said:
I think the issue is just : it's a ****show of awful coding, optimisation and non-existent testing. If manufacturers' programmers put in half the effort debugging their software we as "powerusers" at xda/reddit/... put twisting our brains in and out trying find correlating explanations and workarounds as to why we get UI lags or other absurd bugs (like 5GHz wifi not working anymore) on the 10th ****ing iteration of Android, we wouldn't have all of this. It all boils down to the general idea that because it is consumer grade product, quality check is just a non-subject. Apparent quality is just enough at product launch, and further updates (if they do get round to releasing them) can brake everything without manufacturers being held accountable.
Click to expand...
Click to collapse
Lagging issue I've seen many reporting in xda on the stock rom OOS 10.3.0. But 5GHz is working as expected. I can confirm it because I'm using 5GHz WiFI now and then
adondriel said:
I have the OnePlus 6, and have similar issues, that include swapping apps being slow, but not just the swapping of apps, any app that has typing in it, seems to DIE when I start typing. Maybe this is a google keyboard issue or something? I notice the issue most in the Microsoft Teams mobile app. It also tends to only happen when at least 2 apps are open, if it's on it's own, it seems to do fine.
This might just be coincidence but I went into dev settings and turned on "strict mode" and now I can't get it to lag like it previously did.
I just looked at my running services (dev options > running services) and saw that my Bluetooth was using 2.2GB of ram, and youtube was 1.7GB of that. I toggled bluetooth off, then back on and it reset this. I have not modified the strict mode setting above... still have not had any lag, will update this thread if I do get more lag.
Click to expand...
Click to collapse
After a night/day of normal testing with this, where I would normally have issues, I have not had and of the lag I mentioned above. This seems to have fixed some things. So, I would suggest that you first check to see what running processes are using all the ram, and then turn on strict mode in dev settings, if that doesn't solve your issues. I also have Ram Boost option turned off.
I experience the FPS drop quite often after the update. It's especially noticable when scrolling pages, switching between apps, pulling down the upper panel. The slowness seems to disappear temporarily after closing all apps. But I can't say that some particular app causes the lag.
UPD: A simple test to recreate the problem. I push the square button to switch between apps. Start swiping finger left-right and watch the animation smoothness. After 5-10 seconds comes the wave of low FPS, which lasts for a couple of seconds. Then the process repeats. The slowness doesn't seem to depend on some exact apps that are open.
UPD2: Well, I've just found out that the problem isn't constant throughout the day. There must be some connection to applications running in the background or something like this.