Related
--update4 feb 18 below: camera patch + WIFI dropped connection
Hi,
Sorry to post here, as new user I don't have access to the Android development board.
I have altered [ACL]'s latest kernel (2.6.27-46 git g6a073c7 from 2 feb) to support the Rhodium 100 camera. The update package and the diff are attached.
The change does essentially the same as an earlier change to Andoid SD posted by brinka123, but is implemented differently to prevent upstream rejection as happened to the patch by brinka123. The update package is the 2 feb update that [ACL] posted with the kernel replaced. Can someone can post this to the devel board? I'm looking for testers...
Thanks,
Eric.
--update1 (new user = no new post to devel board):
Thanks arrrghhh for moving my post here. Yes, the zip can be flashed from SD card from the boot menu.
[ACL], the changes apply to all MACH_TYPE_HTCRHODIUM machines (from mach-types.h), that includes all GSM Rhodium devices I believe. I don't know how to narrow that down to the 100 alone, aside from using a kernel boot parameter.
As for the intended scope for this change: most people reporting camera issues are rhod100 users, but I've seen posts from non-rhod100 users having occasional camera crashes. Because the patch targets the used frame rate it is likely that the camera hardware in most rhod100s - and some non-100's? - just can't handle the original framerate. So if there are non-rhod100 users having occasional camera crashes...
--update2
Changed patch to make it rhod100 specific using machine_variant_type. Thanks muziling. See attached zip and diff (postfixed _1). Non-rhod100 users with crashing camera's -if any- should use the original zip to test.
Please note that this patch does not include brinka123's change for low-light conditions. Didn't that one cause problems when zooming in? I can look into that change, but would like to separate it from this patch.
Next thing I want to do is look into the audio issue when using the cam - audio runs for 1 sec, then drops. I need to go into Android code for that*
I've worked hard this evening to compile OMGB with [ACL]'s device specific files (both github), but failed miserably. Looks like I'm missing the rhodium makefiles, any pointers?
I did manage to get 7.5 GB of sources on my PC, so I guess I'm at least halfway
*: while recording video logcat shows a happily recording cam and then suddenly:
V/Libacoustic-wince( 85): msm72xx_start_acoustic_setting
I/AudioHardwareMSM72XX_wince( 85): disabling volume method=AUDIO
V/Libacoustic-wince( 85): msm72xx_set_acoustic_table 256 0
V/Libacoustic-wince( 85): Use current device 13
-- update3
The attachment OMGB_2.6.27.46-01399-g6a073c7-rhod100camera_1.zip lacked matching kernel modules (no wifi, ...).
Corrected that by uploading attachment OMGB_2.6.27.46-01399-g6a073c7-rhod100camera_1a.zip
Note that this second update does nothing for rhod 2xx,3xx devices.
--update4
Camera:
Some people reported improved all-rhodium camera quality under low-light conditions using brinka123's changes. The change that is present in the attached patch does improve low-light image quality somewhat as it lowers the framerate, increasing the ccd integration time (1 frame + blanking). The remaining changes from brinka123 not included in the patch do not improve low-light image quality. These changes just limit the CCD integration time to one frame incl blanking, preventing hardware enforced framerate drop but delivering a darker picture with more noise. So I think the patch as-is is fine.
Wifi:
To properly debug camera audio issues I wanted a build environment using OMGB git + [ACL]'s device_htc_rhodium git. After a week of total war between me and the Android build system I have a working environment that results in a working phone. Had to create lots of Android makefiles from scratch to do that, and by accident it resulted in a phone that doesn't drop it's WIFI connection every now and then (Wifi icon turned gray 1-2 times a day, toggling wifi off/on reconnects). The difference with [ACL]'s build is not in the code, but somewhere in the makefiles + properties + different firmware files and is difficult to narrow down. If the WiFi issue I had is real and not something limited to my phone/access points I can look into this. Anyone with this problem?
Thanks mate, moved your thread to development.
Interested to hear how this pans out. I'm assuming RHOD100 users on OMGB can just flash that .zip via recovery?
ImTuxy said:
Hi,
Sorry to post here, as new user I don't have access to the Android development board.
I have altered [ACL]'s latest kernel (2.6.27-46 git g6a073c7 from 2 feb) to support the Rhodium 100 camera. The update package and the diff are attached.
The change does essentially the same as an earlier change to Andoid SD posted by brinka123, but is implemented differently to prevent upstream rejection as happened to the patch by brinka123. The update package is the 2 feb update that [ACL] posted with the kernel replaced. Can someone can post this to the devel board? I'm looking for testers...
Thanks,
Eric.
Click to expand...
Click to collapse
Hey dood. Lets get some rhod 100 folk to test this bad boy. We also need to make sure it doesnt break the other variants. I'm also going to send this to the kernel team so it can be analyzed for xdandroid as well. If this change is Rhod100 specific, then we need to change it so only rhod100 loads it.
ImTuxy said:
Hi,
Sorry to post here, as new user I don't have access to the Android development board.
I have altered [ACL]'s latest kernel (2.6.27-46 git g6a073c7 from 2 feb) to support the Rhodium 100 camera. The update package and the diff are attached.
The change does essentially the same as an earlier change to Andoid SD posted by brinka123, but is implemented differently to prevent upstream rejection as happened to the patch by brinka123. The update package is the 2 feb update that [ACL] posted with the kernel replaced. Can someone can post this to the devel board? I'm looking for testers...
Thanks,
Eric.
Click to expand...
Click to collapse
Great work, Eric. I have tested now cursorily and first observations are:
1. Camera works great including autofocus
2. Camcorder - videorecording works, but there is problem with recording audio. Recording approximately first 1 second and then silence.
I made 4 photos and 2 videos (30 second and 5 second) and this consumed 49% of my battery.
May I send you any logs or another help with testing?
Anyway many, many thanks to you!
Edit: After recording this kernel is sometimes spontaneously turns on the display including four buttons at bottom, in that moment the LED lights up in orange (wake) and immediately off again and the LED turns green (sleep). Display lights approx. 1 second.
[ACL] said:
Hey dood. Lets get some rhod 100 folk to test this bad boy. We also need to make sure it doesnt break the other variants. I'm also going to send this to the kernel team so it can be analyzed for xdandroid as well. If this change is Rhod100 specific, then we need to change it so only rhod100 loads it.
Click to expand...
Click to collapse
I was under the impression that the 'improvements' would actually help all RHOD's. I know when I ran brinka's kernel for testing, the low-light performance did seem better.
So unless it outright breaks all other RHOD's, I'd say it should be applied to all RHOD's.
milda25 said:
Great work, Eric. I have tested now cursorily and first observations are:
1. Camera works great including autofocus
2. Camcorder - videorecording works, but there is problem with recording audio. Recording approximately first 1 second and then silence.
I made 4 photos and 2 videos (30 second and 5 second) and this consumed 49% of my battery.
May I send you any logs or another help with testing?
Anyway many, many thanks to you!
Edit: After recording this kernel is sometimes spontaneously turns on the display including four buttons at bottom, in that moment the LED lights up in orange (wake) and immediately off again and the LED turns green (sleep). Display lights approx. 1 second.
Click to expand...
Click to collapse
This patch does absolutely nothing for recording audio. I would ask how it worked before, but you've probably never been able to test it.
So long as it fixes the cam, we're good. Recording/audio is completely separate from this patch.
arrrghhh said:
I was under the impression that the 'improvements' would actually help all RHOD's. I know when I ran brinka's kernel for testing, the low-light performance did seem better.
So unless it outright breaks all other RHOD's, I'd say it should be applied to all RHOD's.
This patch does absolutely nothing for recording audio. I would ask how it worked before, but you've probably never been able to test it.
Click to expand...
Click to collapse
Sorry, I did not know this. Before the camera really did not work at all. There is tremendous progress. Thanks.
Tested on Rhod100.
milda25 said:
Sorry, I did not know this. Before the camera really did not work at all. There is tremendous progress. Thanks.
Tested on Rhod100.
Click to expand...
Click to collapse
Yes, it is nice to have the cam working at all, and I realize you couldn't test this before.
I just wanted to make that clear, this will only fix the broken cam. Nothing else...
Both RHOD100,210,300 user had crash
Use function get_machine_variant_type to get rhod type, it will return
MACHINE_VARIANT_RHOD_1XX or MACHINE_VARIANT_RHOD_2XX, MACHINE_VARIANT_RHOD_3XX,MACHINE_VARIANT_RHOD_4XX,MACHINE_VARIANT_RHOD_5XX
muziling said:
Both RHOD100,210,300 user had crash
Use function get_machine_variant_type to get rhod type, it will return
MACHINE_VARIANT_RHOD_1XX or MACHINE_VARIANT_RHOD_2XX, MACHINE_VARIANT_RHOD_3XX,MACHINE_VARIANT_RHOD_4XX,MACHINE_VARIANT_RHOD_5XX
Click to expand...
Click to collapse
Exactly !!!
here is some pseudo to brighten everyones day
Code:
current_variant = get_machine_variant_type();
if ((current_variant == MACHINE_VARIANT_RHOD_1XX)) {
do_rhod100_poop();
}
ImTuxy said:
--update2 feb 08 below
Hi,
Sorry to post here, as new user I don't have access to the Android development board.
I have altered [ACL]'s latest kernel (2.6.27-46 git g6a073c7 from 2 feb) to support the Rhodium 100 camera. The update package and the diff are attached.
The change does essentially the same as an earlier change to Andoid SD posted by brinka123, but is implemented differently to prevent upstream rejection as happened to the patch by brinka123. The update package is the 2 feb update that [ACL] posted with the kernel replaced. Can someone can post this to the devel board? I'm looking for testers...
Thanks,
Eric.
--update1 (new user = no new post to devel board):
Thanks arrrghhh for moving my post here. Yes, the zip can be flashed from SD card from the boot menu.
[ACL], the changes apply to all MACH_TYPE_HTCRHODIUM machines (from mach-types.h), that includes all GSM Rhodium devices I believe. I don't know how to narrow that down to the 100 alone, aside from using a kernel boot parameter.
As for the intended scope for this change: most people reporting camera issues are rhod100 users, but I've seen posts from non-rhod100 users having occasional camera crashes. Because the patch targets the used frame rate it is likely that the camera hardware in most rhod100s - and some non-100's? - just can't handle the original framerate. So if there are non-rhod100 users having occasional camera crashes...
--update2
Changed patch to make it rhod100 specific using machine_variant_type. Thanks muziling. See attached zip and diff (postfixed _1). Non-rhod100 users with crashing camera's -if any- should use the original zip to test.
Please note that this patch does not include brinka123's change for low-light conditions. Didn't that one cause problems when zooming in? I can look into that change, but would like to separate it from this patch.
Next thing I want to do is look into the audio issue when using the cam - audio runs for 1 sec, then drops. I need to go into Android code for that*
I've worked hard this evening to compile OMGB with [ACL]'s device specific files (both github), but failed miserably. Looks like I'm missing the rhodium makefiles, any pointers?
I did manage to get 7.5 GB of sources on my PC, so I guess I'm at least halfway
*: while recording video logcat shows a happily recording cam and then suddenly:
V/Libacoustic-wince( 85): msm72xx_start_acoustic_setting
I/AudioHardwareMSM72XX_wince( 85): disabling volume method=AUDIO
V/Libacoustic-wince( 85): msm72xx_set_acoustic_table 256 0
V/Libacoustic-wince( 85): Use current device 13
Click to expand...
Click to collapse
we share acoustic and libaudio with xdandroid. Just compile it there and move the binaries over. Detule is the master of these for now and he has been killing bugs left and right.
Also your second patch looks worthy. So next round of updates i'm going to include it.
We are tracking this issue on the issues list.
http://code.google.com/p/rhodium-nand/issues/detail?id=15
You can update the request if you have more info.
Info:
Target Device: SM-T560NU only (gtelwifiue)
OS: Android 6.0.1 Marshmallow
Variant: LineageOS 13.0
Status: Usable as daily driver, but still to be considered experimental
This project is a side project of mine to bring Lineage 13.0 back to the SM-T560NU.
I recently purchased one of these, and use a few apps that have not been updated in years. These apps do not work on Nougat, therefore I needed Marshmallow.
vince2678 had a great Lineage 13.0 build, but had started to shift his efforts towards the more popular and updated Android Nougat by the time that I got this tablet. vince had started to warn that he was going to be dropping Marshmallow to focus on Nougat.
Therefore, using his code base, and attempting to apply some more modern patches to keep Lineage 13.0 up to date, I started creating my own builds in private. There was one single, obsecure link to it, on my website, and it was discovered. Since the community has shown interest in this project, and vince has now officially dropped support for 13.0, I am willing to release my private builds.
Please keep in mind that while vince's builds were designed to be as stock as possible, my builds are tailored towards my needs.
They are not perfect, but they work for me. There are still some issues to be ironed out, and sometimes new issues sneak in when you think you are just building a security update
But, since you wanted them, here they are. At the time of this post there is only one, but this will grow over time, when I have spare time to try to fix any issues and apply security updates.
All builds use my optimized kernel.
Releases and known issues:
You can find my builds over at:
https://losupd.zefie.net/builds/full/?C=M;O=D
lineage-13.0_j199_20170720
Android Security Patch Level: July 1, 2017
USB MIDI Support (example video of controlling Logic Pro X with the SM-T560NU)
No changes to previous issues in this build (same issues apply)
lineage-13.0_j196_20170617
Android Security Patch Level: June 1, 2017
AudioFX is missing (disabled in build due to unsolved issue in ROM causing crashes)
Updater is untested. You may or may not get a notification when a new build is available.
Flashing the recovery that comes with these builds is advised against. It may work but is untested. Use my TWRP Build.
Device encryption does not yet work
There is a strange issue that prevents you from taking still images using the built-in camera app. Preview and video works. As a workaround, use any third party camera app. I suggest Open Camera.
Just flashed it, everything works great so far.
Ive tried and liked very much
Smooth and lightweight
So far for me the camera dont work but i can record video
Also the encrypt tablet option does not seem to work (I select the option in the security part of the settings screen, it restarts tablet and thats it)
Other than that it seems to be perfect
Thanks for all the hard work
Solidium said:
Ive tried and liked very much
Smooth and lightweight
So far for me the camera dont work but i can record video
Also the encrypt tablet option does not seem to work (I select the option in the security part of the settings screen, it restarts tablet and thats it)
Other than that it seems to be perfect
Thanks for all the hard work
Click to expand...
Click to collapse
I knew about the encryption but the camera issue is interesting and strange. I just tried it and see what you mean.
I will see what I can do about these issues in the next update, which will probably be mid-august.
Thanks for the report.
The issue seems to be with the Camera app itself, and not any issues with communicating with the hardware (despite the error message), since other camera apps appear to work fine.
In the mean time, if you would like to take still images with this build, I would suggest this great and free (ad free as well) camera app from the play store:
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
I have just tested it (with both rear and front cameras) and it can take still images.
560?
Is it compatible with T560 only ? Whats the difference between T560 and T560NU maybe US Market? or what the difference and where i can get a custom Recovery for the Tab?
bluedesire said:
Is it compatible with T560 only ? Whats the difference between T560 and T560NU maybe US Market? or what the difference and where i can get a custom Recovery for the Tab?
Click to expand...
Click to collapse
This is for the T560NU only, not T560. From what I know they have entirely different processors so there is no way for a universal ROM.
Thanks for this amazing rom. I noticed following: can't change the size of analog clock and sound on the speaker is not very strong.
jon355 said:
Thanks for this amazing rom. I noticed following: can't change the size of analog clock and sound on the speaker is not very strong.
Click to expand...
Click to collapse
The clock issue is likely upstream, since I can't think of anything I did that would prevent resizing of widgets, and other widgets appear to be resizable.
But I will look into it.
Speaker issue noted, there was some issue with the internal mic being too low that I tweaked, I may have to check the values for the speaker.
Edit: personal tests show speaker volume is fine. any louder could damage the speaker. if the volume is low, check that the tablet is not laying on a soft surface or something that would otherwise muffle the speaker in the back. When not obstructed, the speaker volume seems fine to me.
Any progress on Audio FX and Camera issues?
Jacsd said:
Any progress on Audio FX and Camera issues?
Click to expand...
Click to collapse
Unfortunately I have not had the time to work on this in a while. When I don't have time I just update the source and build (and hope it works) for the security updates. This only takes a couple of minutes as the build process does all the work. One should be coming in the next few weeks. Once the automated build finishes, I test it locally for about an hour and if its good, I release it.
I am not sure when I will have time to actually sit and go through the code to try to debug it to fix the outstanding issues. This can take hours or even days of dedicated time which I just don't have at the moment due to trying to keep my bills paid.
Stay tuned to this thread for updates though, and I apologize for the delay.
zefie said:
The clock issue is likely upstream, since I can't think of anything I did that would prevent resizing of widgets, and other widgets appear to be resizable.
But I will look into it.
Speaker issue noted, there was some issue with the internal mic being too low that I tweaked, I may have to check the values for the speaker.
Edit: personal tests show speaker volume is fine. any louder could damage the speaker. if the volume is low, check that the tablet is not laying on a soft surface or something that would otherwise muffle the speaker in the back. When not obstructed, the speaker volume seems fine to me.
Click to expand...
Click to collapse
After uninstalling 3rd party music app, volume is good again.
EDIT:
Unfortunately I am discontinuing this ROM. I made this ROM for my personal use, and it is no longer useful to me, and I do not have the time to debug it. Therefore, I am discontinuing it. The current builds and source will remain up, and if you guys are not having the issues I am having, and would like me to continue doing security updates, I will, so long as it still compiles without much work on my part.
There will be no updates to the existing issues though.
Despite my previous aversion to Android N, I would highly suggest vince's Lineage OS 14.1 builds. They have come a long way since I last tried them, and Android N isn't so bad after all
I haven't gotten a chance to do a logcat or anything, but I'm getting an instant bootloop after installing Nova Launcher.
It wasn't an issue until Nova updated a few weeks ago, and it affects both your builds. That's my favorite launcher, but I guess I can live without it
EDIT: I see that you're discontinuing this, so I guess this post is more of an FYI to other users.
This is not the normal 'lag' but a wierd frame drop issue when scrolling in an otherwise smooth experience.
This doesn't seem to be app specific or kernel specific either. It happens in even the settings app and I've tried pretty much all kernels and different settings but this issue seems to persist. This does not happen in Custom Roms, I tried really hard to replicate it.
I've reported it to Oneplus via the feedback app with logs, but have little hope for a reply from them. I'm just taking a shot at here if anyone else noticed this or maybe even found the reason for it. I checked logs but couldn't find anything specific.
Screenshots attached with 'Profile GPU Rendering' On when the stutter happens.
(Issue since 4.7.6 to now OB4)
Logs of when the stutter happens attached.
Yes am also facing the same.
venky716 said:
This is not the normal 'lag' but a wierd frame drop issue when scrolling in an otherwise smooth experience.
This doesn't seem to be app specific or kernel specific either. It happens in even the settings app and I've tried pretty much all kernels and different settings but this issue seems to persist. This does not happen in Custom Roms, I tried really hard to replicate it.
I've reported it to Oneplus via the feedback app with logs, but have little hope for a reply from them. I'm just taking a shot at here if anyone else noticed this or maybe even found the reason for it. I checked logs but couldn't find anything specific.
Screenshots attached with 'Profile GPU Rendering' On when the stutter happens.
(Issue since 4.7.6 to now OB4)
Click to expand...
Click to collapse
adi105 said:
Click to expand...
Click to collapse
Amazing contribution.
Same issue on OB4. Seems to happen after 3-4 after a reboot
Same things, on custom rom though..
MarcoReckless said:
Same things, on custom rom though..
Click to expand...
Click to collapse
Extensively used CNP and Omni, even intentionally tried to replicate this but couldn't. Seems it's restricted to just OxygenOS.
When Ivrun stock oos, I always use renderkernel. It is the smoothest I've ever seen on this phone. Not sure how to read the GPU bars but it never exceeds above the navbar area. It usually stays right in the bottom half of the navbar.
Give render kernel a try and you really wont be disappointed.
swapavi said:
When Ivrun stock oos, I always use renderkernel. It is the smoothest I've ever seen on this phone. Not sure how to read the GPU bars but it never exceeds above the navbar area. It usually stays right in the bottom half of the navbar.
Give render kernel a try and you really wont be disappointed.
Click to expand...
Click to collapse
Using render right now and yes it is by far the smoothest kernel. But this issue still persists. The only common factor is OxygenOS, I'd assume it to be a hardware or screen protector issue but it does not happen with custom ROMs.
After talking to @joshuous this is what he suspects could be the reason for the issue. Thanks again for explaining.
"The issue was mainly because the graphics buffer could not be dequeued (to allocate free buffers for graphics)
But that was as deep as I could trace
I haven't yet figured out a way to trace further
Maybe OOS screwed up somewhere trying to allocate too many buffers to graphics but not freeing them in time for more frames to be rendered"
There is no likely solution as of yet, will post if and when.
I experienced the same issue for the first time on OB4 and it persists from time to time. Solution: Reboot
Ok so as a temporary fix I found enabling 'Disable HW Overlays' from developer options helps a lot.
This maybe similar to a fix for YouTube lag found on Nexus 6.
https://www.xda-developers.com/fix-youtube-lag-on-the-nexus-6/
Hi, occasionally I have a similar problem where I experience intermittent lags or heavy frame drops during scrolling. My setup is OOS 9.0.3, stock kernel, unrooted.
Turning on "disable HW overlays" definitely helps a lot, but in my case just turning the screen off and on seems to get rid of the quirk at least until I turn the screen off.
Also there was a thread on XDA apparently talking about the same kind of lags, and the OP there said to have solved it by tinkering with some custom kernel to crank up the CPU frequency whenever s/he touches the screen. I didn't try it myself though.
same on op6/6t
on latest stable oxygenOS all ok...
but betas and older stable same lag after fast third scroll/tap... kernel cannot fix it, it's rom issue (
Same issue on oneplus 7T! But no one talks about It, it's absurd. Didn't find any solution, I'm getting crazy because is always so visible
Inviato dal mio HD1903 utilizzando Tapatalk
Hi, I am a new owner of OnePlus 7T, I bought it used yesterday, and it runs Oos 11.0.1.1HD85BA
I'm pretty happy with it although I've noticed some overheating when playing games (just 10 minutes of geshin impact or dead cells), when scrolling tiktok or yt.
In general with average use, with about 5/10 minutes of gaming at most, the battery reaches 15/20% in the evening. I think for an used phone it's good? Or for OP standard is not so good?
Another bug I've noticed is the inability to launch the task manager at times, some inaccuracies in gesture handling, that is pretty imprecise, also I've notice that sometimes notification when the screen is off are not so precise. So I thought:
Do you guys think it's better to go back to Android 10? (if possible, i've read that most of OP user loves OOS10 more than 11) Or is it better to wait for more hotfixes for 11?
I do not know the oneplus world so I rely on you, I've already installed all my apps and backup from my old phone, and If I have to format I won't continue to organize my things.
Just one things: if you have some optimization tips, or something to do when you first have the phone, please tell me... I don't even own a AMOLED display before and I've read that it could become green!!!! What can I do to avoid this problem?
Thank you all in advance
Reset all data
If above does not fix then unlock bootloader, root, install Dora kernel latest, sdcardfs version
I'm seeing lot's of posts about LE2123, LE2120, LE2125 being upgraded to android 12, with lots of people experiencing issues with unstable phones. Please humour me by answering this simple poll.
I would wait a while before updating. 12 has been a bomb and 11 isn't much better across all device manufacturers. No easy fixes.
Let Mikey try it...
You might get more useful info with a poll asking whether people experienced issues. After following several threads across various sites, I'm convinced that only a small minority have actually experienced "issues" (as in, something legit broken). The other vocal folks are just complaining that a feature was removed or changed and they don't like it. It's no different than every other major release.
Every major version is going to be a bit different from the previous one (that's the whole point of the new version number), and there's always a small risk and a small percentage of people who experience issues (which are almost always resolved by a wipe or clean flash). That's why OP tells you to back up your data before upgrading.
I updated to A12 and I am able to see some differences.
1. I've got 5g, volte and vowifi finally (5g on scnd SIM slot)
2. DPI is messed up in certain apps and options.
3. Battery life is worse (but I've been using stock kernel on A11, so this could make a difference)
4. I like A12s way to grant permissions.
Was it worth update? If you like your phone up to date - yes. If you care about system stability and look, stick with A11 until fixed A12 shows up.
It's not a coincidence that OP suspended A12 update. They see it was not ready.
My phone is OP 9 pro EU version. Did wipe it after update.
OnePlus is pulling its OxygenOS 12 update for the OP 9 and 9 Pro
Hopefully a bug-free release will be out soon
www.androidpolice.com
Smedslund said:
OnePlus is pulling its OxygenOS 12 update for the OP 9 and 9 Pro
Hopefully a bug-free release will be out soon
www.androidpolice.com
Click to expand...
Click to collapse
Good thing they pulled it before our OnePlus9Pro forum blew up!
I have the le2123 and I have encountered so many bugs. I did a wipe data and now all seems to make sense.
Now I'm pretty happy with this update. Let's see the battery in the next days.
davyleggend said:
I have the le2123 and I have encountered so many bugs. I did a wipe data and now all seems to make sense.
Now I'm pretty happy with this update. Let's see the battery in the next days.
Click to expand...
Click to collapse
Nice to hear, did they deliver on the throttling?
AndyC76 said:
Nice to hear, did they deliver on the throttling?
Click to expand...
Click to collapse
I think yes? Found this option "high performance option" system always run at max performance.
When enable it an icon in the status bar appears but I think they forgot to change the style of the icon because it's a little oversized.
Apart from that after wipe no more glitched animation, more smoothness in all the operations, allarm clock work, icons and font now are ok and layout too (before i have mismatched dpi in various apps), keyboard now have the button for pull down (before there isn't). The only thing now it's Netflix on platstore, it say device not support.
Rooted with success with no problem, magisk hide works and installed Netflix with apk works too.