Hi guys
I know this issue has been mention a bit, and I've searched through countless threads but I find the search system on the site a little counter intuitive, like forum searches will only bring up the thread, not the actual key word references and I have to search again within the threads to yield results, but I'd like to clarify a few things.
I'm running Cm11 nightlies on the phantom kernel and I have the screen wake issue. It takes multiple attempts to wake up the screen. OK.
I understand this is a problem with Kitkat roms for our device. However, my case is that there is a 50-50 chance that the screen doesn't wake up at all and I have to pull the battery. This makes any rom almost unusable for me as 1 out of 2 times I have to pull the battery to access the phone, Music continues to play, and I can skip tracks or play or pause, and even take photos, which means that the phone unlocks only the screen doesn't light up. If I hold down the power button, I can feel the phone vibrate to indicate the shutdown menu and sometimes I can blindly reboot or turn off the phone by tapping the screen roughly where the menus would be, so the touch is working.
Roms have been reinstalled and dalvik wiped etc but no improvement
I'd like to know if there's something I've done wrong to have so much poor luck. I don;t mind waiting for the screen to light up, or even a few tries, I'm aware of the unstable nature of nightly roms, and I am happy to use it and contribute usage stats to help further development, but not being able to get the phone on is a massive problem, especially when receiving a call
If anyone has any tips, I;d love them to let me know so I can add here as a one stop thread to general KK problems and work-arounds.
Pr m,aybe it's just my phone
Current mods
Xposed framework modules
greenify
kk bugs fixer (currently disable as seems to make no change)
minminguard
no lock home
Xposed gel settings.
No crazy overclocks or aggressive governers (tested with ondemand, intelliactive no difference, but great battery)
General rom experience apart from this - Excellent battery and very snappy, only a little skipping with audio (even with cache increased to 4010)
Cheers people!
try another kk rom
i did not use cm11 b,coz i had problems with the low reciever volume
tryout carbon rom or vanir aosp
they are too good
SOLVED
OK, thanks for the suggestions, actually I had the same issue on all roms that I tried.
The fix was the following, I disabled the NO LOCK HOME Xposed module and now all is back to normal.
i think there was an issue with it auto unlocking the screen on wifi or cel tower that caused the lockscreen to crash from time to time or get stuck. All is working like a dream now.
It~s a shame really, here in Brazilo with the rise of the Iphone and the high robbery rate, it´s quite common now for thieves to stick their gun in your face and demand your password or for you to unlock;disable the password during the robbery so that they can reset the apple acount or phone for resale. With nolock home I could save the cel towers near my home and work (for my walks to and from the subway) so that in case of a robbery, the phone just opens up and shows its unlocked, and then I can remotely wipe it later without giving up account details. Anyway, anybody else with this problem, thats the source of the Issue
Good morning every1,
I installed NeatRom on my i9100 and worked marvellous for months, now is a living hell! Not blaming the Rom itself but some kind of conflict between hardware and software.
Bug Description: screen strange behavior, in certain conditions won't turn on or will show strange colors, over illuminate or darken display, while at start up it will always work fine.
Trigger: locking the screen normailly causes to blackout but it will not turn on again on most tries, pushing the power buttom or the home buttom is equally uneffective most of the times. However, reseting the phone by removing the battery (since there's no display is the only way) will allow the phone to start normally: normal brightness, normal colors and normal operation everytime.
Fixes tried so far: I've reset the phone to factory, erase all cache, partition and delvik, and reduced the amount of apps to keep ram very low in usage. Also, I've removed the phone cover to check the screen connections, check the cable to see if its not broken and everything its fine. The display is not broken or otherwise damaged.
Opinion: since the display works fine at start up and would be working normally for as long as I don't lock it, I'm discarding all hardware problems of the screen itself; and I've removed all apps to avoid conflct of other software and it still has the same problem. Therefore, I think there's somekind of conflict between NeatRom and the screen (drivers maybe).
PLEASE HELP! :crying:
Malakiel said:
Good morning every1,
I installed NeatRom on my i9100 and worked marvellous for months, now is a living hell! Not blaming the Rom itself but some kind of conflict between hardware and software.
Bug Description: screen strange behavior, in certain conditions won't turn on or will show strange colors, over illuminate or darken display, while at start up it will always work fine.
Trigger: locking the screen normailly causes to blackout but it will not turn on again on most tries, pushing the power buttom or the home buttom is equally uneffective most of the times. However, reseting the phone by removing the battery (since there's no display is the only way) will allow the phone to start normally: normal brightness, normal colors and normal operation everytime.
Fixes tried so far: I've reset the phone to factory, erase all cache, partition and delvik, and reduced the amount of apps to keep ram very low in usage. Also, I've removed the phone cover to check the screen connections, check the cable to see if its not broken and everything its fine. The display is not broken or otherwise damaged.
Opinion: since the display works fine at start up and would be working normally for as long as I don't lock it, I'm discarding all hardware problems of the screen itself; and I've removed all apps to avoid conflct of other software and it still has the same problem. Therefore, I think there's somekind of conflict between NeatRom and the screen (drivers maybe).
PLEASE HELP! :crying:
Click to expand...
Click to collapse
Hello,
XDA assist is for newbies finding their way around XDA Developers, it isn't a development section.
Please try posting the bug reports in the same thread you found the ROM in order to provide a helping hand to the developers.
-Vatsal
Judging from user complaints all over the various discussion forums, random spontaneous reboots are not a problem of particular types of Android phones. It is an Android problem. It occurs on many, perhaps all different Android phone types at least since Android 6. For example, it happens on Nexus, Pixel, OnePlus, Xiaomi, Samsung phones, as you can read here and elsewhere by searching for random reboot and spontaneous reboot.
It does not happen to everybody. It is possibly triggered by some Android setting, some core component like the radio, or by certain apps or certain settings in certain apps. It seems to be more prevalent on busy phones with many apps. We currently don't know for sure. Some reports said that the random reboots continued even directly after a factory reset (which would not be a viable solution anyway, even if it temporarily worked). It is likely that there is more than one cause. It certainly can be caused by pressing and holding the power button, possibly inadvertently in pockets or bags. It can be caused by mechanical shock in phones with removable batteries.
But the main cause is in the software, as I could prove in my case, by moving the entire software installation to another phone, which then exhibited the same random reboots. This was on a OnePlus One.
I am writing about the type of random reboot that only occurs while the phone is sleeping. There may be others.
But I can now report a complete success. I have been experimenting with preventing deep sleep. Since I keep the phone on a PARTIAL_WAKELOCK by means of one of the Wake Lock apps, the phone has never rebooted again on its own, not even once. Other users of entirely different phone types, like Nexus, have reported the same success. So at least in these cases the cause is closely related to deep sleep or perhaps to doze mode.
If you are affected, I urge you to try this. The hope is that a continuous partial wake lock solves the problem for most Android phones.
I use the app Wake Lock - PowerManager by darken. This app requires that I start the wake lock manually after each reboot, but since there are no more spontaneous reboots, this is easy enough. There is another, similar app, Wake Lock - CPU Awake by Innovemind, which can set the wake lock automatically after rebooting, but I have not tested it.
The downside is that the wake lock consumes some power. But on a busy phone it does not make much difference. I greatly prefer a phone that uses a little more power over one that reboots randomly.
There is now also some hope that Google can finally locate and repair this terrible defect, now that they know that it is related to deep sleep, assuming they are sufficiently interested in user reports to pick this up.
Hello,
Recently i upgraded my OnePlus 7 to OxygenOS 11 via OTA, and here is a list of a few annoying bugs(features?) that you'll need to know before upgrading:
(Note: I performed hard reset after upgrading, so any bugs here will be persistent and not because of some fixable issues, unless you are rooted/want to use adb maybe?)
(Also, this is the stock OOS 11, not rooted, and no modifications)
1) I'm not sure if it's just me, but the device heats up much faster. Though the temperatures here are high, I tried to maintain as close to a lab condition as possible, maintaining 30C ambient temp. Evaluation was done with a session of Call of Duty Mobile, and Youtube 4K video loopback test. Avg temps are: CODM : OOS 10: 41C, OOS 11: 45C, Youtube: OOS 10: 37C, OOS 11: 38C
2) Performance hit in games and frame drops (CODM, outside the ambient temperature maintained conditions), could be due to overheating? (As i mentioned, ambient temps are a bit high here). Also SystemUI lags sometimes. Adding to that, trying to bring up notification panel while playing a demanding game (like codm), the SystemUI (notification panel) opening animation is really choppy. (Is there some graphic driver issue?)
3) Brightness slider very slow to respond (seriously? Have to wait for 3 sec for the brightness to come up/go down on manually moving the slider)
4) Again, this one could be only me, but the audio seems to be a bit low after the update. All the ringtones and default notification sounds, with the same volume levels feels lower than how it was on OOS 10.
5) Battery drain - Device heat up and performance issues, translate to higher battery drain
6) This may not be a bug, but it's a change that i don't quite like (at least provide options?) : Double tap to wake doesn't give a vibration feedback like how it used to.
7) Everything, including UI and default font size is bigger than what I'm comfortable with (no, changing the font/display size doesn't give the expected results). But there's a workaround: Changing the display dpi from developer options from 384 to 420.
8) I had several app crashes (Instagram, Photos) even after disabling Android System Webview as suggested by some. But this issue seems to have been fixed magically for now.
9) This is a change, but to actually poweroff/reboot, you will need to reach your finger to the top of the screen with the new UI.
10) DC dimming has been removed
11) Weird QC issue-Someone thought any greyed out field in settings is because it's not supported by phone or HEADSET... Even in Private DNS settings.(See screenshot)
12) Natural colour calibration has a weird yellow tint (sRGB profile works fine tho)
13) Lots of missed/delayed notifications. Many times, notifications from apps like Instagram, Telegram doesn't arrive on time, with delays from 2 minutes to never arriving at all. Whatsapp seems to work most of the time. Sometimes, notifications don't make sound (weird), but only flash on the screen (Yes, I've verified all my notification settings, and I've set everything to make sound)
14) Now this might be a personal preference, but I don't quite like the way OxygenOS is trying to mimic OneUI (Huge heading and small contents beneath? Not my taste.) This style is followed in the phone, messaging, contacts, calculator, etcc
15) Quickly switching between recent apps, there's a split second of a black screen that appear before the app UI is displayed (not complaining, but this was not present in oos10, it seamlessly moved from the preview of the app on the recent apps screen to the actual app ui without any flickering, and no, this is not because of dc dimming being off or anything)
16) Google Play Music is still not removed (seriously, why still have it if it can't be used?)
17) FileDash - No longer has the DNS resolver for one.plus address. You will now have to manually type in the address displayed by filedash in your browser. Also, it still uses 2.4GHz and not 5GHz.
Edits: Added more bugs/missing features
Hem981,
I can confirm #7 is an issue on mine as well.
The power menu is an android 11 change not an OOS change.
I upgraded from OOS 10 to OOS 11 no wipe and don't seem to experience the other issues that you are having, except the obvious changes they made to the firmware. Have you tried clearing the dalvik-cache and rebooting? Mine was super buggy before doing this, but then again I just upgraded without wiping.
One issue I've personally noticed is the cell radios were a lot better on OOS 10, and I'm assuming that is the cause of the battery life to be worse.
Another that could be due to doing some debloating is when I take a screenshot and the little preview pops up in the bottom right corner if i click on it the UI will freeze after clicking back. The Nav buttons still work, like you can click on recents and the recent menu appears, back and home work but the screen is frozen otherwise until I force a reboot.
Yeah, I've tried factory reset and then wiping dalvik-cache... The performance was better before i performed the factory reset, i think. Anyway, there are quite a few games/apps where the performance impact is easily visible. Also, the power button thing is an Android change, but i really hoped OnePlus to have done something to make it more easily accessible (OOS is not pure Android). I couldn't find the issue with the cell radio you mentioned (as I've tried in areas in which i already had poor reception, and the performance was what was expected). Anyway, I really hope some of these (at least the performance, battery drain and the brightness slider issue) will be fixed soon over updates.
(For me, the SOT has gone down from 9.5 hours to 7 hours under similar use cases)
Yeah SOT has definitely taken a hit on mine as well, standby time seems the same. I also have noticed that the screen brightness needs to be set higher for the same brightness as OOS 10. The cell radio sometimes seem normal, but most of the time they are about 5-10 dBm higher at my house. I'll probably give a clean flash a try this weekend to see if it clears up.
One more issue found:
Weird red tint on screen auto dimming
The whole display has a weird red tint just before the device is about to lock/turn off screen after the timeout, when the display dims. It is easily noticeable if you have a white screen displayed. It only happens if you have set the brightness slider to anything other than the bare minimum (even a single step above the minimum brightness is able to replicate this issue)
I found something interesting: issue #3, the brightness slider being slow to respond to changes, seems to be fixed by disabling all animations from developer options. Should the window animator duration scale have any effect on the responsiveness/quickness of display brightness adjustment? I think that's stupid.
Also, I am starting to thing we need something like 0.1x duration scale for the animations (all animations on Android, or at least OOS), because honestly, with each new implementation, the animations are being too slow that it degrades the whole experience. 0.5x feels a bit better, but i really think something like 0.4x would match the animation speed of android 10.
You forgot to mention the vibration motor effect which has deteriorated since the update. The device now feels like any other cheap device.
It's kinda weird in my situation, just upgrading from 10.3.8 using an old version of xXx NoLimits to 11.0.0. The phone was super buggy when I first installed, but after rooting, wiping the delvik cache, debloating, removing the xXx module, and time to settle in the only issues I have are the screenshot popup, and the lower cell signal which I'm sure is causing a hit on battery life.
I was going to reinstall this past weekend, but for the time and inconvenience it's not worth the time compared to the minor issues I have.
Edit: Even the screen resolution seems normal now.
Again, don't know if this is an issue for anyone else (and i don't think OnePlus is going to change this): While everything else became bigger on the phone, the buttons/number keypad for typing in the screen lock pin became too small.
Hem981 said:
Hello,
Recently i upgraded my OnePlus 7 to OxygenOS 11 via OTA, and here is a list of a few annoying bugs(features?) that you'll need to know before upgrading:
(Note: I performed hard reset after upgrading, so any bugs here will be persistent and not because of some fixable issues, unless you are rooted/want to use adb maybe?)
(Also, this is the stock OOS 11, not rooted, and no modifications)
1) I'm not sure if it's just me, but the device heats up much faster. Though the temperatures here are high, I tried to maintain as close to a lab condition as possible, maintaining 30C ambient temp. Evaluation was done with a session of Call of Duty Mobile, and Youtube 4K video loopback test. Avg temps are: CODM : OOS 10: 41C, OOS 11: 45C, Youtube: OOS 10: 37C, OOS 11: 38C
2) Performance hit in games and frame drops (CODM, outside the ambient temperature maintained conditions), could be due to overheating? (As i mentioned, ambient temps are a bit high here). Also SystemUI lags sometimes. Adding to that, trying to bring up notification panel while playing a demanding game (like codm), the SystemUI (notification panel) opening animation is really choppy. (Is there some graphic driver issue?)
3) Brightness slider very slow to respond (seriously? Have to wait for 3 sec for the brightness to come up/go down on manually moving the slider)
4) Again, this one could be only me, but the audio seems to be a bit low after the update. All the ringtones and default notification sounds, with the same volume levels feels lower than how it was on OOS 10.
5) Battery drain - Device heat up and performance issues, translate to higher battery drain
6) This may not be a bug, but it's a change that i don't quite like (at least provide options?) : Double tap to wake doesn't give a vibration feedback like how it used to.
7) Everything, including UI and default font size is bigger than what I'm comfortable with (no, changing the font/display size doesn't give the expected results). But there's a workaround: Changing the display dpi from developer options from 384 to 420.
8) I had several app crashes (Instagram, Photos) even after disabling Android System Webview as suggested by some. But this issue seems to have been fixed magically for now.
9) This is a change, but to actually poweroff/reboot, you will need to reach your finger to the top of the screen with the new UI.
10) DC dimming has been removed
11) Weird QC issue-Someone thought any greyed out field in settings is because it's not supported by phone or HEADSET... Even in Private DNS settings.(See screenshot)
12) Natural colour calibration has a weird yellow tint (sRGB profile works fine tho)
13) Lots of missed/delayed notifications. Many times, notifications from apps like Instagram, Telegram doesn't arrive on time, with delays from 2 minutes to never arriving at all. Whatsapp seems to work most of the time. Sometimes, notifications don't make sound (weird), but only flash on the screen (Yes, I've verified all my notification settings, and I've set everything to make sound)
14) Now this might be a personal preference, but I don't quite like the way OxygenOS is trying to mimic OneUI (Huge heading and small contents beneath? Not my taste.) This style is followed in the phone, messaging, contacts, calculator, etcc
15) Quickly switching between recent apps, there's a split second of a black screen that appear before the app UI is displayed (not complaining, but this was not present in oos10, it seamlessly moved from the preview of the app on the recent apps screen to the actual app ui without any flickering, and no, this is not because of dc dimming being off or anything)
16) Google Play Music is still not removed (seriously, why still have it if it can't be used?)
17) FileDash - No longer has the DNS resolver for one.plus address. You will now have to manually type in the address displayed by filedash in your browser. Also, it still uses 2.4GHz and not 5GHz.
Edits: Added more bugs/missing features
Click to expand...
Click to collapse
Hi! Oneplus 7 ownere here.
Try to answer all the points:
1) i don't notice any difference between OOS10 and OOS10 on the heat of the phone
2) I don't know for the gaming performance but i don't play any games...overall, the performance are good, no system lags or freeze BUT I have the same issues with the notification...when i tap a notification, I often have delay, maybe it's just the animation but I remember the same issue on a Oneplus 8t that i tried for 20 days in last November
3) same issue here, very annoying
4) not just you, have same issue
5) battery drain is the same in my case, in standby maybe is less than before
6) me too, but maybe they change this as they planned?
7) yes, same thing. i changed the DPI from developer options too
8) no crashes here
9) this is an Android 11 change from Google, maybe they don't want your device to power off ahahah
10) never had this problem luckily
11) don't know, never tried this
12) i noticed this after reading this point, true on my device too
13) i faced the same issue on the notification sound, the other things works fine
14) me too, if i wanted One UI, i would have bought a Samsung...
15) sometimes happens to me, maybe it's bad ram management?
16) this is ridicolous, why they doesn't remove this app??
17) never tried
I also have an issue on the vibration. Now it's HORRIBLE, i have disabled because it's unusable
So, this is my question: change phone or rollback on android 10?
There's one more addition to the list: Always on display sometimes seems to override the notification lockscreen privacy settings. I have some notifications put as "view private content only when unlocked", but the notification contents are visible just when it arrives on the always on display (though it's content is hidden in the actual lockscreen)
I've reported almost all of these bugs, and hopefully we will see new updates fixing most of these.
Can someone on OOS 10 on OnePlus 7 confirm if the "style preferences" settings in sound settings is greyed out while the output is phone speakers (or no other sound output devices connected)?
New hotfix patch OTA rolling out now...
Here is what's fixed and what's not:
1,2 : Yet to test
3: Not fixed
4:Fixed
5: Yet to test
6: No changes
7: No changes(or not easily noticeable maybe?)
8: Not encountered any "ghost" app crashes yet
9: No change
10: DC Dimming is not back, so no change
11: Not fixed Is it that hard to remove 'headset' text from the UI?
12: Don't know if it's because my eyes adjusted to it, but it seems a bit better now
13: Not yet tested
14: What can I say?
15: Fixed
16: The ghost of Google Play Music still remains
17: Not fixed
Edits: Nothing much is fixed
Performance: Marginal improvements
SoT/Battery: Even worse. Getting almost half the SoT I got on OOS 10 under similar use case and network/tenperature conditions
Ghost app crashes reduced a lot (that might be the only fix) , but is not completely gone (saw that 1 or 2 times)
Haptics is still as bad as before
I'm just worried about this weired bug which has rendered my parallel whatsapp very difficult to use to share media. Any fix for this is highly appreciated - https://forums.oneplus.com/threads/whatsapp-media-problem.1411292/
Thanks and regards
OOS11 - Stable
I have no problems on my device until now (for games I dont know why I do not play)
I noticed, because I have tried both roms(beta4 & stable).Open Beta4 has better "battery management" than stable! Αs strange as it may seem but is a real for me..
Well yes .Battery drain higher than openbeta4
wifi works fine to 5ghz band & generally my device works quite well so far. Patience is needed and all problems will be fixed...
https://postimg.cc/gallery/YtQpVDm
After the recent OS 11 update ,the media in my device ( photos and videos) not being shown properly in Whatsapp. Some of the videos and pictures which I've already deleted in the gallery are appearing again only in whatsapp in unsupported file format.
I'll be glad if someone confirms that it's a bug in OOS 11.0.2 and that my phone is not the only one which is affected.
I'm using WhatsApp and Parallel Whatsapp. Also have setup a Work/Office profile on my phone.
Does anyone have any solution to this issue?
Thanks and regards!
For me, wifi no longer works. Whenever I try to enable it, it just immediately turns off. It also no longer recognizes my SIM card.
itdiestoday said:
For me, wifi no longer works. Whenever I try to enable it, it just immediately turns off. It also no longer recognizes my SIM card.
Click to expand...
Click to collapse
Try wiping cache from recovery
Update 11.0.1.1
I feel like this is a big joke.
Even more battery drain (yes, i did a factory reset).
Brightness slider issue still not fixed.
Performance still degraded (but i think there is a little bit of improvement)
Not sure about Wifi issues as i never had them.
Weird red tint on screen dimming
Still many ugly and inconsistent ui elements
Color profile is back to being broken (the yellow tint returned)
Update: I've started having the wifi disconnection issues, after 11.0.1.1 update. This is way too annoying.