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
Related
My brother's galaxy note have been facing serious sod problems since he bought the phone at Nov 2012. After he faced it the 1st time , he sent to SC and got it back. After 1-2months the problem came again and he asked for my help. I persume it was because the malaysian firmware of the ICS was somewhat unstable from what i read from forums here and there. So i changed the firmware to JB duno from which country when it came out in MAC. After a week or so. The problem reappeared . So I just decided to root and chnge the kernel and also the ROM. Changed the ROM to a stock rom and a kernel. Still the problem persist. I'm out of options. Went to the ****ty SC and the idiots just factory reset the phone and give u back. BUNCH OF RETAR*S . (sorry for my languange)
Hope someone here may help me out with my problem. Thanks a million :laugh:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
abhinav quietly brilliant said:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I just installed an aosp rom (PA) and I hope it fixes the problem. Well I've seen the amount of apps installed in the note and its jst a quarter the amount I have in the Galaxy S2 and my S2 works like a charm. The note has been giving me headache ever since I got it from my brother. Hope this does solve it , if not I guess its something else maybe hardware
Phone sod twice on paranoid android. FML! Guess im visiting SC tmrw again.
Same problem with me..
My Note 1 has SOD since 1st time bought it..
be patience to install JB --> still SOD
change kernel to SpeedMod 5.3 --> SOD again
change kernel to PhilZ --> sometimes SOD
I have read many information that related with SOD in galnote 1, my opinion it is related with hardware too.. sometimes
or it is related with kernel... it can not wake from deep sleep..
anyone have another better suggestion to cure this ?
if u're using pure stock rom still facing the same problems then definitely is hardware issues!
if ur device still under warranties suggest bring to SC ask them do a thorough check on it n let them know what's going on actually...
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
psywarx said:
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
Click to expand...
Click to collapse
Yeah and they will give your phone back only doing a factory reset lol
Sent from my GT-N7000 using Tapatalk 2
I too get this SOD once a week on my GT-N7000
Phone status when this happens:
stock JB(earlier ICS), non-rooted, data connection, wifi, GPS, bluetooth all disabled. Battery mostly above 80%.
Gmail, Google+, Facebook and all other social n/w apps disabled (yes, i am an oldtimer )
During SOD, if a third party calls my number, he hears it ringing, but my handset is dead as dodo (quite dangerous as the calling person may think i am not answering it)
i used to get this when it was on ICS and still getting it after i upgraded to JB.
Most of the time, SOD occurs during wee hours in morning ( i used battery monitor app that logs battery stats every 10 minutes to check the time when this happens).
Sometimes it occurs when the phone is in my jeans back pocket. phone needs a 10 second press on pwr switch to restart it.
Turning off the "power saver" mode seem to reduce the probability of SOD.
i have taken this phone to SC and they re-flashed the JB.
i told the SC chap that i have already done this and couple of factory resets, but he said that they do "much more" than just re-flashing through kies like calibrating camera, bluetooth )
does anyone in the know, know if this is indeed true ?
Thanks
-mprab
updates...
After 2 days of re-flashing at a samsung authorised service center, i got SoD 2 times in a period of 12 hours.
once last night and second time when i was traveling to office.
Last night i installed some bare-minimum apps back after waiting 2 days for any SoD to happen in "stock" condition.
Well.... i did not pay 30K to use the GNote as just a phone, so installed some basic apps (Battery monitor, Bangalore BMTC, RealCalc, GPS Test, ES File explorer and a first time app StatusLogger)
phone went dead at 1:00 am in morning and as usual there was no wakeup alarm.
phone was warm to touch when it was lying dead. The battery which was 96% at 00:30 AM had gone down to 54% at 7:00 AM.
Status logger did not show any loss of GSM signal which might have resulted in phone transmitting at higher power/hunting for signal etc.
The "radio" seemed working, because when i made a call to the dead phone from my landline, i could hear the phone ring instead of expected "phone is switched off" message i was expecting.
So this has to do with application processor going in some infinite loop.
Uninstalling all apps is NOT an option.
anyone know if we can establish any debug connection to phone and know what the hell CPU is up to in this situation ?
any processor logger that will periodically log all the processes running on phone ?
SOD resolved... not a single one since 6 months.
Hey guys, just wanted to share this info with you, I had SOD's like anything and did all freakingly possible things right from flashing roms to kernels, speed up CPU, banging my head in front of the dumb witted morons at samsung service... to get rid of that pain. What helped me was an app called "WAKELOCK" by darken which is merely 72kb in size but works wonders, not a single SOD after that. What u need to do is.... it has a list of presets that makes sure your cpu stays up. You need to select the preset called "partial wake lock" which is at no. 4, and viola...
It ensures that the CPU is running. No SOD ever after. Also, you need to make it autorun on boot from the options. Yea, it does eat up batter a bit more but its definitely manageable. I still need to charge my note only at night.
Just to be sure, I uninstalled it and guess what, SOD returned. So, do try it, I hope it helps...
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.
so I have a k20pro device (chinese rom, imported from china), bought it last year. I worked fine at first. However when I tried to upgrade it to MIUI 10 (chinese rom). It got freezing and blackscreen. the store said it was the screen problem and suggest screen replacement. I refused due to the high price. Then I just put the phone there until today, after 8 month I open it and upgrade to UI11 and it is working better. it still has freezing but no permanent black screen.
is that the software or hardware issue?
You already Fix this problem dude? I have the same problem
killer!os133 said:
You already Fix this problem dude? I have the same problem
Click to expand...
Click to collapse
I have same problem did anybody fixed it yet
Guys im 90% sure its hw issue, i had touchscreen issues till i got new screen. Sometimes when i wanted to check what time is it and unlock my phone, touchscreen wasnt responding till the moment when the touchscreen was completly dead. I think many k20s has some touchscreen issues, but for the price its worth it.
It is a software issue. It started after the upgrade to MIUI 12 and it mostly happens when I use the Uber app. I usually have to restart the device. It is not a hardward issue. I think it should be solved after the next update.
theoluwapelumi said:
It is a software issue. It started after the upgrade to MIUI 12 and it mostly happens when I use the Uber app. I usually have to restart the device. It is not a hardward issue. I think it should be solved after the next update.
Click to expand...
Click to collapse
Damn im confused
Hey, I got the same issue with my K20 pro. And clearly ts not software issue.
I tried many things, Searched many sites.
All k20 pro user whether are on miui 10 or 11 or 12 experiencing this problem.
my worst luck is i m still under warrenty but i got a little crack on my phone within 10 days of purchase, it has been 10 month since than. my phone was working fine and suddenly i am experiencing this issue. my phone is completely blank now. Service center not taking it under warrenty since it broke.
anyone know the actual issue, call or whatsapp me please on 8005808844 and let me know how to fix it
Was about to put it as a [Question] but decided to place it as possible troubleshoot and experience for anyone with same problem.
Damn, was not expecting this and out of the blue.
I used my mi11ultra normally today, on Xiaomi.eu 12.5.11.0.
I order from Uber, while i waited, was playing asphalt 9. Then poof, lost my wifi connection. Could use mobile data.
At 30% battery remaining.
Couldn't connect to wifi and decided to reboot my phone.
For a few tries turning on wifi reboots my phone after freezing for a few seconds.
Sometimes it doesnt even turn on(no blue icon)
Turn off phone and let the heat dissipate. it's not hot today, and im using FHD res at 120hz, also haven't been playing for a long time, maybe 30minutes.
Tried restart i wiped daivilk and art cache on twrp.
Tried updating just now to 12.5.12.0 , nothing.
Tried Reset Wifi, bluetooth and mobile, nothing.
It lets me, sometimes, enable wifi, search for networks, connect and the wifi shuts down after about 5 seconds.
Right now as i was writing this and decide charged the phone so i could factory wipe. Im at 60% battery and the issue is gone for now.
I posting BOLD on battery comment because i found it that that was the issue oddly enough.
I'm charging the phone till 100% and will let you know if it happens again. "i hope i don't jinx it."
My greatest fear is that i would have to send it to repairs which takes time.
I Jinxed it . Going to Factory reset.
Watched abit of Netflix and then suddenly it freezed the phone and rebooted automatically.
EDIT: It's a faulty wifi module... Have to send it for repairs
xwonic said:
I Jinxed it . Going to Factory reset.
Watched abit of Netflix and then suddenly it freezed the phone and rebooted automatically.
EDIT: It's a faulty wifi module... Have to send it for repairs
Click to expand...
Click to collapse
Was it a Chinese version or global originally?
Chinese
speedtripler said:
Was it a Chinese version or global originally?
Click to expand...
Click to collapse
Chinese version. I even flashed original stock Chinese rom 12.5.12.0 and locked bootloader and it freezes and reboots itself when using wifi or bluetooth.
xwonic said:
Chinese
Chinese version. I even flashed original stock Chinese rom 12.5.12.0 and locked bootloader and it freezes and reboots itself when using wifi or bluetooth.
Click to expand...
Click to collapse
Sounds like it might be a hardware issue if it persists across all ROMs
Do you have a warranty to get a free fix ?
speedtripler said:
Sounds like it might be a hardware issue if it persists across all ROMs
Do you have a warranty to get a free fix ?
Click to expand...
Click to collapse
It had warranty, yes, and it was the Wifi module but ultimately i decided to get a refund.
Curiously i read it's a Mi 11 Series issue, if you decide to search in google "mi 11 wifi issue".
So i have to say farewell to Mi 11 Ultra Community.
My decision was done with several annoyances from Xiaomi and not for the hardware itself, all the crazy features and camera are badass.
Lack of optimization,
Missing gestures navigation with different launchers(which other manufactures already fixed long time ago in android 11...)
Generic updates(same changelog for all devices) and lack of transparency.
I still advise my friends and family to get a Xiaomi device for what they get for the price and i keep getting impressed by the hardware in these devices.
Also love the ecosystem and new features being added every MIUI version.
I got a POCO M3 with Android 10 Xiaomi.eu, that works gesture navigation and doesn't need third party apps.
I think it all comes down to software, because in the hardware department there isn't any complain from me.
I might even get a Poco X3 Pro for 170€ for a secondary device and install some AOSP rom there.
This decision might change in the future since Xiaomi said they are implementing a team dedicated for software issues, but not to this device.
Until then goodbye
Just my opinion,
seems like all hardware issues are happening to people who flashed non stock rom's.
Fingerprints before, and now wifi and Bluetooth.
Glad I am with global version and stock rom (tried .eu for a while and found it garbage). fingers crossed to stay happy
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(