Database Info

Some ICS 4.0 bugs and quirks

NOTE: This is a list of bugs for STOCK (NON-MODDED) ICS 4.0.3 & 4.0.4 (LC4, LD2, and LE2) (Most bugs from the initial LC4 leak fixed after the two major version leak updates) from DesignGears.
If you have flashed to ANY OTHER CUSTOM ICS 4.0 ROM, PLEASE WRITE IN THE DEVELOPERS' / ROM thread.
1 - 03/26/2012: When selecting "Contacts to Display" and selecting CUSTOMIZE LIST > Selecting ONLY Google Contacts (EXCLUDE G+).
Then you start typing someone's name, it returns contacts in SIM card and on Google contacts.
2 - 03/26/2012: Autocorrect on the included "Android Keyboard" doesn't work by pressing spacebar.....like it had been in previous 2.3.6. Even when changing setting to VERY AGGRESSIVE. FIXED IN UCLD2 LEAK
3 - 03/26/2012 [CONFIRMED] When deleting a message thread, the phone will freeze and turn into a blank screen (except notification bar) then the messaging app will close. FIXED IN UCLD2 LEAK
4 - 03/26/2012: [CONFIRMED] When using the "PHONE" icon to bring up dialer, contacts tab is no longer associated in it.
5 - 03/27/2012: 50/50 Users report more sensitivity on the touch screen, some report lack of sensitivity of touch.
6 - 03/27/2012: HOW TO take screen shot: Press AND HOLD ... VOL DOWN + POWER BUTTON for at LEAST 1-2 SECONDS. You will then be prompted to view the screenshot in notification bar / indicator.
METHOD #2 of taking screenshots: Press and HOLD Power button + HOME key.
7 - 03/29/2012: Some users report when tapping "RESTART" or "SHUTDOWN" on STOCK Power-button option, the phone will freeze. Either you have it or you don't. FIXED IN UCLD2 LEAK
7 - 04/02/2012: Users report echoing or unable to hear other party on an INCOMING call. This is a "hit or miss" bug.
8 - 04/02/2012: [CONFIRMED]Bluetooth stack in the new kernel has resolved a LOT of vehicle-to-android phone issue (static, drops, functions, etc.).
10 - 04/04/2012: [CONFIRMED BIG ISSUE] When creating a new contact in phone and setting it to GOOGLE CONTACTs; forcing a sync or auto-sync option will NOT push the contact to google servers for backup purposes. However, deleting or creating a contact while logged in on a full web browser will push it back to the phone via sync. FIXED IN UCLD2 LEAK
11 - 04/09/2012: [CONFIRMED] There are known issues with stock email app. Syncing unread/read e-mails will not push back to exchange server email client. Also emails me not completely send and stays "stuck" in outgoing box.
FIX (Thanks dixit):
This google thread shows the official issue and show that it was fixed officially in 4.0.4.
https://code.google.com/p/android/is...etail?id=23534
If you scroll down to post 51 you will see there is a link where someone put the two 4.0.4 APKs from a Spring Nexus S 4G which fixes this issue as explained above. So just go to that link, download the two Email/Exchange APKs, put them in System/App, correct permissions, remove your two Samsung Native Email APKs, and that will fix the issue of emails being stuck in the outbox.
Here is the direct link to those two APKs off Post 51
http://files.devphone.org/404mail/
11 - 04/15/2012: [CONFIRMED] When adjusting ringtone level in SETTINGS > SOUNDS, the ringtone level will not lower or raise; it stays at one level.
FIX: Adjust via volume rocker while in any other system screen (Home, MMS, etc) BUT NOT IN-APP. *Thanks petrochemicals!*

Here's what I found and posted in another thread...
So far so good except a few things:
1) I hate the fact that "contacts" are no longer visible in the dialer. Now I need another icon that I rarely use. The only option appears to hit menu and select contacts from there.
2) The "power off" and "restart" options in the extended power menu (hold power button down) seem to lock up and freeze whenever I try to use one of these thus requiring a battery pull. Anyone else experiencing this?
3) Can't use built in hotspot tethering anymore. This is something that I use with my tablet often. Any solutions other than a 3rd party app? If not, what app is everyone using for hotspot tethering?
4) Why in the world don't the signal bars turn green once fully connected? It's driving me crazy because normally that means its not connected to your Google account. This is the first time I've seen this (of MANY different Android phones). - This appears to be an ATT thing as other carriers and phones change the signal bars color when its connected to your google account (as it always should be).

Grey bars, works for for me; turning green = same color as battery = confusion to some it is acting as a double icon of ur battery? lol
I don't get a freeze in the menu.... I'm assuming you're talking about the built-in menu not a modded one? I just use the one that came with the ICS.
Hotspot tethering, you'll have to wait for a dev to mod that unless you are wanting an app for it.

I can tell you that I got my portable hotspot to work. It gave me numerous error messages though when I first went to set it up and the screen freezes when I turn it on. I went back to home and back to the hotspot settings and the toggle remained on. I changed the default password to all 9s bc I was getting an invalid password error. After that, I connected my old iPhone to the Skyrocket wi-fi.
I used to use Barnicle Wi-fi tether but it doesn't work now. Is there a difference between the stock portable wi-fi hotspot program on the phone and Barnicle? Im just curious if Barnicle masked the fact that the user was tethering.
Sent from my SAMSUNG-SGH-I727 using XDA

Yes, I'm referring to the built in power menu. I fixed permissions in CWM and still no go. Any ideas???

I find the keyboard to be a bit slow on the responsive side. Anyone else running into that or am I just trying to type too fast?

Perform a Factory data / reset?
I find the new keyboard fairly responsive vs the old one; I just thought i typed too fast for the old one lol. This one actually keeps up and Swype keyboard tapping works more fluent as well.

good job guys, keep up the troubleshooting so hopefully some devs will cook up a nice rom

fongz27 said:
Perform a Factory data / reset?
I find the new keyboard fairly responsive vs the old one; I just thought i typed too fast for the old one lol. This one actually keeps up and Swype keyboard tapping works more fluent as well.
Click to expand...
Click to collapse
I'll give that a spin. I did that once already to fix my home button problem, so I'll try and do another. But yea I use to use the ICS keyboard from the market on GB, and that was quick enough for me.

stuff I notice so far
I did notice the contact tab missing from dialer. The menu selected one doesn't allow right and left swipe for call/text. In the contacts app, the swipe works ok.
the only real problem for me, thus far, is when deleting SMS threads; messaging force closes.
Anyone else have that?
BTW thanks for starting this thread, wasn't sure where to post bugs - I think this may be usefull to keep them all in one spot.

Getting some odd behavior from Rom Mngr
Aside from other errors I got, when I ask ROM Mngr. to perform a task, I get a bunch of errors like "Messaging has failed," "Internet has failed," "com.google.xx" has failed. But then it goes and performs the request.
However! Whereas on 2.3.6 UCLA3, when requesting a backup via ROM Mngr., it would go straight to the backup whereas now, it goes into CWM and I still have to select Backup from the option there.

Deleting threads freezes my messaging also.
Sent from my SAMSUNG-SGH-I727 using XDA

Noticed a new one.
Not getting pictures with messages now, too.
Nvm. Damn - I hate bug posts. They come, they go.

The only thing I've noticed so far is I don't seem to get LTE in my house anymore. Boo...

I'm having issues with audio files. I can't use either Google Play Music, Samsung Music Player or Doubletwist to play audio. It creates duplicates which I believe corrupt the file itself.
Sent from my SAMSUNG-SGH-I727 using XDA

jayrod88 said:
2) The "power off" and "restart" options in the extended power menu (hold power button down) seem to lock up and freeze whenever I try to use one of these thus requiring a battery pull. Anyone else experiencing this?
Click to expand...
Click to collapse
I get it too, but there is no need for a battery pull if it freezes during a restart.
Press and hold the power button and the phone will restart after a few seconds.
It's a leak, not an official release, so I fully expected bugs.
Face unlock crashes a lot for me.
It fails o power on the camera and then the keypad doesn't respond for PIN input.
Requires a reboot.

rjohnstone said:
I get it too, but there is no need for a battery pull if it freezes during a restart.
Press and hold the power button and the phone will restart after a few seconds.
It's a leak, not an official release, so I fully expected bugs.
Face unlock crashes a lot for me.
It fails o power on the camera and then the keypad doesn't respond for PIN input.
Requires a reboot.
Click to expand...
Click to collapse
Did you do a complete ext4 wipe / format prior to ODIN ONE CLICK ?
Run factory data reset, then fix permissions and then reboot. Face unlock works perfect and pin input works.

fongz27 said:
Did you do a complete ext4 wipe / format prior to ODIN ONE CLICK ?
Run factory data reset, then fix permissions and then reboot. Face unlock works perfect and pin input works.
Click to expand...
Click to collapse
Yep.
Face unlock does work... just not all the time.

have you done "improve facial recognition " if so how many additional pictures did you take?

Facial unlock is perfect for me. No problems whatsoever.
Sent from my SAMSUNG-SGH-I727 using XDA

Accidentally hitting HOLD button during calls?

I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks

Unfortunately i can't help but i am getting the same issue
Sent from my SM-G930F using Tapatalk

I tried applying different dialer apps and they only serve to change the dialer/contact screens, but the default calling screen containing the HOLD button remains unchanged. I found that using Skype as the default dialer fixes this issue since it uses its own dialing/calling screens, but obviously it's not practical to just rely on Skype. So the problem still remains unresolved.

As an update, someone on Reddit posted a download link to the Google dialer app here at: http://forum.xda-developers.com/galaxy-s6/themes-apps/app-google-dialer-t3323432
This installs a new dialer, which actually provides a new calling screen as well, fixing the main issue. The default dialer is better in my opinion since it opens up the dial pad immediately while this one doesn't, but this is a good option at this point

gomulkaaa said:
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Click to expand...
Click to collapse
even worst than calls is when you press it while watching youtube vids, i wish there was a lock of some sort cuz the music stops paying all the sudden

It's embarrassing when I put my clients on hold and don't realise until they don't respond to me. The cheek hold doesn't result in any audible sound so you can be talking for 20 seconds with the other end on hold. I love the S7 edge but I'm contemplating sending it back. I'll try the Google dialer mentioned above first though

Same issue here. I talk on the phone almost 2 hours a day and this is happening at least 1-2 times in every call! Checked my proximity sensor and it's working as it should.
Any workarounds? Maybe someone can edit the phone.apk and remove this stupid button or disable it? I am against rooting but I will definitely root my phone if there's a fix for this.

Damn, I suffer exactly the same issue! Found this googling for ideas...

Very old thread, but I just wanted to give a suggestion to others with the same issue. I really love the Google Phone dialer app, which actually replaces the calling screen during calls with this app's own screen, so you no longer have the Hold button at such an unfortunate location. If you do choose Google's app, I recommend this specific version: http://www.apkmirror.com/apk/google-inc/google-phone/google-phone-2-05-07_rc4-release/google-phone-2-05-07_rc4-android-apk-download/
The caller-ID function by Google actually works with this version, whereas the other .apk files floating around do not have this function working properly.

I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.

robot1000 said:
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
Click to expand...
Click to collapse
Finally searched for the answer to this today, after several accidental holds on work calls.
The solution above with Google Phone APK worked for me. I just went to SETTINGS - APPLICATIONS - DEFAULT APPLICATIONS and then under Calling App near the top, changed it from Contacts to Phone. . For some reason, I cannot open the phone app itself (gives an error message) but calls do use the phone app rather than Samsung stock dialer.

Turn off screen!! Most phones allow you to turn screen off without interrupting the call.

Same issue with a galaxy A5 2016
Can't understand why samsung doesn't fix it

Anyone else experiencing dropped tap inputs?

On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.

Yes, this is me too exactly. Same thing with the dev option too. Not sure if I should wait for 8.1 or if it's hardware and RMA it. Frustrating because I like this phone.

I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.

I have definitely noticed this as well, happy to know it wasn't just me

cb474 said:
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
Click to expand...
Click to collapse
I tried a reset but the issue still showed up. In fact it happened twice on the first time setup stuff afterwards. I called Google and we went through the motions and reset it from recovery mode but it was still there when I was testing it the next couple hours. Anyway, we're doing the RMA thing. I'll let you guys know how it works out when I get my new phone.

Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.

I find that it occurs when I'm in a small room with the heat turned up. The sensitivity of the touch screen seems to depend a lot on moisture. If I keep my fingers moist (or wear a touch sensitive glove) it works a heck of a lot better.

ritzack said:
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
Click to expand...
Click to collapse
That's good and bad news I guess, hopefully just needs a software update. I have a replacement coming Monday, but I kind of expect no improvement and that this is just a common thing that a lot of people aren't noticing

I noticed that for a while in Google Play Books, in which I tap the screen frequently to turn pages. I tried a factory reset, which didn't help. I tried running in safe mode and testing on Maps and still had a problem, although less frequently (a higher percentage of taps worked). Then it started to work better. We'll see if that lasts.
I tried flicking as opposed to tapping and flicking always works.
I'd suggest posting on the Pixel product forum or calling support, so that Google becomes more aware of the issue. There are some threads on the subject on reddit and the product forum.

Out of interest are you noticing it any particular parts of the screen?
I've noticed it a few times but it's been on areas of the screen near the edges.
I assumed it was some sort of palm rejection thing going on it the background with it thinking I'm accidently mashing the display.

With me it was the right edge toward the middle, as that's where you tap to turn the page in Play Books.

I get it on the back button frequently, but it happened just now in the middle of the screen when I typed the text input box to start writing this

I think this is the whole OS hanging/freezing briefly actually, not a touchscreen input issue
- Pressing the hardware unlock button can get ignored (both locking/unlocking)
- Scrolling from a quick flick + release can suddenly stop (no additional inputs)
So most likely this is a software issue, hopefully fixed in an upcoming update? It's kinda annoying

Did you change the DPI or font size? I go back to default and it seems that everything is good now.
---
update: no it happens again…

nonexistent said:
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Click to expand...
Click to collapse
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..

Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes

Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting any m.reddit thread in chrome and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes

nonexistent said:
Haven't changed the DPI or font size
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
So, I replicated what you told me, 3x. I didn't miss any taps, and no system hang/missed input..
hmm

Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.

nonexistent said:
Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
Yeah, sometimes I see a tap register visually on the screen, but the intended action doesn't happen.
redandblack1287 said:
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
Click to expand...
Click to collapse
It's funny. I had the issue. Did a factory reset. Felt like it was better. But now that I'm thinking about it more I notice it a lot. So I can't tell if it's really different. Before I figured I'd made a mistake. Now I think it's the phone. Damn you phone!
Anyway, I notice that the issue tends to happen more or less randomly, at any position on the screen. Also, sometimes the same tap fails to register twice in a row, but once it's starts working all subsequent taps that come in a row work (say I'm clicking through a lot of menu items in some settings). So maybe that lends some credence to the idea that there is a system for registering the taps that is not waking up and once it does it works fine.
Perhaps related, I have my ambient display set to wake on double tap. Before the Nov update it hardly worked. Now it seems to be working reliably.

Android 9 (Pie) - Bugs after Update

Hello to the XDA Dev Community.
I'd like to start a threat with bugs after the Android Pie update on our devices.
1. Bug:
Camera App forgets the "volume down key" binding. Means, when double pressed in standby mode the cam is not started.
Solution: Sadly this works only temporary - start the cam app and exit or close. After that the above mentioned shortcut / quickstart works for a short time in standby mode.
2. Bug:
This one is still not repaired: when switching to black mode (to lower the battery consumption) one can not see in the apps overview which of the apps are deactivated - the letters are not visible. When you have the white menues, the term "deactivated" is quite readable. (This bug is existent from the beginning with Android 8 - i chatted on this topic with the customer service of Huawei last year but that guy had no blink of an idea, he sounded very unexperienced.)
My Device:
Unbranded, European version, yesterday received the update.
Wonder if anyone experienced same difficulties and perhaps if there are solutions to this.
Have a good day

Whenever you do a significant upgrade, do a factory reset. This cures most problems, people need to start doing this rather then moaning.

Quite a good idea - but I am long enough into the smartphone scene (since Windows CE and Mobile) to know well that "factory reset" is unfortunately not the magic solution to all problems as some would like it to be...
Of course factory reset is done. Problems are still there, and to be honest - we would have not awaited it as a solution to both bugs i mentioned above a priori, would we?
Well besides I recognized another bug or feature(?)
3. Bug (or feature?):
The native mail app no more shows contacts pictures left to the associated mails.
Does someone know if this is somehow configureable?
Thx in advance

Hi,
found next bug.
4. Bug:
Fast double tapping the "square button" works inconsistently.... It should switch between the two last apps in the tasklist..... May be it has to do with a little time delay / time lag in reaction of EMUI9/Pie... I have the slight feeling that the OS is not that fluent as before (under Android 8)
I hope that is it....

That AI thing in the left most corner in the camera APP is not working, it is the same button as the one you see next to the search bar when you swipe down for searching. I think it used to be some kind for scanner or products? Now the button just flicks and does nothing.

ppcppcppc said:
Hi,
found next bug.
4. Bug:
Fast double tapping the "square button" works inconsistently.... It should switch between the two last apps in the tasklist..... May be it has to do with a little time delay / time lag in reaction of EMUI9/Pie... I have the slight feeling that the OS is not that fluent as before (under Android 8)
I hope that is it....
Click to expand...
Click to collapse
Put High performance... I don't know where (probably battery settings?) As I haven't received yet OTA but seems that with that setting the double tap on square against slopes to switch between apps fluently

kotidoti said:
That AI thing in the left most corner in the camera APP is not working, it is the same button as the one you see next to the search bar when you swipe down for searching. I think it used to be some kind for scanner or products? Now the button just flicks and does nothing.
Click to expand...
Click to collapse
Working on my device, I had to confirm the consent before... Maybe u clicked it into the background?
Update:
I deactivated the corresponding Huawei app (HiVision), now it fully disappeared in the cam app and on the lock screen (formerly found at the bottom when you swiped from down to up... The list where the flashlight, calculator and so on appear)

Hey there,
Have you tried to go to battery optimisation (go to settings, hit the search bar on top and start writing "optim" and the first one), then search for "camera" and disable battery optimisation. It solved the problem for me.
I've found that the Pie is more aggresive overall with killing the background apps. I've had to add way more applications (than on droid 8) to the "disable battery optimizations" and to "app launch" (in settings, battery, app launch -> set applications that you want to survive on the background to "manage manually")
ppcppcppc said:
Hello to the XDA Dev Community.
I'd like to start a threat with bugs after the Android Pie update on our devices.
1. Bug:
Camera App forgets the "volume down key" binding. Means, when double pressed in standby mode the cam is not started.
Solution: Sadly this works only temporary - start the cam app and exit or close. After that the above mentioned shortcut / quickstart works for a short time in standby mode.
2. Bug:
This one is still not repaired: when switching to black mode (to lower the battery consumption) one can not see in the apps overview which of the apps are deactivated - the letters are not visible. When you have the white menues, the term "deactivated" is quite readable. (This bug is existent from the beginning with Android 8 - i chatted on this topic with the customer service of Huawei last year but that guy had no blink of an idea, he sounded very unexperienced.)
My Device:
Unbranded, European version, yesterday received the update.
Wonder if anyone experienced same difficulties and perhaps if there are solutions to this.
Have a good day
Click to expand...
Click to collapse

jcalderonv74 said:
Put High performance... I don't know where (probably battery settings?) As I haven't received yet OTA but seems that with that setting the double tap on square against slopes to switch between apps fluently
Click to expand...
Click to collapse
Thanks, will try your idea!
OTA Update: Against all info - the update was found by manual search in the standard system settings. As it was found I parallely checked HiCare App - NO updates were found, it was a joke!
So maybe also check this way, do not trust HiCare alone.
Update:
Found and activated the performance mode (as you said - battery settings). Sadly no change in performance of the app-switching.

Ereniemis said:
Hey there,
Have you tried to go to battery optimisation (go to settings, hit the search bar on top and start writing "optim" and the first one), then search for "camera" and disable battery optimisation. It solved the problem for me.
I've found that the Pie is more aggresive overall with killing the background apps. I've had to add way more applications (than on droid 8) to the "disable battery optimizations" and to "app launch" (in settings, battery, app launch -> set applications that you want to survive on the background to "manage manually")
Click to expand...
Click to collapse
You made my day, thx!
Disabling the battery optimization for the cam app is the solution. It works even after restart of the device without starting the cam app before!
Thx again!

jcalderonv74 said:
Put High performance... I don't know where (probably battery settings?) As I haven't received yet OTA but seems that with that setting the double tap on square against slopes to switch between apps fluently
Click to expand...
Click to collapse
Hi,
It helps a bit, but still inconsistently working, even after restart of the device. I also tried to put EMUI into the AppAssistant app to enforce it, but the app is not selectable (guess it should be HiStart, EMUI or something like that)...
Only solution atm is to SLOWLY double-tapping the square button.

ppcppcppc said:
Working on my device, I had to confirm the consent before... Maybe u clicked it into the background?
Update:
I deactivated the corresponding Huawei app (HiVision), now it fully disappeared in the cam app and on the lock screen (formerly found at the bottom when you swiped from down to up... The list where the flashlight, calculator and so on appear)
Click to expand...
Click to collapse
Update on this issue, I tried to clear data and cache which brought me back to give consent again and all but it still didn't work. What I did was disable it, which tuned it into factory default and then enabled it again and wolah, it works again. Thanks for informing me about the app name btw, would have been impossible without it. HiVision.

Calendar invites for office365 meetings cannot properly be accepted on the device. it sends the originator a 'not supported format.ics' file - rather than actually accepting the meeting.
Pretty stupid tbf. I'll look to move off the standard mail client i reckon

My P20 Pro (C782) finally prompted me to updated to Pie today, but having done so I'm experiencing choppy / clipping / stuttering audio when connected to my Sony WH-1000XM3's (using LDAC codec). This wasn't happening on Oreo at all.
I've done a factory reset, but the issue persists. Happens throughout whatever's playing (Spotify, Tidal, PocketCasts, YouTube) and is especially noticeable when pressing the power button to activate the screen.
Any ideas?

Anyone else having problems with the volume rocker?
I can't slide the volume to the left to get multiple profiles. Isn't it possible with the pie update?

zizzyboi said:
Anyone else having problems with the volume rocker?
I can't slide the volume to the left to get multiple profiles. Isn't it possible with the pie update?
Click to expand...
Click to collapse
Wonder if the volume rocker is not vertically orientated in Pie. Mine is working good, sliding down goes to silent. Above the slider is a button for vibration, sound and silence.

AWretchSavedByGrace said:
My P20 Pro (C782) finally prompted me to updated to Pie today, but having done so I'm experiencing choppy / clipping / stuttering audio when connected to my Sony WH-1000XM3's (using LDAC codec). This wasn't happening on Oreo at all.
I've done a factory reset, but the issue persists. Happens throughout whatever's playing (Spotify, Tidal, PocketCasts, YouTube) and is especially noticeable when pressing the power button to activate the screen.
Any ideas?
Click to expand...
Click to collapse
Hi, seems to be known and somehow a bug in Android 9 with Huawei components, let us hope for updates...
https://forum.xda-developers.com/huawei-p20-pro/help/bluetooth-issues-android-pie-clt-l29-t3889110

Naffets said:
Calendar invites for office365 meetings cannot properly be accepted on the device. it sends the originator a 'not supported format.ics' file - rather than actually accepting the meeting.
Pretty stupid tbf. I'll look to move off the standard mail client i reckon
Click to expand...
Click to collapse
Sounds to be a limitation by Huawei software...
I also recognized following bug (Android 8 & 9):
If I configure any mail account to "manually" in the native Huawei mail app, the app still looks for mails after a time when i only open the inbox....
Same situation when device goes into ultra power saving mode or automatically powers off because of low power....after return to normal state or reboot after charge the app now looks on all mail accounts for new messages itself/automatically. This happens when WIFI was on before powersaving mode or power off. As soon WIFI is available at startup or return to normal mode aforementioned situation occurs.... Can be avoided by canceling WIFI connection to the server/router....
That is indeed annoying!

ppcppcppc said:
Wonder if the volume rocker is not vertically orientated in Pie. Mine is working good, sliding down goes to silent. Above the slider is a button for vibration, sound and silence.
Click to expand...
Click to collapse
And what does sliding to the side do?
It should show all the profiles like media, alarm and phone volume? No?

I noticed that the homescreen shortcuts, that arised if you press and hold on the Phone Manager icon, were removed. Too bad, would link the power mode to homescreen. Even better would be a shortcut in the Quick Settings.

Text input unresponsive after unlocking phone?

Sorry for the weird title, I didn't really know how to concisely describe this issue. I still don't fully understand what triggers it but basically I've noticed that if I lock my phone while on a text chat (in either Textra or Facebook Messenger but probably includes all text chats), then unlock it to reply, I can't click on the text input box or hit the navbar back button for 3-5 seconds. This can also happen while my phone is unlocked when I'm switching through apps so I wouldn't directly blame the action of being locked. I know the phone isn't frozen because I can still hit the back button at the top left corner of the screen fine.
It almost looks as if though it's navbar-related because the pill is white when I unlock the phone, then after a few seconds when it's responsive again the pill is grey. My previous phone was a Oneplus 3 and it never had any issues like this (although it had physical buttons for navigation, not a navbar) so I'm wondering if this is an issue or if this is by design for some reason. I've tested each of the navbar options (traditional navbar, pill, and gesture) and none of them resolve the issue so maybe it really isn't.
One other detail I noticed is that the cursor also doesn't blink for those 3-5 seconds, and then when it starts blinking again I can start typing so it could be something else.
I just find it annoying to have to wait a few seconds whenever I want to unlock my phone and reply to a text and this doesn't seem like regular behaviour, has anyone else heard of or experienced this and know of a fix?
Videos of the issue:
In Textra:
https://imgur.com/X0lw47J
In Facebook Messenger:
https://imgur.com/1IrRfPY

It could be part of the same ghost touch bug. Did you tried to disable NFC and see if those input lags reduce?

ducted said:
It could be part of the same ghost touch bug. Did you tried to disable NFC and see if those input lags reduce?
Click to expand...
Click to collapse
I've had NFC disabled since I got the phone so that isn't it.
I don't think it's ghost touch-related since it doesn't happen sporadically, it just seems to be when I open a text chat app or something too quick which doesn't make sense. Perhaps I can record the issue and upload a video to more clearly show what happens.

I just added videos of the issue to the OP.

That looks weird, did you tried to use the gesture navbar only or the one with all the buttons? I would try also another keyboard just to discard any GBoard related issue.

I've tried every other navbar type (including the one with just gestures and no bar) and the results are the same. I have also tried a different keyboard (Fleksy) and again, same issue. I had essentially the exact same setup as far as apps go on my Oneplus 3 and its fine, so I'm thinking it has to do with either a new version of android or the new OxygenOS but I have no idea.