Database Info

[Q] Tablet screen staying on when the netbook is "closed"

I distinctly remembering when i first got my dock that when i closed the tablet down tot eh keyboard, the screen automatically shut off. For some reason now, with Netformer and Prime 1.5, it no longer does. Anyone know of a fix? I cant even turn it off with the power button if its closed up.

I was having this problem when I had automatic brightness on. I'm on the same rom and kernel.
Sent from my SPH-D700 using XDA App

Turn the touchpad off using the shortcut on the keyboard. Will keep the screen from coming back on when device is closed.

which shortcut is that?

Bonetwizt said:
which shortcut is that?
Click to expand...
Click to collapse
Ist on the physical keyboard where F3 would be on a PC. Between the Bluetooth and Screen Dim keys. I had the same problem and turning it off fixes it.

Ding911 said:
Ist on the physical keyboard where F3 would be on a PC. Between the Bluetooth and Screen Dim keys. I had the same problem and turning it off fixes it.
Click to expand...
Click to collapse
Yep, that's the one I was referring to. Turning off the touchpad will solve the problem of the screen coming back on. At least until Asus completely fixes the issue with a firmware update. And hopefully that update includes a fix for the overall battery drain on the dock that many people, including myself, are reporting to have.

Mine stayed on a couple of time but it was a specific app keeping it awake .... cant for the life of me recall which app though

[q] major bugs in samsung droid charge

Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.

nikchapman said:
Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.
Click to expand...
Click to collapse
I haven't experienced any of the problems you bring up.
Sent from my Gummy Charged GBE 2.0 using xda premium

1. Are you sure that you are not pressing the power button while in the camera application. Doing so will toggle the screen lock and appear to freeze the phone.
Sent from my SCH-I510 using Tapatalk

I haven't experienced any of those issues either.
As for number 4, I think that was a conscious design decision. I don't really like it either, but you can use Tasker or Locale to detect when you're in a call and change your timeout to whatever you want.

nikchapman said:
Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
Click to expand...
Click to collapse
Have not experienced on my stock Charge nor on my rooted Charge. Just tried both to try to get this to happen.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
Click to expand...
Click to collapse
Never had this issue on either phone.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
Click to expand...
Click to collapse
When you have the auto brightness turned off you can push and hold the notification bar and slide your finger to the right or left to raise/lower brightness. Is it possible you are doing this?
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
Click to expand...
Click to collapse
The phone isn't supposed to be waken by shaking it. You can change the time-out timing through the settings. I've never hung up the phone via the power button so I can't even comment on that one.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.
Click to expand...
Click to collapse
Out of curiosity, are you on EE04?

I have not experienced any of these on the 3 months with my phone. It locked up maybe once on the camera but never more than that.

I've had none of these issues and furthermore I second the above thoughts regarding locking three camera and the status bar brightness.
Sent from my SCH-I510 using xda premium

Count me in the camp that says I havent seen any of those issues. As far as the camera goes, the only issue is the substandard SD card that Sammy sends. You cannot record in HD because the card speed is too slow.
All the other issues you are seeing are unique.
Search these forums for them, if others have had the problem you will find someone asked about it.
If you do find them, I am sure that they will be very isolated.

I couldn't say about a totally stock phone as I flashed mine to gummy 1.9.1 on its very first boot, but I have never had a single problem with my phone.
I absolutely LOVE this thing, I have owned a TON of phones and IMHO this is hands down the best phone I've ever owned.
My boss bought a new Bionic last Friday and after playing with it for the day Friday I wouldn't swap my phone even for the Bionic (among other things, the screen SUCKS on the Bionic). My boss doesn't like it either, he is returning it tomorrow.
~John

Never experienced number 1,2 or 4. But I have experienced number 3. Only happens though every couple of weeks. Hardly ever basically. It is weird though. I have no idea why my brightness changes even with my auto brightness off. Still a great phone though.
Sent from my GummyCHARGED Charge using Tapatalk

kelmar13 said:
Have not experienced on my stock Charge nor on my rooted Charge. Just tried both to try to get this to happen.
Never had this issue on either phone.
When you have the auto brightness turned off you can push and hold the notification bar and slide your finger to the right or left to raise/lower brightness. Is it possible you are doing this?
The phone isn't supposed to be waken by shaking it. You can change the time-out timing through the settings. I've never hung up the phone via the power button so I can't even comment on that one.
Out of curiosity, are you on EE04?
Click to expand...
Click to collapse
Omg just read your post about the auto brightness. Never knew that. Thanks!
Sent from my GummyCHARGED Charge using Tapatalk

piizzadude said:
As far as the camera goes, the only issue is the substandard SD card that Sammy sends. You cannot record in HD because the card speed is too slow.
.
Click to expand...
Click to collapse
Mine must have come with a different card as I have had no problem recording in HD (I just tried it again to make sure)

ms0chez said:
Omg just read your post about the auto brightness. Never knew that. Thanks!
Sent from my GummyCHARGED Charge using Tapatalk
Click to expand...
Click to collapse
Lol, anytime!
It's a feature I don't think I could live without now.

I can honestly agree with ur first concern. My camera is wonky. I can take pics all day without flash enabled. But I turn on the flash and try to focus (tap to focus), and as soon as the pic is snapped, the screen goes black, causing me to do a battery pull. Happened to me on my former Charge, my current replacement Charge and my wife's Charge. Happened on stock unrooted, stock rooted, and with custom Roms on all firmware versions. And I can easily replicate it.
Sent from my SCH-I510 using XDA Premium App

Please use the Q&A Forum for questions Thanks
Moving to Q&A

nikchapman said:
Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.
Click to expand...
Click to collapse
Sounds like you have some sort of agenda. Seeing as how nobody here so far has experienced this issues your referring to, I would say nothing is "obvious" at this point, nor do any of the issues above seem to be "serious", save for maybe the camera lockup issue but that very well could be user ignorance.

jpolzner said:
Sounds like you have some sort of agenda. Seeing as how nobody here so far has experienced this issues your referring to, I would say nothing is "obvious" at this point, nor do any of the issues above seem to be "serious", save for maybe the camera lockup issue but that very well could be user ignorance.
Click to expand...
Click to collapse
I think the fact that he is a journalist with some very pointed questions is the dead giveaway for his agenda. He's looking for a sensationalist angle to play for an article. Whether it's against Verizon or Samsung, I don't know, but it's pretty certain he came here with an agenda.

jpolzner said:
Sounds like you have some sort of agenda. Seeing as how nobody here so far has experienced this issues your referring to, I would say nothing is "obvious" at this point, nor do any of the issues above seem to be "serious", save for maybe the camera lockup issue but that very well could be user ignorance.
Click to expand...
Click to collapse
Well put, I agree 100%
~John

never experienced those issues either..probably a android issue..
Sent from my Gummy Charged GBE 2.0 using XDA App

I've had my Charge for about three months. I ran bone stock EE4 for a few weeks and have been using the various iterations of Humble Roms ever since. I never encountered any of the 4 issues brought up by the OP.
As for HD recording, I recall posts mentioning that some phones shipped with class 2 and some with class 4 sd cards. I got a class 4 card in mine and I've never had an issue with recording HD. Likely the source of the recording issue.

Nexus 5 extremely slow and stutter from boot after screen replacement

Hi, I replaced myself the screen (preassembled screen+digitizer+frame). After the replacement everything worked perfectly for like two hours when i rebooted it, from then on it is extremely laggy and stutters from boot animation, and when I press the power button (or when the screen shuts down), the phone itself shut down. In bootloader it doesn't seem to have problems.
I checked every connection inside the device (I've disassembled ad reassembled it several times).. thinking of a software problem, I've flashed marshmallow stock rom frist, and kitkat 4.4.4 then... but it's the same with any factory image.
Maybe I damaged something on the mainboard?
I also made a video to explain the problem:
with a lot of patience I set up a google account and downloaded cpu-z to see if maybe temperature sensor where giving wrong information to the system, but they're fine and everything seems to work propely aside from the stutter.
thanks to anyone who will help me, I'm almost giving up

RedMaio said:
Hi, I replaced myself the screen (preassembled screen+digitizer+frame). After the replacement everything worked perfectly for like two hours when i rebooted it, from then on it is extremely laggy and stutters from boot animation, and when I press the power button (or when the screen shuts down), the phone itself shut down. In bootloader it doesn't seem to have problems.
I checked every connection inside the device (I've disassembled ad reassembled it several times).. thinking of a software problem, I've flashed marshmallow stock rom frist, and kitkat 4.4.4 then... but it's the same with any factory image.
Maybe I damaged something on the mainboard?
I also made a video to explain the problem:
with a lot of patience I set up a google account and downloaded cpu-z to see if maybe temperature sensor where giving wrong information to the system, but they're fine and everything seems to work propely aside from the stutter.
thanks to anyone who will help me, I'm almost giving up
Click to expand...
Click to collapse
It's probably touch lag from the new screen, u probably got a bad one, contact who sold it to u, get a new one
Sent from my Nexus 6 using Tapatalk

soupysoup said:
It's probably touch lag from the new screen, u probably got a bad one, contact who sold it to u, get a new one
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I thought of that, but the fact that the haptic feedback (like the one you have entering app drawer, or returning home) is perfectly sync without lags made me think the touch was ok... and even twrp recovery was working smoothly (coudn't show in the video since I factory flashed kitkat)

RedMaio said:
I thought of that, but the fact that the haptic feedback (like the one you have entering app drawer, or returning home) is perfectly sync without lags made me think the touch was ok... and even twrp recovery was working smoothly (coudn't show in the video since I factory flashed kitkat)
Click to expand...
Click to collapse
What about stock Marshmallow?
Sent from my Nexus 6 using Tapatalk

soupysoup said:
What about stock Marshmallow?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
with 6.0 shuts down after boot animation (and reproduces it stuttered like the kitkat one in the video).
Right after the screen replacement, stock marshmallow was working fine for a while

That's very strange indeed, OK so try this, go into developer setting and check disable HW overlays, and check force GPU rendering, this will make the phone use the GPU for UI stuff, possibly fixing ur studdar, let me kno
Sent from my Nexus 6 using Tapatalk

soupysoup said:
That's very strange indeed, OK so try this, go into developer setting and check disable HW overlays, and check force GPU rendering, this will make the phone use the GPU for UI stuff, possibly fixing ur studdar, let me kno
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
OK, I've just tried... can't tell any differences.
I was thinking that the main way to solve this could be to investigate on the fact that turning off the display (both with power button or by itself after 30sec), shuts down the entire device. Could this be an hardware failure? (maybe generated by a physical damage that I caused)
thank you BTW

RedMaio said:
OK, I've just tried... can't tell any differences.
I was thinking that the main way to solve this could be to investigate on the fact that turning off the display (both with power button or by itself after 30sec), shuts down the entire device. Could this be an hardware failure? (maybe generated by a physical damage that I caused)
thank you BTW
Click to expand...
Click to collapse
That's very weird, what did u replace, and how did u do the replace, did u do the frame as well, and when u took the batt out did it come out easy it did u fight with it, I've heard cases of this happening, and other issues caused by damaging the battery during a fix
PS, no problem man, I know exactly how u feel lol
Sent from my Nexus 6 using Tapatalk

soupysoup said:
That's very weird, what did u replace, and how did u do the replace, did u do the frame as well, and when u took the batt out did it come out easy it did u fight with it, I've heard cases of this happening, and other issues caused by damaging the battery during a fix
PS, no problem man, I know exactly how u feel lol
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I bought a pre-assembled frame-display-touch. The battery came out easily even if I slightly forced it in the bottom. Anyway before replacement the battery was completely discharged... it has been completely discharged for almost two months since I broke the lcd in September. Left the phone disassembled on the desk for two days. After reassemble I plugged in a 2A Samsung charger to fill it up... initially everything was working properly, made a few photos with both cameras to check, a call and some random checks.. still on charge. On the second call I made, the microphone stopped working, so was the third... turned off the device, back on and everything was messed up like it is now.
Well a battery failure could actually make sense...
Inviato dal mio SM-T805 utilizzando Tapatalk

hey i have exactly the same problem with my nexus 5, i haven't opened it neither changed battery or screen but i'm suffering the same issue since a few days ago. have you managed to find a fix?. in my case it just started to do that suddenly. as in the video is totally unusable, i reinstalled latest stock firmware throught the recovery menu but with no luck, everything is ultra slow now
RedMaio said:
I bought a pre-assembled frame-display-touch. The battery came out easily even if I slightly forced it in the bottom. Anyway before replacement the battery was completely discharged... it has been completely discharged for almost two months since I broke the lcd in September. Left the phone disassembled on the desk for two days. After reassemble I plugged in a 2A Samsung charger to fill it up... initially everything was working properly, made a few photos with both cameras to check, a call and some random checks.. still on charge. On the second call I made, the microphone stopped working, so was the third... turned off the device, back on and everything was messed up like it is now.
Well a battery failure could actually make sense...
Inviato dal mio SM-T805 utilizzando Tapatalk
Click to expand...
Click to collapse

pyroxine said:
hey i have exactly the same problem with my nexus 5, i haven't opened it neither changed battery or screen but i'm suffering the same issue since a few days ago. have you managed to find a fix?. in my case it just started to do that suddenly. as in the video is totally unusable, i reinstalled latest stock firmware throught the recovery menu but with no luck, everything is ultra slow now
Click to expand...
Click to collapse
I didn't fix it eventually... but from my experience in fixing PCs, I believe that it could actually be a power issue related to either the battery or some power circuit.
If you've nothing to lose and some dollars to spend, you could try a new battery and see if it works!

EMUI 5 annoying bug

After turning on power saving mode then turning it off, brightness is changing when opening some apps like dialer and google chrome. Similar to EMUI 4.1 when power mode was set to smart but it is happening even when off in EMUI 5.
Before turning on power saving mode for the first time, brightness was always constant.

spix123 said:
After turning on power saving mode then turning it off, brightness is changing when opening some apps like dialer and google chrome. Similar to EMUI 4.1 when power mode was set to smart but it is happening even when off in EMUI 5.
Before turning on power saving mode for the first time, brightness was always constant.
Click to expand...
Click to collapse
It's a known issue and was reported over a month ago on b317.
It happens without ever using power saver on some phones
Sent from my FRD-L04 using Tapatalk

clsA said:
It's a known issue and was reported over a month ago on b317.
It happens without ever using power saver on some phones
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
In emui 4.1, brightness is supposed to reduce in some apps whilst set to 'smart'
In emui 5 when you enabled power saving mode, it reduces the overall brightness. But when you turn it off, the overall brightness goes back to normal but now the brightness is acting like it did in emui 4.1 whilst set to smart. It reduces in some apps. Tried restarting phone but doing the same thing.
I'm using Chinese rom b368 released 2 days ago

clsA said:
It's a known issue and was reported over a month ago on b317.
It happens without ever using power saver on some phones
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
Is there any fix? Really annoying me every time I open up chrome the brightness changes, then again when you exit it. How do bugs like this even get past testing, so obvious.
Also is your option for reducing screen resolution working? Doesn't seem to do anything for me, worked fine in 4.1. Now it just stays at 1920x1080 when I enable it instead of dropping to 1280x720

spix123 said:
Also is your option for reducing screen resolution working? Doesn't seem to do anything for me, worked fine in 4.1. Now it just stays at 1920x1080 when I enable it instead of dropping to 1280x720
Click to expand...
Click to collapse
Not working, noticed that too!

This is probably due to the fact that EMUI 5 is still in it's Beta stage and has allot of bugs that need to be ironed out before it's commercial release.

DarkGuyver said:
This is probably due to the fact that EMUI 5 is still in it's Beta stage and has allot of bugs that need to be ironed out before it's commercial release.
Click to expand...
Click to collapse
On second thought I believe that screen brightness and connected power management is managed much worse then under EMUI 4. Power saving is accessible only through settings and it takes over screen brightness management completely. Besides it doesn't work well.

piskr said:
On second thought I believe that screen brightness and connected power management is managed much worse then under EMUI 4. Power saving is accessible only through settings and it takes over screen brightness management completely. Besides it doesn't work well.
Click to expand...
Click to collapse
Hopefully the actual release of Nougat with fixes these problems.

@spix123 putting brightness too 100% works as a temp workaround

clsA said:
@spix123 putting brightness too 100% works as a temp workaround
Click to expand...
Click to collapse
Yep but that's no go indoors, personally I always leave brightness at around 60% unless its really bright outside

spix123 said:
Yep but that's no go indoors, personally I always leave brightness at around 60% unless its really bright outside
Click to expand...
Click to collapse
I did it, you get use to it pretty quickly
Sent from my FRD-L04 using Tapatalk

DarkGuyver said:
This is probably due to the fact that EMUI 5 is still in it's Beta stage and has allot of bugs that need to be ironed out before it's commercial release.
Click to expand...
Click to collapse
I'm on the very latest China release which is much more frequent than international and the bug is still there. Hopefully its not one of those bugs that people aren't reporting enough and will be stuck in it for months

Where can I fill bug reports. Those things are annoying.
Brand new phone, updated to nougat throu HiCare. Brightness in chrome, gmail and file manager changes every time when I open them. Also the powersaving option with lower resolution doesnt work for me either.

spix123 said:
After turning on power saving mode then turning it off, brightness is changing when opening some apps like dialer and google chrome. Similar to EMUI 4.1 when power mode was set to smart but it is happening even when off in EMUI 5.
Before turning on power saving mode for the first time, brightness was always constant.
Click to expand...
Click to collapse
I have the same issue, did you fix it?

I realized that lowest brightness level in EUMI 5 is brighter than in EUMI 4.1 ??

Really stupid bug that shows how poor emui developers are. Still in latest chinese developer rom, no sign that developers are even aware of the problem. Don't know how so few little people are reporting this, must be blind.
It should only happen when power saving mode is enabled like it did in older emui.
It causes so many problems. I have screen set to my preferred brightness then it dims so much when I open browser that I have to increase brightness every time. The only work around is to use 100% brightness all the time, then it does not dim the screen but this just a stupid waste of battery and bad for your eyes indoors.

clsA said:
It's a known issue and was reported over a month ago on b317.
It happens without ever using power saver on some phones
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
Is it still there on latest EU rom?
I'm using latest chinese developer updated yesterday and still happening

spix123 said:
Is it still there on latest EU rom?
I'm using latest chinese developer updated yesterday and still happening
Click to expand...
Click to collapse
Yeah its still there on emui 5.0 and 5.1 i have mate 9 pro and p10 plus and both of them has the same issues

Ok, now we are in november and the problem persists -_-

What benefits have you noticed from 9.5.7 OTA and what's still broken?

This is for a better understanding of where we are standing now. 9.5.7 was rather a significant hotfix, but did they deliver?
What benefits have you noticed from 9.5.7 OTA and what you think needs work still.
I already noticed pictures are more accurate on low light whlie also more popping and saturated in normal mode,
Also after receiving a phone call, the loudness and clarity could be told from 5 feet away without using loud speaker.
I wasn't really experiencing most of the other issues, so, what was fixed for you?

Ghost touches are fixed! As far as the camera goes... i haven't compared it yet, but people say its much much better. Ambient display was a bit buggy for me on 9.5.5. Sometimes it works, and other times it didn't, but after the update i am yet to see it not working. I really appreciate this update and hope for more improvements in the future.
Edit: Btw first time using a OnePlus device and im loving it so far. Only issue for me is lack of sd card slot when it has 2 sim slots.

Ambient display is fixed and camera has improved hugely, especially night mode... Huge improvement

Much better overall...

They claim to have improved touch response. Maybe better now with tempered glass protector.

Still difficult to pull down status bar while in a call.

Full screen games still got issues with getting statusbar visible.

A little more overnight drain... 5%... might take a few days to settle in again or something... don't know

whatthekj said:
Still difficult to pull down status bar while in a call.
Click to expand...
Click to collapse
I didn't know about that issue, it would be good for you to submit it it in OP forums. Meanwhile, Only if if you have rooted you can fix that by installing Renovate ICE magisk module and enable Statusbar peek in Rice Tweaks

GUGUITOMTG4 said:
I didn't know about that issue, it would be good for you to submit it it in OP forums. Meanwhile, Only if if you have rooted you can fix that by installing Renovate ICE magisk module and enable Statusbar peek in Rice Tweaks
Click to expand...
Click to collapse
Yeah I posted it on the OP forums the first week the phone started shipping out and I am using the RICE. Thankfully they offer a work around.

Ambient display still broken for Nova Launcher and I'm sure for others as well, when unlocking it goes to black screen and only nav bar. Which as been reported by others. When ambient display disabled everything works fine.

Takes about 5 seconds to take a nightscape picture, I can´t hold my hands steady for that long, so using regular mode for night photos which actually works surprisingly well. Still would like to have the option though.

*808*# to calibrate promixity sensor doesn't work. Unable to open the sensor calibration. And the old pocket mode isn't in settings anymore.
Conclusion is that while being carried in my pocket screen goes on very often.
Anyone else?

Warp charged is borked for me since 9.5.7, it changes between warp, normal and no charging about every 5 seconds, my old 5 cable does the same but funnily enough warp charge pops up with it, and my 5 dash charger works fine. And once the phone is about 90% the issue goes away completely. Also a factory reset didn't fix it and I know for sure I didn't have it on 9.5.5 because my phone vibrates every time it switches back to warp charge (which happens a lot and repeatedly as well as the animation on the lock screen) and its never done that before. (here is my post on the OP forums for any that want more info: https://forums.oneplus.com/threads/op-7-pro-warp-charging-not-working-anymore.1051041/)

I didn't see the ghost touch issue on 9.5.5, but right after booting into 9.5.7 I saw ghost touches
I have disabled NFC now and have not seen it since

mattboxer said:
Warp charged is borked for me since 9.5.7, it changes between warp, normal and no charging about every 5 seconds, my old 5 cable does the same but funnily enough warp charge pops up with it, and my 5 dash charger works fine. And once the phone is about 90% the issue goes away completely. Also a factory reset didn't fix it and I know for sure I didn't have it on 9.5.5 because my phone vibrates every time it switches back to warp charge (which happens a lot and repeatedly as well as the animation on the lock screen) and its never done that before. (here is my post on the OP forums for any that want more info: https://forums.oneplus.com/threads/op-7-pro-warp-charging-not-working-anymore.1051041/)
Click to expand...
Click to collapse
Try charging while the phone is off, let the battery drain low, plug it for 1.5 hour. If it goes up to 100% in that time, then its not a hardware malfunction but an OS bug

nickname_marco said:
*808*# to calibrate promixity sensor doesn't work. Unable to open the sensor calibration. And the old pocket mode isn't in settings anymore.
Conclusion is that while being carried in my pocket screen goes on very often.
Anyone else?
Click to expand...
Click to collapse
did you debloat you OS? I did using tomato debloater, and with it some some of the calibration/ engineering mode went away as they where part of the apps to be removed. if reflashing your OS wont solve it for you, you might have a broken sensor

GUGUITOMTG4 said:
did you debloat you OS? I did using tomato debloater, and with it some some of the calibration/ engineering mode went away as they where part of the apps to be removed. if reflashing your OS wont solve it for you, you might have a broken sensor
Click to expand...
Click to collapse
No, that's not what I wrote. Engineering mode app opens, but the calibration section doesn't work. It was working before. Someone else confirmed it to me in another thread.

GUGUITOMTG4 said:
Try charging while the phone is off, let the battery drain low, plug it for 1.5 hour. If it goes up to 100% in that time, then its not a hardware malfunction but an OS bug
Click to expand...
Click to collapse
I'll give that a try tonight and see what happens

I do not take many pictures I am glad to read though the camera may have improvements.
Noticed no changes so far.