** update -screen realignment resolved the issue **
I posted the following on another board with no luck. Maybe someone here has some suggestions:
Hello all. I've just started encountering an odd issue today on my Touch. When in any of my email apps, I am unable to scroll unless I apply a great deal of preassure with the stylus. Normal preassure has no effect. I can also use my finger, but again, only by using an unusually high amount of preassure.
What's stranger, is that everything else is working perfectly fine. Scrolling functions are superb otherwise. I'm only encountering the problem specifically when in my email.
Is there a registry setting specifically for email scrolling or something? I haven't done any hacks that are out of the ordinary. I only started having the problem this morning.
Any help is appreciated. Thanks
Related
Because I can't post in the proper place, maybe the forum admin could transfer
this post to the proper place(development).
On version b-37(5/26) of the AKOP build for vision I have a couple of comments.
I have exercised this build for the last few days and it works very well, I only have found a couple of possible bugs.
The mic in the headset(earbuds) does not seem to work for phone calls. The little switch on the headset does seems to work and the playback works fine. The mic in the phone works fine if you unplug the headset. There might be another program switching the mic off, but I haven't found any. It is like the mic is in mute and the mute switch does nothing on the headset mic.
The WiFi is off when the phone boots up, This might be a feature rather than a bug. Unless there is a lot of complaints I don't think it needs to be changed. The Internet phone from T-mobile does not work(known).
Another problem and I don't know if it is a program problem of a version problem.
I have tried many web browsers and on some sites they are very slow for the page to loads(like a minute or so). It might have something to do with Flash,
although most sites are OK. You Tube does work OK. Another quirk is the sites will come on with low resolution and then it appears as though the site has finished loading and the font is fine. It appears as though some sort of page loading problem. This happens with all the browsers I have tried.
A couple of times I have had the font under the Icons scramble, if the page gets rewritten then the font is OK.
All in all this is a very good version with very few bugs, great job !!!
Clyde
New build is up. Some of your bugs should be fixed already (e.g. with microphone).
AKOP build 38
The mic problem is fixed in b38(thanks), only one other problem that is new
to b38 is that the Home key and the Search key on the bottom of the phone
no longer function.
I found that the included browser has problems when loading then freezing on a
white screen. Other browsers seem to work, so deleted same.
I might add that in b37 and b38 the track pad finally works like it is supposed to.
In earlier versions and 2.3.4 it never worked properly. Also, the lights on the
keyboard and the 4 buttons on the bottom of the phone now stay lighted and
don't go off and on. Thanks for the improvements.
Clyde
Hello,
I also use the ROM and find it great. But I have two problems with it.
I can't send MMS. I have delete and recreated the MMS-APN but without any change.
My second problem is the clock when I use the apex launcher. When the phone ist unused for a while the clock goes wrong. On the widgets it shows 10:20, on the screenlock it shows 9:45 an the realtime ist 11:34 or so.
I hope someone has an answer.
thx
Home Key fixed
Found the problem I was having with the Home key being non-functional.
Seems like 2 programs I found write data where it is not supposed to be,
they are Android Assistant and Super Task Killer. If you run either one of these
programs the home key becomes non-functional.
The standard included browser has a problem with most of the time not
starting and giving only a white screen. I have tried 6 other browsers and all
work fine. Deleted same.
This fixed the 2 major problems with Build 38. There is a minor problem with the
Sim Card recognition, gives a error message to restart which is in error. The
main screen comes up long before the initial boot process has finished. I think
init.d is running after the main screen comes up. Works fine if you just let it
complete its work.
Build 38 is very stable and has very few problems. Great work !!
Clyde
Hello everyone. I've done a few searches on here but haven't found this exact problem. Relevant details without extra background info are in bold.
My wife and I each got an S4 with Sprint's recent BOGO promotion. My phone has had no issues. It came with MDL in the box, which I updated to MF9 via OTA, flashed TWRP via Heimdall in Linux, rooted, and installed the hotspot mod.
Her phone - completely stock MF9 and new from the store - has had problems, one of which I've so far been unable to fix. (How I wish it were mine. I develop for Android, but this is much more of a pain for her.) Hers already had MF9 at the store. It had the Google Services Framework/Core Apps runaway process issue with heat/battery drain from the start - which I fixed. However, it also has unresponsive sensors for ~3 seconds when receiving a call. It's almost as if there's some lag in activating the sensors. The phone is otherwise snappy with no other lag noted.
- Hard reset has been tried.
- The touchscreen is unresponsive during this time, though the display functions.
- The gesture for answering (when enabled) also does not work.
- We haven't tried enabling the home key to answer, but this will be next.
I've seen this before with Android a good while back. It was an inherent problem with Gingerbread on many phones. Haven't seen it pop up in Jellybean at all. In trying to diagnose, I've ensured that all bells and whistles are turned off. No air gestures are on.
We'd really like to get it working as it should. Has anyone else experienced this? Any advice?
Many thanks!
I believe this is more of a stock software issue. I have had the issue since day one.
When I turned off svoice and some of the other added features most of the lag disappeared. Svoice is pretty good at creating lag as far as ive seen.
Voice response seems to create th lag as it is awaiting a voice command from you.
This is what I have noticed anyway.
Sent from my SPH-L720 using xda app-developers app
I'm running stock android 7.1.1 on a Nexus 6p and there's a dramatic lag in scrolling response. When the screen is scrolling quickly and I put down my finger to stop the scroll there is a huge lag before the scrolling stops. About half a second or more. It seems to occur in all apps (and even system settings menus). I've had this problem since buying the phone a couple weeks ago. It's driving me nuts. I never have this problem with my iPad, MacBook or even my ancient nexus 4. The odd thing is that if instead of just putting down my finger I drag my finger slightly (in any direction) then the lag almost disappears, but obviously that's a very awkward thing to do, especially when none of my other devices require it. Does anybody else have this problem (and hopefully a solution)?
I've talked to Google customer support. They told me to clear the cache of every app (yes that does take quite a while) and to clear the partition cache. This did not resolve the problem and now they want me to do a factory reset, which apparently is the last step before hardware warrantee measures. I'd love to know if this is a common problem.
Al--g said:
I'm running stock android 7.1.1 on a Nexus 6p and there's a dramatic lag in scrolling response. When the screen is scrolling quickly and I put down my finger to stop the scroll there is a huge lag before the scrolling stops. About half a second or more. It seems to occur in all apps (and even system settings menus). I've had this problem since buying the phone a couple weeks ago. It's driving me nuts. I never have this problem with my iPad, MacBook or even my ancient nexus 4. The odd thing is that if instead of just putting down my finger I drag my finger slightly (in any direction) then the lag almost disappears, but obviously that's a very awkward thing to do, especially when none of my other devices require it. Does anybody else have this problem (and hopefully a solution)?
I've talked to Google customer support. They told me to clear the cache of every app (yes that does take quite a while) and to clear the partition cache. This did not resolve the problem and now they want me to do a factory reset, which apparently is the last step before hardware warrantee measures. I'd love to know if this is a common problem.
Click to expand...
Click to collapse
Hi, I made some tests in your issue doesn't occur on my 6P with stock 7.1.1.
Sent from my interstellar 6P
same here
Al--g said:
I'm running stock android 7.1.1 on a Nexus 6p and there's a dramatic lag in scrolling response. When the screen is scrolling quickly and I put down my finger to stop the scroll there is a huge lag before the scrolling stops. About half a second or more. It seems to occur in all apps (and even system settings menus). I've had this problem since buying the phone a couple weeks ago. It's driving me nuts. I never have this problem with my iPad, MacBook or even my ancient nexus 4. The odd thing is that if instead of just putting down my finger I drag my finger slightly (in any direction) then the lag almost disappears, but obviously that's a very awkward thing to do, especially when none of my other devices require it. Does anybody else have this problem (and hopefully a solution)?
I've talked to Google customer support. They told me to clear the cache of every app (yes that does take quite a while) and to clear the partition cache. This did not resolve the problem and now they want me to do a factory reset, which apparently is the last step before hardware warrantee measures. I'd love to know if this is a common problem.
Click to expand...
Click to collapse
You aren't the only person who has experienced this issue but I haven't had it happen. I don't know if anyone found a solution but if you do a search in this section you should find a thread very similar to yours with a lot of responses. I think some people experienced the issue after updating to 7.1.1
jhs39 said:
You aren't the only person who has experienced this issue but I haven't had it happen. I don't know if anyone found a solution but if you do a search in this section you should find a thread very similar to yours with a lot of responses. I think some people experienced the issue after updating to 7.1.1
Click to expand...
Click to collapse
Thanks, I'll have a look. (Tried searching before but didn't find anything.)
For me the problem predates 7.1.1
I found the source of my scroll lag issue. I sometimes enable the magnification gesture in the accessibility settings (because I often use a particular transit app that has insanely small icons). I realized that when I have this setting turned on the scrolling gets laggy. Turning off the magnification gesture seems to solve the problem completely. Not sure if there's any workaround other than disabling the gesture setting.
Just picked up an Android version, touch pad... Is it just mine or are they all wonky like this? Random vibrations, half the time it thinks I'm clicking something, scrolling is just ridiculous.. This can't be how it was designed, is it?
The trackpad shouldn't be behaving like that. I was describing the YB (on MacRumors of all places) and how well it worked but another member complained about the same symptoms that you described. Their issues were resolved by updating to Nougat. I suggest doing that if you haven't already. If the problem persists after that, try a factory reset.
I've been looking around to solve this issue, but haven't have much luck. It looks like it's an issue with a good number of ROMs on this phone, but my issue is that after some time, the touchscreen in some games and apps stops working normally.
Phone is running Lineage 16, rooted w/ magisk
To have it work, I need to hold one finger on the screen and the other finger will register properly.
The issue can temporarily be fixed by rebooting the phone.
I notice the issue occurring when an app/game accesses the camera. At that moment, issue occurs.
I came across this in my searches: https://review.lineageos.org/c/Linea...ative/+/198809
Not sure exactly how to work with that, but I figured I would provide as much info as I can before asking for help. Thanks ahead for the help