Develop Bugs

eInk update modes

There seems to be very little actual documentation on the various eInk update modes.
Most of the information seems to have been extracted from working code.
Some of that code does not seem to be optimal in any case.
I'd like to start this thread on a discussion of the update modes.
You can look at all the code posted, but the bottom line is that eInk mode is configured by passing six discrete pieces of information to the EPD driver.
These six pieces may be wrapped up into a single static entity.
Name of entity requesting change (for logging purposes only)
Region, one of enumRegion[] (Region 4-7)
A rectangle, normally {0, 0, 600, 800}
Wave, one of enumWave[] (GC, GU, DU, A2, GL16, AUTO)
Mode, one of enumMode[] (INACTIVE, ACTIVE, ONESHOT, CLEAR, ACTIVE_ALL, ONESHOT_ALL, CLEAR_ALL)
Threshold, an int 1-15, only applies to A2 mode
A2 is the one bit, fast drawing method. It leaves ghosting behind.
In some applications, you would like to enable faster scrolling in A2 mode and then have it revert to "normal" upon completion.
I have an application with a full screen scroll.
After experimenting with the values, these two configs seem to do the job nicely.
Code:
configA2Enter = makeConfig(rpc, waveEnums[WAVE_A2], regionEnums[REGION_6], modeEnums[MODE_ACTIVE_ALL], THRESHOLD);
configA2Exit = makeConfig(rpc, waveEnums[WAVE_AUTO], regionEnums[REGION_6], modeEnums[MODE_ACTIVE_ALL], 0);
No user intervention is necessary, it scrolls quickly and redraws a clean image when done.
(A view.invalidate() is necessary after you invoke configA2Exit)
Does anybody have any further insight into these values or suggestions for improving them?

Some additional information on the A2 ("no refresh", 1 bit) mode.
Some of the other modes can be selectively applied to portions of the screen.
The A2 mode may only be applied to the entire screen.
The threshold value, which some may construe as "brightness" or "contrast"
is the cutoff threshold between black and white of the original image.
A value of 1 will only generate black in the darkest areas of the original image.
A value of 15 will only generate white in the whitest areas of the original image.
That is, 1 will give you a light image, 15 a dark image.

Renate NST said:
Some additional information on the A2 ("no refresh", 1 bit) mode.
Some of the other modes can be selectively applied to portions of the screen.
The A2 mode may only be applied to the entire screen.
The threshold value, which some may construe as "brightness" or "contrast"
is the cutoff threshold between black and white of the original image.
A value of 1 will only generate black in the darkest areas of the original image.
A value of 15 will only generate white in the whitest areas of the original image.
That is, 1 will give you a dark image, 15 a light image.
Click to expand...
Click to collapse
Nice find! I didn't know that was a B/W threshold. But I think you meant "1 gives a light image and 15 a dark image".
I've just tried using this in NoRefreshToggle, but the result was not as good as before. The image is much more just solid black and white because you can't see the dither patterns that represent grey (they appear only at very specific white levels, which would be nice to tweak too).
What I actually use for "contrast" adjustment in NoRefreshToggle is a different approach. Using a fixed threshold of 14 (dark image), I've managed to lower the black level (turning it more greyish) to achieve a smaller color range. This way, the dither patterns appear more often. However, my technique to achieve this effect is not so elegant: I overlay the entire screen with a semi-transparent white pane. This has the inconvenient of controlling the pane visibility: whenever A2 mode is turned off (by user or system), I need to hide the pane View.
If I could temporarily avoid the automatic changing of screen modes by the system, this would be much simpler. I've had no success at this issue so far.

marspeople said:
I think you meant "1 gives a light image and 15 a dark image".
Click to expand...
Click to collapse
Yup, good catch. The preceding two sentences were correct. I edited the third.
I have a demo panning grayscales. It's easy to see where the threshold is occurring. Shown below.
Oh! I did see something about the dither modes.
They would certainly be useful for video, less so for text.
I think a system-wide use of A2 would be a bit counterproductive.
The fonts look better with 16 shades.
The best use would be to have browsers and viewers use A2 for panning and zooming.
And another thing:
I don't know how you are getting the dither in there, but since you are doing an overlay anyway,
maybe you should try a halftone screen approach to see how it would work.
The simplest halftone screen would be a checkerboard with two different transparencies.
That wouldn't sacrifice too much resolution.

Renate NST said:
I think a system-wide use of A2 would be a bit counterproductive.
Click to expand...
Click to collapse
i seems to me that n-r mode would be much more usefull if would could regulate when its on a and when off. Its quite pain running the app again and again. it seems to me that quicker reaction is much better than nicer pictures in average use - pdf reading, browsing, video, managing system...

marspeople said:
I've just tried using this in NoRefreshToggle, but the result was not as good as before. The image is much more just solid black and white because you can't see the dither patterns that represent grey (they appear only at very specific white levels, which would be nice to tweak too)
Click to expand...
Click to collapse
I don't think the dithering can be 'tweaked' as such. It's caused by the reduction of 24-bit color images to the 16-bit colorspace of the OS. Dithering is performed by the graphics hardware to prevent obvious colour banding, and there's no OpenGL functions to control dithering parameters.
The A2 mode seems to choose a threshold value for black in the 16-bit colorspace. Values above this are white. In order to obtain black and white dithering we have to pick values in the 24-bit colorspace which all lie in the same 16-bit band.
The easiest way I've found is to keep the R and G values at 255 and vary the B value. I think the default threshold lies at 255,255,198. If you start at that and increase the B value you get 7 dithered grey shades before you reach white.

Guys, as far as i know, eink display is build of tiny capsules, much smaller that one pixel is, and a chip is joining them into pixels. So mayby there is a way to divide single pixel into 2 or even 4? It is much much work, but it would make us easier draw some tones of monochrome? Example: to get dark gray, instead of displaying one of five black pixels white, we can make one's "subpixels" 3/4 black, 1/4 white.
Does it make sense/do you get it?

Renate NST said:
I think a system-wide use of A2 would be a bit counterproductive.
The fonts look better with 16 shades.
The best use would be to have browsers and viewers use A2 for panning and zooming.
Click to expand...
Click to collapse
I agree with you. But having temporary exclusive control of A2 mode would make my application more efficient. I don't intend to use A2 system-wide.
Renate NST said:
And another thing:
I don't know how you are getting the dither in there, but since you are doing an overlay anyway,
maybe you should try a halftone screen approach to see how it would work.
The simplest halftone screen would be a checkerboard with two different transparencies.
That wouldn't sacrifice too much resolution.
Click to expand...
Click to collapse
I just tried this but I've got nothing more than a simply darker and checkered image. I don't understand how it would be better.

marspeople said:
I don't understand how it would be better.
Click to expand...
Click to collapse
Well, halftone screens have been around forever.
Think of it this way, it would give you two different thresholds.
With a bigger pattern you would get more thresholds but a coarser pattern.
That is always the way with dithering or halftone.
Probably a screen would not work well with an underlying dither.

A useful observation from http://forum.xda-developers.com/showthread.php?t=1502723&page=11 is that by listening to the screen you can hear screen activity.
After a quick test I suspect ONESHOT mode allows the screen to enter a power saving mode (in which the screen is completely silent) after a few hundred ms of inactivity, while ACTIVE prevents it. No idea whether there are other issues involved.

The native Reader.apk uses GU, ONESHOT_ALL when turning pages.
Every 6th page it uses GC, ONESHOT_ALL.

In an overnight test with the nook screensaver / lock screen mode inhibited by my application and no screen updates, I obtained power consumption of 0.75% / hour with ONESHOT mode. In a previous test with ACTIVE mode I got ~7% / hour with the same scenario(!)
With fast screen updates of ~ 1Hz ONESHOT does not appear to give any power saving benefit over ACTIVE mode, and a quiet hiss can be heard from the screen at all times in both modes at this refresh rate. I think this indicates the ONESHOT mode allows the screen to enter a power saving mode after a period of inactivity.
Neither of these were scientific tests but I strongly suggest trying ONESHOT mode in favour of ACTIVE whenever using A2 mode.

Well, there must be some benefit sometime to the ACTIVE mode or they wouldn't have it.
It's hard to differentiate the different modes, but it seem that ACTIVE responds quicker with less delay.
I switch to ACTIVE_ALL, A2 for panning and switch back to ONESHOT_ALL, AUTO afterwards.
(I don't use full-time A2).
See my demo of panning: http://forum.xda-developers.com/showthread.php?t=1563645
I'm running about 7%/hour drain. My Nook is not suspending when I do a simple power button click. I don't know why.

A few folks seem to be using EpdController in a useful manner.
Their use of Java reflection is clever, but it's not supposed to be that difficult.
I wrote a Java stub (basically declarations) for EpdController and wrapped it in a jar.
If you just put this jar in your compilation classpath with your normal android.jar
then you will be able to use the EpdController without all the fuss and muss.
For example, in my latest (unreleased) version of UsbMode I want the blinker to go on and off cleanly:
Code:
EpdController.setRegion("UsbMode", EpdController.Region.APP_3, blinker, EpdController.Wave.DU);
That's it, one line, no initialization.
The EpdController class was designed to handle such trivial uses.
Note: This jar itself has no functionality, all the method bodies are {}.
You will have to import android.hardware.EpdController

The 1.2 update uses a different EpdController and has a new EpdRegionParams.
This may or may not break code written for previous versions.
The best way to write code to use EpdController is to have it detect if there is no Epd
(i.e. for other devices), the old version or the new version.
Wrap a try/catch around a Class.forName("android.hardware.EpdController").
Wrap a try/catch around a Class.forName("android.hardware.EpdRegionParams").
The new epd.jar in the signature will allow you to compile without using redirection both the old and the new.
For details on the changes, see: http://forum.xda-developers.com/showpost.php?p=35390192&postcount=8

Bump & additional info.
By experimenting and reading documentation for other eInk controllers I've figured out the following:
Controllers support different algorithms for updating the pixels depending on the precision of the gray scale required and the compensation for previous ghosting.
On the Nook, we have the choice of waveform modes:
GC
GU (gray update)
DU (direct update)
A2
GL16
AUTO (auto selection of algorithm)
The screen can be divided up into regions where different algorithms may be used.
Some controllers support 15 regions, ours supports 8.
4 of these regions are earmarked for system usage, specifically:
Toast (popups)
Keyboard (soft keyboard layout)
Dialog (popups)
Overlay
The remaining 4 regions are left for the user.
Note: "HwRegion" is an enum for the complete 8 regions, "Region" is an enum for the 4 user regions.
An example: In my audio recorder I have two regions set aside for the VU bar graphs.
By setting these two regions to DU I get rid of update clutter and the response is quicker.
Currently, the EpdController in the Nook only operates with portrait coordinates.
If you wish to use this while in landscape mode you will have to rotate the coordinates first yourself.
It's sometimes hard to see exactly what/if some EPD setting is doing.
A good way to check it is to set a region for one half the width of whatever active graphic element you are trying to improve.
The difference can be very clear.

Renate NST said:
There seems to be very little actual documentation on the various eInk update modes.
Most of the information seems to have been extracted from working code.
Some of that code does not seem to be optimal in any case.
I'd like to start this thread on a discussion of the update modes.
You can look at all the code posted, but the bottom line is that eInk mode is configured by passing six discrete pieces of information to the EPD driver.
These six pieces may be wrapped up into a single static entity.
Name of entity requesting change (for logging purposes only)
Region, one of enumRegion[] (Region 4-7)
A rectangle, normally {0, 0, 600, 800}
Wave, one of enumWave[] (GC, GU, DU, A2, GL16, AUTO)
Mode, one of enumMode[] (INACTIVE, ACTIVE, ONESHOT, CLEAR, ACTIVE_ALL, ONESHOT_ALL, CLEAR_ALL)
Threshold, an int 1-15, only applies to A2 mode
A2 is the one bit, fast drawing method. It leaves ghosting behind.
In some applications, you would like to enable faster scrolling in A2 mode and then have it revert to "normal" upon completion.
I have an application with a full screen scroll.
After experimenting with the values, these two configs seem to do the job nicely.
Code:
configA2Enter = makeConfig(rpc, waveEnums[WAVE_A2], regionEnums[REGION_6], modeEnums[MODE_ACTIVE_ALL], THRESHOLD);
configA2Exit = makeConfig(rpc, waveEnums[WAVE_AUTO], regionEnums[REGION_6], modeEnums[MODE_ACTIVE_ALL], 0);
No user intervention is necessary, it scrolls quickly and redraws a clean image when done.
(A view.invalidate() is necessary after you invoke configA2Exit)
Does anybody have any further insight into these values or suggestions for improving them?
Click to expand...
Click to collapse
Excellent work! Do you happen to understand/can write up what the various fast mode/no refresh hacks do/how they use these different modes?
I've had X 'running' on my nook but only by triggering a full refresh every few seconds, and wondered how I could be more selective.
My reading of Norefresh was that it was doing something like parsing android log structures for areas that have changed.
Is there an easy way to trigger a refresh of part of the display from userspace, preferably directly on the driver or fb?
As for where the dithering is done, my guesswork is this is done by a blob running on the DSP module within the OMAP (which is perhaps the only interesting use of it I've seen).
Dave

Just done some playing writing directly to the entires in /sys/class/graphics/fb0 ; so for example:
echo -n 100,100,200,200,0,14 > epd_area
echo 2 > epd_refresh
causes the square 100,100->200,200 to be refreshed
the 14 being REGION(8)+CLEAR(4)+ONESHOT(2)
the 0 is wvfid+threshold*65536 I think.
I've put some code that runs under X to trigger updates; here (actually the comment is wrong, it's currently using oneshot+clear);
I never managed to get active to work.
http://forum.xda-developers.com/showthread.php?p=42393733#post42393733
Dave

[Q] Z1compact: getting minimum brightness LOWER

Hello Everyone,
I have a problem with my amami and I doubt I am the only one but for some reason people do hardly complain: the brightness even at lowest possible setting is still too bright.
I had this back when I had original FW and I am having the same issue with CM11 (latest nightlies). Using manual control or auto-brightness doesn't make much difference, i.e. in a totally dark room the ambient light sensor reports 0Lux and the screen is still too bright.
I found a workaround already (the ScreenFilter app that people recommend all over the internet) but it sucks because it heavily reduces the picture quality, i.e. visibly reduces contrast and especially the gray color resolution. And it also doesn't reduce power consumption like real brightness value change would do.
I looked around for possible solutions and there is a trick with writting a new value of current limit to Linux settings (some mA value between 0 and 20 to some max_current file in procfs). And this really helps but also impacts the maximum brightness, the screen is hardly ready in sun light with reduced current.
Is there a silver bullet? I am thinking about writing an app for that but it would require SU permissions and is kinda dirty to implement. Can anyone recommend a better solution?

have you tried the xposed Modul "minimum brightness" ?

Install Lux Brightness. from play store.
You can overboost it or make the screen so dark that you can't even see it.
Another great screen mod is Twilight which basically dims the screen red based on clock so it helps fall sleep faster when using phone before bed.

New Folder said:
Install Lux Brightness. from play store.
Click to expand...
Click to collapse
Yes, another vote for Lux. It lets you set brightness to negative levels, mine is usually around -50%. https://play.google.com/store/apps/details?id=com.vito.lux&hl=en

Vote for Lux here too.
Nothing comes close

camaro322hp said:
Yes, another vote for Lux. It lets you set brightness to negative levels, mine is usually around -50%. https://play.google.com/store/apps/details?id=com.vito.lux&hl=en
Click to expand...
Click to collapse
Thanks for the hint. I tried the Lite version and AFAICS it simply uses the same trick as ScreenFilter and other "sub-zero" regulators, putting an alpha overlay on top of the image stack.
You can identify this kludge easily by looking at the button areas, they don't get darker anymore. And you can see the black level not getting real black, i.e. the power consumption is not reduced.
However, Lux seems to be one of the better toys because of the plugin interface. Unfortunately there is no HW plugin for Sony devices but judging by the quick look at the Nexus-4 plugin (it's open source!!) it should be possible to adopt this method to Z1 as well. So, maybe when someone could eventually implement that.

xposed Modul "minimum brightness" works, i tested it for you. you can make the screen dim to complete black with your normal display brightness slider without grey or black overlay. it just sets down the minimum brightness level to 1 or 0 (default is 10 or 20), so it should also work with enabled auto brightness

chertVdetali said:
I looked around for possible solutions and there is a trick with writting a new value of current limit to Linux settings (some mA value between 0 and 20 to some max_current file in procfs). And this really helps but also impacts the maximum brightness, the screen is hardly ready in sun light with reduced current.
Click to expand...
Click to collapse
As far as i remember, /proc is only used to call upon information, not to set specific values. What you are looking for is placed within /sys.
To be precise in /sys/devices/leds-qpnp-ee125e00/leds/wled:backlight/. There you will find a file called max_current with which you can easily control the brightness and set it to a very low level. Note that this actually dims the screen and not just applies a filter like most apps do...
One drawback is that the value will change again after you restarted the device. I set up a little flow with Automate β that takes care of this for me. I find this solution a lot better than all the screen filter apps.
This is true for CyanogenMod 11 and GreatDevs Kernel. It might be different on Stock. I know that the path for my Nexus 7 is sys/class/leds/lcd-backlight.
I hope this helps you a little bit.

rob rich said:
xposed Modul "minimum brightness" works, i tested it for you. you can make the screen dim to complete black with your normal display brightness slider without grey or black overlay. it just sets down the minimum brightness level to 1 or 0 (default is 10 or 20), so it should also work with enabled auto brightness
Click to expand...
Click to collapse
I am wondering how you can claim that the result is complete black. Calling this black is like saying "TN monitors have good black values" (I know such people, they change their mind quickly when they see my Eizo with a VA panel at night).
No, seriously, the default was already 10 (see config.xml in cm11 repo) and the difference between 1 and 10 is hardly visible. It's still way too bright for work without eye strain in the darkness.
@Wooaarr: thanks, this is apparently the way to go, I just need to find time to configure it. And yes, of course, the file is in sysfs and not procfs (automated typing, when I grew up with Linux there was no sysfs out there ).

chertVdetali said:
I am wondering how you can claim that the result is complete black. Calling this black is like saying "TN monitors have good black values" (I know such people, they change their mind quickly when they see my Eizo with a VA panel at night).
No, seriously, the default was already 10 (see config.xml in cm11 repo) and the difference between 1 and 10 is hardly visible. It's still way too bright for work without eye strain in the darkness.
@Wooaarr: thanks, this is apparently the way to go, I just need to find time to configure it. And yes, of course, the file is in sysfs and not procfs (automated typing, when I grew up with Linux there was no sysfs out there ).
Click to expand...
Click to collapse
when i disable autobrightness and push the slider to the left my screen goes completely off, so you wanna say that screen off isnt black? funny

chertVdetali said:
Thanks for the hint. I tried the Lite version and AFAICS it simply uses the same trick as ScreenFilter and other "sub-zero" regulators, putting an alpha overlay on top of the image stack.
You can identify this kludge easily by looking at the button areas, they don't get darker anymore. And you can see the black level not getting real black, i.e. the power consumption is not reduced.
However, Lux seems to be one of the better toys because of the plugin interface. Unfortunately there is no HW plugin for Sony devices but judging by the quick look at the Nexus-4 plugin (it's open source!!) it should be possible to adopt this method to Z1 as well. So, maybe when someone could eventually implement that.
Click to expand...
Click to collapse
Interesting information, I did not know that. You are correct, the navigation buttons are brighter than the rest of the screen at negative values. I had noticed that before but didn't know why. Works well enough for me though.

rob rich said:
when i disable autobrightness and push the slider to the left my screen goes completely off, so you wanna say that screen off isnt black? funny
Click to expand...
Click to collapse
Well, you claim that it works for me because you tested it on your device. So... yeah, why not, I could say what you mentioned above just following the same logics. :silly:

android P

I followed a guide to use vpn to get android p update, after update I wonder where is android p features?!
No round corners
Brightness issues
No digital dashboard
And I wonder if this is the last release or just beta although in the update page didn't say beta!!

Medo22 said:
I followed a guide to use vpn to get android p update, after update I wonder where is android p features?!
No round corners
Brightness issues
No digital dashboard
And I wonder if this is the last release or just beta although in the update page didn't say beta!!
Click to expand...
Click to collapse
Final release with bugs

theforbidden said:
Final release with bugs
Click to expand...
Click to collapse
Yes, as same as releasing android o with no charge sound and warm display color temperature
Google sucks!!

i can't confirm this.
i got alot Pie features like:
- new look and feel
- navigation gestures
- snappier and more fluid system
- YT fullscreen
- AI Battery
- digital wellbeing
and much more i guess.

Medo22 said:
I followed a guide to use vpn to get android p update, after update I wonder where is android p features?!
No round corners
Brightness issues
No digital dashboard
And I wonder if this is the last release or just beta although in the update page didn't say beta!!
Click to expand...
Click to collapse
No round corners - what round corners you are referring to ?
Brightness issues - the brightness issues such? for me I notice that the brightness is significantly reduce when u reduce the brightness to the lowest
No digital dashboard - if you are referring to digital wellbeing , you need to download it from playstore first after update to PIE.

mytowyn said:
No round corners - what round corners you are referring to ?
Brightness issues - the brightness issues such? for me I notice that the brightness is significantly reduce when u reduce the brightness to the lowest
No digital dashboard - if you are referring to digital wellbeing , you need to download it from playstore first after update to PIE.
Click to expand...
Click to collapse
This corners not rounded as in pixel phones and also why the color isn't just blue like pixel istead of this strange color!!

No text copying from recent apps screen like pixel

For brightness I have to slide it for about 45% to get the same brightness as 20% in oreo and for sure it's more battery consuming!

The rounded corners thing is true, notification shade and quick actions are not as rounded as Pixel and you can't select text from an Overview/recent apps. But you can always flash custom ROM if you're not satisfied. I personally like it and, performance-wise, it works great. Once they polish these bugs, it will be even better experience.

The corners are rounded because the phone's screen has rounded edges..Unless you mean about another thing... What do you mean with digital dashboard? If you mean Digital WellBeing you might need to join their beta. I had no problems with the brightness.. the only problems I had is with the camera and I had one time when the recent screen was stuck for 4 seconds

Medo22 said:
For brightness I have to slide it for about 45% to get the same brightness as 20% in oreo
Click to expand...
Click to collapse
Me too !

Another bug in landscape you can't go to settings!!

Medo22 said:
Another bug in landscape you can't go to settings!!
Click to expand...
Click to collapse
If you tap the bottom edge, it does open on my phone.

After upgrade i have problems with the wifi. I m not able to Connect

mircescu11 said:
After upgrade i have problems with the wifi. I m not able to Connect
Click to expand...
Click to collapse
Forget saved networks and sign back in

Reset data/wiffi.

anyone having problems with stock camera? after a few hours stopped to work, it shows me error

Brugos27 said:
anyone having problems with stock camera? after a few hours stopped to work, it shows me error
Click to expand...
Click to collapse
Clear cache and data of the camera app, it'll work again.

godoy.rafa said:
Clear cache and data of the camera app, it'll work again.
Click to expand...
Click to collapse
even cleaning cache and forced ... after opening again the cam will show the same message. Dont know if its fault of last update to PIE.
But only stock camera, with any other camera app from playstore, will work ok... just the stock wont work.

Brugos27 said:
anyone having problems with stock camera? after a few hours stopped to work, it shows me error
Click to expand...
Click to collapse
Disable do not disturb mode

[NEW] aodNotify - Notification Light / LED for OnePlus Nord + No fingerprint visible!

This app was initially developed for Samsung Galaxy devices with Always on Display. As OnePlus devices will also get an Always on Display soon i decided to create a version specially for OnePlus devices. For now the app runs in a compatibility mode as the Always on Display has not been released yet. App is in beta stage currently.
You need a notification light / LED for your OnePlus Nord?
With aodNotify you can easily add a notification light / LED to your OnePlus Nord!
You can select different notification light styles and show the notification light around the camera cutout, screen edges or even simulate an notification LED dot in the statusbar of your OnePlus Nord or OnePlus 8!
This app hides the fingerprint icon, so the icon can not burn in your screen! Enjoy your notification light!
MAIN FEATURES
• Notification light / LED for OnePlus Nord or OnePlus 8!
• Double tap to wake when notification arrives!
• Charging / Low battery light / LED
MORE FEATURES
• Notification light styles (around camera, screen, LED dot)
• Custom app / contact colors
• ECO animations to save battery
• Interval mode (on/off) to save battery
• Night times to save battery
BATTERY USAGE PER HOUR ~:
• LED - 7.5%
• LED & INTERVAL - 5.5%
• LED & ECO ANIMATION - 3.5%
• LED & ECO ANIMATION & INTERVAL - 2.5%
Without notification light the app consumes almost 0% battery!
DOWNLOAD:
DEVICES
• OnePlus 8
• OnePlus Nord
• OnePlus 7 (untested)??
• OnePlus 6 (untested)??
NOTES
• The app is still in beta stage, errors may occur!!
• OnePlus may block this app with future updates!
• Please check if the app is compatible before updating phone software!
• Altough we never experienced any screen burn in issues on our test devices, we recommend to not keep the notification light / LED active for a long time! Use at you own responsibility!
"OnePlus" is a protected trademark of "One Plus Technology Co., Ltd"

Reserved

Latest public beta (join directly from PlayStore) has experimental OnePlus Nord support.
Please reply if the camera cutout is working. You can do some fine adjustment in dimension settings. Will update the position if needed.
Thanks for testing!

How can I move it over the front camera? Can't move it more tothe left...

wonsky21 said:
How can I move it over the front camera? Can't move it more tothe left...
Click to expand...
Click to collapse
seems completely offset. Which resolution do you use on the phone?

Jawomo said:
seems completely offset. Which resolution do you use on the phone?
Click to expand...
Click to collapse
I realized I didn't update to the latest beta. Now it is ok

wonsky21 said:
I realized I didn't update to the latest beta. Now it is ok
Click to expand...
Click to collapse
Does the position need any correction? Or is it perfectly aligned?
I will adjust the presets then.

It was too low and too far to the left. Shape was bad too. These are my settings, it fits perfectly now.

wonsky21 said:
It was too low and too far to the left. Shape was bad too. These are my settings, it fits perfectly now.
Click to expand...
Click to collapse
Could you please set "Resize" to 0% and then check if any "fine tuning" is needed. Or if we can leave "fine tuning" values on 0.
Thanks for testing!

It is HUGE with resize set to 0...

wonsky21 said:
It is HUGE with resize set to 0...
Click to expand...
Click to collapse
You also need to set all values to 0 in fine tuning

When fine tuning settings are set to 0 the app restarts itself

wonsky21 said:
When fine tuning settings are set to 0 the app restarts itself
Click to expand...
Click to collapse
Did you sent the crash report? or isnt there any?

I cleared app data and cache, and set everything again. Now these are my tuned settings

errr .... I'm using this phone with the front camera outside of the screen, no hole in the actual screen, this oval **** drove me crazy.
when tried to set the ofsets to be around the cameras, the phone simply won't use the portion of the screen where the cameras are.
is there anything that can be done with that?

1immortal said:
errr .... I'm using this phone with the front camera outside of the screen, no hole in the actual screen, this oval **** drove me crazy.
when tried to set the ofsets to be around the cameras, the phone simply won't use the portion of the screen where the cameras are.
is there anything that can be done with that?
Click to expand...
Click to collapse
Did you join the beta program from Playstore, and updated to the latest beta? If so, clear app data and cache, and set values from my post, and you'l be fine.

I did, still can't move the ring outside of the screen.

Works like charm.. I just faced a small issue when in lockscreen.
It messes up the tap the screen to show feature in the ambient display. Only double tap works properly, single tap doesn't . Hope this gets fixed in the future updates.
Thanks for the efforts^_^!

Srijith Bharadwaj said:
Works like charm.. I just faced a small issue when in lockscreen.
It messes up the tap the screen to show feature in the ambient display. Only double tap works properly, single tap doesn't . Hope this gets fixed in the future updates.
Thanks for the efforts^_^!
Click to expand...
Click to collapse
Did you need some position fine tuning? or does the camera cutout fit for you?
Yes, ambient display is not supported yet.

Jawomo said:
Did you need some position fine tuning? or does the camera cutout fit for you?
Yes, ambient display is not supported yet.
Click to expand...
Click to collapse
Needed to tune the cutout as it doesn't actually fit perfectly by default.

Question 12 "Stable" Issues Thread

Besides the general low quality of this piece of software, here are some specific pains:
1. SafetyNet test fails (no root) - WTF? Can't use any of my work applications because of that.
2. Status bar notification icons don't appear (except for Gmail, for some reason)
3. About device shows there's an update available but I can't update because I'm not the "owner" of the device (there is only 1 user configured, no multiple users) - screenshot attached.
Please share your experience and whether or not you're seeing the same issues (or more).
Thanks!

Another botched update from oneplus scams

Well, it's a good thing I decided that the OP9P would be my last OP smartphone. I'm gona stick with Pixel phone from now on. Finally release A12 and no phone or data works. Really OP???

- Phone stuck in 60hz like 99% of the time.
- Keyboard doesn't have this convenient padding anymore. (On botttom to make typing easier.)
- [Launcher] Can't search apps with a single up swipe anymore, will have to find some hacky solution again. Usually I put a KISS launcher shortcut on other phones. But why ruin it when they had it ....
- [Launcher] Folders open on the middle of screen. Makes no sensse.
- [Launcher] The whole launcher experience is just way worse.
- Battery Management is a mess, now there are other options per app. The previous settings were reset.
- Rooting with Canary Magsik can soft brick. Managed to fix it but it took me a while and I consider myself a veteran.
Honestly, tons of great features are missing. I wish they would just give us a lean AOSP instead like the ASUS Android and call it a day. This feels like a botched, budget Android on a cheap Chinese phone.

App drawers can only display 4 icons per row. Anyone knows how to change it to 5 per row or more?

it is no longer possible to film and in 21:9... or I am blind.
Like a say h8Aramex Phone stuck in 60hz like 99% of the time.
anhtin said:
App drawers can only display 4 icons per row. Anyone knows how to change it to 5 per row or more?
Click to expand...
Click to collapse
it's possible. settings --> home screen and lock screen

purpleman2k said:
Status bar notification icons don't appear (except for Gmail, for some reason)
Click to expand...
Click to collapse
That's not actually a bug, that's feature. Go to notification settings for particular app and you can set to show notification icon on status bar. Disabled by default for all apss (I think it should be enabled by default), except Gmail, Dialer and a few others.
Bug I found:
- font size issues. I want to set small fonts and dpi. But some apps, like default camera app, power menu, google feeds when swipe etc has still default large font, experience is terrible
- custom dpi set in developer settings will be reverted after reboot. If you set smaller dpi in phone settings, it will be applied a few seconds after boot, phone starts with default dpi
- AOD does not work, even if enabled, screen will turn off when inactive
I installed via built in ota from Oxygen 11 Global, I got update to ColorOS 12

Just got my first 1+ yesterday and was really impressed with the OOS 11 experience.
All day long. All the magic has gone after the update.
In addition to what was already said, the AOD is flickering terribly.
Perhaps it is caused by the pwm of low frequency.

Lol, I paid 1000 euros for this phone because the software was supposed to be good...

Oh yeah, the CLOCK. What is WRONG with that CLOCK!? LMAO.
I mean look at this ABOMINATION.
WHO DRAWS A CLOCK LIKE THAT? SATAN?!?!??!
Like wtf lol.

I have a new problem. I listen to music while walking with my wireless headphones. The phone is in my pocket. Unknown reason causes the phone to crash.
I feel it's going to be complicated.... At least I have 5G working.

Why would they remove the seconds on the clock feature. This update is horrible all around

anhtin said:
App drawers can only display 4 icons per row. Anyone knows how to change it to 5 per row or more?
Click to expand...
Click to collapse
Get Nova launcher and don't look back?

I'm not even going to upgrade A12, I deleted the 4gig update I got from Oxygen Updater. Oneplus just shoot them self in the foot and will not recover from this. I'll be suprise if they sell 1k Oneplus 10 phone next month.

h8Aramex said:
Oh yeah, the CLOCK. What is WRONG with that CLOCK!? LMAO.
I mean look at this ABOMINATION.
WHO DRAWS A CLOCK LIKE THAT? SATAN?!?!??!
Like wtf lol.
View attachment 5476711
Click to expand...
Click to collapse
Is your phone in 24-hour format? Mine looks normal in 12-hour format but like yours in 24-hour format. I don't use the stock clock app so I hadn't noticed.
ddizzy81 said:
Why would they remove the seconds on the clock feature. This update is horrible all around
Click to expand...
Click to collapse
They didn't. This is only when setting an alarm in the clock app.

Camera goes bananas when zoomed beyond 10x.. See attached

Any custom DPI set in developer options is completely lost after reboot.
Reported by me multiple times and was also seen in previous phones/Android versions.

Hi all, i can't open the icon option in the Launcher and and in the settings too it simply crash and nothing. Anyone as an idea? I just wipe launcher data but nothing.

h8Aramex said:
- Phone stuck in 60hz like 99% of the time.
Click to expand...
Click to collapse
Did you select "High" refresh rate in settings? Mine is at 120hz the vast majority of the time.

I have issues with screen brightness not adjusting to low-light conditions. When setting my phone on my dash mount I have to manually adjust the screen brightness down or go blind, even in dark mode. Worked fine with Oxygen OS 11. Fairly disappointed with the overall quality of this update, and I usually love getting the shiny new OS version update.