Related
Is the Shield Tablet even worth rooting. I mean, it is stock android with Nvidia stuff. And rooting it just takes away the Nvidia logo when turning it on, and its few apps that do more good than harm. Is there a mod out there that will beat out Lollypop? Only thing I can really think of is Carbon KitKat, and I'm not sure if the Tablet runs crappy because of the hardware or because of the software. I haven't been in the scene for a while (and when I was I wasn't there for long), but my swag snapback wearing friend put Cyanogen on his phone (yes, they're evolving) from the Cyanogen website. Has this in it's essence killed the development for systems since they made it easier to run the OS? Much of the ricing vocabulary is jargon for me, so please explain it instead of avoiding it, for example I don't know the difference between a root vs. recovery vs. rom vs. kernel and TWRP vs ClockworkMod, Unofficial mods vs official.
What do you guys run? What do you recommend visual appeal, and what do you recommend for performance? Can I possibly run Carbon Kitkat while keeping the nVidia apps?
Mehhh I only rooted for xposed modules... honestly stock lollipop with a ntfs SD card to get around the SD card issues and root really isn't a factor in performance. Just using like gravity box and an ad block. I think if you have a lte version it may be more useful so u can mess with radios but I can't vouch for that.
Sent from my SAMSUNG-SM-N900A using Tapatalk
I only rooted for viper audio. Major improvement then without
I'd say its definitely worth it for the fact that you can move all your games off of the internal storage onto the SD card using virtualized directories (ie FolderMount) so the data appears on internal storage but actually resides on your SD (load times have been fine for me with a 64 GB class 10, HL2, Portal, TT Games, etc.)...although I'd probably root either way just for a few specific root apps and the fact I root every android device I ever get.
Side note: PLEASE don't use NTFS on flash storage (unless you absolutely have to)...it doesn't know how to cope with it and over time will have degraded performance. Use exFAT, it was pretty much made for this purpose. I've heard people having issues with exFAT on the shield (specifically 128 GB SDs it seems), but my 64 GB worked perfectly on KitKat and now on LolliPop
Since you're not familiar to the terminology, I'll give you the "concise" (I sometimes ramble...) summary of my understanding:
1. Rooting is giving yourself full administrative power over every single file and operation on your phone. Use this power responsibly, meaning think twice before executing a command and bear the consequences like an adult (or enjoy the benefits like a giddy goof!)
2. Recovery is a partition on your device's storage. Stock recovery usually only automatically performs the one task of factory reset/wipe of your device's data, but a custom recovery can allow you to flash (install) programs or even a customized version of the whole operating system (a custom ROM).
3. ROM technically stands for "Read-Only-Memory" but these days it refers to the actual operating system that's residing within that read-only-memory. You've heard of the Cyanogen ROM, which really means Cyanogen's customized operating system for your read-only-memory.
4. Kernel is basically a magical piece of software that tells your device's hardware how to function. So, if you use the wrong kernel, your device's hardware won't know how to function properly and you'll run into problems. But using a customized or optimized kernel will allow your hardware to function much more efficiently or unlock abilities that your hardware didn't know it could do (e.g. undervolting to save power, communicating with USB devices via USB on-the-go, etc.)
5. TWRP and ClockworkMod are both examples of very popular recovery partitions. Some people prefer one over the other. I personally like TWRP because it has an easier to use interface for me.
6. Unofficial vs official mods are best discussed using an example like a cyanogen ROM. An unofficial cyanogen mod means that it's not officially made by the Cyanogen team and is therefore not supported so you can't go crying to Cyanogen if you've messed up your device using an unofficial mod. Official mods are the stuff officially released by Cyanogen and will be fully supported by their team.
I hope the above helps with your understanding of some terminology. Below, I describe my opinions on whether rooting / custom ROMs are worth it.
I'm currently using the nVidia stock firmware, so I'm not using a custom ROM. The downside is that I miss out on the great customized features like clearing all recent apps from memory, or holding the Overlay button to switch to my last-used app, etc. The upside is that I get to use the nVidia-specific features, such as stylus-only mode (I use it a lot for annotating PDFs / research papers / drawings etc.) or the Console Mode for when I hook up the tablet to the big TV. I've tried a custom ROM and loved the somewhat increased smoothness and extra features, but I personally wanted the nVidia-specific features more than the custom features.
That said, I have rooted my stock nVidia firmware because I wanted to block ads without downloading or purchasing an additional app. I've used the root privileges to allow me to modify my hosts file to redirect ad URLs to 127.0.0.1, which gives those ads no data therefore effectively blocking them. That's all I use my root privileges for, and some of you might think "that's it?!?!" and to that I say "yyyyyyup".
Long post, but congrats for making it this far and thanks for reading!
amartolos said:
The downside is that I miss out on the great customized features like clearing all recent apps from memory, or holding the Overlay button to switch to my last-used app, etc.
Click to expand...
Click to collapse
Since you're rooted, check out the app "Recently" from Chainfire - it provides much better control over the stock 'recents' menu as well as the option to clear all.
Sent from my SGH-I337M using XDA Free mobile app
An Droid said:
Since you're rooted, check out the app "Recently" from Chainfire - it provides much better control over the stock 'recents' menu as well as the option to clear all.
Sent from my SGH-I337M using XDA Free mobile app
Click to expand...
Click to collapse
neat, i didn't know they made such an app! thanks =)
ben.nesheim said:
Mehhh I only rooted for xposed modules... honestly stock lollipop with a ntfs SD card to get around the SD card issues and root really isn't a factor in performance. Just using like gravity box and an ad block. I think if you have a lte version it may be more useful so u can mess with radios but I can't vouch for that.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Same thing I do. I rarely flash a custom ROM if the device is stock or near stock android. Simply rooting, installing an adblocker and installing xposed framework is good enough for me.
Sent from my SM-N900V
Evolve
Rooting is Evolving
To me for buy the shield tablet is going beyond on your imagination, why don't try something new, come on is a piece of hardware, you just installing a software and why not with a such powerful device,you don't want more juice and control.
My ST LTE root and some utilty and tool apk got between 60000 and 62000 in antutu performance and stability, but careful in what you do.
I see many people doing modifications and having many issues and then spending a lot of time having to mess with their devices in order to get them back in order. If that's your thing great and I used to be one of you ...
... but these days I try and consider very carefully everything I do so everything works rather than spending hours basically being a mechanic if you want to use a car analogy. I want to drive my car not spend most of the time fixing it.
I see people with a lot of issues after they've done a lot of "do it because it can be done" modifications, their devices become unstable and then they don't know what caused it due to having five or ten major modifications.
One at a time:
1. Nandroid Backup.
2. Do 1 modification
3. Use your device for a day
4. If everything is working, go to 1, otherwise see 5.
5. If everything is not working restore backup from 1. and start at 2. again.
Now my opinions (as a half interested longtime Android user and a new Shield Tab user) are:
TheSkywayBridge said:
Is the Shield Tablet even worth rooting. I mean, it is stock android with Nvidia stuff. And rooting it just takes away the Nvidia logo when turning it on, and its few apps that do more good than harm.
Click to expand...
Click to collapse
It depends - if there is some added functionality that you cannot have any other way then yes.
Rooting by itself actual does nothing to the ROM but it allows other applications that might change your boot logo. What will change your boot logo usually is using a custom ROM or kernel.
But you can absolutely make any firmware better by rooting your device for example by installing Viper4Android which will improve sound quality and a ton of other stuff.
TheSkywayBridge said:
What do you guys run? What do you recommend visual appeal, and what do you recommend for performance? Can I possibly run Carbon Kitkat while keeping the nVidia apps?
Click to expand...
Click to collapse
After a few devices it's been my preference to use stock ROM's with custom kernels (sometimes) because I mainly use my phones and tablets to play games and with some rare exceptions the dev community doesn't get to the performance level when I benchmark them.
If I never played games then CM and other custom firmware is better.
Unless I'm mistaken there is no CM based ROM that allows Nvidia Shield Controller usage so for me personally it's even less appealing as a prospect on the Shield Tablet to not run stock.
Since I'm a new Shield Tablet user I've only used some LP version (which arrived with the tablet) then had an awful experience with Nvidia's OTA update when I attempted to update to MM after no mods :|
However I went back to LP v5.1.1 and it's an amazing tablet again which doesn't surprise me as it usually seems you need to stick 1 major version behind on Android if you want to customise it and run apps you like sometimes.
I'm now going to apply a custom kernel onto stock firmware as this has often been the "winning" combination if you want to evaluate ROMs using benchmarks.
Hello,
I am Nexus 5 user myself. I have a friend at work that was looking to switch over from the iPhone to Android and I sold him on the OnePlus One for the price, spec, and larger screen size. He has had decent luck with it so far but has been getting a lot of app and system app crashes lately. I think he may have received one OTA update to CyanogenMod since he's had the phone. I want to improve his Android experience, so I am wanting to get him as close to stock as possible but with some customization.
Personally, I have run multiple custom roms & custom kernels on my Nexus 5, but always end up going back to Stock image with Franco Kernel and Xposed Framework with Gravitybox and several other modules. I want to get him as close to this setup as I can on his OnePlus One.
From what I can tell it looks like OxygenOS is based on AOSP, so that means no CAF kernel right? So can I flash OxygenOS on his OnePlus One and then flash the plain old vanilla Franco Kernel? I know Gravitybox is officially only supported on Nexus devices but I know it will work on AOSP ROMs.
Is OxygenOS the way to go to get this phone close to stock image? Any other suggestions that may allow the use of a dark material theme (or does OxygenOS have this already?). Any assistance is appreciated. I want to get him up an running on a nice stable OS. I know it was great pre-Jellybean, but I haven't been all that impressed with CyanogenMod OS since then personally.
jsgates said:
Hello,
I am Nexus 5 user myself. I have a friend at work that was looking to switch over from the iPhone to Android and I sold him on the OnePlus One for the price, spec, and larger screen size. He has had decent luck with it so far but has been getting a lot of app and system app crashes lately. I think he may have received one OTA update to CyanogenMod since he's had the phone. I want to improve his Android experience, so I am wanting to get him as close to stock as possible but with some customization.
Personally, I have run multiple custom roms & custom kernels on my Nexus 5, but always end up going back to Stock image with Franco Kernel and Xposed Framework with Gravitybox and several other modules. I want to get him as close to this setup as I can on his OnePlus One.
From what I can tell it looks like OxygenOS is based on AOSP, so that means no CAF kernel right? So can I flash OxygenOS on his OnePlus One and then flash the plain old vanilla Franco Kernel? I know Gravitybox is officially only supported on Nexus devices but I know it will work on AOSP ROMs.
Is OxygenOS the way to go to get this phone close to stock image? Any other suggestions that may allow the use of a dark material theme (or does OxygenOS have this already?). Any assistance is appreciated. I want to get him up an running on a nice stable OS. I know it was great pre-Jellybean, but I haven't been all that impressed with CyanogenMod OS since then personally.
Click to expand...
Click to collapse
You can't install Franco on Oxygen, as far as I know there's only one compatible kernel for Oxygen, can't remember which one it is though. In saying that, Oxygen is fairly close to stock so that might be what you're looking for. If you're considering install GravityBox in order to get some extra customisation then going close to stock probably isn't the best idea, it might be better to grab one of the ROMs that has some customisation built in natively.
About a stable ROM? I'm not really a good kernel user since I always use the default rom kernel. You may want to try a customed UI named Flyme based on 5.0.2. I think that it really made my phone's using time longer, and the camera is also better that Cyan. Hope I helped you.
I have been a flashaholic for some time, probably the Eclair days, but I really question if it's worth it now days.
Most Lollipop and newer ROMs, except for Nexus devices, seem to have some kind of issues... If not immediately, then over time. While at the same time factory ROMs get better, partially because the base code is better and because many manufacturers are getting better at it.
And now, some features are being blocked just by unlocking of bootloader, even if you're otherwise stock, like Android Pay and others like Pok�©mon Go.
I find all I really do now on custom roms is some interface tweaks... Change the battery icon, add a clear all button to recents, and add arrows to the navigation bar, all minor stuff. Otherwise things like Nova Launcher, SwiftKey, and GSAM largely don't even require root anymore much less a custom ROM. Part of it used to be for battery life, but now, at least on modern Moto devices, most custom roms struggle just to match the battery life of stock.
I've tried every rom for this device I can find, here and other places, and they all seem to have a variety of things that fail, from minor annoyances to major services broken like GPS, or they fail over time.
My question for discussion is it still worth it, and why do you ROM or even root anymore?
I used to run a variety CM ROM's on Samsung Galaxy & Note devices. Starting with the Galaxy S2 Skyrocket and then every decent device Samsung released until the bootloaders stopped getting cracked.
There was always something that just didn't work right and I'd have random crashes.
But for me it was semi-worth it. I like to tinker and customize a lot.
Fast forward to the last thirteen months with my first non-Samsung since. A Motorola Moto X Pure.
Best damn phone I've ever had.
And there is CM available, but I quickly discovered AOSP ROM's like Dirty Unicorn and Broken OS.
Both these ROM's are FULL of customization not found in Xposed modules, and both ROM's have been 100% reliable.
I may have had one lockup in the last 13 months. And everything from GPS to Bluetooth, etc. have all worked perfectly.
So for me, yes... custom ROM's are more than worth it once you find the right ROM. My phone is heavily customized to my needs and super reliable.
The only thing lacking with MotoX was kernel development. Which I guess is where you start losing some reliability.
But it's also where I'm hoping the Pixel will get some good development and I'm looking forward to it. :good:
Non-rooted stock MM has been going great for me lately. Lots of great built in features like Moto actions, etc. I play Pokemon while walking on my breaks at work, and the last few updates forced my hand to go back to stock. I was (am) also a flashoholic, and it was mainly to have custom features and better performance on outdated and mfg abandoned phones. It was also a must for my Kindle Fire. I really don't see myself going away from stock MM (soon to be Nougat) on my MXPE at this point. I still flash ROMs on my G2 and Note 3 though, but barely use them outside the house.
CZ Eddie said:
I used to run a variety CM ROM's on Samsung Galaxy & Note devices. Starting with the Galaxy S2 Skyrocket and then every decent device Samsung released until the bootloaders stopped getting cracked.
There was always something that just didn't work right and I'd have random crashes.
But for me it was semi-worth it. I like to tinker and customize a lot.
Fast forward to the last thirteen months with my first non-Samsung since. A Motorola Moto X Pure.
Best damn phone I've ever had.
And there is CM available, but I quickly discovered AOSP ROM's like Dirty Unicorn and Broken OS.
Both these ROM's are FULL of customization not found in Xposed modules, and both ROM's have been 100% reliable.
I may have had one lockup in the last 13 months. And everything from GPS to Bluetooth, etc. have all worked perfectly.
So for me, yes... custom ROM's are more than worth it once you find the right ROM. My phone is heavily customized to my needs and super reliable.
The only thing lacking with MotoX was kernel development. Which I guess is where you start losing some reliability.
But it's also where I'm hoping the Pixel will get some good development and I'm looking forward to it. :good:
Click to expand...
Click to collapse
Hmm... I have been on that "rom that shan't be named on XDA" for a while now. After a month started suffering SoD randomly and Play Services has stopped issues. DU 10.6 couldn't maintain GPS lock, but 10.5 was fine, seemed to effect only a handful of devices, lucky me.
Anyway, thanks for your input.
acejavelin said:
Hmm... I have been on that "rom that shan't be named on XDA" for a while now. After a month started suffering SoD randomly and Play Services has stopped issues. DU 10.6 couldn't maintain GPS lock, but 10.5 was fine, seemed to effect only a handful of devices, lucky me.
Anyway, thanks for your input.
Click to expand...
Click to collapse
I also have been a avid user of the "rom that shan't be named on XDA" for many months now with no real issues. By chance have you tried a fresh install again. The latest release was back in late August a 4.9.1 version that made corrections to some issues on the 4.9 release.
Jimi Mack said:
I also have been a avid user of the "rom that shan't be named on XDA" for many months now with no real issues. By chance have you tried a fresh install again. The latest release was back in late August a 4.9.1 version that made corrections to some issues on the 4.9 release.
Click to expand...
Click to collapse
Not yet... I have been on 4.9.1 already, and have been working with the devs a bit on it but seems mostly isolated to my device.
acejavelin said:
Not yet... I have been on 4.9.1 already, and have been working with the devs a bit on it but seems mostly isolated to my device.
Click to expand...
Click to collapse
If anything try a fresh install and see if your issues were only from maybe a bad original install. If they show up again then I would say they are isolated to your device.
Jimi Mack said:
If anything try a fresh install and see if your issues were only from maybe a bad original install. If they show up again then I would say they are isolated to your device.
Click to expand...
Click to collapse
I'm out of town for the weekend, in a rather rural area, so maybe will try tomorrow evening.
LMT pie, adaway, naptime, and general tweaking are the only reasons I root on a phone this close to stock android.
I didn't run custom ROMs on this phone until about August of this year. That was when battery life on aicp started to get comparable with stock for me. I can get most of the features I want from gravitybox, but I prefer them baked into the ROM. Xposed always seems a little problematic even when you don't install janky modules. I really like the notification led; missed that when I got this phone. I know we're supposed to use moto display, but I think that makes more sense on amoled than a great big LCD. Never had good luck with lightflow or the led enabler apps, but the custom roms work great. I really like slim recents too. I haven't found any modules that work to put KitKat like recents on M ROMs.
TruPureXMM + GravityBox
Loved my MXP so much I bought one for my mom who was hating her iPhone5. Kept it stock (for obvious reasons), so I have a good baseline to compare to my MXP running TruPureXMM + GravityBox. I've tried a bunch of ROMS for this phone but I always come back to TruPureXMM + GravityBox. Oh, and Tasker.
There is no way in hell I would go back to stock.
I used Cyanogenmod on my HTC Incredible and Verizon Galaxy Nexus. Didn't root or ROM for a while due to using the stock ROM on the 2nd generation Verizon Moto X 2014 and stock Android on the Nexus 5X and 6P. But, I had the itch to unlock the bootloader on my Moto X Pure, due to curiousity, and because it's likely that we will only see one more Nougat update. I tried CM13, but I was getting UI freeze ups and slowdowns on multiple builds, so I tried Dirty Unicorns 10.6, and that has been working fine. I may return to the stock ROM after the Nougat update, but in the meantime, I'm happy experimenting with different ROMs on the Pure.
I'd be cool with stock- as long as I could debloat it.
And it was updated fairly quickly.
Stock for this phone is great. Better than most. Only issue really is Moto is so far behind on security updates. They are on what, May I believe? CM13 is Oct.
Sent from my XT1575 using XDA-Developers mobile app
Stock here, never a issue. With Nougat in the horizon, a custom ROM is a big NO for me.
Enviado desde mi XT1575 mediante Tapatalk
I would say TruPureX with a few mods is a very solid and stable way to go. I myself am on TurboROM which has ceased current development, but have ZERO issues. AICP's MM build is the most feature filled and works flawlessly aside from one issue I don't have on other ROMs, where my bank app only shows black when using the camera to deposit checks, making AICP unusable for me, but highly recommended for others to try as that's the absolute only issue I could find after a week full of testing (Kind of what I do as a hobby is push ROMs to their limits to find the issues.)
So in short: TruPureXMM, TurboROM, AICP - are all great choices without the negatives associated with many custom ROMs.
Pretty sure we are all here to push the ROMs to he limits lol?
Sent from my XT1575 using XDA-Developers mobile app
Speaking of custom ROMs, I just searched android file host for Clark and there are new 7.0 builds of zephyros, pure nexus, aosp, and cos.
I'm in a limited data area so I haven't downloaded or tried them out yet.
jason2678 said:
Speaking of custom ROMs, I just searched android file host for Clark and there are new 7.0 builds of zephyros, pure nexus, aosp, and cos.
I'm in a limited data area so I haven't downloaded or tried them out yet.
Click to expand...
Click to collapse
Running the latest Zephyr after trying AICP and CM14. Uses substratum and SuperSU. Camera recording isn't working with snapdragon camera (FC), google camera (records but doesn't save). Had an android.phone FC but replaced with google phone/contacts and no problems so far. Still need to test speakerphone and bluetooth, but assuming those work as well as 6.0.1 I'm pretty impressed by Birdman.
Any roms that anyone can recommend? CM13 and OrionOS both have very bad stuttering after some time of use. Has anyone tried Pure Nexus or Slim6? Just need a good daily driver that can handle games without heating up so hot, and handle most social apps great...
jason2678 said:
Speaking of custom ROMs, I just searched android file host for Clark and there are new 7.0 builds of zephyros, pure nexus, aosp, and cos.
Click to expand...
Click to collapse
Seriously? We've got like one and a half here.
I recently got a second-hand S6 from work. My first step is always to look up the XDA forums on the phone to see what my options are.
It seems that a lot of people are happy with the stock ROM, so that could be enough. However, I like root, since I like certain apps that need root. So if that already triggers KNOX, I might as well install Lineage on it while I'm at it.
So I'd love to hear some opinions. Should I stick to stock, or go through the (badly documented, sorry) process of getting this phone customized?
You should definitely stick with stock ROM if you want to use your phone as daily driver.
I always liked the call recording feature so I can keep track of verbal agreements made over the phone. I believe it can be done using Xposed, but Lineage has it built-in (although it doesn't auto-trigger unfortunately). Even with stock, I'd still need root to do it, and that triggers Knox, right?
Thanks, hopefully some more people will have something to say about it.
Custom ROMs are good, but there are always some sort of malfunctions.
For a phone that has an up-to-date firmware, I wouldn't install custom ROM.
While S6 support has dropped, meaning that it will no longer receive an update, but it still has an updated firmware, I would say it will stay good for at least one more year.
After that I'll consider installing custom ROMs, just like what I did with my older phones.
And as @forumber2 mentioned, for a daily driver, stock is better.
However, if you don't mind troubleshooting the issues on the custom ROM and have the time, then you should install it.
And about rooting, yes, it will trigger the Knox, but since Nougat, I've unrooted my phone and I personally didn't need to root it again, though I'm kinda considering it.
The bottom line is that stay with the stock for a while, if didn't satisfy you, then install customs. The stock ROM, doesn't have many issues, or at least I didn't encounter many that I couldn't solve, just like any other stock ROM.
stock ROM. but you can root it and use xposed to do some things you want..
None of the AOSP ROMs have a camera that is on par with the stock one - that's my reason for sticking through with stock on an Android phone since... ever, really. I'm not a fan of keeping things the way they are. If the camera would be as good as on stock, I'd ditch stock immediately, but unfortunately, the drivers for the camera are proprietary, so, it's unlikely that that will ever be the case.
BUT you can get stock-based custom ROMs - I'm currently using the S8+ port, which seems to be working flawlessly. They are usually debloated, with various tweaks and features that aren't usually available, quicker and just generally better.
Stay stock man custom Rom are bad you will lose many futures and performance and battery . I play games on s6 I tried all custom Roms nothing worked always end up with performance and Wi-Fi problems I am now on latest stock nougat and I will just wait until I find cheap s8 then I will sell this poor s6.
There nothing you can do about s6 to get him better than stock. Nothing except get root to use some apps like change location or install some sound apps that requires root..thats it
For years I have rooted my phones, and have had just about all the OEM's at one time or another. Since I've had my Pixels, not so much. So I decided to Root my Pixel, and run a custom ROM for the weekend, and today, I had had enough, and went back to stock. It's just not for me anymore. I like for everything to work, and what I get from stock is just perfect for me. Why is everyone else still holding on?
I miss being a flash-a-holic lol. I would always flash alot of custom roms also and my fav was Pure Nexus. i'm currently stock and fine with it well i wanted to try Q so. I still wanted a Pure Pixel rom but it never happened.
I think pretty much the ability to properly backup and restore using Titanium Backup. Otherwise, I as well would be done with root. Sure would make the monthly updates easier...
I have always rooted my devices. From Nexus 6p, Pixel XL, Pixel 2XL, I never felt I needed to, they always ran great and did exactly what I needed. My favorite, including a 2 days battery was Pixel 2 XL.
However, with Pixel 3 XL, the battery, and now the lagging, has been a nightmare. It's like I am dealing with samsumg all over again, like it was with samsumgs, pockets pcs, etc...
I was about to root and flash a custom until I saw your post... which means, not even the custom roms will fix this horrible phone... thats sad... I always buy my pixels on launch date, but I will eagerly wait for the next one, but only buy it 3 or 4 months later, if I buy it. For now, I am now researching between the latest samsung, OPO and Huawei to replace my P3XL, I really can't take it anymore. What a waste of money in this phone, and is not even worth half of what I paid now....
I use a custom rom for customization (changing statusbar color, accent colors, customize reboot menu, change statusbar icons, etc). Use root so I can disable navbar and use pie controls, use tasker and other apps properly, enable fingerprint pay where it is not allowed, and many other things.
I admit on stock you can use tulsadiver's mods to change most of the things a custom rom does, but you have to redo it on every update.
Stock with root and ElememtalX kernel for the extra high brightness mode. Need it because I mount my phone to the handlebars of my motorcycle for Nav. It's ok without it, but so much better with it.
I held off for years before putting a custom ROM on my Pixels, but I finally relented because of some lag on my 3XL. Now I'm running the latest AOSiP with Kirisakura kernel, and everything works beautifully and better than stock. Those of you who are having issues and have nothing to lose should definitely try a custom ROM. I haven't yet found anything that doesn't function better than stock. It's been totally stable and fully functional for me. With better performance and more features, of course.
There are still a couple reasons that keep me flashing custom. Not as many as there used to be. I still enjoy it though. Just like switching Linux Distros. I do it when I'm bored. It's fun.
For me. It's roms. Kernels. Titanium. And ad blockers.
There are lots of reasons to still root. But to each there own.
What finally drove me away from custom ROMs is that devs would stop supporting my device as soon as a new flashier, newer, c00l3r device came out. Basic bugs wouldn't get fixed. They'd be switching forums every few months (XDA? Telegram? Google+?). I'd donate $100 and a month later my favorite features would stop working or be dropped.
In short, lack of long term (6-9 months "long term"?) basic stability in favor chasing the latest new toy. I get it, it's their free time, but that's why I donated, and this is why I left.
This is the first Android device I've had I've kept stock with exception to rooting and a few Magisk modules like ViPER4Android. Other than that, I have to admit I am pretty content with the stock experience.
After almost 3 years (starting with the OG PIxel and XL), I finally installed a custom ROM on the 3XL but left the 3 stock and rooted. I may go back to stock and rooted with Q coming. The biggest reason for me to quit swapping custom ROMs on these devices is that TWRP has really become nothing more than a zip flasher. Multiple slot issues and no real Nandroid functionality makes it so that a custom ROM just replaces stock if you are happy with it and support continues. The time to completely wipe and reconfigure after a custom install just isn't worth it more than once for me.
Data backs up fine on TWRP and restoring it gets back all your settings.
Ad-blocking, ad-blocking, and ad-blocking.
I just can't use a phone that shows adverts - they p1ss me off no end. Not only the fact they take up half the screen, and steal bandwidth, but the tracking is basically illegal but still done relentlessly.
21cdb said:
I held off for years before putting a custom ROM on my Pixels, but I finally relented because of some lag on my 3XL. Now I'm running the latest AOSiP with Kirisakura kernel, and everything works beautifully and better than stock. Those of you who are having issues and have nothing to lose should definitely try a custom ROM. I haven't yet found anything that doesn't function better than stock. It's been totally stable and fully functional for me. With better performance and more features, of course.
Click to expand...
Click to collapse
Active edge, and Pixel stand doesn't work as it should. Also with all the custom ROM's I flashed they would just reboot randomly.
djcrystals said:
There are still a couple reasons that keep me flashing custom. Not as many as there used to be. I still enjoy it though. Just like switching Linux Distros. I do it when I'm bored. It's fun.
Click to expand...
Click to collapse
I get that. It's one of the reasons that got me into it in the first place.
cantara256 said:
What finally drove me away from custom ROMs is that devs would stop supporting my device as soon as a new flashier, newer, c00l3r device came out. Basic bugs wouldn't get fixed. They'd be switching forums every few months (XDA? Telegram? Google+?). I'd donate $100 and a month later my favorite features would stop working or be dropped.
In short, lack of long term (6-9 months "long term"?) basic stability in favor chasing the latest new toy. I get it, it's their free time, but that's why I donated, and this is why I left.
Click to expand...
Click to collapse
Honestly that's actually one of the advantages of still Rooting. Getting the latest software on a device that is no longer supported.
krs360 said:
Ad-blocking, ad-blocking, and ad-blocking.
I just can't use a phone that shows adverts - they p1ss me off no end. Not only the fact they take up half the screen, and steal bandwidth, but the tracking is basically illegal but still done relentlessly.
Click to expand...
Click to collapse
dns.adguard.com
jmartin72 said:
Active edge, and Pixel stand doesn't work as it should. Also with all the custom ROM's I flashed they would just reboot randomly.
Click to expand...
Click to collapse
Both features work great in the latest AOSiP build. Also haven't had any random reboots.
jmartin72 said:
dns.adguard.com
Click to expand...
Click to collapse
That only works on wifi right? On mobile data it uses your providers DNS?