Database Info

Is this the ultimate BUG?

I just found the ultimate bug and I believe this bug is responsible for G-Alarm and pTravelalarm not working. These alarm programs set the system volume to a predefined value, no matter where it was before (off, for example).
Why the heck does the PHONE RINGER volume influence the SYSTEM volume?
Check out the video:
here
http://www.youtube.com/watch?v=aBZAkJwDHT0
Can this be fixed in Windows? Reg-Hack?

Anyone here with a AT&T Fuze that can test this please? Is my hardware defective? I'm still within the 30 days to return that sucker if it is.
Thanxxx

Wow, strange!!
I already saw your post in the G-Alarm thread yesterday.
Just tested it with my Touch Pro running ROMeOS 1.51, and I do not have this bug.

johanromijn said:
Wow, strange!!
I already saw your post in the G-Alarm thread yesterday.
Just tested it with my Touch Pro running ROMeOS 1.51, and I do not have this bug.
Click to expand...
Click to collapse
I suspect it is related to the latest AT&T stock rom. I hope someone with a brand new AT&T version can test this. If it's just a rom problem, then I can probably flash mine but I don't want to try that right now and lose warranty if I'm not sure...
here's my latest video that shows directly how crucial this bug is to any alarm program:
http://www.youtube.com/watch?v=lKIqwyk9g9I
Cheers
Stefan

Again, it's myself who figured it out. After hours of trying and 3 hard resets (thanks to SpriteBackup I didn't have to install everything over again!)
Here is the result and the culprit is identified!
http://www.youtube.com/watch?v=M_6-i976_xE
Anyone else here with the AT&T Fuze that has the same problem? Is there a fixed version of ozim available?

electron73 said:
Again, it's myself who figured it out. After hours of trying and 3 hard resets (thanks to SpriteBackup I didn't have to install everything over again!)
Here is the result and the culprit is identified!
http://www.youtube.com/watch?v=M_6-i976_xE
Anyone else here with the AT&T Fuze that has the same problem? Is there a fixed version of ozim available?
Click to expand...
Click to collapse
Interesting, but can you please post your solution in text form as well so that every single person who reads this thread from now until the end of time does not have to go watch a Youtube video ?

DrunkenOstrich said:
Interesting, but can you please post your solution in text form as well so that every single person who reads this thread from now until the end of time does not have to go watch a Youtube video ?
Click to expand...
Click to collapse
Yeah sure, no problem. I just thought a picture says more than 1000 words and a video says even more. But here in plain English:
Starting up the OZ IM Messenger Client on the AT&T Fuze (or worse, having it autostart with the system) completely screws up the system volume settings. Suddenly the RINGER volume slider also influences the SYSTEM volume. Say you turn your ringer volume all the way down but you still want to listen to mp3's in Windows Media... nada. If you set your phone to silent or vibrate and have a nice alarm program like G-Alarm installed, the alarm will go off but no sound out of the speaker!
After closing down OZ IM you still have to soft-reboot to get your system sounds back.

DrunkenOstrich said:
Interesting, but can you please post your solution in text form as well so that every single person who reads this thread from now until the end of time does not have to go watch a Youtube video ?
Click to expand...
Click to collapse
Seconded. Technical stuff lends itself to words better.

dr g said:
Seconded. Technical stuff lends itself to words better.
Click to expand...
Click to collapse
Is there a newer version of the OZ IM available that doesn't f*** up the system volume? That company's website doesn't even allow you to contact anyone, let alone check for updates or get support

Here's the newest development in this case.
Tried a different OZ IM (verizon version) last night and the sound bug was GONE. BUT I got errors connecting. Found out that there is a config file with verizon gateway in it, replaced it with the AT&T one. Still an error. Different one though (404). Re-installed the original AT&T version. Sound bug back immediately
Just overwrote the .exe file with the one from Verizon: Sound bug gone but again connection error 404...
WTF?
Anyone have a different AT&T version besides the obviously screwed up 2.0.84 M ?

[Q] Nexus 5 incoming call screen gets me stuck

earched Google all over and couldn't find a solution for this. When I get an incoming call on my nexus 5, half of the screen goes black, and the main buttons disappear, and I can't do anything with the status bar. Basically, I can't do anything besides answer, hang up or text. Only after I answer the functionality returns. It's really annoying when I'm in the middle of something and than someone calls and I can't just ignore it, I have to wait until the caller hangs up (and then usually he will call again). The half black screen also bothers me but it's not the real problem, I just guess it's part of the bug. I tried using 3rd party apps for incoming calls but they don't solve this problem. This is how it looks like (I can't post a picture so copy the link):
img208.imageshack.us/img208/1973/919d.png
I'm surprised I didn't find a solution because it's a very annoying problem and I don't think it only happens to me. I'll be glad if you know how to fix this. Thanks

shahar4499 said:
earched Google all over and couldn't find a solution for this. When I get an incoming call on my nexus 5, half of the screen goes black, and the main buttons disappear, and I can't do anything with the status bar. Basically, I can't do anything besides answer, hang up or text. Only after I answer the functionality returns. It's really annoying when I'm in the middle of something and than someone calls and I can't just ignore it, I have to wait until the caller hangs up (and then usually he will call again). The half black screen also bothers me but it's not the real problem, I just guess it's part of the bug. I tried using 3rd party apps for incoming calls but they don't solve this problem. This is how it looks like (I can't post a picture so copy the link):
img208.imageshack.us/img208/1973/919d.png
I'm surprised I didn't find a solution because it's a very annoying problem and I don't think it only happens to me. I'll be glad if you know how to fix this. Thanks
Click to expand...
Click to collapse
That's exactly how its meant to be. If you flash a ROM like omni you can get a less intrusive dialer that looks something like this:
http://omnirom.org/wp-content/uploads/2013/11/UnobtrusiveCallNotify.png
If you've never installed a ROM before there are loads of tutorials to get you started, just don't take any shortcuts (like toolkits!)
//Nexus 5//Nexus 4//HTC WFS//

Tom540 said:
That's exactly how its meant to be. If you flash a ROM like omni you can get a less intrusive dialer that looks something like this:
(URL)
If you've never installed a ROM before there are loads of tutorials to get you started, just don't take any shortcuts (like toolkits!)
//Nexus 5//Nexus 4//HTC WFS//
Click to expand...
Click to collapse
But wouldn't flashing the device prevent me from upgrading my android version? I mean, one of the advantages in nexus is that it gets more upgrades and sooner than everybody else, isn't it?

shahar4499 said:
But wouldn't flashing the device prevent me from upgrading my android version? I mean, one of the advantages in nexus is that it gets more upgrades and sooner than everybody else, isn't it?
Click to expand...
Click to collapse
most custom roms get updated even before an ota is out. once google drops source into aosp, that day or next, most custom roms update. sometimes this happens a week before otas go out, sometimes its about the same time.

simms22 said:
most custom roms get updated even before an ota is out. once google drops source into aosp, that day or next, most custom roms update. sometimes this happens a week before otas go out, sometimes its about the same time.
Click to expand...
Click to collapse
So what you're saying it's that custom ROM is always better?

shahar4499 said:
So what you're saying it's that custom ROM is always better?
Click to expand...
Click to collapse
have u tried one of the full screen caller id apps ?
I tried this one on my Moto G with Android 4.3.
https://play.google.com/store/apps/details?id=tw.nicky.HDCallerID
see if it works for your phone.

same problem here, thanks god i'm not alone! I simply don't get why on incoming calls i cant hit the home button and go back on my stuff!!! annoying. hope in a solution, had tried many apps but didn't find the right one

I have the same problem in the last month I had this issue 5 or 6 times until now...any idea besides installing a custom ROM?

Similar problem here.
I have a similar problem. No black screen but I can't do anything and the nav bar disappears. N5 with 4.4.4 stock, Franco Kernel, root, xposed Framework. I found out that other phones have the same problem and in a moto x thread I found a thread that perfectly matches my problem.
I think it's an android bug.. like a file system or something.. not related to any customization.

Marshamallow piece of crap

Hi,
I have a moto g 3 and updated to marshamallow.
it was the first time i ever upgraded an android phone.
little did i know the troubles this would cause.
-phone is now considerably slower.... **noticeable SLOWER!**
- I used to shake my phone and lit up the flashlight. now that works 1 out of 20 tries. its bugged.
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
I want to downgrade to lollipop.
Can anyone point me to a how to link procedure?
i need some foolproof very in detail.procedure, im a guy with general computer knowledge, but not a die hard.
have not rooted a phone ever. but if theres a procedure for downgrading that is detailed thoroughly & foolproof id appreciate the link so I can study it.
This

Have you done a factory reset? that solves most problems.

jazf78 said:
Hi,
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
Click to expand...
Click to collapse
Being a fellow who uses the phone as a phone, I immediately noticed that thing after upgrading from a CM12.1 based rom to a CM13 based one... It was one of the functions I used more during the day.
Some other things that makes me want to come back to CM12.1...? yes.
-The fact that the Contact tab inside the dialer doesn't filters out contacts I decided to not show on the Contact app.
-(Not really a MM issue, but instead related to Cyanogenmod.) No call recording (another essential feature for me)!
The phone part of our "smart" devices is becoming worse and even more worse every update . Maybe it's time to come back to a Nokia 3310 or a Qtek 9090 like in the good old days

jazf78 said:
Hi,
I have a moto g 3 and updated to marshamallow.
it was the first time i ever upgraded an android phone.
little did i know the troubles this would cause.
-phone is now considerably slower.... **noticeable SLOWER!**
- I used to shake my phone and lit up the flashlight. now that works 1 out of 20 tries. its bugged.
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
I want to downgrade to lollipop.
Can anyone point me to a how to link procedure?
i need some foolproof very in detail.procedure, im a guy with general computer knowledge, but not a die hard.
have not rooted a phone ever. but if theres a procedure for downgrading that is detailed thoroughly & foolproof id appreciate the link so I can study it.
This
Click to expand...
Click to collapse
If your using Indian XT1550 please take TWRP backup and give me the download link I need it very badly.

ethaniel said:
Being a fellow who uses the phone as a phone, I immediately noticed that thing after upgrading from a CM12.1 based rom to a CM13 based one... It was one of the functions I used more during the day.
Some other things that makes me want to come back to CM12.1...? yes.
-The fact that the Contact tab inside the dial
no idea what this all meant. plz stay on topic, thanks
Click to expand...
Click to collapse

Nazeerchauhan said:
If your using Indian XT1550 please take TWRP backup and give me the download link I need it very badly.
Click to expand...
Click to collapse
im from México.

eemgee said:
Have you done a factory reset? that solves most problems.
Click to expand...
Click to collapse
i haven´t but i read somewhere else that a factory reset would not downgrade android version. since it also changed its firmware..
dont know if thats true or false.. did you or anyone reading this has actually done a factory reset and their android device downgraded itself? need to be sure, dont want to waste time, backing **** up, doing factory reset
only to notice it still marshmallow and then redownload and restore everything so i can use the phone and still have the problem.
thanks

jazf78 said:
ethaniel said:
Being a fellow who uses the phone as a phone, I immediately noticed that thing after upgrading from a CM12.1 based rom to a CM13 based one... It was one of the functions I used more during the day.
Some other things that makes me want to come back to CM12.1...? yes.
-The fact that the Contact tab inside the dial
no idea what this all meant. plz stay on topic, thanks
Click to expand...
Click to collapse
I wasn't so much off-topic, it was something related to the thread title (Marshmallow piece of crap), but OK! I respect your statement. Last reply I make on this thread.
Hope tomorrow will be a better and happier day for you
Click to expand...
Click to collapse

jazf78 said:
Hi,
I have a moto g 3 and updated to marshamallow.
it was the first time i ever upgraded an android phone.
little did i know the troubles this would cause.
-phone is now considerably slower.... **noticeable SLOWER!**
- I used to shake my phone and lit up the flashlight. now that works 1 out of 20 tries. its bugged.
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
I want to downgrade to lollipop.
Can anyone point me to a how to link procedure?
i need some foolproof very in detail.procedure, im a guy with general computer knowledge, but not a die hard.
have not rooted a phone ever. but if theres a procedure for downgrading that is detailed thoroughly & foolproof id appreciate the link so I can study it.
This
Click to expand...
Click to collapse
I think downgrading will be a more difficult task than a factory reset. A factory reset should clear all your issues.

Android Auto issues on Poco F1 Custom Roms

On all custom Roms I've tried so far (and they've been a few), there's an ongoing problem while using Android Auto connected to the car's built-in display. Basically, if you plug in your phone and start using AA, after a while the bottom bar on the car's display will disappear, and although you can keep driving and AA will keep working, once you stop and unplug the phone from the car, the phone will lock you out and it's screen will start to flicker and go crazy, giving you no other option but to force reboot the phone.
This issue was present on MIUI Oreo roms as well, but since they updated to Pie last month, it was addressed and a fix was found (seems it was related to the devices default display drivers). For custom Roms, there's a temporary workaround, which is to disable hardware overlays in developer settings, but you need to do this every time you reboot your phone since these settings don't stick permanently.
I've posted and mentioned this issue on several different custom ROM threads, but as far as I know, none of the devs has acknowledged the issue nor has tried to find a solution. So, the question is; how many of you have the same problem?
Please provide your feedback, as it would be good to let the devs know this is not unimportant or isolated.

krilok said:
On all custom Roms I've tried so far (and they've been a few), there's an ongoing problem while using Android Auto connected to the car's built-in display. Basically, if you plug in your phone and start using AA, after a while the bottom bar on the car's display will disappear, and although you can keep driving and AA will keep working, once you stop and unplug the phone from the car, the phone will lock you out and it's screen will start to flicker and go crazy, giving you no other option but to force reboot the phone.
This issue was present on MIUI Oreo roms as well, but since they updated to Pie last month, it was addressed and a fix was found (seems it was related to the devices default display drivers). For custom Roms, there's a temporary workaround, which is to disable hardware overlays in developer settings, but you need to do this every time you reboot your phone since these settings don't stick permanently.
I've posted and mentioned this issue on several different custom ROM threads, but as far as I know, none of the devs has acknowledged the issue nor has tried to find a solution. So, the question is; how many of you have the same problem?
Please provide your feedback, as it would be good to let the devs know this is not unimportant or isolated.
Click to expand...
Click to collapse
On which MIUI Version are you having that problem?
Which car display with which software version are you using?
For me with MIUI 8.12.27 weekly EU version and Skoda Bolero display I'm not having the issue you describe.

MikelFuchs said:
On which MIUI Version are you having that problem?
Which car display with which software version are you using?
For me with MIUI 8.12.27 weekly EU version and Skoda Bolero display I'm not having the issue you describe.
Click to expand...
Click to collapse
Please read the title: on custom roms, not miui...

You wrote on Oreo stock ROM it was present to.

oiseau1201 said:
You wrote on Oreo stock ROM it was present to.
Click to expand...
Click to collapse
Yes, and it was (plenty of comments on MIUI forums and over the net, if you want to take a look...) They fixed it on Pie, and if you're still running Oreo and don't have issues, then I guess they fixed it there, too.
This poll, topic and thread is for the issues still affecting Aosp based custom roms, such as Crdroid, PE, Lineage, etc.

Even I would like to know the result of this poll. I am on the verge of trying out a custom ROM (since i am done with the bugs in MIUI). But if AA doesn't work on custom ROM, it is a showstopper for me.

Hi,
I have a different issue with Android Auto.
My problem is that when I connect to Android Auto, after a couple of minutes (1-2, 2-3 minutes) the screen on the car's display seems to be stuck, and from then on it doesn't follow my progress on the way. The screen itself is not frozen, because e.g. I can make a reroute but after it is done it goes back to the "original" state of my route when it stopped progressing. The screen remains responsive regarding the controls because I can even change to Google Maps on the car's AA display, and it works flawlessly.
Anyone else had this issue?
I'm using xiaomi.eu rom 9.1.17 beta

aghilvr said:
Even I would like to know the result of this poll. I am on the verge of trying out a custom ROM (since i am done with the bugs in MIUI). But if AA doesn't work on custom ROM, it is a showstopper for me.
Click to expand...
Click to collapse
I'm currently on Crdroid, and in my opinion it's the one that works best. As for the AA issue, it's present on all custom roms, but for the time being, I'm using the workaround I mentioned on OP and can use AA fully.

rn74 said:
Hi,
I have a different issue with Android Auto.
My problem is that when I connect to Android Auto, after a couple of minutes (1-2, 2-3 minutes) the screen on the car's display seems to be stuck, and from then on it doesn't follow my progress on the way. The screen itself is not frozen, because e.g. I can make a reroute but after it is done it goes back to the "original" state of my route when it stopped progressing. The screen remains responsive regarding the controls because I can even change to Google Maps on the car's AA display, and it works flawlessly.
Anyone else had this issue?
I'm using xiaomi.eu rom 9.1.17 beta
Click to expand...
Click to collapse
Strange, I tried an EU rom about a couple of weeks ago for a few days and AA worked out of the box. Didn't like the MIUI stuff, though, so reverted back to Crdroid.
I however remember I flashed the full MIUI rom completely, wiping everything and starting from scratch, so if you want to stick with MIUI, maybe you should do a fresh install...

krilok said:
Strange, I tried an EU rom about a couple of weeks ago for a few days and AA worked out of the box. Didn't like the MIUI stuff, though, so reverted back to Crdroid.
I however remember I flashed the full MIUI rom completely, wiping everything and starting from scratch, so if you want to stick with MIUI, maybe you should do a fresh install...
Click to expand...
Click to collapse
Edit: just noticed. Are you using Waze for navigation? If you are, there's an ongoing location issue with the app running on MIUI...

Having the same issue running PIxelExperience and it's driving me nuts.
krilok said:
, there's a temporary workaround, which is to disable hardware overlays in developer settings, but you need to do this every time you reboot your phone since these settings don't stick permanently.
Click to expand...
Click to collapse
I did not know that, thanks for the tip .
Update: you can automate disabling the hardware overlays using Tasker and the Secure Settings plugin

bob*nwk said:
Having the same issue running PIxelExperience and it's driving me nuts.
I did not know that, thanks for the tip .
Update: you can automate disabling the hardware overlays using Tasker and the Secure Settings plugin
Click to expand...
Click to collapse
Thanks, I had read you could use tasker for that, but it's a paid app and I wouldn't be using it for anything else at the moment. I'm fine with remembering to disable it manually. Still, I believe the issue has to be addressed at some point by the devs...

One General question:
The only thing keeping me away from custom roms is the AA issue. Nice to hear that at least we have a workaround.
At the moment i am on MIUI Android pie and using a VW in build AA Display. The issue i'm having is that WhatsApp notifications are not shown on the Display. I can send WhatsApp Messages via Ok Google but not able to hear received messages.
Do you guys have the same issue?

gella1992 said:
One General question:
The only thing keeping me away from custom roms is the AA issue. Nice to hear that at least we have a workaround.
At the moment i am on MIUI Android pie and using a VW in build AA Display. The issue i'm having is that WhatsApp notifications are not shown on the Display. I can send WhatsApp Messages via Ok Google but not able to hear received messages.
Do you guys have the same issue?
Click to expand...
Click to collapse
Wouldn't be able to confirm that, although I did read somewhere that if you're using any Dual apps on MIUI, AA won't work correctly. Are you using two WhatsApp accounts by any chance...?
I can tell you though that on the current rom I'm using (crdroid), they do work and appear on the cars screen, although most of the time there's no notification ringtone whenever they arrive. Since that was happening on my previous phones too, be it on nougat, oreo and pie, I guess that's a problem with AA itself...

Thanks for your quick reply.
Happy to hear that it is generally working.
Not using dual Apps. Will try to flash a custom Rom in the next days

krilok said:
Thanks, I had read you could use tasker for that, but it's a paid app and I wouldn't be using it for anything else at the moment. I'm fine with remembering to disable it manually. Still, I believe the issue has to be addressed at some point by the devs...
Click to expand...
Click to collapse
If you buy it, I guarantee you will be using it for a lot more than just that...

papete said:
If you buy it, I guarantee you will be using it for a lot more than just that...
Click to expand...
Click to collapse
I can confirm this. Best $5,- I spent on an app ever.

papete said:
If you buy it, I guarantee you will be using it for a lot more than just that...
Click to expand...
Click to collapse
I understand and appreciate the recommendation, but I've already got Macrodroid for other automation functions...

I don't get the menu on the bottom visible with disabling HW Overlay, tested Nitrogen,CRdroid, Liquid Remix,LOS
using: beryllium-9.1.24-9.0-vendor-firmware

mf76130 said:
I don't get the menu on the bottom visible with disabling HW Overlay, tested Nitrogen,CRdroid, Liquid Remix,LOS
using: beryllium-9.1.24-9.0-vendor-firmware
Click to expand...
Click to collapse
Works for me and others as well, although someone did mention on another thread he couldn't get this workaround to work either...
This is my setup:
USB debugging on and hardware overlays disabled.
In AA developer options, enable 720, 1080, unknown sources.
If it still won't work, then Im guessing it could maybe be due to different screen panels or something...

Two weird issues on Oneplus 6

I have a Oneplus 6 256GB, got it second hand in good condition, with original OxygenOS 10.3.5 ROM.
Works good, but two issues:
1. When calling a number I am unable to press keys for an automatically spoken menu and unable to mute microphone. Even when installing another dialer the issue persists.
2. The Quicksettings tiles cannot be edited or re-ordered, the pencil icon is missing and long pressing also does not do anything.
I have searched the internet, but no solutions found.
Anyone familiar with this issue ?

mermaidkiller said:
I have a Oneplus 6 256GB, got it second hand in good condition, with original OxygenOS 10.3.5 ROM.
Works good, but two issues:
1. When calling a number I am unable to press keys for an automatically spoken menu and unable to mute microphone. Even when installing another dialer the issue persists.
2. The Quicksettings tiles cannot be edited or re-ordered, the pencil icon is missing and long pressing also does not do anything.
I have searched the internet, but no solutions found.
Anyone familiar with this issue ?
Click to expand...
Click to collapse
I would try to update. For me personally when I encountered a bug that I couldn't deal with I would switch to the beta version... And back to the regular build as needed. Running the beta is really easy. Of course OnePlus is fixing things still on this phone, but not as rapidly as before. And at some point they won't fix much at all, then your best option will be to move to a custom rom... Or another phone. I'm sure that's a year or so away though.
Sent from my ONEPLUS A6003 using Tapatalk

jasonv31 said:
I would try to update. For me personally when I encountered a bug that I couldn't deal with I would switch to the beta version... And back to the regular build as needed. Running the beta is really easy. Of course OnePlus is fixing things still on this phone, but not as rapidly as before. And at some point they won't fix much at all, then your best option will be to move to a custom rom... Or another phone. I'm sure that's a year or so away though.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
I just did the latest update before rooting last weekend.

mermaidkiller said:
I just did the latest update before rooting last weekend.
Click to expand...
Click to collapse
Then I would try a full wipe and reinstall. Or the beta. Or another rom. Good luck.
Sent from my ONEPLUS A6003 using Tapatalk

Any luck with a fix for your issue(s) ?
I moved from latest beta to clean install of latest stable OnePlus stock rom. Not seeing any of the issues you mentioned. Hope that was fixed... [emoji16]
Sent from my ONEPLUS A6003 using Tapatalk

mermaidkiller said:
I have a Oneplus 6 256GB, got it second hand in good condition, with original OxygenOS 10.3.5 ROM.
Works good, but two issues:
1. When calling a number I am unable to press keys for an automatically spoken menu and unable to mute microphone. Even when installing another dialer the issue persists.
2. The Quicksettings tiles cannot be edited or re-ordered, the pencil icon is missing and long pressing also does not do anything.
I have searched the internet, but no solutions found.
Anyone familiar with this issue ?
Click to expand...
Click to collapse
Try to clean flash or use msm tool

chandu dyavanapelli said:
Try to clean flash or use msm tool
Click to expand...
Click to collapse
That's what I'd do. ☝ Maybe roll back using MSM tool and then update from there. When is the last time you formatted data @mermaidkiller ? Just curious. Just sounds like an issue that may happen if a good wipe wasn't done....Hope you get it fixed! I'm quite sure you know about MSM tool. Takes about three or four minutes to let it do its thing. Super easy to use!!