My wife has a G7 Thinq that has been having this problem for a while now. She gets the debris/moisture error when the phone has had no exposure to water at all. There is nothing in the port at all. No amount of drying/cleaning makes any difference. When the error occurs, she gets frequent notifications and can only charge the phone wirelessly. The only fix is to factory reset the phone. Then, it's fine for a while (it was 2-3 months this last time), as long as she does not restart the phone. It often, but not always, recurs after a restart. Once the error occurs, it persists until a factory reset.
Because it goes away after a factory reset, I'm inclined to think it's a software issue, but I've had no luck in identifying an app responsible for it. Has anyone else seen this behavior, or know how to solve it? It has the stock ROM on it, and I've wondered if a custom ROM would fix the problem. However, she likes the stock ROM, so I'm not exactly eager to change that.
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
blackhawk said:
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
Click to expand...
Click to collapse
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
drfarmkid said:
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
Click to expand...
Click to collapse
If it didn't crop up right after the reload it indicates something that was added or a changed setting.
Clearing the system cache can only be done off the boot menu. This can cure many types of erratic behaviors.
For individual apks clearing their data can do the trick when clearing the cache doesn't.
A hard reboot simulates pulling the battery or pull the battery if it's removable.
I run many of my system apks as the factory loaded versions because of issues with their updated versions.
Next reload pay close attention to any updates.
If it's software caused it may prove a challenge to track down.
Could be an internal hardware failure. Try a known good cable and charger. Google the issue, others may have had the same problem and have a solution.
Clearing the cache, factory resetting the phone, etc. didn't work this time around. I was going to try putting a custom ROM on it, until I started looking into it and found out the bootloader can't be unlocked (it's the T-mobile version).
In the service menu (dial *#546368#*710#) there is a setting to shut off moisture detection. That also didn't fix it. However, I did find something in there that I don't understand that might be informative. My daughter has the same phone, so I looked through some things in there comparing the two. Under a menu called "Type-C checker" there is a table where the two phones differ. My wife's phone says:
Supported ModeUFP DFPMODEFAULTPOWER ROLEFAULTDATA ROLEFAULTVCONNN
My daughter's phone says "NONE" where my wife's says "FAULT". Does that mean anything?
I'm now suspecting some sort of hardware fault, perhaps a short in the charging port. I can buy that daughter board with the USB port for ~$15. What are the odds replacing that will fix it?
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
Hopefully it's a permanent change.
Androids wuv attention...
drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
hey, can you have found what was the issue because I have exactly same issue like your phone.
Related
Hello, I have a weird situation on my hands here and was wondering if you might be able to help.
Firstly...
HTC incredible.
CM-7.0.3 stable (most recent)
CM kernel2.6.37.4 #27
Overckocled 1.1GHz
radio 2.15.00.09.01 (going to work now, need to update, just saw it was outdated)
Long story short.
my phone has been working fine, no issues whatsoever until yesterday. Yesterday my Market app and browser started crashing as soon as I started them.
Today more things are crashing, and at a much higher rate of failure. Normally I would just clear the cache, and the applications cache, and the problem would be fixed (this has been a problem in the past) however this is more than just one application.
popup error reporting reports that specific applications have failed (market, browser, etc), but I also get general "framework" crash popups. Ideas?
Side note. I am also noticing a very long startup time on restarts, much longer than in the past.
I have not made any recent changes to my phone (over-clocking, kernels, radios, ROMS) other than of course installing apps.
Warning message example.
com.android.market
com.google.processes.gapps
android.processes.media
Ideas
first thing i would do is clear cache and dalvik cache and try fixing permissions.
If those don't work which I won't be surprised if they don't I would...
clear all data and reflash the ROM. Quick and Painless with titanium backup.
I already cleared the caches and fixed permissions.
I know re-flashing everything will work, and I have doen that in the past, however I am really tired of it. It seems to be mort stable now, and almost fixed completely. (I didn't change anything after repair attempts stated above)
My question is really what ic causing this, and is there anything I can do to stop this from happening.
If this is something that happens all the time.... must be something you are specifically doing.
My friends inc was doin the same.thing. I couldn't even get into Rom manager or titanium. Never ran into that problem before in almost a year with the inc. Reflashing was the only thing that worked. As for the cause... its a computer. Computers don't need reasons to go hay wire.
There was a time my inc wouldn't stop rebooting... multiple times a day... very annoying. Did everything including goin back to stock. One day after a couple months of that crap.... it just stopped randomly rebooting...
Well...
Firstly I agree, but dont know why...
This happens with different severity levels on average .9 times a month.
The strange thing is that I do nothing specifically at the time to cause this. No kernel installs, reflashes, rom updates, radio updates, or anything specific. It is just general use. It is not as if this happens as soon as I do anything in particular.
Any thought on any specific configurations that might cause this to happen over time, or settings that I can change? I would understand this happening on a system update, or major change, but that does not seem to be the cause in this case, or any other times this has happened.
What I would do...
Go completely back to stock. Run that for a month. If it STILL happens... take it to Verizon to exchange for a new one cause this isn't normal.
Thats the thing...
Hmmm... I have considered doing that. I am not sure I want to go through the trouble. Any other thoughts? (assuming that the phone itself is fine for the sake of this thread.)
Anyone else getting this error? After reading the two main errors seem to be faulty camera hardware and bar code scanning apps. I uninstalled my bar code scanner and the problem persists. There is a small dent next to my flash under the camera but this came with the phone and my camera worked for a while. Taking the battery out and putting it back in fixes the problem about half of the time, but only is good for one to two uses. I'm thinking of sending this in, but I'm waiting until the SGSII HD is out in case they offer to replace it with any phone. Wishful thinking, I know.
And here's the error:
Are you on the stock rom? I got that yesterday but a reboot fixed it.
HJZS2K said:
Are you on the stock rom? I got that yesterday but a reboot fixed it.
Click to expand...
Click to collapse
Stock ROM not rooted. No modifications what-so-ever.
8mileroad said:
Stock ROM not rooted. No modifications what-so-ever.
Click to expand...
Click to collapse
Try doing a factory reset. Sometimes an app installed on the phone might screw up with a hardware's function. For example, I've always use Screebl Pro on my phone to let it control how my screen turns off. I decided to try their new Beta version. A few days later, I cannot seem to manually turn off my screen by pressing the power button. Every time I press the power button, the screen will come back on on its own. I can try up to 4-5 times before it eventually goes off. I though my phone finally broke as I tried uninstalling and reinstalling apps, changing settings here and there to no luck. I finally realized about the beta Screebl I had installed, and decided to disable it. The moment I did that, the phone was back to normal, no weird things happening to it.
So try doing a factory reset first before sending it back.
Strangely enough uninstalling Reconage has seemed to fix this. Can anyone else confirm it breaks your camera? The comments don't say it does so it must be something with the Nitro.
I get it too on cm7 all the damn time. I can record 1 video then after I stop, it messes up and I have to reboot to record again.
Any more definitive answer on this issue? My wife's Nitro HD has started giving this error in the last few days and no amount of rebooting seems to be fixing it. She is stock plus a few apps. I uninstalled nearly everything that uses the camera, reboot the phone, and still have the problem.
Alternatively, is there a way to see what apps were installed/updated by date? The last photo she took was on 6/13, so if we can figure out what apps have been updated since then that might help us get to the bottom of the issue.
Some background info.
I bought my pixel XL from the Google store and I believe it came with the 63L build out of the box. I have since made it a point to completely wipe and fastboot flash the latest image Everytime an update is release, right now I am on the 26U build. The only thing I have done to my phone (and these bugs happen before and after) is bootloader unlock and root.
The bugs.
Every once in a while, my volume controls will quit working. I notice it happen more if I cast to my Chromecast and play a song or video (seperate) on my device. I'll hit the volume button and literally nothing will happen. To fix this I usually have to turn the display off, wait a few seconds, wake it back up, then the controls work fine again. I do not believe it is a hardware issue because i can fix it Everytime it happens.
The second bug, probably the most annoying, is that my nav bar will become completely unresponsive occasionally while in landscape orientation. Say I'm watching a video on YouTube in full screen, if I swipe to pull out my nav bar and hit the home/recent/back button, nothing will happen. I will see the animation however no vibration (feedback) or a action occurs.
This happens in games, YouTube, web browsers, doesn't matter as long as my phone is in landscape mode. Also note that when this happens, my device refuses to rotate back to portrait. This leaves my only solution (same as the volume bug) to turn off the display, wait a few seconds, and then I back on. Sometimes, however, this don't even work, and I'll have to jump straight to settings from my lockscreen to force the phone to portrait where the functionality of the nav bar returns.
I've contacted google, they run me through the typical steps "delete cache, have you tried a reset, update to the latest software", but nothing fixes it. They have told me repetitively it's not a common problem and it's not a problem that's worth rma'ing over.
I've been discovering my pixel has many small issues that no one else has. Such as the horrible transfer speed explain in my earlier thread, these bugs above, refusing to charge when the device is off, etc.
Has anyone had similar problems?
@noidea24,
I've had none of those issues. In fact, my Pixel XL has been flawless.
Not good. I guess I'm going to try and force a RMA.
noidea24 said:
I've contacted google, they run me through the typical steps "delete cache, have you tried a reset, update to the latest software", but nothing fixes it. They have told me repetitively it's not a common problem and it's not a problem that's worth rma'ing over.
Click to expand...
Click to collapse
Sorry to nit, but when I read the statement above I can't help but wonder if you actually did a factory reset. Reason I say that is you stated "have you tried a reset" and you didn't explicitly state that you did.
I kind of doubt the responsiveness stuff you're referring to is hardware related, it's probably software.
Whether or not a rogue app is affecting your device or a root app is impossible to determine without doing a factory reset and carefully adding one app/change at a time until the problem comes back. It's a PITA but that's what I'd do first to rule out hardware, and I'd simply run email and messaging apps unrooted for at least 24 hours to rule out hardware issues before I start loading up my favorite apps.
muzzy996 said:
Sorry to nit, but when I read the statement above I can't help but wonder if you actually did a factory reset. Reason I say that is you stated "have you tried a reset" and you didn't explicitly state that you did.
I kind of doubt the responsiveness stuff you're referring to is hardware related, it's probably software.
Whether or not a rogue app is affecting your device or a root app is impossible to determine without doing a factory reset and carefully adding one app/change at a time until the problem comes back. It's a PITA but that's what I'd do first to rule out hardware, and I'd simply run email and messaging apps unrooted for at least 24 hours to rule out hardware issues before I start loading up my favorite apps.
Click to expand...
Click to collapse
A factory reset is far from a pain in the ass, and yes, i have done it many times. the only things that makes it suck is when i have to transfer files back to my device because (as mentioned) i have terrible transfer speed from pc to device.
i have literally done everything i can to make this devices worth the price, and things are only getting worse. Since the post (later that night) i factory flashed once again, and re locked the bootloader. No root, No extra apps, hell, the only apps i had on my phone to begin with were facebook messenger, and that pixel car racer, i dont use anything else. ive had an even worse bug come in where my phone completely freezes when opening google camera and swiping to the video section. ill have to hold power until it force resets.
ive been with xda since my Motorola droid, Ive built roms for the community for my lg g2 and my nexus 6. hell, i even built kernels for my 5x (not public), so im a little past your average user complaining about some things that dont work due to user error. these are legitimate device flaws and malfunctions, and i was simply asking if anyone else has experienced them. and since it seems no one has, i have deemed my device faulty. now i have to come up with $600 for a service hold to get it replaced.
My experience with Googles first official flag ship has been pathetic, and im hoping that this replacement device i get (eventually) will persuade me not to go back to my 6p.
Well if that's the case then yeah I hope a replacement device will solve your issues. Sounds like it will.
Didn't mean to rile you up, just looking for clarity.
Good luck!
Hey guys,
I need your help here my G3 is acting up now and its really irritating me. So what happens is when im using the phone my WiFi will suddenly drop and I would have to wait around 5 minutes every-time this happens to me. I don't have a problem with my router its a fast router and works well all the time. Lets say i to go into a bathroom and when using the phone the WiFi will drop instantly and I've tried all the steps by forgetting the wifi and re-typing it again, factory resetting going onto my 2.4.GHZ and still receiving the problem. Is there ANY fix out there that can do it its really annoying me and i need it fixed. Please.
Thank you.
I'm no expert, but in my opinion (and assuming you haven't tried this yet) the first thing I would do is to do a hard reset. It is unclear from your post if the problem is occurring immediately after a hard/factory reset, so will assume you have added all apps afterwards.
If it is still happening after that (and before you start installing all your apps) then you have a problem with the phone itself. If not add all your apps back and ensure all have been opened/run.
If it starts happening again, then it might be an app causing it. Hard reset again and then add your apps back piecemeal (maybe 5 at a time - keep not of which ones you are doing) and open each one after installation (as installing is one thing, but the running of an app might be the cause)
This way, if it does start happening again, you will know which 1 (or maybe 5) app(s) is to blame.
As I said, I am no expert, but this is the logical way I would go about eliminating or trying to find the cause of an annoying problem.
rjcb23 said:
I'm no expert, but in my opinion (and assuming you haven't tried this yet) the first thing I would do is to do a hard reset. It is unclear from your post if the problem is occurring immediately after a hard/factory reset, so will assume you have added all apps afterwards.
If it is still happening after that (and before you start installing all your apps) then you have a problem with the phone itself. If not add all your apps back and ensure all have been opened/run.
If it starts happening again, then it might be an app causing it. Hard reset again and then add your apps back piecemeal (maybe 5 at a time - keep not of which ones you are doing) and open each one after installation (as installing is one thing, but the running of an app might be the cause)
This way, if it does start happening again, you will know which 1 (or maybe 5) app(s) is to blame.
As I said, I am no expert, but this is the logical way I would go about eliminating or trying to find the cause of an annoying problem.
Click to expand...
Click to collapse
I had a similar issue and the cause for me was having both 2.4 GHz and 5GHz WiFi networks SSID the same. If you have a dual band router name each differently. Hope that helps.
Sent from my LG-D851 using Tapatalk
Update on the phone I did manage to do a factory reset and have fixed the problem thank you rjcb23
Weird though I did multiple factory resets and that actually managed to fix the problem aha. Thank you. : )
Well, I had the 6 Pro for about 36 hours. It kept rebooting randomly, even after a factory reset, so it's going back for an exchange.
Has anyone else had this issue?
skyman631 said:
Well, I had the 6 Pro for about 36 hours. It kept rebooting randomly, even after a factory reset, so it's going back for an exchange.
Has anyone else had this issue?
Click to expand...
Click to collapse
No definately not, here the worst I have experienced is some app crashes, they probably aint android 12 ready, and some pretty big lag moments
I don't have any issues. Do you have the November update yet?
For some strange reason, I noticed exactly this aswell (one time, this morning). I was working out and my phone laid on the table, when I saw it lit up because it restarted for no reason.
I guess it's a software bug.
And no, there was no automatic system update - I checked, I'm still running the old version.
copong said:
I don't have any issues. Do you have the November update yet?
Click to expand...
Click to collapse
Is there a bugfix list of any sort about the most recent sytsem update?
I tried to find one, but as of now I have been unsuccessful.
No, nothing at all either. Mine also installed silently at some point. I recall a notification asked for a reboot yesterday morning.
No, not had one random reboot since I got it on Tuesday.
Nothing here either. Good luck!
copong said:
I don't have any issues. Do you have the November update yet?
Click to expand...
Click to collapse
I had the November update and all apps had been updated as well. It would freeze and then reboot.
I did a factory reset and did not restore any of my apps, just ran it with the factory apps, and it still did it. Since no one else is having the issue, I'm feeling confident it was a bad unit. I had the 128 gb version.
It's back to the pixel 5 for another week or so. I had to exchange that after I got it too because of a bad proximity sensor. Either I just have really bad luck or Google needs to tweak their quality control department.
Weird unexplainable OS crashes like that are usually due to faulty hardware, potentially RAM
If you're having issues, do yourself a favor and keep an itemized list (on your device, word doc on pc, somewhere) and notate the following for each occurrence:
-date / time
-the fault (self reboot, major lag, over heated, fast battery discharge, etc.)
-what you had to do to clear it (rebooted, closed app, powered off/on, etc.)
When talking with Google about a replacement, having THIS information ready to read off will make it extremely hard from them to give you any grief about you needing a warranty replacement.
An itemized list of faults is MUCH better evidence that you need a replacement than "well, it rebooted a few times last month"
copong said:
Weird unexplainable OS crashes like that are usually due to faulty hardware, potentially RAM
Click to expand...
Click to collapse
I am inclined to agree here, but my years of working with Windows and Android incl. rooting and using custom roms and kernels want to disagree here. There can be half a gazillion software based reasons for an OS crash, especially with a buggy release like Android 12. Not sure if you participated the beta, but it reminded me of Windows 11. There was a buggy beta build with about 100 bugs, they fixed 20, called it a day and released it. Now we new P6 owners can play beta testers Volume 2 for Google.
One very important thing here is also: Did you guys set up your phone "clean" or did you copy over your old phone by cable or did you use backup?
Any of these things can cause issues.
I, for example, used a cable to transfer all file and apps from my P4 XL to my P6 Pro. It's possible that this is the rootcause for some issues, or maybe it's not. Maybe there are even problems that occur only if you transfer your files from specific phone models to this one, you never know.
Morgrain said:
I am inclined to agree here, but my years of working with Windows and Android incl. rooting and using custom roms and kernels want to disagree here. There can be half a gazillion software based reasons for an OS crash, especially with a buggy release like Android 12. Not sure if you participated the beta, but it reminded me of Windows 11. There was a buggy beta build with about 100 bugs, they fixed 20, called it a day and released it. Now we new P6 owners can play beta testers Volume 2 for Google.
Click to expand...
Click to collapse
Sure, but the OP stated the crashes are happening right after a factory reset, and anecdotal evidence on this thread suggests it's not widespread. It does point to some sort of hardware problem.
I'm having exactly the same issue!
I got the phone today and booted it up for the first time. I selected my language and as soon as I pressed get started it froze, then got stuck in a bootloop. I fixed that by factory resetting from within recovery.
Once I'd gotten through the setup it crashed again when I clicked on the apps button in the optional setup. Because of this I factory reset and set the phone up for a third time.
Third time I got through setup with know issues but the phone freezes/reboots roughly once every two hours. I've been searching all day to see if anyone else has mentioned this issue.
I guess this phone is going in for replacement. Does anyone happen to know how long that takes/ if I'm going to be without a device for long?
They told me 3-5 business days to get a replacement. I expect mine early next week.
skyman631 said:
They told me 3-5 business days to get a replacement. I expect mine early next week.
Click to expand...
Click to collapse
Do you have to send the old device back first?
skyman631 said:
Well, I had the 6 Pro for about 36 hours. It kept rebooting randomly, even after a factory reset, so it's going back for an exchange.
Has anyone else had this issue?
Click to expand...
Click to collapse
I just had 3 random reboots today. Phone just laid on the side of my table on my laptop, doing nothing. It was in the span of probably ~10 minutes each reboot. A strange observation I made - now that I removed my phone from the back of my laptop and laid it directly on the table, no more reboots. Maybe it's a coincidence, maybe it has something to do with the magnets of my Laptop (has quite a lot inside). Not sure what to make of this. It kinda feels like a software buggy-thing, but it's odd that it sometimes just comees and goes. It also only appears to be in absolute idle. I had my phone working yesterday for about 12 hours, incl. using it constantly with navigation, and it never faltered for once. That's why I'd say it's a software thingy, if it had something to do with hardware, it would reboot/fail when under load. But it doesn't.
Had 4 total reboots as of now (had the phone since 27.10).
First reboot was yesterday (28.10) morning when working out, phone laid idle around, booted up.
And now again 3 reboots, morning, laid around, did nothing.
So I've had probably a dozen in two days. I take my phone out of my pocket and attempt a fingerprint unlock only to be told that my PIN is required after a restart. At first I wasn't sure if it was actually rebooting until last night. It prompted me for my pin and upon entering it, the screen locked up for about 20 seconds and it rebooted.
This morning I woke up and was yet again greeted with the "PIN required after restart" and less than 20 minutes later it was the same thing. Only once hav I witnessed the "G" boot animation, but everytime I see my UI loading. So I'm not sure if it's always a full reboot or some times it's just the UI crashing. Everything on my device is stock.
cloudraker said:
So I've had probably a dozen in two days. I take my phone out of my pocket and attempt a fingerprint unlock only to be told that my PIN is required after a restart. At first I wasn't sure if it was actually rebooting until last night. It prompted me for my pin and upon entering it, the screen locked up for about 20 seconds and it rebooted.
This morning I woke up and was yet again greeted with the "PIN required after restart" and less than 20 minutes later it was the same thing. Only once hav I witnessed the "G" boot animation, but everytime I see my UI loading. So I'm not sure if it's always a full reboot or some times it's just the UI crashing. Everything on my device is stock.
Click to expand...
Click to collapse
Did you transfer your old phone over with a cable, or backup, or did you start "fresh"?
Maybe we can narrow it down if it's software or hardware problem.
Morgrain said:
Did you transfer your old phone over with a cable, or backup, or did you start "fresh"?
Maybe we can narrow it down if it's software or hardware problem.
Click to expand...
Click to collapse
I did a partial transfer. I was coming from an iphone 12 so I transferred photos and contacts only. And I transferred via cable.