I am running stock 5.0.1 on my T-Mo Note 4, and the things horribly, awfully slow. It's glitchier than ever too. It randomly restarts and sometimes it's so slow my screen turns off before a menu appears after I click it. Also my phone reboots randomly! It's like a soft reboot, once it turns back on, I'm right where I left off.
Is anyone else experiencing this? I really wanted Lollipop but this is just the worst thing I have ever seen.
Any suggestions? I'm relatively new to the whole scene, but I got TWRP recovery installed, I know how to flash with odin (already bricked and un bricked my phone).
I miss Xposed, but the new xposed with lollipop and Touchwiz set up seems extremely daunting.
So my question is, should I go back to stock kitkat so I can use Xposed again, or is there a better custom rom?? I tried alliance, which really intrigued me but it got stuck at the boot screen (surprise).
I'd flash pop rocks 7x. Mega is doing an amazing job with issues such as yours. And you can run xposed with it.
Just follow the instructions in the op.
http://forum.xda-developers.com/showthread.php?t=3096286
It's the first rom I flash for people. It's a great way to start and often my dd.
Wifi calling for 5.0.1 is super glitchy, every morning I wake up and wifi calling has reg99 or 82 error. Is there a ROM with working wifi calling and stable. Would like the double tap to wake option if there is such a rom for the tmobile note 4.
DaltonMplz said:
I am running stock 5.0.1 on my T-Mo Note 4, and the things horribly, awfully slow. It's glitchier than ever too. It randomly restarts and sometimes it's so slow my screen turns off before a menu appears after I click it. Also my phone reboots randomly! It's like a soft reboot, once it turns back on, I'm right where I left off.
Is anyone else experiencing this? I really wanted Lollipop but this is just the worst thing I have ever seen.
Any suggestions? I'm relatively new to the whole scene, but I got TWRP recovery installed, I know how to flash with odin (already bricked and un bricked my phone).
I miss Xposed, but the new xposed with lollipop and Touchwiz set up seems extremely daunting.
So my question is, should I go back to stock kitkat so I can use Xposed again, or is there a better custom rom?? I tried alliance, which really intrigued me but it got stuck at the boot screen (surprise).
Click to expand...
Click to collapse
From battery to boot its all about a custom kernal in my opinion.
@jovy23 has a killler rom for the N4 Tmo. DarthStalker V2
If you wipe properly using twrp.
And flash emotion kern R16.
With synapse controller app.[emoji106]
Youll be blown away.[emoji41]
Even stock its one of the Most loaded and clean running Roms out on the market...
Nice built in themes as well..
If youd like to know good flashing procedures hit me on the Pm..
[emoji16]
Flashvetrin
Flashvetrin said:
From battery to boot its all about a custom kernal in my opinion.
@jovy23 has a killler rom for the N4 Tmo. DarthStalker V2
If you wipe properly using twrp.
And flash emotion kern R16.
With synapse controller app.[emoji106]
Youll be blown away.[emoji41]
Even stock its one of the Most loaded and clean running Roms out on the market...
Nice built in themes as well..
If youd like to know good flashing procedures hit me on the Pm..
[emoji16]
Flashvetrin
Click to expand...
Click to collapse
Agreed. He just released a new version 18, but the wifi calling is still under construction and working on r16
Related
I don't have the time to constantly be looking for new roms to make my phone run properly. My phone is always freezing up due to the stupid Touchwiz UI and I absolutely hate it. I am sick and tired of my phone freezing up and lagging constantly and having to do factory reset and reinstalling all my apps fresh.
So I was wondering, what can I do to fix this problem in a easier manner? I was thinking about rooting the phone, saving all my app data, unrooting, resetting the phone, rooting again, uninstall bloatware, reinstalling apps with their data, and unrooting.
Here are my concerns though. I want to be able to reset the phone using the orignal factory reset. I don't have time or care to install new roms on my phone as I want to keep my warranty and I want to be able to sell my phone in the future.
So what are my options here? What can I do and what are my steps to start doing them?
I am on AT&T Note 3 with kitkat 4.4.2 with my build number ending in NC2.
Is the Note 3 development this bad? Not one response in a couple days. Anyone have a simple answer?
I just want to know if I can factory reset if I root my device and how I could complete unroot.
joshlete said:
Is the Note 3 development this bad? Not one response in a couple days. Anyone have a simple answer?
I just want to know if I can factory reset if I root my device and how I could complete unroot.
Click to expand...
Click to collapse
Simple answer is root with towelroot, and when you want to do a complete factory reset, flash stock NC2 using the guide in this thread.
I think your original question about what options you have is a little more complicated...rooting your phone technically voids your warranty, but if you're referring to the KNOX warranty flag then towelroot doesn't trip that flag. Reflashing stock NC2 with Odin will unroot your phone automatically so no worries there either. What I'm getting at is flashing roms isn't going to void your warranty any more than rooting with towelroot will, on the other hand uninstalling system apps can cause lots of problems, so you may find it easier to flash a near-stock rom that has the bloatware already removed.
But if you're set on not flashing anything, then I'd suggest using titanium backup to freeze any apps you don't want instead of uninstalling them. If you uninstall the wrong app you could end up having to do a factory reset anyway just to get your phone working again. Freezing system apps can cause problems too but it's generally easier to unfreeze an app than try and find and reinstall a system apk. And as tempting as it is don't uninstall My Magazine you'll get FC all over the place and your email won't work properly
So if I install that stock rom, would I be able to update my phone using the internal updater? I just want to be able to install Android 5.0 when/if it comes out for the Note 3. Seeing how AT&T note 3 has little to no roms to install. Very disappointing.
The Odin files in that thread are for stock NC2 and unless you flashed a rom after your second post you're still on stock...it's the exact same AT&T stock build...flashing it won't really benefit you at all unless you rooted and made changes to your system. I assume by internal updater you mean the OTA updates that get pushed out from AT&T then yes since that is the official AT&T build if you flash it you will still get those updates provided AT&T is your carrier. There may not be a lot of roms but the ones we have are great I'd encourage you to try one or two there are a couple "debloated" stock roms I think would give you what you're looking for in terms of stability but of course it's up to you if you just want to stay stock
joshlete said:
So if I install that stock rom, would I be able to update my phone using the internal updater? I just want to be able to install Android 5.0 when/if it comes out for the Note 3. Seeing how AT&T note 3 has little to no roms to install. Very disappointing.
Click to expand...
Click to collapse
Wow... just... wow.
This POST is disappointing.
I'm on the same boat as you OP. When time comes for a new phone, my next phone will never be another Samsung phone again. I will only consider phones that are close to stock. Most likely Motorola X or Sony Z3 Compact or similar.
TouchWiz is so disappointing. It's slow and creates lags even for just checking what time it is.
Fortunately I have some time so unlike OP, I tried debloating stock rom, tried at least 5 custom roms. Most of the custom roms have either too much theme customization (really not my taste) or something else doesn't work (NFC payment or deep sleep or some other thing). And they all claim super duper fast and rock stable, but those are hyperboles. The only time I experienced one rom being faster than the other was with Galaxy S5 port rom, but that was most likely due to the fact that standby mode is disabled because we have no way to update the firmware. In other words, uses more battery but still lasts a day. Also, I never seen the battery last exceptionally longer than the stock rom, so don't trust the super long lasting battery claims.
The easiest way to get your phone run smoothly is to factory reset it, and then only install select apps that you really need and know that it won't be a resource hog reporting your every move.
Oh, and last year's Moto X (dual core) feels faster than a quad core Note3 for everyday task in my hands. I wish we had a google experience rom for n900a.
brisinger08 said:
The Odin files in that thread are for stock NC2 and unless you flashed a rom after your second post you're still on stock...it's the exact same AT&T stock build...flashing it won't really benefit you at all unless you rooted and made changes to your system. I assume by internal updater you mean the OTA updates that get pushed out from AT&T then yes since that is the official AT&T build if you flash it you will still get those updates provided AT&T is your carrier. There may not be a lot of roms but the ones we have are great I'd encourage you to try one or two there are a couple "debloated" stock roms I think would give you what you're looking for in terms of stability but of course it's up to you if you just want to stay stock
Click to expand...
Click to collapse
Could you link me to some stock roms? I lost my game in rom finding and can't seem to get a good running/looking rom.
RErick said:
Wow... just... wow.
This POST is disappointing.
Click to expand...
Click to collapse
Most useless post of the year goes to......
joshlete said:
Could you link me to some stock roms? I lost my game in rom finding and can't seem to get a good running/looking rom.
Most useless post of the year goes to......
Click to expand...
Click to collapse
UR Droid is probably the closest to stock...Knox removed, sd card write permissions fixed, etc. are the only mods...that said carl's made a ton of flashable zips too so if you did want to start making mods yourself chances are you won't have any problems while running his rom
FireKat is one you've probably run across. That is a stock rom all of the mods/optimizations/etc mega makes are from other stock builds. There's no theming or anything like that it's more like "TouchWiz optimized"...again nothing extraneous added if you want to add tethering, call recording, etc you'll have to do it yourself. FireKat is geared towards speed and battery life but it's rock solid with no known issues. All of the rom updates you see are for performance improvements as opposed to the majority of the aosp-hybrid or heavily themed roms where updates are for bug fixes.
Both devs are really helpful and responsive definitely check out their threads though since I'm not up to date with both roms. I have flashed both of them at some point and both are significant improvements over stock...of course no one can tell you what roms you'll like or should flash but I'd be pretty surprised if you have a better experience on stock than either of these roms.
I've been running a stock rooted 4.4.2 for months and it was not laggy at all.
In the application manager settings I turned off all bloatware apps that I did not use. I froze (with titanium backup) all bloatware that could not be turned off in settings and also froze anything that says "knox" in the title. I used xposed installer to install many modules that allowed me to tweak my stock rom... including greenify to auto hibernate apps, smart booster to manage ram, boot manager, and also Wanam xposed for ui customizing...
My phone has run extremely well.
I just made the jump to 4.4.4 and got it rooted (thanks to @muniz_ri and a few others).... exact same setup again... stock rooted... turn off and freeze un-needed apps... xposed modules... and again it is running nice and smooth.
I also use nova launcher prime because it feels more responsive and does more things that I want (like a home screen that will autorotate to landscape mode).
Wow, that's a lot to have for being stock .
The only way to get rid most of your concerns is to root your phone. Then you can delete all other useless apps that you don't need and slow your phone down a bit.
But installing a new Rom is the best way to have a peace in mind I think. Dynamic KitKat is one of the best roms for our phone. I've been using it for months and there is nothing I can say how much I like it. Sometimes I experience lag, but that is to be expected because of Android's ability to do multitasks.
Just my 2 cents.
hey guys hope all is well
so i may have somewhat softbricked my g4 dont really know how but i will explain what i did
hopefully someone can point out where i went wrong and how to fix it
Step #1
got root using this guide previously used the guide to get root on my ATT LGG4 worked fine
so got root, was successful everything worked fine
step #2
installed flashify
granted root access; all good
installed TWRP via flashify; all good
step #3 backup via TWRP all good
step #4 flashed G4H811 10N xTreme ROM v2.0 from this via TWRP; All good
step #5 attempt to install xposed framework 64bit from xposed respository via TWRP
supposedly installed fine but thats where the problems started to occur
random crashes of main apps system apps touch screen stops responding android.system crashes etc
step#6 try to flash back to prior TWRP backup
flashed back but same problems still occur
#step 7 flashed back to xtreme rom still same problems
#step 8 flashed to H811 10N stock Restore found herehttp://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-10n-stock-restore-t3191756
still same problems even though twrp and root are now gone because "clean install of stock rom"
did i **** up during the xposed install? how do i fix this
thanks a ton guys
-ben
armadilloben said:
hey guys hope all is well
so i may have somewhat softbricked my g4 dont really know how but i will explain what i did
hopefully someone can point out where i went wrong and how to fix it
Step #1
got root using this guide previously used the guide to get root on my ATT LGG4 worked fine
so got root, was successful everything worked fine
step #2
installed flashify
granted root access; all good
installed TWRP via flashify; all good
step #3 backup via TWRP all good
step #4 flashed G4H811 10N xTreme ROM v2.0 from this via TWRP; All good
step #5 attempt to install xposed framework 64bit from xposed respository via TWRP
supposedly installed fine but thats where the problems started to occur
random crashes of main apps system apps touch screen stops responding android.system crashes etc
step#6 try to flash back to prior TWRP backup
flashed back but same problems still occur
#step 7 flashed back to xtreme rom still same problems
#step 8 flashed to H811 10N stock Restore found herehttp://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-10n-stock-restore-t3191756
still same problems even though twrp and root are now gone because "clean install of stock rom"
did i **** up during the xposed install? how do i fix this
thanks a ton guys
-ben
Click to expand...
Click to collapse
Did you flash the bootstack for 10N?
I did NOT flash the bootstack for 10n because the guide said not to if you were already on 10n
I was on 10h, rooted with TWRP.
I then installed Exposed.
After a couple of days, I flashed 10N when it was made available by MicroMod777.
Even though everyone was running smoothly with 10N, I was having:
- touchscreen issues where one of every two touches weren't recognized.
- lag up the wazoo while scrolling, etc.
I was like, wow, this ain't good.
So I uninstalled Exposed, and I was still having the issues.
Then I was going to flash my 10h Nandroid, where I wasn't having zero issues.
But then I figured I'd let 10N settle in, so to speak.
After several hours without any further changes, 10N was running like clockwork without any issues. Smooth as butter.
I mention this as it may pertain to you.
You've made the many changes, so now just let things settle down and see how it goes.
I know that sometimes things just have to settle in. Why for some and not for others? I don't know.
It just is.
You got twrp to work on att?
Sent from my LG-H811 using Tapatalk
I really hope that the issues will disappear its more than the touchscreen is unresponsive every other touch its like not working at all then it will work randomly. Also the power button doesnt seem to open the power menu either.
So as i stand rn im back on the custom room rooted twrp but no xposed. Still the same problems but i have twrp installed which hopefullyis a good thing.
I hope it resolves itself after time but that most likely wont work
And no this is a tmobile g4 i moved over to tmo the other day. Im talking on my att g4 and trying to fix the tmo g4
armadilloben said:
I really hope that the issues will disappear its more than the touchscreen is unresponsive every other touch its like not working at all then it will work randomly. Also the power button doesnt seem to open the power menu either.
So as i stand rn im back on the custom room rooted twrp but no xposed. Still the same problems but i have twrp installed which hopefullyis a good thing.
I hope it resolves itself after time but that most likely wont work
And no this is a tmobile g4 i moved over to tmo the other day. Im talking on my att g4 and trying to fix the tmo g4
Click to expand...
Click to collapse
Do a kdz restore to 10N.
Sent from my LG-H811 using Tapatalk
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
http://forum.xda-developers.com/showthread.php?t=3107848
Sent from my LG-H811 using Tapatalk
is there a guide to do that? i cant seem to find it on here at all
armadilloben said:
is there a guide to do that? i cant seem to find it on here at all
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3107848
Sent from my LG-H811 using Tapatalk
so i did the KDZ restore booted up the phone play services crashes the power or volume buttons still dont work and the touchscreen/general ui are still extremely unresponsive and system.ui crashes like crazy
wtf is causing this i thought the KDZ restore was like a full wipe?
Just thinking out loud.
Was this device possibly plugged into an outlet and received a power surge?
Or did moisture get to it somehow?
Or something similar to the above scenarios?
I'm thinking it may be a hardware issue affecting the software, as compared to strictly a software issue.
Or maybe things just have to settle in for up to 48 hours.
I got my Nexus 6P for Christmas, and I decided to root my Motorola Nexus 6 from last year. I've been waiting to do this for a few months, and was excited to finally enable several of the options I couldn't otherwise enable (such as double tap to wake and auto rotate on the lock screen and Google Now launcher). About an hour ago I got around to rooting and done so with little issues. It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. I rooted following the steps in a YouTube video by DroidModderX and the device is running perfectly fine. The device hasn't died yet, and I'll be interested to see when it will die. The battery life seems to fluctuate between 4,001% and 4,204% (Those two figures being the highest and lowest figures respectively). Rebooting does not fix this error.
I know it's not a massive problem, but I'd like to know what's causing this issue and how to resolve it. I haven't flashed any custom OS's on my phone, I'm still running stock Android 6.0.1 Marshmallow with the latest December security patches. The device is carrier unlocked also. How can I fix this?
Thanks,
Eamonn.
sonic2kk said:
It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. being the highest and lowest figures respectively). Rebooting does not fix this error.
Click to expand...
Click to collapse
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
sansnil said:
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
Click to expand...
Click to collapse
Ah, thank goodness. I'll re-root tomorrow and post back if I have any problems. Thanks!
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Why did you need root for the Google now launcher?
mikeprius said:
Why did you need root for the Google now launcher?
Click to expand...
Click to collapse
What do you mean? I can run the Google Now launcher perfectly fine. Root works fine as well. The problem isn't with the Google Now launcher but with the warning on boot. I didn't need to root, I chose to. Am I misunderstanding?
Your original post made it seem like you need root for double tap to wake and Google now launcher.
sonic2kk said:
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24269982087021512 gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: https://www.androidfilehost.com/?fid=24340319927534323 (flash this also after you flash the bootstack).
HueyT said:
(removed url) gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: (removed url) (flash this also after you flash the bootstack).
Click to expand...
Click to collapse
Worked perfect. That got rid of the corrupt message. One last question: (This is the last one, I swear! ) Are you saying that Android Pay won't work at all after rooting or that it wouldn't have worked if that screen had have appeared on boot? I hope to use the service if and when it comes to the UK.
mikeprius said:
Your original post made it seem like you need root for double tap to wake and Google now launcher.
Click to expand...
Click to collapse
Ah, sorry for the confusion my friend ?
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
orangekid said:
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
Click to expand...
Click to collapse
Haha if it wasn't a display error I might have (Though it would have only been like 3 days on the Nexus 6 )
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Dalek Caan said:
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Click to expand...
Click to collapse
Sorry, I don't remember where I got the updated files now. I do remember sticking to looking on XDA and not just searching randomly online, maybe you could try searching the forums?
is it possible to root with chainfire root files. I did a clean install of the January security update, then flashed the latest boot.img from chainfire then flashed SuperSU 2.66.zip through TWRP, but im still getting this. I received this same issue with the last patch. Im at the point where it isnt worth rooting. Any help would be appreciated.
So I was running LiquidSmooth 5.1.1 CM-based ROM for a longest time. But the times they are a changin. MM stock came. But with it I don't see that many ROMs - 2 so far. Both of each have issues. Iron has bloated from 1.4 GB stock to 2.3GB, what an achievement. Simpler doesn't like OpenGapps. It seems everybody is happy with stock MM.
I'm not. I miserably failed to get rid of Knox, or whatever new AKMS name Gnusmas came up with. That Knox bastard shows its notification every time I setup WiFi. Knox thinks that restarting and reverting the change (WiFi ?) is par for course. Primary cause is TWRP recovery (non standard). So I cannot have root, cannot have TWRP, cannot get rid of bloat, battery life and smoothness suffering, cannot use root apps like TiBu.
I ended up using Schischu's MM, which gave me zero issues, worked with OpenGapps with half-kick, and I have Screen-on-time around 8 hours, which is astonishing.
Just install the stock ROM. Works fine for me. The TWRP and SuperSU install is pretty standard. I have no idea what you're whining about. Maybe you should no use "non-standard"?
tried stock
tried stock - wifi would reset after reboot due to Knox.
Look for sweet rom it is at lollipop but it is Knox free.....
I don't know what knox has to do with wifi. At least, I haven't heard about it yet, and haven't observed it myself.
bravomail said:
tried stock - wifi would reset after reboot due to Knox.
Click to expand...
Click to collapse
There must be something else going on. I'm rooted with Superuser & TWRP on stock MM. I'm not having any wifi or Knox issues.
Sent from my SM-T800 using XDA-Developers mobile app
Hi, I have been seeing significant lag of my phone and various times to the point that my phone becomes inoperable for a period of time and after the phone recovers it never goes back to full speed., I have to restart. I'm stock not rooted anymore and recently formatted and started from scratch but see no improvement. This is especially annoying when running android auto at which point the phone and the app barely work. Any suggestions? I don't think its a better thing because i had it happen at 60 and at 40 though definitely see it more at 40 or less. Is there a good way to see what app might be causing this?
Install a different kernel. Stock is garbage
Sent from my Nexus 6 using Tapatalk
I don't think k I want to root again.
You don't need root to install a custom kernel. In fact you don't even need to install TWRP. Using ADB you can flash the custom kernel. Just make sure you have USB debugging enabled in Developer Options and make sure your bootloader is unlocked.
Strephon Alkhalikoi said:
You don't need root to install a custom kernel. In fact you don't even need to install TWRP. Using ADB you can flash the custom kernel. Just make sure you have USB debugging enabled in Developer Options and make sure your bootloader is unlocked.
Click to expand...
Click to collapse
Same exact issue here. F*** Google for screwing up our stock phones and not fixing them. What would you suggest for a kernal and rom. It has been a long time since I was rooted with a custom rom but I can't take this for another day.
jspector said:
Same exact issue here. F*** Google for screwing up our stock phones and not fixing them. What would you suggest for a kernal and rom. It has been a long time since I was rooted with a custom rom but I can't take this for another day.
Click to expand...
Click to collapse
Hello... I think all ROMs perform the same in term of fluidity and speed. Some have different features and customization options. I run Pure Nexus on my N6, N6P and Pixel XL. All use ElementalX kernel. I like this configuration. But there is a lot of different possibilities.
I suggest you to look at the forum and read a little bit the first posts of the different ROMs/kernels and see what they have to offer. :good:
Good luck...
I've had this same exact issue. I thought about switching back to MM because I had great battery life on MM. I also thought about flashing Franco Kernel and go from there. It is one that has the option to hide that the bootloader is unlocked. I don't really want to have my bootloader unlocked, and I don't think I can make changes to the kernel easily without having it rooted, something else I also don't want to do. Maybe MM is the best option. Google is still sending out security updates for MM.
Well problem solved I should say. Used nexus root kit to root and install Pure nexus. Only issue I had was I had a gapps from 2015 that crashed everything so I reinstalled with a new gapps. Working great and the speed is back.
Then unless you wanted an old copy, you downloaded the wrong version of Pure Nexus. The latest version includes the Google apps in the ROM, eliminating the need to flash a GApps package.