Flickerfree kernel - OnePlus 6 Questions & Answers

I love my new OP 6 phone, except one thing - PWM driven display below some brightness setting. Most things I read on the subject came from this wonderfull post (and kernel), which deals with the same thing on Samsung Galaxy. Is there any way we could achieve similar effect on our phones by some kernel / system tweaks? I would much rather deal with mura effects than eye strain, or at least drop the PWM - driven portion of the scale way down. I was trying to get started, poke around a little for backlight drivers and kernel source code, but I have little to none kernel development experience and knowledge so I got lost pretty quickly and do not know if it is even possible on Qualcomm platform.

Since I knew there is an app called Oled Saver on Google Play store, it prevents your brightness lower than certain value which may trigger the Flickering
Except that, the Mi 9 is rumored to get a DC Dimming for all the time update, most possibly tinkered with Its kernel, for our old obsoleted device, we could all depend on that OLED Saver App and tolerate the brighter display at night in order to prevent flickering
While DC dimming for all the time, is achieved more and more, hopefully we might see more new phones shipped with Officially DC dimming kernel, thus its Custom ROMs and users could all be able to utilize this flipper switch to save our eye from display flickering

Smurf Kernel has an option called 'Flicker free) in it's config file which should handle this problem
https://forum.xda-developers.com/oneplus-6/development/4-9-109-smurfkernel-1-0-0-t3805948
It's also overall a very good kernel, I use it since quite a time now

castrum_doloris said:
Smurf Kernel has an option called 'Flicker free) in it's config file which should handle this problem
https://forum.xda-developers.com/oneplus-6/development/4-9-109-smurfkernel-1-0-0-t3805948
It's also overall a very good kernel, I use it since quite a time now
Click to expand...
Click to collapse
I second this, Smurf kernel actually implements the code from the kernel linked in the OP, if i'm not mistaken. Already read this from the Smurf thread.
And agreed, the kernel is very good !
Edit : Wait, i didn't see the OP date, why has this been dug up ?

pokevitek said:
I love my new OP 6 phone, except one thing - PWM driven display below some brightness setting. Most things I read on the subject came from this wonderfull post (and kernel), which deals with the same thing on Samsung Galaxy. Is there any way we could achieve similar effect on our phones by some kernel / system tweaks? I would much rather deal with mura effects than eye strain, or at least drop the PWM - driven portion of the scale way down. I was trying to get started, poke around a little for backlight drivers and kernel source code, but I have little to none kernel development experience and knowledge so I got lost pretty quickly and do not know if it is even possible on Qualcomm platform.
Click to expand...
Click to collapse
So i read your post and overall i figured out that you have screen flickering issue when on low brightness. I had the same issue and additionally, it flickered alot when restarting/locking/unlocking the phone. I took mine to service centre and they said it's a hardware issue and replaced my display. No issues till now after that. This issue was also brought up in the oneplus community and even the bug hunters contacted me. At the end, the conclusion came as hardware issue.
Maybe yours is the same.

Deleted

Well, seems like OnePlus guys read XDA Forums sometimes haha !
https://www.xda-developers.com/oneplus-dc-dimming-optional-feature-future-update/

Related

Pipo M6 RK3188 16GB Review

Hey guys, I just received my Pipo M6 today so I thought I'd offer my experience so far. Keep in mind that I am coming from an iPad mini and my daily driver is a HTC One X running Cyanogenmod 10.1.
Build Quality:
TBH, I was hoping for something a little better after reading some user reviews. It's still quite good overall but there's just a few too many seams and the edges are a little rough at certain points. Nothing major but it just feels like a made and designed in China product. It doesn't bother me so much though since I won't notice it after putting it in a case.
I was glad to find that underneath the temporary screen protector which comes with all new products these days, there was another one underneath it which means you won't need to bother with putting on one yourself.
Screen:
VERY pretty. Viewing angles are good and colours really pop. Brightness level is amazing and will surely be sufficient even if you are in the dessert. In terms of resolution, you can set it to HD mode or Normal which requires a restart. I couldn't really notice any differences although I might if I had another one sitting side by side. Only thing is, I used both AnTuTu and Android System Info to find out the resolution and there seem to be some discrepancies.
Under HD Mode, both apps reported a resolution of 1536x1952 with 320dpi. Now that's still within Retina level territory but they were advertising 2048x1536. Not a huge difference I know but still a little annoying.
At Normal Mode, AnTuTu reported 1600x1128 and Android System info reported 1200x1528. Not sure why the two differed but the difference is negligible when you do the math.
User Interface:
As you may know, you have the choice of using the standard Jelly Bean interface or the special Pipo interface which makes everything look a bit like Windows 8. I chose to go with the latter. Everything is quite smooth although perhaps not quite as flawless as my iPad mini but with Android devices, I've come to accept that.
I really like where they're going with this interface although there are some definite rough edges. It comes preloaded with 5 home screens labeled: Home, Media, Apps, Office and Web. These can not be removed. Within each, there are some widgets which corresponds to their respective headings. These widgets cannot be changed or removed. The other objects that cannot be changed or removed are the boxes ala Windows 8 which are predetermined to be either editable shortcuts or folders. I find this a bit annoying because sometimes I don't need so many folders and would prefer to just launch an app immediately when I tap it. You can add more homescreens and name them how you like but you can't change their colour or the types of boxes they contain. Overall, it all looks very nice but needs to be more customisable.
Performance:
I haven't had a chance to install any games yet but so far the "feel" of the device seems very solid. I do have a problem when trying to install N.O.V.A. 3, i can't even find it in the Google Play Store. After finding it through Google, it says that my device cannot support it. I don't get it. My One X can install this game and it's far below the specs of the M6. If anyone can let me know why this is, I can install it and let you know how it performs.
Battery Life:
When I opened the box, it was already switched on and showed that it had been running on battery for about 28 hours (so it was probably opened by customs since it was posted out a week ago). Since then I've had the screen almost constantly on doing various things for the last 5 hours and it still has 40% juice left. Pretty good then!
Conclusion:
Overall, I'm quite happy. It has some small niggles but then it was pretty cheap. For the people who are worried that the RK3188 can't handle a retina display, I think you can relax. Everything runs smoothly enough. Plus, if you really prefer a lower resolution, you can change it in the settings to conserve battery life and increase performance. It beats having an M7, M8 or M9 purely because they have much smaller batteries. The 2x5000 mAh battery in the M6 was designed for the retina screen so if you use the normal resolution, it would wipe the competition clean.
MarcusJKX said:
Only thing is, I used both AnTuTu and Android System Info to find out the resolution and there seem to be some discrepancies.
Under HD Mode, both apps reported a resolution of 1536x1952 with 320dpi. Now that's still within Retina level territory but they were advertising 2048x1536. Not a huge difference I know but still a little annoying.
At Normal Mode, AnTuTu reported 1600x1128 and Android System info reported 1200x1528. Not sure why the two differed but the difference is negligible when you do the math.
Click to expand...
Click to collapse
This is normal. Physically, the screen resolution is 2048x1536. The bottom of the screen is allocated for soft buttons, hence you get smaller vertical resolution available to apps.
Do a test - change the tablet orientation, and check the resolution again.
Thank you for this comprehensive review. I myself also own a M6 3g and can mostly agree with your points. I myself think the build quality is quite good. No gaps or loose buttons.
Sent from my JB 4.2.2 powered HTC Desire using Tapatalk
pulsar124 said:
This is normal. Physically, the screen resolution is 2048x1536. The bottom of the screen is allocated for soft buttons, hence you get smaller vertical resolution available to apps.
Do a test - change the tablet orientation, and check the resolution again.
Click to expand...
Click to collapse
Ahh i see, that makes sense. I never owned a device without physical or capacitive buttons so it didn't occur to me.
andbroe said:
Thank you for this comprehensive review. I myself also own a M6 3g and can mostly agree with your points. I myself think the build quality is quite good. No gaps or loose buttons.
Sent from my JB 4.2.2 powered HTC Desire using Tapatalk
Click to expand...
Click to collapse
Yeah I think it's also not bad. I wouldn't really call them gaps, but the seam that runs around the edge of the device definitely doesn't look consistent on my machine; some parts look a tiny fraction wider than the rest. Maybe you had better luck. bBy the way, do you have any idea why the Google Play Store won't let me download N.O.V.A. 3? I'm sure the specs are enough since even my HTC One X running a Tegra 3 can download it. Only thing I can think off is that the internal storage doesn't have enough space but then shouldn't it download into the NAND Flash? I have plenty of space there.
UPDATE: Been spending some more time with it. I am liking it less now that it's frozen up twice (both times requiring a hard reset by sticking a little needle in the small hole next to the back camera - didn't lose anything though). Also, I have a few apps that force the tablet into a vertical orientation and every time, they would force it into an upside down position (where the power button would be on the bottom as well as the front camera). I guess this indicates that the tablet's natural position is contrary to its physical design. I find this quite annoying to be honest and should hopefully be easily fixable with a firmware update. I hope they get on it! God I wish I can install Cyanogenmod on this.
MarcusJKX said:
God I wish I can install Cyanogenmod on this.
Click to expand...
Click to collapse
+1
About the freezing. It happened also to me. Once even during a cold boot! But I am confident it is only a software problem. Maybe one day, when some of the excellent developers of XDA - developer take care of this baby we will get Cyanogenmod.
For the meantime I run RileyROM 1.2 (rooted and cleaned up, based on latest ROM from Pipo) and that works quite good.
See you
andbroe said:
+1
About the freezing. It happened also to me. Once even during a cold boot! But I am confident it is only a software problem. Maybe one day, when some of the excellent developers of XDA - developer take care of this baby we will get Cyanogenmod.
For the meantime I run RileyROM 1.2 (rooted and cleaned up, based on latest ROM from Pipo) and that works quite good.
See you
Click to expand...
Click to collapse
Thanks for the tip! So you didn't encounter any more problems after installing this rom?
MarcusJKX said:
Thanks for the tip! So you didn't encounter any more problems after installing this rom?
Click to expand...
Click to collapse
Another m6 user here also with a one x...
I also had the few freezes but since stopping using chrome, which runs like a dog anyway on this, it hasn't done it. Mines rooted and using the late June firmware. Only issue I've had other than that is a battery hiccup where it went from 65% to 13% in minutes and then back to 65% when the charger was plugged in. I have since ran it dead charged to 100% and calibrated the battery. The battery also doesn't have the correct MV reported
Other than that fast smooth even in retina mode and decent build. Can't find a hw 4k player yet tho like the a31
Steve
5teve said:
Another m6 user here also with a one x...
I also had the few freezes but since stopping using chrome, which runs like a dog anyway on this, it hasn't done it. Mines rooted and using the late June firmware. Only issue I've had other than that is a battery hiccup where it went from 65% to 13% in minutes and then back to 65% when the charger was plugged in. I have since ran it dead charged to 100% and calibrated the battery. The battery also doesn't have the correct MV reported
Other than that fast smooth even in retina mode and decent build. Can't find a hw 4k player yet tho like the a31
Steve
Click to expand...
Click to collapse
Yeah the first time it froze on me, I was also using Chrome. Can't remember what I was doing the second time. Anyways, I'm using the default browser now which suits me fine. Whats the difference between that and chrome anyway? i dont think ive had any issues with the battery although it did go from 14% to 4% awfully quick earlier. What do you mean the battery doesnt have the correct MV? Do you mean its not 10,000 mAh as advertised? How do you check that by the way?
I've been testing the more recent chinese builds (#17 is the latest one I've used) and have had no issues with Chrome or games. They apparently use the new Rockchip SDK 2.0, but I'm hoping we'll see these integrate the latest Mali drivers in the future. You can find the latest releases (currently #20) here http://pan.baidu.com/share/home?uk=1946954351 and if you don't want it in chinese, you should use the Rockchipfirmware kitchen to debloat and modify it. There are no changelogs included with these ROMs though, so you'll be flying blind.
MarcusJKX said:
Yeah the first time it froze on me, I was also using Chrome. Can't remember what I was doing the second time. Anyways, I'm using the default browser now which suits me fine. Whats the difference between that and chrome anyway? i dont think ive had any issues with the battery although it did go from 14% to 4% awfully quick earlier. What do you mean the battery doesnt have the correct MV? Do you mean its not 10,000 mAh as advertised? How do you check that by the way?
Click to expand...
Click to collapse
On mine which is on the SDK2 firmware - there is a big difference with chrome and the stock browsers - chrome is massively laggy, freezes, stutters and is generally rubbish. Stock browser is fast and smooth. The only issue I have is not being able to scroll down on translated pages (htcmania) but change of orientation solves that..
regarding the mV issue, I am using GSam battery monitor and it reports the voltage as being 7mV
Steve
matnl said:
I've been testing the more recent chinese builds (#17 is the latest one I've used) and have had no issues with Chrome or games. They apparently use the new Rockchip SDK 2.0, but I'm hoping we'll see these integrate the latest Mali drivers in the future. You can find the latest releases (currently #20) here http://pan.baidu.com/share/home?uk=1946954351 and if you don't want it in chinese, you should use the Rockchipfirmware kitchen to debloat and modify it. There are no changelogs included with these ROMs though, so you'll be flying blind.
Click to expand...
Click to collapse
Hmm that all sounds a bit too complicated for me. I went through quite a bit of trouble trying to put Cyanogenmod on my One X even with so many instructions available out there. Dont know if I can handle installing a ROM on a device that's not so commonly supported.
5teve said:
regarding the mV issue, I am using GSam battery monitor and it reports the voltage as being 7mV
Steve
Click to expand...
Click to collapse
Hmm well when I use Android System Info, it says my battery is 8mV. Does that mean its 8000mAh? If so then I'm gonna be a bitnpissed coz the whole reason chose the M6 over the M7 was because the battery. I actually prefer a slightly smaller tablet.
MarcusJKX said:
Hmm that all sounds a bit too complicated for me. I went through quite a bit of trouble trying to put Cyanogenmod on my One X even with so many instructions available out there. Dont know if I can handle installing a ROM on a device that's not so commonly supported.
Hmm well when I use Android System Info, it says my battery is 8mV. Does that mean its 8000mAh? If so then I'm gonna be a bitnpissed coz the whole reason chose the M6 over the M7 was because the battery. I actually prefer a slightly smaller tablet.
Click to expand...
Click to collapse
No voltage and current are different. eg a USB port outputs 5v (5000mV) at 500mA (or 0.5A)
Updating firmware on this is easy.. you use software on the PC to upload and flash.. the only panic I had was a very very long boot time the first time while it updates, I thought I had broken it. I was surprised how painless it was.
Thanks
Steve
5teve said:
No voltage and current are different. eg a USB port outputs 5v (5000mV) at 500mA (or 0.5A)
Updating firmware on this is easy.. you use software on the PC to upload and flash.. the only panic I had was a very very long boot time the first time while it updates, I thought I had broken it. I was surprised how painless it was.
Thanks
Steve
Click to expand...
Click to collapse
Well I think I can flash it since they provided the instructions themselves and I found some other instructions online but when matnl mentioned debloating and modifying the ROM to make it English, that worried me. Do you think it's really worth it? Did u notice a big performance increase?
MarcusJKX said:
Well I think I can flash it since they provided the instructions themselves and I found some other instructions online but when matnl mentioned debloating and modifying the ROM to make it English, that worried me. Do you think it's really worth it? Did u notice a big performance increase?
Click to expand...
Click to collapse
Mine was supplied with the pre SDK2 firmware, and it was a big difference going to the SDK2.0 firmware. I didnt debloat at all, I installed the one that said english, it booted in chinese, so i had to work my way through to changing the language to english. On first boot i opted for standard jellybean launcher and then installed apex for a bit of customisability. there didnt look like too much in the way of chinese apps and bloat?
Rooting was easy as there is a batch file on Htcmania that does it for you.
Steve
5teve said:
Mine was supplied with the pre SDK2 firmware, and it was a big difference going to the SDK2.0 firmware. I didnt debloat at all, I installed the one that said english, it booted in chinese, so i had to work my way through to changing the language to english. On first boot i opted for standard jellybean launcher and then installed apex for a bit of customisability. there didnt look like too much in the way of chinese apps and bloat?
Rooting was easy as there is a batch file on Htcmania that does it for you.
Steve
Click to expand...
Click to collapse
I just did the debloat bit because otherwise you're stuck with apps in chinese which are difficult to remove. But as Steve said, it's fairly simple to figure out how to switch the UI to english or anything you like once you've installed the ROM. Like Steve, I also use Apex Launcher rather than the Pipo one.
Another thing I did was use a different parameter file so that I have 4GB of user space rather than the standard 2GB. But this probably is beyond the scope of this thread.
matnl said:
I just did the debloat bit because otherwise you're stuck with apps in chinese which are difficult to remove. But as Steve said, it's fairly simple to figure out how to switch the UI to english or anything you like once you've installed the ROM. Like Steve, I also use Apex Launcher rather than the Pipo one.
Another thing I did was use a different parameter file so that I have 4GB of user space rather than the standard 2GB. But this probably is beyond the scope of this thread.
Click to expand...
Click to collapse
Alright, my M6 froze again today whilst using Pulse so I think I've had enough. I'm gonna try to flash it with a rom. A couple of questions first. How can I check which SDK I'm on? It says my Kernel version is 3.0.36+ from June 25th. Does that mean I'm on SDK2.0 already since it's the latest?
Anyways, I don't wanna bother anyone here with writing out a full instructional so can someone please just confirm that all I need to do is follow this guide: http://www.freak-tab.de/rrileypm/First Time User Guide_pr0_rev5.pdf Of course, instead of using the RileyROM 1.2, I will use the M6 4.2.2 #20 from http://pan.baidu.com/share/home?uk=1946954351 . Also, why are there two files with the same name there? One uploaded on the 13th and one on the 15th of July? Thanks alot guys!
i already posted this to other threads
i bought my pipo m6 a week ago.. so far so bad!.. first off, i got a dirt INSIDE the screen, i was forced to remove the screen guard to see if its not a dirt in between the screen and the screen guard. unfortunately its inside the screen so there's no way of removing it without opening the whole system.. 2nd, im experiencing lags and forced close, QUAD CORE? 2GB RAM? what the!! my friends dual core phone is much better! mine doesnt even have to many apps yet. 3rd, i tried to play 1080 movies, mp4, it lags and crashes at me. aside from all this disappointing experience PIPO luncher form time to time force closes. another worse experience is that i experience FREEZE UP. the whole system froze while browsing facebook, for 20 minutes, all hardware buttons, touchscreen are not responding. i was forced to reset it via the little whole at the back of the device....i already updated to the 6/26 firmware release... but still getting the same issues. battery was good YES. but performance was disappointing. NOT TO MENTION the other users who comment about the SPEAKER! GOD! speaker sucks! based on a video i watched it was loud! but my SONY NEO V is way better! i hope that there is a FIRMWARE FIX to all this! except ofcourse about the screen dirt.. i was expecting to much about the new processor (QUAD CORE, better the DUAL CORE, RIGHT???), the ram but was getting to much frustration. the only GREAT thing about this device is the RETINA SCREEN, not including the DIRT of course, the the BATTERY!
Click to expand...
Click to collapse
SquallDNA said:
i already posted this to other threads
Click to expand...
Click to collapse
I can understand your frustration. I've experienced everything you mentioned except for the dirt (although I do have a small black smudge underneath the glass near the right speaker). I'm really starting to regret getting this thing (especially with news of the Nexus 2 7" coming out soon at a possibly cheaper price point). I'm really hoping installing something like the RileyROM 1.2 will help fix these issues.
MarcusJKX said:
I can understand your frustration. I've experienced everything you mentioned except for the dirt (although I do have a small black smudge underneath the glass near the right speaker). I'm really starting to regret getting this thing (especially with news of the Nexus 2 7" coming out soon at a possibly cheaper price point). I'm really hoping installing something like the RileyROM 1.2 will help fix these issues.
Click to expand...
Click to collapse
i hope so too. thanks
SquallDNA said:
i hope so too. thanks
Click to expand...
Click to collapse
I just flashed the RileyROM 1.2. They were right, it really was very easy. I'm in the process of restoring everything. I'll report back with my impressions on the performance later.

[RANT] - Lollipop is not great, but tolerable

I was very excited to see this:
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
So, I pushed ahead thinking that Lollipop has already been in the wild long enough, surely the initial kinks like WiFi drops and battery hogging have been resolved. No such luck, and after doing it, it looks like I'm going to have to do this:
http://forum.xda-developers.com/showthread.php?t=2784880
Lollipop is horrible. My phone no longer does one of the most basic things that's been around since the G1: Go (the F) to sleep! Seriously?!?!
Here are my other problems:
-Phone doesn't sleep on its own if timeout set for longer than 30 seconds (and even then, it's not reliable)
-WiFi doesn't reconnect after sleep (when sleep even happens, which is only when I push the button to force it). I have to toggle WiFi off/on to reconnect.
-Battery drain is pretty bad. My first month with the S5 had me barely even thinking about charging. Now, with Lollipop, I feel like I'm back on my old HTC MyTouch!
-The silly way they implemented the lockscreen. Here's my problem: I can ONLY use Settings > Sound and Notification > While locked with the option "Do not show notifications". Why? Any other setting blocks the Owner Information (Settings > Lock screen > Owner Information). If I don't, and if I'm unfortunate enough to have lost my phone, yet fortunate enough to have it found by a good samaritan, I better hope I haven't miss any calls or received any messages in the meantime. This one REALLY GRINDS MY GEARS because it's a horribly-implemented Feature ... at least the others are unintended bugs, but somebody had to give this one the green light.
-I can't adjust the icon sizes anymore. There used to be a choice of large or small icons.
-Oh, and for some bonehead reason, Samsung decided their stock ROM wouldn't have the Lollipop built-in flashlight icon.
-Another intentional feature that I can't disable: the phone keeps a history of recent activity that persists through reboots. YUCK! Why can I not disable this?!?! Again, another bonehead call that somebody had to green-light, without even considering the possibility that I might want to turn it off!
-All the UI "polishing" and improvements don't mean a thing to me, I want it to work.
I found all of the above in less than 24 hours on Lollipop! I might lose my s**t entirely if I keep it for much longer.
Here is my take on why:
Google and Apple are in a heated race to the top. They wrongly assume that what will set each apart from one another is almost entirely dependent on what a few bloggers say about some hot new feature. The paradigm appears to be something like: "Who cares if millions of loyal subscribers lose functionality when we want 100 people to have this one obscure and half-baked feature?"
Latest != Greatest
-----
EDIT:
I've had a change of heart on this. It's not too bad, I just needed to adjust a few settings and live with the other issues.
I too do not like the lolli. Bad battery life, and for some reason the Heart rate monitor led turns on whenever anything is within a half inch of it. I just can't figure that out, but it sucks the battery like a red led vampire!
Sent from my SM-G900V using XDA Premium HD app
Tldnr
Don't start a thread just to complain
Lmfao when I saw that link and clicked it, I actually had that same thread opened moments before opening this thread because I, too, am having to go back to KitKat. I laughed for a good 20 seconds. Lollipop is freaking terrible at the moment. Zero customization and Google + Samsung are forcing too much garbage on us without giving any bit of customization.
mygraine said:
I too do not like the lolli. Bad battery life, and for some reason the Heart rate monitor led turns on whenever anything is within a half inch of it. I just can't figure that out, but it sucks the battery like a red led vampire!
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
Heart rate monitor thing was fixed in OC4 I think, but if it still goes off a factory reset will fix it.
Agree
OP, I agree with you. It probably is the first version without the definitely improvement overall for users. It is risky to upgrade and troublesome if it didn't work out well on your devices. Wish Android 5.1 could be better than Kitkat overall.
I have absolutely no problems with the lollipop. I always had it stock from the start and just let the OTAs take over on their own. Have you tried even rebooting into recovery and wipe cache? Even though it's not a custom recovery you can still do that, also even when you dirty flash nightlies that's something that's good practice. My wife's phone had similar issues that I wasn't experiencing, until I did that to her phone and now she's having no problems. Now the general annoyances of how Samsung implemented ****, I understand, it's stupid with not having native flashlight, tethering is annoying having to use foxfi, and the lockscreen.. bleh. But other than that, everything is actually working like it is supposed to
Chiming in, Yes it's bad.
I have two lines with Verizon, both with S5 phones on them. Great device, its actually the first Android phone I've had that I did not do anything with beyond the out of the box experience. That changed when Lollipop was pushed via OTA, the most prominent issue I experienced on both of my S5s is general responsiveness issues, simple things like switching apps or launching apps sometimes would leave me with a white screen for between 5-10 seconds, an eternity especially when the device was lighting fast on 4.4.4 Kitkat. I followed every suggestion from wiping the device in Android, Wiping in recovery, wiping cache, all of these with only marginal improvements. It really is a shame that Google / Samsung did not do a bit better quality assurance on this build before it was pushed out to carriers and ultimately peoples devices. It says something that other carriers skipped 5.0 and that very rapidly 5.1 surfaced on Newer devices / Nexus devices.
As of last night both of my phones are Odin'd back to 4.4.4 and its like having a brand new phone. Sure, there might not be as much polish, but there are no features I will die without having. The only one that I can say I do miss is the feature where the device will disable the lock screen when your smart watch or home WiFi is connected.
Here's to hoping that Google eventually gets Android 5 right in the optimization department and that Samsung picks it up for the S5, and that Verizon gets it ready for OTA before I am ready to move on to a new device. Not interested in the S6 at all for its sealed nature for storage and battery, but that's for another thread on a different day.
-Nate
I Have to agree. I've given it several chances to perform to expectations but it just fails.... ( insert sad puppy face here ) no matter what I have tried it just under-performs and the biggest thing is the horrible battery life. Sooooo yeah like most of the other commentators in this thread, I'm moving back to 4.4.4......
Unfortunately/fortunately, I have found most of my battery issues were solved with a factory reset. I'm more frustrated that Samsung seems to having issues with Android Auto.
ldeveraux said:
Tldnr
Don't start a thread just to complain
Click to expand...
Click to collapse
Observations, not complaints. Getting these points out in the open is an essential stepping stone to getting them fixed. Maybe, just maybe, a Producteer or architect at Google has read this by now so they know what to improve next time. Problems cannot be solved until they are defined.
---
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.
CaptainRewind said:
Observations, not complaints. Getting these points out in the open is an essential stepping stone to getting them fixed. Maybe, just maybe, a Producteer or architect at Google has read this by now so they know what to improve next time. Problems cannot be solved until they are defined.
---
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.
Click to expand...
Click to collapse
Yeah, go start a petition, just like the bootloader guys, see how far it got them? No one from google reads your complaint threads and regrets their work...
ldeveraux said:
Yeah, go start a petition, just like the bootloader guys, see how far it got them? No one from google reads your complaint threads and regrets their work...
Click to expand...
Click to collapse
Yeah, I guess that was wishful thinking.
In any case, it seems this thread was a complete waste of time. It made me feel better at the time, but looking back on it and the purpose of this site, it doesn't add any value or help anyone modify their phone. Not only that, one of my primary reasons for the OP was the screen lock issues which turned out to be an app, not the Android version.
So, I stand corrected. Live and learn. Enough said.
My wife would never let me root her phone ever. After this update either I find a way to go back a few with root or it goes against the wall. Looks like I have to start reading and figure out how to do this.
Lol I love how you described it. Sometimes you have to vent. Lol
CaptainRewind said:
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.
Click to expand...
Click to collapse
Care to share where this app is?
Sent from my SM-G900V using XDA Free mobile app
dk-v1 said:
Care to share where this app is?
Click to expand...
Click to collapse
This is the one:
https://play.google.com/store/apps/details?id=com.eolwral.osmonitor&hl=en
It's a great app, but something about it staying active in the Notification Bar keeps the screen awake. I still use the app, just can't keep the notification active in Lollipop.
And in case it isn't obvious, even though I still have my concerns about Lollipop, I never did go about the procedure of downgrading. It looks like a risky procedure, and I don't want to trip Knox, or worse, have a brick.
CaptainRewind said:
This is the one:
https://play.google.com/store/apps/details?id=com.eolwral.osmonitor&hl=en
It's a great app, but something about it staying active in the Notification Bar keeps the screen awake. I still use the app, just can't keep the notification active in Lollipop.
And in case it isn't obvious, even though I still have my concerns about Lollipop, I never did go about the procedure of downgrading. It looks like a risky procedure, and I don't want to trip Knox, or worse, have a brick.
Click to expand...
Click to collapse
Ok, so it's not a stock app. I am still having poor battery life and overheating issues.
Sent from my SM-G900V using XDA Free mobile app

Micro-stutters and GPU governor behaviour

Hello,
Like a lot of people on the various Oneplus 6 forums, I too am experiencing occasional micro-stutters in the UI. I wanted to start a discussion here for people who are also experiencing this and also to share various ways to mitigate it.
On my Oneplus 3 (had it for 2 years) I always had the GPU governor set to "performance" and it was always butter smooth with decent battery life. There were never any dropped frames or micro-stutters because everytime I touched my screen the GPU would jump to max (450Mhz) before dropping back down to minimum. This ensured a speedy UI when touching and scrolling the screen.
I want to repeat this on my Oneplus 6 but I'm having difficulty in getting the phone to use the performance GPU governor. I can set it to performance but doing so doesn't ramp the GPU to max frequency when touching the screen like it did on my Oneplus 3
I'm currently on OOS 5.1.8 rooted with magisk and running ElementalX kernel.
Can anyone please test this out on their phone - set performance GPU governor and check what happens to the GPU frequency when touching the screen (use a GPU frequency monitoring app). It should jump to MAX freqency but it doesn't for me.
I'm interested to know if it does for anyone else - perhaps on a different kernel than ElementalX
have this micro stuttering, very annoying ...
damn ,just as i was about to get a op6 after next week.
what exactly is this micro stuttering? im currently using a 6p and feel somewhat outdated with the snap810.
i get occassional lags and its annoying, and also stutters.
im surprised to see the stuttering in op6, if more ppl have this i might ditch the 6 and get a 5t..
EDIT: Darn, googled oneplus stuttering and it seems the 5t is affected too ._.'
If you are experiencing shuttering while scrolling as the finger is on the screen. It's an app with accessibility access causing it. Removing the app completely fixes it
leondestiny said:
damn ,just as i was about to get a op6 after next week.
what exactly is this micro stuttering? im currently using a 6p and feel somewhat outdated with the snap810.
i get occassional lags and its annoying, and also stutters.
im surprised to see the stuttering in op6, if more ppl have this i might ditch the 6 and get a 5t..
EDIT: Darn, googled oneplus stuttering and it seems the 5t is affected too ._.'
Click to expand...
Click to collapse
Don't listen to him, he's full of crap honestly. If you CHOOSE to obsess over minor non-issues that 99.9% of people won't notice, that's your (OP's) problem, not OnePlus's. This phone is faster than anything on the market and if OP is really so desperate to find something better he's more than welcome to develop his own ROMs and kernels, or produce his own phone that he thinks is perfect and see how many people buy it.
TheNetwork said:
Don't listen to him, he's full of crap honestly. If you CHOOSE to obsess over minor non-issues that 99.9% of people won't notice, that's your (OP's) problem, not OnePlus's. This phone is faster than anything on the market and if OP is really so desperate to find something better he's more than welcome to develop his own ROMs and kernels, or produce his own phone that he thinks is perfect and see how many people buy it.
Click to expand...
Click to collapse
honestly i was paranoid for a while only, i know the op6 is the phone to get for me.
i will probably get one after like 10 days..
i bet it will be like night and day difference between my 6p ..
excited to get it, which color would you recommend?
i wanted the grey version initially but i heard it can be slippery?
the black one will have more grip but is a fingerprint magnet, what about the white one.. hmm
i guess either of the 3 will be fine, will see what they have i guess.
and i think OP could fix his stutters simply by rooting and flashing some goodies.
i root my phones day1 XD
i hope dev support will be good for OP6, heard that theres that a/b thing.
and some roms called treble roms? apparently are not so stable, but that there will eventually be normal custom roms..
plus i saw nathan in the op6 section, theres flash kernel for the op6 baby..
cant go wrong with this one..
now i only need to find myself a good glass screen protector ,since the one it comes with is a plastic sp.
TheNetwork said:
Don't listen to him, he's full of crap honestly. If you CHOOSE to obsess over minor non-issues that 99.9% of people won't notice, that's your (OP's) problem, not OnePlus's. This phone is faster than anything on the market and if OP is really so desperate to find something better he's more than welcome to develop his own ROMs and kernels, or produce his own phone that he thinks is perfect and see how many people buy it.
Click to expand...
Click to collapse
Mind your own business. Minor non issues, yeah sure. You obviously have no idea what op is talking about.
i too have noticed it, and i'm using franken kernel
masri1987 said:
i too have noticed it, and i'm using franken kernel
Click to expand...
Click to collapse
Something like an app is causing that. I can run through apps, scroll constantly in settings, scroll and surf on the web constantly with no stopping and I get maybe 1 frame lost every 20 seconds or so. I have like 60 apps installed.
I'm using stock , never rooted , I have never notice this stutter.
I have rooted alot of phones too, just not the op6 because I see no need to.
Maybe faulty units ?
If you want to see stutter use the s8 lol.
I noticed does drops also. But whit https://forum.xda-developers.com/oneplus-6/development/kernel-franken-t3799290/ newest version it almost gone for me. Very little when it occurs.
For me those drops are gone again after a reboot, but they are always coming back.
Lownita said:
For me those drops are gone again after a reboot, but they are always coming back.
Click to expand...
Click to collapse
Yes, I noticed that, so far almost a day and no annoying stutters, hope so to stay that way ? will report how it will stay after a night.
Driver007 said:
Yes, I noticed that, so far almost a day and no annoying stutters, hope so to stay that way ? will report how it will stay after a night.
Click to expand...
Click to collapse
That's mostly when they are coming back for me, after a long time of idling. Let us know, thanks!
Fully stock phone. No microstutters, but the frames do drop from 60+ normally to about 30 on some ui interactions. Still smooth to the eye though.
I've come to the conclusion that the UI stutters and animation jank is much worse in 5.1.8 so I am downgrading to 5.1.6 until Oneplus sorts it's Oxygen OS out. There are clearly problems within OOS itself with stutters. Many others are also observing this too and those who are not, are either not bothered by it (maybe used Samsung previously so are used to it) or simply don't see it even though it is there.
The proof of this is that I have set performance governors on both big and little CPU clusters AND also set performance GPU governor (so in effect, throwing the entire resources of Oneplus 6 at the UI) and still there are dropped frames all over the UI. Hell, even my old Oneplus 3 was never nearly this bad and was buttery smooth in comparison. I am completely disappointed with this phone having been superbly impressed with the Oneplus 3. These kind of UI stutters are why I don't touch Samsung anymore and I thought I had found refuge in Oneplus phones
I'm probably going to get a Pixel 3 next time round and if I can't get a buttery smooth UI on Oneplus 6. I'm begginning to consider selling it and moving on such is my frustration and disappointment.
Come on Oneplus! you can do better than this
Edit: before anyone starts saying anything, I DON'T have xposed or any fancy mods. All I have is stock OOS with Magisk rooted. I have tried 3 different kernels on 5.1.8 - Elemental, Stock and Blu_spark. All produce these stutters/frame drops.
carlos67 said:
I've come to the conclusion that the UI stutters and animation jank is much worse in 5.1.8 so I am downgrading to 5.1.6 until Oneplus sorts it's Oxygen OS out. There are clearly problems within OOS itself with stutters. Many others are also observing this too and those who are not, are either not bothered by it (maybe used Samsung previously so are used to it) or simply don't see it even though it is there.
The proof of this is that I have set performance governors on both big and little CPU clusters AND also set performance GPU governor (so in effect, throwing the entire resources of Oneplus 6 at the UI) and still there are dropped frames all over the UI. Hell, even my old Oneplus 3 was never nearly this bad and was buttery smooth in comparison. I am completely disappointed with this phone having been superbly impressed with the Oneplus 3. These kind of UI stutters are why I don't touch Samsung anymore and I thought I had found refuge in Oneplus phones
I'm probably going to get a Pixel 3 next time round and if I can't get a buttery smooth UI on Oneplus 6. I'm begginning to consider selling it and moving on such is my frustration and disappointment.
Come on Oneplus! you can do better than this
Edit: before anyone starts saying anything, I DON'T have xposed or any fancy mods. All I have is stock OOS with Magisk rooted. I have tried 3 different kernels on 5.1.8 - Elemental, Stock and Blu_spark. All produce these stutters/frame drops.
Click to expand...
Click to collapse
Can you post the bug reports or your observations to official oneplus bug reporting platform?
This will draw their attention and issue might be solved much faster than posting it here.
https://forums.oneplus.com/feedback/
Thanks
sarus_b said:
Can you post the bug reports or your observations to official oneplus bug reporting platform?
This will draw their attention and issue might be solved much faster than posting it here.
https://forums.oneplus.com/feedback/
Thanks
Click to expand...
Click to collapse
Have just submitted a bug report to Oneplus. Thanks for the link :good:
I suggest anyone else experiencing this does the same. If we all do then Oneplus may take notice.
carlos67 said:
Have just submitted a bug report to Oneplus. Thanks for the link :good:
I suggest anyone else experiencing this does the same. If we all do then Oneplus may take notice.
Click to expand...
Click to collapse
Share link so I can confirm it
marko94 said:
Share link so I can confirm it
Click to expand...
Click to collapse
The post immediatly above mine

Ram management

What to enable or disable to make it less aggressive?
Bump
Hi,
I have the same problem and it is f*** annoying! I have the 8GB version of the OP7pro and I don't know why the phone always closes my apps after a certain amount of time. I have disabled all (as far as I know) battery optimization features and also disabled the RAM booster.
In parallel I still run a Galaxy Note 3 with a really old custom rom, which has started to act a bit buggy now, but this phone does not overwrite MY settings and kills apps I want to keep open.
Does anyone know how to get rid of this behavior? Or is the only way to flash a custom rom again? I don't know if it is related to Oxygen OS or Android 9.
Thanks
GP
This is the problem with Chinese oems. Aggressive ram management, notification problems, not quite there cameras. Having the hardware is one thing. Software r & d is something else.
Can't remember exactly where I read it but...OnePlus is supposedly working on an update to "fix" the problem with aggressive killing of background apps as a result of all the complaints they receive concerning this issue. Something that can possibly help along with shutting off all battery/ram management is to lock your open apps to keep them open. While scrolling through your open apps you will see a three dot menu in the top right corner and one of the options is to "lock" the app which is supposed to lock it in memory/RAM. YMMV
jaseman said:
Can't remember exactly where I read it but...OnePlus is supposedly working on an update to "fix" the problem with aggressive killing of background apps as a result of all the complaints they receive concerning this issue. Something that can possibly help along with shutting off all battery/ram management is to lock your open apps to keep them open. While scrolling through your open apps you will see a three dot menu in the top right corner and one of the options is to "lock" the app which is supposed to lock it in memory/RAM. YMMV
Click to expand...
Click to collapse
Are we sure this isn't a Pie issue? I just came from a pixel 3xl and had the same issues in the beginning. Everyone blamed the 4gb RAM as the culprit. Google eventually updated a Fix but it wasn't 100% fixed. It was better but apps still closed to early. So maybe we're looking at an Android problem. Who knows
Sent from my GM1915 using Tapatalk
tropical cactus said:
This is the problem with Chinese oems. Aggressive ram management, notification problems, not quite there cameras. Having the hardware is one thing. Software r & d is something else.
Click to expand...
Click to collapse
This is totally crap, I switched from my Note 3, which I still like very much (but only with AOSP based custom ROM) to OP because I don't like the way Samsung and Huawei gone to. I'm not rooted right now, so I can not tell what can be done with Magisk Modules or Xposed Modules (or other mods) on a Oxygen based ROM.
Can someone tell if this behavior can be stopped with mods or is the only way to switch to an AOSP based ROM again?
I wanted to give Oxygen OS a try but right now I'm not fully convinced with the current situation, even if OP is one of the fastest supplier for updates. I don't like it, when a manufacturer tells me what I can do with a device and what not. At least OP should give me the choice how strict the RAM management is and when I want to get apps closed.
Missing notifications is one other big point. Due to the fact that there is no notification LED and no AOD (STILL) I tried several third party apps to get a AOD, but the battery drain on this apps is heavy as f*** and they often do not work correctly, because the system prevents them to run correctly.
Does anyone know a good way to get a reliable way for notifications?
Thanks.
GP
General-Pain-666 said:
This is totally crap, I switched from my Note 3, which I still like very much (but only with AOSP based custom ROM) to OP because I don't like the way Samsung and Huawei gone to. I'm not rooted right now, so I can not tell what can be done with Magisk Modules or Xposed Modules (or other mods) on a Oxygen based ROM.
Can someone tell if this behavior can be stopped with mods or is the only way to switch to an AOSP based ROM again?
I wanted to give Oxygen OS a try but right now I'm not fully convinced with the current situation, even if OP is one of the fastest supplier for updates. I don't like it, when a manufacturer tells me what I can do with a device and what not. At least OP should give me the choice how strict the RAM management is and when I want to get apps closed.
Missing notifications is one other big point. Due to the fact that there is no notification LED and no AOD (STILL) I tried several third party apps to get a AOD, but the battery drain on this apps is heavy as f*** and they often do not work correctly, because the system prevents them to run correctly.
Does anyone know a good way to get a reliable way for notifications?
Thanks.
GP
Click to expand...
Click to collapse
Not only that. 3rd party apps like notification buddy work but Google Assistant stops working once you install it. I don't know what GA has to do with notification lighting. It's supposed to be a phone first and foremost. OnePlus seems to have forgotten what it is they're making. Something as basic as missed notifications seems not terribly important to them.
tropical cactus said:
Not only that. 3rd party apps like notification buddy work but Google Assistant stops working once you install it. I don't know what GA has to do with notification lighting. It's supposed to be a phone first and foremost. OnePlus seems to have forgotten what it is they're making. Something as basic as missed notifications seems not terribly important to them.
Click to expand...
Click to collapse
I agree. Samsung and Huawei show that AOD can work without heavy battery drain, so why can't OP get this to work or can they but don't want it?
I will root the device and have a look what I can optimize.
What I cannot change (unfortunately I had no chance to hands on the device before I bought it) is the size and the weight. It is to big and way to heavy. Not only while taking a phone call, even if you just hold it in one hand and do some stuff, it gets heavy within a very short time.
Maybe this OP was my first and last one - I will see. But it seems that all devices get bigger and heavier with every iteration, which is totally insane.
smallsmx301 said:
Are we sure this isn't a Pie issue? I just came from a pixel 3xl and had the same issues in the beginning. Everyone blamed the 4gb RAM as the culprit. Google eventually updated a Fix but it wasn't 100% fixed. It was better but apps still closed to early. So maybe we're looking at an Android problem. Who knows
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
It's definitely a pie thing as Android 10 had much better ram management even on pixel 2xl with 4gb ram. I suspect it will resolve most of our problems.
General-Pain-666 said:
I agree. Samsung and Huawei show that AOD can work without heavy battery drain, so why can't OP get this to work or can they but don't want it?
I will root the device and have a look what I can optimize.
What I cannot change (unfortunately I had no chance to hands on the device before I bought it) is the size and the weight. It is to big and way to heavy. Not only while taking a phone call, even if you just hold it in one hand and do some stuff, it gets heavy within a very short time.
Maybe this OP was my first and last one - I will see. But it seems that all devices get bigger and heavier with every iteration, which is totally insane.
Click to expand...
Click to collapse
I have a problem with the weight as well, like my previous note 9. I got the s10+ after that, before being enticed by all the YouTube reviews of the 7pro at launch. I'm beginning to regret that decision. Dual speakers are no where near the s10+ and neither is video stabilisation. I'm on the beta 2 now, rooted and the experience is beginning to improve. Sure there are pros like the fast charging, display and the quick implementation of android 10. I can't justify the note 10 and all the year end releases with SD 865 round the corner so I guess I'll just have to put up with it.
tropical cactus said:
I have a problem with the weight as well, like my previous note 9. I got the s10+ after that, before being enticed by all the YouTube reviews of the 7pro at launch. I'm beginning to regret that decision. Dual speakers are no where near the s10+ and neither is video stabilisation. I'm on the beta 2 now, rooted and the experience is beginning to improve. Sure there are pros like the fast charging, display and the quick implementation of android 10. I can't justify the note 10 and all the year end releases with SD 865 round the corner so I guess I'll just have to put up with it.
Click to expand...
Click to collapse
You're on Beta software...what do you expect? I'm on stable and all is working fine. I'm on T-Mobile but using an unlocked 7 Pro purchased from OnePlus directly.
jaseman said:
You're on Beta software...what do you expect? I'm on stable and all is working fine. I'm on T-Mobile but using an unlocked 7 Pro purchased from OnePlus directly.
Click to expand...
Click to collapse
Did you actually read what I wrote? The experience has improved on android 10.
i had the s10+ and i couldnt deal with the half bakes software. so oneplus was the natural choice for me.
sure the speakers arent the best but theyre plenty fine - its not like we use our speakers for hidef sound, wireless headphones or a jukebox can take care of the rest (i have these strategically placed around the house so its never an issue when i play music)
failing AOD, dt2w is just as good imo.
tropical cactus said:
I have a problem with the weight as well, like my previous note 9. I got the s10+ after that, before being enticed by all the YouTube reviews of the 7pro at launch. I'm beginning to regret that decision. Dual speakers are no where near the s10+ and neither is video stabilisation. I'm on the beta 2 now, rooted and the experience is beginning to improve. Sure there are pros like the fast charging, display and the quick implementation of android 10. I can't justify the note 10 and all the year end releases with SD 865 round the corner so I guess I'll just have to put up with it.
Click to expand...
Click to collapse
virtyx said:
i had the s10+ and i couldnt deal with the half bakes software. so oneplus was the natural choice for me.
sure the speakers arent the best but theyre plenty fine - its not like we use our speakers for hidef sound, wireless headphones or a jukebox can take care of the rest (i have these strategically placed around the house so its never an issue when i play music)
failing AOD, dt2w is just as good imo.
Click to expand...
Click to collapse
If you use Magisk, make sure to flash Ainur Sauron. That's an absolute game-changer for audio quality. I can't say the audio will quite compare to the Note 9 (I own it), but it should be fairly comparable to the S10+ (Have two in the family). The Note 9 has the advantage of actual front-facing speakers since it has bezel.
If you want to use Viper or JamesDSP, you'll need to also flash AML in Magisk which allows for multiple audio mods to be integrated. If you want a simple flash and away w/o further customization, then just flash Ainur Sauron.
Thank you. Good recommendation

Question Screen weirdness on me the other day.

My pixel 7 pro freaked out on me the other day and went black on me when I played a game and didn't come back for over 15 minutes then finally was responding again. Any reason why this happened . Hopefully software and not hardware. Hasn't happened since but still concerning .
Anyone ?
Redbeardkevv said:
Anyone ?
Click to expand...
Click to collapse
Flaky game? I never play games on any tool, which a smartphone is. I wish the OEM's would stop trying to make it even possible. Buy a "gaming" phone which is designed specifically for that purpose. In fact, some of the best phones available today (spec wise) are gaming phones! If it only happened while playing the game then that is where I would look.
jaseman said:
Flaky game? I never play games on any tool, which a smartphone is. I wish the OEM's would stop trying to make it even possible. Buy a "gaming" phone which is designed specifically for that purpose. In fact, some of the best phones available today (spec wise) are gaming phones! If it only happened while playing the game then that is where I would look.
Click to expand...
Click to collapse
This is one of the most ridiculous responses I have ever seen. There is nothing that makes a "gaming phone" special. They're using the same hardware and software as any other phone with gaming-specific gimmicks. The phone has a throttle mechanism to prevent any kind of damage.
EtherealRemnant said:
This is one of the most ridiculous responses I have ever seen. There is nothing that makes a "gaming phone" special. They're using the same hardware and software as any other phone with gaming-specific gimmicks. The phone has a throttle mechanism to prevent any kind of damage.
Click to expand...
Click to collapse
Ridiculous...maybe...but the fact remains that you experienced this WHILE playing a game! So I wonder what the problem may be?
Hmmm
jaseman said:
Ridiculous...maybe...but the fact remains that you experienced this WHILE playing a game! So I wonder what the problem may be?
Click to expand...
Click to collapse
That's called a hardware defect if the hardware can't cope. Going blank for 15 minutes is not normal.
Hardware hmm and not software?
Redbeardkevv said:
Hardware hmm and not software?
Click to expand...
Click to collapse
What were you playing? If it was a graphically intensive game, I would definitely lean more towards blaming the hardware. It's very rare that a game can actually make a phone that unstable. In fact I can't remember the last time I've had a game make my phone unresponsive.
Roblox with my nephew
Redbeardkevv said:
Roblox with my nephew
Click to expand...
Click to collapse
I've never played that game but their site seems to suggest some rather low requirements so I would be shocked if an ARMv8 processor like Tensor 2 is going to struggle with it.
Android warning screens
Due to the very large number of Android devices in existence, we cannot be certain that all devices will run optimally even if they are running the correct version of the operating system and do not have a Tegra 2 chipset.
We have 2 levels of unsupported Android devices - skippable and unskippable:
Skippable Devices: These types of devices will get a warning telling you that your device may not be powerful enough to play experiences smoothly. This is just a warning to let you know that while your device isn't specifically supported, experiences might still run though they will likely lag a little (or a lot). Tapping outside the warning box will make it go away and the experience should keep loading.
Unskippable Devices: will get a message that informs you that your device doesn't meet the minimum system requirements. This means the device is not able to play experiences on Roblox. This message usually shows up on devices that use the Tegra 2 graphics chipset or a processor older than ARMv7. These kinds of tablets/phones do not support features that the Roblox needs to be able to function. However, users with these unskippable messages will still be able to access all other parts of the app outside of experiences.
Click to expand...
Click to collapse
https://en.help.roblox.com/hc/en-us/articles/203625474-ROBLOX-Mobile-System-Requirements
Yea I was thinking it had low requirements. Maybe bad coding ??? But then again no other app or game has caused that to happen. Sooo. Yea
I don't think it's software. I already had one screen die. Went black and never came back on. I had it fixed under warranty at a local UbreakIFix (Asurion - Google's warranty partner). Techs were aware of a similar problem with the 5a and replaced my screen same day.
I've had a few wonky screen issues that hard locked my phone. Had one go black, but fortunately came back after holding power down. It once went all yellow with weird shapes/sections. And then just had some freezes with artifacts on the screen.
I'm going away for the holidays so I'll send it back when I get home if I'm still having issues. If you're going away, I'd suggest taking a backup phone just in case. Had mine die the first time when I was visiting my folks out of state. It sucked with no backup.
One thing I noticed is the screen does a fuzzy flash whenever I plug in a USB charger. It's only a split second but it is noticeable. Has anyone else experienced that?
Superguy said:
I don't think it's software. I already had one screen die. Went black and never came back on. I had it fixed under warranty at a local UbreakIFix (Asurion - Google's warranty partner). Techs were aware of a similar problem with the 5a and replaced my screen same day.
Click to expand...
Click to collapse
Most of these failures have been a combination of both hardware and software - nothing is actually wrong with the screen. I'm not sure exactly how it happens, but it seems that this usually involves a OS crash (phone freezing up) followed by an attempt to reboot, but for some reason the bootloader has become corrupted and the device won't start. Fixing it generally involves replacing the mainboard, because most repair centers don't have the QPST or the software needed to perform low level reflash. This is a known issue over several generations of Pixels; the cause is unknown.
V0latyle said:
Most of these failures have been a combination of both hardware and software - nothing is actually wrong with the screen. I'm not sure exactly how it happens, but it seems that this usually involves a OS crash (phone freezing up) followed by an attempt to reboot, but for some reason the bootloader has become corrupted and the device won't start. Fixing it generally involves replacing the mainboard, because most repair centers don't have the QPST or the software needed to perform low level reflash. This is a known issue over several generations of Pixels; the cause is unknown.
Click to expand...
Click to collapse
What was weird is when mine went black, the phone would still boot and in theory was still usable. Pushing the buttons gave haptic feedback like they were bringing up the power menu or adjusting the volume. I just couldn't see what was going on or use touch to give input.
They told me they just replaced the screen. Didn't touch the motherboard.
I was using one of the custom kernels so I ended up having to wipe it and went back to stock kernel with magisk and some modules. It hasn't acted up as much as it did with the custom kernel, but there are still issues. I suppose it could be something that's messed up in the stock kernel, and perhaps tweaks a dev made in theirs may have exasperated it some.
If I end ups ending it back, I'll try a custom kernel again, but for now, I'm just sticking with stock.
*no disrespect intended or implied to any dev
Superguy said:
What was weird is when mine went black, the phone would still boot and in theory was still usable. Pushing the buttons gave haptic feedback like they were bringing up the power menu or adjusting the volume. I just couldn't see what was going on or use touch to give input.
Click to expand...
Click to collapse
Yeah, that's definitely a display issue. I'm talking about when the device doesn't work or respond at all, maybe vibrates on power up but doesn't respond to anything, and usually will come up as "Qualcomm Bulk USB" or something when connected to PC
Superguy said:
They told me they just replaced the screen. Didn't touch the motherboard.
I was using one of the custom kernels so I ended up having to wipe it and went back to stock kernel with magisk and some modules. It hasn't acted up as much as it did with the custom kernel, but there are still issues. I suppose it could be something that's messed up in the stock kernel, and perhaps tweaks a dev made in theirs may have exasperated it some.
If I end ups ending it back, I'll try a custom kernel again, but for now, I'm just sticking with stock.
*no disrespect intended or implied to any dev
Click to expand...
Click to collapse
For sure, active development may or may not have stability issues, it's all a learning process!

Categories

Resources