Related
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.
It took my a while, but thanks to Wugfresh I was finally able to instal 5.1 on my N6. Curious to know what the general consensus is. I've only had it up and running for 6 hours, but has anyone noticed improvement in battery life or memory management?
Thanks.
When I get it.....
For now still waiting.
Think I will like the change in notifications where I can select WiFi hotspot with going into settings.
The battery life has always been great on 5.01
Read all 4 cores are active but I doubt I will notice.
AstroDigital said:
When I get it.....
For now still waiting.
Think I will like the change in notifications where I can select WiFi hotspot with going into settings.
The battery life has always been great on 5.01
Read all 4 cores are active but I doubt I will notice.
Click to expand...
Click to collapse
Franco's kernel has given my battery some extra life, I hope this update does the same.
I have yet to get the two bugs that were really getting on my nerves previously in 5.0 and 5.0.1
1- Random restarts. They could happen at any time, but it seemed like they would happen when I was trying to text. I'd try to keep closing my text messenger application (happened with both Google Messenger and Hangouts), but it didn't always help. I'd send a text message, put my phone down and then a few seconds later, notice the Google logo because it was restarting.
2- Sometimes when the screen powers up, all I see on my lock screen is a blank black background, the on-screen back button and the usual clock and what not at the top of the phone. Otherwise, the screen itself is black and I'm basically locked out of my phone until I restarted it. If I was lucky and I was using my Bluetooth headset, if I received a phone call, that would sometimes get the phone to snap out of it and allow me to answer the phone call and then when the call was done I'd get the normal lock screen again.
So far so good with 5.1 *knocks on wood*
I just flash it this morning and I feel like im still on 5.0.1. I only use 1 wifi connection and 1 bluetooth connection, so a drop down menu doesn't really effect my daily usage since I don't switch them. Whatever they did behind the hood to improve performance/battery will be nice, but haven't had it installed long enough yet to notice anything different really.
I would also like to know how the 4 cores being force enabled effects the experience before I make the jump.
5.1 is what Lollipop should have been from launch. It's equivalent to Windows 7 replacing Vista. It's that much better.
Sideloaded with adb on my stock att N6. Seems real quick so far. Don't notice any additional drain on battery.
So far it seems about the same as before to me. However, I am on Sprint and the new radio that prevents duplicate texts is awesome so that part of it makes it seem like a new device.
I play Hearthstone, Kingdom Rush and Clash of Clans on My nexus 6 and they all run fine so far.
I did un-encrypt like before. I cannot comment on battery life yet since it hasn't even been 24 hours for me since I updated.
So far so good. Battery life has certainly improved, it was pretty abysmal for me before. I only experienced one bug that I know of on 5.0.1 where occasionally my status bar and nav bar would disappear and the phone was in a partially locked state. Trying to slide down the notification drawer would show the lockscreen. Hopefully that's fixed.
is double tap to wake.. enable in 5.1??
I'm not on a N6 yet, but my GNex is on 5.1, and to compare (because I've only got 1Gb of RAM here, it's a good test because the margins are so small compared to having 3Gb) the 5.1 update is by far the most stable yet for my device. 5.0 was baaad, but consider how many commits corrected memory leaks and you can tell this is the one. I'm looking forward to getting my N6 with 5.1 on it.
Big dialer bug in 5.1. Anyone else getting it?
My screen immediately locks and turns off in the dialer when initiating or answering phone calls. I have no access to onscreen controls until the call is terminated. I cannot hangup, select speakerphone, go to my home screen, etc., until the call ends and Android gives me my screen back.
I'm stock rooted on a 64gb N6 on Verizon. In order to maintain my data and settings I used fastboot to individually flash the new bootloader, radio, system, and boot images.
The same thing happened to an acquaintance of mine who is not rooted and did a fresh install.
Bug reported to Google, ID 160006, if you're interested.
Sent from my Nexus 6 using XDA Free mobile app
I am noticing a huge performance improvement from 5.0.1 already. Battery life is also better. I am not having the dialer issue like some, but have seen 3 instances of people saying the same thing.
Was on stock, now on Vanillipop 1.6 with Franco Kernel r20.
Much smoother and the battery seems improved. Still testing out.
Fly135s said:
Big dialer bug in 5.1. Anyone else getting it?
My screen immediately locks and turns off in the dialer when initiating or answering phone calls. I have no access to onscreen controls until the call is terminated. I cannot hangup, select speakerphone, go to my home screen, etc., until the call ends and Android gives me my screen back.
I'm stock rooted on a 64gb N6 on Verizon. In order to maintain my data and settings I used fastboot to individually flash the new bootloader, radio, system, and boot images.
The same thing happened to an acquaintance of mine who is not rooted and did a fresh install.
Bug reported to Google, ID 160006, if you're interested.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
got a tempered glass protector on it?
Fly135s said:
Big dialer bug in 5.1. Anyone else getting it?
My screen immediately locks and turns off in the dialer when initiating or answering phone calls. I have no access to onscreen controls until the call is terminated. I cannot hangup, select speakerphone, go to my home screen, etc., until the call ends and Android gives me my screen back.
I'm stock rooted on a 64gb N6 on Verizon. In order to maintain my data and settings I used fastboot to individually flash the new bootloader, radio, system, and boot images.
The same thing happened to an acquaintance of mine who is not rooted and did a fresh install.
Bug reported to Google, ID 160006, if you're interested.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Do you use a screen protector that covers the sensor? I know there is a thread somewhere around here with a lot of people that have that issue and it's because of their screen protector in 5.1 for some reason.
jakebites said:
I would also like to know how the 4 cores being force enabled effects the experience before I make the jump.
Click to expand...
Click to collapse
Greatly, its butter all the time.
I haven't noticed a whole lot yet, some games seem to be playing a lot better, the graphical glitch I was seeing on xcom seems to have disappeared so its actually playable now
I've been experiencing an increase in fluidness (is that a word) throughout the UI as a whole, the phone moves from task to task without any stutter and the animations seem to have a bit more polish to them. Checking on the battery now, but I was never a power user to begin with. Overall it may not look like much but you can tell there are some big time enhancements coming from 5.0.1
Hey all,
So I've had my S8 since launch and I've enjoyed it but I have an issue that I've been trying to pinpoint the cause of for a few weeks now. At a high level, if I reboot the phone in the morning, I can use it all day as I wish and it works perfectly, no slowdown anywhere and good battery life. I plug the phone in at night when I go to sleep and when I wake up I start using it again. Either right after I wake up or over the course of a few hours the phone begins to slow down with things like notification shade/app switcher crawling until I either a) reboot or b) change display resolution. Doing either of these "fixes" it until the next night and then again when I wake up I have the same issues.
I've been trying to figure out what's causing this. I've tried disabling features, uninstalling apps, etc.
One thing I have found is that when I'm having this problem if I force close 'System UI' in App Manager (this is just restarting that process since you can't kill it really) the smoothness comes back but it doesn't last as long as when I either reboot or change resolution.
My theory is that something is conflicting with the Android UI and over time it's causing it to slow down. Rebooting or changing display resolution restarts the Android UI so essentially same thing.
My first question is has anyone seen this behavior where the notification shade/app switcher (native UI not apps) slow down? I know there's at least some people on Reddit with same issue. If you have this issue does FC'ing System UI 'fix' it for you temporarily?
I'm trying to figure out what is running on my phone while I'm sleeping at night which is obviously causing this. Any ideas would be helpful. Oh also when I wake up and I go into app switcher it only shows like 3 cards where before I go to bed it would be like 10+ so something is killing apps at night too. I turned off Google backup for today and will reboot before tonight to see if maybe that's it.
Appreciate your help.
Thanks.
I've had my S8+ since the launch weekend on ATT, always connected to my Gear S3, and connected to my Misfit Ray. I've not noticed any slowdown of the UI. My AOD clock is slow to show the hands if the screen is off when I use the numerical clock AOD, but nothing else observed.
I would guess you've installed (or haven't uninstalled/disabled) some apps that are using a lot of background processes. I removed/disabled the few ATT apps on the device except Call Protect, and I don't use Gmail (resource hog). I actually use very few Google apps, they're just not very well coded, it seems (maybe a "goof off" day every week isn't such a great policy?)
In settings, go to Device maintenance, click on battery, and see if anything strange is going on there under App power monitor.
I've NEVER liked Samsung phones, and I've NEVER been interested in owning one, but I saw the Galaxy Gear S3 and fell in love, and truthfully, I bought the phone as an accessory to the watch, so I'm not an apologist for any shortcomings.
Instead of restarting, go to settings/device maintenance, what's the percentage here? go to optimize, does it help? which apps use the battery most? How much RAM is available. If nothing shows up, you probably would need something like wakelock detector (it needs root) to trace apps usage, especially at night. Also you could try to force stop other apps and see which one is interfering? For example phone is slow, force stop first 10 apps, if not fixed force stop next 10, if fixed, next time force stop one at the time from that batch of tens.
Mines just started doing this the other day. I think I have an idea if the problem, I'm just trying to find proof at this point. I recently downloaded this all to let me see the upload/download speeds if my network in the notification bar. It lets you set the refresh rate, to which I set it to 2 seconds, which I knew regardless would tax my system, I just didn't expect my ui to slow to a crawl.
Delete any Bixby remapping app as well, known to cause many issues including unpredictable lag.
Last night I got one of those cheap Chinese smartwatches for $40 locally. (Amazon seems to have some for $20 at amzn.to/2qpSftK) Yeah I know, I know, but I work at a job that is anal about cell phones (a major gripe of mine the way places can be that way) and I need to know if my child's ride at school doesn't show up or if school lets out early due to a power outage etc, if that happens then I HAVE to pause what I'm doing and make a call or two to make pickup arrangements or else it's a legal issue of child abandonment. Such may only happen 2-3 times an entire school year, but it has happened a few times--my mother-in-law's battery was dead and she was running late, or she couldn't find her keys etc--in such cases I had to track down someone locally and get them to step-in, last minute.
Thus, I need a smartwatch which can relay calls which have come in so I can see them and it also needs to push SMS messages and let me reply to them, that way without even pulling my phone out of my pocket I will know if this has occurred (and can quickly reply to SMS) but I can otherwise keep my phone in my pocket knowing beyond any shadow of a doubt that if a call or SMS has come in, this watch WILL pick it up and I WILL be able to reply to them.
This watch I got, it is fine with relaying phone calls and it even relayed the audio from a YouTube video I was watching on the phone itself, but it WILL NOT WORK with relaying SMS. At first it did, such requires installing a "BT Notifier" on the phone (which is the best?) but even then it was hit or miss, and then it just stopped. I've done EVERYTHING in terms of different BT Notifier apps, I even scanned the "OCR Code" or whatever to point to the BT Notifier specific to that model (it appears to be a GT08 type, with the "fan" style of icons, menu/phone on the bottom left and names/text on the right, this YouTube video Ksy0pd-12BI shows one like it), I set that app up--no matter, IT WILL NOT push SMS to this smartwatch, no way/no how.
Is this a common occurrence with such smartwatches? Is this a case of that I'm going to have to just accept this model CANNOT handle SMS no matter what and get something else, vs being able to actually fix this? One model I had read good things about in an article (BIT and 2lTVoxg) called the OUMAX Bluetooth Smart Watch S6 for around $50, this model looked like a good one because it downplays "fitness" features I do not at all need and instead stresses pushing smartphone notifications and being able to replay to them, which is what I DO need. I started to get it on Amazon but then it would've required several days to get here and I need something up & running quickly but without spending $250. Maybe I should've just gotten that and waited?
Tips in general?
If anyone has any tips please do reply, I am only say this because I have an update but that doesn't mean I am not still looking for help.
I've somehow got it working just fine, no timing out of connectivity or any such thing. I had saved the downloaded BT Notifier .apk file from the app it referenced in the barcode I scanned, and I tried again but this time I disabled an app I've used on the phone for a long time--NoLED, which displays a moving dot on the LCD when notifications arrive, making it unnecessary to "wake up" the phone to see missed calls etc. I've used that app for forever, it's a long-time staple of mine, but I wondered if it was possibly interfering with this process.
I'm not sure if that is the case, but since disabling it (but also turning the watch off and letting it charge to full overnight) it's working great today. I possibly could get beyond that eventually but for now I'll take it, I mean having a smartwatch does somewhat make it less necessary anyway. The only issue now--the band, it won't attach and it's apparently a permanent part of the watch's structure, not easily swapped out. I'm not sure how I'll get around that, maybe stitching another watch band on top of it using a sewing kit?
Ultimate Fix: Watch-Specific App/Disable/Install 3rd Party
I'm somewhat disappointed in the lack of replies. Is this because this watch is now perhaps an older model, or what is the reason?
In any case, I now have the ultimate fix.
It's 3 things:
(1) Install the watch-specific app by scanning the QR code and "sideloading" the app
(2) "Force Stop" this app in Google settings but DO NOT uninstall it, leave it installed.
(3) Install the 3rd party app by "Shenznen Fan Yun Technology Co, Ltd" (green background, white circle with exclamation point) then under the "Accessibility" enable the second "BT Notifications" entry, leave the 1st one at OFF
When I got this watch, the first thing I did was download that 3rd party app, it worked some but not consistently, then it totally stopped. I then stumbled across the QR code in the watch, scanned it, installed that app, and that worked--but that app was FULL of adware, constantly bugging me to install this app or that, launching a new tab and page in my Chrome browser, and just being a total pain. I was glad the watch worked, but hated that behavior--so much I disabled the app, figuring I'd just have to re-enable it when the watch was being used.
On a hunch, eager to try again, with the watch-specific app still disabled, I downloaded the 3rd party "Shenznen Fan Yun Technology Co, Ltd" app and, just totally guessing, under "accessibility" enabled the 2nd entry (both entries have identical names so you can't tell which is which), but didn't uninstall the watch-specific app only because I figured that I would end up having to revert back to it anyway.
To my surprise, this has worked. It seems to require me turning the watch off and connecting through the watch initially, but however I get a connection and the SMS message log on the phone populates on the watch, at that point it is stable and reliable from that point on. I had it running today all-day and was receiving texts and the inbox was coming up reliably.
I hope this helps somebody. (Note: this watch is still being sold as eBay item #381686066028.)
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.