Develop Bugs

[Q] os 4.6.1 bug for unlocked 32g

Hi, there, I just updated my phone, the unlocked us 32 g version, to the 4.6.1 using the o2 update image.
However, I just encounter a problem with the calling.
When I call out, it is fine. Everything is ok. However, when there is a call came in, I hear nothing . Only if I turned on the speaker, or plugged in the earbud, I can hear the voice from the other side.
Did anyone meet the same problem ？ or if there is anything else we can do to fix it ?

Having the same issue. Installed the AT&T version, 32 gb unlocked fire...
Sent from my SD4930UR using XDA Free mobile app

Hi, I update with O2 FireOS 4.6.1 and I haven't the issue, but you can try this:
1. Settings
2. Applications & Parental Controls
3. Manage Applications
4. Phone
5. Clear Data & Cache
6. Reboot your phone.
And If work for you, please post here.
If no work, please post here.

Thanks。
I didn't reset the phone to factory.
Now everything works fine.
One thing to mention here.
At first, I installed the newly updated Google things, and the play store didn't work.
Then I uninstalled them , and installed the original ones, (introduced in the video taught us how to install them), and now everything is OK.

luckysir said:
Thanks。
I didn't reset the phone to factory.
Now everything works fine.
One thing to mention here.
At first, I installed the newly updated Google things, and the play store didn't work.
Then I uninstalled them , and installed the original ones, (introduced in the video taught us how to install them), and now everything is OK.
Click to expand...
Click to collapse
I'm having the same issue. I tried the phone/clear cache/data, that didn't help. Also deleted the cache partition which I saw mentioned from another site. That didn't help either. I'd really rather not factory reset my phone. Anyone else have the issue and resolve it another way, or have any ideas for me?
Basically the earpiece doesn't work whether I get a call or make a call. Works fine over bluetooth, headset, or speakerphone. Just regular call, can't hear anything whether making the call or receiving it.

luckysir said:
Hi, there, I just updated my phone, the unlocked us 32 g version, to the 4.6.1 using the o2 update image.
However, I just encounter a problem with the calling.
When I call out, it is fine. Everything is ok. However, when there is a call came in, I hear nothing . Only if I turned on the speaker, or plugged in the earbud, I can hear the voice from the other side.
Did anyone meet the same problem ？ or if there is anything else we can do to fix it ?
Click to expand...
Click to collapse
Same issue here but I copied the question from here and posted on may day
I got this:
Hello,
My name is Vijay, I'm with Fire Phone support.
I'm sorry to hear about the trouble you've with the Fire Phone. This is definitely not what we want our customers to experience.
We are aware of this issue with the Fire Phone. I'd like to ask my sincere apologies for the inconvenience caused to you.
Our developers have isolated this issue to hearing aid on Fire Phone. In order to resolve the issue, please follow the below steps:
1. Swipe down from the top of the screen to open the Quick Actions panel, and then tap Settings > Device > Manage accessibility.
3. Use the switch to turn Hearing Aid Mode off, on, and then off again without leaving the Settings page. If Hearing Aid Mode is already on, use the switch to turn it off.
4. Please make a call to determine if the issue is resolved,
If you're still unable to hear the other caller, please restart the Phone by press and holding the Power button for 40 seconds.
Make sure to remove any wired headsets and/or turn off Bluetooth, and then make another test call.
Hopefully this should resolve the issue.
In case, if the issue still persists, please reach us over Phone so we can pull some information from your Phone so that we can work towards resolving the issue.
Click to expand...
Click to collapse
after step 4 my problem solved.

Notifications disappearing (messaging apps)

Hello everybody,
I got a strange problem occuring only in a certain situation. In order to explain better, have a concrete example here:
I write a message in Whatsapp or Threema. Then I lock the phone by closing the flip cover: The screen then shows the clock from "Asus Flip Cover" and turns off after 5 seconds. So far so good. Now: When I get a message, I hear the notification sound. I open the flip cover and... the notification immediately disappears. So sometimes I miss important messanges, just because of this bug.
At first I thought that it is a third party app that is responsible for this strange behaviour. But yesterday I did a reset of the entire phone via the settings app and didn't even use a backup to restore it. The bug reappeared.
Apparently nobody else is encountering this bug, so before sending the phone back I thought that maybe someone has an idea or even solution for me. The phone is the ZE551ML (not rooted or unlocked) and yesterday I also installed the new firmware (.59); the bug was there since I got the phone, but as I said: I thought it is a third party app that is responsible for this behaviour and I had no time to reset it earlier because of exams and stuff... Is there another way to reset the phone? Maybe a better one than the one over the settings app?
Sincerely,
Christophe

Is autostart denying these apps from automatically starting? By default it denies all apps. D'you have smart-saving mode on with extend standby or the option that turns off data when screen is off?
Is your lockscreen set to show notifications?

Hi rlaw,
rlaw said:
Is autostart denying these apps from automatically starting? By default it denies all apps.
Click to expand...
Click to collapse
WhatsApp and Threema are both allowed to auto-start. I remember that I had to set both of them to "allow".
rlaw said:
D'you have smart-saving mode on with extend standby or the option that turns off data when screen is off?
Click to expand...
Click to collapse
Battery mode is set to "Performance mode".
rlaw said:
Is your lockscreen set to show notifications?
Click to expand...
Click to collapse
The following are my settings under "Settings" -> "Sound & notification":
When device is locked: Show all notification content
App notifications: Threema and Whatsapp have no special settings
Apply Material Design: OFF
Notification access: ASUS Launcher

I'm sorry you're experiencing this. I'm tagging ASUS employee @Tuanies hopefully he can provide further assistance. I'm out of ideas since you have already factory reset the phone.

Does this happen if you disable the flip cover features?

Tuanies said:
Does this happen if you disable the flip cover features?
Click to expand...
Click to collapse
You mean turning the entire Asus Cover View off? I just tried and the messages still disappear. Actually the screen turns on automatically, the lockscreen appears and they disappear within a second.
After the reset I even got the strange behaviour that messages arrive, sometimes, late or only when I open the specific app.

Do you have any notification filters set?

Tuanies said:
Do you have any notification filters set?
Click to expand...
Click to collapse
No.

Just tell me if you think the problem is hardware related or software related. Personally I wouldn't say it is hardware related but one may never know for sure.
I know the firmware from ASUS is quite buggy (and has a lot of translation faults btw.) and, according to some research on the internet, ASUS often tries to break the law by not repearing rooted devices even if it is entirely legal in the EU. So before unlocking the bootloader and trying an alternative firmware, I just want to be sure.

yoshegg said:
Just tell me if you think the problem is hardware related or software related. Personally I wouldn't say it is hardware related but one may never know for sure.
I know the firmware from ASUS is quite buggy (and has a lot of translation faults btw.) and, according to some research on the internet, ASUS often tries to break the law by not repearing rooted devices even if it is entirely legal in the EU. So before unlocking the bootloader and trying an alternative firmware, I just want to be sure.
Click to expand...
Click to collapse
Sounds like a software problem, does it happen right after a wipe without anything else installed? Could just be an installed app causing issues.

Tuanies said:
Sounds like a software problem, does it happen right after a wipe without anything else installed? Could just be an installed app causing issues.
Click to expand...
Click to collapse
What do you mean by "wipe"? Do you mean booting into recovery? As is mentionned above I did a reset via the settings of the phone. After this reset I only installed Threema and Whatsapp and the problem appeared again.

Does it happen before those two apps are installed?

Tuanies said:
Does it happen before those two apps are installed?
Click to expand...
Click to collapse
How should I know? The problem appears with messaging apps, so I can't test it without them.

a possible answer
I think I had the same problem after arbitrarily swiping or tapping the wrong response to use CM lock for Asus with the latest updated.
Google "Lock apps" function integrated with CM AppLock" to navigate to a possible hidden app setting preventing you from seeing notifications and uncheck "Hide notifcations... " under the "Options" heading on said page.
shortcut:
(App Drawer settings, lock apps, input pattern you chose, settings (upper right 3 dots), uncheck "Hide notification")
I now have all my notifications back that I allowed in other settings.
I hope this helps.
I tried to post the URL, but I haven't posted 10 times yet.
-Mike

G4 H815L Freezes on calls and hang up

Hello there,
I've searched this problem over google for several times now, with no results hitting the problem i seem to have.
In depth, the problem is so:
Whilst in a call, after t (a certain amount of time which is not fixed) time (it can be seconds or minutes), I suddenly stop hearing the other person, and the phone won't respond to any attempts of hanging up myself. after a few more seconds frozen there's a *pwahh* sound and it hangs up.
any ideas what could this be?

almogkm said:
Hello there,
I've searched this problem over google for several times now, with no results hitting the problem i seem to have.
In depth, the problem is so:
Whilst in a call, after t (a certain amount of time which is not fixed) time (it can be seconds or minutes), I suddenly stop hearing the other person, and the phone won't respond to any attempts of hanging up myself. after a few more seconds frozen there's a *pwahh* sound and it hangs up.
any ideas what could this be?
Click to expand...
Click to collapse
Hi Almog,
I live in Israel also and have LG G4 H815L also.
I don't have the problem you mentioned.
Maybe the problem is with your cellular carrier. Try to insert different SIM card (from different carrier) and see if the problem continues, if yes, try to factory reset your phone.

Al0n said:
Hi Almog,
I live in Israel also and have LG G4 H815L also.
I don't have the problem you mentioned.
Maybe the problem is with your cellular carrier. Try to insert different SIM card (from different carrier) and see if the problem continues, if yes, try to factory reset your phone.
Click to expand...
Click to collapse
I'll try it. But if it doesn't work? what might cause such problems?
After a bit of cunsoltion someone told me it might be a motherboard issue, could it be so?

almogkm said:
I'll try it. But if it doesn't work? what might cause such problems?
After a bit of cunsoltion someone told me it might be a motherboard issue, could it be so?
Click to expand...
Click to collapse
first of all when did this problem started?(played with the theme on your phone ?changed icon pack? after you installed certain app? updated software?changed battery(not from the 2 you got with the phone) ? changed you screen protector lately? switched network?played with the dialer settings?did you update any application?changed any thing?)
basically if you dont think you have done any of the above just do factory reset...but before you do that download cpu z make sure all of the 6 cores are up and that the clock speed is 384 Mhz - 1.82Ghz if it does not show that you probably have a problem with the motherboard..(although you can still have a problem even if it does show its not an official indicator lol)
some of those thing might sound stupid but...when it started is the key to this.
honestly i would start with place the original battery than check if i have the correct network settings than cpu z than roll back anything i touched to default(settings and theme) than check if i disabled any app/service that might be needed than shut down background applications (1 by 1 ) after that uninstalling applications(1 by 1) after that factory reset after that take off the screen protector(which he might be even a little over the proximity sensor and than it will make the phone go crazy) and than send it to LG to fix it.

xzfzx said:
first of all when did this problem started?(played with the theme on your phone ?changed icon pack? after you installed certain app? updated software?changed battery(not from the 2 you got with the phone) ? changed you screen protector lately? switched network?played with the dialer settings?did you update any application?changed any thing?)
basically if you dont think you have done any of the above just do factory reset...but before you do that download cpu z make sure all of the 6 cores are up and that the clock speed is 384 Mhz - 1.82Ghz if it does not show that you probably have a problem with the motherboard..(although you can still have a problem even if it does show its not an official indicator lol)
some of those thing might sound stupid but...when it started is the key to this.
honestly i would start with place the original battery than check if i have the correct network settings than cpu z than roll back anything i touched to default(settings and theme) than check if i disabled any app/service that might be needed than shut down background applications (1 by 1 ) after that uninstalling applications(1 by 1) after that factory reset after that take off the screen protector(which he might be even a little over the proximity sensor and than it will make the phone go crazy) and than send it to LG to fix it.
Click to expand...
Click to collapse
well, i obviously changed things on my phone if change means to download an app and update it once in a while..
i've tried to switch SIMs with a friend who's using a different carrier and it didn't happen, although today it didn't happen.. i'll try getting a new SIM card, and if that doesn't work i'll try factory reset, and if THAT doesn't work than i'll send it to LG.
the hussle of checking each individual setting change is to damn big.

almogkm said:
well, i obviously changed things on my phone if change means to download an app and update it once in a while..
i've tried to switch SIMs with a friend who's using a different carrier and it didn't happen, although today it didn't happen.. i'll try getting a new SIM card, and if that doesn't work i'll try factory reset, and if THAT doesn't work than i'll send it to LG.
the hussle of checking each individual setting change is to damn big.
Click to expand...
Click to collapse
=)
i just hate factory reset ,because when you think you got all the apps you had installed suddenly when you need an app the most you realize that you forgot to reinstall it. lol
i know you can backup your apps but i always forget to do that.
but you are right , check individual app could be frustrating, but you can eliminate default apps or common apps such as facebook or whatsapp and such because if they were the source to the problem they will probably fix it in a day or two and you would see more people complaining about it.

accessibility service being off automatically

Hi,
I am using OP3 from last 1 month. Some app required accessibility service to be on, I observed that accessibility service being off automatically. Like applock, voodoo, freecharge, 360 security. Because of this applocks fingerprint is not working
Also sleep(turn of display) sometimes not worked
Any other faces this issue??
What is the problem? Can someone help me to solve this.
Phone is not rooted.
Thanks in advanced

I'm facing the same problem since updated to 3.2.0. In 3.2.1 the problem persist.
Till now the only solution was to boot in safe mode and grant to apps access everywhere.
Also not rooted, 100% stock.
If anybody knows a different solution I will also appreciate.
Sent from my ONEPLUS A3003 using Tapatalk

been having this issue myself - another relevant issue is that when you enable an accessibility service the PRE-BOOT PIN screen gets disabled.

O don't know how many people have this problem, I've tried to report also on oneplus.net but there till now, nobody reacted.
Forgot about pre-boot pin, your right buddy.
Sent from my ONEPLUS A3003 using Tapatalk

3.2.2 is coming let's see, it it resolves

got 3.2.2 - have't had the issue come up yet but it's only been a few hours

Both the start up pin and the accessibility randomly turning off are google issues and not directly related to the oneplus.
For the accessibility service randomly turning off. try turning off the battery optimization for the app that needs access. see if that works.
This might work for the pin. Also might have to redo it every time you reboot your phone.
If you have Require Pin At Boot enabled: disable "require pin at boot" option, enable Accessibility Service, and re-enable the security option.

2x4 said:
got 3.2.2 - have't had the issue come up yet but it's only been a few hours
Click to expand...
Click to collapse
use the groom icon in recent apps and you will see it happen even on 3.2.2

lparcshinoda said:
use the groom icon in recent apps and you will see it happen even on 3.2.2
Click to expand...
Click to collapse
Yes it is happening after using groom,

skavangar said:
Both the start up pin and the accessibility randomly turning off are google issues and not directly related to the oneplus.
For the accessibility service randomly turning off. try turning off the battery optimization for the app that needs access. see if that works.
This might work for the pin. Also might have to redo it every time you reboot your phone.
If you have Require Pin At Boot enabled: disable "require pin at boot" option, enable Accessibility Service, and re-enable the security option.
Click to expand...
Click to collapse
It is not google issue, before this i was using nexus 6 and i didn't feel it. Also i checked on various mobiles

skavangar said:
Both the start up pin and the accessibility randomly turning off are google issues and not directly related to the oneplus.
For the accessibility service randomly turning off. try turning off the battery optimization for the app that needs access. see if that works.
This might work for the pin. Also might have to redo it every time you reboot your phone.
If you have Require Pin At Boot enabled: disable "require pin at boot" option, enable Accessibility Service, and re-enable the security option.
Click to expand...
Click to collapse
It is not google issue, before this i was using nexus 6 and i didn't feel it. Also i checked on various mobile.

ONE PLUS replies my mail as follow
"we don't suggest any third party application so hence I request you to please uninstall the third party application. "

niranjansahu009 said:
ONE PLUS replies my mail as follow
"we don't suggest any third party application so hence I request you to please uninstall the third party application. "
Click to expand...
Click to collapse
wow

You have to turn off the battery optimisation for the app that uses the accessibility service. This will fix the issue.
This fixed it for me at least.

I tried this, after cleaning apps from recent app option. After this service being off, even if battery optimization is off for that apps,

lparcshinoda said:
use the groom icon in recent apps and you will see it happen even on 3.2.2
Click to expand...
Click to collapse
Now i not used that groom button. And it is going perfectly

adding the app that uses accessibility to the white list for battery optimization solved this issue for me

2x4 said:
adding the app that uses accessibility to the white list for battery optimization solved this issue for me
Click to expand...
Click to collapse
No I din for me

Question Issues afteratest update

S21fe updated to UI5.
Couple of issues.... Fingerprint reader sometimes doesn't work when phone hasn't been used for some time. When it happens I need to double tap the screen to wake it up and then scan my fingerprint again.
Also "back" gesture (where I swipe up from the right bottom of the screen) sometimes instead of going back brings up the list of background apps.
Both issues very annoying.
Anyone else experienced anything similar?

Try clearing the system cache. Double check all settings. If that flaws things get more complicated...
A factory reset may be needed, but hard to say if it will resolve the issues. Someone will need to try the latter if the former doesn't work. A global reset of settings is a less drastic option but it may not be enough and still take a lot of time.
This is one reason why I spurn upgrades on a platform that's fulfilling its mission. Lol, I'm still using UI 1.5, no glaring issues.
Unfortunately with latter versions an upgrade may resolve flaws in earlier post >1.5 variants. Tough choice once you are on Android 11 as there's no roll back on stock Samsung's for that. I wasn't locked into using 11 on my N10+'s and never will load it. 12 is even worse.
Roll back is an option for you if bootloader wasn't upgraded too. Eventually Samsung will fix it if it's a firmware/software glitch but don't hold your breath for that

blackhawk said:
Try clearing the system cache
Click to expand...
Click to collapse
With each major update, I always clean the system cache from the recovery !

jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
That may not be enough if going from 11 to 12, etc.
Rule #1 - if the OS is fast, stable and fulfilling its mission let it be! You have little to gain and a lot to lose. Although there was a big security hole in 12, not sure if it was patched already or if the patch is in what you just install. Oddly that hole isn't in 9-11.
Gookill is a mess...

I have the same problem with fingerprint unlocking. It simply doesn't work (if I press the side button, it works). Some hours ago I wiped the system cache and after that, I didn't notice the described problem. I will see in the next few hours.

Now I changed "Fingerprints -> Show icon when screen is off" to "Tap to show" instead of "On always on display" which was the default after the upgrade to Android 13.
UPDATE: The phone still has the same problem. Sometimes it simply doesn't allow it to unlock with a fingerprint. The screen is locked as hell. Only the side button unlocks it.

If you go to Lock screen>Always On Display>Show always, does that solve your problem? Mine was set to "show for new notifications" only and the fingerprint icon would disapperar after locking it.

Mine was set to "Show for new notifications". As you suggested, I changed it to "Show always" and we will see, how it works. In my opinion, it is better to show display only when something happens. But something changed and problems occurred.

Report: it didn't help. I have found out that the issue appears if the phone is locked for a while and then a notification comes. This is the reason why this problem exists also while using Android Auto. It creates a notification when it connects ... and then the phone can be unlocked with a fingerprint until the side button is pressed. I'm sure this is a bug that didn't exist before the upgrade to Android 13.

no such issues here with the eu version. definitely an upgrade in every way.

After 3 days with Android 13 on snapdragon variant, only two minor issues found here : slow charging (2h20 from 0 to 100, less than 2h before) and an "unauthorized action due to modified device" screen when rebooting, disappearing by touching "OK" button. Don't know what is unauthorized but... well. I was rooted before, now stock unrooted and relocked bootloader. It doesn't seems to lock something, everything I use is working.

I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.

d0j0m0j0 said:
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
Click to expand...
Click to collapse
The recent update with the December security patch seens to have resolved this issue for me.
Edit: scratch that, still not fixed...
Edit2: turning off lock scrern mods in Galaxy MaxHz seems to help.

jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
How does one do that?

xda-eh said:
How does one do that?
Click to expand...
Click to collapse
It's on the boot menu on Samsung's.

blackhawk said:
It's on the boot menu on Samsung's.
Click to expand...
Click to collapse
You're referring to accessing the recovery mode as explained here?

xda-eh said:
You're referring to accessing the recovery mode as explained here?
Click to expand...
Click to collapse
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.

blackhawk said:
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
Click to expand...
Click to collapse
The link I provided and the one you did refer to the same thing. Only difference is my link also provides a way to do it via ADB. In any event, thanks for your response.