Hi folks,
Recently, I experienced an annoying bug which I wanted to ask you about:
When the keyboard case (original Folio Keyboard) ist attached to my M5 PRO, it happens from time to time that the brightness adjusts itself to 0.
Even with automatic brightness deactivated.
I am typing and then it goes down and I cannot continue writing, unless I hit the Back button(either software or hardware button).
For better understanding I have uploaded a short video to my Dropbox, where it will remain until I need the space:
https://www.dropbox.com/s/bz3gpvfb4ie9cw0/20180430_172623.mp4?dl=0.
I am typing in German in the video, but the text really isn't that important, I ws just typing for showcasing purpose of the bug. Sorry about the music, I was sitting at a café, when recording this and unaware that the app recorded external sound and then too lazy to make a new one ...
--> When in desktop-Mode the bug appears, too - I can then see the "System"-Icon in the Task-Bar (which you will not find i the video, I found that out after recording the video and have not made another one, yet.)
What might be relevant:
1) Using Nova Launcher Pro
2)BuildVersion: CMR-AL19 8.0.0.122(C432); EMIU: 8.0; Android: 8.0
3)With Huawei Start (Huawei Launcher's name in German, don't know whether it is the same in English) it happens slighty differently: It adjusts too often, when surrounding light is not changing, but it does not go to =, in Desktop-Mode, however, it goes to 0.
On android-hilfe.de another German user has experienced this behavior - thinking about a correlation to the keys [P] and [Q], I doubt that!
Has anyone else experienced this bug?
Any help would be appreciated!
Thanks in advance!
Kevin
Related
Has anyone noticed a change in how the touchscreen behaves after installing ICS?
It seems to me that it is biased a little more towards interpreting a touch as swipe or scroll rather than select. For example clicking links in a webpage or tapping icons on the homescreen seem to require a much more deliberate effort to select/open. It's not awful, but I would like to be able to bias it back a little more to selecting rather than swiping.
Is there a setting for this anywhere or an app available that allows adjustment?
I would to know too.. I hate this..
But it's not just from latest ICS 4.0.3 International, the Beta version also suffer same thing.
Is HC not like this? (I upgraded to 4.0.3 Beta as soon as after bought Mediapad )
Yes, I noticed it also. When you turn on Settings - Developer options - Pointer location, it clearly shows how your clicks/dots becomes swipes/lines.
yes, you're right.. it sometime (most time ) cause texting experience not so fluid (letter not appear as it's detected as swipe not click).
got the same thing.. i've changed the launcher, so with the Apex launcher it's not that bad in the homescreens.. when i enabled the option to show "pointer location" i can see the "tap" as a line, or a "swipe" line :\
tried the same on my Galaxy S, and all the "taps" are only a small point.. it's much better than on the MediaPad.. i hope it's just a software issue and it can be solved..
maybe, we could try something like "screen booster" or "touchscreen booster" from the Market (Play)
Erratic screen while charging
The other thing I've noticed after ICS international is that the touchscreen is now erratic while charging and in a case. I believe this is a common problem with capacitive touchscreens, but hadn't noticed it until after flashing ICS. It is not an issue if I remove the pad from the case and hold it in my hand.
Anyone else seen this?
This sensitive touchscreen isn't Angry Birds friendly. Constantly shakes a little bit.
soooo.....is there any solutions?
noaustin said:
soooo.....is there any solutions?
Click to expand...
Click to collapse
Not unless huaweis coders tweak it or releases the source code.
Hello,
Firstly i want to apologize you for mistakes in my English (the original post is correct in Polish – I created this topic on other polish forum and I did not get answers. I hope that someone will help me )
I have a problem with an inoperative back camera phone brand lg. Recently assumed the new digitizer (after replacement experiencing this problem). After work I noticed the camera does not work.
The following is a screenshot of how to behave camera system after it starts. At the beginning it is a black background, and the available options (possibility to change the image size etc.). After a while of inactivity (approx. 30 seconds), the screen changes color to green. I think the better of these situations presents screenshots.
Screenshots I can send to private message
Hi guys. Sorry for my bad English and for "click bait" title.
Recently I installed the app "Activity Launcher", so I wandered through the various activities of the various system applications and I found this:
Pressure sensing:
Screenshot 1
Screenshot 2
If I press harder it recognizes the intense pressure and vibrates. (I clearly speaks of the width trace, rather than in 3D pressure)
I also downloaded the firmware Mate S because it should have this functional setting, but I did not find anything that I can make a "porting" to make it work on my Honor 7, not even a XML. Anyone wants to try? :fingers-crossed:
Thanks you all
Maybe an App developer will look here and we can get it.
I personally don't think it's really useful, because it's quite unprecise..
I suppose it´s the function that allows H7 to distinguish between double knuckle (capture screen) and a double tap.
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...
So here's a ROM that i would recommend even tho it's in beta Corvus OS it's android 12 and everything works even the Camera but sadly not the greatness of Sony's Camera app...i personally haven't tried it with the Custom Kernel Kirisakura just yet but i will and report back on here if they place nice together...Magisk also works great with this ROM you just have to be careful what you flash...
Hopefully our device will be fully supported soon.
Just putting down some thoughts here.
Double tap to wake is borked, the setting already hints that it is unlikely to work and I can confirm this.
Forcing native res works rather poorly. On reboot I need to reset the dpi to make the GUI play nice, but some things remain iffy. Such as:
Gesture navigation still thinks preview windows should be the lower res, not native (looks poor, see attached images)
Some random visual glitches that cause a silent crash + restore, it's not critical but you can see it happening
No built-in battery health (as in limiting it), have to use something external (AccA)
Camera quality is way worse compared to stock. I don't mind as much as I don't care a lot, but quality regression is very significant (if I have to quantify it, I would accept 20-30%, but this feels more like 60%)
The GCAM's I've found that don't immediately crash (not many) all have serious bugs
No camera app found that plays nice with front camera, hope you weren't planning on taking pictures with the front camera
Edit: For 6 you can actually use the native app. Performance is super bad though.
To not sound too much like a downer I'll also put in some "niceties" compared to stock.
Holding volume button to seek is now native
OTA work again
Good visual eyecandy for charging, locking and more
No bloatware galore
Much much finer control over lots of little things, especially status bar is very nice
Other things:
The default launcher is a bit lacking, so I installed Nova 7, but this still has some shenanigans with force reloading and short unresponsiveness with gesture navigation. Very annoying, but I'm quite sure this is not the fault of the ROM. Just hoped this was improved (suggestions welcome)
If someone found a good GCAM please share, the ones I've found are either broken or seriously lacking.
It seems that sometimes the phone does not respond to my finger until I press the button. This could be intentional to prevent accidental unlocks / phone being locked for X seconds because lots of "bad" fingerprints detected.
UsernameNotRecognized said:
Just putting down some thoughts here.
Double tap to wake is borked, the setting already hints that it is unlikely to work and I can confirm this.
Forcing native res works rather poorly. On reboot I need to reset the dpi to make the GUI play nice, but some things remain iffy. Such as:
Gesture navigation still thinks preview windows should be the lower res, not native (looks poor, see attached images)
Some random visual glitches that cause a silent crash + restore, it's not critical but you can see it happening
No built-in battery health (as in limiting it), have to use something external (AccA)
Camera quality is way worse compared to stock. I don't mind as much as I don't care a lot, but quality regression is very significant (if I have to quantify it, I would accept 20-30%, but this feels more like 60%)
The GCAM's I've found that don't immediately crash (not many) all have serious bugs
No camera app found that plays nice with front camera, hope you weren't planning on taking pictures with the front camera
Edit: For 6 you can actually use the native app. Performance is super bad though.
To not sound too much like a downer I'll also put in some "niceties" compared to stock.
Holding volume button to seek is now native
OTA work again
Good visual eyecandy for charging, locking and more
No bloatware galore
Much much finer control over lots of little things, especially status bar is very nice
Other things:
The default launcher is a bit lacking, so I installed Nova 7, but this still has some shenanigans with force reloading and short unresponsiveness with gesture navigation. Very annoying, but I'm quite sure this is not the fault of the ROM. Just hoped this was improved (suggestions welcome)
If someone found a good GCAM please share, the ones I've found are either broken or seriously lacking.
It seems that sometimes the phone does not respond to my finger until I press the button. This could be intentional to prevent accidental unlocks / phone being locked for X seconds because lots of "bad" fingerprints detected.
Click to expand...
Click to collapse
Yeah this is the only ROM that i found that legit decided to be custom and not just copy/pasta of Pixel Experience without the GCAM and a different name.....for what I use my phone for it's 100% functional...but it's far from being perfect for everyone rn...
Ainz_Ooal_Gown said:
Yeah this is the only ROM that i found that legit decided to be custom and not just copy/pasta of Pixel Experience without the GCAM and a different name.....for what I use my phone for it's 100% functional...but it's far from being perfect for everyone rn...
Click to expand...
Click to collapse
Yeah, this is why I've been very hesitant to install to install GSI ROMs, all the issues I've mentioned are because the X1 III is not the same as most other devices.
Wake to tap? Device specific thing.
Native res issues? X1III specific.
No built in battery health? Not device specific, devs pls
Camera issues? Device specific.
I think I'll drop the higher res as that will remove the most jarring of issues. The camera is whatever as it will not improve by switching to PE and double tap to wake is meh. Annoying at worst.
UsernameNotRecognized said:
Yeah, this is why I've been very hesitant to install to install GSI ROMs, all the issues I've mentioned are because the X1 III is not the same as most other devices.
Wake to tap? Device specific thing.
Native res issues? X1III specific.
No built in battery health? Not device specific, devs pls
Camera issues? Device specific.
I think I'll drop the higher res as that will remove the most jarring of issues. The camera is whatever as it will not improve by switching to PE and double tap to wake is meh. Annoying at worst.
Click to expand...
Click to collapse
True that...but hey it's there Incase people get bored lol
UsernameNotRecognized said:
Just putting down some thoughts here.
Double tap to wake is borked, the setting already hints that it is unlikely to work and I can confirm this.
Forcing native res works rather poorly. On reboot I need to reset the dpi to make the GUI play nice, but some things remain iffy. Such as:
Gesture navigation still thinks preview windows should be the lower res, not native (looks poor, see attached images)
Some random visual glitches that cause a silent crash + restore, it's not critical but you can see it happening
No built-in battery health (as in limiting it), have to use something external (AccA)
Camera quality is way worse compared to stock. I don't mind as much as I don't care a lot, but quality regression is very significant (if I have to quantify it, I would accept 20-30%, but this feels more like 60%)
The GCAM's I've found that don't immediately crash (not many) all have serious bugs
No camera app found that plays nice with front camera, hope you weren't planning on taking pictures with the front camera
Edit: For 6 you can actually use the native app. Performance is super bad though.
To not sound too much like a downer I'll also put in some "niceties" compared to stock.
Holding volume button to seek is now native
OTA work again
Good visual eyecandy for charging, locking and more
No bloatware galore
Much much finer control over lots of little things, especially status bar is very nice
Other things:
The default launcher is a bit lacking, so I installed Nova 7, but this still has some shenanigans with force reloading and short unresponsiveness with gesture navigation. Very annoying, but I'm quite sure this is not the fault of the ROM. Just hoped this was improved (suggestions welcome)
If someone found a good GCAM please share, the ones I've found are either broken or seriously lacking.
It seems that sometimes the phone does not respond to my finger until I press the button. This could be intentional to prevent accidental unlocks / phone being locked for X seconds because lots of "bad" fingerprints detected.
Click to expand...
Click to collapse
Alright some more shenanigans and needing to do a clean install further I do know some more things now.
1. is still broken, I'll try flashing a different kernel perhaps.
2. It's actually not so bad. It will remember and auto apply on reboot after a couple seconds. Gesture and notification bar may be slightly borked, but that's fixed fast by reloading system UI and switching between gesture and button navigation. The thing about recents has been resolved by switching to a different launcher with it's own quickswitch (lawnchair).
3. Acca works fine.
4/5/6 Nothing.
Another update.
2 is fine. Just don't use the built in launcher while forcing 4k. Just use lawnchair or something (+ quickswitch).
On another note, automatic brightness does NOT appear to work. This is quite the massive issue. I'm honestly a bit baffled how I haven't noticed until today.
AOD is also quite broken, while the phone is on the wireless charging and being ratiod to 90% it will continously blink. That's super annoying as I normally use AOD to check if I got a message, if it blinks it takes my attention, effectively defeating the entire purpose of AOD. *Groan*
These issues are really starting to stack up by now, I'm seriously considering reverting to stock. I'm really worried something else won't be working once I need it in the future.
UsernameNotRecognized said:
Another update.
2 is fine. Just don't use the built in launcher while forcing 4k. Just use lawnchair or something (+ quickswitch).
On another note, automatic brightness does NOT appear to work. This is quite the massive issue. I'm honestly a bit baffled how I haven't noticed until today.
AOD is also quite broken, while the phone is on the wireless charging and being ratiod to 90% it will continously blink. That's super annoying as I normally use AOD to check if I got a message, if it blinks it takes my attention, effectively defeating the entire purpose of AOD. *Groan*
These issues are really starting to stack up by now, I'm seriously considering reverting to stock. I'm really worried something else won't be working once I need it in the future.
Click to expand...
Click to collapse
No autobrighness may be caused by not having an overlay. I've also been annoyed by that on Pixel Experience. Can you create a fresh overlay for this phone and do a pull request with phhuson's repo? (I assume that's what must done)
thatguy222 said:
No autobrighness may be caused by not having an overlay. I've also been annoyed by that on Pixel Experience. Can you create a fresh overlay for this phone and do a pull request with phhuson's repo? (I assume that's what must done)
Click to expand...
Click to collapse
Well, sort of.
[Kernel][12.04.2023][Android 13] Kirisakura 3.0.1 for Sony Xperia 1 III aka "Sagami"
Kirisakura-Kernel for the Sony Xperia 1 III Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Sony Xperia 1 III aka Sagami. Sagami is the internal codename for this years development platform of Sony Mark III devices. Please...
forum.xda-developers.com
Issue is that the "official" info provided by Sony seems to explicitly disable double tap to wake.
This makes absolutely no sense as double tap to wake works fine in the vanilla ROM.
Maybe someone can confirm this? It's been some time.
UsernameNotRecognized said:
Well, sort of.
[Kernel][12.04.2023][Android 13] Kirisakura 3.0.1 for Sony Xperia 1 III aka "Sagami"
Kirisakura-Kernel for the Sony Xperia 1 III Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Sony Xperia 1 III aka Sagami. Sagami is the internal codename for this years development platform of Sony Mark III devices. Please...
forum.xda-developers.com
Issue is that the "official" info provided by Sony seems to explicitly disable double tap to wake.
This makes absolutely no sense as double tap to wake works fine in the vanilla ROM.
Maybe someone can confirm this? It's been some time.
Click to expand...
Click to collapse
It's available in stock but it has never worked correctly. The proximity sensor doesn't disable it! There's a "Prevent accidental operations with screen off" setting as the world's dumbest work-around. That puts a keyboard and alert on the screen while you're walking. It stops emergency butt-dialing but the battery still runs down.
kevinmcmurtrie said:
It's available in stock but it has never worked correctly. The proximity sensor doesn't disable it! There's a "Prevent accidental operations with screen off" setting as the world's dumbest work-around. That puts a keyboard and alert on the screen while you're walking. It stops emergency butt-dialing but the battery still runs down.
Click to expand...
Click to collapse
A what now? I do recall the proximity sensor not working really well with dt2w but at least it worked and I didn't notice some significant battery drain.
I did see some things about dt2w being disabled because the touch interface is powered when the screen is powered and this can't be decoupled. I'm not sure if this applies to this phone though.
Regardless, it shouldn't really matter as the X1 III is an OLED screen anyways. So as long as it's full black it should be fine(?)
I'm not asking for the perfect solution and if battery drain slightly increases that's a worthwhile investment to me. At least provide the option. Don't decide what I want because it has potential side-effects (just warn or something lol).
Actually I'm going out on a limb and stating that dt2w should be enabled by default if the device's screen is an OLED screen. Overlay and device specific things be damned.