Related
So i bought my G2 three days after launch and had none of the common issues until about a week before the OTA. I started experiencing the shutdowns at random and it slowly got more frequent (4 times a day). The OTA hit and i didnt have another shutdown for a week. Then one. Then two about three days later. Now its back to an everyday thing. Is there something i can do to fix it. Im not rooted and im not using any weird widgets or apps.
Is it rebooting or just shutting down and you have to press the power button to turn it back on? If its just shutting down and not rebooting then I think you might have a loose battery.
Sent from my T-Mobile G2 running Cyanogenmod.
Well, i hit the power button to wake up the screen and i get nothing. After a few seconds the white screen with the htc logo appears and the phone boots. I assume its shutdown cause it acts like its off. If it was a loose battery why would the OTA slow it down for a bit?
After the OTA (that was supposed to fix the random reboots/shutdowns), I had the same thing. About a week of none, and then they started again. Since I've perm-rooted, installed the BaconBits kernel and messed around with some Sense ROMs. Not one shutdown. I think T-Mobile's ROM build(s) for this phone just suck and that's the problem. Only on stock have I had the issue.
Yea I'm Experiencing the same issue. I Upgrade the OTA about three weeks ago and now out of know where it randomly turns off it doesn't shut OFF , it just turns off and then i have to take the battery out and reboot it all over again? Any Suggestions?
rolandoagarcia said:
Yea I'm Experiencing the same issue. I Upgrade the OTA about three weeks ago and now out of know where it randomly turns off it doesn't shut OFF , it just turns off and then i have to take the battery out and reboot it all over again? Any Suggestions?
Click to expand...
Click to collapse
I have the same issue however i thinks its due to a loose battery.
Sent from my HTC Vision using XDA App
Please see this post, I think this problem is wider spread than you may think: DesireZ issue
Hi guys,
Not exactly the most positive of first posts but here we go. There's a problem with my phone that I can't find the solution for...
Essentially my phone randomly turns itself off (no power down sequence, almost as though the battery's being taken out if you know what I mean) and then it has difficulty in fully booting again. For some reason it also likes to revert my wallpaper back to the original as stock.
The first thing that I thought of was malware, with the wallpaper - so I tried a couple of anti-malware apps to no avail. As my device was rooted, I then flashed back to stock, locked and unrooted it and checked the behaviour. Again to no avail (then again I've never rooted/unrooted so this may have been done incorrectly). By the looks of it, the worst case scenario is a problem with battery connections/hardware...
So the question is have you guys come across this before? Is there a solution to this or is Google/LG going to have to give me a replacement?
Many Thanks.
Weird, I just had this happen couple hours ago, I was watching a video and close the app. I press the power button to put it to sleep. Just like 20 second later, I press the power to wake it and it don't do anything. I had to hold the power button to turn it on. I check the battery status afterward and it looks like it drop between 5-10 percent in the chart after it turn on. The battery must have failed or something. This also happen to my wife phone couple weeks back, although she had to do a hard reset(power+volume up and down) it have not happen again though.
Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need
maintains
kyokeun1234 said:
Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need
Click to expand...
Click to collapse
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.
Thrice87 said:
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.
Click to expand...
Click to collapse
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.
kyokeun1234 said:
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.
Click to expand...
Click to collapse
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable
Thrice87 said:
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable
Click to expand...
Click to collapse
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?
kyokeun1234 said:
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?
Click to expand...
Click to collapse
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.
Thrice87 said:
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.
Click to expand...
Click to collapse
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app
kyokeun1234 said:
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, after completely reverting the phone back to its stock version and pretty much everything else, it's still doing it - which surely points to a problem with the chip (or something). So, I've contacted google about a replacement and so far so good - got through in 5 minutes and sorted out the RMA and everything, should be delivered in the next few days.
Thanks for the help anyway. I'm going to avoid rooting this one for the time being to see how it behaves.
I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.
hfuizo said:
I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.
Click to expand...
Click to collapse
Yeah that's not my problem at all Lol. Glad you've figured it out and I bet that magnet caused the issue IMO
Sent from my Nexus 4 using xda app-developers app
Funny I had the same thing happen to me last night. I was using the phone put it down for a minute or two and then could not wake the phone. What was interesting was when I couldn't get it to turn on I plugged in into the charger and let it sit for a few hours. When I was finally able to restart it using the the power, vol button the battery was at the same level before the incident. In other words whatever happened prevented the battery from being charged. I am stock and rooted and haven't loaded any new apps in over 2 weeks
Sent from my Nexus 4 using xda app-developers app
I have almost the same problem as the op but I do have a shut down sequence. It does randomly shut down itself. The first thing I got the phone I rooted it and it was fine working on modaco for 2 weeks then one day it kept shutting down upon boot until like 10 tries later I successfully got back in but lasted only a few mins and sometimes hours. Im gonna rma this pos and I hope I can get it replaced soon. I try it with stock rom and kernel then modaco with stock kernel then modaco with faux kernel. Same problem.
I had these problems earlier ... I just gave HARD RESET by pressing power key for more than 5 sec.
Then i figured, it was due to Undervolting ! and Processor going to a DEEP SLEEP all together !
So i removed UVing and it was cool since then ! ... Although my signature says the rest !
I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.
The same happens several times a week with my nexus 4 running latest cyanogenmod. I will revert it to clean stock in a few days to see how it goes. I don't think that is a hardware problem but time will tell.
MildewMan said:
I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.
Click to expand...
Click to collapse
Don't know if anyone is keeping up or cares, but I wanted to update and say that this did not fix the problem. 4.2.2 also did not fix the problem. I guess I could try getting a new one from Google.
My wife and I are both having this problem. Hers is completely stock, I'm unlocked and rooted. I was hoping it would be fixed with 4.2.2, but if it hasn't then it maybe time to get replacement N4s
I can't imagine this issue is very widespread, since there have only been a few threads about it. Its a big nuisance especially because it usually happens at night when I'm expecting my alarm to go off at night.
I hadn't wanted to send for replacements since it seems like a software issue but I'm getting fed up.
Sent from my Nexus 4 using xda app-developers app
Just had this problem occur with my N4 last night..... Phone is 2 weeks old.
Went to bed, plugged in the phone to charge [it was at about 50% or so, so not exactly low].
Woke up at 8.30 wondering why my alarm didn't go off at 7.30.... looked over and the phone was off.
It also didn't want to turn back on either. Took about a minute of holding in the power button for various amounts of time before it finally kicked to life [at 100% charge too].
This is going to be a real problem if this problem reoccurs. At home I have a clock radio but I travel a lot and rely on my phone to wake me up!
Here's hoping we can start to identify what is causing this issue. All I can add is that it is not low-battery related.
As stated in the sig. Phone is unlocked/rooted with stock rom.
I'm bone stock, no root and have recently applied the L720VPUFNAE update. Since taking the update, the phone has had nothing but problems. When awakening 50% of the time I will get nothing but a black screen and will have to hard boot the phone. The other 50% of the time, it's extremely slow to accept my unlock code. Half of my home screen shortcuts are gone, just disappeared. Battery life is terrible, just a few hours of life. I've browsed here for solutions and have seen some people having similar issues on other sites, but no solutions. Is there a way to force the update again to see if that fixes it? Any other solutions aside from factory reset? Often times the phone will ring and I cannot even answer it because it won't wake up properly!
I would suggest to factory reset the phone then proceed to Odin NAE tar that is available in the development section. Of course back up important things just to be sure. I had bad battery life for a few days. Until I discovered that it was clash of clans that was draining my battery. On Wi-Fi with the screen off it would drain about 4% since using greenify on it my battery now doesn't drains 0-1% under the same circumstances. You might have a rouge app that is draining your juice.
Sent from my SPH-L720 using Tapatalk
I am having these same exact issues. Really don't want to do a factory wipe if possible, but I am starting to think I may have to do it.
Also, the wifi issues have not been fixed with this release.
Anyone using anything like Juice Defender since the update -- is it helping with battery drain?
hshendon said:
I am having these same exact issues. Really don't want to do a factory wipe if possible, but I am starting to think I may have to do it.
Also, the wifi issues have not been fixed with this release.
Anyone using anything like Juice Defender since the update -- is it helping with battery drain?
Click to expand...
Click to collapse
What Wi-Fi issues. So far I haven't ran into a single one on unrooted.
try greenify it works wonders.
Sent from my SPH-L720 using Tapatalk
After the last update to 4.3 a few months back, I also had some serious issues which were only solved by a factory reset. I hate the thought of doing it again, it's so much work getting all the tweaks and settings back the way they were. But it appears that may be my only option. Each OTA patch Samsung has released has been a disaster, it's getting to the point where HTC might be back on the menu for me.
Bit dramatic there. If a factory reset fixes it there's nothing wrong with the update which you might have to do with an htc update also.
i can agree on the insane batt drain but other then tbat im error free.. the batt drops even while on the 1.5amp charger..
Sent from my SPH-L720 using xda app-developers app
chris-allen said:
i can agree on the insane batt drain but other then tbat im error free.. the batt drops even while on the 1.5amp charger..
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
It would drop on a 1.5 amp because the stock is a 2 and, wouldn't it?
Sent from my SPH-L720 using Tapatalk
probly right.. you should see it off the charger.. drop a percent per min.
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 12:31 AM ---------- Previous post was at 12:28 AM ----------
i wonder if there is a way to.boost the amp output on my laptop...itz usb2.0 @500ma
Sent from my SPH-L720 using xda app-developers app
I got the notification just now. How can I make it go away?
Google services framework is trying to update it.
Sent from my SPH-L720 using Tapatalk
As a followup to my own post, here's what I tried to fix it:
1 - A full factory reset with data wipe. Unsuccessful.
2 - A visit to the Sprint Store to have them nuke & pave the device to complete stock (it already was, but hey). Unsuccessful.
3 - Remove the Exchange Active Sync account. Successful.
To me this indicates a severe issue with the stock EAS client that comes with Kit Kat. If you are having similar problems to me, where the lock screen takes 20 seconds to appear, battery drain is enormous and the phone has problems "waking up" from screen power-off, try removing your Exchange account.
I might have to give something like Touchdown a try, I'm open to suggestions of a less costly alternative though.
once i remove it.....what will become unusable??
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 09:17 PM ---------- Previous post was at 09:14 PM ----------
just deleted the exchange services app.....is that ok? i dont use email on this device anyways except the gmail.
Sent from my SPH-L720 using xda app-developers app
I don't know if it's the same for you, but I had the native Exchange Active Sync email configured on my device with a enforced PIN lock. When my EAS account was configured under KitKat, the PIN lock screen had all sorts of issues, the device would get hot and battery life would go out the window. I deleted the EAS account, not the service.
Since then, I switched to Nine for my Exchange mail and the problem is completely gone. To make sure I configured the native app and deleted it a number of times. Each time the native EAS email was configured and the lock screen set, the phone crapped out. Nine enforces the same PIN lock policy, however my lock screen no longer freezes and kills battery. I am using "device security" with Nine, not "account security".
I'm honestly surprised to be the only one to experience this after combing through this and other forums. It means there's either something unique about my phone hardware/config or my Exchange server that causes the PIN lock screen to crap out. I don't have any lock screen widgets active.
My wife has a bone stock S4 with the same problems. We flashed the stock kitkat tar with odin and wiped data which didn't help. She doesnt use exchange, just gmail. Im trying to convince her to move to a gsm provider and get a nexus. Im Effing done with sprints garbage network and garbage bloated roms. Any suggestions before I set this phone on fire?
Sent from my Nexus 5 using Tapatalk
KatanaMan said:
I'm bone stock, no root and have recently applied the L720VPUFNAE update. Since taking the update, the phone has had nothing but problems. When awakening 50% of the time I will get nothing but a black screen and will have to hard boot the phone. The other 50% of the time, it's extremely slow to accept my unlock code. Half of my home screen shortcuts are gone, just disappeared. Battery life is terrible, just a few hours of life. I've browsed here for solutions and have seen some people having similar issues on other sites, but no solutions. Is there a way to force the update again to see if that fixes it? Any other solutions aside from factory reset? Often times the phone will ring and I cannot even answer it because it won't wake up properly!
Click to expand...
Click to collapse
So I had the same problem and this drove me crazy. I tried wiping Cache from OS, from Home key+Up volume+power, I tried a factory reset, I event tried applying the 4.4.2 patch via ODIN. I tried removing the lock screen and company email. The problem kept coming back.
Today however I brainstormed with a coworker who also has a working 4.4.2 S4 on ATT. After comparing settings for the lock screen we noticed the new swipe option and turned that on. What a bad move... that locked the phone up hard to the point I kept getting "com.android.systemui" stopped responding. I had no choice but to pull the battery and reset a few times and it didn't fix the problem. At last I had the idea to pull the SD card and boot the phone. That worked!
Everything worked exactly as snappy as it did with 4.3, so I rebooted a few times, got some texts, turned on the lock screen in order of swipe, and then PIN. With everything working I turned off the lock screen and put the SD card back in.
No problems....
rebooted
No problems...
turned back on the lock screen and all has been running well.
I'll report back if it slows down in a few days but at this point I've come to the conclusion that this problem has to do with the SD card. My thought is the Symbolic link which guides the OS to the SD card stay in the system even after the reset or upon reapplying a Play app. The removal and boot without the card removed the symbolic link and reset all the ExStorage to the new Kernel/OS version.
Hope this helps anyone suffering the same problems!!
Just wanted to throw my 2 pennies of experience in the ring. I'm on MF9 Bootloader and just recently moved to an NAE rom and kernel. I at first left my modem MF9, and everything was fine. Yesterday I flashed NAE modem and thats when the lag/black screen/CPU continuously working began. I cleared cache and Dalvik and still no fix. Being that I had just flashed the modem, I flashed back to MF9 modem and the issues went away. I then repeated the NAE modem flash and same issues came back. I'm back on MF9 modem and back to normal so far. I will also say that after flashing modems, there is a pop-up at boot that says something about android updating(no this is not the normal message when you clear dalvik). I dont know what the exact issue is, but for now I'm going to stick with MF9 modem.
Edit - Before anyone asks, I did check the MD5 of the NAE modem. That was my first thought is maybe a bad download.
Did you end up fixing your issue? I tried the SD card thing and it seemed good for 12 hours or so and then started having issues again. Thanks.
viper126 said:
So I had the same problem and this drove me crazy. I tried wiping Cache from OS, from Home key+Up volume+power, I tried a factory reset, I event tried applying the 4.4.2 patch via ODIN. I tried removing the lock screen and company email. The problem kept coming back.
Today however I brainstormed with a coworker who also has a working 4.4.2 S4 on ATT. After comparing settings for the lock screen we noticed the new swipe option and turned that on. What a bad move... that locked the phone up hard to the point I kept getting "com.android.systemui" stopped responding. I had no choice but to pull the battery and reset a few times and it didn't fix the problem. At last I had the idea to pull the SD card and boot the phone. That worked!
Everything worked exactly as snappy as it did with 4.3, so I rebooted a few times, got some texts, turned on the lock screen in order of swipe, and then PIN. With everything working I turned off the lock screen and put the SD card back in.
No problems....
rebooted
No problems...
turned back on the lock screen and all has been running well.
I'll report back if it slows down in a few days but at this point I've come to the conclusion that this problem has to do with the SD card. My thought is the Symbolic link which guides the OS to the SD card stay in the system even after the reset or upon reapplying a Play app. The removal and boot without the card removed the symbolic link and reset all the ExStorage to the new Kernel/OS version.
Hope this helps anyone suffering the same problems!!
Click to expand...
Click to collapse
ACoolGuy said:
Just wanted to throw my 2 pennies of experience in the ring. I'm on MF9 Bootloader and just recently moved to an NAE rom and kernel. I at first left my modem MF9, and everything was fine. Yesterday I flashed NAE modem and thats when the lag/black screen/CPU continuously working began. I cleared cache and Dalvik and still no fix. Being that I had just flashed the modem, I flashed back to MF9 modem and the issues went away. I then repeated the NAE modem flash and same issues came back. I'm back on MF9 modem and back to normal so far. I will also say that after flashing modems, there is a pop-up at boot that says something about android updating(no this is not the normal message when you clear dalvik). I dont know what the exact issue is, but for now I'm going to stick with MF9 modem.
Edit - Before anyone asks, I did check the MD5 of the NAE modem. That was my first thought is maybe a bad download.
Click to expand...
Click to collapse
Same thing happened to my S4. Moved to an NAE ROM and also installed the NAE firmware. Could not figure out why this slow down was happening. After some googling I ran across something that suggested installing the MF9 firmware again. After flashing 3 times to actually get it to stick, my issues went away.
I don't understand why some phones don't like the NAE firmware, but I just chalk it up to technology is weird sometimes and have accepted it. It works fine and good signal with the MF9 firmware, so I'm not worried about getting NAE to work.
I did just notice about 3 days ago that my battery life was dropping a lot without even using it. This is on stock unroofed NAE. I used to average 15 hours with 3.5hrs screen time. Now I am lucky if I can get 7 hours with 2 hours of screen time. It might be my phone so I might go to A sprint store to see if my battery is failing. It isn't a rouge app that is affecting it , not low signal( have an airwave). I go.to sleep with 90% and wake up 6 hours later with around 50% or less.
Sent from my SPH-L720 using Tapatalk
dpotter38 said:
Same thing happened to my S4. Moved to an NAE ROM and also installed the NAE firmware. Could not figure out why this slow down was happening. After some googling I ran across something that suggested installing the MF9 firmware again. After flashing 3 times to actually get it to stick, my issues went away.
I don't understand why some phones don't like the NAE firmware, but I just chalk it up to technology is weird sometimes and have accepted it. It works fine and good signal with the MF9 firmware, so I'm not worried about getting NAE to work.
Click to expand...
Click to collapse
When you say MF9 firmware do you mean you are running NAE rom with MF9 modem like the other poster? Thanks.
---------- Post added at 11:55 AM ---------- Previous post was at 11:16 AM ----------
tripleoptic said:
When you say MF9 firmware do you mean you are running NAE rom with MF9 modem like the other poster? Thanks.
Click to expand...
Click to collapse
Well my wifi broke flashing modem to MF9... guess I'll need to flash back.
Hey Guys,
I've been having problems with my nexus 4 randomly shutting down itself. The problem is sometimes when my phone goes to sleep mode it doesn't wake up again when I push the power button. There is no shut down animation or anything, it just randomly turns off. I have to long press the power button to reboot the phone. I'm currently on PA Final 4.41 along with hellsdoctor R20 kernel, this happens on both Dalvik and ART. My brother who is on a completely stock nexus 4 which was updated to 4.4.4 via OTA has the same problem as well.
I'm thinking it might be a bug in android 4.4.4 but not sure. Anyone have a fix for this problem? Thanks so much.
swiftyy said:
Hey Guys,
I've been having problems with my nexus 4 randomly shutting down itself. The problem is sometimes when my phone goes to sleep mode it doesn't wake up again when I push the power button. There is no shut down animation or anything, it just randomly turns off. I have to long press the power button to reboot the phone. I'm currently on PA Final 4.41 along with hellsdoctor R20 kernel, this happens on both Dalvik and ART. My brother who is on a completely stock nexus 4 which was updated to 4.4.4 via OTA has the same problem as well.
I'm thinking it might be a bug in android 4.4.4 but not sure. Anyone have a fix for this problem? Thanks so much.
Click to expand...
Click to collapse
Turn off auto update apps in playstore. Happend to me before to. Something happends when on wifi and phone in deepsleep the playstore auto updates the apps and it doesn't respond and I have to keep pressing the power button to power it on.
I have no more shutdowns since 4.4.3. But I use stock rooted.
Sent from my Nexus 4 using XDA Premium 4 mobile app
stuffynet said:
Turn off auto update apps in playstore. Happend to me before to. Something happends when on wifi and phone in deepsleep the playstore auto updates the apps and it doesn't respond and I have to keep pressing the power button to power it on.
I have no more shutdowns since 4.4.3. But I use stock rooted.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will try to turn off my auto update but I don't think it's the problem. My brother's phone which is completely stock, not rooted and has auto update off still experience the same problem as well.
Sent from my Nexus 4 using Tapatalk
My mother's full stock nexus 4 with android 4.4.4 experience no such problems
Same here
I got this crash today too. It just got stuck. Forced reset and it's ok. But again, this happens since 4.4.4
And i get some crazy lags on Google+ sometimes ... and this is a first. Don't know if it is the app, rom or Kernel.
I am on Paranoid Android 4.4.1, with Franco's kernel and running ART.
Also i am running ART for a long time now and never had any problems.
So I tried turning off Google Play updates and the problem persists. It usually happens around after the phone has been on for 30+ hours. Gonna try to switch back to Dalvik and see if the problems persist. Never had this happen before only after updating to 4.4.3+ ROMs have this started happening. Very stumped as to how to fix it
Right, so I think I cracked this one...
I handed in my headset in order for customer service to fix it and of course they flashed it with Googles 4.4 image(had to upgrade to 4.4.4 once I turned it on)...
After rooting it and flashing a bunch of custom roms I suffered from the same problem, it drove me nuts but I remembered it didn't happen when I upgraded from 4.4.2 so I downloaded a 4.4.2 image and flashed it(used wugs toolkit-the manual option) flashed TWRP recovery and a custom rom and I'm random shutdown free for the last few hours, hope that helps...
same problem here 100% stock android 4.4.4 (using nova but can't imagine that matters) last night was the first time i picked up the phone and pressed the power button... nothing. long pressed the power button for 8-10 seconds and it booted up. now again about 15 hours later i pick up the phone press the power button and nothing. never happened before and i assume its something to do with the 4.4.4 update. i dont use auto updating in the play store and this has literally never happened before yesterday.
sideswipe14 said:
same problem here 100% stock android 4.4.4 (using nova but can't imagine that matters) last night was the first time i picked up the phone and pressed the power button... nothing. long pressed the power button for 8-10 seconds and it booted up. now again about 15 hours later i pick up the phone press the power button and nothing. never happened before and i assume its something to do with the 4.4.4 update. i dont use auto updating in the play store and this has literally never happened before yesterday.
Click to expand...
Click to collapse
Im still random shutdown free, im not sure the solution i suggested on my earlier post will work for you but you can always try it and see...
swiftyy said:
Hey Guys,
I've been having problems with my nexus 4 randomly shutting down itself. The problem is sometimes when my phone goes to sleep mode it doesn't wake up again when I push the power button. There is no shut down animation or anything, it just randomly turns off. I have to long press the power button to reboot the phone. I'm currently on PA Final 4.41 along with hellsdoctor R20 kernel, this happens on both Dalvik and ART. My brother who is on a completely stock nexus 4 which was updated to 4.4.4 via OTA has the same problem as well.
I'm thinking it might be a bug in android 4.4.4 but not sure. Anyone have a fix for this problem? Thanks so much.
Click to expand...
Click to collapse
Try a 4.4.3 kernel like hellscore b47 or if you think it's a wifi issue a 4.4.2 version like b46 with the wifi fix.
http://forum.xda-developers.com/nexus-4/general/qa-kernel-hells-core-kitkat-b45-stable-t2495373
Jagdish84 said:
Im still random shutdown free, im not sure the solution i suggested on my earlier post will work for you but you can always try it and see...
Click to expand...
Click to collapse
How many hours has your phone been on? Mine usually shutdowns itself after 30+ hours.
Sent from my Nexus 4 using Tapatalk
danmen2 said:
Try a 4.4.3 kernel like hellscore b47 or if you think it's a wifi issue a 4.4.2 version like b46 with the wifi fix.
http://forum.xda-developers.com/nexus-4/general/qa-kernel-hells-core-kitkat-b45-stable-t2495373
Click to expand...
Click to collapse
I just reflashed PA 4.41 and running the kernel that came with PA. I believe it's the stock android one. Let's see how it goes.
Sent from my Nexus 4 using Tapatalk
sideswipe14 said:
same problem here 100% stock android 4.4.4 (using nova but can't imagine that matters) last night was the first time i picked up the phone and pressed the power button... nothing. long pressed the power button for 8-10 seconds and it booted up. now again about 15 hours later i pick up the phone press the power button and nothing. never happened before and i assume its something to do with the 4.4.4 update. i dont use auto updating in the play store and this has literally never happened before yesterday.
Click to expand...
Click to collapse
When did you update to 4.4.4? I never experienced this on 4.4.2 either. Only started happening after I updated to 4.4.4. I think for me it happened the first night after updating.
Sent from my Nexus 4 using Tapatalk
The only thing I can tell you is, that 4.4.4 causes a lot of problems recently. You are by far not the only one with this problem. I've also experienced random shutdowns like yours, bootloops, devices not turning on again...
Especially stock 4.4.4 causes problems. I could not identify the problem or bugfixes by now. It is really complicated since some devices work fine with 4.4.4 and some dont.
I only can suggest you to flash a 4.4.3 rom. That is the only work around.
swiftyy said:
How many hours has your phone been on? Mine usually shutdowns itself after 30+ hours.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Approx 24 hrs atm
same problem here...
Same here.
I have had the same problem since i updated to 4.4.4... except mine shuts off only when i touch the screen (like pull the menu down, open a app, ect.) so, I went and did a factory reset, nothing changed. downloaded the Nexus Root Toolkit, did a flash stock to 4.4.4 again, nothing.. Then now I have tried another flash stock to 4.4.3 but now have manually updated to 4.4.4. I will reply again to see if this changes anything.
My Nexus 4 is completely stock, not rooted, never tampered. So I am very surprised with this issue, but I have had another issue.. Along with the shutting off issue I have a problem which so far was fixed with the first Flash stock(i think) I would use my Nexus 4 with signal for texting and using data but when i went to actually use data like to search something up it would randomly say i have "no service".. not sure why it did this, happened when I had 4 bars and didn't move..
Still not working
After I did the Flash Stock to 4.4.3 and then manually updated to 4.4.4, my nexus still doesnt work. Dont even bother trying it.
I have the same issue however with a mail app, while the phone is perfect without the mail app
On 10/17/16 I took the OTA to take me from the July Security patch to the September security patch, with build number G935TUVU4APIA.
With in the first day of the update I experienced the phone freezing on the home screen, then rebooting. Later on I found it had rebooted while in my pocket (prompted for pin and system up time was minutes). Ever since over past 6 days it has become frozen and rebooted multiple times a day. Anywhere 2 to 5 times a day doing various different things.
I have tried clearing all system and app cache since after the update. Unfortantely that has not helped at all. So what I would like to know is anyone else on this build experiencing these reboots, or was before and fixed it?
I'm trying to determine if its a bug with this build, cause I will be really annoyed if I have to go through the trouble of a factory reset, then find out it didn't help cause its an issue with this specific build. If some other stock people can confirm this build is not rebooting for them I will give factory reset a try.
AndroidPurity said:
On 10/17/16 I took the OTA to take me from the July Security patch to the September security patch, with build number G935TUVU4APIA.
With in the first day of the update I experienced the phone freezing on the home screen, then rebooting. Later on I found it had rebooted while in my pocket (prompted for pin and system up time was minutes). Ever since over past 6 days it has become frozen and rebooted multiple times a day. Anywhere 2 to 5 times a day doing various different things.
I have tried clearing all system and app cache since after the update. Unfortantely that has not helped at all. So what I would like to know is anyone else on this build experiencing these reboots, or was before and fixed it?
I'm trying to determine if its a bug with this build, cause I will be really annoyed if I have to go through the trouble of a factory reset, then find out it didn't help cause its an issue with this specific build. If some other stock people can confirm this build is not rebooting for them I will give factory reset a try.
Click to expand...
Click to collapse
Idon't have this build installed yet but the previous one and had the same issue, turned out to be my alarm clock plus app causing it to reboot on an alarm.
Sent from my SM-G935T using Tapatalk
Shrubby said:
Idon't have this build installed yet but the previous one and had the same issue, turned out to be my alarm clock plus app causing it to reboot on an alarm.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Dang that sucks, worse time for it to fail when its supposed to wake you up lol! Thanks or the suggestion but I don't think its app related since it happens on home screen, in app drawer, in chrome, and in my pocket with screen off. Unless its an app in the back ground. But I haven't installed any new in past 5 days apps that I would say are uncommon that aren't supported well.
Edit: I just checked. Since the OTA I did install 1 app the day after. The Nexia app for smart thermostat that came with my new furnace. I don't think thats it since I can recall at least 1 reboot after the OTA and before that app. But just in case I will uninstall that app for a couple days just to test. Thanks!
Shrubby said:
Idon't have this build installed yet but the previous one and had the same issue, turned out to be my alarm clock plus app causing it to reboot on an alarm.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
I use I cant wake up alarm clock and experience that too. I am rooted but still keep the alarm clock because it rearms on reboot and still works. so no biggie for me
Sent from my SM-G935T using Tapatalk
I had a serious freeze/lock up last night. I am on the same build and NOT rooted. I even tried holding down the power button and the phone was unresponsive. Cap. keys stayed lit the whole time. After holding down for 45 sec or so it finally relented and rebooted. But this combined with random heat surges/ups really have me pissed.
Had the same issue. On u firmware now cuz i couldnt take it. One thing that seemed to help some was removing the sd card and wiping cache then rebooting. I let it run for a few hours then put in sd card. Seemed to help alot
I'm back to follow up with the results from uninstalling the only app I installed since the update. It actually almost went 24 hours without a freeze and reboot. I was starting to think it actually was the culprit. But then I had 2 freezes and reboot today. ��
So I have switched back to my Nexus 6P for a while. Thanks to those who also reported the same issue! Since other people are reporting the same issue it seems to be a bug in this build unfortunately. So here is to Samsung pushing out a fix soon. Until then I will be using my 6P. If they haven't fixed it in a couple weeks then I will probably flash to the U firmware too. What variant is the U firmware from anyways? The unlocked North America variant?
I installed the update and have been running it for the past four days with no problems to report thus far. If I get a reboot or any freezing I'll let you folks know. Perhaps try a factory reset.
Sent from my SM-G935T using Tapatalk
I get a reboot twice a day. Sometimes the phone will freeze while I'm scrolling through my internet browser or it will reboot if I'm using the SAMSUNG branded car charger and Google Maps at the same time. Other times it'll just randomly reboot out of nowhere.
This is extremely frustrating. T-Mobile recommended that I get an exchange and I did get an exchange and the same day it rebooted on me. I called complaining that it's not a hardware issue and they told me to exchange the phone again. Smh.
This sucks especially since I use GPS a lot. This phone was/is perfect before the update.
Sent from my SM-G935T using XDA-Developers mobile app
OuncE718 said:
I get a reboot twice a day. Sometimes the phone will freeze while I'm scrolling through my internet browser or it will reboot if I'm using the SAMSUNG branded car charger and Google Maps at the same time. Other times it'll just randomly reboot out of nowhere.
This is extremely frustrating. T-Mobile recommended that I get an exchange and I did get an exchange and the same day it rebooted on me. I called complaining that it's not a hardware issue and they told me to exchange the phone again. Smh.
This sucks especially since I use GPS a lot. This phone was/is perfect before the update.
Click to expand...
Click to collapse
Yeah... Carriers need to train their employees to be able to know how to tell the difference between a hardware and software issue. For example if a user reports something didn't happen until a recent update, then that should be an automatic sign to not waste that customers time with a pointless exchange.