Related
I have been on the fence for this ever since it has been out. I have been to bestbuy and verizon to test out the demo units multiple times and both units seem to have the same issue.
When I open some apps, say dolphin hd for example, I can see screen artifacts for a second. Like colored dashes of varying lengths, and this seems to happen often.
Second, when I am trying to pinch and zoom or scroll in Dolphin, it jerky and spastic, there was one other app that did this as well but I can remember which one. The scrolling on the stock browser seems ok but not the best.
Anyway, do any of you see this? More than likely a software fix, but hey, you never know.
And a rant, who on earth thought of that flimsy power adapter, good grief, they were both broken and the two stores when I first went to look but have since been replaced. And the power button? I have to turn it over to find it.....
Rant off and hoping to fall of the fence.....
Matt
The power button is actually placed well I think. It's not in the way and not hard to get to. I rarely have my device on a table cause of the viewing so it's not a hassle. Also I have not experienced that with dolphin HD on my device.
It's a Dolphin HD problem.
The stock browser rocks.
I haven't noticed any screen artifacts on my display whatsoever. For the most part I disregard demo displays in any store, as you have thousands of people with their hands all over it and the mentality of "Its not mine, what do I care?". God only knows what was done to the demo units.
I have not used Dolphin HD browser at all, so I can't comment on that, i'll try and download it today and give you another reply. The android browser pinch to zoom works damn near flawlessly for me.
As for the power cable, yes I was a little weary of it and the size. But since the battery lasts for quite awhile on this thing, I just plug it in on my nightstand and it lasts me through the day.
My typical uses through the day are music, browsing the internet on breaks, work e-mail, picture management, and work e-mail (exchange push). I start work at about 8 o cloak and am usually done around 6. During this time theres constant use of e-mail and music, and when the day is finished I am around 35%-50% on battery depending on how the day has gone. When I am home, its light browsing and maybe a game for awhile.
The power adapter could become an issue if you plan on having it travel with you constantly, but in a fixed location for charging and nothing disturbing it, its not so much of an issue.
Are you seeing the artifacts? It is like a blip and then the app starts.
I know what you're talking about... but it only occurs for me with Dolphin. I used to use that as my main browser and pinch/zoom when it would try to reload the text/images it would be very jittery.
Again though it's the apps issue not the tablet or honeycomb.
I just had to change the default browser to load as a desktop and not as a mobile device.
i know this probably a common excuse, but HD Dolphin isnt made for honeycomb. Dolphin is making a tablet specific browser and hopefully it'll be release soon. i have both installed just to keep my browser option open.
as for the power button, i think it's the best place. what you dont release from the demo unit is that when actually have in your hands, it's completely different. if the power button was along the side anywhere, it could be easily hit. especially laying down it on it side or even having it in a tablet stand. i even have some issues with the volume button when i place it in my tablet stand.
besides all that, i contact Quickoffice and asked about whether they're developing a Honeycomb specific Quickoffice with editing and making new documents. they said yes
I use the stock browser with no problems.I don't see why they had Dolphin browser on the Xoom anyway because its not designed for honeycomb & furthermore those demo units are no way to judge the Xoom anyway.People push everything in sight on them & mess them up anyway.
I'm surprised they don't perform a reset every once in a while to clear up the device of any hangups.
Though I guess it makes for a pretty good stress test to see if it can handle anything that is thrown at it.
Mooem7 said:
I'm surprised they don't perform a reset every once in a while to clear up the device of any hangups.
Though I guess it makes for a pretty good stress test to see if it can handle anything that is thrown at it.
Click to expand...
Click to collapse
yeah I put all kind of stuff on there testing stuff I read here.
Launcherpro
dolphin
spareparts
asee ( app i use for my home dvr)
The verizon store also had an ipad right next to it, and I do have an ipad now, but love my Droidx.
the other thing I seem to notice is that the colors are a little washed out on the xoom compared to the ipad and the ipad is much brighter, but that always is best especially late at night in the bed. The ipad is to brit on tne dimmest setting.
Man i just cant decide to drop the dough....
not the kinda thing i want to write up first thing in the morning but i want to see if i'm alone here or if these are release wide bugs in which case hopefully asus will fix them.
for some perspective, i have a galaxy nexus and that does not have any of these issues.
Gallery: i downloaded a few files off of the internet and then never showed up in the browser, even after forcing a refresh and erasing the data they did not show up. After rebooting they showed up, but on first boot nothing would work.
MKVs/AVIs. diceplayer
So 720p MKVs are even worse than before. they lag so bad that it makes honeycomb look good. 720p avi file plays perfectly.
standard def avi files in diceplayer and moboplayer are being sped up just slightly. kinda like looking at a 120hz tv. was not like this in honeycomb.
And on my Galaxy Nexus these files play perfectly in diceplayer and moboplayer, so i doubt it's an ICS issue, but an asus issue.
------
curious to see if anyone else has these issues. honestly very upset with the video issues. i was hoping that ICS would finally allow me to play my hd videos, and now my HD and SD videos are screwed up. almost like asus is forcing me to buy the prime if i want to watch videos, which i refuse to do
Two bugs I've seen so far:
-Battery meter taps out at 99%... It will not say 100. The lockscreen says Charged, but check in Battery and it says 99%, also in the notification area in the lower right.
-Two hours later, the Sync Browser in the Accounts and Sync is still thinking...
fatesealer said:
Two bugs I've seen so far:
-Battery meter taps out at 99%... It will not say 100. The lockscreen says Charged, but check in Battery and it says 99%, also in the notification area in the lower right.
Click to expand...
Click to collapse
I have the same on my Moto Defy with ICS. It only reaches 100% when charger connected but will drop to 99% if removed. I guess, "It's not bug, it's a feature". You can try Battery Calibration if it never reaches 100%.
battery charge
My nexus S never charges over 96%. Then I found its a "feature". It is meant to prolong battery lifespan.
Stock internet explorer turns off by it self.
fatesealer said:
Two bugs I've seen so far:
-Battery meter taps out at 99%... It will not say 100. The lockscreen says Charged, but check in Battery and it says 99%, also in the notification area in the lower right.
-Two hours later, the Sync Browser in the Accounts and Sync is still thinking...
Click to expand...
Click to collapse
Please read up on LiPo batteries. It is working as intended. LiPo's are not meant to be ever fully charged.
http://en.wikipedia.org/wiki/Lithium-ion_polymer_battery
People having problems with things shutting down, done a factory reset?
I know it's a huge pain, but the lag/stopping of programs I was having appears (so far) to have been solved by a wipe, and re-install of all my apps.
Thiesen said:
Please read up on LiPo batteries. It is working as intended. LiPo's are not meant to be ever fully charged.
http://en.wikipedia.org/wiki/Lithium-ion_polymer_battery
Click to expand...
Click to collapse
Ok, as a remote control hobbyist who uses lipos all the time, this is just not true. There is no reason why at a certain voltage (4.2 per lipo cell) that the TF should read 100%, this is not normal behavior..but 1% is a negligible drop in battery performance, but could only get worse.
My major bug I discovered- Do NOT use ANY LCD density apps, it will severely mess up you keyboard scaling while not affecting anything else, so I used another one and my launcher is FC'ing will not even boot into it. Time to factory restore..
Factory restore worked, did not even lose root access, but in the process discovered two things, one cool, the other not so much.
1: Asus task manager widget!!
2: tapping VERY quickly seems to be registered as a long press..try it on a widget, just tap it very fast, see if it lags up and then highlights as if it is ready to be dragged, the next tap on the screen will be seen as a drop. Apparently there are touch screen issues even within the official build..CONFIRMED.
luna_c666 said:
2: tapping VERY quickly seems to be registered as a long press..try it on a widget, just tap it very fast, see if it lags up and then highlights as if it is ready to be dragged, the next tap on the screen will be seen as a drop. Apparently there are touch screen issues even within the official build..CONFIRMED.
Click to expand...
Click to collapse
I can't seem to duplicate this error.
Regarding the widgets, I'm not so sure that it's a bug. Now I hate to harp that drum but it's very consistent in the way it acts, and I've only found that behaviour with widgets specifically. In fact, the whole tablet runs like a bloody dream after the update, with touch reaction being one of the improved things. Regarding trouble with video in dice, I'm lucky to not have the same fate. Then again I've always been on stock.
Holy ****, I'm actually blown away. Swiftkey feels so much better now too, and there's absolutely no typing lag in chrome, which was the first thing I downloaded. Wow
EDIT:
But Chrome will never support Flash. Weh.
I as well am blown away.. Never going back to HC lol! ICS is just so smooth, and even with a couple quirks, better than HC
The quirks I see could possibly be with not having rebooted since install, so grain of salt with these please:
Slight lag when opening some programs that are not in memory
slight type lag if other things are going on (picky, I know)
bit of an install lag
Its damned good, but why oh why does the bloody GMail widget *STILL* not update/refresh properly?? i.e. what *should* happen is that new emails arrive, and the widget refreshes highlighting the new email in bold and showing an unread count..
Nope.. no dice.. seems to suffer from exactly the same behavior as the old Honeycomb widget, i.e. it updates some of the time at best (a force close on "Launcher" will cause it to refresh just as before).. In the grand scheme of things, this is small potatoes but it would've been nice if it just *worked*
In other news, the stock browser seems great and typing lag is definitely a thing of the past on forum sites like XDA
jms_uk said:
Its damned good, but why oh why does the bloody GMail widget *STILL* not update/refresh properly?? i.e. what *should* happen is that new emails arrive, and the widget refreshes highlighting the new email in bold and showing an unread count..
Nope.. no dice.. seems to suffer from exactly the same behavior as the old Honeycomb widget, i.e. it updates some of the time at best (a force close on "Launcher" will cause it to refresh just as before).. In the grand scheme of things, this is small potatoes but it would've been nice if it just *worked*
In other news, the stock browser seems great and typing lag is definitely a thing of the past on forum sites like XDA
Click to expand...
Click to collapse
as far as email widget, do you have push notifications on for gmail?
panorama mode doesn't work with the new camera app, it just shows a black screen. Has anyone else experienced this ?
I also got a random reboot, which is new for me,, as HC never did that.
Another thing I've noticed: When I do a shutdown, I have to plug in power to get it to come bakc on. No amoutn of holding or pressing the power button will work without power applied.. Doesnt bode well for me, as it happened also on spark rom when I had it. Seem that i'm the only one with this issue :/
No sound of any kind system, media or otherwise. Silent mode is not on. Really weird. Had no problem with the tablet playing/making sounds prior to the ICS update.
Anybody dock since ics? Im not seeing my battery info for the dock in notifications, just that it is docked.
Some of the buttons(namely the settings button) dont work or dont work the same. Maybe there is suppose to be a firmware update? Is there away for it to force a check for an update of the docks firmware?
kingofyo1 said:
as far as email widget, do you have push notifications on for gmail?
Click to expand...
Click to collapse
Yep, all enabled. As I said above, it works *sometimes* and always after you force close Launcher, but we shouldn't have to do that..
Had a look around, and irritatingly some people get the same problem and some don't so there's no conclusive answer
G+ keeps closing
I did not notice any sort of issue with dice and 720p mkv files. Should I be looking for something specific ? (These profiles are baseline as high causes artifacts under hc).
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.
Guys, this might be a solution to the jittery slow finger scrolling that seems to be plaguing “some” PH1 devices.
Before I get flamed, please note I’m genuinely trying to help out this community. I don’t own an essential phone but i’d like to. I own a oneplus 3 and recently experienced exactly the same slow finger scroll jitteryness even though flick scrolling was pure butter. This began to happen on my device all of a sudden and I tried everything (and I mean EVERYTHING!) to get to the bottom of why normal scrolling lists etc was totally smooth but if you dragged your finger slowly to scroll it was horribly jittery or juddery. I even tried different kernels, GPU Rendering toggling etc etc etc. I finally got my slow finger scrolling back to being buttery smoooth again purely by chance.
I removed 2 apps that I had set “on” in accessibility settings. BAM! Slow scrolling changed immediately from horrible to smooth. Now I dont know if it was having both apps enabled in Accessibility settings or just one but I dont really care. All I know is that my phone responded immediately on making this change, no need for a reboot. Why did this make my phone slow scrolling lag? I’ve no idea. But, just to double check it was this I re-enabled the 2 apps in Accessibility settings and guess what, normal scrolling stayed buttery smooth but slow finger scrolling changed back to lumpy, jittery, almost like the text was vibrating as it scrolled on the screen.
I know some of you will think “WTF!” and so did I on discovering this. Why would this innocuous setting make a difference to scrolling???
Anyway, give this a try. I know my phone is different to yours but the way my phone went was exactly like the scrolling on the essential phone in the youtube videos floating around. Horrible!! Afterwards, my scrolling is back to pure butter in all scenarios.
I hope this solves the issue for you guys. Good luck and let me know if this works for you
p.s. just to be clear, my 2 apps were Nova launcher and Caller Name Talker. Setting both these to “off” did the trick for me. In your case I’d advise setting ANY apps you have “on” in Accessibility settings to “off”. If it doesn’t work immediately, try a reboot although my Oneplus 3 didn’t need a reboot :good:
Thanks for the tips!! Unfortunately I currently have Nova Launcher set to "off" in the accessibility settings and don't have the other app you're talking about. I still have the stutter
Good thing is, Essential said they do have a fix for it and will push it out in the next OTA this month
flakko86 said:
Thanks for the tips!! Unfortunately I currently have Nova Launcher set to "off" in the accessibility settings and don't have the other app you're talking about. I still have the stutter
Good thing is, Essential said they do have a fix for it and will push it out in the next OTA this month
Click to expand...
Click to collapse
Well if they do manage to fix this issue then I will definitely buy one. Providing of course that they sort out any early batch quality control issues too. This is without doubt the most beautiful phone ever created.
Camera quality is not important to me but smoothness is my thing. Thats why I don’t buy Samsung/HTC/LG anymore. I’ve seen my brothers s7 edge and it’s a disgraceful stutter/lagfest compared to my Oneplus 3. I got fed up of trying to hone laggy “flagship” phones to be smoother years ago. Pure android or as close to it now for me.
Only totally smooth phones I’ve ever known are Nexus, Oneplus and Pixel phones. My current Oneplus 3 is the smoothest android experience Ive ever had upto now and although I was looking to upgrade in 2017 to something with a SD835 chip, nothing apart from Essential phone has perked my interest so far.
Good to know there's an OTA coming. Mine seems worse when I'm plugged in charging. Scrolling twitter it will freeze, then sometimes it jumps around opening links I never clicked on.
Also, anyone have trouble registering presses on the edge of phone? Any settings in the top right take about 4 or 5 presses to open.
The official fix is coming. Essential received a fix from Qualcomm and it will be included in Octobers second update, it also includes latest security patch
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.