[Q] Reboot issue with gps on while on a call - EVO 4G Q&A, Help & Troubleshooting

I thought this issue had been fixed with the 3.29 OTA but yesterday this just happened to me again. I was using Google Navigation and while I was driving I got a call. While talking for a minute or two then my phone rebooted. Are there others still having this issue? Should I try to go get another phone?

Related

[Q] G2 Apps Start Force Closing

On my G2, I've noticed that previously perfectly working apps will suddenly stop working, giving me a force close error whenever I try to launch them after being installed for a period of time. The only way I've been able to fix it is by uninstalling and then reinstalling the application.
Has this occurred to anyone else? And what should I do to fix this problem?
yes, i had this problem a few days ago...i did a factory reset and everything works fine as of now.
are there any solutions that don't require a wipe?
i had to wipe, and i lost all my mileage records i had entered into the mileage app, and my text messages before i backed them up...
its not too bad when its 2 weeks worth of information... but if this is going to occur often, its not going to be pretty
The two times that happened to me a simple power off/power on worked and they stopped Force Closing. I'm taking it that it didn't work in your situation and the uninstall/reinstall was the only fix?
yea i tried rebooting it several times, but after my latest wipe, nothing bad has happened...
still an issue that should be raised if its been replicated more than once
Ive had this problem with the stock browser and twitter, rebooting seemed to fix it.
Ah, one of those times where fix_permissions would be nice.
I've had to uninstall and re-install several of my apps because they've been force closing.
Sent from my T-Mobile G2 using XDA App
I've had this happen and it was acting really weird before it did it. It did like a vicious reboot and just about any app other than stock got a force close upon opening. It's gotta be software issues, god I hate stock roms. Damn TMobile and trying to restricting our joy of root.
Sent from my T-Mobile G2 using XDA App
This is starting to happen to me on my G2 as well now. I have uninstalled the Apps I could (except the preinstalled ones) and still they are force closing on me. I also have Factory Reset the phone several times and it still is happening. I have already exchanged my G2 once at Walmart for a flickering screen but im pretty sure the 14 days are up now with them. At this point I'm sure I have to call Tmobile.
Anyone have any ideas before I call T-Mobile?
I'm not rooted at all just plain stock.
Thanks

Gyro settings acting up

Panning and rotate aren't working at all. They just stopped working recently and panning force closes when I try to test it.
Sent from my Epic 4G Touch on Calc's GB ROM
I had the same problem. Dropped the phone from 2 feet and it would take forever to go to landscape and never go back to portrait. I flashed a ROM that morning before work and didn't get a chance to test anything till after the drop. I thought it was the ROM so I flashed a stock ROM and the problem persisted. So I flashed like 5 different ROMs and the problem persisted, then I realized that the gyro or accelerometer broke that day I dropped it. I downloaded an app to read sensor data, tried it on a couple of GB and ICS ROMs and the accel and gyro readings were always screwy. The funny thing is that when I took it to sprint they thought they were going to fix it with a factory reset. The guy came back out 10 minutes later confident it was fixed and the problem persisted. He didn't know that I had done extensive testing to find the root of the problem. Take it in let them do whatever they do then get a new one from warranty.
Thanks it managed to fix itself. Panning doesn't work still, but getting it replaced would be more trouble for me than for them for something I don't even like.

Camera, Netflix, YT, and Flashlight Apps Crash on my VZW GNex

I RMA'd my first GNex last August with a cracked screen, the one I got back had some problems:
Camera App crashes. Sometimes on startup, other times after a few seconds, and occasionally it doesn't crash until after I've been able to take a full photosphere, but usually the first two. It shows force close screen.
Netflix crashes after a few seconds to a few minutes. It does not show a force close screen, it just restarts the app.
Youtube won't load videos and when it does, it gives an error after a few seconds or minutes.
All flashlight/torch apps crash either on startup or after a few seconds.
I got tired of this, and didn't want to deal with Verizon's ****ty RMA service again, and since it seemed like it could be a software problem, I chose to root it and try to fix it with a custom ROM. I flashed CM9 and the problem persisted. Thinking it was too late to go back, I've just dealt with it until like a week ago.
Then I heard that a 4.2 update was coming to the VZW GNex, and returned to stock using this method (Would hyperlink, but don't have post count. It's the first result when you google, "Return to Factory State (Unroot and Relock) site:rootzwiki.com" without quotes. I flashed the JB files). Shockingly, the camera, Netflix, YouTube, and flashlight apps worked. However, when the 4.2 update came along, it broke everything again.
So that brings me to my questions:
Does anyone know of any way to fix this? Preferably without rerooting, but I'm still up for that if necessary.
Would I still be under warranty if I followed the linked method for unrooting?
EDIT: I'd also like to add that music playback is interrupted when either the camera or the flashlight app crashes.
go back to stock manually using this thread
Uelmm fuppofed
samersh72 said:
go back to stock manually using this thread
Click to expand...
Click to collapse
I'm already stock...
To reiterate: About a week ago I unrooted and flashed a stock 4.1 rom that fixed everything. When I got the OTA update to 4.2 everything broke again.
I also just did this, and it worked for a minute or so, but the apps are back to crashing now.

Camera frusturating problem

Hey guys,
I have a weired camera problem and I coudn't find anyway to fix it
The camera was working perfectly fine until one day It started being unresponsive sometimes and now I got to the point where it rarely responds!!!
When I open the camera sometimes it just shows black screen and I'm unable to do anything then after about 3 secs phone reboots and sometimes the camera app launches but the viewfinder is just black and sometimes it simply fc's!!!
I tried several camera apps (manul camera....) but in vain!
My first attempt to fix this was deleting data and cache for camera app! then I made a factory reset then I tried updating to android N DP4 and then I rolled back and in vain!!!
Once the camera srops working it will not work again until I reboot the phone and after I reboot it the camera will work for about 5 minutes to 1 hour then the problem starts showing!!!
Hope yo Guys can help me solve the issue I really like the phone and I don't wanna lose it!
Thx in advance!
Sounds like a hardware issue to me. I would send it in for warranty or repairs if possible.
Did you managed to get it fixed? I have the exact same issue. I think it first started happening after the latest security updates. I hope it's not hardware related, this phone just came back from lg repairs for faulty digitizer.
i got the same problem. i just try to install the final version of android 7.0 and hope the problem won't show again...
i'm anyway quite sure it's not a hardware problem, cause when the camera works it works great and shoots perfect photos and videos...i think it's the last security pack update which causes these problems, and maybe the solution will be the new security pack update, of september
I had the same issue, and I simply couldn't fix it by any means. It just started to happen after 3 months of use, and came out of nowhere.
I had to return it, luckily it was amazon......
Really weird.

Fix for OnePlus 3 Rebooting during Navigation? (Happens both on CM13 and stock)

Has anyone figured this out yet? This is infuriating. I had it reboot twice in 30 min with my stock ROM, so I had OP support "wipe" it, and reload the OS. After that, the GPS was all ****ed up so I said screw it and rooted it.
30 min into my drive into work today, it REBOOTED while running CM13 nightly and using Waze.
Charging doesn't change the outcome, bluetooth, etc. etc.
I am about to throw this phone out and get a pixel
never had this problem with MAPS.ME.
which navigations apps cause the problem?
I've been using Waze and Google Maps. It is totally random. Sometimes it won't happen for a week then all the sudden it reboots 4 times in a row.
Are you maybe using Xposed + n-ify?
The only time I had issues when using google maps navigation was when using n-ify.
Other than that, I used tha OP3 as a navigator for hours on our last scotland trip
and occasionally the last couple days without any issues.
No xposed or n-ify
+1.
I am using BJRR rom, which is also CM based.
But this problem is not persistent. Sometimes I can driver 1 hour without problem, but it could also happen within 15 minutes after I start driving.
I thought switching back to stock ROM can solve the problem, but I feel lucky that I haven't done that because it seems also to be an issue in stock, at least some of us has.
i had random restarts on 3.2.6 and 3.2.7 with root and exposed during navigation.
about 2 weeks ago switched to tesla n -- no reboots.
I have the same issue. It happens very randomly and in all roms I've used. (only marshmallow based) Usually after couple of hours of navigation either the phone reboots or looses GPS signal and only way to restore GPS lock is to reboot.

Categories

Resources