Related
hey guys, I don't know what happened but about 30 min ago, every time I try to open Google Maps I get the Force close notification.....anybody have any ideas of how I can fix this? I tried restarting the phone and uninstalling and reinstalling updates but nothing has helped
It's happening to me too. Started about an hour ago. It doesn't happen every time, but pretty often. Since we're not alone, it sounds like google has changed something server side that's sending data that kills the client.
oh pheww.....I thought I was alone lol
not to seem like an a-hole and be happy it's happening to you....but just sayin....haha
Thanks... I was a little worried myself, I installed the wifi tethering mod earlier today and thought I might have screwed the phone up.
Weird! Just started happening to me too. Thanks god for this forum and the search button, because I almost just began the nightmare of trying to figure out which new app or kernel I installed was causing this issue. Guess ill wait now since I'm not the only one. It's probably a Google server causing a problem.....
Same here, just started a little bit ago ... I don't think I can leave the house safely if I don't have access to google maps!$%!
edit: Just a possible fix ... I uninstalled and reinstalled and so far so good...
Are you guys using a modified rom?
Sent from my 1 gigahertz quake 3 playing, Quadrant bustin telephone
I uninstalled/reinstalled didn't help, but if I use WiFi it works fine. Weird.
Me too, except worse - my entire phone freezes up and I have to pull the battery. Not an east or safe thing to do while driving. Started happening about a week ago. Anybody know why?
Forgot to say. Stock ROM on my Vibrant.
shrasmyl said:
Forgot to say. Stock ROM on my Vibrant.
Click to expand...
Click to collapse
Stock Rom here too. Just started doing this to me today also, but only when I use it on the wifi on 3g its fine.
uninstall the google maps update and it will work for now. Google broke it and they will fix it.
Elite GunnerX said:
uninstall the google maps update and it will work for now. Google broke it and they will fix it.
Click to expand...
Click to collapse
Yeah thats what I did.
Same here...Stock Rom started doing this a couple hours ago.
Sent from my Samsung Vibrant
RIP my beloved rooted G1
Same is happening to me...rooted with stock rom. I kind of stop using google maps because of gps issue.
Sent from my SGH-T959 using XDA App
Have you guys tried factory data wipe and reset?
*2767*3855#
I got the crash only when WiFi was turned on . I uninstalled all the updates and am not getting it anymore.
Mine not forcing close, but a black screen "force me to shut down and boot the phone manually".
Everytime I opened google map with GPS on, the phone hanged and I needed to long press the power button to boot..
That is an issue I have seen with lag fix installed...i had to odin back to stock install lag fox then install apps...fixed all my fc issues on stock and other roms...anyways food for thought.
Sent from my SGH-T959 using XDA App
Updated today but still black screen when GPS is on...need to restart the phone manually everytime!!
Hi all,
Got my phone a week ago today, the issue started the next day. It happens about 1-2 times per day. Ill lock the phone and when I go to unlock it later, the screen won't wake up. I have to yank the battery to get it active.
Has anyone else experienced this?
Sent from my T-Mobile G2 using XDA App
sounds like a software bug, its usually something you installed thats running in the background.
-You can try trial by error and try to detect which app is causing it
-Or, wipe the device and start fresh
I doubt it- I don't have much installed beyond stock, just a handful of items that I also ran on my G1.
How does one perform a factory reset on a G2?
Weaseal said:
How does one perform a factory reset on a G2?
Click to expand...
Click to collapse
I was overthinking it and assumed this required bootloader/recovery - it's in the Privacy section of Settings.
lol, yup thats exactly where it is.
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.
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.
Hi everyone!
So I just had this problem after I woke up yesterday. I googled a lot but only found similiar problems.
Let me tell you what happened chronologically:
After turning the phone on in the morning it started updating apps as if I was doing a firmware update: "updating apps 1 of 135" etc. Note that my nexus was already running on 5.1.1 and had the latest updates installed.
Now it randomly freezes the screen on whatever screen it was before it happens and it won't respond to any touch input. This can also happen when not using the phone, then it will freeze at the lockscreen (the time freezes with it so sometimes i can see at what time it froze). Also, it loses connection with Wi-Fi as i'm using Whatsapp Desktop when i'm on my laptop and it mentions me that my phone is not connected.
The only thing that "fixes" (temporarily) it is a reboot. Now sometimes, on the lockscreen, i can just hold the power button and the pop-up comes in to turn the phone of, which i can somehow just tap on an it responds by turning the phone off. But sometimes (less frequent than the latter mentioned) the pop-up doesn't come in and holding the power button for a few secs will do the trick.
I hope I informed you all enough and my end question is: does any of you know what this is? How i can fix it or what i can do to prevent it or anything as I am hopeless. (my G3 is up for reparation so this is my sisters old phone, i had a nexus 4 myself for 2 years before the G3).
Thanks in advance!!
The best way to test it is by reformat the OS.
I positively think that it will solve the problem.
Since the phone is no longer under warranty, I guess there is no harm to install custom rom on it. They are fast and stable too.
Hope this help. Good luck.
Sent from my Nexus 4
EXACT thing happened to me too. Backup your data and hard reset from recovery. This fixed it for me
Same problem here bro, but neither custom roms or factory reset helps.... Is there anyone who has successfully solved the problem ?
multimedias said:
Same problem here bro, but neither custom roms or factory reset helps.... Is there anyone who has successfully solved the problem ?
Click to expand...
Click to collapse
Then it's time to change the screen or phone. Looks like it is a hardware issue.
Nitin
nitin.chobhe said:
Then it's time to change the screen ...
Nitin
Click to expand...
Click to collapse
I agree, your screen needs to be replaced.