Develop Bugs

Question Oxygen OS 12 Idle Touch Sampling Rate

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

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

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

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

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

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

Switch back to OOS11 if it's a problem.

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

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

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

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

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

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

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

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

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

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

Question Updated To (13) Dev. Preview #2 & Lost Vo5G For Voice Calls!

Recently, when I decided to receive the OTA for 13 Dev Preview#2, among some of the changes from Tiramisu, or build #1, was my Pixel 6 Pro no longer had the feature Vo5G for voice calls.
This feature with it's own toggle used to reside at the bottom of the internet settings screen, right underneath the setting, "Allow 2G".
I did a beta feedback report on this, and will update this post when/if they find a solution for this issue. es

evnStevn said:
Recently, when I decided to receive the OTA for 13 Dev Preview#2, among some of the changes from Tiramisu, or build #1, was my Pixel 6 Pro no longer had the feature Vo5G for voice calls.
This feature with it's own toggle used to reside at the bottom of the internet settings screen, right underneath the setting, "Allow 2G".
I did a beta feedback report on this, and will update this post when/if they find a solution for this issue. es
Click to expand...
Click to collapse
Beta 1 should come out tomorrow, so I guess we will see what happens.

Doug8796 said:
Beta 1 should come out tomorrow, so I guess we will see what happens.
Click to expand...
Click to collapse
Where did you hear the 13 beta would drop tomorrow?

opz187 said:
Where did you hear the 13 beta would drop tomorrow?
Click to expand...
Click to collapse
DP1 came out on the 2nd Thursday of February Android 13 Developer Preview 1 is here with themed icons, privacy changes, and more
DP2 came out on the 3rd Thursday of March Android 13 Developer Preview 2 arrives with notification permission requests and other changes
But March was when we had the late update for the Pixel 6/Pro as well (I think), so maybe that affected DP2.
More generally, here's the monthly plan for Betas, although it doesn't mention dates or particular Thursdays, probably because it's always tentative: Android 13 Developer Preview

roirraW edor ehT said:
DP1 came out on the 2nd Thursday of February Android 13 Developer Preview 1 is here with themed icons, privacy changes, and more
DP2 came out on the 3rd Thursday of March Android 13 Developer Preview 2 arrives with notification permission requests and other changes
But March was when we had the late update for the Pixel 6/Pro as well (I think), so maybe that affected DP2.
More generally, here's the monthly plan for Betas, although it doesn't mention dates or particular Thursdays, probably because it's always tentative: Android 13 Developer Preview
Click to expand...
Click to collapse
Gotcha, makes sense now

This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.

Well said, and as I said on reddit:
"The first build was released on 2nd Thursday, the 10th of February. The second build was released the 3rd Thursday, the 17th of March. Due to the dirty pipe exploit and taking an average of the two dates of the month (roughly 13.5 day of the month (rounds up)), the build will almost certainly come out tomorrow, April 14, 2022."
roirraW edor ehT said:
DP1 came out on the 2nd Thursday of February Android 13 Developer Preview 1 is here with themed icons, privacy changes, and more
DP2 came out on the 3rd Thursday of March Android 13 Developer Preview 2 arrives with notification permission requests and other changes
But March was when we had the late update for the Pixel 6/Pro as well (I think), so maybe that affected DP2.
More generally, here's the monthly plan for Betas, although it doesn't mention dates or particular Thursdays, probably because it's always tentative: Android 13 Developer Preview
Click to expand...
Click to collapse

here you go, tell me if you need something more. es

LLStarks said:
This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.
Click to expand...
Click to collapse

LLStarks said:
This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.
Click to expand...
Click to collapse
a magenta fan too, I take it? was that what you were looking for? If you need something different just let me know. es

The modem in DP2 is older and less refined than the newer builds of Android 12+.

This is not a modem issue as far as I've seen. It's possible that the early modems didn't support it, but the carrier config is the culprit here. There are clear differences between DP1 and DP2 where a flag that literally says vonr/vo5g is missing.
Maybe I'm doing this wrong, but replacing the DP2 one with the DP1 version doesn't seem to enable it. I was trying to adapt a magisk module to do that. But it's a little weird because sometimes the carrier configs are encoded and other times they are mostly plain text.
At least Google is acknowledging it.

LLStarks said:
This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.
Click to expand...
Click to collapse
LLStarks said:
This is not a modem issue as far as I've seen. It's possible that the early modems didn't support it, but the carrier config is the culprit here. There are clear differences between DP1 and DP2 where a flag that literally says vonr/vo5g is missing.
Maybe I'm doing this wrong, but replacing the DP2 one with the DP1 version doesn't seem to enable it. I was trying to adapt a magisk module to do that. But it's a little weird because sometimes the carrier configs are encoded and other times they are mostly plain text.
At least Google is acknowledging it.
Click to expand...
Click to collapse
Hey, I was just reading your comments, and yes, now, they are acknowledging the missing field. The first time I sent beta feedback on this issue was two weeks prior. They got everything from me, bug report, screen recordings from #1 & #2, as if "the before, and after" weight -loss ads! So a day or goes by, got the buginizer confirmation in my inbox, and I looked for the report filling in the beta feedback app grouped together with others I reported and the whole thing had been deleted, it wasn't anywhere! So I said fuc$ this shi#, I did the whole thing over again, even flashed back to DPB #1, to make sure Vo5G was still there! (lol) This time around, I made mention (several times) throughout my feedback report, that this first report seem to fall off of the radar, and could someone explain how & why, it had to be human error, blah, blah blah, & anyway this time around, it seems to be getting worked, but not vanishing into thin air. A friend of mine that I spoke to about this, got me in his mindset that this was maybe something that wasn't supposed to get out for public consumption until their Pixel 7 Series rollout, of course equipped with (stable) Android 13, and Vo5G Voice Calls included in their "Feature Blitz". To be honest, I'm still not so sure some of that isn't going on, as we all know both Google & Samsung been playing that shi# for years (because they can)!

LLStarks said:
This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.
Click to expand...
Click to collapse

hey, thanks for the hit. es

they better include that feature when they release android 13 for pixel 6 series, i currently dont even have voLTE which is extremely annoying, even when i have 2 sims installed, if I make a phone call it disconnects my data on both lines and I am unable to use internet at all, its making me want to switch to another phone.

Beta 1 still doesn't include this.

NewDev4IOS said:
they better include that feature when they release android 13 for pixel 6 series, i currently dont even have voLTE which is extremely annoying, even when i have 2 sims installed, if I make a phone call it disconnects my data on both lines and I am unable to use internet at all, its making me want to switch to another phone.
Click to expand...
Click to collapse
I heard it was omitted (not included) from DP#2 affecting only T-Mobile customers?! It may be just a rumor, others may be experiencing the same as us. I happy to learn we will see it again soon, next update or Android 13 Beta along with Face Unlock!

Doug8796 said:
The modem in DP2 is older and less refined than the newer builds of Android 12+.
Click to expand...
Click to collapse
how did that happen...another of Google's attempts to get all the teams back under one roof, post-covid 19 style-ish, by bringing back the ever popular, "Bring Your Medical Marijuana To Work" week?! lol

The QPR modems have generally been the newest.
But with respect to Vo5G in particular, I'm not really sure where the carrier settings are being read from. Overwriting the protobuf files for T-Mobile doesn't seem to help.

General Sailfish OS for Xperia 10 III

Xperia 10 III is now officially supported by Sailfish OS: https://blog.jolla.com/xperia-10-iii/
From Wikipedia:
Sailfish OS is a Linux-based operating system based on free software, and open source projects such as Mer as well as including a closed source UI. The project is being developed by the Finnish company Jolla.
Click to expand...
Click to collapse
Anyone in here tried it yet?

I've bought my license and am trying to get this going - I've been unable to use the fastboot command to unlock the bootloader, which I assumed was due to the Android version being 12, and I'm now struggling to downgrade this to 11 as it seems all the tools for doing so are Windows only.
Has anyone done this process on Linux successfully? I understand some people on the Sailfish forums have managed to get it to flash over an Android 12 base but I can't even get to that stage because of the OEM unlock command failing.
Really looking forward to going back to Sailfish after a bit of a hiatus though!

Piecer said:
I've bought my license and am trying to get this going - I've been unable to use the fastboot command to unlock the bootloader, which I assumed was due to the Android version being 12, and I'm now struggling to downgrade this to 11 as it seems all the tools for doing so are Windows only.
Has anyone done this process on Linux successfully? I understand some people on the Sailfish forums have managed to get it to flash over an Android 12 base but I can't even get to that stage because of the OEM unlock command failing.
Really looking forward to going back to Sailfish after a bit of a hiatus though!
Click to expand...
Click to collapse
According to its readme file, Newflasher runs on Linux too: https://github.com/munjeni/newflasher
So I think it should be possible to flash an Android 11-based firmware from here: https://forum.xda-developers.com/t/stock-firmware-backups.4382229/ using this tool. But I never used it (neither on Windows nor on Linux) so I can't say for sure whether that works.
As for the issue with unlocking your bootloader, at the risk of stating the obvious, did you enable "OEM unlocking" in developer options?

As for the issue with unlocking your bootloader, at the risk of stating the obvious, did you enable "OEM unlocking" in developer options?
Click to expand...
Click to collapse
Ha! Yes I did do all the required steps. I found an Android 11-based build on the Sailfish forums which worked, after doing it twice with Newflasher. Once this was done the OEM unlock command did its thing without a hiccup. Sailfish OS is now running nicely on the 10 III - hopefully Jolla are able to provide some more complete instructions for those who have managed to upgrade themselves into a documentation loop!

I've been using the X10III with Sailfish for several days now, and the experience is quite smooth. There is no green tint visible, but the "color space" gets really smashed and mangled in low light + low brightness situations... I think it's more or less the same bug. The best way to describe is that the dark areas of the screen are rendered with 8-bit color palette and way too high brightness. I created a bug report for it over at Sailfish OS Forum for those who wish to keep an eye on that.
There are three known issues: Camera API doesn't support the three back cameras (Camera2 API does support it, so it's very fixable), the indicator led is way too green (driver issue), and issues with noise cancellation during phone calls (seems to be fixed in git).
Despite the above, SFOS on X10III a hugely net positive! VoLTE works now - finally - so spring 2023 can now arrive (killing 3G here in Finland). 5G support is not there (yet?), which is a tiny bit unfortunate.
I didn't realize that the AOSP firmware is so far away from Android firmware... I somehow assumed before that they were the same... Oh well, live and learn.

direc85 said:
Despite the above, SFOS on X10III a hugely net positive! VoLTE works now - finally - so spring 2023 can now arrive (killing 3G here in Finland). 5G support is not there (yet?), which is a tiny bit unfortunate.
I didn't realize that the AOSP firmware is so far away from Android firmware... I somehow assumed before that they were the same... Oh well, live and learn.
Click to expand...
Click to collapse
I have a hard time understanding why it is necessary to repair a thing that is not broken?
VoLTE calls? Why? Today, almost every phone subscription includes if not all free, then at least thousands of minutes of free calls. In addition, there are available all sorts of apps that you can use for voice calling.
And in general, calling is the least used feature of the phone lately.

ksuuk said:
I have a hard time understanding why it is necessary to repair a thing that is not broken?
Click to expand...
Click to collapse
What exactly are you referring to? 3G, the OS in the device, or something else..?
ksuuk said:
VoLTE calls? Why? Today, almost every phone subscription includes if not all free, then at least thousands of minutes of free calls. In addition, there are available all sorts of apps that you can use for voice calling.
Click to expand...
Click to collapse
Why shouldn't I use what I already paid for?
But yes, phone calls are getting rarer; for me it's something between daily and weekly. But still, it's the official method to be reached, supported by pretty much every device, so why not just use it instead of apps.
Also, if I wanted to use only apps to talk with my friends, I'd have five chat apps installed, some of them analyzing me, and all of them draining my battery. No thanks...
But let's get back to topic. Does anyone know how to solve the color banding issue on AOSP?

direc85 said:
I didn't realize that the AOSP firmware is so far away from Android firmware... I somehow assumed before that they were the same... Oh well, live and learn.
Click to expand...
Click to collapse
Tell me, are there any battery charging settings in this OS? Android in Xperia 10 III has settings to limit charging to 80, 90% a very nice option.

Aranornen said:
Tell me, are there any battery charging settings in this OS? Android in Xperia 10 III has settings to limit charging to 80, 90% a very nice option.
Click to expand...
Click to collapse
I can't say anything about features built into the OS (as I've never used it), but I was able to find two 3rd party apps which let you limit the maximum battery charge level:
Battery Buddy | OpenRepos.net — Community Repository System
openrepos.net
takimata / harbour-battery-charging-control · GitLab
SailfishOS application which allows to stop battery charging at user-defined levels.
gitlab.com

Piecer said:
I've bought my license and am trying to get this going - I've been unable to use the fastboot command to unlock the bootloader, which I assumed was due to the Android version being 12, and I'm now struggling to downgrade this to 11 as it seems all the tools for doing so are Windows only.
Has anyone done this process on Linux successfully? I understand some people on the Sailfish forums have managed to get it to flash over an Android 12 base but I can't even get to that stage because of the OEM unlock command failing.
Really looking forward to going back to Sailfish after a bit of a hiatus though!
Click to expand...
Click to collapse
hi can you help me o i have an Xperia 5 phone running sailfish os same as your Xperia 10 mark 3 i cant buy license to run apk app you can extract aliendalvik file can you give it to me, i will keep it from sharing to anyone, because it is the source of life jolla , i will transfer you a small amount of money, i come to sailfish os full of passion but not enough money , hope you can help, thank you very much

General Oxygen OS 13 ver. F.16

Yesterday I installed Oxygen 13 F.16
Bugs that started with Android 12 still ported to Android 13.
1. The photo has no latitude and longitude. There is only the name of the street (and the wrong one, theneighboring one).There is no Google Minimap as before.
2. The Task Manager does not close all open applications. There is always one left. And this is extremelystressful.
3. In a private safe, the photos do not rotate horizontally.
4. When touched, the phone does not show the current time. You have to tap 2x hard for it to display the time.
5. The notification sound of SMS, washing machine, dryer, coffee machine is the same.

Why post bugs here? Report them to OnePlus.

djsubterrain said:
Why post bugs here? Report them to OnePlus.
Click to expand...
Click to collapse
Because it's about OnePlus 9 Pro?
So that OP 9 Pro users know what awaits them with the new Oxygen OS 13?
I guess I made myself clear.

Alex_H_H said:
Because it's about OnePlus 9 Pro?
So that OP 9 Pro users know what awaits them with the new Oxygen OS 13?
I guess I made myself clear.
Click to expand...
Click to collapse
Yeah I suppose, forewarned is forearmed, if you do get bugs, remember to post them in OP tho, if no-one tells them then they won't investigate

djsubterrain said:
Yeah I suppose, forewarned is forearmed, if you do get bugs, remember to post them in OP tho, if no-one tells them then they won't investigate
Click to expand...
Click to collapse
I am not prejudiced. 2 years I reported these problems on the OP forum, sent to the OP service ..
For 2 years, they didn't fix anything, they just broke the system more.
I am not the only one who has these problems. Many users have the
Hopefully everything would be okay at Oxygen 12. Unfortunately, it was tragic. Oxygen 13 is another crap in OP 9 Pr
The problems started with the pseudo update LE2123_11_C.38. It only got worse with each new one.
1000 EUR for rubbish.

Alex_H_H said:
Yesterday I installed Oxygen 13 F.16
Bugs that started with Android 12 still ported to Android 13.
1. The photo has no latitude and longitude. There is only the name of the street (and the wrong one, theneighboring one).There is no Google Minimap as before.
2. The Task Manager does not close all open applications. There is always one left. And this is extremelystressful.
3. In a private safe, the photos do not rotate horizontally.
4. When touched, the phone does not show the current time. You have to tap 2x hard for it to display the time.
5. The notification sound of SMS, washing machine, dryer, coffee machine is the same.
Click to expand...
Click to collapse
Let's go through these, one by one, just to be thorough.
1. This seems like a genuine bug, but there's no sense in complaining about it if you don't report it to OnePlus.
2. This is a feature I think, where some apps have priority and remain as a sticky in the app switcher. You can customise this, look in the settings. eg. I only sticky Spotify and ultimately always close the rest.
3. Probably a bug, see no. 1.
4. Well that's what AOD is for no?
5. This seems more like a missing feature to me than a bug. Again, report it to them.
Did you report any of them to OnePlus at all? Because you have some actual points of criticism here.
(If you are actually as upset with this as you seem to be, try a Custom ROM, it's what they're here for ;-))

Tr4il said:
Let's go through these, one by one, just to be thorough.
1. This seems like a genuine bug, but there's no sense in complaining about it if you don't report it to OnePlus.
2. This is a feature I think, where some apps have priority and remain as a sticky in the app switcher. You can customise this, look in the settings. eg. I only sticky Spotify and ultimately always close the rest.
3. Probably a bug, see no. 1.
4. Well that's what AOD is for no?
5. This seems more like a missing feature to me than a bug. Again, report it to them.
Did you report any of them to OnePlus at all? Because you have some actual points of criticism here.
(If you are actually as upset with this as you seem to be, try a Custom ROM, it's what they're here for ;-))
Click to expand...
Click to collapse

Tr4il said:
Let's go through these, one by one, just to be thorough.
1. This seems like a genuine bug, but there's no sense in complaining about it if you don't report it to OnePlus.
2. This is a feature I think, where some apps have priority and remain as a sticky in the app switcher. You can customise this, look in the settings. eg. I only sticky Spotify and ultimately always close the rest.
3. Probably a bug, see no. 1.
4. Well that's what AOD is for no?
5. This seems more like a missing feature to me than a bug. Again, report it to them.
Did you report any of them to OnePlus at all? Because you have some actual points of criticism here.
(If you are actually as upset with this as you seem to be, try a Custom ROM, it's what they're here for ;-))
Click to expand...
Click to collapse
For 2 years I have been reporting it to the OP service. As I wrote earlier, no fixes in subsequent patches. I am tempted to try Cyanogen. After all, Oxygen comes from him.

Alex_H_H said:
For 2 years I have been reporting it to the OP service. As I wrote earlier, no fixes in subsequent patches. I am tempted to try Cyanogen. After all, Oxygen comes from him.
Click to expand...
Click to collapse
The original OxygenOS maybe, yes, but the latest iterations of OxygenOS are based of OnePlus's ColorOS. And Cyanogen does not exist anymore. Try its successor LineageOS if you're feeling like using barebones Android, I'd recommend crDroid or PixelExtended.

General Magic OS 7 Beta Recruitment

Honor are now recruiting beta testers for Magic OS 7 on the Magic 4 Pro.
Open the My HONOR app, select club, on the top it should say Magic OS Beta recruitment, select sign up.
You have until 28th February to sign up, beta testing begins on March 2nd.
You must be running Magic UI 6.0.0.180.

afgzee said:
Honor are now recruiting beta testers for Magic OS 7 on the Magic 4 Pro.
Open the My HONOR app, select club, on the top it should say Magic OS Beta recruitment, select sign up.
You have until 28th February to sign up, beta testing begins on March 2nd.
You must be running Magic UI 6.0.0.180.
Click to expand...
Click to collapse
In UK only I think ?!

nico97470 said:
In UK only I think ?!
Click to expand...
Click to collapse
Possibly UK only as I am in the UK. I cannot confirm though.

afgzee said:
Possibly UK only as I am in the UK. I cannot confirm though.
Click to expand...
Click to collapse
I will patiently wait for the beta proposal in France. ( Mayotte for me in the Indian Ocean) .

Just received magic os 7.0

Just signed up, let's see what happens next.

i have the global version in NA, is it not possible to get it?

Terens said:
i have the global version in NA, is it not possible to get it?
Click to expand...
Click to collapse
Only region 431 here is the news from the club https://www.hihonor.com/uk/club/top...-recruitment-notice/topicid-3516159450152960/

afgzee said:
Just received magic os 7.0
Click to expand...
Click to collapse
Super ! What are your first impressions or feelings about this beta?

nico97470 said:
Super ! What are your first impressions or feelings about this beta?
Click to expand...
Click to collapse
It was slightly laggy at first, but I think my phone just needed a bit of time to get used to it. The settings menu has been slightly polished up, settings menu looks very similar to emui 12.
There is a new assistant called yoyo, not sure if this is just a rebranded Huawei celia.
The UI is exactly like magic UI/EMUI, so no change there so far.
Since this is the first beta there are no major UI changes, possibly in the following betas to come.
I did notice when trying new things and current things like using the software update checker that it gets stuck on loading for about 10 seconds until it checks for updates.
It's based on android 13 with January 2023 security patch.
A bit disappointed as I thought since Huawei sold honor they would come up with a UI of their own at this point but its still pretty much Huawei's EMUI.

afgzee said:
There is a new assistant called yoyo, not sure if this is just a rebranded Huawei celia.
Click to expand...
Click to collapse
I have a Chinese version and the assistant only in Chinese understands how you are?

volkodav1975 said:
I have a Chinese version and the assistant only in Chinese understands how you are?
Click to expand...
Click to collapse
Yoyo is unusable in Europe. So yoyo is useless.

afgzee said:
It was slightly laggy at first, but I think my phone just needed a bit of time to get used to it. The settings menu has been slightly polished up, settings menu looks very similar to emui 12.
There is a new assistant called yoyo, not sure if this is just a rebranded Huawei celia.
The UI is exactly like magic UI/EMUI, so no change there so far.
Since this is the first beta there are no major UI changes, possibly in the following betas to come.
I did notice when trying new things and current things like using the software update checker that it gets stuck on loading for about 10 seconds until it checks for updates.
It's based on android 13 with January 2023 security patch.
A bit disappointed as I thought since Huawei sold honor they would come up with a UI of their own at this point but its still pretty much Huawei's EMUI.
Click to expand...
Click to collapse
The umbilical cord is hard to cut.

Hi, does work call recording on magic os 7?

afgzee said:
Just received magic os 7.0
Click to expand...
Click to collapse
Hello, can you ccheck, is there after update a VOLTE ?

afgzee said:
It was slightly laggy at first, but I think my phone just needed a bit of time to get used to it. The settings menu has been slightly polished up, settings menu looks very similar to emui 12.
There is a new assistant called yoyo, not sure if this is just a rebranded Huawei celia.
The UI is exactly like magic UI/EMUI, so no change there so far.
Since this is the first beta there are no major UI changes, possibly in the following betas to come.
I did notice when trying new things and current things like using the software update checker that it gets stuck on loading for about 10 seconds until it checks for updates.
It's based on android 13 with January 2023 security patch.
A bit disappointed as I thought since Huawei sold honor they would come up with a UI of their own at this point but its still pretty much Huawei's EMUI.
Click to expand...
Click to collapse
Hello, can you ccheck, is there after update a VOLTE ?

afgzee said:
magic 7
Click to expand...
Click to collapse
Check the call recording works? Thread 'Call Recording Android 12 (new Honor)'

volkodav1975 said:
Check the call recording works? Thread 'Call Recording Android 12 (new Honor)'
Click to expand...
Click to collapse
It works!

goshoa said:
Oi, o trabalho de gravação de chamadas no magic os 7?
Click to expand...
Click to collapse
It works

Just wanted to add that call recording does work, but if you plan on using Google Wallet to pay, that doesn't work. It says the device is rooted or unsupported.
So if you to plan on using it don't update to v7 just yet, I will keep you all updated as updates push through.