Phone Shuts down when notifications come - Moto G4 Plus Questions & Answers

Exactly what the title says it suddenly shuts down with a sort of click sound coming from the speaker's when notifications pop up. I tried silencing notifications but didn't work. I obviously can't block notifications. G4 plus is actually my dad's phone and it's really affecting his work. Any fix cuz this thing started happening after the warranty period more often. In the warranty time it happens like once or twice. Now it happens atleast once every day. Here's a screen shot of the system information if it helps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I have the same problem.
I was on LineageOS 14.1, so I thought it was a dirty flashing problem.
I full wipe and installed againg Lineage, same behaviuor.
This week I flashed stock firmware (december update), same beahviour.
When I receive a notification (not always, but very frequently) I can hear the very start of the sound and then the phone shuts down.
I loose also the messages/whatsapp/ecc, because shutting down is so quickly that the phone doesn't memorize the notification.
So I can't know who write to me.
Instead, I have no problem when the phone is silent/vibration, but obviously is a problem to have the phone always mute.
I think it's an hardware problem, I'm thinking to sendo it back (it's in warranty).
Any suggestion?

Same problem here also .. When notification comes its automatically shutdown..

Related

HD2 vibration stopped working !!!! [FIXED] WITH PICTURES

Hey everyone
Today I realised that my HD2 vibration doesnt work, I dont know why and what happened but it doesnt work, the only thing that I can say and hear is the click that I can hear whenever I try to turn on the phone , it seems its trying to vibrate but cant , only one click and the phone boots up normally , everything else works fine , I can also hear the click whenever I recieve a call or text .
What can I do to fix it ?
Basically I could fix it, the problem was flash cover, camera flash cover or glass as you can see in the picture had been pushed in a little bit and because it is exactly on the vibration motor itd prevent it to work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I opened the phone and pushed it back , now its working
I fixed it, and edited the topic coz thought it might be useful as this might happen to someone esle
cheers
Nice fix. Did the cover or it's supports break, or did it just pop out of position?
It wasnt loose, so probably something from outside caused it pop out of its position.

[Q] Nexus froze during long call - would not boot again

Loving the Nexus 4 (stock JOP40D + root) although I'm having some issues with the phone sometimes rebooting randomly (1-2 times a day)
and today it turned itself off during a long call (after about 45 mins) and would not boot again.
I pressed all combinations of buttons, plugged into the charger and it would not turn on.
Left it aside for a few mins, pressed power+vol and it booted normally as if nothing happened.
I then went to check the battery settings, and noticed a strange gap (screenshot) like the ones I was getting on my S2 after this kind of reboot.
Any ideas of what could have caused this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
looks like it's getting hot and shutting itself off.
get it replaced
munchy_cool said:
looks like it's getting hot and shutting itself off.
get it replaced
Click to expand...
Click to collapse
Thanks. Could that really be the case though? It didn't feel hot in my hand
I'd RMA it. I'm getting an RMA device for a "faulty battery". Many Nexi have shipped with dud batteries. Not sure if that's your particular issue, but call Google.

Random Freezes after Sideloading Lollipop

I sideloaded the OTA from stock configuration about 2 weeks ago, and since have experienced random freezes about 5-6 times.
At first I thought the phone was actually just randomly shutting down on its own since I couldn't turn the screen on, but then I noticed that the notification light was blinking (not red). Also my battery stats show the weirdest thing when this happens -- battery is not discharging, and everything is inactive except for wi-fi. Screenshots below.
Every time this has happened has been after a period of inactivity (after I've put it down for more than 30-40 min). I've experienced no other problems besides this so far.
Has anybody experienced this? Do you think a factory reset would help?
Note the OTA link and sideloading guide I got was from here: http://www.reddit.com/r/Android/comments/2mgh8o/nexus_4_lollipop_ota_link_and_update_guide/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's called the screen of death, and it's a long standing issue with the N4. See:
http://forum.xda-developers.com/nexus-4/help/nexus-4-randomly-off-intermittently-t2077148
https://code.google.com/p/android/issues/detail?id=52926
FormerSlacker said:
It's called the screen of death, and it's a long standing issue with the N4. See:
http://forum.xda-developers.com/nexus-4/help/nexus-4-randomly-off-intermittently-t2077148
https://code.google.com/p/android/issues/detail?id=52926
Click to expand...
Click to collapse
Aw crud. I have never experienced this before lollipop and I've had my N4 for 2+ years. Wonder if it would go away if I reverted to Kitkat. In any case, thank you for your answer.

N4 dropped in water. Battery drain after replacing daughterboard or software update

Phone: Nexus 4 running on CM 11 nighty 2014-12-12
Hi guys, the following happened to me and it's making me crazy:
- Dropped my N4 into the toilet ~10 days ago.
- After the drop my status LED was permanently on. I opened the phone and cleaned it: status LED running fine again.
- Recognize the microphone isn't working anymore
- Ordering new daughterboard and replace it
- Recognize everything is working fine BUT while calling someone I don't hear anything and the called person doesn't hear me.
- Thought to myself: ****, I destroyed the phone
- Doing another upgrade to CM with cache/dalvik wipe: stil no sound
- via web research I see that it's a bug and has nothing to do with me dipping the phone
So I was quite happy but now I have a ****in battery drain all the time as you can see on the screenshots that I took after leaving my phone pretty untouched over night:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this a software error? Or could it be a water damage issue somehow?

Nothing but scrambled pixels on screen

Phone suddenly ended up like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Doesn't matter if you go to recovery or download mode, it can't display anything else other than that. Is it a hardware problem? If so, what could be the cause?
https://photos.app.goo.gl/SI4tnxO2fE40zudn2
I think I have the same problem as you, but I can go into download mode and recovery. Another problem also is that my phone also randomly becomes frozen with similar scrambled pixels that while in the middle of a task (i.e. browsing the web, social media, etc.) I would like to ask you, how long have you had this phone for and have you rooted it? Because this problem occurred a few weeks after I rooted it. It could be either rooting it (which triggers KNOX, which is a fuse or something which blows, so it cannot be undone) or a battery issue since my phone is approaching 3 years. It is in light of recent events concerning Apple and with slowing down their phones to prevent things like this. However, I am purely speculating but yeah. As of now, I am not aware of any fix and am pretty sure this is a hardware issue since I have flashed many custom ROMs with no success. (Sorry this is a long read. )
It's definately a hardware issue.

Categories

Resources