Related
Coming from WM6, I find it odd that there's no manual screen rotation options in Android. Odder still, that there's no 180-degree rotation mode.
I have a universal Car Mount from my old phone that I like, mostly because it attaches to the air vents. I find this positioning is better than a conventional windshield mount on my car, and avoids the typical issues with suction cups continuously falling off (or melting into place).
The problem is that the dock blocks the USB charging ports on the corner of the Atrix. I can get around this issue by putting the phone in upside down, however to do so I need to 'flip' the display.
The Motorola Auto-Rotate feature does not support the 180-degree position out of the box. I've found several posts asking about this feature, but no answers except a vague reference to Cyanogen Mod, implying that this will take more than a standard app/widget can do.
So, is it possible to do this on the Atrix now that we have root and deodexing options available? This is my first Android phone, so I'm not yet familiar with its innards.
Alternatively, is it possible to flip the display on a given application, specifically Nav or one of the offline GPS programs?
Ideally, what I'd like to see is:
A Widget or shortcut to manually set and/or toggle screen rotation like what was standard on WM6. Outside of the car dock, this is also useful when using the phone on a desk or bed at odd angles.
Script/Shortcut/Icon that sets a specific rotation and then launches the car dock (or GPS app).
Use Launcher Pro.
Gives you full 360 screen rotation.
Sent from my MB860 using XDA App
No, unless I'm missing something, it does not.
LauncherPro does allow the home screen to be rotated (which is not what I care about right now), but it does not support rotating it 180-degrees (upside down).
Ahh you're right.
The dock will flip to 180, but the screen stops at 90.
Any ideas?
I don't mind playing with Androids internals (time permitting) if this is possible , but as I said my experience with Android so far is minimal (particularly compared to the xda experts).
According to http://developer.motorola.com/docst...at_runtime__Allow_the_user_to_set_preferences, the only options for application preferences are landscape or portrait. Not sure if this is applicable though.
I've found an old related thread for the G1 here http://forum.xda-developers.com/showthread.php?t=449688&page=2 added screen rotation to that device. It does note though that not all rotations are implemented, and is probably also talking in the context of 2.1.
Another related thread at http://stackoverflow.com/questions/...e-rotations-by-90-but-enable-rotations-by-180 seems to imply that the 180-degree rotation won't work until we get the Android 2.3 update.
The android docs includes a ROTATION_180 definition for the Surface object with a setOrientation method on http://developer.android.com/reference/android/view/Surface.html
It appears that CyanogenMod 7 adds this capability: http://nightly.posterous.com/rotate-180
Clearly we're not going to see CM on the Atrix for a while, but is there anyway we can backport this feature into the Atrix, or will this have to wait for the fabled 2.3 update?
‘Life’, as per John Horton Conway’s original creation. It simulates the existence of a two dimensional array of cells which will continue, or not, into the next generation based on a few simple rules. Which are:
If a cell has two or three neighbours, it will continue into the next generation. If an empty square is surrounded by three neighbours, then a new cell will be ‘born’ into it on the next generation. In all other cases which is where a cell has less than two or more than three neighbours, then the cell will die, simulating a lack of breedable neighbours, or lack of food due to overcrowding, respectively.
These simple rules create a complex world, where order and chaos reign, and quite often change places with each other, before finally settling down to a stable or completely static state, sometimes after hundreds, if not thousands, of generations.
The program is a Win32 C++ implementation in an executable of only 13Kb in size, although it consumes around 200Kb of memory when running. It uses basic GDI drawing functions so it will run on any ARM powered Pocket PC or Smartphone, from WM2003 onwards. Just drop the executable on your device and run it. It will also run on any sized screen up to 1024x1024 pixels, so that should take care of all current devices. It matches the grid size to the screen size. Cell populations cycle every half a second.
The original population is a randomly generated, with a one in four chance of a cell being present, after that the above rules take over.
MENU OPTIONS:
Restart will regenerate another random selection.
Auto Restart will make an intelligent guess that the population has reached a stable or static situation and will automatically restart after around 20 seconds of such a situation being reached. It has a reasonable attempt, but it cannot spot all possible stable or static situations.
Start Edit: Stops the generation and allows you to edit the cell pattern.
Pocket PC: - Tap the screen to create or remove a cell.
Smartphone:- Use the D-Pad to move the inverted cursor to the required square and press the centre Enter button.
Clear will erase all cells.
Run restarts the generations.
Wraparound removes the bounding effects of the edges of the display. When selected, cells' affects are allowed to roll over, left/right and up/down. The display, in effect, then becomes part of an infinitely repeating pattern.
Pressing the OK button does not terminate the program. Select End Program to close it completely.
If you have a Wizard, Kaiser or similar device, where the display can be switched from portrait to landscape, and if you do so, the program will continue, but you may invoke a near catastrophic extinction, as the display gets realigned to the new layout.
For a more complete article on this topic, have a look at:-
http://en.wikipedia.org/wiki/Conway's_Game_of_Life
The samples image shows a few shapes to try. They are the glider, the R pentamino, the spinner and the 10 consecutive cells. The R Pentamino generates a chaotic pattern of many cycles before it settles down, all the others are static/cyclical patterns. Auto Restart cannot detect the 10 consecutive cells, the repeating pattern is too complex for it to spot.
Update: 17/06/2011 Version 1.1 fixes the Embedded C++/WinMo 6.5.3 Dialog Box issue mentioned in
http://forum.xda-developers.com/showthread.php?t=635063
If you are running Winmo 6.5.3 and you downloaded this before 17/07/2011, you will need version 1.1 in the zip file below.
UPDATE: CE Version added.
If you have bought an ARM powered Windows CE device and are thinking
"What the hell do I do with this?!!"
try the CE version, then you can think,
"What the hell does this do?!!!"
Do not run the CE version on your SmartPhone or PPC device, the display will look awful. The same applies to running the Mobile version on a CE device, but try it if you must. An extra caveat is that your CE device should be running a version backwardly compatable with the Embedded C++ 4.0 'Standard' SDK
P.S. I wrote this program originally to run under DOS, over twenty years ago. It was written in 8086 assembly language, as it was the only way to get it run fast enough on a 12Mhz 80286, and drive an 640x480 mono VGA screen fast enough for it not to look awful. These days, on a current Intel Core class processor, the same program now runs through hundreds of generations per second, rendering it almost useless. Even though the program is now ported to C++ under a completely different platform, some of the original code optimization methodologies remain. They still work!
Thanks a lot.
Updated to 1.2
On Pocket PC/WinMo Professional/Windows CE platforms only:-
During 'Edit' mode, click and drag to set or erase a series of consecutive cells. Set or erase depends on whether the first cell clicked was empty or occupied, respectively, and will continue in the same mode until the mouse or stylus is lifted.
This makes it much easier to create the 10 cell line pattern as mentioned above.
None of this applies if the program is running on Smartphone or WinMo Standard platforms.
Hello.
I apologize in advance if this is not the right forum to post in, or if it's not the right site at all, but a friend whose specialty is Android led me here, and told me to post my problems here.
I am a long-time iOS user. But I am also disabled : I have 1/20th vision on my left eye and nothing on the right one. My eyes are easily blinded by light, and as such I find it painful to read text on a screen when it's black on a white background. In Windows, for instance, I change the Windows theme back to Classic Windows so I can edit the different colors that make windows, buttons, and menus so they are easier on my eyes. In OSX, I use the 'Invert Video' feature on a shortcut key, so that when I press it, the screen suddenly inverts all colors, makign it much easier on my eyes. (Sadly, it also inverts colors on pictures, but that's okay, I can live with switching back and forth if needed.) On Chrome (any OS), I use the Stylish extension to force every site's CSS to follow my own and keep backgrounds dark and text light... You get the idea. On iOS, a similar feature to the one in OSX exists, and you have to press the home button three times to switch it on or off.
If I'm posting on this forum, this is because I have questions regarding Android's features for disabled people like me.
From my understanding, and from what I briefly tried on my sister's Acer E330 (Android 4.0.4) there is no such feature. A friend with a Nexus 4 confirmed this too.
I was wondering if there was some kind of plugin, addon, extension, app or whatever that would allow me to redefine Android's interface (a theme perhaps?) or even better, some kind of 'Invert Video' feature just like on iOS. I'm asking about this because I'm considering buying a Android device since I realized I was starting to have problems with some displays used on recent iPhones, iPads, Macbooks or even on regular PC laptops like MSIs' or Samsungs'.
The problem I have has been unresolved so far as there is no way to tell what part/setting of recet LCD/LED displays make my eyes sore after about 5 minutes of use. I did a lot of research without being able to find out what caused this exactly, but a lot of people seem to have the same kind of problem while having a normal eyesight unlike I do.
So, right now, two things prevent me from being sure if I should buy a Android phone or not :
- I need to make sure the display is fine with my eyes.
- And the reason why I'm posting this here, is that I want to know if it's possible to have the same kind of feature on iOS/OSX for changing colors of the whole screen by the press of a physical button on the device several times (this seems like the best solution, as a system setting switch would be a bit painful to use. FYI I really overuse and abuse this feature because it allows me to quickly switch to a dark background on white pages, while restoring the normal colors if the next page I'm visiting has a black background.)
So there it is, again, I apologize if that wasn't the right forum or anything. I hope someone here can help me with this problem. I'm not a die-hard Apple fanboy : I just happen to use their devices because they are the simplest to work with considering my disability.
Thanks in advance.
This is not my code and I apologize if this doesn't belong here, I think it does.
Simply enter this into a terminal emulator, it does not survive a reboot, so I'm posting this in hopes ROM makers will add it in.
Code:
echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture
Source is here
Big Cam said:
This is not my code and I apologize if this doesn't belong here, I think it does.
Simply enter this into a terminal emulator, it does not survive a reboot, so I'm posting this in hopes ROM makers will add it in.
Code:
echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture
Source is here
Click to expand...
Click to collapse
Its also pretty useless for alot of scenarios with the finger print scanner - its fine when connected to a trusted BT device and then swipe to unlock or if you want to check the time with a double tap.
Its pointless otherwise, however a nice feature for the sake of a feature - the power button achieves the same thing or just finger print to unlock right out the pocket.
The only case I have found a use for the D2W is when in my car connected via BT streaming music and want to quick unlock in traffic to change a track without having to reach around my phone holder on the windscreen to unlock via the scanner.
I'd hazzard a guess its why google never enabled it out the box but left the function in.
hutzdani said:
Its also pretty useless for alot of scenarios with the finger print scanner - its fine when connected to a trusted BT device and then swipe to unlock or if you want to check the time with a double tap.
Its pointless otherwise, however a nice feature for the sake of a feature - the power button achieves the same thing or just finger print to unlock right out the pocket.
The only case I have found a use for the D2W is when in my car connected via BT streaming music and want to quick unlock in traffic to change a track without having to reach around my phone holder on the windscreen to unlock via the scanner.
I'd hazzard a guess its why google never enabled it out the box but left the function in.
Click to expand...
Click to collapse
I already use this while my phone is on the desk. Way quicker to double tap screen and input key then grab phone and pick it up
hutzdani said:
Its also pretty useless for alot of scenarios with the finger print scanner - its fine when connected to a trusted BT device and then swipe to unlock or if you want to check the time with a double tap.
Its pointless otherwise, however a nice feature for the sake of a feature - the power button achieves the same thing or just finger print to unlock right out the pocket.
The only case I have found a use for the D2W is when in my car connected via BT streaming music and want to quick unlock in traffic to change a track without having to reach around my phone holder on the windscreen to unlock via the scanner.
I'd hazzard a guess its why google never enabled it out the box but left the function in.
Click to expand...
Click to collapse
I mean, come on man. the conceptual point of Android was the ability to have your choice of options than what a single company deems necessary. It becomes second nature once you have devices that have it like the m8 or Nexus 9. Also some cases or bumpers tend to mush the power button travel, making even that way more difficult.
Even that aside, sometimes you just want to check and manage notifications or whatever, fingerprint immediately unlocks the device.
Jbluna said:
I mean, come on man. the conceptual point of Android was the ability to have your choice of options than what a single company deems necessary. It becomes second nature once you have devices that have it like the m8 or Nexus 9. Also some cases or bumpers tend to mush the power button travel, making even that way more difficult.
Even that aside, sometimes you just want to check and manage notifications or whatever, fingerprint immediately unlocks the device.
Click to expand...
Click to collapse
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Do we need root for this to work?
hutzdani said:
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Click to expand...
Click to collapse
I dont want to pick up my phone and movie it around to get to the fingerprint scanner. Even getting to the power button can cause me to focus to much attention. A double tap is quite easy todo to check what notifications you have.
You have never used double tap is my guess and I recommend it even if it seems kinda useless.
hutzdani said:
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Click to expand...
Click to collapse
DT2W is an AWESOME feature - even if it was disabled by Google after careful thought. Yes, the fingerprint scanner is quick and very convenient. However, because it bypasses the lock screen it also bypasses lock screen notifications. Sometimes I just want to read a quick text/push notification without picking up my phone or locating the power button. A quick double tap on the screen is a lot better than picking up the phone, using my fingerprint to unlock, and then swiping down the notification shade to read my updates.
deeproot said:
I dont want to pick up my phone and movie it around to get to the fingerprint scanner. Even getting to the power button can cause me to focus to much attention. A double tap is quite easy todo to check what notifications you have.
You have never used double tap is my guess and I recommend it even if it seems kinda useless.
Click to expand...
Click to collapse
Used DT2W with N5 / 6 / 7 / G3 and G4 because it was useful as I never used pin entry or any other type of passworded lock, just swipe to unlock.
Now we have a finger print scanner the whole idea of D2TW is depricated alongside active display ( to a certain degree & AW )
D2TW works fine as a quick check for the time but coupled with finger prints its a dead end function beyond checking the time or expanding a notification, notifications are mostly acted on in day to day use.
Now go through the motions - You DT2W see a notification you want to attend to and your faced with one of two things 1. Finger print to get in or 2. Pin or pattern unlock.
In these two cases its slower than just doing FP or Unlock codes - Now factor in the accuracy of DT2W ( yes it can be adjusted ) but some cases it will just ignore it and require a more firm press on the screen.
Now we have two hurdles to factor in - now Imagen your at Google and your selling a device with a quick and efficient and secure way of getting into your device fast to compete with the growing trend of other OEMs.
Do you plump for a slow unaccurate system that does not even get you into the device and still requires PIN entry to do stuff or do you go the FP route.
looking at it this way makes it all very clear from Googles perspective as to why its not enabled by defult.
I like DT2W don't get me wrong but its just irrelevant for those who will use the FP in conjunction with the LED or active display or AW.
The fact that it only serves a good useful purpose when connected to a trusted device for quicker access, alone shows how its a Gimmick feature these days due to tech moving on.
Alot of people will still naturally use the power switch to check the screen for notifications as its been creature habit for many since androids inception, LG introduced it and it gained traction before the whole active display thing moto dropped on the scene.
Now with active display ( Frankly a stupid gimmick if you ask me - give me a blinky LED anyday ) and android wear ( if you can believe that is even worth the effort or cash trust me its not ! ) its even less relevant to DT2W to read the screen.
Point is its not there by defualt for a reason - a design reason - a technical reason - a marketing reason : yes android is open source and google knows nexus people like to tweek their devices so they will have left some gems for people to play with.
As a device they are selling DT2W is not a likely candidate to hit the specs sheet or the TV adverts or Ads is it now when its up against bigger better selling features : FP / Permium build quality / USB C / Slow mo video capture e.c.t
I like to look at things from both points of view but DT2W has little going for it these days with all the additional functionality
hutzdani said:
Used DT2W with N5 / 6 / 7 / G3 and G4 because it was useful as I never used pin entry or any other type of passworded lock, just swipe to unlock.
Now we have a finger print scanner the whole idea of D2TW is depricated alongside active display ( to a certain degree & AW )
D2TW works fine as a quick check for the time but coupled with finger prints its a dead end function beyond checking the time or expanding a notification, notifications are mostly acted on in day to day use.
Now go through the motions - You DT2W see a notification you want to attend to and your faced with one of two things 1. Finger print to get in or 2. Pin or pattern unlock.
In these two cases its slower than just doing FP or Unlock codes - Now factor in the accuracy of DT2W ( yes it can be adjusted ) but some cases it will just ignore it and require a more firm press on the screen.
Now we have two hurdles to factor in - now Imagen your at Google and your selling a device with a quick and efficient and secure way of getting into your device fast to compete with the growing trend of other OEMs.
Do you plump for a slow unaccurate system that does not even get you into the device and still requires PIN entry to do stuff or do you go the FP route.
looking at it this way makes it all very clear from Googles perspective as to why its not enabled by defult.
I like DT2W don't get me wrong but its just irrelevant for those who will use the FP in conjunction with the LED or active display or AW.
The fact that it only serves a good useful purpose when connected to a trusted device for quicker access, alone shows how its a Gimmick feature these days due to tech moving on.
Alot of people will still naturally use the power switch to check the screen for notifications as its been creature habit for many since androids inception, LG introduced it and it gained traction before the whole active display thing moto dropped on the scene.
Now with active display ( Frankly a stupid gimmick if you ask me - give me a blinky LED anyday ) and android wear ( if you can believe that is even worth the effort or cash trust me its not ! ) its even less relevant to DT2W to read the screen.
Point is its not there by defualt for a reason - a design reason - a technical reason - a marketing reason : yes android is open source and google knows nexus people like to tweek their devices so they will have left some gems for people to play with.
As a device they are selling DT2W is not a likely candidate to hit the specs sheet or the TV adverts or Ads is it now when its up against bigger better selling features : FP / Permium build quality / USB C / Slow mo video capture e.c.t
I like to look at things from both points of view but DT2W has little going for it these days with all the additional functionality
Click to expand...
Click to collapse
Agree to disagree. Double tapping for a quick check of the time or a notification is a handy feature. Not every notification requires you to act on it. A lot of times (Gmail Spam) I will DT2W and then swipe to dismiss the notification. That does not require using a pin and or fingerprint.
hutzdani said:
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Click to expand...
Click to collapse
Your argument is pointless, just because google turned it off doesn't mean it doesn't serve a purpose. Example, google heavily pushed ambient display over LED notifications and we all know LED notifications work ten times better....
Yep, my phone sits most of the day next to me in a trusted space and it is mucho nice to be able to double tap in and check messsages, time, etc. without having to specifically hit the power button to light the phone up. Further I have owned a phone where the power button eventually died and DT2W removes the majority of cycles on the power button. It can be done when the phone is on either side. It can be done while the phone is in a dock and more without taking your eyes off the road if docked in the car. Just because someone in particular doesn't use it doesn't mean it isn't a useful feature.
I think the reason DT2W was disabled is because someone on the android team secretly is taking money on the sly from Apple in exchange for removing useful and nice features from android. Anyone who says anything else clearly needs more tequila in their life.
i couldn't get this to work. anyone else successful?
I'd like to have this enabled on mine when it gets here Monday. Why not? When it's on table I can just tap to check it. More is more
Sent from my XT1096 using Tapatalk
double tap to LOCK?
Is it possible to modify your code so double (or maybe triple?) trap would lock the device? Thanks!
Big Cam said:
This is not my code and I apologize if this doesn't belong here, I think it does.
Simply enter this into a terminal emulator, it does not survive a reboot, so I'm posting this in hopes ROM makers will add it in.
Code:
echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture
Source is here
Click to expand...
Click to collapse
.
There is no need for this anymore, by installing a custom Kernel you can get this highly needed feature.
im currently running ElementalX Kernel which enables DT2W.
http://elementalx.org/devices/nexus-6p/
Working like a champ. I hope Francisco Franko kernel gets realeased soon.
Yeah, this is redundant now.
Sent from my Nexus 6P using Tapatalk
Excellent, that's what I was hoping would happen!
hutzdani said:
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Click to expand...
Click to collapse
It is made difficult by the finger print scanner being on the back of the device. If it was on the front the functionality would be unnecessary. I like the scanner on the back for in the hand use but it is a limiting factor during use on a table/flat surface.
byproxy said:
i couldn't get this to work. anyone else successful?
Click to expand...
Click to collapse
1) You must be rooted
2) type
Code:
SU
into terminal
3) type the code
Code:
echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture
Hi all, can anyone who owns the tablet check if your set has this issue as well? I'm using the Mediapad M5 Pro.
Basically on my set there is a problem with the touchscreen whereby when making small adjustments, changing directions with small movement will cause the touchscreen to hang and cause the touch input to jump a few pixels.
Any help would be appreciated as I'm trying to figure if this is a hardware issue with my set or if its a software issue that affects all M5 Pro.
I have an inkling that this could be caused by palm rejection configuration of the tablet that is overly aggressive, causing the touchscreen to bug out as such.
Videos to illustrate problem: (use the direct links if the embedding doesn't work)
(in app drawer) https://youtu.be/Ni5xvRPgAdE
(in pubg mobile) https://youtu.be/mibyKmaXA0E
(in chrome remote desktop) https://youtu.be/vpmXleSaNZU
My M5 Pro is having this issue too...
Afaik there is a threshold level when to recognize an input as a "tap" and when as a "swipe/movement"
We humans are too inaccurate so that one tap often contains a movement by accident. To cancel that out minor movements are still considered taps.
Would be interesting to see if it is the same on lineage OS. If it is,then the reason is probably palm rejection or some weird thing. If it's not the reason is most likely how Huawei calibrated it.
At least that's what I think without any proof
lolmensch said:
Afaik there is a threshold level when to recognize an input as a "tap" and when as a "swipe/movement"
We humans are too inaccurate so that one tap often contains a movement by accident. To cancel that out minor movements are still considered taps.
Would be interesting to see if it is the same on lineage OS. If it is,then the reason is probably palm rejection or some weird thing. If it's not the reason is most likely how Huawei calibrated it.
At least that's what I think without any proof
Click to expand...
Click to collapse
Good point, but the thing is the jitters still occur after I start to scroll the pages. Afaik, upon the very first contact against the digitizer the system should identify if its a tap or scroll input. Once a scroll input is identified, the consideration for tap input should be nullified.
In that case if we were to refer to the videos I shown, as soon as my finger taps the screen and starts scrolling, the digitizer should be relaying information to the phone that it is a scroll, there is no reason for the phone to think that I am still performing a tap after I have been scrolling around without lifting my finger off the screen.
Of course, I am no coding expert and what I am stating here is based on logic and my limited understanding of computer language. So my point is I still think it's a software bug that Huawei needs to address and as evident on their past phones (P20 Pro, Honor 9), it is not the first time bad touch firmware has been heard of on a Huawei device.
**Another point is that if you were to perform the same test but instead with the M-pen, the touch screen would work just fine. But stylus touch input runs differently from finger touch input, so I am not too sure about how to comment on this.
jerronchua55 said:
Good point, but the thing is the jitters still occur after I start to scroll the pages. Afaik, upon the very first contact against the digitizer the system should identify if its a tap or scroll input. Once a scroll input is identified, the consideration for tap input should be nullified.
In that case if we were to refer to the videos I shown, as soon as my finger taps the screen and starts scrolling, the digitizer should be relaying information to the phone that it is a scroll, there is no reason for the phone to think that I am still performing a tap after I have been scrolling around without lifting my finger off the screen.
Of course, I am no coding expert and what I am stating here is based on logic and my limited understanding of computer language. So my point is I still think it's a software bug that Huawei needs to address and as evident on their past phones (P20 Pro, Honor 9), it is not the first time bad touch firmware has been heard of on a Huawei device.
**Another point is that if you were to perform the same test but instead with the M-pen, the touch screen would work just fine. But stylus touch input runs differently from finger touch input, so I am not too sure about how to comment on this.
Click to expand...
Click to collapse
I agree with you. They managed to fix the emui touch bug though where two simultaneous inputs were denied after a short time. (also was / is on the p10 and other emui devices)
And that's why I was curious about lineage OS.
The pen works with a different digitizer though. So different production, drivers etc
Not fixed even with the latest update with Gpu turbo...
anyone have solution for this??
i don't know if this is solution but there is 1 option. I don't know how is in english because i have polish language but if u
Polish - Ustawienia - inteligętna pomoc - Ułatwienia dostępu - Gesty powiększania
Translator google XD ???? - Settings - intelligent help - Accessibility - Gestures of magnification
when I have this option turned on, the touch screen responds very strangely and with an delays in all apps (games too)
DDragonDD said:
i don't know if this is solution but there is 1 option. I don't know how is in english because i have polish language but if u
Polish - Ustawienia - inteligętna pomoc - Ułatwienia dostępu - Gesty powiększania
Translator google XD ???? - Settings - intelligent help - Accessibility - Gestures of magnification
when I have this option turned on, the touch screen responds very strangely and with an delays in all apps (games too)
Click to expand...
Click to collapse
Is already off but still having same touch issue...