Lagging poor performance. - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

Lagging poor performance. - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

Having major problems with my Note 4. It is often really sluggish. Has horrible lag. Sometimes it just randomly resets. And, when it resets, sometimes it goes straight to download mode and says could not do normal boot at the top. For example, right now it has been on the Samsung galaxy note 4 boot screen for a few minutes. I had to pull the battery for it to boot. Sometimes, when I press and hold the power button, it doesn't respond.
I have tried a number of fixes.
-Factory reset.
-Full wipe
-Format data, then full wipe
-Odin back to stock firmware (KK, LP and MM)
-Restore backup from TWRP
I searched and saw another thread with similar symptoms, but it was pretty old with only one response. I am really at a loss as to what to do. I can only assume it is hardware related. I haven't really dropped it. No water damage. Always in a case.
Any help would be appreciated

I had the exact same issues you are describing. It ended up being the only reason i upgraded to note 7. Now of course note 7 is being recalled & i wish i could go back to a fully functional note 4.
Hope somebody has a solution for this!

The OP describes a bad flash or OTA update, corrupt partition or failing eMMC. I'd advise replacing battery as a first step of troubleshooting. Make sure it's charged fully at least once and have 75% or more capacity before starting.
I've never had to do anything risky with "PIT with repartition" or "nand erase all" but there are other advanced forums for that but I don't venture into recommending risky measures I haven't performed with experienced guidance. You could find these by googling or visiting Sammobile specific forums- I don't think it's acceptable to post external links.
But before I considered risking those methods there's some steps I'd eliminate first (warning: they may seem redundant but if having issues, I'd be thorough even if it appears redundant):
1. Backup and boot system, enable developer mode and enable USB debugging.
2. Disable reactivation lock in Settings/Security.
3. Open SuperSU app and fully un-root.
4. Wipe everything but extSdCard, factory reset and format data and power down and pull battery. Get serial number from underneath battery for Smart Switch.
5. Install Smart Switch on PC.
6. IMO, you should Odin stock tar before using Smart Switch if previously rooted.
7. Use Smart Switch to either install latest update or emergency restore phone. I didn't know Smart Switch worked in Note 4 so refer to Sammobile.
8. Once done, Check stock for stability for days before opting to do anything unless you've duplicated same results. If you have a true hardware issue, it may be evident while trying these steps.
9. Determine if you need to do anything further. I can't help with the riskier stuff; I've been fortunate enough not to experience anything warranting a risky procedure.
Sent from my SM-N910P using Tapatalk

i am now having this same issue on my note 4. i have gone through all of the steps outlined in this thread. The only thing i haven't tried yet is a full repartition. Any thoughts? OP have you had any success?
Thanks,
JD

I succeeded in a full brick lol. That's about it. Wont even charge/power on.

last night i re-odined with a pit file. I had selected re-partition, nand erase and hone EFS clear. I did get a successful odin and the phone had to reactivate with sprint. IN the end i still have the very laggy performance, phone sometimes not responding and spontaneous reboots.
All of this started in an instant. Everything was running fine on a TW rom that i had been running for about a week. I went to use the camera, the app froze and the speaker made a slight static kind of sound and then all of this started. No matter what kind of rom i put on here they now all act the same. very strange.
JD

JudasD said:
last night i re-odined with a pit file. I had selected re-partition, nand erase and hone EFS clear. I did get a successful odin and the phone had to reactivate with sprint. IN the end i still have the very laggy performance, phone sometimes not responding and spontaneous reboots.
All of this started in an instant. Everything was running fine on a TW rom that i had been running for about a week. I went to use the camera, the app froze and the speaker made a slight static kind of sound and then all of this started. No matter what kind of rom i put on here they now all act the same. very strange.
JD
Click to expand...
Click to collapse
Doesn't sound like you're having all the issues posted by the OP if stock was fine for a week and you can Odin successfully and have no issue until installing a custom ROM.
You replaced your battery and stopped using older ones? That camera issue was either a bad battery or incompatible camera in a custom ROM, IMO.
The stock ROM that worked fine for a week and the custom ROM that spontaneously reboots, which were they? Most likely, you're limited to what mods you can apply. In that condition, were you using stock or custom kernel? Kernel tweaker or none? Am I wrong to conclude your issue is the custom ROM and possibly custom setups?
Could you describe the random reboots? I've personally experienced a scenario where a ROM may run fine until user factory resets and ItsOn tries to install its bootstrapper but cannot with custom kernel or missing resources. It's persistent though, got a prompt to reboot with no issue or reason given when all seems well except the prompt to reboot that may actually become unexpected reboot if notification it's disabled and ignored. Some have found its best to factory reset and wipe internal memory when this happens and then install custom ROM cleanly. @freeza even added a line in script to delete /carrier/ItsOn folder and contents when that was identified as the issue when not wiping internal memory when completing ItsOn bootstrapper prior to installing custom ROM. I believe that works in that scenario but it highlights a need for user to follow OP install to prevent that in ROMs that omit that line in scripts. This could be a disconnect where phone isn't tested but deemed compatible with Sprint and data patch.
But kernel tweaks can cause issues with random reboots. The kernel I use works well with interactive governor but the rest are not as stable or fluid. I can under volt but only 25 or 30 mV and I limit over clocking to 2 steps above stock, no further (goal is stability without hurting battery with reasonable gains). You should consider that each processor has already been profiled to run within a specific volt to frequency table based on its ability so there's little room to limit with no adverse effects. Major steps can have adverse effects. Over clocking should also be given the same respect. We're already maximizing performance near threshold of stability. Think small steps, rather than large. Using the developer recommended kernel tweaking app is paramount for success as well.
Swapping kernels repeatedly may also leave your phone in an incompatible state so that even restoring boot.img partition to stock isn't helping. The reason is the modules the kernel uses. Developers will modify the contents of /system/lib/modules. Hopefully that's done in a compatible way but each custom flash over pre-existing custom setup may not be ideal but works best flashed over stock modules. If developer has done thorough testing, maybe the adverse effects have minimized but you can see where not having the phone for testing may impact users. Restoring boot.img only leaves the modules in unintended modification, especially for stock boot.img
Just a few examples of why a custom ROM may not be as compatible as stock for some users or carrier subscribers. You should mention the ones not being so compatible when comparing to stock as well as knowing that custom kernel tweaks and applications may not work as well on all ROMs.
There is a possibility you've chosen an incompatible ROM; ported ROMs may be nearly fully functional but have issues like you described. There's many workarounds posted in this forum that admittedly aren't fully functional; much effort has been shared by a few that have given much effort to find most compatible ROM but I think we'll get more stable support out of the box for Sprint version on Sprint from @tx_dbs_tx soon enough if your phone holds up- the OP describes an all too common failure with eMMC failure on Note 4. Sprint compatibility is tougher due its network and porting ROMs is tedious and may not work fully on phones not on hand for test.
Sent from my SM-N930P using Tapatalk

samep said:
Doesn't sound like you're having all the issues posted by the OP if stock was fine for a week and you can Odin successfully and have no issue until installing a custom ROM.
You replaced your battery and stopped using older ones? That camera issue was either a bad battery or incompatible camera in a custom ROM, IMO.
The stock ROM that worked fine for a week and the custom ROM that spontaneously reboots, which were they? Most likely, you're limited to what mods you can apply. In that condition, were you using stock or custom kernel? Kernel tweaker or none? Am I wrong to conclude your issue is the custom ROM and possibly custom setups?
Could you describe the random reboots? I've personally experienced a scenario where a ROM may run fine until user factory resets and ItsOn tries to install its bootstrapper but cannot with custom kernel or missing resources. It's persistent though, got a prompt to reboot with no issue or reason given when all seems well except the prompt to reboot that may actually become unexpected reboot if notification it's disabled and ignored. Some have found its best to factory reset and wipe internal memory when this happens and then install custom ROM cleanly. @freeza even added a line in script to delete /carrier/ItsOn folder and contents when that was identified as the issue when not wiping internal memory when completing ItsOn bootstrapper prior to installing custom ROM. I believe that works in that scenario but it highlights a need for user to follow OP install to prevent that in ROMs that omit that line in scripts. This could be a disconnect where phone isn't tested but deemed compatible with Sprint and data patch.
But kernel tweaks can cause issues with random reboots. The kernel I use works well with interactive governor but the rest are not as stable or fluid. I can under volt but only 25 or 30 mV and I limit over clocking to 2 steps above stock, no further (goal is stability without hurting battery with reasonable gains). You should consider that each processor has already been profiled to run within a specific volt to frequency table based on its ability so there's little room to limit with no adverse effects. Major steps can have adverse effects. Over clocking should also be given the same respect. We're already maximizing performance near threshold of stability. Think small steps, rather than large. Using the developer recommended kernel tweaking app is paramount for success as well.
Swapping kernels repeatedly may also leave your phone in an incompatible state so that even restoring boot.img partition to stock isn't helping. The reason is the modules the kernel uses. Developers will modify the contents of /system/lib/modules. Hopefully that's done in a compatible way but each custom flash over pre-existing custom setup may not be ideal but works best flashed over stock modules. If developer has done thorough testing, maybe the adverse effects have minimized but you can see where not having the phone for testing may impact users. Restoring boot.img only leaves the modules in unintended modification, especially for stock boot.img
Just a few examples of why a custom ROM may not be as compatible as stock for some users or carrier subscribers. You should mention the ones not being so compatible when comparing to stock as well as knowing that custom kernel tweaks and applications may not work as well on all ROMs.
There is a possibility you've chosen an incompatible ROM; ported ROMs may be nearly fully functional but have issues like you described. There's many workarounds posted in this forum that admittedly aren't fully functional; much effort has been shared by a few that have given much effort to find most compatible ROM but I think we'll get more stable support out of the box for Sprint version on Sprint from @tx_dbs_tx soon enough if your phone holds up- the OP describes an all too common failure with eMMC failure on Note 4. Sprint compatibility is tougher due its network and porting ROMs is tedious and may not work fully on phones not on hand for test.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
I apologize i was not 100% clear in my previous post. I was running a custom rom when the camera issue happened. Since then any rom i install is very laggy and has spontaneous reboots. This includes stock odin roms with no mods at all. I have also tried multiple batteries.
JD

JudasD said:
I apologize i was not 100% clear in my previous post. I was running a custom rom when the camera issue happened. Since then any rom i install is very laggy and has spontaneous reboots. This includes stock odin roms with no mods at all. I have also tried multiple batteries.
JD
Click to expand...
Click to collapse
OK, my mistake too. Maybe you said that before and I didn't follow the flow of your comments.
You did the nand erase all but do you typically wipe internal memory and factory reset prior to flashing ROM or stock tar? I also prefer to power down and pull battery before going to download mode and flashing stock tar.
If you've done everything and get random reboots on stock or failed to normal boot or eMMC failure, that may be your eMMC failing or other internal failure. I would expect it only gets worse over time- time to repair our replace. I just did my local research with uBreakItIfixIt and the guy says I'd have to bring in my own part but labor is only $10 plus tax to replace main motherboard. Part lists on web for $80 or more. Amazon has a listing for it too.
https://www.amazon.com/gp/aw/d/B01M..._SY340_FMwebp_QL65&keywords=Motherboard+N910P
Sub $100 repair estimate isn't so unreasonable compared to increasing cost of upgrading to locked phone with no root possibilities. But HTC is an option if their offering is appealing. I'm thinking maybe 2017 HTC has an appealing upgrade that I may find worthy for the money. Sure wish an OEM would duplicate the Note 4 on a refresh with updated internal components.
If my phone were to break today, I'd give that a go. I trust business names like Amazon and uBreakItIfixIt. Ubreakitifixit usually has parts on hand for simple or common repairs like screens, internal batteries and USB ports. That outfit just did an economical repair in an iPhone 6 for my wife. Replaced screen and battery for just over $160.
Sent from my SM-N930P using Tapatalk

Related

[Ask Your Questions Here] Questions & Answers for Epic 4G Users

CLICK HERE TO GO TO THE WIKI
I have decided to open a Questions and Answers thread on this section of the forum. This is a good way to keep the number of new threads with questions down to a minimum, which will make new threads essentially for people that are contributing to the Samsung Epic 4G. This includes, but is not limited to, people that are providing the following:
- Roms & Kitchens
- Programs & Apps
- Fixes & Tweaks
- Skins & Themes
- Tips & Tricks
I would like to request the help from other members to keep the thread in order and in check. This will have the added side effect of creating an ever self updating knowledge base that will far extend the content of the Wiki. This will in turn save us from having to answer the same question a billion times...
Please refer to the Wiki first before asking any questions though! It can be located here: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700
CLICK HERE TO GO TO THE WIKI

Any idea when the OTA push for2.2 will start?

jg187211 said:
Any idea when the OTA push for2.2 will start?
Click to expand...
Click to collapse
Unfortunately, we don't have anyone in the community who has inside access to that information. Some of our members are affiliated with Sprint, and so have slightly more reliable rumors, but even their sources have thus far been wrong if they quoted a specific date...
So I hope you understand that I'm not being a jerk when I say, we won't know until it actually happens (and this will probably always be the case)
That being said, this most recent leak (DK28) seems stable so far IMO, so it could potentially become our official update

ok im a total noob to all this stuff. i followed the guide to update my epic to 2.2. the problem is, that the camera, gallery, and a couple other apps dont work. Can someone help me? Should i go back to 2.1, if so, how do i do that?

EDIT: Angry rant removed, thanks to the mods for a quick response (and to the member who's post was removed: no hard feelings, I hope you understand)
Just remember to read before posting, to make sure your post will be relevant and not redundant
jayzn210 said:
ok im a total noob to all this stuff. i followed the guide to update my epic to 2.2. the problem is, that the camera, gallery, and a couple other apps dont work. Can someone help me? Should i go back to 2.1, if so, how do i do that?
Click to expand...
Click to collapse
Whenever flashing a ROM using either recovery, it's always a good idea to wipe the phone (as in factory reset - I'm not referring to wiping the cache or the dalvik cache, although both steps are also usually recommended)
If you used the odin method described in this thread: http://forum.xda-developers.com/showthread.php?t=861213
then you might have flashed the wrong tar - DK05 and DK17 both had the camera problem, make sure you have the DK28 file.
If you have the right tar, then you could have an incomplete download... I doubt that though, when that happened to me, my phone wouldn't boot at all. But you might want to redownload the tar just to be sure (double check the filesize after it finishes and before you flash, if it seems too small then it messed up again)
That's the best general advice I can offer, but if you'd like to provide more details about the method you used (especially a link to the guide you used, if it isn't the one I provided), someone here might be able to identify where you're going wrong

i followed the instructions from http://forum.xda-developers.com/showthread.php?t=861213. i didnt use odin, i just used the .zip method. it took me a lot of tries cause i kept getting errors. the second mirror link worked for me, but like i said, my camera, gps, gallery and some other apps dont work.
oh and everytime i try to flash again, i get the error.

It sounds like you're either starting from the wrong rom or not wiping the phone before flashing the zip. All of the zip updates I have seen require you to start from DI18 stock (root an clockwork seem to be okay in my experience, all other mods must be removed) - if you have installed any custom roms, your best bet is to follow the odin method using the stock DI18 tar - so you may as well just skip the zip methodand odin to the stock DK28 tar
And you absolutely must wipe the phone (again, factory reset - I suspect many people are just wiping the cache and/or the dalvik cache).
Sent from my SPH-D700 using XDA App

Odin flashing
I've got a quick question. I'm looking to move to a build using the DK28 information release and it requires that I update the pit and modem files on my phone using Odin. Do I need to flash a 2.2 rom right away or am I safe to boot into my current rom first?

KaiXXV said:
I've got a quick question. I'm looking to move to a build using the DK28 information release and it requires that I update the pit and modem files on my phone using Odin. Do I need to flash a 2.2 rom right away or am I safe to boot into my current rom first?
Click to expand...
Click to collapse
Are you doing the strictly odin method (full froyo in a tar file)? Or an update.zip?
The odin method *should* include the modem and everything (and you use the updated pit in the same process) - you'll have to read the particular thread that you got the download link from, but I haven't noticed any odin tar files that required the modem separately
For the update.zip method, I don't know if it matters whether you flash the modem before or after applying the zip through recovery - I don't think either one overwrites the other, but that's a part of the process I can only guess about. But regardless of when you odin flash the modem, that's when you'll use the new pit file (the same as the odin-only method above).
As far as I know, the primary difference is that the update.zip doesn't inherently overwrite user data (but you'll probably have broken programs that FC all the time, which means a wipe is necessary, making this somewhat null). I prefer the odin method because it is a fresh flash of the entire system (I usually let it repartition as well - no one else has posted about that feature so I have no idea if it's a fluke that it hasn't given me problems)
Hope that helps

which is the best
so i have updated to dk28 froyo 2.2 i like battery life and performance can anyone offer info on which is the best rom for me or just some insight on which rom is the best overall

How do I stop running applications from starting every time I restart my phone?? I have the start up auditor but for some reason everytime I restart my phone the apps I have disabled keep restarting themselves and I have to go into the running programs and disable them manually. WTH?? Doesnt programs constantly running in the background kill the battery life?? How do I disable apps from starting?

youngpro83 said:
How do I stop running applications from starting every time I restart my phone?? I have the start up auditor but for some reason everytime I restart my phone the apps I have disabled keep restarting themselves and I have to go into the running programs and disable them manually. WTH?? Doesnt programs constantly running in the background kill the battery life?? How do I disable apps from starting?
Click to expand...
Click to collapse
How I understand it, especially with Froyo, you shouldn't have to kill programs in the background, if said 'background' process or service is working normal or efficiently. I still kill the DRM process when I reboot my phone, and not sure if it's still causing drain issues.
Also (someone else confirm this), I believe that constantly 'killing' certain background processes actually uses MORE battery, since it has to constantly restart itself. I've had a much more stable device *not* using auto killers, and just sniping one here and there that I know to cause drain.
Some reading material on GC, tho, in regards to memory management

Ignore me!

devo52 said:
so i have updated to dk28 froyo 2.2 i like battery life and performance can anyone offer info on which is the best rom for me or just some insight on which rom is the best overall
Click to expand...
Click to collapse
A lot of it is personal preference - this early in the game, the primary differences between the roms are going to be mostly cosmetic. So for now, the best advice I can offer is to try each of them and decide which theme you like. Regardless of how you upgraded, you had to use odin, so you have succeeded at the most difficult step of the process - and odin can bring your phone back to life if something goes wrong, so it's an invaluable skill to have.
In the meantime, keep watching the threads (quietly, unless you have a question that hasn't been asked already - we're working on cleaning up the forum to make it easier for everyone to find answers... but I digress...)
It's too early to be sure of any of the fixes out there - we have at least three separate fixes for the GPS issues; some people find success with one, others with another, and a lucky few don't need the fixes at all... so in summary, we can't say which is better or worse just yet, stay tuned and decide whether you want to experiment on the bleeding edge, or wait for these things to be stable and thoroughly tested.
And if you have any doubts, just stick with the stock DK28 for now

tl;dr, questions in BOLD.
Okay, after spending the entire night scouring the internet/this forum and starting from absolutely zero-knowledge about the Android OS, I managed to update my Epic to 2.2, and root the phone. Now, I'm kinda stuck as far as customization goes. I see all these cool skins and battery life mods and stuff, but they don't exactly offer any steps as to how to install them. Since I don't exactly know what file-types do what, I'm kinda shooting blindly at trying to update/install something "custom" onto the phone. So, my question(s) is/are:
What does the ROM do?
What does the ROOT do?
I know the root basically "unlocks" your phone, but that's all I know. The process of customizing the phone still remains a mystery. (that's the problem with following step-by-step instructions, rather than actually knowing what you're doing.)
I also don't understand the purpose of flashing a phone. Flashing, in my experience is to update something, like say a BIOS. But that sets the system back to square 1 as far as all settings go, in this particular example.
If I flash, with say Odin, after having updated to DK28 and "rooting," won't this make all the "customization" that I've done prior basically 'null' because I've just flashed the phone into a blank-state?
Sorry if these are questions easily answered by searching, but I just spent my entire sleep-cycle trying to find the answers to these questions, and managed to only get so far. I look forward to the answers On another note, I am now EXTREEEEMELY pleased with my phone. Before this evening, I was just the regular, old run-of-the-mill enduser. I liked the cool built-in customizations and all the apps and what not, but never dreamed of being able to customize my phone to THIS EXTENT. So, now it's something I'm very interested in doing..it makes my phone truly mine.

zdavidi said:
What does the ROM do?
What does the ROOT do?
Click to expand...
Click to collapse
Did you see the link to the Wiki in the original post of this thread? That's where I started when I first got here, it helped me understand the basics.
zdavidi said:
If I flash, with say Odin, after having updated to DK28 and "rooting," won't this make all the "customization" that I've done prior basically 'null' because I've just flashed the phone into a blank-state?.
Click to expand...
Click to collapse
It depends on what you flashed with Odin. If you only flash a modem file, then your customizations and apps are untouched. If you flash an entire ROM in "tarball" form then not only does it re-write the modem but it also overwrites all user data. Think of the latter as resetting the phone to stock and works even if you cannot boot up.

When can we expect a custom Kernel with netfilters for wifi tethering?

n00b question.
If an SDK version is released (say, like, Gingerbread today), does that mean chefs could take it and cook up a ROM for ANY phone (say, like, the Epic)? Or do they need something else to do that?

Remove Touchwiz Launcher (consequences?)
Hey-- I'm using Quantum 2.0.0 ROM, and I never use the touchwiz launcher. Does anyone know if it's safe to just remove the apk? (TouchWiz30Launcher.apk) or is there other functionality tied to it?
I use LauncherPro, fyi.

Please forgive my ignorance... I've searched the forums, looked at the wiki...
I use titanium backup and am now running the DK27 froyo build by noobnl. My question... How do I restore my e-mail accounts to the phone everytime without having to re-type them in? I've been flashing a rom every other day on average since I got the phone and it's getting REALLY old.

Won't wake up from sleep, battery drained.

Welp, the sleep of death. After not using the phone for bouts of 30ish minutes (possibly correlated to having an incoming SMS during that period), I will hit the power button only to find the phone does not respond. I will have to pull the battery, and when I reboot, ~80% of battery remains (it was fully charged before).
This happens on battery and on the charger alike.
Running CM7/MIUI (happens on both), and Chad's Latest.
Help!

Before you rule out hardware/software failure, you should try an alternate battery. Quick Q/A rundown:
*How long (in hours/days/weeks) has this issue been occurring?
*Have you removed any system apps?
*Install any partially incompatible mods?

It started recently, when I changed things up a little bit:
1) I got a new phone (replaced the HTC INC)
2) replaced the SD card to 16gb

It sounds more like a battery issue, have you tried switching batteries?

SlimSnoopOS said:
It sounds more like a battery issue, have you tried switching batteries?
Click to expand...
Click to collapse
The times I've had that issue it was almost always kernel related. Some kernels attempt to do things that simply don't work too well on certain ROMs or hardware. I'd be suspect of whatever sleep settings the kernel has.

Wow, I would not have thought of that. I haven't been very experimental with kernels, I'm one of those "find one kernel that works and stick with it" type users.

Thanks, I tried an older version of chad's, but maybe his whole line doesn't work? On two phones, that seems unlikely, but I will give it a whirl. I will keep stock CM7 kernel and report back if it gives me problems.
I hope it isn't Chad's...I love those kernels....

Well, I changed kernels to default, and it's still happenning. I get random reboots, about 4x a day. I reformatted my SD card and it helped performance a lot, and I thought that was causing the reboots, but the problem persisted.
Any help? Please? This is strange and it drains my battery.
Seems to happen around getting a text message/notification.
My thoughts revolve around: 1) the 3g is f*cking up my phone, but that would be strange, or 2) the vibration associated with the notification is rebooting the phone? Thoughts?

The way I see it there are a couple remaining options to try:
1) Flash a different rom outside of MIUI & CM7; however I'm doubtful this would resolve it as you experience reboots on two different roms.
2) Revert to stock Froyo using RUU file and see if reboots continue. RUU can be found at: dougpiston.com and there are threads detailing this process in the Droid Inc Dev. Section
3) Are you able to try a new/different battery?
Couple additional questions:
When you wipe & flash roms, do you Format Boot and Format System in addition to Format Data/Wipe Cache/Wipe Dalvik Cache? If not, possibly try this.
You experience reboots while within a rom, does your phone reboot while you're in Recovery? To clarify, if you were to attempt to manually flash a new rom does it reboot prior to/while in the process of flashing a rom?

which of the custom ROMs are you liking best?

I've been following the ROM dev daily but I've been stuck in the hospital and not been able to flash any of them yet.
I'm getting out today and plan on checking one out asap and am curious as to which one I should go with.
I would appreciate any feedback on them that you can provide!!

scott0 said:
I've been following the ROM dev daily but I've been stuck in the hospital and not been able to flash any of them yet.
I'm getting out today and plan on checking one out asap and am curious as to which one I should go with.
I would appreciate any feedback on them that you can provide!!
Click to expand...
Click to collapse
I am still running rooted stock. One of the ROMs that had K9 Mail wouldn't work for me on Exchange 2K10. You could also look at the # of posts in each of the threads, that may ID where most of the peeps are headed.
I really wanted to say that I hope you are doing better. My phone haxoring started with a long hospital stay back during the Razor days.
I do like LG's native e-mail client. Only Samsung's e-mail client is better.

scott0 said:
I've been following the ROM dev daily but I've been stuck in the hospital and not been able to flash any of them yet.
I'm getting out today and plan on checking one out asap and am curious as to which one I should go with.
I would appreciate any feedback on them that you can provide!!
Click to expand...
Click to collapse
I currently only used the Domination HD ROM, and it has its goods n bads.
the Goods:
1) Lag is virtually gone! Phone runs really smooth and fast, with almost no stuttering.
2) Some extra visual improvements, like the Roboto Fonts and ICS wallpapers included (although it didn't show up on mine for some reason)
3) ICS sounds/notifications
the Bads:
1) Video Recording (camcorder) is borked as for now. You cannot record a video, the app just freezes at 00:00:00
2) Bootup time is significantly longer (might be closer to 2-3 min bootup time) but someone said that it might be due to the deodexing of files in the phone.
3) the claimed Bravia Engine and Xloud features implemented in the ROM just cannot be seen/heard. Supposedly it is there and running, but to some, nothing looks any different than the usual HD look of the phone and the sound is no louder than default. So those 2 features either are not working or just not noticeable enough.
That's my small review on the Domination HD ROM. I might have missed something and if I did, hopefully the next person will add to it.

SnoopDawg said:
I am still running rooted stock. One of the ROMs that had K9 Mail wouldn't work for me on Exchange 2K10. You could also look at the # of posts in each of the threads, that may ID where most of the peeps are headed.
I really wanted to say that I hope you are doing better. My phone haxoring started with a long hospital stay back during the Razor days.
I do like LG's native e-mail client. Only Samsung's e-mail client is better.
Click to expand...
Click to collapse
hey thanks Amigo! I hope all is well with you now as well.
I took your advice and flashed the kernalpan1c ROM and am checking it out now.
aquariuz23 said:
I currently only used the Domination HD ROM, and it has its goods n bads.
the Goods:
1) Lag is virtually gone! Phone runs really smooth and fast, with almost no stuttering.
2) Some extra visual improvements, like the Roboto Fonts and ICS wallpapers included (although it didn't show up on mine for some reason)
3) ICS sounds/notifications
the Bads:
1) Video Recording (camcorder) is borked as for now. You cannot record a video, the app just freezes at 00:00:00
2) Bootup time is significantly longer (might be closer to 2-3 min bootup time) but someone said that it might be due to the deodexing of files in the phone.
3) the claimed Bravia Engine and Xloud features implemented in the ROM just cannot be seen/heard. Supposedly it is there and running, but to some, nothing looks any different than the usual HD look of the phone and the sound is no louder than default. So those 2 features either are not working or just not noticeable enough.
That's my small review on the Domination HD ROM. I might have missed something and if I did, hopefully the next person will add to it.
Click to expand...
Click to collapse
super, Thank you eh. nice. I really want to try this one too. I got the impression from following the thread that the video cam issue can't be resolved. Perhaps I read it wrong, I will go back through the posts. I too want that vid cam on this phone. But I am very curious about that Bravia engine and Xloud and if/how much they make a difference on my device.
I am liking the kernalpani1c ROM, it does seem smooth, I uninstalled the GO launcher, sticking with Zeam after comparing the 2 with the new ROM, Zeam is noticeably faster & smoother for me.
The best thing about the custom ROMs for me is I had to use Malninion's unbricking method to fix this phone several weeks ago which uses the SU640, now I am back to the proper one.
I think I'll check out that Domination ROM next.

scott0 said:
hey thanks Amigo! I hope all is well with you now as well.
I took your advice and flashed the kernalpan1c ROM and am checking it out now.
super, Thank you eh. nice. I really want to try this one too. I got the impression from following the thread that the video cam issue can't be resolved. Perhaps I read it wrong, I will go back through the posts. I too want that vid cam on this phone. But I am very curious about that Bravia engine and Xloud and if/how much they make a difference on my device.
I am liking the kernalpani1c ROM, it does seem smooth, I uninstalled the GO launcher, sticking with Zeam after comparing the 2 with the new ROM, Zeam is noticeably faster & smoother for me.
The best thing about the custom ROMs for me is I had to use Malninion's unbricking method to fix this phone several weeks ago which uses the SU640, now I am back to the proper one.
I think I'll check out that Domination ROM next.
Click to expand...
Click to collapse
I might switch to kernelpanic's rom next week or so when I have the time to start fresh. I'm gonna format the /data partition so it will a be clean slate.
Well, like i've mentioned, me and some others don't really see any difference either the bravia engine or Xloud is doing to the phone. The image quality on the phone is the same, and the loudness is just as loud as stock. Shrugs, it might just be me I dont know lol. Feel free to try it and let us know what you think about it

aquariuz23 said:
I might switch to kernelpanic's rom next week or so when I have the time to start fresh. I'm gonna format the /data partition so it will a be clean slate.
Well, like i've mentioned, me and some others don't really see any difference either the bravia engine or Xloud is doing to the phone. The image quality on the phone is the same, and the loudness is just as loud as stock. Shrugs, it might just be me I dont know lol. Feel free to try it and let us know what you think about it
Click to expand...
Click to collapse
I was wondering about the clean slate starting fresh myself, does that make a difference?
I went to get the other ROMs and such but noticed their instructions were different than kernalpan1c, they did not state to clear caches and wipe system, etc so I stopped there.
so a question- it's safe and correct to always do the following 2 steps when flashing any ROM
3. Format /system in Mounts and Storage
4. Then "wipe cache partition" and "advanced > wipe dalvik cache"
thanks for the inputs

aquariuz23 said:
3) the claimed Bravia Engine and Xloud features implemented in the ROM just cannot be seen/heard. Supposedly it is there and running, but to some, nothing looks any different than the usual HD look of the phone and the sound is no louder than default. So those 2 features either are not working or just not noticeable enough.
Click to expand...
Click to collapse
why on earth would anybody need some st1nk'n bravia engine while there already is lg mobile engine in stock ROM? ther U go http://www.youtube.com/watch?v=KD3GSzOBuUo

scott0 said:
I was wondering about the clean slate starting fresh myself, does that make a difference?
I went to get the other ROMs and such but noticed their instructions were different than kernalpan1c, they did not state to clear caches and wipe system, etc so I stopped there.
so a question- it's safe and correct to always do the following 2 steps when flashing any ROM
3. Format /system in Mounts and Storage
4. Then "wipe cache partition" and "advanced > wipe dalvik cache"
thanks for the inputs
Click to expand...
Click to collapse
So far from what I have followed, the 2 steps you've mentioned are safe to follow. The only thing they've all mentioned is: "DO NOT WIPE/FORMAT /Data Partition" Just making it big, bold and bright so you don't miss it LOL. Kernelpanic figured out that it is some kind of a glitch in CWM that causes data corruption when you wipe/format the /Data partition.
Domination's ROM also states to wipe /system and dalvik cache, it's a standard thing i'm guessing. The only reason I want to start from a clean slate is that I don't want any bugs or system clash when I flash a new ROM over an existing ROM, so I think wiping /data will be essential.
Btw, Kernelpanic has suggested that if you do need to wipe /data, to please first flash back LG's default recovery using the image you've backed up prior to flashing CWM on the phone, and then formatting the phone back to factory settings using it. When factory reset is complete (which means /data is also wiped), you can then flash back CWM and then flash the new ROM.
Hopefully this will help you decide on your steps. Again, wiping /data is not necessary at all, it's just an option that technically should be done but right now is not so safe to do. Be careful and as always, we are not responsible for a gorgeous brick on your desk lol.
---------- Post added at 05:06 PM ---------- Previous post was at 04:58 PM ----------
Billy Madison said:
why on earth would anybody need some st1nk'n bravia engine while there already is lg mobile engine in stock ROM? ther U go http://www.youtube.com/watch?v=KD3GSzOBuUo
Click to expand...
Click to collapse
I like that commercial lol. That is very informative and interesting to watch. Very true wat you said about the Bravia engine. Tbh, like I previously mentioned, I do not see any benefit of the Bravia engine on this phone, and definitely not the Xloud feature. Thus, I'm thinking of trying another ROM that has all capabilities functioning, thus the Camcorder.
Just wondering, if you truly can replace the "visual engine (e.g. LG's engine with Bravia Engine), could that be the reason why the camcorder won't work? It's kinda weird that the camera works but the recording function doesnt.

well,
i flashed the domination ROM and it installed, I poked around and decided I needed the video camera, so shut down, booted in to CWM and flashed the other ROM, it said it installed, i rebooted it would not open, stuck on boot, so i shutdown, booted into cwm and restored the 1st ROM but now i am stuck on a boot loop and cannot access cwm.
derp.
update: flashed the su640 ROM so I am back in biz, gotta root and flash CWM.
so i guess this is a fresh flash after all!
i'm at 32% batt, superoneclick does not want to root atm , letting it charge a bit and will try to reroot.

scott0 said:
well,
i flashed the domination ROM and it installed, I poked around and decided I needed the video camera, so shut down, booted in to CWM and flashed the other ROM, it said it installed, i rebooted it would not open, stuck on boot, so i shutdown, booted into cwm and restored the 1st ROM but now i am stuck on a boot loop and cannot access cwm.
derp.
update: flashed the su640 ROM so I am back in biz, gotta root and flash CWM.
so i guess this is a fresh flash after all!
i'm at 32% batt, superoneclick does not want to root atm , letting it charge a bit and will try to reroot.
Click to expand...
Click to collapse
Yeah, that's what I feared, that when flashing another ROM over existing rom and not deleting /data might give an error. Which other Rom were you attempting to flash over Domination?

aquariuz23 said:
Yeah, that's what I feared, that when flashing another ROM over existing rom and not deleting /data might give an error. Which other Rom were you attempting to flash over Domination?
Click to expand...
Click to collapse
was trying to flash the RebelRom after the Domination. the switch from kernalpanic to domination went fine but the switch from Domination to Rebel FUBARed the phone, same exact steps followed. it also messes up the phone where a restore does not work then cwm is not accessible.
yup, serious issue that is not pointed out very well anywhere. the phone was ruined. in fact it's now stuck on the su640 ROM rooted but not recognized by adb so no su access, adb shell command returns a dollar sign and stalls, and the su640 wireless issue means no internet access on the phone so I can't get terminal emulator on it to move img files in to place.
ATT is sending me a replacement under the warranty.
my opinion atm on the custom CWM and the available ROMs is the ROI is not there.
The Roms don't perform any better than a rooted and debloated stocker IMO to justify the risk it takes checking them out.

scott0 said:
was trying to flash the RebelRom after the Domination. the switch from kernalpanic to domination went fine but the switch from Domination to Rebel FUBARed the phone, same exact steps followed. it also messes up the phone where a restore does not work then cwm is not accessible.
yup, serious issue that is not pointed out very well anywhere. the phone was ruined. in fact it's now stuck on the su640 ROM rooted but not recognized by adb so no su access, adb shell command returns a dollar sign and stalls, and the su640 wireless issue means no internet access on the phone so I can't get terminal emulator on it to move img files in to place.
ATT is sending me a replacement under the warranty.
my opinion atm on the custom CWM and the available ROMs is the ROI is not there.
The Roms don't perform any better than a rooted and debloated stocker IMO to justify the risk it takes checking them out.
Click to expand...
Click to collapse
Damn, seems like there is still some figuring out to do. A lot of the troubles keep pointing to CWM. What did you tell AT&T to get them to send you a warranted phone?

Kaiser_Beef said:
Damn, seems like there is still some figuring out to do. A lot of the troubles keep pointing to CWM. What did you tell AT&T to get them to send you a warranted phone?
Click to expand...
Click to collapse
i told them the phone was stuck on the LG boot screen and it would not turn off entirely. if I hold the power button down long enough the screen would flash off but it would instantly reboot itself again. the phone did finally fully boot to the su640 ROM but no data/internet access. then they had me do a factory reset which failed as well, after the reset the phone would still boot to main screen instead of to the setup screen.
It was a long telephone call. but ultimately I was transferred to the warranty dept, the 1st tech agent filled that warranty person in who then just checked a cople things and then agreed to ship me a replacement expedited, scheduled delivery is Monday.

scott0 said:
was trying to flash the RebelRom after the Domination. the switch from kernalpanic to domination went fine but the switch from Domination to Rebel FUBARed the phone, same exact steps followed. it also messes up the phone where a restore does not work then cwm is not accessible.
yup, serious issue that is not pointed out very well anywhere. the phone was ruined. in fact it's now stuck on the su640 ROM rooted but not recognized by adb so no su access, adb shell command returns a dollar sign and stalls, and the su640 wireless issue means no internet access on the phone so I can't get terminal emulator on it to move img files in to place.
ATT is sending me a replacement under the warranty.
my opinion atm on the custom CWM and the available ROMs is the ROI is not there.
The Roms don't perform any better than a rooted and debloated stocker IMO to justify the risk it takes checking them out.
Click to expand...
Click to collapse
So out of all the 3 ROMs you've tried which one did you like the most? Well, of course the rebelrom doesn't count cuz it borked your phone lol. Sorry to hear that though. I had this bad feeling when you mentioned that it froze after flashing that you flashed rebelrom, and yup that's what you did lol. Didn't you read through the thread though? Many of them got stuck in boot loops and not being able to recover after it.

yes, of course I read through the thread. I had the time to read through all the threads many times and did, even jotted notes down. I was fully aware of the risks involved and don't recall *****ing. I am patiently awaiting my replacement phone generously provided by ATT.
my conclusion was that none of the ROMs are worth the risk. The first one doesn't perform any better than a stock phone debloated + a better launcher, the second one has a very long boot time, then performs no better than a debloated stocker minus the video recorder.

scott0 said:
my conclusion was that none of the ROMs are worth the risk. The first one doesn't perform any better than a stock phone debloated + a better launcher, the second one has a very long boot time, then performs no better than a debloated stocker minus the video recorder.
Click to expand...
Click to collapse
I will say upfront to anyone looking at using my ROM, it is a de-odexed ROM minus bloat, a better launcher, some optimizations (ie ICS app process and system server, build.prop tweaks), and the carrier text removed from the status bar. With that said, de-odexed does run smoother than stock (odexed). CF-Bench scores are for example higher on my ROM than on stock.
We're not going to see dramatic speed improvements past that without custom kernels or CM/AOSP.

scott0 said:
yes, of course I read through the thread. I had the time to read through all the threads many times and did, even jotted notes down. I was fully aware of the risks involved and don't recall *****ing. I am patiently awaiting my replacement phone generously provided by ATT.
my conclusion was that none of the ROMs are worth the risk. The first one doesn't perform any better than a stock phone debloated + a better launcher, the second one has a very long boot time, then performs no better than a debloated stocker minus the video recorder.
Click to expand...
Click to collapse
lol scott, I never said anywhere that you were *****ing about bricking. I was just wondering why try when you know you have 80% of bricking? But anyways, it's great that you are getting a replacement from AT&T.

A few questions before rooting...

I am going to root my phone and have a few questions before I do. I am coming from a sensation and with the htc I only had 1 way to root so are any of the methods better or worse than others? I was planning on using to root injected stock rom method.
Secondly, I've read and still don't understand, could somebody explain the loss of imei to me? Htc doesn't have anything like that so I am confused about the backup of it?
Finally, could somebody suggest a good starting point for a rom and kernel combo? Unlike my htc I'm pretty happy with the stock rom sped and battery. I mainly want to tweak the looks of things a little, maybe a new battery icon and moving the clock position.

Best way to root is the video in my signature (use my files, too). It's easier and faster than the way you describe. I wish people would forget that stupid flash counter exists. It's not like we can't reset it.
Loss of IMEI very rarely happens when you flash. But, once you flash CM10, just run the terminal emulator that comes with it: su > reboot nvbackup. Now your IMEI is backed up, and you are protected against possible, but unlikely, loss. I've flashed every day for two months and never lost mine.
Rom: Why use ICS when you can use JB? IMO, the sole reason to use an ICS build is wifi calling. Use CM10. Use the stock CM kernel. CM doesn't have center clock (AOKP does), but IMO, CM is the better of the two. A lot of people like to flash custom kernels. They usually provide marginally better battery life, overclocking/undervolting, etc. I feel that none of these are necessary. There is an additional problem that the 3rd party kernels always lag behind CM's kernel merges, also. This typically results bootloops. So make sure the kernel you flash (if you do), is compatible with the newest CM build.

No the method does not matter, root is root. Read about them and use the one you are comfortable with.
Yes, HTC does have IMEI. All GSM phones do. It is basically the serial number your phone uses to connect to the network. All you have to do is follow the instructions in one of the threads to back it up.
For stock based ROMs on ICS, I like Wanamlite.

Aerowinder said:
Best way to root is the video in my signature (use my files, too). It's easier and faster than the way you describe. I wish people would forget that stupid flash counter exists. It's not like we can't reset it.
Loss of IMEI very rarely happens when you flash. But, once you flash CM10, just run the terminal emulator that comes with it: su > reboot nvbackup. Now your IMEI is backed up, and you are protected against possible, but unlikely, loss. I've flashed every day for two months and never lost mine.
Rom: Why use ICS when you can use JB? IMO, the sole reason to use an ICS build is wifi calling. Use CM10. Use the stock CM kernel. CM doesn't have center clock (AOKP does), but IMO, CM is the better of the two. A lot of people like to flash custom kernels. They usually provide marginally better battery life, overclocking/undervolting, etc. I feel that none of these are necessary. There is an additional problem that the 3rd party kernels always lag behind CM's kernel merges, also. This typically results bootloops. So make sure the kernel you flash (if you do), is compatible with the newest CM build.
Click to expand...
Click to collapse
Thanks for the reply, CM10 wasn't officially supported with the htc so it never really worked great, but it looks like the M version is pretty smooth and ironed out so I'll definitely try that. I guess a lot of the threads I've read were early ones from before the flash counter could be reset, I thought it was a bigger deal than it seems like it is. I'll try your sig's root method. Oh yeah, wifi calling doesn't work for me right now with the stock rom so losing it isn't a big deal at all.
joshnichols189 said:
No the method does not matter, root is root. Read about them and use the one you are comfortable with.
Yes, HTC does have IMEI. All GSM phones do. It is basically the serial number your phone uses to connect to the network. All you have to do is follow the instructions in one of the threads to back it up.
For stock based ROMs on ICS, I like Wanamlite.
Click to expand...
Click to collapse
I wasn't saying HTC doesn't have imei, I was saying in a year of having it and before with the G2 I never once read any threads about people "losing" it, so I wanted to know what makes the s3 different.

That was SOOOO much easier than the sensation was. The senny took me over an hour, I had to learn adb and had to check and recheck a ton of commands before entering each to make sure I didn't brick anything. This was fast and easy, but now I can't seem to get into twrp recovery? Every time I try vol up/home/power it boots into what I'm assuming is the standard stock recovery?

My signature has an explanation for that.

Thanks again, I don't understand why but I installed cwm touch and it worked and then used goo manager to install twrp again and now it works fine. I know there's a whole thread about twrp but what do you like and why?

I stopped using TWRP because the keyboard (at least at the time) didn't work properly. It would close for no reason, making me retype the file names. Took me 5-6 times once, for this file name: CM10-XXXX. 9 characters. Would just keep closing and resetting the characters I had already typed. I've heard the new version, 2.3, has some pretty bad bugs, but I haven't used it, so can't confirm. Developer is currently fixing said problems. I also find the slide-to-continue gimmick to be ridiculous. I will say, however, that flash-queuing is a good idea.
I won't even discuss CWM because we have CWM Touch. The layout is nonsensical. Everything seems to be in random order, no dividers to make things easier to read, no prompt on fix permissions. Other than that, it's great. It allows you to delete stock recovery, and it keeps root for you when you flash OTA files with it.
CWM Touch is what I use, and will continue to use until something better shows up.

One more question, is there a way to double check once I've done the su/nvbackup using terminal emulator, or should I just assume that if the phone rebooted after running that command that it was successful?

When you reboot with that command, you will see blue text at the top left corner of the screen, like when you are going into recovery. It says it's copying modemst1 and modemst2 to fsb and backup. Yes, the names are incorrect, but you get the idea.

How is your Nexus 5x experience with custom ROM/kernel vs. full Stock?

Wasn't sure if this would fit better under Q&A, but wanted to get the opinions of my fellow Nexus 5x users who spent some time with stock, unrooted, locked bootloader and then switched to the custom scene and learn just how much better (or worse) the experience was.
I haven't been in the mod game as much since my Galaxy Nexus and Motorola Droid days, when one click root/unlock, custom recovery, flash ROM and flash kernel all took just a few minutes. The guides for the 5x seem a bit more intimidating, especially when it comes to having all the right ingredients to keep Android Pay working. People seem to be saying some really great things about the Cataclysm+ElementalX combo, as well as other ROMs and kernels.
Anyway, before I dive in to the land of full data wipes and avoiding bootloops, I wanted to ask Nexus 5x nation - how's your custom experience, and was it worth it?

I'm using Cataclysm+ElementalX and this
Awesome battery life and screen on time and still very smooth.

Lossyx said:
I'm using Cataclysm+ElementalX and this
Awesome battery life and screen on time and still very smooth.
Click to expand...
Click to collapse
That's the route I would be looking to take, I think. Response has been great for the interactive governor mods. Was the whole process (unlock, systemless root, ROM/kernel install) pretty easy, or did you run into a lot of issues? Also, Android Pay still working?

Moonboots said:
That's the route I would be looking to take, I think. Response has been great for the interactive governor mods. Was the whole process (unlock, systemless root, ROM/kernel install) pretty easy, or did you run into a lot of issues? Also, Android Pay still working?
Click to expand...
Click to collapse
Fairly easy yes, I followed Heisenbergs guide , but if you want a more automated way you could try Wugfresh Toolkit, The systemless root is basically has the sam install process (flashable zip) and ElementalX doesn't conflict with system partition so Android pay should work. And, I don't use Android Pay as my country doesn't have (or maybe) Google Play yet. Didn't stumble to any issues at all.

Moonboots said:
That's the route I would be looking to take, I think. Response has been great for the interactive governor mods. Was the whole process (unlock, systemless root, ROM/kernel install) pretty easy, or did you run into a lot of issues? Also, Android Pay still working?
Click to expand...
Click to collapse
Unlock, Systemless root, ROM/Kernel is extremely easy. That's why I love Nexus Devices. You'll be able to do it in your sleep after the first couple of times. No issues should arise as long as you do everything in the correct order. Android Pay still works with Systemless Root, again, as long as you follow directions.
I'm running Ubermallow and Phasma Kernel, and after trying many different kernels and a few different ROMs, this is definitely my favorite combination. Fast, extremely optimized, just the right amount of customization and Phasma is one of the most feature-rich kernels out there for this phone. Feel free to experiment, though. Everyone has different tastes and usage patterns. So what works for me, may not necessarily be for you. Luckily flashing new ROMs and kernels takes 5 like minutes so you can give them all a shot!
I can safely say that you'll never want to go back to stock after finding the combination that works for you

Thanks for the thoughts and encouragement, all! I do recall the flashing addiction from the old Moto Droid days with Bugless Beast, AOKP and CyanogenMod. Good to know there are some great options here.
Another question I had regarding upgrading to new versions. When 6.0.2 drops, or one of the monthly security updates, etc., it used to just be a dirty flash over the current ROM, clear dalvik/cache, and reboot system. Am I correct in saying it's more involved this time around? The guides seem to point to a lot more steps for your basic ROM upgrades.

Roms and updates
Moonboots said:
Another question I had regarding upgrading to new versions. When 6.0.2 drops, or one of the monthly security updates, etc., it used to just be a dirty flash over the current ROM, clear dalvik/cache, and reboot system. Am I correct in saying it's more involved this time around? The guides seem to point to a lot more steps for your basic ROM upgrades.
Click to expand...
Click to collapse
This was my first phone that I modified, mainly because I use Linux, and my old phones seems to need Windows to do anything. I followed this guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930. It worked perfectly, and when I needed to apply the update, I followed step 10 of that guide; worked perfectly, with no loss of data or settings at all.
Then, I flashed Cataclysm over that update, without erasing anything other than cache, and when I finished and rebooted, I thought it didn't work until I checked settings and found the rom's single entry for settings. Nothing else changed.

Moonboots said:
Thanks for the thoughts and encouragement, all! I do recall the flashing addiction from the old Moto Droid days with Bugless Beast, AOKP and CyanogenMod. Good to know there are some great options here.
Another question I had regarding upgrading to new versions. When 6.0.2 drops, or one of the monthly security updates, etc., it used to just be a dirty flash over the current ROM, clear dalvik/cache, and reboot system. Am I correct in saying it's more involved this time around? The guides seem to point to a lot more steps for your basic ROM upgrades.
Click to expand...
Click to collapse
Rom upgrades are easy.
Download the factory image and extract boot.img, system.img, and vendor.img.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.

Tomyk89 said:
Rom upgrades are easy.
Download the factory image and extract boot.img, system.img, and vendor.img.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Click to expand...
Click to collapse
I assume fastboot flash radio radio.img if a new radio is included with the update, as well?
After reading through all the awesome resources and recommendations provided by you guys, I think I will unlock, root, install TWRP, decrypt, flash Elemental X, and toy with the interactive governor settings thread that's in the general forum.
That way I can keep Android Pay with systemless root and continue to stay up to date on the latest factory images using Tomyk's note above, is that correct?

Moonboots said:
I assume fastboot flash radio radio.img if a new radio is included with the update, as well?
After reading through all the awesome resources and recommendations provided by you guys, I think I will unlock, root, install TWRP, decrypt, flash Elemental X, and toy with the interactive governor settings thread that's in the general forum.
That way I can keep Android Pay with systemless root and continue to stay up to date on the latest factory images using Tomyk's note above, is that correct?
Click to expand...
Click to collapse
You are correct on the radio.img comment
I personally didn't go the systemless route but I think you're on the right track. I know that a lot of people in other forums have successfully kept Android Pay capabilities after everything so you may want to do a bit more digging. If i find the answer I'll post it for you.

Just as a counter point, stock is working well for me and I feel no need to root at this time. Performance and battery life are already top notch. :good:

N5x, EX kernel, unencrypted, systemless root:
much better performance (both due to EKm and no encryption, and to a lesser extent adaway), worse battery life due to issues with nlpcollectorwakelock from Google play services, which may or may not be related to the rom (Didn't have issues with googleplayservices on stock)
just flashed xposed in an effort to curb these wakelocks by means of Amplify.

2x4 said:
N5x, EX kernel, unencrypted, systemless root:
much better performance (both due to EKm and no encryption, and to a lesser extent adaway), worse battery life due to issues with nlpcollectorwakelock from Google play services, which may or may not be related to the rom (Didn't have issues with googleplayservices on stock)
just flashed xposed in an effort to curb these wakelocks by means of Amplify.
Click to expand...
Click to collapse
I've been having problems with Google Play Services battery drain. Since I still haven't taken the leap to unlock and root, I have no way of pinning the wake locks to nlpcollector but that could be my culprit too.
See attached pictures - This happens once every few weeks overnight, and I usually clear apps from memory before going to bed. So much for doze.

Moonboots said:
I've been having problems with Google Play Services battery drain. Since I still haven't taken the leap to unlock and root, I have no way of pinning the wake locks to nlpcollector but that could be my culprit too.
See attached pictures - This happens once every few weeks overnight, and I usually clear apps from memory before going to bed. So much for doze.
Click to expand...
Click to collapse
it gives me some relief to see that, since that means it's not related to my custom rom, but instead your run of the mill google play services issues..... so hopefully an update to GPS will fix that soon.

2x4 said:
it gives me some relief to see that, since that means it's not related to my custom rom, but instead your run of the mill google play services issues..... so hopefully an update to GPS will fix that soon.
Click to expand...
Click to collapse
Play Services goes through weird phases where it just destroys your battery, and without something like amplify to curb the frequent wakelocks, there's no way around it for the average user. It's a shame.

2x4 said:
it gives me some relief to see that, since that means it's not related to my custom rom, but instead your run of the mill google play services issues..... so hopefully an update to GPS will fix that soon.
Click to expand...
Click to collapse
FYI - it may have been a recent Snapchat update that made that app even worse than normal. Uninstalled it and smoothness and long battery have returned.

Moonboots said:
FYI - it may have been a recent Snapchat update that made that app even worse than normal. Uninstalled it and smoothness and long battery have returned.
Click to expand...
Click to collapse
Thanks for the heads up, I don't have snap chat installed though

Develop Bugs

welcome