Hi there,
I am a (almost) happy owner of a pixel c,
but the device has massive performance issues since the last couple of weeks.
A typical geekbench 4 result should be around ~1400 single core / 3000 multi core,
my device shows 800 single core / 1700 multi core and is extremely lagging with almost anything.
Opening chrome for example needs 10-15s depending on the last visted site.
Therefore I decided to flash the latest office rom and cleanup the device. The first try was to only factory reset it, skip the whole setup procedure and make a new benchmark: Same result. Next step was to factory reset it, unlock the bootloader, flash the newest rom from google, twice (!!), relock the bootloader, startup - factory reset, and setup. After this procedure: Same result :-/
Is there anybody having the same issues? Am I missing something?
Happy for any advice, the device is nearly unusable in this state..
Cheers
It sometime takes a little while after installing ROM or resetting the device for it to optimize itself and the apps. I now the new Geekbench 4 scores differently now on all devices. Also, have you tried to wipe system cache in recovery mode? Grasping at straws but worth a shot.
I'm having these same issues as well. My 64GB went from lightning fast to slower than the worst throwaway android tablet I've owned, literally over the course of two days.
I can second the exaggerated lag, in everything from launching any app, scrolling, and also the boot process. Last night, it went from about 20% charge to 0% in less than 10 minutes because of a boot loop I've never seen before. It was showing the broken android avatar with the text "no command" on the screen. Once it died, I let it chill for a few minutes before plugging it in. It did boot "normally," but it was and still is experiencing the crazy lag issues.
Weird stuff, but most likely not a coincidence considering both the similarity of the issues and the timeframe.
Related
My DINC runs great most of the time. But at least once a day it will become very very slow and almost unresponsive. The commands still work, but take 5-10 seconds to complete. A reboot fixes it completely until the next time that it occurs. This has happened with every kernel, ROM, radio, recovery etc. that i've flashed. I first noticed this after flashing a Cyanogen release MONTHS ago and it hasn't gone away since then. Has anybody else run into this and come up with a fix?
I'm currently running MIUI 12.11 with the 2.15.00.09 radio and invisiblek's #18 kernel...obviously i'm rooted with S-off as well.
I have that happen periodically but it is pretty rare and usually I am trying to do a bunch of things at once so I just assume it is user load on the phone.
try unsyncing everything for a day - see if it still happens
If you call it a dinc its going to act like one.
seriously though you have given us nothing to go on here.
what are you running? have you done a full wipe/factory reset?
lafester said:
If you call it a dinc its going to act like one.
seriously though you have given us nothing to go on here.
what are you running? have you done a full wipe/factory reset?
Click to expand...
Click to collapse
What do you mean i've given you nothing to go on? I said exactly what i'm running. I don't know what more info you'd want about my phone... I've tried system wipes and flashing different ROMS...all to no avail. This can occur when the phone is sitting idle and other times it happens when i'm doing small things like using TFLN (texts from last night). When I was running Cyanogen months ago it would occur every morning when I would go to turn off my alarm...so it was happening at some point during the night when I was doing nothing. The only app that I have running overnight is Locale.
I basically posed the question to see if anyone else is having the same issue. If not, then it probably has to be something to do with one or more apps not playing nicely.
Make sure you do a full wipe, wipe dalvik, each time you flash to a different ROM.
Second, are you overclocking at all? If you are using setCPU, make sure that the max speed is set to at least 998. I have run into where installing a new ROM the max/min speeds are set low to 245. This causes overall phone slowness though...
If you are overclocking, set it to 998 max and see what happens. I cannot go over 1113600 max or my phone gets all weird.
smtom said:
try unsyncing everything for a day - see if it still happens
Click to expand...
Click to collapse
ditto.
if your phone is syncing a lot of things (facebook, 5 e-mail accounts, twitter, etc.) it might be slowing things down significantly.
Hello all,
Let me start off the message by mentioning that I have been a (altogether) very happy user of cyanogen mods with my last 3 android phones.
The last and current (but it seems not for long) is an HTC One X, which is over 2 years old.
This poor thing has gone through so many ROMs that I have lost count.
It is currently running on a stable cm10.2.1, upgraded from cm10.1.3.
I have experienced sudden power offs when there were obvious battery drain, battery overheat, weird app installation issues, especially since moving to cm 10.2.1, which also caused the GPS to stop getting any satellite signals.
However, the phone has recently (a couple of weeks) leveled up into a bizarre mode:
It will power off all of a sudden, the battery levels are not low 65-75%, so I would assume it was just some process in the background, and go ahead and start the phone up again to go and check through the logs, or even disable/cleanup dodgy overreacting apps. But to my surprise, the phone passes the quietly brilliant screen, as well as the CM logo with the circling arrow and as soon as you can see the background it shows Powering off - the phone is shutting down.
For those brief couple of seconds I can see the battery indicator (top right corner) showing a small part of it in red, letting me believe the battery's status is critically low. So I let the phone charge for half an hour, and start it up again, with the same result, once the device goes past the logo and the background shows, the Powering off message appears again. The battery indicator is still showing a small red circulating section of the whole.
The next step was to go and check in recovery mode. The battery on the TWRP screen shows almost 70%, and this leads me to assume there is something wrong with the battery. But the phone is not turning off for as long as in recovery mode. I still haven't ruled out the battery issue, and will test it when I get delivered and replace the spare one I have ordered.
Reading through forums and other threads, there were people complaining that they had the same issues when the phone was trying to change from 2G to 3G and the other way around, so I removed the sim card and have restarted the phone, still the same result, powering off after boot.
I also reflashed 10.2.1 thinking that a clean installation will help getting rid of some new app/processes that might be causing this, but exactly the same powering off occurs after booting. The same happens even after a factory reset.
Usually, after half an hour of inactivity the phone would start up normally, but today it has been several hours and the behavior is not improving.
At this point I can't get into the phone other than on recovery, I can't copy from/into its storage anything, not even the nandroid backups I regularly do (and which stupidly I haven't copied over to an external storage). I could try reflashing some stock image, but even that I don't have on the internal storage.
So as you see, I am bit stuck. Phone will not stay ON long enough for me to connect to my machine and save my backups, or load any new stuff.
If you have any other suggestions other than this, or perhaps a workaround to what I have already tried, I would extremely appreciate it.
Cheers,
Mad
I have the same problem..
I have tried everything, but nothing helped me.
Now my battery is 0% and i cant do nothing - cant charge it, cant boot in bootloader.
Something heppened when you changed the bettery?
Hi.
Why is G3 laggy ?
Mainly because of the heat issue it has, at least that's the case with me.
When the phone is at "normal" temperature after using internet and so on,
it gets a little warm. After that the thermat thtottling limits the max cpu freguency
to about 1200mhz. No wonder it gets laggy.
I did some testing.
I ran the Antutu about 20 times in different temperatures.
Before running Antutu, I booted the phone, closed all the apps, in airplane mode and waited 5 min before each test.
When the phone was "hot" I got scores about 32000. When warm, 37000 and when cold, in fridge, I got over 42000 every time.
The fridge also showed that full cpu speed was used, which was not the case when it was warm or hot.
So.
Some of you guys have a good cpu and motherboard, which means no lagging.
Some of us have not so good and that's why we get even reboots because of heat.
Easy fix from LG would be very strict thermal throttling for the reboot problem.
But at the same time we get even more laggy phone, because of lower cpu frequencys.
F..
I can never pick when it will heat up, but when it does the battery just drains (I'm running v10j).
I think it is a screen issue. Something to do with what the processor and screen run. I'm on 30-40% brightness almost all the time (which is a shame).
Benchmarking in the fridge... that is classic...
I'm starting to think it's the LG software on the phone causing the heat and lag, i recently had issues after removing an app (App Updates) then factory resetting after removing this app and factory reset it would break a few function in my phone including making me go through the setup process after every boot and recent apps menu not opening and notification bar somtimes not pulling down (restart sometimes fixes this) and unable to open settings from the notification bar and possibly other things BUT despite these issues my phone was VERY COLD with the screen on!! and MUCH less laggy. but after i reinstalled "App Updates" and factory reset the heat issue came back.
Just to be sure, i tried again with the same results:
I removed "App Updates" again and factory reset and the heat and lag went away again. (but some stuff breaks)
I installed "App Updates" again and factory reset and the heat and lag came back again. (but everything works again)
I'll take up your suggestion and try to freeze App Updates.
How do you freeze app update centre?
With Titanium Backup. In general I don't uninstall any app, I just freeze them. Works the same and I still can go back if something happen.
So. It's only working if we freeze the app then factory reset? After a factory reset it's staying freezed that is?
U don't really need to factory reset after freezing. Just freeze it and it will be as good as uninstalled, but, with always an option to defrost.
He factory reseted because he was facing issues.
Well, I mostly asked because there is no difference.
Completely stock T-Mo m8. Been running Lollipop since the OTA came through, and it has worked fine for the longest time, no problems other than a bit of lag, even after clearing the cache.
A couple of days ago, the phone began to shut down whenever (seemingly) any app was launched when on battery, and then would not boot on repeated attempts. It doesn't seem to make it past the first stage of the bootloader (first HTC screen, pre-animation), most of the time. Sometimes it will make it to the T-Mobile animation and then give up.
While plugged in, it boots and works fine 9/10 times, but sometimes gives some resistance to booting. If it is unplugged and any apps are launched, it shuts down as if the battery were removed. Though, the whole while the battery seems normal, no weird fluctuations or sudden drops in battery level.
If it is unplugged after having booted and it is relatively inactive (no apps launched, or any processes, i.e. alarms, syncing, downloads, etc.), it will remain powered on.
I have attempted to Factory Reset a couple of times, and cleared the cache a couple of times. The problem persists. I can boot into recovery, though I am not rooted.
Is my battery in need of a replacement or some such? I would like to remain fully stock if at all possible. I may be able to get a replacement phone out of T-Mobile, but would also like to avoid that.
Unlocked s-off US model on verizon running viper now, but I've tried all of the other roms and done a whole bunch of RUU flashes back to the original verizon rom.
Now everything seems slower - especially restoring TB backups and app optimization (initial and after clearing cache). Seems to be taking at least twice as long as in the past if not 3-4x longer. Just re-flashed RUU thinking it would fix things but again it's taking forever to optimize apps after a brand new install. Have wiped everything countless times. Also slight stuttering when installing apps from the play store and doing something else. Wasn't like this initially. Is it possible that read speeds were altered somehow? I haven't played with the kernel so far so I'm completely out of ideas.
Check the ram consumption and how hard the cpu is working when your using the phone; was your phone ever running hot on a particular rom? It's possible you may have damaged your cpu, download Cpuz and see how each core of the cpu is working and also do a benchmark and Compare it to other people with the same phone.
Sent from my SM-N920F using Tapatalk