Related
Just flashed CM12 posted in the development section on 2 brand new fires that were on 5.0.1 for my kids. No games play audio properly, its just sound of jibberish \ glitchy. What gives, worked fine on fire OS. Thx
I'm getting this too with some games on the rr rom.
Sent from my SM-N9005 using Tapatalk
cm.12.1 with 501 software
So far on certain games such as subway surf and temple run, it sounds as if the sound has crashed and is stuck. Managed to fix the issue once by clearing the cache but it's happening again on more than one tablet
Yes, Subway Surfers is the game with the issue, and Shopkins. A few games works fine. I have been able to make it work by toggling the sound on/off within the game after minimizing the game and reopening from the recent app menu. I disabled the audiofx as well. I read about a similar issue with CM12.1 on another device forum and it mentioned something about forcing 2 cpu cores to stay active? No idea what that's about. I hope someone can help us with it or I may have to go back to stock.
I'm having the same issue with certain games. It also happens on SlimLP 2.3, which is where I first noticed it. I then tried CM only to find the same issue. :/
And yet for me Temple run and subway surfers works fine, I have the issue with pac-man CE and ski safari 2.
Sent from my SM-N9005 using Tapatalk
Audio loops in "Adventure Capitalist" also
Audio locks up and loops at high (or sometimes super slow) speed on the game Adventure Capitalist also, typically after viewing an advertisement. This happened on my tablet and I thought it was just mine until I heard my daughter's tablet doing it on Subway Surfers. Both tablets are Amazon Fire 7 5th Gen running CM12.1 Unofficial (from FireOS v5.0.1 via TWRP).
So I had this issue myself and found that turning audio fx off solves it on cm 12.1 and RR
If you are still having the sound issue try that
Damn, disregard. Sound went back to heinous
Was there ever a solution for this problem? I'm on CM 12.1 2016-06-14 and still experiencing these issues, e.g. with "Minions Paradise" and some others. Game itself is running fine but sound is broken...
cybermcm said:
Was there ever a solution for this problem? I'm on CM 12.1 2016-06-14 and still experiencing these issues, e.g. with "Minions Paradise" and some others. Game itself is running fine but sound is broken...
Click to expand...
Click to collapse
Seems to be an issue with all custom ROMs for this device. Only FireOS is glitch free.
cybermcm said:
Was there ever a solution for this problem? I'm on CM 12.1 2016-06-14 and still experiencing these issues, e.g. with "Minions Paradise" and some others. Game itself is running fine but sound is broken...
Click to expand...
Click to collapse
sadly it's sometimes the app itself. Can you uninstall and re download? It might fix it, but might be a waste of time.
ldeveraux said:
sadly it's sometimes the app itself. Can you uninstall and re download? It might fix it, but might be a waste of time.
Click to expand...
Click to collapse
This doesn't help, I've 2 Fire for my kids and both have this problem...
Thx for your answers maybe a developer will fix this in the future...
cybermcm said:
This doesn't help, I've 2 Fire for my kids and both have this problem...
Thx for your answers maybe a developer will fix this in the future...
Click to expand...
Click to collapse
Likely not given problem impacts all custom roms for this device (different developers) and has remained unresolved for 6+ months. If audio performance is a priority might consider returning to FireOS and stripping out all the Amazon crud that makes it a dog.
Audio bug was fixed with CM-12.1 version 2016-08-10. This is really great!!
Thx developers!
The phone just vibrates on and on, and then does nothing.
It does not matter if the screen is on, or unlocked, or I am even at the app itself.
Once every ten attempts it works, and then nothing again. Uninstalled/Reinstalled app. Nothing.
Anyone experienced this?
Thanks
same here
evak2979 said:
The phone just vibrates on and on, and then does nothing.
It does not matter if the screen is on, or unlocked, or I am even at the app itself.
Once every ten attempts it works, and then nothing again. Uninstalled/Reinstalled app. Nothing.
Anyone experienced this?
Thanks
Click to expand...
Click to collapse
Hi,
Ah, I thought I was going crazy. I used it for a month or so, and it worked even early January, and then, it suddenly stopped working (no modifications done to the phone). Also using Oneplus 3T here. The card which is used for Android Pay still works just fine.
So there must be something with TFL then...
Kind regards,
Denis
meptalon said:
Hi,
Ah, I thought I was going crazy. I used it for a month or so, and it worked even early January, and then, it suddenly stopped working (no modifications done to the phone). Also using Oneplus 3T here. The card which is used for Android Pay still works just fine.
So there must be something with TFL then...
Kind regards,
Denis
Click to expand...
Click to collapse
Thanks, quite possible.
My parent's phone (also a 3T) works fine. Just not mine. Maybe theirs will go bogus down the line as well.
I'm actually annoyed because it's never worked for me since getting this phone :/ No mods, all stock. I have rooted and messed around, but it didn't work before I did that, nor after returning to stock.
I'm having the same problem. I could get through the barriers but not out. Very annoying.
evak2979 said:
The phone just vibrates on and on, and then does nothing.
It does not matter if the screen is on, or unlocked, or I am even at the app itself.
Once every ten attempts it works, and then nothing again. Uninstalled/Reinstalled app. Nothing.
Anyone experienced this?
Thanks
Click to expand...
Click to collapse
Definitely happening to me as well, since one update in January. On a bus the phone continually buzzes, on the tube it just fails.. I've not managed to see it work yet
#oneplus3t #nfcfail
It worked on 4.0.2 and before, and its wqorking again on the 7.1.1 update. Used it for the last few days on Tube no problem, it even seems a little quicker than before ;
TheBishopOfSoho said:
It worked on 4.0.2 and before, and its wqorking again on the 7.1.1 update. Used it for the last few days on Tube no problem, it even seems a little quicker than before ;
Click to expand...
Click to collapse
Which version of OS are you using? 4.0.3? Has there been an 7.1 update to the Oneplus 3t? I'm still on 7 or do you mean android pay update for 7.1?
So it seems quite stable now? Last time I used it I couldn't get out of the underground (OS 3.6.x I think that was.)
Eggstones said:
Which version of OS are you using? 4.0.3? Has there been an 7.1 update to the Oneplus 3t? I'm still on 7 or do you mean android pay update for 7.1?
So it seems quite stable now? Last time I used it I couldn't get out of the underground (OS 3.6.x I think that was.)
Click to expand...
Click to collapse
Im running 7.1.1 Oneplus Beta 3 for the Oneplus. Its a great update to 4.0.3, better battery life and Android pay works.
Still working fine? Contemplating if i should use android pay or my other contactless card.
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Matzeus said:
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Click to expand...
Click to collapse
Probably a hardware issue. Find one of the many sensor testing apps and run it several times to identify a weak or defective sensor. There is not going to be a cleaning or software solution. If you do find a sensor not working 100%, do another clean wipe and test again before looking into replacement. Normally the FR on the P4 is extremely fast and accurate.
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Matzeus said:
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Click to expand...
Click to collapse
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
v12xke said:
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
Click to expand...
Click to collapse
How can you say google forums are a joke when literally hundreds of people are having the same issue? I dont want to believe that we all have hardware issues. Otherwise the hardware would be some hot garbage.
I removed and readded the face multiple times already.
I booted into safe mode. It works there. But like I said, it also works after a normal reboot for some hours/days before it needs a reboot again.
I also did test the sensors, no errors there. However my next step is to run the test when the error is present.
Any specific suggestion on which app I should use for testing?
Thanks again.
@Matzeus
No specific sensor app. Facial data is stored on the Titan M chip, and the only way I know to wipe that facial data and potentially fix it is by doing a factory reset from the stock recovery. Fastboot flashing will not wipe the Titan data and even from recovery is only a partial wipe. If you've ever had TWRP installed, there is a looong thread on broken face lock there. FDR from both recovery and setup would be my next suggestion.
@v12xke
In the past i ran the factory default from the system settings, didnt help. After that I used Googles "Android Flash Tool", which didnt help either.
Additional information: the device has never been rooted or anything. Always been on stock firmware.
Anyways, small update on the whole thing:
The issue occured again, I ran the app "Soli Sandbox" and it simply didnt do anything. So far so good.
After closing Soli Sandbox and clicking on the face unlock option in the system settings, magically everything worked properly again. Even without a reboot.
I am not sure what solved the error now..
I guess its safe to say, that all motion gestures stop working once the problem occurs.
Will keep this thread updated as I find out more.
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
The march update claims to have brought some improvements to Pixel 4s face unlock feature. At least thats what they say in the official changelog.
Biometrics
General improvements for face unlock stability & performance *[4]
Lets see if the problem is gone now. Will keep this thread updated.
sufy1000 said:
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
Click to expand...
Click to collapse
It's uncannily good. I keep the phone upright in a cradle by my PC so I can monitor it, and all I have to do is turn my head to peek, and it unlocks every time. It's pretty amazing. I've never had a problem with it.
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Matzeus said:
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Click to expand...
Click to collapse
Still going strong? And did you notice this issue on Android 10?
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Matzeus said:
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Click to expand...
Click to collapse
Thanks. I've got a new 4 XL that definitely has this issue but I didn't spend much time with it before updating to 12 from 10. It's a real PITA. I've never installed a custom ROM, but thinking I may need to do what you've done as this is irritating af.
@puzzlefighter
Just go for it man.
I was so upset about face unlock and i regret that i didnt install a custom ROM earlier.
Share your results afterwards please if you installed a custom ROM
this is not a hardware problem, but a software one, it started with the release of android 12, the problem is not in the face unlock sensor, but in the proximity sensor, it sticks, as if it was closed with a finger, I use Pixel experience + 12, this firmware does not have this problem, I'm disappointed with google developers(
I installed Real Racing 3 when the game starts the message that the UINPUT-Goodix controller is connected and the basic controls do not work.
Does anyone have the same problem?
Same problem here, really frustrated
Installed real racing and facing same issue on xiaomi 11t
Same problem ( game controller connected:uinput-goodix. ) issue started after android 12 miui 13 update currently using miui 13.0.2.0 global and has this problem in real racing 3, f1 mobile etc even the fire shoot button in dead trigger 2 also not showing in some missions so stuck at a level because of not being able to complete it because of touch button not showing
pippo211 said:
I installed Real Racing 3 when the game starts the message that the UINPUT-Goodix controller is connected and the basic controls do not work.
Does anyone have the same problem?
Click to expand...
Click to collapse
Exactly the same problem on my 11Tpro. MIUI 13.0.8.0. Is someone working on this?
Exactly the same problem on my 11Tpro. MIUI 13.0.8.0. Is someone working on this?
About uinput-goodix issue on K50 Gaming sensors when opening RR3
Xiaomi's official store is insensitive at least in trying to help solve the problem with a cell phone that they sold me a few days ago.
It wouldn't be hard for them to help me.
Here's my protest and I'll reconsider the next time I want to buy a phone, if it's worth the risk.
K50 GAMING.mp4
drive.google.com
any tips from the developers?
**** xiaomi lol sorry for this, i have Xiaomi 11T Pro and have same problem!
Same problem unfortunately no fix till today 11May no fix has been published
I tried to ticket to either of FM\ EA , Xiaomi but no Answer till now and yesterday FM released a new update but no fix been patched i play RR3 since 2014 and use Xiaomi never had problem like this so disappointment
I think I've found a solution to this, go to the Game Turbo menu, then settings, then under Game DND disable "Restrict buttons and gestures"
Same problem with gangster vegas touch controls are not showing because of this imaginery game controller detection which I don't have even my bluetooth is turned off
I have same issue using redmi note 10 pro
modren combat 5 and apex legend mobile, same problem. how can we fix it?
same problem in redminote 10 pro android 12, how fix it? very frustrated
Yousef8001 said:
I think I've found a solution to this, go to the Game Turbo menu, then settings, then under Game DND disable "Restrict buttons and gestures"
Click to expand...
Click to collapse
How do I do that? There is no such setting there.
Edit: I found it, but the issue is still present, I disabled this option and I still can't use touch controls
herdunz73 said:
same problem in redminote 10 pro android 12, how fix it? very frustrated
Click to expand...
Click to collapse
I know! Man, try to reboot your phone, it helped me! And also try to disable "Restrict buttons and gestures" under DND In game turbo settings. I figured out that you have to reboot your phone if you want to play games with touch, I already told that to Xiaomi and I hope they will fix it, so you won't be forced to reboot.
k_e_K_e__ said:
I know! Man, try to reboot your phone, it helped me! And also try to disable "Restrict buttons and gestures" under DND In game turbo settings. I figured out that you have to reboot your phone if you want to play games with touch, I already told that to Xiaomi and I hope they will fix it, so you won't be forced to reboot.
Click to expand...
Click to collapse
I tried it but not work.
pippo211 said:
I tried it but not work.
Click to expand...
Click to collapse
Oh, I'm sorry
Same here as of July 5th
daviddg5 said:
Exactly the same problem on my 11Tpro. MIUI 13.0.8.0. Is someone working on this?
Click to expand...
Click to collapse
Apr 7, 2022
Add bookmark
#6
Exactly the same problem on my Poco F4 gt
Hi...
I played normally on Android 12, but when updating to 13 the game has a black screen... I already did the Hard reset, reinstalled, completely cleaned all the files and the problem persists. Sometimes restarting the phone and opening the game right when Android loads the game works, but most of the time it just gets a black screen. Does anyone have an idea how to resolve this? Oneplus support blames Riot and Riot support blames Oneplus!
Are you rooted? Any mods? Are you using qhd or fhd? What version/region do you have? 60 or 120hz? Any ad blockers?
dladz said:
Are you rooted? Any mods? Are you using qhd or fhd? What version/region do you have? 60 or 120hz? Any ad blockers?
Click to expand...
Click to collapse
No Root.
CN - Global Rom
Bootloder Unlocked
qhd and fhd same problem
60 or 120hz same problem
Any configuration I leave it presents the same error ... The game only works if I restart the phone and open the game right when the system starts, if I wait 5 seconds it no longer works. And when functional, it has FPS drops.
Same problem, but after last wild rift update rebooting not working anymore
Being BL unlocked alone trips some SafetyNet things iirc, since you're already unlocked. Your only solution might be to root and add Wild Rift to the Magisk deny list or using Shamiko.
BolAchUdO said:
No Root.
CN - Global Rom
Bootloder Unlocked
qhd and fhd same problem
60 or 120hz same problem
Any configuration I leave it presents the same error ... The game only works if I restart the phone and open the game right when the system starts, if I wait 5 seconds it no longer works. And when functional, it has FPS drops.
Click to expand...
Click to collapse
It's been a couple of months since I'm having this bug just wanna know any of you guys find a solution for it? Or riot or OnePlus FINALLY fixed this issue?
Scar3crow7 said:
It's been a couple of months since I'm having this bug just wanna know any of you guys find a solution for it? Or riot or OnePlus FINALLY fixed this issue?
Click to expand...
Click to collapse
No. I write to the Riot support from time to time, but nothing changes. They say problem on the OnePlus side
This bug its Oneplus side, for sure. I have a "workaround", just unninstall or disable "app enhancement service" (package com.oplus.cosa) and reboot, after that try open the game.
THE "GAMES APP" WILL STOP WORKING PROPERLY, but Wild Rift should open now.
Machad3x said:
This bug its Oneplus side, for sure. I have a "workaround", just unninstall or disable "app enhancement service" (package com.oplus.cosa) and reboot, after that try open the game.
THE "GAMES APP" WILL STOP WORKING PROPERLY, but Wild Rift should open now.
Click to expand...
Click to collapse
WOW... Now Wild Rift is OK for me...
I use ADB and remove the COSA!
Tks!
BolAchUdO said:
Hi...
I played normally on Android 12, but when updating to 13 the game has a black screen... I already did the Hard reset, reinstalled, completely cleaned all the files and the problem persists. Sometimes restarting the phone and opening the game right when Android loads the game works, but most of the time it just gets a black screen. Does anyone have an idea how to resolve this? Oneplus support blames Riot and Riot support blames Oneplus
Click to expand...
Click to collapse
Same here After auto update need to downgrade to android 12
last time before update need restart and force open wild rift then can play
did u find how to fix?
tired already to downgrade to android 12
SyafiqFyllows said:
Same here After auto update need to downgrade to android 12
last time before update need restart and force open wild rift then can play
did u find how to fix?
tired already to downgrade to android 12
Click to expand...
Click to collapse
unninstall "app enhancement service" (package com.oplus.cosa) and reboot via ADB!