Android Pay not working in London underground/buses/tfl after Nougat update - UK Only - OnePlus 3T Questions & Answers

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.

Related

Freezing all the Time...

I've been using Incubus26Jc's Froyo v. 12 and My Vogue has been freezing over and over all the time. Seems not to be app specific, and seems to happen when its charging and when its on battery.
Any chance I've got a setting wrong? My guess is that my phone is dieing. Any advice?
I've had this problem on the earlier versions, but now on release 12, I have only had 2 freezes... Sometimes you just have to let the phone sit. I guess it kinda gets overwhelmed and needs a little rest :/
Is my situation the same? I'm running SagaROM Froyo Ultralite [v1.2.1, 7/28/10] and every time the screen goes to sleep and goes into lock mode, it reboots. What can I do to fix this? Please & thank you!
deltagamer said:
I've had this problem on the earlier versions, but now on release 12, I have only had 2 freezes... Sometimes you just have to let the phone sit. I guess it kinda gets overwhelmed and needs a little rest :/
Click to expand...
Click to collapse
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
evilclosetmonkeynate said:
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
Click to expand...
Click to collapse
Try going back to RLS10.5 with the 15-07-2010 version of Zimage. That eliminated the freezes for me. And it seems a lot faster.
evilclosetmonkeynate said:
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
Click to expand...
Click to collapse
Try going back to RLS10.5 with the 15-07-2010 version of Zimage. That eliminated the freezes for me. And it seems a lot faster.
Thanks @richardk3 ... I have the NBH, but I didn't save the 10.5 install file. Anyone have a link?
Update: Searching the forum didn't find it but a Google Search did: http://www.mediafire.com/?ond2tmmzolggtmm
If you search the main Froyo thread, incubus put up a link to the archive of recent releases.
I went back to RLS10.5 and the 7/15 zImage per richardk3's suggestion. At first I did notice less freezing and overall better performance. But then I made a long call (over 5 min) with BT headset and the phone became unresponsive. BT and the call were still working fine, but the phone was unresponsive and had to be reset at the end of the call.
This is pretty consistent across all builds in Eclair and Froyo. I've reached the point where I basically accept that this is always going to happen and I'll need to reboot. It's worth the trade-off, though, since this build is so amazing and Android is so much better than WinMo.
Johndixon, if you're running from nbh then you may need to clear the dalvik cache from the boot screen menu. Worked for me when the freezes came fast and furious.
jstrom23 said:
I went back to RLS10.5 and the 7/15 zImage per richardk3's suggestion. At first I did notice less freezing and overall better performance. But then I made a long call (over 5 min) with BT headset and the phone became unresponsive. BT and the call were still working fine, but the phone was unresponsive and had to be reset at the end of the call.
QUOTE]
I'm having the exact same problem... always becomes unresponsive at the end of the call when using Bluetooth. I've tried combinations of RLS10.5 and RLS12, and a couple of zImages.
Other than this, it's super fast and stable... But it would be great to figure out what is causing the freezing.
Click to expand...
Click to collapse
eugene2007;7515857
I'm having the exact same problem... always becomes unresponsive at the end of the call when using Bluetooth. I've tried combinations of RLS10.5 and RLS12 said:
I'm having the same problem without using Bluetooth.
Can you gather the debugging info that DZO needs, as described here:
http://208.100.42.21/showthread.php?t=712310&page=180
Click to expand...
Click to collapse

Is it possible to turn off the warning for battery 30 %?

IF there is something I really don't need then it is to know that there's about 1/3 of the power left in the battery! I would like to stop that warning, but I can't find anywhere to do that. Is it possible, or is it a quirk I'll have to live with on this phone? They all have some quirks, just in different areas.
Mastiff said:
IF there is something I really don't need then it is to know that there's about 1/3 of the power left in the battery! I would like to stop that warning, but I can't find anywhere to do that. Is it possible, or is it a quirk I'll have to live with on this phone? They all have some quirks, just in different areas.
Click to expand...
Click to collapse
And the warning is so loud.. I have reported this to Sony so I hope they will change it
Sent from my F8131 using XDA-Developers mobile app
Yeah, hope is always eternal, but I'm afraid that's not likely, since the accelerometer problem (which means that the screen won't follow the phone's direction, but stay in portrait mode) hasn't yet been fixed several months after the first reports. So the best would be if it was possible to fix through an app with a rooted phone or something like that.
Mastiff said:
Yeah, hope is always eternal, but I'm afraid that's not likely, since the accelerometer problem (which means that the screen won't follow the phone's direction, but stay in portrait mode) hasn't yet been fixed several months after the first reports. So the best would be if it was possible to fix through an app with a rooted phone or something like that.
Click to expand...
Click to collapse
That one is fixed... Have you not yet received the nougat update?
Sent from my F8131 using XDA-Developers mobile app
I am on Nougat from about a week ago (Telenor for Norway), and it is most definitively not fixed, at least not in this phone. The phone doesn't rotate at all except for when I use an app, Screen rotate.
Mastiff said:
I am on Nougat from about a week ago (Telenor for Norway), and it is most definitively not fixed, at least not in this phone. The phone doesn't rotate at all except for when I use an app, Screen rotate.
Click to expand...
Click to collapse
I am on beta and it worked from day one here.
I guess you should try a software reset.
Sent from my F8131 using XDA-Developers mobile app
How about three resets in two days? I bought the phone a week ago, after years of Samsung. Took me days to figure out how to root, and in the meantime it had upgraded itself to N because I didn't see what I clicked on (eye operation makes it a bit difficult these days). So I got it downgraded to MM, reset it, backed up the TA files, upgraded to N again, reset it and activated USB debugging for Flashtool, unlocked the bootloader, reset it again and finally set it up the day before yesterday. So I seriously doubt that another rest would change much.
Edit: Oh, and it may be different from phone to phone. According to your sig you do not have the same phone as me.
Mastiff said:
How about three resets in two days? I bought the phone a week ago, after years of Samsung. Took me days to figure out how to root, and in the meantime it had upgraded itself to N because I didn't see what I clicked on (eye operation makes it a bit difficult these days). So I got it downgraded to MM, reset it, backed up the TA files, upgraded to N again, reset it and activated USB debugging for Flashtool, unlocked the bootloader, reset it again and finally set it up the day before yesterday. So I seriously doubt that another rest would change much.
Edit: Oh, and it may be different from phone to phone. According to your sig you do not have the same phone as me.
Click to expand...
Click to collapse
I have not updated my signature...I have the xp.
It is quite funny as all I know of have gotten their screen rotation fixed with the software update. I guess you are unlucky... Which nougat firmware have you installed?
Sent from my F8131 using XDA-Developers mobile app
I see. So it's the map not fitting the terrain.
Well, maybe I should try yet another reset. I have Titanium, so it's quite easy to get back to where I am now if it doesn't help. I have F8131_Telenor Mobil NO_1303-3350_39.2.A.0.361_R7C
So I did. Reset, and didn't do anything but log into my Google account. When I got through the setup process there was no rotation at all. Then I started thinking. Could it have anything to do with the rooting? I use TWRP and the ANdroPlus kernel, and I checked the AndroPlus website. Turned out that they had a new kernel out just yesterday, and the note got me thinking:
v19
Add support for 39.2.A.0.361
Click to expand...
Click to collapse
That was the number on the firmware I'm using. So I flashed that, and bingo! Now I'm rotating! Well, at least my screen is, I don't even dare to think about rotating after yesterday's celebration. Keywords: Crayfish and shrimps, duck breast and chocolate mousse, followed by as many beers as my 50 year old body can take. And that's quite a lot! So today is not my most productive day this year... But thanks for getting me on the right track, if you knew it or not!
Edit: There's a new TWRP recovery as well for the phone, 3.0.3.0, dated a couple of days ago.
Mastiff said:
So I did. Reset, and didn't do anything but log into my Google account. When I got through the setup process there was no rotation at all. Then I started thinking. Could it have anything to do with the rooting? I use TWRP and the ANdroPlus kernel, and I checked the AndroPlus website. Turned out that they had a new kernel out just yesterday, and the note got me thinking:
That was the number on the firmware I'm using. So I flashed that, and bingo! Now I'm rotating! Well, at least my screen is, I don't even dare to think about rotating after yesterday's celebration. Keywords: Crayfish and shrimps, duck breast and chocolate mousse, followed by as many beers as my 50 year old body can take. And that's quite a lot! So today is not my most productive day this year... But thanks for getting me on the right track, if you knew it or not!
Edit: There's a new TWRP recovery as well for the phone, 3.0.3.0, dated a couple of days ago.
Click to expand...
Click to collapse
Hilarious ??? good that it worked out for you.
I am glad for the info as it then was kernel related.
Sounds like you had a great time last night. I hope you get a great year to follow ?
Enjoy your rotating Xperia ?
Sent from my F8131 using XDA-Developers mobile app
I have so say that I hope for a great year too, but it may be an intersting one!
Oh, and found out that it wasn't the kernel after all. It was regular rooting with SuperSU that broke the rotation, so now I'm trying the systemless root from phh. I'll let you now if that works, just to complete this part of the thread (which is really so off the original topic that it should have been split to another thread!).
Mastiff said:
I have so say that I hope for a great year too, but it may be an intersting one!
Oh, and found out that it wasn't the kernel after all. It was regular rooting with SuperSU that broke the rotation, so now I'm trying the systemless root from phh. I'll let you now if that works, just to complete this part of the thread (which is really so off the original topic that it should have been split to another thread!).
Click to expand...
Click to collapse
Thanks man.. I have rooted a lot in the past but I don't want to unlock my bootloader anymore... Back in the days when phones were slower it made sense to root and mess with the config and custom roms.. But today... Not much, what is the reason to why you are rooting?
Sent from my F8131 using XDA-Developers mobile app
I root for two main reasons:
1. You can't do a really good backup in any other way than with Titanium backup, and I like to start semi-fresh every now and then when there's been too much bull tested and tried on the phone.
2, and this is the real kicker: For some idiotic reason a non-rooted Android phone can't do AirPlay in any way. I have a whole-house system that incorporates streaming over WiFi from my phone, and if I don't root, I can't use any of the streaming apps that support AirPlay (my favourite is AirAudio) to stream audio from whatever app I want to, since it can stream the actual phone audio. DLNA is totally useless because I have to use particular apps to stream with that, and they are not the apps I actually use. So basically Google has with a rather dumb choice forced me to root.
Mastiff said:
I root for two main reasons:
1. You can't do a really good backup in any other way than with Titanium backup, and I like to start semi-fresh every now and then when there's been too much bull tested and tried on the phone.
2, and this is the real kicker: For some idiotic reason a non-rooted Android phone can't do AirPlay in any way. I have a whole-house system that incorporates streaming over WiFi from my phone, and if I don't root, I can't use any of the streaming apps that support AirPlay (my favourite is AirAudio) to stream audio from whatever app I want to, since it can stream the actual phone audio. DLNA is totally useless because I have to use particular apps to stream with that, and they are not the apps I actually use. So basically Google has with a rather dumb choice forced me to root.
Click to expand...
Click to collapse
The Xperia backup does the trick for me... It saves data so I have a complete backup.
The second makes good sense, I don't use apple so I don't know the problem but hope it will work out in the future mate ?
Sent from my F8131 using XDA-Developers mobile app
Doubful. It's a proprietary Apple system so they won't support it in Android, and from what I've heard that's why they make it as difficult as possible to support it, so root is necessary. Anyway, I'm good with that, as long as I get root. It took me some days, but Sony's a new thing to me. Still love that ability to work with a wet screen. Samsung really has a problem there.
I only get the warning at 15%, this is where I set the auto stamina to notifiy me when stamina kicks in.
How weird. I have turned off that bull totally, don't need it. I'm never that far from a charger, in my boat, car, house or motorcycle. So no stamina mode at all, still it wines at 30 %.
Mastiff said:
How weird. I have turned off that bull totally, don't need it. I'm never that far from a charger, in my boat, car, house or motorcycle. So no stamina mode at all, still it wines at 30 %.
Click to expand...
Click to collapse
try setting auto stamina at 15%, it's the lowest you can set, and see if the 30% will stop.
Good point, I'll try. I seldom let the battery go so low, while 30 is not that uncommon. I'll try and see what happens later today, thanks!

RP2-specific fixes/updates with 9.0 update?

To those who have updated to Android 9.0, have you seen any improvements/fixes specific to the RP2? I know many of us have noted issues with the speakers (notably at lower volumes) and the camera software (mostly fixed by using Gcam), although there's been other more isolated/random issues for some too (Bluetooth, cellular signal, etc).
I haven't done extensive testing, but I do nelieve the small issues I've had with the speakers at low volumes are fixed. The only issue that I've seen in the last couple days I've had pie is that my wifi will randomly stop being able to access the internet, but turning wifi off and on fixes it and mostly a minor inconvienence. It's probably worth noting that I have Magisk with many modules installed.
Hangouts doesn't give a notification sound when the app isn't open. I've made another thread about that earlier
------------------------------------------------------------------------------
Never mind. Had to go deep into Hangouts settings to fix it. Still annoying
I would willingly trade fully functional wifi for speakers that don't crackle and cut out at lower volumes, since I have unlimited data and solid LTE signal everywhere I go. Though I've had that wifi issue on rare occasion on Oreo too.
They moved the clock :'(
Anyone notice potential decrease in touch sensitivity after the upgrade? I had a screen protector on and it seemed like I need to push down a little more to get the touches to register. Took off the protector to test and it was fine with just the screen. Put another one on and occasionally touches aren't registering or registering but releasing early on swipes.
Sent from my Phone 2 using Tapatalk
CalebQ42 said:
I haven't done extensive testing, but I do nelieve the small issues I've had with the speakers at low volumes are fixed. The only issue that I've seen in the last couple days I've had pie is that my wifi will randomly stop being able to access the internet, but turning wifi off and on fixes it and mostly a minor inconvienence. It's probably worth noting that I have Magisk with many modules installed.
Click to expand...
Click to collapse
How do you unlock your bootloader, bro? How did you root your phone?
acegrace said:
How do you unlock your bootloader, bro? How did you root your phone?
Click to expand...
Click to collapse
Follow the guide here, it's what I used to get everything under way. As long as you didn't install the latest OTA that dropped last week.
https://forum.xda-developers.com/razer-phone-2/how-to/root-pie-guide-t3910407
Gamesoul Master said:
Follow the guide here, it's what I used to get everything under way. As long as you didn't install the latest OTA that dropped last week.
https://forum.xda-developers.com/razer-phone-2/how-to/root-pie-guide-t3910407
Click to expand...
Click to collapse
crap, i just updated last night - can i factory reset and do the same thing?
alawiggle said:
crap, i just updated last night - can i factory reset and do the same thing?
Click to expand...
Click to collapse
Nah, you're good now. Warrior's thread (which the post I gave you directly references) has the updated boot image for MR1 (which is what you're on now), so just use that and you should be fine.
Oh! And turn off any unlock security (PIN, fingerprint, etc) you may have on before doing it. Just to be safe. You can turn it all back on when you're done rooting.
Gamesoul Master said:
Nah, you're good now. Warrior's thread (which the post I gave you directly references) has the updated boot image for MR1 (which is what you're on now), so just use that and you should be fine.
Oh! And turn off any unlock security (PIN, fingerprint, etc) you may have on before doing it. Just to be safe. You can turn it all back on when you're done rooting.
Click to expand...
Click to collapse
nice, thanks!

Phone freezes after Android 10 Install

On my Verizon Note 9, not rooted. Holding down the power button doesn't help. I have to hold the power and vol down key to reboot phone.
Has anyone else had this issue, or have a solution?
Try booting into Recovery Mode and wipe the cache partition. If that doesn't work. Then I would manually reinstall the stock OS back onto your device as there is a chance something went wrong during the OTA installation process.
n960f exynos, im also experiencing random freezes after android 10 update. Once-twice a week. First screen doesn't show any updates, but i can feel haptic feedback, so i presume everything works underneath freezed screen, and shortly after that phone freezes completly( with screen still on) , only holding down power for 30sec seems to helps.
Unfortunately clearing cache nor fresh odin flashing of full firmware helped. I noticed it is happening while phone is warm from charging or just plain using.
wodzini said:
n960f exynos, im also experiencing random freezes after android 10 update. Once-twice a week. First screen doesn't show any updates, but i can feel haptic feedback, so i presume everything works underneath freezed screen, and shortly after that phone freezes completly( with screen still on) , only holding down power for 30sec seems to helps.
Unfortunately clearing cache nor fresh odin flashing of full firmware helped. I noticed it is happening while phone is warm from charging or just plain using.
Click to expand...
Click to collapse
N960u, not a single issue with 10. Been using it since beta. So maybe the exynos version has bugs
Nope, Op has a Verizon phone...
That's US only isn't it?
Maybe Canada...
My Exynos Note 9 hasn't had any problems since I updated to 10 either but then again, different set-ups may cause different issues...
ultramag69 said:
Nope, Op has a Verizon phone...
That's US only isn't it?
Maybe Canada...
My Exynos Note 9 hasn't had any problems since I updated to 10 either but then again, different set-ups may cause different issues...
Click to expand...
Click to collapse
I'm in the US (Michigan), and have a snapdragon version.
So the question is, anyone with an Exynos Chipset experiencing the same problem as this may indeed be a Snapdragon related problem( with this, admittedly limited, sample it seems so)...
ultramag69 said:
So the question is, anyone with an Exynos Chipset experiencing the same problem as this may indeed be a Snapdragon related problem( with this, admittedly limited, sample it seems so)...
Click to expand...
Click to collapse
Maybe. All I know now is I'm beginning to regret updating. At first my phone was fine. But after a few days, it's sluggish. And to let me know it's not just an isolated problem, my wife's S-9 (on a different carrier) has begun to experience the same issues as my Note 9.
I swear, if it wasn't for the S-pen, I'd have gone over to Apple by now. Android is just one headache after another.
Kamau54 said:
Maybe. All I know now is I'm beginning to regret updating. At first my phone was fine. But after a few days, it's sluggish. And to let me know it's not just an isolated problem, my wife's S-9 (on a different carrier) has begun to experience the same issues as my Note 9.
I swear, if it wasn't for the S-pen, I'd have gone over to Apple by now. Android is just one headache after another.
Click to expand...
Click to collapse
You can just downgrade back to pie it's not that big of deal.
wodzini said:
n960f exynos, im also experiencing random freezes after android 10 update. Once-twice a week. First screen doesn't show any updates, but i can feel haptic feedback, so i presume everything works underneath freezed screen, and shortly after that phone freezes completly( with screen still on) , only holding down power for 30sec seems to helps.
Unfortunately clearing cache nor fresh odin flashing of full firmware helped. I noticed it is happening while phone is warm from charging or just plain using.
Click to expand...
Click to collapse
Well.. After march security updates, random freezes stopped.

Question Are there people without ramdump?

today i've bought my new zenfone 8, i was leaving a xiaomi mi 10 because of proximity sensor problems and miui instability.
read lots of reviews about zenfone 8 and all were enthusiasts... today after buying it i found a first post about ramdump, since today afternoon i've read lots of posts....
i've seen my phone is 04/21 MFD....
will it die? are there people wich had this phone (04/21 batch) without problems? searching around in forums seems that anyone sooner or later had the problem... so the phone is in the box and i don't know if i will return it or keep it... give me a little trust in this phone
Do you like to play Russian Roulette?
If you open the box you will have to.
I have phone of same batch 04/2021 and had ramdump once. But I easilly quit it with keys combo. I do not know why it works for some but not for others.
so there are people who never had problems?
cause i could see 30 people having problems, but i'd like to know if are 30 people on 50 or 30 people on 1000, it would be a big difference
Mine is mfd 04/2021 and I still have no problems
There is 35 confirmed cases of this issue and it might not be the same issue as Ramdump is just something zenfone 8 falls back to when there is a problem with the phone. Who knows how many (tens of thousands) people are there without any issues.
I would say relax and enjoy your phone. Don't unlock the bootloader so you don't lose the warranty, but other than that just use it normally.
I just checked and I also have MFD 04.2021. I never had any problems (not that I am aware of) so I never bothered to check before. Does the problem only happen on certain devices? I have the basic version with 8 GB RAM and 128 GB ROM. Happy customer so far.
EDIT: I am running stock firmware, if that matters. Haven't altered anything (yet).
Used it for more than 4 months without problems (bootloader unlocked).
With Lineage 18.1, it worked great for a day, maybe even less. Now I get at least a couple ramdumps every day.
How do one check MFD?
[email protected] said:
How do one check MFD?
Click to expand...
Click to collapse
It is written on the box
Undead_Son said:
Used it for more than 4 months without problems (bootloader unlocked).
With Lineage 18.1, it worked great for a day, maybe even less. Now I get at least a couple ramdumps every day.
Click to expand...
Click to collapse
The problem in the official forum is a "one time" thing, if you get the "waiting for flashing full ramdump", its bricked and you can't do a thing, beside sending it in.
On my brand new ZenPhone 8 running Lineage for Microg 8.1 October 7th version I'm getting the ramdump screen, but only under specific circumstances:
1. not connected to wifi/wifi off
2. on a call
3. have headphones plugged in to the jack
it almost always crashes within 20 seconds. If any of those conditions are not met it works fine (or at least appears to so far). I've tested this ~8 times in a row with all other (known) variables remaining constant.
When it crashes, pressing power for ~15 seconds shuts it down, and it can then be started normally. I hope this helps anyone else e countering the same problem.
Someone had this ramdump issue on unlocked bl but on stock rom? Especially with at least some magisk mods?
MasterWoju said:
Someone had this ramdump issue on unlocked bl but on stock rom? Especially with at least some magisk mods?
Click to expand...
Click to collapse
Yes! My first time with this issue. Never before.
I'm on the lastest Android 12 stock rom (UL-ASUS_I006D-ASUS-31.1010.0410.72-1.1.25-2204-user).
- Unlocked BL
- Rooted with Magisk 23
- Kirisakura_Sake_S_2.0.1 flashed with EXKM
- Only one Magisk module (Font_Manager-v5_6_4-117)
I was playing a game (Zombie Tsunami ). I got my screen freezing, ... dark screen and ramdump issue.
Edit: My MFD is 05.2021
I have too MF 4.2021 - using since 5-2021. I'm very happy with this phone. For all this time I'v got only landscape bug on video - fixed with OTA update.
I'm using stock soft - Android 12 31.1010.0410.72

Categories

Resources