When I was on Custom Roms (CM, AOKP, PA) I had the following Problems:
Screen does not turn on after call
Random Reboots (especially during calls)
Device Getting Slow (Trim-Erase)
Sometimes takes long to wake up and show lockscreen
So I tried different Roms (As mentioned above) and used the lagfix app (even bought the pro version to shedule it for every day).
The Call Problem persisted but the other ones were first gone but reoccured after 1-2 Weeks of Usage.
So I went back to Stock (4.2.2).
After one week of usage I have again the following problems:
Random Reboots During call
Long Screen-Wake Times (especially when Navigation is on)
Google Play does not start, just crashes (And yes I tried to remove updates, clean cache and data...)
Any Idea whats wrong with my device?
Related
I've run several different JB Roms but they all have a tendency to either reboot or refuse to turn on from sleep. It's not my power button (looked a thread where the person couldn't get their phone from sleep and it was a power button issue) because I can use the button to do a hard reboot. At times the ROM will simply stop. I'll be listening to music and the music stops playing and I can't get it to respond or I'll be in my app drawer and it won't change pages. Also, (and I'm not sure if they are related) Google Music will play music but will stop playing a song halfway through and start the next song.
I've wiped the cache and dalvic cache, fixed permissions made a nandroid and restored it and flashed new roms with a full wipe. That will fix the issue for a day or so but then the problems return and I'm starting to get a tad annoyed. Is this kernel related or is it possibly hardware related?
I, too, washaving issues with Google Music fetching songs while running the latest AOKP. However, the problem seems to have stopped with the official release of AOKP JB last week.
RR and SOD, like you described, are issues I'm still having though. They've gotten a lot better since last week. I've heard adjusting your CPU governor settings can help with the SOD.
I am currently running the latest build of the PacMan rom for my Sprint S3, but my problem didnt start there. As over the course of a few weeks my phone has been randomly crashing while running build 7 of Slimkat. It started crashing when i wanted to take a picture with the AOSP camera (when i hit the camera button and then it would shut off). Then it progressed to just crashing trying to use accuweather, or even when the screen was auto-rotating in my SMS app. So finally i just backed up my important bits and made a clean wipe into Wicked X 8.0 TW rom (because i'm on Ting and TW roms initially work on their network and wanted to export, or to just copy down the settings of, the APN xml to use in AOSP roms). After playing around with that for 20 minutes, i didn't experience any fc's or reboots. Though i did not use the camera in that time (i forgot to check). To which i then wiped it into PacMan rom that im at now. Which at the moment seems fine to do everything, except it will shut off if i want to OPEN the camera (doesn't let me use it at all). Plus i did have it crash once rotating with the play store up...
So im kinda lost, i wonder if this is just an issue with the camera in the rom, or if it might be a bigger issue with the phone itself. As ive been having the same random error's with two roms and i dont see anyone having FC's with pacman rom with the camera.
more testing done
So i have also attempted to odin completely back to stock and i have a stock rooted rom with nothing touched. The sudden shut-offs still happen and occur randomly. I installed logcat and what seems to be throwing error's is the accelerometer. Plus at first when i flash a new rom it seems to work ok with no problems for the first day, then suddenly start showing symptoms the next. Plus ive had it shut off during bootup too while going through the sprint 4g animation screen. Though i have not had it die on me in recovery, so thats a thing.... Plus it will rotate no problem half the time, and then ive seen it die rotating to use my keyboard.
So at this point i feel like its actually a hardware option. If it is the accelerometer, is it easy to fix (i guess re solder the connections if they're broke?)? or should i just try and replace the main board?
I haven't posted much in these forums so I can't post on the thread of the ROM itself. I'm having some problems with this ROM.
On the newer updates of Hangouts and Snapchat the phone acts super buggy.
In snapchat the video function just freezes the screen. Looks as if I've taken a photo but then snapchat is unresponsive. I've been running this ROM for almost a year and this is the first time I've experienced this.
In Hangouts I'm just experiencing HELLA lag. Which honestly seems to be happening to the phone in general recently (about 2-3months). Whenever I chose a contact and start typing sometimes it'll just go back to the contact selection page. Sometimes as I'm swiping words won't register (in all apps).
Other laggy/buggy issues I've noticed is that the pattern unlock function sometimes lags HARD. Other times the button doesn't wake my phone for like a minute. This didn't happen before when I first started running this ROM.
Any help/insights would be much appreciated.
Have you updated your firmware to the latest? Have you tried doing a factory reset (erasing data and cache)? It sounds like firmware or something on the data partition causing it. Especially since you said you have been running this ROM for awhile and we have had two firmware updates in the past couple months. Also the data issue might he true because there could be an app that is causing this issue. Happens more often than you think.
TL/DR: try new firmware and wipe data/cache from recovery and let us know if it is fixed.
Sent from my One using XDA Free mobile app
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.
Hello XDA,
I have reviewed everything that is out there on the internet and have not been able to resolve my issue.
I have LG G3 Rogers version, unlocked, never rooted. It used to work fine before. I started noticing my Youtube videos from the app stopped playing giving an error message (Error code is different every time) Youtube videos from the browser play but without sound, Instagram videos/live streams/stories (anything that has sound; IG videos with no sound when posted by the user works fine) stopped playing, spotify wouldn't play music but the timer of the track would keep going. This is with headphones, without headphones. Doesn't matter. Then when I restart my phone, the issue is completely fixed, for some time until it starts again. The way I know it will mess up is my pattern unlock sound goes out first. Then my lock sound and eventually certain key taps are not recognized. But again, when I restart the phone, everything is fine. I use Action Launcher 3, I've tried without it. I have factory reset my phone and I am running Marshmallow.
Any ideas? Much appreciated.
Thank you.
Re:
bluinitro said:
Hello XDA,
I have reviewed everything that is out there on the internet and have not been able to resolve my issue.
I have LG G3 Rogers version, unlocked, never rooted. It used to work fine before. I started noticing my Youtube videos from the app stopped playing giving an error message (Error code is different every time) Youtube videos from the browser play but without sound, Instagram videos/live streams/stories (anything that has sound; IG videos with no sound when posted by the user works fine) stopped playing, spotify wouldn't play music but the timer of the track would keep going. This is with headphones, without headphones. Doesn't matter. Then when I restart my phone, the issue is completely fixed, for some time until it starts again. The way I know it will mess up is my pattern unlock sound goes out first. Then my lock sound and eventually certain key taps are not recognized. But again, when I restart the phone, everything is fine. I use Action Launcher 3, I've tried without it. I have factory reset my phone and I am running Marshmallow.
Any ideas? Much appreciated.
Thank you.
Click to expand...
Click to collapse
If you have been using it for more than three years in a row, The android version wears out... (gets old)...
you might have to check for system updates or (in rare cases (or) you cannot tolerate kinda case) you can flash another rom on your LG G3.
Android ROMs give you a better battery life (which also eventually wears out after three years of usage) and better performance...
Hello,
I got a new battery about 6 months ago so not so worried about that part. Is there any to troubleshoot and deduce what could be causing this issue?
Hello,
Quick update: I have not had any issues with the phone for about 2-3 days now. I had pattern unlock set on my device with rain dew drops as the dots. Since I've removed the dew drops, this issues has stopped. Currently I have knock code set on as screen lock. I will now try pattern unlock again, but with basic dots only to see if this occurs again. Keep you posted.