I'm currently running Resurrection Remix JB v3.0.9 ROM on my galaxy S2 with the 3.0.15-Siyah-s2-v4.1.5+ kernel. The performance is fine until I have been using the phone for a few hours, after which it becomes progressively slower, almost to a point where it is unusable. Eventually the screen starts to flicker and the phone switches off. I've not tweaked any performance settings. The available RAM is being maintained at a normal level throughout. I would appreciate any ideas regarding the cause of this...
I wonder if it has anything to do with the memory leak that CM10 suffers. However, it only becomes unbearable after a few days, not a few hours. Have you done the usual cache and dalvik cache wipes and fix permissions in recovery?
Sent from my GT-I9100 using xda app-developers app
I did do that when I installed the ROM yes, I had the exact same problem when I used Jelly Bam AOKP build 4 ROM. I don't recall this happening with cm10 nightlies, that used to just freeze and crash randomly instead.
Well I believe it is because of the memory leaks linked with JellyBean. Perhaps when we get source code it will be fixed.
Sent from my GT-I9100 using xda app-developers app
I've had similar flicker issues but only in my browsers book marks. I'm running the same version too, but then I had this in the previous build also.
Can't say I've had any real issues with it other than that. In fact this build has performed better than the last one fixing a few camera issues I had previously.
On the scale of things the flicker issue in my book marks is fairly small. It's otherwise running well with the rest of the management holding out quite well.
Lemontang said:
I've had similar flicker issues but only in my browsers book marks. I'm running the same version too, but then I had this in the previous build also.
Can't say I've had any real issues with it other than that. In fact this build has performed better than the last one fixing a few camera issues I had previously.
On the scale of things the flicker issue in my book marks is fairly small. It's otherwise running well with the rest of the management holding out quite well.
Click to expand...
Click to collapse
I too had flicker issue while playing videos
I decided to change to a different ROM in case this was a factor, this time ICS rather than JB so I flashed 7comp 1.3.2. The phone has been working perfectly fine but the flickering/switching off issue has just returned (1st time in 2 days, phone has been rebooted in this period), no slowing down this time, just a rapid screen flicker/dimming for a few seconds then off. When I rebooted, the battery level had fallen from 85% to 9% (common S2 issue I believe), and the flickering/switch off occured again almost immediately. Could it be related to a cpu governor or undervoltage setting? The phone is set to -50mV across the range, although I did do an extensive bench test on both cpu and gpu last night and it passed no problem. It doesn't seem to occur when doing a particular task either. Any ideas on this one would be appreciated?
elfrider said:
...the battery level had fallen from 85% to 9% (common S2 issue I believe), and the flickering/switch off occured again almost immediately. Could it be related to a cpu governor or undervoltage setting...
Click to expand...
Click to collapse
I had a brief issue with this when I 1st installed JB, (battery measurement), I just reset the battery monitoring in JB and it's been reading fine since.
Just out of curiosity, have you tried adjusting the voltage to see if this makes any difference with the flickering? I never used the ICS Resurrection version so unsure if this option is available in it.
I've reset the voltage levels to default in case this was a factor but the problem is still present. It's following a very distinct pattern now- the phone will switch off randomly without any clues that there's something wrong (no flicker or lag), it only happens when I'm using it but not when I'm doing anything in particular. I'll then reboot it, the battery will be showing near empty and the screen will then flicker within seconds of me doing something and the phone will switch off. It will keep following this pattern forever, the only way to stop it is to plug the phone in, the phone will then be perfect until I unplug it, then the screen will soon flicker and it switches off. The only way to cure it is to leave it switched off for a substantial period, then it will be fine for about a day, sometimes two. Very weird, and very annoying.
Sent from my GT-I9100 using xda app-developers app
Related
Has there been any resolution to the 1 - 2 second wake up lag yet? I've seen several "fixes" like reducing the resolution of the lock screen wallpaper etc but none of these work for me. I've experienced the lag on KE7 stock ROM, Cognition ROM, Villain ROM and now on Lite'ning ROM.
Not sure if I agree that it's being caused by the CPU clocking down when the phone is asleep either. When I use SetCPU to set the minimum clock speed to 1.2Ghz the wake up lag is still there.
Also the lag does not occur when the phone is plugged in and SetCPU is telling me that the phone still clocks down to 200Mhz when asleep and plugged in.
Someone must have some idea what is causing this #$%$## lag.
I use Softlocker Free for this.. Works perfect for me, a bit reduced battery life but not enough to stop me from using it..
Thanks for the reply. I tried Softlocker a while back and found the battery drain pretty heavy. Might give it another go. I was thinking there must be a permanent fix for this lag problem though. Hopefully it's just a matter of someone finding it.
I also noticed the lag on my old i9000 as soon as I updated to GB so know this is across the different samsung models on GB in addition to SGS2. I really do think its the clock going down despite your setcpu settings. Use cpuspy free from market and you will see what I mean. Once its in standby it goes into deep sleep which I believe is lower than 200? But set it to 1200 min and see if cpuspy logs it as going below that just to see
It will happen on every rom right now since they are all based on the firmware. I really think it saves battery going into that clock mode and if someone comes up with a fix the cpu will have to run at a higher clock rate and battery loss will be significantly higher
Sent from my GT-I9100 using XDA App
Mines instant with No Lock.
Sent from my GT-I9100 using Tapatalk
Tell us what you did to stop the wake lock. Is it plugged in though?
Sent from my GT-I9100 using XDA App
I am using Lite'ning rom 1.4 right now, when I press the home button til the screen on take around 0.5 second, is it normally?
I've tried this app,and it did seem work. I'll try to see how about the drain of power.
I was using No Lock and it didn't make any difference. What is really annoying me about this is that some users are seeing the lag and others apparently aren't. The lag on my phone is probably about 1 second. This isn't a really big deal unless this sort of thing annoys you. My iPhone didn't have the lag, my Desire didn't have the lag and I feel a high end phone like this shouldn't have the lag either.
blue265 said:
Once its in standby it goes into deep sleep which I believe is lower than 200? But set it to 1200 min and see if cpuspy logs it as going below that just to see
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I'll have a play and see.
do you guys get lag when using the power button? I get a small lag when using the home button, but if use the power button its instant.
djsaad1 said:
do you guys get lag when using the power button? I get a small lag when using the home button, but if use the power button its instant.
Click to expand...
Click to collapse
There seems to be nearly as many combinations of symptoms as there are phones. Mine has the same 1s or so lag regardless of how I wake it up. I tried SoftLocker again. Not only does it chew the battery, it was randomly causing my phone not to wake up at all, which then required a reboot. Softlocker has since been uninstalled.
The lag definitely doesn't show itself if the phone is plugged in or if music is playing in the background. Also if the phone has only been asleep for 5 or 10 seconds the lag is generally not there.... but not always. This seems to be inconsistent.
Then there are the fortunate users who aren't seeing the lag at all..... unless of course they are failing to mention that they have something running in the background like the music player that is stopping the phone going into deep sleep.
All I know for sure is that it's a PITA that Samsung needs to address. Given that I've read it was an issue with the S, I'm not holding my breath on that one though.
appro77 said:
There seems to be nearly as many combinations of symptoms as there are phones. Mine has the same 1s or so lag regardless of how I wake it up. I tried SoftLocker again. Not only does it chew the battery, it was randomly causing my phone not to wake up at all, which then required a reboot. Softlocker has since been uninstalled.
The lag definitely doesn't show itself if the phone is plugged in or if music is playing in the background. Also if the phone has only been asleep for 5 or 10 seconds the lag is generally not there.... but not always. This seems to be inconsistent.
Then there are the fortunate users who aren't seeing the lag at all..... unless of course they are failing to mention that they have something running in the background like the music player that is stopping the phone going into deep sleep.
All I know for sure is that it's a PITA that Samsung needs to address. Given that I've read it was an issue with the S, I'm not holding my breath on that one though.
Click to expand...
Click to collapse
Don't want to fork/derail the thread, but are you guys experiencing only the "Wake Up Lag" or also the lag when pressing the Home button while unlocked. I see some lag when using the home button to go back to Homescreen 1 for example. In case you folks are seeing lag in both the cases like me, could it be that both have the same underlying cause.
There is this other theory about the bundled Voice Talk app from Vlingo having the shortcut of Home button double tap, which causes any Home button tap to wait until the double tap window before doing its thing. I don't see that mentioned in this thread, but it kind of makes sense for the Home button lag, but perhaps not so much for the Wake lag (at least I could not think of a reason for that to happen). What do you guys think about both these problems?
appro77 said:
Then there are the fortunate users who aren't seeing the lag at all..... unless of course they are failing to mention that they have something running in the background like the music player that is stopping the phone going into deep sleep.
All I know for sure is that it's a PITA that Samsung needs to address. Given that I've read it was an issue with the S, I'm not holding my breath on that one though.
Click to expand...
Click to collapse
Well well finally users are reporting this problem, good to see its not only me.
Anyway, I don't think the Phone goes to any underclocked frequency when it goes to sleep. Cause if you can test SetCPU by setting it to 200 MHz then you will notice that in 200 MHz the phone turns itself off, you have to turn it on manually. So the problem is related with firmware definitely. And there are no fortunate users, some users don't take this as a problem, some don't notice it and some notice but doesn't agree, but here or there everyone has the bug. I hope the issue will be fixed in future firmware upgrade.
Regards.
Sent from GT-I9100
It may seem crazy but...
The delay depends heavily on the lock image you choose for lock screen.
With stock image it's instant, with custom background it slows down significantly.
My theory is that custom image is being resized while low Cpu frequency, it takes a while.
Sent from my GT-I9100 using XDA Premium App
rdy2go said:
It may seem crazy but...
The delay depends heavily on the lock image you choose for lock screen.
With stock image it's instant, with custom background it slows down significantly.
My theory is that custom image is being resized while low Cpu frequency, it takes a while.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
I've just tested that, it's the same no matter what background I use.
Wow..
Seems like the thread I can finally count on! Lots of behavior that I experience as well. I have the home button lag and the wake up lag and it's bugging me.
One thing to note.. The wake up lag is worse when you have an SD card inserted -> This scenario was the same for the SGS1 too. Anyone can confirm this?
I'm using No Lock as personal preference but the lag is always there. All behavior you guys mention (abt headphones plugged in, charging, within 5-10secs) are all being observed.
Eagerly waiting for a fix!
I had lag on my first SGS2, but it was worse that yours, at about 9-10 seconds (that's no exaggeration) plus high battery drain (Only getting about 6-7 hours battery at normal use). Went and got a new S2, no lag, and battery lasts 36 hours now.
It may not be the case with yours that its faulty, but I think I fixed the first SGS2 by flashing a newer rom, then doing hard reset and clearing cache's. I now have 2 shiny new SGS2's working as normal.
TheBishopOfSoho said:
I had lag on my first SGS2, but it was worse that yours, at about 9-10 seconds (that's no exaggeration) plus high battery drain (Only getting about 6-7 hours battery at normal use). Went and got a new S2, no lag, and battery lasts 36 hours now.
It may not be the case with yours that its faulty, but I think I fixed the first SGS2 by flashing a newer rom, then doing hard reset and clearing cache's. I now have 2 shiny new SGS2's working as normal.
Click to expand...
Click to collapse
I did flash a newer ROM, but didn't do a hard reset.. all my apps were intact. Perhaps I will spend sometime on it this weekend. By the way, which ROM did you flash on your first SGS2 that fixed the problem?
Also, I tried SoftLocker and it works!! The only downside is the battery life. I loose about 4-5% per hour while I was asleep. That bring me to say that the delay is not caused by the voice input function, but rather due to the device going into deep sleep (which may be normal). But it's the waking up that's taking long.
Still seeking for more ideas...
MasK said:
Also, I tried SoftLocker and it works!! The only downside is the battery life. I loose about 4-5% per hour while I was asleep.
Click to expand...
Click to collapse
Yes, I found that SoftLocker is not really a solution because of the battery drain and some other bugs it introduced.
Anyone who is experiencing this lag should be contacting Samsung. I contacted Samsung Australia and they told me they had not heard of the problem. If everyone who is experiencing the problem reported it to Samsung, I think there may be a far better chance of a fix. Anyone who is annoyed by this bug, please email Samsung via the link on their website. If they are flooded with complaints they "may" act and provide a fix.
Hello All!
I am running the latest CM10 Jelly Bean ROM ( 8/21 nightly) and really like it for the most part - seems to be smooth, no major issues (well, keep reading), installed easily enough etc. I am pretty experienced with Android and flashing, etc.
I've had a problem that started with the ROM..my phone shuts off completely when it's charging and reaches a full charge. It's happened a couple of times. And yes, it IS charging, it's not the battery running low. lol. I reflash an ICS ROM and the problem goes away.
Any ideas?
witwolf said:
Hello All!
I am running the latest CM10 Jelly Bean ROM ( 8/21 nightly) and really like it for the most part - seems to be smooth, no major issues (well, keep reading), installed easily enough etc. I am pretty experienced with Android and flashing, etc.
I've had a problem that started with the ROM..my phone shuts off completely when it's charging and reaches a full charge. It's happened a couple of times. And yes, it IS charging, it's not the battery running low. lol. I reflash an ICS ROM and the problem goes away.
Any ideas?
Click to expand...
Click to collapse
What kernel are you running? Is it the stock kernel or did you flash devil kernel? If you flashed devil, did you modify any of the settings with the devil control app? If you did not install devil and are running with their default kernel, have you changed the settings at all? Have you UVed at all? OCed?
Also, is it really turned off completely? Like, the whole green battery charging symbol...or is it a SOD? If it's a SOD, it could likely be a kernel thing, which is why I asked all those kernel related questions ^^...although in hindsight, I should have probably asked this first, and then moved to asking about the kernel lol
Xenoism said:
What kernel are you running? Is it the stock kernel or did you flash devil kernel? If you flashed devil, did you modify any of the settings with the devil control app? If you did not install devil and are running with their default kernel, have you changed the settings at all? Have you UVed at all? OCed?
Also, is it really turned off completely? Like, the whole green battery charging symbol...or is it a SOD? If it's a SOD, it could likely be a kernel thing, which is why I asked all those kernel related questions ^^...although in hindsight, I should have probably asked this first, and then moved to asking about the kernel lol
Click to expand...
Click to collapse
Hello Xenoism!
Thank you so much for the reply. And shame on me for not giving you all of the information! I should know better! LOL.
So to answer your second question first, it turned off completely. When I press the power button, it switches on, boots up and shows a fully charged battery.
I've also noticed that the CHARGE indicator is not working...it does not show when my phone is charging (the icon in the notification bar).
I AM using the Devil kernel (1.2.1 I believe it is) as is, without any modifications except I OC to 1.3 or 1.4GHz. I've made no changes to the Voltages.
I suppose if I just reflash without DEVIL I can see if the problem continues. That really should have been my first step, right?
Again, thank you!!!
witwolf said:
Hello Xenoism!
Thank you so much for the reply. And shame on me for not giving you all of the information! I should know better! LOL.
So to answer your second question first, it turned off completely. When I press the power button, it switches on, boots up and shows a fully charged battery.
I've also noticed that the CHARGE indicator is not working...it does not show when my phone is charging (the icon in the notification bar).
I AM using the Devil kernel (1.2.1 I believe it is) as is, without any modifications except I OC to 1.3 or 1.4GHz. I've made no changes to the Voltages.
I suppose if I just reflash without DEVIL I can see if the problem continues. That really should have been my first step, right?
Again, thank you!!!
Click to expand...
Click to collapse
No problem at all, just trying to help ^^;
Trying out the stock kernel might be best, since from my experience things like this tend to be the result of some kernel related issue. If you're certain its not a sleep of death (which can be easily mistaken as the device being off, since the phone will appear off and you will need to hold the power button in order for the phone to reboot), and you haven't undervolted at all, then the answer becomes a tad more tricky. Off the top of my head, I might suggest downloading "Cpu Spy" from the market for free, and checking to see while charging what frequency your phone likes to stick around at....if for some reason the phone is staying higher than 100, it may be simply the result of it overheating overnight while charging which causes it to turn off. ^^
Make sure you do not have deep idle selected! I had the same issue. I also have an issue with charging icon (not status bar though). When phone is off and charging the battery icon doesn't turn green and show charge level, however it is charging. It doesn't effect performance at all so no worries.
Running helly 0817 with latest devil kernel.
Its peanut butter jelly(bean) time...
It is possible that because of your high overclocking, when the battery becomes high, the phone's voltage gets messed up our something and your phone shuts off.
Xenoism said:
No problem at all, just trying to help ^^;
Trying out the stock kernel might be best, since from my experience things like this tend to be the result of some kernel related issue. If you're certain its not a sleep of death (which can be easily mistaken as the device being off, since the phone will appear off and you will need to hold the power button in order for the phone to reboot), and you haven't undervolted at all, then the answer becomes a tad more tricky. Off the top of my head, I might suggest downloading "Cpu Spy" from the market for free, and checking to see while charging what frequency your phone likes to stick around at....if for some reason the phone is staying higher than 100, it may be simply the result of it overheating overnight while charging which causes it to turn off. ^^
Click to expand...
Click to collapse
Thank you for the great reply and usefull information. I actually left my phone at my sister's the other day and she lives in another city, lol, and am using a temporary replacement so I haven't had a chance to investigate further. But once I get the phone back I'll look into the Cpu Spy and also using the default kernel.
Again, thank you!
samsgun357 said:
Make sure you do not have deep idle selected! I had the same issue. I also have an issue with charging icon (not status bar though). When phone is off and charging the battery icon doesn't turn green and show charge level, however it is charging. It doesn't effect performance at all so no worries.
Running helly 0817 with latest devil kernel.
Its peanut butter jelly(bean) time...
Click to expand...
Click to collapse
Thanks for the feedback!
As I mentioned in an earlier reply, I left my phone in another city so I'll have to wait to get it back to check it out and look into the deep sleep issue...I appreciate the help and ideas!!!
K
Hi guys,
My Atrix 4G is acting weird for the past 2 days. I was running Nov 25 CM7 nightly with faux 1GHZ kernel when the issue first occurred. The phone got too hot suddenly, it shot up from 32C to 58C in a few seconds and the charge started decreasing from 38% to 15% in 2 to 3 seconds. Before I could realize what happened, the phone turned off. I plugged in my charger after letting it to chill, and the phone started charging.
After sometime, I saw that the phone had charged till 25%. So I booted into CM7. Within no time, the phone got extremely hot and turned off again. It did not start charging till it came to normal temperature.
I somehow managed to flash the stock CM7 kernel, assuming that the issue was with the Faux kernel. After that, the phone was operating at normal temperature for a couple of hours. I thought that the Faux kernel was the culprit and thought that my issue is resolved. But after a couple of hours, I again felt the phone getting too hot in my pocket and before I could react, it turned off.
Please help me. Is the battery dead and needs a replacement? Or is it with the ROM? I've been running CM7 with stock/Faux kernel for many months and never faced such an issue.
Note: The issue started happening some time after I installed two apps. One is the Koi Live Wallpaper and one is the Xperia S launcher. Now both are uninstalled but the issue still persists.
Thanks in advance for your help.
It does sound similar to how a PC would react to an overheating CPU/GPU. In that case, you want it to shut off before permanent damage. Heat does not play well with electronics.
See if you can go under Performance Settings and set it to "powersave" and lower the clock speed to the next lowest setting (912 or 800). If it continues, try to backup everything and do a clean install. If the problem persists, it's not related to software.
Are you having the same issue in recovery? It might prove to be a challenge if it does.
Other suggestions: Remove any case you have on there along with the backing to get more air flow. Try to use it in a cold area, or in front of a fan or something. People have tried linking busted display digitizers with excess heat, might want to be careful.
Sent from my MB860 using xda app-developers app
I have that problem but with ICS/JB roms, the phones gets hot because my cpu is stucked at 750 MHz for some reason i don't know
Normally i don't have those problems with cm7, but when i had it i solve it by just installing another faux kernel. right now i'm running v023 at 1Ghz and it's working properly.
Maybe you can try to fix the permissions under CMW, sometimes that correct some problems
Try CPU spy and see if your phone is running at high clock speed all the time.
Sent from my MB860 using xda app-developers app
Thanks guys for the ideas.
The issue doesn't seem to be related to the ROM or kernel. It is with the hardware, because the phone is heating up even while it is switched off. The battery needs to be removed and after it is cooled, the phone works normally for some hours before it starts heating up again.
If it is getting heated up even while switched off, the issue has to be with the battery or the phone's circuit. Not sure which one is affected and I dont have a replacement battery to test.
Any ideas?
gkarthik16 said:
Thanks guys for the ideas.
The issue doesn't seem to be related to the ROM or kernel. It is with the hardware, because the phone is heating up even while it is switched off. The battery needs to be removed and after it is cooled, the phone works normally for some hours before it starts heating up again.
If it is getting heated up even while switched off, the issue has to be with the battery or the phone's circuit. Not sure which one is affected and I dont have a replacement battery to test.
Any ideas?
Click to expand...
Click to collapse
Are you saying it's overheating while completely powered down or just when screen is off? Is it still under warranty?
エイトリックス から 送ります
thesummoner101 said:
Are you saying it's overheating while completely powered down or just when screen is off? Is it still under warranty?
エイトリックス から 送ります
Click to expand...
Click to collapse
It's overheating when the phone itself is off. It's weird. Looks like the battery is leaking charge. And it is not under warranty
gkarthik16 said:
It's overheating when the phone itself is off. It's weird. Looks like the battery is leaking charge. And it is not under warranty
Click to expand...
Click to collapse
That is weird. Sorry, I can't be further help. Good luck.
エイトリックス から 送ります
Okay first of all, I've scoured not only XDA but even Google for an answer to this problem to no avail. So if anyone has/knows of any thread that has the answer, please kindly reply or notify me so we can have this thread removed.
Here goes,
I'm experiencing a very unique (afaik) problem with my Galaxy S3. This started a few months back, when the phone started getting random reboots/ freezes and terrible battery life on ANY ROM/Kernel. I've tried CM, SlimBean/Kat, and even Stock and nothing worked. Finally I figured maybe the battery was shot. So a few days ago I went and got a new battery, and that's when it got weird.
I used the latest SlimKat after replacing the battery and after powering on the device, EVERYTHING seems perfect. It's really fast and responsive, battery drain while screen is on is extremely acceptable, things worked like new again. UNTIL I switched off the display, after 5 mins, I pulled out the phone and it was switched off. At first I thought maybe the initial charge wore down so I charged the phone to full, then powered it on. Again, everything went smoothly BUT, after switching off the display for more than 1 minute, the phone shuts off automatically.
I switched to the latest stock 4.3 ROM and restored everything to factory settings and it seems to have helped at first. As usual, everything is fast and battery doesn't drain so much BUT, after putting the phone to sleep, it takes 5-10 seconds for the screen to wake after pressing the power button, and even if it wakes up, it becomes EXTREMELY laggy and often freezes requiring a reboot. As usual, after a fresh reboot, everything becomes awesome again until I have to turn the display off for more than a minute.
I've tried everything, even installing an app that prevents deep sleep but the problem persists. It improved a little after flashing stock rom and reverting everything back so I'm really hoping this isn't a hardware issue. Is there maybe something else I can try, settings/software-wise? The phone is almost 2 years old and is already out of warranty.
I'm hoping it's not the sleep of death thing because the phone isn't exactly bricked. I can still use it for as long as it doesnt have to go into deep sleep (I turn it off before putting in my pocket and turn it on again when I need to browse/use the camera which is all it's good for in its current state.)
Also, the symptoms don't really fit the usual "Sleep of Death/Brickbug" Symptoms I've read about.
Hey, I remember having a similar problem. I formatted both my internal sd and external sd. Haven't had any problems ever since. Hope this helps.
Sent from my SM-N9005 using XDA Free mobile app
Already tried that. I did full wipes/formats on all my installs. I even tried not having an external SD inserted for the Odin installs. I tried not installing any app on the phone and it still gets messed up after going to sleep. As fresh installed AOSP or Pure Stock ROM. Odin flashes no problem so I'm really hoping nothing hardware-wise is messed up. I had to re-flash PIT after getting a new battery though, could I have messed something up there that would lead to this?
There is an app for that deep sleep syndrome, it's on playstore its calles brick check or something like that, if you cant find just google it.
And I dont think that could be software problem, BUT depends on what apps you used, flashes you made.
Hope it hepls
Well, i don't think its deith break, but i had the same essue with unofficial 4.3 and then at official 4.3 it worked well,
it may be a break in the motherboard or something.. as u tried every rome avilable it couldn't be softwear thing..
the app for emmc firmware is called 'eMMC check', you can find it on playstore
edit: does your phone heat up? or battery? did your display ever turned blue when waking up from sleep?
it could be also a short with your display/motherboard or other connectors or battery connector... and the protection kicks in
if you're good with tools and phone is not under warranty, you could disassemble it and reassemble/reseat the connectors
or, could be the power button shorting, if you decide to open it, examine the power button
@Eibram did you ever undervolt or overclock when using custom kernels or roms? Because it could be hardware damage.
Also, do as they tell you above, check if you have the insane f01 emmc chip. I know it's a common missconception going around that since 4.1.2 the SDS got fixed, but it didn't really get fixed since it's a firmware problem in the emmc patched through software which just makes it highly unlikely to happen (but not impossible).
I did some minor undervolting way back before JB came out but not since over half a year ago. I did the eMMc check and yes, I do have the inane chip.
Just an update, I re-flashed a PIT file and a rescue firmware and it seems to have helped a bit. It was running fine for over 12 hours aside from a random reboot just now.
I'm observing the phone right now to see wether the reboot was just coincidental. I really wish this is just a software thing.
Okay one more update, 2 days in and I've only experienced the one random reboot. It's still sometimes slow when waking up, but something around 2-5 secs sore not 5-15 seconds slow. I'm thinking that must be due to touchwiz bloat.
Not sure what is happening, but this phone went from being awesome to being hardly usable in a very short amount of time. I downloaded a Verizon update on or around November 5th, and ever since then, I have noticed the following issues ever since then.
- Overall slowness. Whether it's switching apps, making phone calls, turning the screen on or off...everything is just much slower and lags more often.
- Unresponsive at times. This occurs most often during phone calls. The proximity sensor does not activate correctly (screen will not turn on when I move the phone away from my face), and the touchscreen will not register input. It will happen other times, but never seems to follow a specific pattern.
- Random soft resets. Every once in a while, it will randomly go to the Verizon splash screen, for no reason. This has happened in the middle of phone calls, while using apps, and while the phone is just idle.
- Increased battery drain. Even turning down the screen brightness, and using some apps like CM cleaner to keep apps closed and clear up RAM usage, I am experiencing drain at an exponential rate (over 10% per hour when idle, and sometimes up to 20% per hour doing simple things like texting and making phone calls.)
I have researched multiple websites' solutions for crappy G3 performance. Some of their proposed solutions have applied to my problems, and I've tried each and every one of them. Nothing has really helped...turning brightness down, using apps like CM Cleaner and Battery Doctor, etc. My last hope is that I unmounted my SD card this morning...which, if it works, will be fine, but is kind of a bummer because I would have liked to have the expandable storage.
Unless the update I downloaded from Verizon (I don't think it was an actual Android update, but I'm not sure?) is what caused this, I can't find any more potential problems other than my phone being defective...which just doesn't make sense, as I've had it since launch now with no issues. The only other thing that I can think which may be affecting things is that the phone is encrypted (the SD card was not, I never found the time and eventually forgot)...and is also using a piece of software called Maas360 (which I installed around the same time as the update was downloaded), which I'm hoping does not affect phone performance this much, because it will be required by my work starting in the next couple weeks.
amsage3 said:
Not sure what is happening, but this phone went from being awesome to being hardly usable in a very short amount of time. I downloaded a Verizon update on or around November 5th, and ever since then, I have noticed the following issues ever since then.
- Overall slowness. Whether it's switching apps, making phone calls, turning the screen on or off...everything is just much slower and lags more often.
- Unresponsive at times. This occurs most often during phone calls. The proximity sensor does not activate correctly (screen will not turn on when I move the phone away from my face), and the touchscreen will not register input. It will happen other times, but never seems to follow a specific pattern.
- Random soft resets. Every once in a while, it will randomly go to the Verizon splash screen, for no reason. This has happened in the middle of phone calls, while using apps, and while the phone is just idle.
- Increased battery drain. Even turning down the screen brightness, and using some apps like CM cleaner to keep apps closed and clear up RAM usage, I am experiencing drain at an exponential rate (over 10% per hour when idle, and sometimes up to 20% per hour doing simple things like texting and making phone calls.)
I have researched multiple websites' solutions for crappy G3 performance. Some of their proposed solutions have applied to my problems, and I've tried each and every one of them. Nothing has really helped...turning brightness down, using apps like CM Cleaner and Battery Doctor, etc. My last hope is that I unmounted my SD card this morning...which, if it works, will be fine, but is kind of a bummer because I would have liked to have the expandable storage.
Unless the update I downloaded from Verizon (I don't think it was an actual Android update, but I'm not sure?) is what caused this, I can't find any more potential problems other than my phone being defective...which just doesn't make sense, as I've had it since launch now with no issues. The only other thing that I can think which may be affecting things is that the phone is encrypted (the SD card was not, I never found the time and eventually forgot)...and is also using a piece of software called Maas360 (which I installed around the same time as the update was downloaded), which I'm hoping does not affect phone performance this much, because it will be required by my work starting in the next couple weeks.
Click to expand...
Click to collapse
Ah encryption. That's your culprit. It sounds like you took Verizon's 11c update on the 5th of November. This was a minor security update that also added some minor features like a camera shortcut on the lockscreen. A lot of people have been experiencing very poor performance on the G3 after encrypting internal storage. Apparently, it drastically reduces read/write speeds as of now and is not ready for primetime. Hopefully with the Lollipop update around the corner, we will see this issue fixed. I would suggest decrypting your phone and seeing if that makes an improvement on overall fluidity. I know that that is a pain, but this seems like what has happened to several people who encrypted data on a stock LG ROM. Best of luck and let me know if encryption is not the issue!