Looking for help on this one. Every 3-5 days my Ultra gets into a state where no voice can be heard by either myself or the person on the other phone when a call is made or received, but I can hear the ring tone if I'm calling prior to the person answering, and my phone rings as normal if someone calls me. But when answering the call it's just silence on both sides. A reboot fixes this only for it to happen again 3-5 days later, requiring another reboot.
At first I assumed it was a corruption of the rom I had installed, so I flashed back to my stock image with Odin, including a fresh VOD CSC install. Unfortunately, it's still happening after this. Speaking as an engineer, it's unusual but not unheard of for a device to have a hardware issue of this type and it be rectified each and every time with a reboot, that would normally point to a software/firmware error of some sort. However, the fact it's continuing to happen after a completely fresh re-flash of stock Android suggests my worst fears that it is hardware. I could try some things, like not installing Magisk or even re-locking my bootloader, but I don't believe either would be a factor. I only used Magisk for rooting and don't install additional modules. I've also ruled out the sim card or sim slots by swapping to an e-sim, only for it to still happen.
Anyway, any suggestions would be welcome, especially if you have suffered something similar. There is an easy fix, which is to schedule a reboot every morning at around 3am, but I'd sooner not have to do this before working out what the underlying cause is.
I don't have a solution for you but I just wanted to share that I am having the same issue. But I'm not using Magisk and not unlocked, or rooted. The only thing I did was flash stock Samsung and disable some bloat.
I was having the issue the other night (for the second time) when calling my carrier (AT&T) about an order. I just assumed it was them at first. I disabled wifi calling (after them not hearing me several times) then tried again and it worked.
Were you using wifi calling at the time? I haven't been able to reproduce the issue yet so I don't know if disabling wifi calling had anything to do with it working.
Just to clarify, you say you're using Magisk but you're not unlocked or rooted? That isn't possible, but perhaps you just worded it wrong and you meant you're not using Magisk.
Funny you should mention Wifi-Calling, when it happened a few weeks back I force closed Wifi calling in an attempt to track down any potential services that might be causing the problem. And when I did that the calling started working again without a reboot. I thought I'd tracked it down and thought I'd test it again once it happened again a few days later, I would then freeze wifi-calling (something I never use) which would hopefully stop it ever re-occurring. However, the second time I force stopped wifi-calling it didn't fix the issue.
Beefheart said:
Just to clarify, you say you're using Magisk but you're not unlocked or rooted? That isn't possible, but perhaps you just worded it wrong and you meant you're not using Magisk.
Funny you should mention Wifi-Calling, when it happened a few weeks back I force closed Wifi calling in an attempt to track down any potential services that might be causing the problem. And when I did that the calling started working again without a reboot. I thought I'd tracked it down and thought I'd test it again once it happened again a few days later, I would then freeze wifi-calling (something I never use) which would hopefully stop it ever re-occurring. However, the second time I force stopped wifi-calling it didn't fix the issue.
Click to expand...
Click to collapse
I missed a word when I first replied. I added "not" to Magisk but you must have seen it before I fixed it.
I've had many work meetings (on phone) since then and haven't had it pop up. I haven't changed anything and even have wifi calling back on, so I'm at a loss.
OK, traced this to possibly be linked to the attached logcat. Any suggestions?
Also, contrary to my claim in the opening post, the dial tone can only be heard sometimes.
An additional oddity, whilst the fault is occurring (prior to a reboot), voice calls on WhatsApp work fine.
Perhaps a form of modem fault?
I give up on this. I flashed the stock VOD rom in Odin and relocked the bootloader to take it as close to stock as possible (minus the knox flag being tripped which is unavoidable at this point) and it still showed the issue after a couple of days. I've also disabled Bluetooth at a service level to no avail as I thought it might be a glitch with that.
It's clearly a hardware issue that will only be resolved with a logic board replacement. Which currently aren't available.
One good thing is that a full reboot isn't required to fix it, a soft reboot seems to do it. So I've got a link to do that on my home page, only takes 10-15 seconds.
Beefheart said:
OK, traced this to possibly be linked to the attached logcat. Any suggestions?
Also, contrary to my claim in the opening post, the dial tone can only be heard sometimes.
Click to expand...
Click to collapse
Hi, sorry to re-open this old topic. My S21 has the same problem from the beginning, but I have the stock rom. Did you get this log using *#9900# tool? Which log level did you use? Which file is the attached one? BTW, I'm almost sure that it's an hardware failure, did you solve it? Thanks
nrg84 said:
Hi, sorry to re-open this old topic. My S21 has the same problem from the beginning, but I have the stock rom. Did you get this log using *#9900# tool? Which log level did you use? Which file is the attached one? BTW, I'm almost sure that it's an hardware failure, did you solve it? Thanks
Click to expand...
Click to collapse
I'm afraid not, I ended up selling it as parts or repair a few weeks after that post.
Beefheart said:
I'm afraid not, I ended up selling it as parts or repair a few weeks after that post.
Click to expand...
Click to collapse
Thanks anyway, I will try to bring mine to the repair center.
Related
Hey,
My AT&T rooted nexus one is still randomly rebooting if I use 3g data. I am in Costa Rica and the 3g is on the 850 band. I also have to add the apn "kolbi3g".
So basically I can use the phone for anything and it works great, but if I add the apn and start using the 3g heavily I will get a reboot, sometimes it will reboot vibrate 7 times and I have to pull the battery. I have tried 2.1 and 2.2 rooted and not also cyanogen 6 all the same problem.
If I do *#*#4636#*#* and select the wcdma only it runs the 3g better but reboots way more, sometimes the instant I place load on the connection. However if I select wcdma "unkown" the 3g works much better I can use it sometimes 30min at a time without a problem.
So any ideas what I could try? Is there a kernel that will up the volt's a bit just help stability? Or anything else I could try? Data roaming is off, I have tried both off and on, no difference that I can tell.
Thanks a lot this is driving me crazy! Just got this phone Sunday too sick to my stomach of the thought I spend $600 on this phone if I can't get 3g to work
How about radio image???
It is currently on baseband 4.06.00.12_7. Is there a more current radio?
I came across this multiple reboot issue on a (locked) Vodafone UK Nexus.
It booted into the OS (lockscreen) and as soon as data connected it looped back to the last couple seconds of the animated Nexus logo.... and again.... and again.
I powered down the unit (battery pull), booted into bootloader (voldown+power) and selected clear storage (voldown,voldown,power) then (volup) to confirm.
This deletes the user data and you have to sign in and set up the phone again but it certainly fixed the issue. My only guess is some user data became corrupt and the kernel panicked and forced a partial reboot.
Give it a try and lemme know.
Cabarnacus said:
I came across this multiple reboot issue on a (locked) Vodafone UK Nexus.
It booted into the OS (lockscreen) and as soon as data connected it looped back to the last couple seconds of the animated Nexus logo.... and again.... and again.
I powered down the unit (battery pull), booted into bootloader (voldown+power) and selected clear storage (voldown,voldown,power) then (volup) to confirm.
This deletes the user data and you have to sign in and set up the phone again but it certainly fixed the issue. My only guess is some user data became corrupt and the kernel panicked and forced a partial reboot.
Give it a try and lemme know.
Click to expand...
Click to collapse
Just did that (had the phone plugged into wall charger), and the second I got to the home screen it rebooted then vibrated like 6 or seven times. Seems to do it worse when it is plugged in. And now it won't even boot up even after pulling the battery, it vibrates 6-7 times.
I am really worried about this, any other ideas??? I will try anything! Thanks for the help
Update! Now the phone just reboot when I do anything period with it plugged in. Just like posted in another thread on this section!
Please any ideas I am very desperate and very sick to my stomach!
Hmmm very strange.
I'm aware from what you were saying on the other thread that you've got an unlocked bootloader and you're wondering what to do on the warranty front.
If you've really tried different combinations of stock and custom firmware and having the same issue I'm tempted to say its a hardware issue.
Many people have returned their unlocked phones with no comeback from HTC some have reported that they have noticed the unlocked bootloader and have issued a motherboard repair as part of the fix because of this.
Although im unsure of the additional cost (if any) i would definitely recommend going through the warranty repair route with HTC. They won't say no and send you back the same broken phone. And who knows, if its a confirmed hardware issue they may just replace it as a goodwill gesture.
Other than that I don't have any more ideas.
A nexus support thread has a popular answer referring to the clear storage fix.
http://www.google.de/support/forum/p/android/thread?tid=40f52d29e9c4177e&hl=en
Just make sure you are definitely clearing the storage FROM THE BOOTLOADER before calling HTC. It is the first thing they will make you do before accepting a return anyway.
Cabarnacus said:
Other than that I don't have any more ideas.
A nexus support thread has a popular answer referring to the clear storage fix.
http://www.google.de/support/forum/p/android/thread?tid=40f52d29e9c4177e&hl=en
Just make sure you are definitely clearing the storage FROM THE BOOTLOADER before calling HTC. It is the first thing they will make you do before accepting a return anyway.
Click to expand...
Click to collapse
Ok thank you so much sir. I am so glad to hear that I may still have a chance at getting it replaced! It was very fullish of me to unlock it, I know, it is just that I figured it was software and could be fixed by unlocking. It is going to cost me $$$ to get this to the States, but that is life. If I still can't get it to work I will call htc and let you know what they say
Little update here. I cleared storage again and just simply disabled data, I have been using the phone for a couple of hours on work without any problems. Next thong I am going yo yty is another friends 3g similar card and see if it still reboots on that sim, if it does then I am calling HTC.
Also still open to any other ideas you guys may have.
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
anibjoshi said:
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
Click to expand...
Click to collapse
upload it on youtube and post the link.
And something else. Make a factory reset again and then don't install any apps. Does the error also occure?
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
LibertyMarine said:
upload it on youtube and post the link.
And something else. Make a factory reset again and then don't install any apps. Does the error also occure?
Click to expand...
Click to collapse
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
anibjoshi said:
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
Click to expand...
Click to collapse
after seeing your video, I am even more confused. I really don't know what could cause this problem. But the fact, that I didn't have this issue and almost no other person too, makes me think about a hardware defect. But the randomness and that it only occures after several days don't support this theory. So the only thing we can do about his is basic troubleshooting.
- 1) Try to flash Cyanogenmod and try this mod for several days
- 2) Try another Rom, for example: Omni Rom
- 3) Try to use a different Kernel for GPE stock.
- 4) Use a RUU that matches for you
Sorry, I don't have any other ideas left! But after this troubleshooting we may get new information or gain some knowledge that allows us to determine the cause of this error more exactly!
anibjoshi said:
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
Click to expand...
Click to collapse
Try flashing a Sense ROM, like ARHD or MaximusHD?
Enviado de meu HTC One usando Tapatalk
LibertyMarine said:
after seeing your video, I am even more confused. I really don't know what could cause this problem. But the fact, that I didn't have this issue and almost no other person too, makes me think about a hardware defect. But the randomness and that it only occures after several days don't support this theory. So the only thing we can do about his is basic troubleshooting.
- 1) Try to flash Cyanogenmod and try this mod for several days
- 2) Try another Rom, for example: Omni Rom
- 3) Try to use a different Kernel for GPE stock.
- 4) Use a RUU that matches for you
Sorry, I don't have any other ideas left! But after this troubleshooting we may get new information or gain some knowledge that allows us to determine the cause of this error more exactly!
Click to expand...
Click to collapse
The original device shipped with sense Rom. I flashed GPE to check if it was a software fault. But no luck. It gave the same problem although significantly later(about a week after I flashed it).
One more thing, I hope this gives some more information..
One time, I had rooted the device and installed a custom recovery. The phone was then working perfectly for about 4-5 days. and then later when I went ahead and unrooted the device, it immediately started giving problems. So I rooted it again hoping that the problem will go away, but no luck...the problem persisted. So, I had no option than to factory reset again, at which point it started working perfectly again.
This is all so bizarre, I have never seen something like this happen
This is just a theory, but is it possible that there is a problem with the hardware which gets triggered only on certain conditions, like some interrupt, or flag or something like that?
So until those conditions are not met, the device runs perfectly, and when they are, it starts giving issues.
Thats all i can think of as the reason.
well its clearly something youre installing if it is occuring after a few days, a root app which controls your sensor or brightness probably, do you have apps of that nature?
IINexusII said:
well its clearly something youre installing if it is occuring after a few days, a root app which controls your sensor or brightness probably, do you have apps of that nature?
Click to expand...
Click to collapse
No I rooted the device but did not install any root apps...i unrooted the device to install the GPE Rom(not necessary i know, but it seemed like a proper way) and found that it started giving problems immediately. Can non-root regular apps also cause such problems? I had installed only a limited number of apps anyway, updated the pre installed apps, facebook, twitter, whatsapp, some games..thats it..nothing wierd..
Might be a Screen-Off max. frequency issue. Like the phone gets only 500Mhz in sleep mode at maximum. Which is to low for an incoming call. Could you install a app like Android Tuner or Trickster Mod to check your Screen-Off Max frequency. If it`s that low, set it to ~1000Mhz.
anibjoshi said:
The original device shipped with sense Rom. I flashed GPE to check if it was a software fault. But no luck. It gave the same problem although significantly later(about a week after I flashed it).
One more thing, I hope this gives some more information..
One time, I had rooted the device and installed a custom recovery. The phone was then working perfectly for about 4-5 days. and then later when I went ahead and unrooted the device, it immediately started giving problems. So I rooted it again hoping that the problem will go away, but no luck...the problem persisted. So, I had no option than to factory reset again, at which point it started working perfectly again.
This is all so bizarre, I have never seen something like this happen
This is just a theory, but is it possible that there is a problem with the hardware which gets triggered only on certain conditions, like some interrupt, or flag or something like that?
So until those conditions are not met, the device runs perfectly, and when they are, it starts giving issues.
Thats all i can think of as the reason.
Click to expand...
Click to collapse
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
LibertyMarine said:
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
Click to expand...
Click to collapse
Agreed, trying following the guide and if it doesn't work make it s-on and send it to HTC for them to give a look.
Sent from my HTC One
LibertyMarine said:
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
Click to expand...
Click to collapse
I will definitely follow your guide and try to troubleshoot the problem. I hope its not some hardware defect and I dont have to send the device to HTC. I've heard those guys are poor at customer service
Thanks a lot, you've been a great help!
Btw, I was trying to find that Thanks button since the first day, I just couldn't figure out where it was. I just did.
Thanks again
Yup try installing kernel and custom rom.
Remove the case and try ( i know this is stupid thing but can give it a try)
Jvov said:
Agreed, trying following the guide and if it doesn't work make it s-on and send it to HTC for them to give a look.
Sent from my HTC One
Click to expand...
Click to collapse
Thanks for your help buddy! I really appreciate it!
anibjoshi said:
I will definitely follow your guide and try to troubleshoot the problem. I hope its not some hardware defect and I dont have to send the device to HTC. I've heard those guys are poor at customer service
Thanks a lot, you've been a great help!
Btw, I was trying to find that Thanks button since the first day, I just couldn't figure out where it was. I just did.
Thanks again
Click to expand...
Click to collapse
Thanks ! That's awesome and gives so much motivation! If you find out that you have a hardware defect and that you have to send it to HTC, I'll give you some information how to deal with those guys that you get your warranty.
I'm running 4.3 rooted on ML2, stock ROM. Within the last week I started experiencing a strange problem - after every single phone call made or received, I lose all network connection for about ten seconds. I get the circle with the line through it. Going into settings shows actual connection drop, not just the icon. Then, the connection reappears. I've made no modifications since rooting it in April, nor do I recall removing or freezing any apps any time recently. Powering down and/or removing the battery has done nothing to help.
Any ideas what would cause this? I can't find any threads here, or through a google search, discussing this problem. Any help is appreciated.
Update - same problems when running in safe mode.
Well, this seems to have been a local network problem, as the issue has magically disappeared. Nothing exciting to report.
fullboogie said:
Well, this seems to have been a local network problem, as the issue has magically disappeared. Nothing exciting to report.
Click to expand...
Click to collapse
Remove SIM card and clean?
Yep - did every trick in the book. Even reflashed via Odin to be sure I didn't have a corrupted radio file. It just started working again. I"ve seen the same problem reported in other parts of the country, apparently the result of something AT&T was doing to the network.
Love the device, but this one is going in for an exchange. Not sure if it will resolve the issues I had, but my phone was behaving badly. I unlocked and rooted it about 10 minutes after I got it, using the Chainfire method here..
1) WiFi reception is awesome, except it drops the connection constantly! I have an entry level commercial AP (Unifi) and the thing is awesome. All kinds of devices connected to it, but this Moto can't stay connected. From the logs on the controller, it appears to be switching channels constantly. Wifi goes from all bars to bars with x to off.
2) Reboot results in bootloop. On more than one occasion, I had to reset the device multiple times to get it to boot. This morning, I could not get it to complete a boot at all. I've since reflashed the Tmo stock ROM.
3) Lookout randomly comes back! Froze it with TiBu, stop and disable in app manager... nothing kills it! Reason 1 for root!
The WiFi issue is a killer. Again, I am going to take this one in and exchange it for another and hopefully the WiFi issue is gone. I think I'll need to restrain myself from rooting until I pass the exchange date.
I had similar issues what i did was flash the stock boot img then do a factory reset and reroot and everything is good now
forty9er said:
I had similar issues what i did was flash the stock boot img then do a factory reset and reroot and everything is good now
Click to expand...
Click to collapse
Thanks! I will give that a shot before I take it in.
I've been back on stock with unlocked bootloader for a day and change, and I still get WiFi drops. It seems to happen more with BT on, but they certainly haven't gone away. I've changed a bunch of things on my AP to try and eliminate them too, but it hasn't helped much. I may try disabling the A/C radio (which fixes it for some), but that's hardly an answer. I am starting to think that this is a Nougat or a Qualcomm issue.
Seems like a hardware issue. If it was a software issue then it would affect more than just you. So far you are the only person on various forms I go to having issues.
Sent from my Moto Z (2) using Tapatalk
Tidbits said:
Seems like a hardware issue. If it was a software issue then it would affect more than just you. So far you are the only person on various forms I go to having issues.
Click to expand...
Click to collapse
Well, it seems I'm not the only one.
https://forums.lenovo.com/t5/Moto-Z...terprise-type-5Ghz-band-802-11AC/td-p/3816198
I actually have this issue with another device too , so I think it's either an Android, AP or a Qualcomm thing. Some have said turning off the A/C/N radio helps, but that's not a "solution."
I'm having random restarts with the s21 ultra, seems the phone is having an error in the background and restarts to avoid freezing or something.
I checked all the auto-restart options are off. The restarts really happen randomly, sometimes im watching a youtube video, sometimes chatting on whatsapp, and it happens almost once/twice a week.
But what i noticed lately, mostly its when an app is using the camera. Sometimes i try to launch the stock camera app and it doesn't launch (writes a quick note that its unable or something) and the phone reboots.
Any solution of what to do? I keep entering the members app after the phone restarted and send the crash log to Samsung but until now I have the same problem and no fix.
Its really unacceptable, i have paid alot for this phone, i got the 512GB with 16GB ram and in the end the phone crashes when opening the stock camera app. Really will never buy Samsung ever again
First, you need to track down the source of the problem.
I wouldn't even let WhatsApp run on my phone... it's nothing but trouble.
Try clearing the system cache.
Clear cam data.
Because it's rebooting you can't see what was running/cache last.
This is abnormal behavior and may indicate malware.
Look at 3rd party apps you have installed for starters.
blackhawk said:
Instead *****in you need to track it down...
I wouldn't even let WhatsApp run on my phone... it's nothing but trouble.
Try clearing the system cache.
Clear cam data.
Because it's rebooting you can't see what was running/cache last.
This is abnormal behavior and may indicate malware.
Look at 3rd party apps you have installed for starters.
Click to expand...
Click to collapse
Where can he go to see what apps caused the crash -- isn't there something in the Android system that allows him to see that?
oae08 said:
I'm having random restarts with the s21 ultra, seems the phone is having an error in the background and restarts to avoid freezing or something.
I checked all the auto-restart options are off. The restarts really happen randomly, sometimes im watching a youtube video, sometimes chatting on whatsapp, and it happens almost once/twice a week.
But what i noticed lately, mostly its when an app is using the camera. Sometimes i try to launch the stock camera app and it doesn't launch (writes a quick note that its unable or something) and the phone reboots.
Any solution of what to do? I keep entering the members app after the phone restarted and send the crash log to Samsung but until now I have the same problem and no fix.
Its really unacceptable, i have paid alot for this phone, i got the 512GB with 16GB ram and in the end the phone crashes when opening the stock camera app. Really will never buy Samsung ever again
Click to expand...
Click to collapse
Do a return/RMA before time runs out? It could be a hardware issue.
nixnixnixnix4 said:
Where can he go to see what apps caused the crash -- isn't there something in the Android system that allows him to see that?
Click to expand...
Click to collapse
If it hadn't rebooted it would show as a running or cache app in Device Care or Developer options.
After reboot that's all cleared pretty sure the cache is too but you can double check.
oae08 said:
I'm having random restarts with the s21 ultra, seems the phone is having an error in the background and restarts to avoid freezing or something.
I checked all the auto-restart options are off. The restarts really happen randomly, sometimes im watching a youtube video, sometimes chatting on whatsapp, and it happens almost once/twice a week.
But what i noticed lately, mostly its when an app is using the camera. Sometimes i try to launch the stock camera app and it doesn't launch (writes a quick note that its unable or something) and the phone reboots.
Any solution of what to do? I keep entering the members app after the phone restarted and send the crash log to Samsung but until now I have the same problem and no fix.
Its really unacceptable, i have paid alot for this phone, i got the 512GB with 16GB ram and in the end the phone crashes when opening the stock camera app. Really will never buy Samsung ever again
Click to expand...
Click to collapse
I would try to get the device replaced by Samsung as soon as possible if I had the option rather than trying to troubleshoot it. This is abnormal behaviour, maybe software, maybe hardware but if I can get the device replaced, I'd choose that as the first option.
I had a similar issue with my brand new HTC Desire S (ages ago) and foolishly tried to solve the problem by trying software hacks, almost tripped the security flag and missed the DOA claim window trying to sort it out myself. Fortunately came to my senses and took it to the service centre and got a replacement on the same day.
If that's not an option for you, then we can all huddle together here and try to figure this out.
And by the way, don't hate on Samsung because your device isn't performing well. Sometimes this happens with complex electronic devices. That's what the warranty is for. If they don't honour the warranty, then we can all swear at them with abandon. Calm down and contact the service centre.
Be mad at Samsung for many things. Not this. Their QA isn't that bad and also head-to-head with Apple's, statistically speaking. Wait till you see what Pixels have been doing, LOL.
enigmaamit said:
I would try to get the device replaced by Samsung as soon as possible if I had the option rather than trying to troubleshoot it. This is abnormal behaviour, maybe software, maybe hardware but if I can get the device replaced, I'd choose that as the first option.
I had a similar issue with my brand new HTC Desire S (ages ago) and foolishly tried to solve the problem by trying software hacks, almost tripped the security flag and missed the DOA claim window trying to sort it out myself. Fortunately came to my senses and took it to the service centre and got a replacement on the same day.
If that's not an option for you, then we can all huddle together here and try to figure this out.
And by the way, don't hate on Samsung because your device isn't performing well. Sometimes this happens with complex electronic devices. That's what the warranty is for. If they don't honour the warranty, then we can all swear at them with abandon. Calm down and contact the service centre.
Click to expand...
Click to collapse
It may be hardware or firmware. Or completely self inflicted.
If you can return it, I would do so.
When buying an Android always go for one with an SD card slot; use it as the data drive and the OS/apps go on the internal memory. Makes life and reloads much easier... and faster.
I always build my computers with data drives, even did it with my laptop. Among other things it helps to protect your data. In almost all OS crash and burns, the data drives remain intact. Nonetheless you back up the data drives to at least 2 hdds that are physically and electronically isolated from each other.
enigmaamit said:
I would try to get the device replaced by Samsung as soon as possible if I had the option rather than trying to troubleshoot it. This is abnormal behaviour, maybe software, maybe hardware but if I can get the device replaced, I'd choose that as the first option.
I had a similar issue with my brand new HTC Desire S (ages ago) and foolishly tried to solve the problem by trying software hacks, almost tripped the security flag and missed the DOA claim window trying to sort it out myself. Fortunately came to my senses and took it to the service centre and got a replacement on the same day.
If that's not an option for you, then we can all huddle together here and try to figure this out.
And by the way, don't hate on Samsung because your device isn't performing well. Sometimes this happens with complex electronic devices. That's what the warranty is for. If they don't honour the warranty, then we can all swear at them with abandon. Calm down and contact the service centre.
Click to expand...
Click to collapse
I am not really sure what their warranty policy in KSA is. Will go to them in person and check what they will offer after making a backup of my data. But I expect they do not allow to get replacement (i have the device since about 4 months now) but this problem was not happening the first 2-3 months. But i haven't installed a single new application (so we cant say it may be a new 3rd party app)
blackhawk said:
Instead *****in you need to track it down...
I wouldn't even let WhatsApp run on my phone... it's nothing but trouble.
Try clearing the system cache.
Clear cam data.
Because it's rebooting you can't see what was running/cache last.
This is abnormal behavior and may indicate malware.
Look at 3rd party apps you have installed for starters.
Click to expand...
Click to collapse
I do not have many 3rd party apps for starters (less than 20) and i have the same exact apps on my other honor 10 phone which dont have this problem at all, so i believe its not from a 3rd party app.
Clearing cache and cam data are the first things ive done, and the same issue reoccurs.
Im posting this not for *****in but for users to give me ideas of what to do since im frustrated and i have done all the 'quick fixes' i could think of with no success.
If there is a way i can view the crash log, then that might be helpful...
oae08 said:
I am not really sure what their warranty policy in KSA is. Will go to them in person and check what they will offer after making a backup of my data. But I expect they do not allow to get replacement (i have the device since about 4 months now) but this problem was not happening the first 2-3 months. But i haven't installed a single new application (so we cant say it may be a new 3rd party app)
Click to expand...
Click to collapse
Only way to be certain is to ask them I guess.
Do you get the standard 1 year warranty in KSA? Or is it different?
I don't think there is any harm in asking. if they can diagnose the issue, they may be able to repair it at least, if not give you a replacement.
enigmaamit said:
Only way to be certain is to ask them I guess.
Do you get the standard 1 year warranty in KSA? Or is it different?
I don't think there is any harm in asking. if they can diagnose the issue, they may be able to repair it at least, if not give you a replacement.
Click to expand...
Click to collapse
We get 24 months warranty by samsung here, but I am not sure if they allow replacements in their warranty. I've had previous bad experience where they kept trying to 'repair' the device and same problem came again (long time ago- over 5 years so maybe things have changed).
oae08 said:
We get 24 months warranty by samsung here, but I am not sure if they allow replacements in their warranty. I've had previous bad experience where they kept trying to 'repair' the device and same problem came again (long time ago- over 5 years so maybe things have changed).
Click to expand...
Click to collapse
Wow! That's double the warranty coverage offered to us here in India.
If you think it's a software issue, and don't think Samsung will be of much help, then start with a factory reset. If that doesnt solve it, clean flash fresh firmware. If still no joy, then mostly it's going to be a hardware issue. Whatever you do, don't root or trip the e-fuse in any way if you want to have any hopes of claiming warranty in the future.
Hey
I also had this problem.. My phone would keep restarting while watching any type of video and/or using any app that used the camera. The phone screen would almost become "glitchy" with green lines and restart.
I even had an official Samsung partner come repair my phone at my home. He replaced the motherboard and the battery, but sadly this didn't fix the problem.
Lucky I was still within my 14 days with my phone network to get it replaced.
ItsSpain said:
Hey
I also had this problem.. My phone would keep restarting while watching any type of video and/or using any app that used the camera. The phone screen would almost become "glitchy" with green lines and restart.
I even had an official Samsung partner come repair my phone at my home. He replaced the motherboard and the battery, but sadly this didn't fix the problem.
Lucky I was still within my 14 days with my phone network to get it replaced.
Click to expand...
Click to collapse
Wow.
He should of just replaced the display too
oae08 said:
I'm having random restarts with the s21 ultra, seems the phone is having an error in the background and restarts to avoid freezing or something.
I checked all the auto-restart options are off. The restarts really happen randomly, sometimes im watching a youtube video, sometimes chatting on whatsapp, and it happens almost once/twice a week.
But what i noticed lately, mostly its when an app is using the camera. Sometimes i try to launch the stock camera app and it doesn't launch (writes a quick note that its unable or something) and the phone reboots.
Any solution of what to do? I keep entering the members app after the phone restarted and send the crash log to Samsung but until now I have the same problem and no fix.
Its really unacceptable, i have paid alot for this phone, i got the 512GB with 16GB ram and in the end the phone crashes when opening the stock camera app. Really will never buy Samsung ever again
Click to expand...
Click to collapse
t's all because the device used is problematic or the application has an error?