AOSP Stuttering Issues - Nexus 6 Q&A, Help & Troubleshooting

So I want to start this out by saying this isnt a Note 4 vs Nexus 6 thread or a complaining thread about how the Nexus 6 sucks.
This is a thread to try and figure out the culprit of an issue I think a lot of us are having, but not all of us.
I was running Euphoria OS for a while, loved it. But there was one nagging issue, it would stutter. It was almost as if there was a delay and the device couldnt process all the frame and would drop them. It was still responsive, just not fluid at all. It wasn't on every single screen or animation, but it would appear on every unlock, opening certain programs and almost always on swiping in a sidebar menu. It is very very noticeable if you put Phase Beam or Sun Beam wallpapers on, the animation was not even remotely smooth. I tried different Kernels (I was decrypted BTW) and all of them showed the same behavior. I then set my governors to Performance to speed up the ramp up time, no change. I adjusted the DPI, no change. Nothing I could do would get rid of the janky issues.
I chalked it up to the ROM and installed the nightly CM build (1/20), the exact same issue appeared even without signing into my Google account. Just the ROM and GAPPS were flashed. Switched to another AOSP (modified) based ROM (not CM based) and the same issue happened again. It seems that only stock unmodified ROM's run smoothly on my device.
Is anyone else seeing this? Does anyone else have any thoughts as to why I am seeing this. I know I am not alone, a few people on Reddit said they saw the same thing on Euphoria (again its not the ROM's fault, its something else).
My device:
32GB Nexus 6
Sandisk/Samsung
Decrypted Androbench numbers on Franco R9:
Fsync ON - SEQ RD 163.46MB/s - SEQ RW 43.35MB/s
Fsync Off - SEQ RD 152.76MB/s - SEQ RW 198.95

altimax98 said:
So I want to start this out by saying this isnt a Note 4 vs Nexus 6 thread or a complaining thread about how the Nexus 6 sucks.
This is a thread to try and figure out the culprit of an issue I think a lot of us are having, but not all of us.
I was running Euphoria OS for a while, loved it. But there was one nagging issue, it would stutter. It was almost as if there was a delay and the device couldnt process all the frame and would drop them. It was still responsive, just not fluid at all. It wasn't on every single screen or animation, but it would appear on every unlock, opening certain programs and almost always on swiping in a sidebar menu. It is very very noticeable if you put Phase Beam or Sun Beam wallpapers on, the animation was not even remotely smooth. I tried different Kernels (I was decrypted BTW) and all of them showed the same behavior. I then set my governors to Performance to speed up the ramp up time, no change. I adjusted the DPI, no change. Nothing I could do would get rid of the janky issues.
I chalked it up to the ROM and installed the nightly CM build (1/20), the exact same issue appeared even without signing into my Google account. Just the ROM and GAPPS were flashed. Switched to another AOSP (modified) based ROM (not CM based) and the same issue happened again. It seems that only stock unmodified ROM's run smoothly on my device.
Is anyone else seeing this? Does anyone else have any thoughts as to why I am seeing this. I know I am not alone, a few people on Reddit said they saw the same thing on Euphoria (again its not the ROM's fault, its something else).
My device:
32GB Nexus 6
Sandisk/Samsung
Decrypted Androbench numbers on Franco R9:
Fsync ON - SEQ RD 163.46MB/s - SEQ RW 43.35MB/s
Fsync Off - SEQ RD 152.76MB/s - SEQ RW 198.95
Click to expand...
Click to collapse
Well, I get the unlock stutter and some other subtle stutters on every non-stock kernel that I've tried. It happens consistently, then disappears completely once I flash the stock kernel. This is on 5.0.1 stock, though. I've only been on one AOSP ROM briefly and experienced the same.
My device:
32GB Nexus 6
Sandisk/Samsung
Decrypted

you have to play with your cpu, and set it up to run how you like it. it doesnt happen on its own, you have to do it. unless you really like how the roms stock kernel runs.

simms22 said:
you have to play with your cpu, and set it up to run how you like it. it doesnt happen on its own, you have to do it. unless you really like how the roms stock kernel runs.
Click to expand...
Click to collapse
Like I mentioned in the OP though, I have run all AOSP eligible Kernels on various governors and settings with no change. However, If I run any of the kernels on a stock based it runs like butter.

altimax98 said:
Like I mentioned in the OP though, I have run all AOSP eligible Kernels on various governors and settings with no change. However, If I run any of the kernels on a stock based it runs like butter.
Click to expand...
Click to collapse
Yeah you may be right. My brother nexus 5 stock not even rooted look smoother then my phone. I'm running pure shamu with Franco. I'm Also gonna try a stock ROM to see the differences.

altimax98 said:
Like I mentioned in the OP though, I have run all AOSP eligible Kernels on various governors and settings with no change. However, If I run any of the kernels on a stock based it runs like butter.
Click to expand...
Click to collapse
ive run aosp since aosp came out, no stutters. but i run it at 2650mhz(3033mhz now)/300mhz, ondemand/deadline.

funcrusher said:
Well, I get the unlock stutter and some other subtle stutters on every non-stock kernel that I've tried. It happens consistently, then disappears completely once I flash the stock kernel. This is on 5.0.1 stock, though. I've only been on one AOSP ROM briefly and experienced the same.
My device:
32GB Nexus 6
Sandisk/Samsung
Decrypted
Click to expand...
Click to collapse
So if you run CM or any of the others on the default Kernel you are fine, but not on custom kernels... Interesting, I cant recall if I used the stock CM kernel or not. I know Euphoria ships with Lean so It wouldnt matter there.
edit - Dont you lose theme manager though? Or do you use the app to set the SELinux to Permissive?

simms22 said:
ive run aosp since aosp came out, no stutters. but i run it at 2650mhz(3033mhz now)/300mhz, ondemand/deadline.
Click to expand...
Click to collapse
I even tried Performance 2650/1728 with no changes to the stutters.. I don't think its a speed issue.

altimax98 said:
I even tried Performance 2650/1728 with no changes to the stutters.. I don't think its a speed issue.
Click to expand...
Click to collapse
performance is the absolute worst governor to use, ever.

altimax98 said:
So if you run CM or any of the others on the default Kernel you are fine, but not on custom kernels... Interesting, I cant recall if I used the stock CM kernel or not. I know Euphoria ships with Lean so It wouldnt matter there.
edit - Dont you lose theme manager though? Or do you use the app to set the SELinux to Permissive?
Click to expand...
Click to collapse
No, I'm saying that I experience the same stutter you're describing (particularly unlock) on the 5.0.1 factory image using any custom kernel. It goes away once I flash back to the stock kernel.

simms22 said:
performance is the absolute worst governor to use, ever.
Click to expand...
Click to collapse
Oh, I thought it just ran it harder. I usually run Interactive.

It sounds to me like all the different rom makers are including some common change in their kernels compared to the factory kernel. Not all that surprising, since when one person makes a change that everyone likes, everyone will do a pull and bring in ALL the changes from that kernel (including the bad ones).... and or everybody forks someone, who is probably not AOSP. CM tends to be a common place to fork or pull from.

Related

[Kernel][Request] - HTC Stock Sense kernel with GPU+ 5pt multi touch?

Would any dev or anyone who knows a bit about compiling be able to do this? I've tried some other kernels, and generally love some of the features and performance they bring, but none of them has been 100% stable for me. Stock kernel is 100% stable, but lacks the 5 point multitouch which I do use for emulators, and GPU+ which makes a noticeable difference in 3D graphics smoothness.
The closest I found was HeyItsLou's #8 (I might have the number wrong) which runs great, has the multitouch, but no GPU+ Lou's has some other good features that seem to help smoothness and battery life too.
Maybe Lou or someone could throw GPU+ into that kernel? Or just take the stock kernel and add GPU+ and multitouch? Would anyone else be interested in this?
Um what about the. 32 incredikernel?
Sent from my ADR6300 using XDA Premium App
That's what I'm running now but it will randomly peg the CPU (system panel shows Android System as maxed out) and slow the phone to a crawl, requiring a reboot. And no, I'm not running SetCPU. That is the ONLY problem I have with that kernel, but I've never had that happen on the stock kernel. I don't want to deal with the random lockups anymore.
Ziggy's kernel doesn't have the lock ups, but doesn't run as smooth either, and I notice a lot of stutters while gaming.
I don't know why that would be. I compiled it for someone a few days ago and he loves how it runs.
Sent from my ADR6300 using XDA Premium App
what is 5pt multi touch?????
jdog94 said:
what is 5pt multi touch?????
Click to expand...
Click to collapse
Just that, you are able to use five fingers (or "points") simultaneously.
From my understanding, multitouch is affected by the touch panel you have, and also the way it is flashed. There was a compatible recovery floating around a while ago, but it's no longer maintained.
Yeah not all phones support 5pt
Sent from my ADR6300 using XDA Premium App
Phydo - I've actually been running your undervolted version of Chad's kernel for the last few days. I'm still having the same issue. In Chad's thread, there were actually a few people having the exact same issue. It was thought that SetCPU was somehow to blame, but again, I don't even have that installed.
From a performance standpoint, Chad's kernel is the one I've had the best results with and keep going back to, but this issue with the CPU getting stuck at 100% load happens regularly, every 24-48 hours.
bast525 said:
Phydo - I've actually been running your undervolted version of Chad's kernel for the last few days. I'm still having the same issue. In Chad's thread, there were actually a few people having the exact same issue. It was thought that SetCPU was somehow to blame, but again, I don't even have that installed.
From a performance standpoint, Chad's kernel is the one I've had the best results with and keep going back to, but this issue with the CPU getting stuck at 100% load happens regularly, every 24-48 hours.
Click to expand...
Click to collapse
I'd be willing to bet your problem is the ProcessStats.java bug documented in Issue 9733. It is exacerbated by kernels that add extra frequencies. Some ROMs work around the issue by making the time_in_state file unreadable, but SetCPU undoes this workaround every time you open it. 24-48 hours seems about right for the time it was taking for me to run into this problem. I'm now running with an init.d script that redoes the chmod 600 every 5 minutes just in case I open SetCPU and the problem has gone away.
Aweaver33 - would this be something I could easily incorporate into my own ROM? I'm running a mostly stock ROM that I customized by adding an earlier Evo framework and taking out some stuff I didnt want. Would I be able to flash your init.d script? Or since I don't run setcpu, could you explain or point me somewhere I could figure out how to make time_in_state unreadable?
EDIT: nevermind.... aweaver you are awesome for posting that link. I will try to chmod the time_in_state file as outline in that thread and see if I can make it 48 hours without it making the cpu.
Do you know how specifically this is kernel related? I've had this issue with Chad's kernel, and the old KingKlick kernels. I have NOT had the issue on the very old Hydra kernel or any of the stock kernels. I guess its just the number of frequencies they enable? Man if chmod'ing that file is all it took to fix that bug.... you are my friggin hero dude. I've been mostly using Chad's kernel since December and love it but MAN I hated the phone locking up every two days!
bast525 said:
Do you know how specifically this is kernel related? I've had this issue with Chad's kernel, and the old KingKlick kernels. I have NOT had the issue on the very old Hydra kernel or any of the stock kernels. I guess its just the number of frequencies they enable?
Click to expand...
Click to collapse
Yeah, it's mostly just the number of frequencies they enable. Also a potential, but smaller, contributor would be governor settings that result in a more even distribution of frequencies, which would result the overall file size getting larger more quickly. I first noticed this issue when I was doing stability testing that intentially created an even distribution of frequencies and made it less than a day before triggering the bug.
Well, I'm at 36 hours of running now, so far no issues. I did open the time in state file and noted it is still updating, though the permissions were correctly changed.
My only problem now is the leaked GB roms that popped up today... I want to flash one but I REALLY want to see if after six months of dealing with this very annoying bug, if it is finally fixed. I gonna TRY to resist flashing til tomorrow.
Any way to make the change in permissions to the time in state file stick? It undoes the changes on reboot
bast525 said:
Any way to make the change in permissions to the time in state file stick? It undoes the changes on reboot
Click to expand...
Click to collapse
That's where the init.d script comes in. Put the following in a file in /etc/init.d/ and set permissions to 755:
Code:
#!/system/bin/sh
while [ 1 ]; do
chmod 400 /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
sleep 300
done
If there is no /etc/init.d folder, and I create and throw that file in there will it work?
EDIT: nevermind... tried it, didn't work. Created the folder, put the file I'm there, rebooted. Let phone sit five mins, looked at permissions for time in state file, they were still at default. Does it need to have an extension? I just named it "fix".
Sorry, it looks like the /etc/init.d/ directory is not standard Android. The following is the last line in my /bootcomplete.inc.rc file, which looks like what enables running the scripts in the /etc/init.d directory:
Code:
/system/xbin/busybox run-parts /system/etc/init.d
I'm not sure if that line was automatically added when I installed busybox, or if something else put it there.
It's cool, I found an alternate method. There's a very small app in the market simply called "Autostart", to use it you create a script, name it autostart.sh, drop it in a folder you create in /data/, and it runs at boot same as if it were in init.d. I took your script and modified it a bit to make it not repeat every 300 seconds. I don't run SetCPU so I only need it to run once at start up.
I still haven't let the phone run for 48 hours straight to verify this fixed it, but still man thank you for the info, it is greatly appreciated. After reading that Google bug thread you linked, I have very high hopes that this is the fix I've been looking for for six months now.
Thanks again man and I'll report in a day or two as I have no more reasons to reboot for a while.
48 hour mark just passed and still running like a champ

[Q] 2012 Nexus 7 - CyanogenMod fix the laggy speed?

Does changing over CyanogenMod on a 2012 Nexus 7 Wifi 32GB, fix the extreme bad performance?
Or is it time to junk it?
There is 25+ GB free on the device, ran the memory cleanup apps, still junk. Any of the apps I try and use random freeze for 5+ seconds at a time, it is slower than my nexus 4 by far. The nexus 4 runs circles around the nexus 7.
Will installing cyanogenmod fix this?
jimmyjoebob said:
Does changing over CyanogenMod on a 2012 Nexus 7 Wifi 32GB, fix the extreme bad performance?
Or is it time to junk it?
There is 25+ GB free on the device, ran the memory cleanup apps, still junk. Any of the apps I try and use random freeze for 5+ seconds at a time, it is slower than my nexus 4 by far. The nexus 4 runs circles around the nexus 7.
Will installing cyanogenmod fix this?
Click to expand...
Click to collapse
try purity ROM, by far the fastest and smoothest Nexus 7 ROM ive tried
P.S. no matter how much you try, the nexus 7 will NEVER be as fast as the Nexus 4
SnapDragon S4Pro > Tegra 3
The hardware has not changed, so..
Perhaps it's time to factory reset. If you're rooted, just back up with Titanium Backup and restore after if you like.
You can also try a custom kernel that has dynamic fsync or disable fsync, that'll help on IO lag. However, it won't fix it entirely. Factory reset should help there.
Tegra 3 has some bad IO problems, and the storage chips in the Nexus 7 16gb sucks, although you say you have the 32G so I'm surprised there's an issue there. But it's manageable. Trust me, mine drives me nuts too sometimes, so I factory reset about every 4-5 months, depends on when it starts pissing me off.
I have the 16GB 2012 model, and performance has been a problem. I installed KitKat and did a factory reset, that made it run quite nicely for a while.
But today it's started playing up badly, rebooting regularly. I think there might be a problem with RAM, but I can't be sure. Tried to do another factory reset, but that also makes it reboot.
Thinking about trying a different ROM, see if that sorts it out.
Purity ROM is very smooth, does not lag, no random reboots.
I do use purity and faux kernel....
Sent from my C5303 using Tapatalk
Thanks I will give that ROM a go.
I have performed quite a few factory resets, this does speed things up for a few weeks, then it slowly starts to slow down and then become pretty much unusable, like it is now.
I have left it plugged in and powered on in the hopes that the trim flash process would kick in and perform magic, but no magic results there.
The problem is NOT a ROM. It's the hardware.
Certain ROMs might be better about certain things.. Less stuff running, perhaps the kernel has different options etc.. But the problem is the device itself. Different ROMs might be slighly tweaked to make things better, or may just mask it with fsync.
That said, I like dynamic fsync, even if it's a potential loss of data. m-kernel has that. Franco's kernel has the ability to turn off fsync, but it's on by default.
Try flashing Legolas93's f2fs kernel and recovery here. Made a huge difference to the responsiveness and speed of my 32gb N7 running the latest CM11!

No matter what I do, I always have problems

hello all, ive just been having these issues, their always random, either its screen of death, random reboots, google services f/c'ing, it doesnt matter what rom i flash, or if i fastboot back to stock, nothing changes, theres always "something" that goes wrong. I've tried, and tried and tried but something always seems to be messed up with this phone. I dont know what im doing wrong, I've been flashing roms for years and never had so many problems, except, I had these same issues on the nexus 5, same thing.
anybody ells going through this? or is it just me?
i have both nexus 5 and nexus 6, i know both of them very well, is there anything i can help you with? ive figured out solutions to the majority of random things theyve thrown at me..
Thanks for the help. Well, every rom i try has browser f/cs, google play f/cs random reboots sometimes it reboots and wipes cache for some reason. Sometimes its like system ui f/cs so it just does a "soft" reboot, i have audio issues even on stock, like when i get a call, the ringtone starts out real quiet then boosts all the way up, sound is distorted over 50%, i tried to up my voltage by 15mv global and that didnt help anything..... Im not sure what to do, i already switched out the phone once, i think im at the end of my 15 day byers remorse period
Sent from my Nexus 6 using Tapatalk
Andromendous said:
Thanks for the help. Well, every rom i try has browser f/cs, google play f/cs random reboots sometimes it reboots and wipes cache for some reason. Sometimes its like system ui f/cs so it just does a "soft" reboot, i have audio issues even on stock, like when i get a call, the ringtone starts out real quiet then boosts all the way up, sound is distorted over 50%, i tried to up my voltage by 15mv global and that didnt help anything..... Im not sure what to do, i already switched out the phone once, i think im at the end of my 15 day byers remorse period
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Ima jump in here and try to provide a helpful response.
The nexus 6 is the best device I've ever owned beside my beloved g2, I did have to get my nexus 6 replaced the second day I had it because of a battery issue, but no problems ever since.
As far as the Gapps force closing, try using a different set of Gapps. I prefer to use the latest version of the multirom twrp and always use Banks Gapps(pm me if you can't find them.)
Only onn two, maybe three, roms have I had soft reboots/blackscreens/systemui closes. And most of the time they can be solved with a different kernel and a bit of tuning with an app such as faux123 or kernel auditor.
Audio problems can be hard to fix, but let's make sure you can distinguish the problems from the features. An example of a common misconceptions is the audio "clipping" or "lagging" when rotating the screen. This is a feature, it is swapping the left and right channels to keep the audio correct. There is a build prop line you can edit to diable this.
The phone ringtone volume steadily increasing is also a feature in most roms, including stock. It can be found in Settings>sound and notifications> and somewhere near the vibrate option.
Sound distortion is a problem I suffered from on older roms. I eventually started using viper4android on ALL of the roms I install with the superior audio driver (power drain is unnoticeable). All the settings are super easy to use, and easy to discover while playing a song and listening to the differences. Just make sure selinux is set to permissive.
I don't think increasing/decreasing the voltage can be any good for the hardware. If your car says "premium only" then you shouldn't run regular or racing fuel, you should stick to what was intended to work. You can kill battery life, starve the cpu/gpu, increase lag and overheating when messing with voltages.
Try this.
Go get the LATEST version of twrp, go find the Pure nexus rom and download it and Banks gapps, also go find francos kernel and download the latest release.
WIPE EVERYTHING TWICE (cache, dalvik, system, data) and install ROM>KERNEL>GAPPS and reboot into your super stable phone!
Message me for anything else!
Andromendous said:
Thanks for the help. Well, every rom i try has browser f/cs, google play f/cs random reboots sometimes it reboots and wipes cache for some reason. Sometimes its like system ui f/cs so it just does a "soft" reboot, i have audio issues even on stock, like when i get a call, the ringtone starts out real quiet then boosts all the way up, sound is distorted over 50%, i tried to up my voltage by 15mv global and that didnt help anything..... Im not sure what to do, i already switched out the phone once, i think im at the end of my 15 day byers remorse period
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
what bin number does your phone have? try raising your cpu, inly at your highest cpu, by 20-30mV more. about it wiping the cache, what build android are you on? it used to do that to me all the time, but not since android 5.1.1 hit aosp.
noidea24 said:
Ima jump in here and try to provide a helpful response.
The nexus 6 is the best device I've ever owned beside my beloved g2, I did have to get my nexus 6 replaced the second day I had it because of a battery issue, but no problems ever since.
As far as the Gapps force closing, try using a different set of Gapps. I prefer to use the latest version of the multirom twrp and always use Banks Gapps(pm me if you can't find them.)
Only onn two, maybe three, roms have I had soft reboots/blackscreens/systemui closes. And most of the time they can be solved with a different kernel and a bit of tuning with an app such as faux123 or kernel auditor.
Audio problems can be hard to fix, but let's make sure you can distinguish the problems from the features. An example of a common misconceptions is the audio "clipping" or "lagging" when rotating the screen. This is a feature, it is swapping the left and right channels to keep the audio correct. There is a build prop line you can edit to diable this.
The phone ringtone volume steadily increasing is also a feature in most roms, including stock. It can be found in Settings>sound and notifications> and somewhere near the vibrate option.
Sound distortion is a problem I suffered from on older roms. I eventually started using viper4android on ALL of the roms I install with the superior audio driver (power drain is unnoticeable). All the settings are super easy to use, and easy to discover while playing a song and listening to the differences. Just make sure selinux is set to permissive.
I don't think increasing/decreasing the voltage can be any good for the hardware. If your car says "premium only" then you shouldn't run regular or racing fuel, you should stick to what was intended to work. You can kill battery life, starve the cpu/gpu, increase lag and overheating when messing with voltages.
Try this.
Go get the LATEST version of twrp, go find the Pure nexus rom and download it and Banks gapps, also go find francos kernel and download the latest release.
WIPE EVERYTHING TWICE (cache, dalvik, system, data) and install ROM>KERNEL>GAPPS and reboot into your super stable phone!
Message me for anything else!
Click to expand...
Click to collapse
Thanks for the info. As for the google f/cs, so far that was only on one rom, and i havent had it since. Only browser f/cs are what im dealing with now. As for the sound. I understand the differences between the features, this is not a feature, i know what you mean by increasing ringtone, my issue is nothing like that, its not like, the sound slowly gets louder and louder... It starts out real quiet, and then BOOM full volume. Sometimes the speakers pop a little. Its weird, because it only does this the very first time a sound is played, if i have for instance, touch sounds enabled, and go through my ringtones, i dont have any sound issues. But if i turn off touch sounds, then go back to ringtones, the very first one i select will be reeeeal low.... And then BOOM full volume. This was the very first thing i checked when i switched out phones, and the very first time i tryed it on the brand new phone it did this very same thing. I just assumed it was a known issue.
Sent from my Nexus 6 using Tapatalk
simms22 said:
what bin number does your phone have? try raising your cpu, inly at your highest cpu, by 20-30mV more. about it wiping the cache, what build android are you on? it used to do that to me all the time, but not since android 5.1.1 hit aosp.
Click to expand...
Click to collapse
bin number? do you mean BUILD number? I have the tmobile variant of the nexus 6, before i started flashing roms, the first thing i did was download the factory image of 5.1.1 for the tmobile version, which is (LYZ28E), then i found the unenforced encryption boot.img someone posted which is the same boot.img, I unlocked, flashed the stock 5.1.1 image, unencrypted the device, then went on to flashing roms, right now, im on cyanideL which is LYZ28E, and so far, ive had two reboots, one of them had wiped cache by itself apon rebooting, same sound issues, same browser force closing, i even tried chrome, which force closed the second i loaded a web page, other than that, taptalk, g+ hangouts all work fine, its just these 3 or 4 same issues with pretty much all roms
Andromendous said:
bin number? do you mean BUILD number? I have the tmobile variant of the nexus 6, before i started flashing roms, the first thing i did was download the factory image of 5.1.1 for the tmobile version, which is (LYZ28E), then i found the unenforced encryption boot.img someone posted which is the same boot.img, I unlocked, flashed the stock 5.1.1 image, unencrypted the device, then went on to flashing roms
Click to expand...
Click to collapse
ok, got ya.
which browser do you use btw?
simms22 said:
ok, got ya.
which browser do you use btw?
Click to expand...
Click to collapse
sorry, i edited my post above, I try to use AOSP, which seems to be the best, it force closes the least, but chrome immediately f/c's, firefox works pretty good too, but it has graphical glitches all over the place,
ugh..... so i just wiped everything twice and flashed pure nexus rom, and i have no service, at all... . it just never ends.
Andromendous said:
ugh..... so i just wiped everything twice and flashed pure nexus rom, and i have no service, at all... . it just never ends.
Click to expand...
Click to collapse
reboot.
try this rom, with the latest gapps, and supersu, its Terminus https://goo.gl/ojD6Z6
now i know that this rom has no issues. if you start developing issues, its either something that your doing, or defective(or something else?).
simms22 said:
reboot.
try this rom, with the latest gapps, and supersu, its Terminus https://goo.gl/ojD6Z6
now i know that this rom has no issues. if you start developing issues, its either something that your doing, or defective(or something else?).
Click to expand...
Click to collapse
well, its definitely getting interesting. I just tried optipop, and my sound was working normaly! but to my amazement, it was very laggy and system animations werent working correctly, if i backed out of a screen, sometimes it would slide down, sometimes the creen would just flash white and would switch to the last screen, if that makes any sense. I got the same thing as all roms, no network, but i went and searched for networks and it failed, but then my network signal popped up, and when i tried it a gain, tmobile popped up.
so now im trying tremindous, and its doing the same thing with the network, im testing everythnig ells now.
BTW, what kernel would you suggest?
Andromendous said:
BTW, what kernel would you suggest?
Click to expand...
Click to collapse
either elementalx, vindicator, despair, or lean kernel.
simms22 said:
either elementalx, vindicator, despair, or lean kernel.
Click to expand...
Click to collapse
Why not Franco kernel? Just a question
gee2012 said:
Why not Franco kernel? Just a question
Click to expand...
Click to collapse
he doesn't include ondemand and no oc. i know his conservative is similar to ondemand, but its not the same. and i strictly use ondemand. about oc, he made me an oc kernel that i used for a little, but its old now. amyways, i dont really use his kernel, but we are still friends
simms22 said:
he doesn't include ondemand and no oc. i know his conservative is similar to ondemand, but its not the same. and i strictly use ondemand. about oc, he made me an oc kernel that i used for a little, but its old now. amyways, i dont really use his kernel, but we are still friends
Click to expand...
Click to collapse
How is OC for batterylife? Is there a big difference when you OC to say 3Ghz and what about heat issues or do you undervolt?
gee2012 said:
How is OC for batterylife? Is there a big difference when you OC to say 3Ghz and what about heat issues or do you undervolt?
Click to expand...
Click to collapse
i get from 5-6.5h sot using 3033mhz/300mhz ondemand/deadline. and the n6 doesnt have a heat issue. in fact, i have a hard time getting it over 75C whwn im pushing it to try and get hot.
simms22 said:
i get from 5-6.5h sot using 3033mhz/300mhz ondemand/deadline. and the n6 doesnt have a heat issue. in fact, i have a hard time getting it over 75C whwn im pushing it to try and get hot.
Click to expand...
Click to collapse
Ok, running Terminus with the latest hellscore kernel and i cant believe it but everything is working good so far. Gonna test some more now. Thanks for the help simms
Andromendous said:
Ok, running Terminus with the latest hellscore kernel and i cant believe it but everything is working good so far. Gonna test some more now. Thanks for the help simms
Click to expand...
Click to collapse

My Nexus 6 Is Terribly Slow

Couple couple of things here:
1) I bought a nexus 6 from the Google Play store. I got a few updates since then and also rooted the phone. What I did not notice is the build number. The build number on my phone is: LYZ82J. I searched and found that this is a T-Mobile build. This is really strange because this is not a t-mobile phone. Although my carrier IS T-mobile.
2) The reason why I noticed the build number is this: I wanted to disable the forced encryption. My nexus is running EXTREMELY slow! Its just lags after lags. And I figured maybe disabling the encryption might help.
3) I tried everything to speed up the phone. At this exact moment I have 54.64GB of storage and 1.8 GB of ram Free on my device. I have uninstalled all of the third party apps that run on background, such as Facebook. Other than the root, everything else is completely stock on this phone. I do not have anything running in the background for things like Tasks, Launcher, Gestures, etc.
4) I ran a test on Geekbench 3. Every app was closed. And no third party app was running in the background and I got 774 for single core.
Questions:
1) Why do I have T-Mobile's build on my phone. And is this the reason that the phone is slow.
2) Why is my Pure Stock Nexus 6 so slow.
3) Can I download a factory image from Google's Website and Flash a Different build number on my phone?
3) If not, how can I disable encryption. And will it help speed up my phone?
Thank you so much for your answers in advance.
Mine also has random slow downs. I can't stand it, there's no way such a powerful device should stutter from time to time. I'm running the M3 preview, rooted, i don't think i'm encrypted.
azizmuradov said:
Couple couple of things here:
1) I bought a nexus 6 from the Google Play store. I got a few updates since then and also rooted the phone. What I did not notice is the build number. The build number on my phone is: LYZ82J. I searched and found that this is a T-Mobile build. This is really strange because this is not a t-mobile phone. Although my carrier IS T-mobile.
2) The reason why I noticed the build number is this: I wanted to disable the forced encryption. My nexus is running EXTREMELY slow! Its just lags after lags. And I figured maybe disabling the encryption might help.
3) I tried everything to speed up the phone. At this exact moment I have 54.64GB of storage and 1.8 GB of ram Free on my device. I have uninstalled all of the third party apps that run on background, such as Facebook. Other than the root, everything else is completely stock on this phone. I do not have anything running in the background for things like Tasks, Launcher, Gestures, etc.
4) I ran a test on Geekbench 3. Every app was closed. And no third party app was running in the background and I got 774 for single core.
Questions:
1) Why do I have T-Mobile's build on my phone. And is this the reason that the phone is slow.
2) Why is my Pure Stock Nexus 6 so slow.
3) Can I download a factory image from Google's Website and Flash a Different build number on my phone?
3) If not, how can I disable encryption. And will it help speed up my phone?
Thank you so much for your answers in advance.
Click to expand...
Click to collapse
1. I don't know the logic behind the updates, but since your on t-mobile, the updates appear to pull toward your carrier. Doesn't seem to matter that you have non branded.
2. I have always found stock to be much slower than roms. I know it's a pain, but it does help to wipe the phone from time to time.
3. Yes
4. You have use a kernel that doesn't force encrypt, and do a complete wipe to get rid of the current encryption. i dont believe it will speed up the phone to any noticeable amount.
My suggestion would be to go with a well made ROM (there are plenty).
I suggest Pure nexus ROM with hells kernel.
It will give you a stockish feel without all the stock lag.
My geekbench below, running pure and hells.
OTA builds are decided by your sim. T-Mobile sim get T-Mobile build.
Geekbench score running JDX 3.0.4. http://forum.xda-developers.com/nexus-6/development/rom-jdx-1-0-t3121053
im glad that i was off today, from both work and xda. otherwise, id explain about whatever you ask..
I get a pretty good score running stock and always have. Maybe try reflashing a factory image and start over?
Toaplan said:
I get a pretty good score running stock and always have. Maybe try reflashing a factory image and start over?
Click to expand...
Click to collapse
are you running a custom kernel or completely stock? if completely stock, do yoj mess with your cpu at all?
simms22 said:
are you running a custom kernel or completely stock? if completely stock, do yoj mess with your cpu at all?
Click to expand...
Click to collapse
I'm completely stock by manually flashing the image files one by one from the Google factory images page. No custom kernel or CPU tweaking. I did root and decrypt using WugFresh NRT.
EDIT: I guess decryption requires a custom kernel technically...
Always remember, those benchmarks mean nothing. the benchmark scores can easily be manipulated by the software optimization and a little system tweaks. A phone with 4 cores can get a higher score than a phone with 6 cores thanks to the system tweaks (in android particularly done in build.prop) and better software optimization. So for me benchmarks are nothing more than a little estimate and their value doesn't mean anything in the practical world.
And if you want to keep your phone upto date without any issues,you should download the nexus 6 toolkit, its the best thing to restore your phone whenever it gets bricked. It's a simple click procedure with one click rooting to boot loader unlocking, try it.
dixonl90 said:
Mine also has random slow downs. I can't stand it, there's no way such a powerful device should stutter from time to time. I'm running the M3 preview, rooted, i don't think i'm encrypted.
Click to expand...
Click to collapse
Mine slows to a crawl from time to time, event the soft buttons not responding to touch for several seconds. The boot animation is similarly slow.
It's always been like this as far as I can remember. I am running CM 12.1 nightlies, encrypted.
I guess it depends on your definition of slow. I am just running plain Old stock rooted 5.1.1 encrypted and my device is fast and smooth.
I would suggest wiping the phone and starting over from stock.
Yeah I would wipe and start from scratch. In addition, I would force fstrim on /data and fsck /data /system and/cache.
Sent from my Nexus 4 using XDA Free mobile app
I never notice any lag on my nexus 6, its stock on page plus. I have no issues with this phone at all. My moto x pure that I had was a laggy turd, I traded it for a nexus 6
I bought my N6 about a month ago, it was running 5.0.1 during the setup it went through 6 updates until it was on 5.1.1 and build was LMY48M and it's lightning fast. I'm also on Fi network with no problems. Maybe your sim card is bad or carrier is slow. You might want to flash the latest build and a new sim.
Good Luck
Sent from my Nexus 6 using XDA Free mobile app
Removing encryption will definitely speed up your phone without reducing battery performance (maybe even improving it).
I'm using N6Shamu Rom with LeanKernel and find a nice balance of performance and battery life.
If you just want performance try Pure Nexus Rom
My Nexus 6 slows down a lot also. I ran geekbench 3 and was getting 700s for single core, well below avg.
This seems to happen after getting a bit warm. If I run geekbench about 2-3 times, the phone starts slowing down a lot. I'm thinking I have a hardware issue.
But other times the phone is buttery smooth as are high demanding games. Who knows.

[LineageOS] Stutter or lag when swiping or scrolling

Hi. I flashed LineageOS 16 recently (clean flash) and the ROM is really good in a lot of aspects, I'm really digging it. But something that bothers me is that sometimes when scrolling through an app or swiping (like on Instagram) there's a noticeable frame drop or stutter. Interesting enough, it happens only on certain apps and moments and not always but it's enough to bother me since stock was so smooth (coming from Oreo Stock).
Is it something that normally happens with this phone? If so, is there a fix for it? Maybe a Magisk module or something.
I appreciate your help, thanks in advance.
For the stutter and performance issues, I recommend the LKT magisk module. I personally use the performance preset on lineage os, and it works fine.
T1Coreon said:
For the stutter and performance issues, I recommend the LKT magisk module. I personally use the performance preset on lineage os, and it works fine.
Click to expand...
Click to collapse
I mean, it does work but not to the extent I'd like. Isn't Moto X4 capable of handling this ROM? Or is it something else's fault?
You're not alone, I've had the exact same experience.
The fist post in the LOS thread says to use Oreo firmware. Not sure of that is no longer correct since it's LOS 16 which is Pie.
I ended up going back to stock Android One.
Out of curiosity do you have a 3GB ram or 4GB ram version?
cdkg said:
You're not alone, I've had the exact same experience.
The fist post in the LOS thread says to use Oreo firmware. Not sure of that is no longer correct since it's LOS 16 which is Pie.
I ended up going back to stock Android One.
Out of curiosity do you have a 3GB ram or 4GB ram version?
Click to expand...
Click to collapse
I have the 3GB version. However, I almost sure it's not a RAM issue since one of the things LOS does very good is keeping apps in the background, actually in that regard is better than stock IMO, though I've only tried stock Oreo on this phone.
This problem is a little one but it annoys me quite a bit since when I was running stock ROM the overall performance was always snappy. I should try wiping cache/dalvik with TWRP but I haven't had the chance atm.
BTW, how's stock Pie? I'm curious.
I have found that if you go into developer options and disable HW overlays, that fixes it. However, for some reason, that setting seems to revert back after some time. So that might be a bug.
One_Vision said:
I have the 3GB version. However, I almost sure it's not a RAM issue since one of the things LOS does very good is keeping apps in the background, actually in that regard is better than stock IMO, though I've only tried stock Oreo on this phone.
This problem is a little one but it annoys me quite a bit since when I was running stock ROM the overall performance was always snappy. I should try wiping cache/dalvik with TWRP but I haven't had the chance atm.
BTW, how's stock Pie? I'm curious.
Click to expand...
Click to collapse
I really like the most recent stock FI PPW29.69-39-1. It's pretty snappy and the double-tap-power-button- to-open-camera works faster than previous builds.
Im seeing some pretty poor UI performance as well. Especially in Firefox and K9 email. I didn't see any strain in the CPUs (none went over 20% utilization while I was experiencing the lag). LOS 16 is pretty young, might be some optimations just aren't there yet? Today's changelog was dense so people are absolutely working hard on it.
Edit: FWIW Firefox and k9 are slow on Havoc as well but Havoc's performance has been otherwise stellar. 3D performance included.
i noticed it only happen when battery saver is on. try it
Activate Developer Options, set all values for animation times to zero, phone is more fluent afterwards.

Categories

Resources