Develop Bugs

Few problems after updating to Marshmallow

Hello!
My current problems after updating to 6.0 are:
-Battery (!) one of the serious problems, the battery just drains like crazy, Chrome take 1-3% every few minutes, i cant use the phone more then 1.5-32hours in average. even less, use.
-The phone became much slower since the update. It is no as smooth as it used to be
My phone is currently at stock rom, I udpated via OTA update and now the phone is barely usable.

Same here.

Amo5 said:
Same here.
Click to expand...
Click to collapse
Make sure you have the latest version of Chrome installed.
Use Greenify or Kin or both to help shut down apps in the background when not needed.

Rapunzl said:
Make sure you have the.
Use Greenify or Kin or both to help shut down apps in the background when not needed.
Click to expand...
Click to collapse
I have the latest version of Chrome installed already.
The problem is mostly when im USING Chrome so Greenify wont be a big help here, btw i dont have root so its not so much effective without it.

Amo5 said:
Same here.
Click to expand...
Click to collapse
after downgrading to LP, i got my 3hrs minimum screen on time. The phone barely heats and the performance became much better.
The problem is with the MM update i guess.
Hope it helps you.

rongold3 said:
after downgrading to LP, i got my 3hrs minimum screen on time. The phone barely heats and the performance became much better.
The problem is with the MM update i guess.
Hope it helps you.
Click to expand...
Click to collapse
How do you downgrade it?

Amo5 said:
How do you downgrade it?
Click to expand...
Click to collapse
Using lggup.

Update to MM and do a factory reset right after and restart your phone, should be smooth sailing after a couple of charges.. No lag or batt drain here

[Q] How is your experience with Nougat so far?

Hello all,
As the title says, what is your opinion about Nougat? After reading so many bug related posts here and in reddit, im frustrated to update to the newest version of android. How does it compares to marsmalow in terms of battery, performance and bugs? Is it safe to update now, of do your suggest to wait a little longer for a bugfix update? And finally, if your suggest me to update, do your recomend any custom rom/ kernel?
Thanks in advance.

Fine, I love my 5X, but there are some bugs that I have:
*In Whatsapp audios or call if I put my face in the phone (or simple if I cover the distance sensor) the screen goes black and I can't turn on again...maybe if a press the power button 3 times the screen turns on. that is REALLY annoying!, I dont know if is a software problem or if my tempered glass is the real problem...
*The screen rotates very easy...sometimes I move my phone just a little and the screen rotates...
*When screen turns off it doesnt fade "slowly"...its something cosmetic but I dont like it haha

Jerber said:
Fine, I love my 5X, but there are some bugs that I have:
*In Whatsapp audios or call if I put my face in the phone (or simple if I cover the distance sensor) the screen goes black and I can't turn on again...maybe if a press the power button 3 times the screen turns on. that is REALLY annoying!, I dont know if is a software problem or if my tempered glass is the real problem...
*The screen rotates very easy...sometimes I move my phone just a little and the screen rotates...
*When screen turns off it doesnt fade "slowly"...its something cosmetic but I dont like it haha
Click to expand...
Click to collapse
Hm, i dont use whatsapp so i dont mind if there is a bug about it. Do you have the same problem during calls too? Also, what about battery and performance?

I have these bugs:-
1. I have a problem with the battery percentage toggle, i change it to like "everytime" but sometimes it auto switches back to "only when charging", in 6.0.1 there was only an option to show percentage which worked fine.
2. I also have a problem after sep security update the swipe up from overview to open multiwindow doesnt work, it is on in the settings tho, it worked on the first 7.0 aug security one but now it doesnt.

U_Midrar said:
I have these bugs:-
1. I have a problem with the battery percentage toggle, i change it to like "everytime" but sometimes it auto switches back to "only when charging", in 6.0.1 there was only an option to show percentage which worked fine.
2. I also have a problem after sep security update the swipe up from overview to open multiwindow doesnt work, it is on in the settings tho, it worked on the first 7.0 aug security one but now it doesnt.
Click to expand...
Click to collapse
This features disable automatically when you go to System ui tuner. Just enable it and don't touch this settings.

Also, I have a bug with double icon of alarm clock in status bar, like on screenshot. Reboot can fix it.

57DeNiK57 said:
This features disable automatically when you go to System ui tuner. Just enable it and don't touch this settings.
Click to expand...
Click to collapse
oh yea that is why it sometimes worked lol yup just change the settings and leave them there and dont open system ui tuner, its still a bug tho.
57DeNiK57 said:
Also, I have a bug with double icon of alarm clock in status bar, like on screenshot. Reboot can fix it.
Click to expand...
Click to collapse
is that the pixel launcher ?

U_Midrar said:
is that the pixel launcher ?
Click to expand...
Click to collapse
Yes, it is

57DeNiK57 said:
Yes, it is
Click to expand...
Click to collapse
u been using it for long ? is it like stable ?

U_Midrar said:
u been using it for long ? is it like stable ?
Click to expand...
Click to collapse
I used it since 12 september. Yes, good launcher, but I installed it as apk, so google now doesn't work.

57DeNiK57 said:
I used it since 12 september. Yes, good launcher, but I installed it as apk, so google now doesn't work.
Click to expand...
Click to collapse
yea i have the apk too, i dont use google now and it sometimes gets in the way so thats good for me

I think i can live with a few bugs. What about the more important things like battery life and performance? How do they compare to marsmalow?

giannism13 said:
I think i can live with a few bugs. What about the more important things like battery life and performance? How do they compare to marsmalow?
Click to expand...
Click to collapse
I recently reverted back to marshmallow, I was getting horrible battery drain. Like 10℅ an hr while in my pocket. I had to leave it on battery saver mode if I wasn't going to be near a charger. But besides that it's awesome, love all the new features.
Sent from my Nexus 5X using Tapatalk

For me, unlocking the device harder. I have to swipe further in order to do it, and it also happens when I want to swipe a notification at the lock screen.
In addition Spotify song playing from google now through an Android Wear does not work unless the Nexus is unlocked.
Finally, battery life is not really god in my case.

After reading your replies, i decided to stay in marsmalow for a couple of months. Thanks everyone

It's only been a couple days for me but everything is working well on the stock OTA update so far.
I like the new features and Doze is working brilliantly again so there is a noticable improvement to battery life.
Sent from my Nexus 5X using XDA-Developers mobile app

I'm on stock+ 7.0 Nougat everything work very Well no problème here on Nougat .... Very good 7.0 Nougat
Root systemless ok
Magisk ok
Pokémon go ok
My mother ok euh yes she Can use my nexus 5x
Battery life 2 days with no game , 1 day with Pokémon go or if i play so hard 7 hours
I'm happy on 7.0 but i would like xposed and custom Rom with theme engine , substratum is to young

4.1.1 vs open beta 13

Suggest me......

search the forums and make your own decision

OB13 is better since you don't need to install magisk for the touch latency update. They finally fixed the latency issue and the speed gains from it are pretty noticeable. Everything else is pretty much the same thing.

but android system take lot of battery in standby mode in beta13.

Cybertron™ said:
but android system take lot of battery in standby mode in beta13.
Click to expand...
Click to collapse
No, just no. Flat battery line for me.

MarcTremonti said:
No, just no. Flat battery line for me.
Click to expand...
Click to collapse
idk why is here.

Cybertron™ said:
idk why is here.
Click to expand...
Click to collapse
other reasons then, wakelocks, logcat error spam or god knows. nothing to do with OB13.

crzykiller said:
OB13 is better since you don't need to install magisk for the touch latency update. They finally fixed the latency issue and the speed gains from it are pretty noticeable. Everything else is pretty much the same thing.
Click to expand...
Click to collapse
Except there is no new OOS Launcher, and no auto night mode in 4.1.3

Face Unlock much slower after today's update =(

After updating to 43 OTA 004, Faceunlock is no longer instant. now you see first the lockscreen flash and then UI slide in. I went back to 43 OTA 003, but same situation.
before it was just press powerbutton/doubletap screen and the screen turned on showing instantly UI whereever you left off. just like all the reviewers showed it. I dont have file to go back to inital firmware 001 .... :/
VERY DISAPPOINTING, it really breaks the "instant" feeling. hope they fix it soon.
meanwhile, no speed increase in fingerprint reader. still slightly slower than OP3.
UPDATE: solved - it is Nova Launcher with a custom wallpaper that caused this -> back to Oneplus launcher, set new wallpaper = FaceUnlock instant again!

Not a terrible trade-off for more security.
FP sensor still fast af.

t2jbird said:
Not a terrible trade-off for more security.
Click to expand...
Click to collapse
what makes you think they inceased security?
t2jbird said:
FP sensor still fast af.
Click to expand...
Click to collapse
coming from OP3, that s not true... at least not for me YMMV
i can upload side-by-side vid tonight.

Hope everyone is reporting these "bugs" to OnePlus instead of just reporting them here.

Baldilocks said:
Hope everyone is reporting these "bugs" to OnePlus instead of just reporting them here.
Click to expand...
Click to collapse
reason for posting it here is to find out if anyone else experiencing this

ewww i hope not, then there is no difference than what was on the OP3/T smart lock, i liked the option that u didn't have to swipe up, i will prob return mine if this is the case.

phynesse said:
what makes you think they inceased security?
coming from OP3, that s not true... at least not for me YMMV
i can upload side-by-side vid tonight.
Click to expand...
Click to collapse
https://www.xda-developers.com/oneplus-face-unlock-oneplus-5t/

Works great for me!
I dont even see the lockscreen!

t2jbird said:
https://www.xda-developers.com/oneplus-face-unlock-oneplus-5t/
Click to expand...
Click to collapse
sooo, not security focused then. also doesnt explain why it now shows the lockscreen, instead of unlocking straight to UI... like with fingerprint

Nick502 said:
Works great for me!
I dont even see the lockscreen!
Click to expand...
Click to collapse
thanks for reply. and you are on which Oxygen version? 4.7.1 or higher?

phynesse said:
thanks for reply. and you are on which Oxygen version? 4.7.1 or higher?
Click to expand...
Click to collapse
Im on 4.7.2

Nick502 said:
Works great for me!
I dont even see the lockscreen!
Click to expand...
Click to collapse
+1 same here it unlocks instantly. I have added a FP too.

gianton said:
+1 same here it unlocks instantly. I have added a FP too.
Click to expand...
Click to collapse
thanks, ok then i did something to cause it... hm too bad

Here on 4.7.2 its also slow.

I had the same problem and factory reset: face unlock is back to being instant, and the finger print reader is noticeably faster. It is troublesome, however, that an OTA forced me to factory reset a 3 day old phone...

I have also reset after update but not solved.

I updated homescreen and lockscreen wallpaper with a custom one and experienced a slight drop on face unlock speed. Meaning that I was able to see the lockscreen for 1/10 of a second before the homescreen was there. I reverted the wallpaper choosing one of oneplus 's and face unlock speed was back to instant. Just a tip.

Works fine for me. I'm on FreedomOS based on Oxygen 4.7.2.

xByt3z said:
Works fine for me. I'm on FreedomOS based on Oxygen 4.7.2.
Click to expand...
Click to collapse
This is the 5t thread and not 5, thanks.

Schrotty35 said:
This is the 5t thread and not 5, thanks.
Click to expand...
Click to collapse
I'm aware. I built FreedomOS myself for the 5T.

Question Oxygen OS 12 Idle Touch Sampling Rate

In the "touchMultiTest" tool, the touch sampling rate remains 0, untill the finger is moved quite a bit, the resultant feedback is abrupt and inaccurate.
Noticable while sniping in PUBG and scrolling slowly.
This is an extremely annoying issue which was nonexistent in Android 11 older 0xygen OS
This problem is present in all the Android 12 builds of OOS/color OS.
Can others confirm this and bring it to OnePlus' attention?
What can i do to let OnePlus know about this on their "community" app?

Quite possibly the app needs to be updated for the feature to work with newer API

miravision said:
Quite possibly the app needs to be updated for the feature to work with newer API
Click to expand...
Click to collapse
Not an app specific issue.

1. If you have a thick case on that doesn't let heat out your SOC might throttle
2. If you have a screen protector /tempered glass on, try without it or try RMA

miravision said:
1. If you have a thick case on that doesn't let heat out your SOC might throttle
2. If you have a screen protector /tempered glass on, try without it or try RMA
Click to expand...
Click to collapse
Tried all that, i can confirm that this is an issue with OOS 12 and Color OS 12.
All the other Android 12 custom ROMS that I've tried, does not have this problem.
Its an issue specific to OOS 12.
This problem has persisted from way back, since the DP2 (Developer Preview 2) release.

SillyP said:
Tried all that, i can confirm that this is an issue with OOS 12 and Color OS 12.
All the other Android 12 custom ROMS that I've tried, does not have this problem.
Its an issue specific to OOS 12.
This problem has persisted from way back, since the DP2 (Developer Preview 2) release.
Click to expand...
Click to collapse
Upon further investigation, I think it has something to do with the kernel used in OOS 12 builds

Switch back to OOS11 if it's a problem.

TheKnux said:
Switch back to OOS11 if it's a problem.
Click to expand...
Click to collapse
yes, I have resorted to 11.2.10.10 build, but before I did so, I captured and sent OnePlus a log of what I was facing through the feedback app.
lets see how they respond, they asked me to be patient.
Did you experience the issue I'm talking about?

SillyP said:
yes, I have resorted to 11.2.10.10 build, but before I did so, I captured and sent OnePlus a log of what I was facing through the feedback app.
lets see how they respond, they asked me to be patient.
Did you experience the issue I'm talking about?
Click to expand...
Click to collapse
I experienced a whole lotta jank on all of their A12 builds. I never got around to installing OB3, but I did install the build that apparently broke everyone's data (oddly it didn't break mine). I think OB2 was by far the most stable build they put out for A12.
I tried PA for a bit but I'm a features guy and went back to OOS11.

TheKnux said:
I experienced a whole lotta jank on all of their A12 builds. I never got around to installing OB3, but I did install the build that apparently broke everyone's data (oddly it didn't break mine). I think OB2 was by far the most stable build they put out for A12.
I tried PA for a bit but I'm a features guy and went back to OOS11.
Click to expand...
Click to collapse
Now I'm on Xtended. Had to go back to Monet since OOS doesn't use it. Plus a less jank A12 ROM.

TheKnux said:
Now I'm on Xtended. Had to go back to Monet since OOS doesn't use it. Plus a less jank A12 ROM.
Click to expand...
Click to collapse
What is "monet" ?
Also im currently on the C.44 build of OOS 12 on my LE2125.
Idk what OnePlus did, but the touch "deadzone" issue is non-existent ONLY in PUBG mobile.....things are perfect there.
But its present everywhere else and in all the other games ( PUBG New State, COD Mobile, etc) ...
The touch "deadzone" issue is undeniably apparent now...
Easily observed when switching between "PUBG New State" and "PUBG Mobile"

TheKnux said:
Now I'm on Xtended. Had to go back to Monet since OOS doesn't use it. Plus a less jank A12 ROM.
Click to expand...
Click to collapse
I'm flashing Xtended right now, lets see how things are. Judging from the screenshots from the dev's post, this ROM looks delish.

Can anyone confirm if the issue is fixed in the lastest c.61 update.
They addressed system fluency

smjunaid said:
Can anyone confirm if the issue is fixed in the lastest c.61 update.
They addressed system fluency
Click to expand...
Click to collapse
PUBG/PUBG New State and some other popular games has this issue fixed.
It was indeed an API related issue.

SillyP said:
PUBG/PUBG New State and some other popular games has this issue fixed.
It was indeed an API related issue.
Click to expand...
Click to collapse
I was having the issue in the launcher even. In c.60
Even using Facebook and all other apps. During scrolling and holding the scroll with a finger

The problem very well does still persist throughout c.61.
By "system fluency", OnePlus probably means animation improvements.
smjunaid said:
I was having the issue in the launcher even. In c.60
Even using Facebook and all other apps. During scrolling and holding the scroll with a finger
Click to expand...
Click to collapse

SillyP said:
The problem very well does still persist throughout c.61.
By "system fluency", OnePlus probably means animation improvements.
Click to expand...
Click to collapse
Thanks for the prompt response. I don't know why people don't notice such a huge blunder. Thanks again mate