Database Users

Why Root?

OK. First let me say I am not a total noob. I go back to the original droid and up to the LGG2 in rooted every device. It was, in part, due to Verizon being so dang slow to update their devices. Now, though, I am finding no real reason to root. Transparent bars are not enough for me to do it Every person I find who roots the G2 has some issue. ART crashes some phones. Others have call issues. This or that will not function. Yes it fun to play with new things, but is it worth it? I am sure there will be people that will say they have zero issues but from what I am reading, I find it hard to believe they have zero.
Sent from my Nexus 10 using Tapatalk 4

I have no issues related to being rooted. Now most ROMs I've tried have their fair share of bugs, but that's part of the gamble you take a with a phone as new as this. Give it half a year and most of the things developed for the G2 will be ironed out.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM 4.3.

Vepaot said:
I have no issues related to being rooted. Now most ROMs I've tried have their fair share of bugs, but that's part of the gamble you take a with a phone as new as this. Give it half a year and most of the things developed for the G2 will be ironed out.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM 4.3.
Click to expand...
Click to collapse
I agree in part, but even after they are worked out you will normally find issues, even if minor, in the best of Roms. I point to Cyanogen just as an example. They are a great group with a quality ROM. Release candidates are super stable, but will have an issue or two. They also solo not have all the new stuff people crave like a nightly will have. But with nightlies you get instability. Please guys, I know everyone is going to jump in and say how great their favorite ROM is. That is not the point of my comments. I do not care what ROM you have. There is going to be a bug. I guess stock can be the same, but in general I am now leaning towards stock uprooted. With the LG g2 I have yet to see a feature stable enough to void warranty for. In a year from now that may change. At one time or was just a hobby. Flash and try everything. Add this, remove that. But this phone has so much stock I can no longer recommend rooting to any one. Obviously I have no issue if you do. I am just wondering what is driving people to root the G2?
Sent from my VS980 4G using Tapatalk

Bigralphn said:
OK. First let me say I am not a total noob. I go back to the original droid and up to the LGG2 in rooted every device. It was, in part, due to Verizon being so dang slow to update their devices. Now, though, I am finding no real reason to root. Transparent bars are not enough for me to do it Every person I find who roots the G2 has some issue. ART crashes some phones. Others have call issues. This or that will not function. Yes it fun to play with new things, but is it worth it? I am sure there will be people that will say they have zero issues but from what I am reading, I find it hard to believe they have zero.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Titanium Backup, AdAway, Xposed
What does ART have to do with root?
edit: you should change from why root to why custom rom...and at that why AOSP based rom

It's not so much the reasons listed above though they are all good. The main reason for me to Root is to remove all the Bloatware I can off my phone. This includes apps and options. I like to get my unit down to as bare as I can and build it back up the way I want a phone to be. I got the G2 for the hardware specs and not for anything else LG or Verizon was offering me.
Plus it is fun to deal with new Roms as they are being created.
And there will never be ZERO issues with any Rom and that includes the manufacturers release. If that is so good at the time of release why would there be Updates.

rquinn19 said:
Titanium Backup, AdAway, Xposed
What does ART have to do with root?
edit: you should change from why root to why custom rom...and at that why AOSP based rom
Click to expand...
Click to collapse
I suppose you are right on the why custom room. I am stock rooted on my Nexus 10 unrooted on this. With ART, it seems to be a reason people for since that is the only way to get it on most devices. That was all I was implying there. Perhaps when we finally get 4.4 ART will be available sans root
Sent from my VS980 4G using Tapatalk

High Battery Consumption & Slow Performence

--edit--
figured it out... please delete post.

engeloded said:
--edit--
figured it out... please delete post.
Click to expand...
Click to collapse
It is usually best to leave your post and supply your solution for others... Deleting it kind of defeats the purpose of this community. Even if it was a "dumb" thing, it may save someone else from starting a new thread looking for the same answer someday.
Sent from my Motorola XT1575 using XDA Labs

Sorry, didnt know.
I had a new phone with CM13, Xposed & TWRP and the phone was laggy with low battery life.
The problem was the OS. The current CM13 is a nightly version and probably not stable for daily use. at the moment
I wouldnt recommend anyone using it for the time being.
Thank you.

Reading through most of the comments of the ROMS I don't see any of them worth running without having issues... I will stay stock 6.0 24.221.4 rooted for now.
I came back to this phone hoping the development would get better. One thing nice is having TWRP back coming from the LG G4 and V10.
Still on the fence and may be returning it again... I wonder if the Moto Z Play will be a good phone...
Missing the wireless charging already. LOL
.

Screen gets black sometimes

Hi guys, my smartphone's screen gets black sometimes, and, after a quarter of second, it gets back. It's a Moto G Play (4th gen.). I want to unlock BL, root and change ROM too. But I'm scared about if it isn't a h/w issue.
If you can give me a hand, it'd be really appreciated.
Here's a logcat taken from the boot until 1 hour of activity reached: https://gist.github.com/FacuM/1bf3d99bf1c6c7dc4178051ab197074d
And here you can get a .zip packed version: https://gist.github.com/FacuM/1bf3d.../d2c32dcd9a3a30e28ae25e43d0c79f6427cda676.zip
Here, a logcat from when I wiped logcat until I opened a lot of apps with at least one black flashing: https://gist.github.com/FacuM/b72ae8c12bb50c5aebfec3c0eb3cf497
And here a .zip packed version: https://gist.github.com/FacuM/b72ae.../2e47f0cd8418ebda2c8522cac8b85b2bde826cdc.zip

If it gives us both any relief, I can confirm the issue - it's like the blink of an eye, so fast, quite rare and absolutely random. A quick Google search only hinted towards the Moto display function which might be the issue but I didn't disable it because it's one of the phone's killer features
So, I 've decided to wait for an app update or the Nougat update that's on the way (?) and see if it gets fixed - otherwise I will pay a visit to the local Moto service center in terms of guarantee

dbal said:
If it gives us both any relief, I can confirm the issue - it's like the blink of an eye, so fast, quite rare and absolutely random. A quick Google search only hinted towards the Moto display function which might be the issue but I didn't disable it because it's one of the phone's killer features
So, I 've decided to wait for an app update or the Nougat update that's on the way (?) and see if it gets fixed - otherwise I will pay a visit to the local Moto service center in terms of guarantee
Click to expand...
Click to collapse
Thanks for your answer. Basically, the problem as I see might be related to GBoard or Moto Display, as you say.
Also, I don't know if you've checked the logs I uploaded, but there are a lot of OMX decoding errors, I'm almost sure that there's no hardware failure there.
I'm now going to unlock Bl and see what's up with a custom ROM.
Sent from my Moto G Play (4th gen.) using Tapatalk
------
EDIT: Before proceeding, disabled Moto Display. Will give more feedback later.
Anyways, flashing again got the issue completely gone. Maybe your theory is the most appropriate.

Well, I wouldn't suspect Gboard because I 've noticed the thing days before I got it installed
I also don't vote towards hardware issue that's why I am not extremely eager to visit the service plus the fact that the issue happens 1-2 times a week and I almost forget it in the meantime
If you go for a custom ROM, this might shed some light whether it's firmware or app related and what we have to expect as a solution - don't forget to post some feedback after a few days testing
Let's see btw if anyone else posts here for having the issue as well

dbal said:
Well, I wouldn't suspect Gboard because I 've noticed the thing days before I got it installed
I also don't vote towards hardware issue that's why I am not extremely eager to visit the service plus the fact that the issue happens 1-2 times a week and I almost forget it in the meantime
If you go for a custom ROM, this might shed some light whether it's firmware or app related and what we have to expect as a solution - don't forget to post some feedback after a few days testing
Let's see btw if anyone else posts here for having the issue as well
Click to expand...
Click to collapse
BTW, I've already disabled Moto Display. I haven't fell asleep yet and it's 7 am here. Tomorrow I'll keep testing and hope it doesn't fail anymore. If not, I'll go for Bl unlocking and get rid of this Motorola's buggy attempt of softly modded AOSP.
Sent from my Moto G Play (4th gen.) using Tapatalk

Here I've uploaded a screencast of what appears to be related to the bug and shows clearly it's a software bug related to the video render in Marshmallow.
https://youtu.be/qhmUN43y0Pk
Sent from my Moto G Play (4th gen.) using Tapatalk

facuarmo said:
and shows clearly it's a software bug related to the video render in Marshmallow.
Click to expand...
Click to collapse
That's great news to know :victory: (since it's not hardware related and could be fixed in an updated firmware) but can you please elaborate a bit, how you prove this claim and this short video shows it?

dbal said:
That's great news to know :victory: (since it's not hardware related and could be fixed in an updated firmware) but can you please elaborate a bit, how you prove this claim and this short video shows it?
Click to expand...
Click to collapse
Sometimes, life's about taking the risk.
I've unlocked BL, flashed recovery and installed AOKP.
Now, no flickers found.
Prove:
https://youtu.be/T3e8-6dnyl0
Hope you like guys, and you take the risk too. Flashing a ROM solved everything.

Getting back to the thread after 2 weeks just to confirm your long testing now...is the bug still away or has reappeared somehow?
I am asking before I make the switch to LineageOS which seems a pretty good implementation of nougat

dbal said:
Getting back to the thread after 2 weeks just to confirm your long testing now...is the bug still away or has reappeared somehow?
I am asking before I make the switch to LineageOS which seems a pretty good implementation of nougat
Click to expand...
Click to collapse
I've compiled a kernel based on Squid2's sources with the fixed SELinux setup, then you should see no flickers so far in any ROMs.
Mine's working without any flicker, but I've only tested in Custom ROMs. Maybe you can try on stock?
https://forum.xda-developers.com/g4-play/development/kernel-somefeak-moto-g4-play-t3544556
Good luck and sweet flashes! :fingers-crossed:

Worth it to root?

I recently got this 6P, commingled from a rooted, unlocked, cm13 HTC one m9, would it be worth it to still root? I loved tweaking my m9, unfortunately it was an att version. So it was really hard to find Roms and tweaks that worked for it. I love my 6P so far and it performs wonderfully, just lacks that extra bit of tweaking.

Etheralrealm said:
I recently got this 6P, commingled from a rooted, unlocked, cm13 HTC one m9, would it be worth it to still root? I loved tweaking my m9, unfortunately it was an att version. So it was really hard to find Roms and tweaks that worked for it. I love my 6P so far and it performs wonderfully, just lacks that extra bit of tweaking.
Click to expand...
Click to collapse
There are a lot of Roms, mods and kernels available for the 6P. If you like customizing your phone then you should go for it.

jhs39 said:
There are a lot of Roms, mods and kernels available for the 6P. If you like customizing your phone then you should go for it.
Click to expand...
Click to collapse
Oh yea, i know you can install custom kernals to overclock, do you know of any good ones?

Etheralrealm said:
Oh yea, i know you can install custom kernals to overclock, do you know of any good ones?
Click to expand...
Click to collapse
I don't think it's necessary to overclock the 6P. The most popular kernels are probably Franco's if battery life is your main concern or Elemental if you want more control over performance than you get with the stock kernel. I increased my battery life a bit by switching to Elemental but I didn't use any settings that would negatively affect performance, which is more important to me than battery life. Pure Nexus is a very popular Rom, although I didn't personally have a good experience with that one. I'm happy with Cortex. Some people prefer Megapixel. There's lots of custom ROMs depending on what you are looking for. Just browse through the development threads on XDA.

jhs39 said:
I don't think it's necessary to overclock the 6P. The most popular kernels are probably Franco's if battery life is your main concern or Elemental if you want more control over performance than you get with the stock kernel. I increased my battery life a bit by switching to Elemental but I didn't use any settings that would negatively affect performance, which is more important to me than battery life. Pure Nexus is a very popular Rom, although I didn't personally have a good experience with that one. I'm happy with Cortex. Some people prefer Megapixel. There's lots of custom ROMs depending on what you are looking for. Just browse through the development threads on XDA.
Click to expand...
Click to collapse
Ive been thinking about it for a while now, had everything downloaded. thanks, just installed Lineage OS.

It was not worth to root, actually, until Nougat was released. I remember getting very quick updates, that were actually improving user experience. I was actually a very pro-stock person, but recently i rooted my phone and installed Pure Nexus. Not going to stock anytime soon

IMO there is plenty to keep your tweaking urge satisfied even if you choose to just run the stock rom, rooted with a good kernel. Monthly updates, great root apps and rock solid. Regardless, you'll definitely want to unlock the bootloader and enable USB debugging. Don't worry about the persistent boot nag screen about locking the bootloader- It's normal. Best of luck.

Hi Guys, I've unlocked the phone and rooted as well. Running megapixel ROM now and I'm very pleased with the pixel experience.
Only thing that bothers my OCD is the warning screen when I turn on the phone that says phone cannot be checked for corrupted software or something. It says to lock the bootloader. I have seen some posts over here on XDA saying that even if I restore back to stock completely using the the factory images, that message won't go away. I wonder what will happen when I sell it...

Rooting back in the day (CM6 era) provided usefulness in providing features that were not available from factory.
Nowadays, OEM software has implemented many of those features to their devices which eliminates the need to root for a lot of people. Now that updates are once a month, it makes it an inconvenience to having to update properly. Safetynet doesn't pass without configurations and may fail in the future when the new exploits are patched. You'll also have to factory reset during version updates which make it a hassle.
IMO, rooting nowadays causes more of an inconvenience than purpose. I prefer getting updates quickly and easily without having to fiddle around and everything works as it should.
The main question is, what is the REAL reason why you're wanting to root? If it's solely for the purpose of feeling like you modified something your phone, then I would say keep it unrooted unless your willing to lose all your data when a major version comes out.
Sent from my Nexus 6P using Tapatalk

If you want to use your phone outdoor with a decent screen brightness, you'll have to root.

Jules Winnfield said:
If you want to use your phone outdoor with a decent screen brightness, you'll have to root.
Click to expand...
Click to collapse
Unfortunately, this will cause screen burn-in earlier.
Sent from my Nexus 6P using Tapatalk

ceo.mtcl said:
Hi Guys, I've unlocked the phone and rooted as well. Running megapixel ROM now and I'm very pleased with the pixel experience.
Only thing that bothers my OCD is the warning screen when I turn on the phone that says phone cannot be checked for corrupted software or something. It says to lock the bootloader. I have seen some posts over here on XDA saying that even if I restore back to stock completely using the the factory images, that message won't go away. I wonder what will happen when I sell it...
Click to expand...
Click to collapse
The message will go away if you restore fully to stock and then relock the bootloader.

jhs39 said:
The message will go away if you restore fully to stock and then relock the bootloader.
Click to expand...
Click to collapse
Thank you for confirming. I really hope that it goes away after full restore to factory settings. Is there any zip file available, flashing which will make it go away while I am on custom ROM? Or does it always stay on all custom ROMs?

ceo.mtcl said:
Only thing that bothers my OCD is the warning screen when I turn on the phone that says phone cannot be checked for corrupted software or something. It says to lock the bootloader. I have seen some posts over here on XDA saying that even if I restore back to stock completely using the the factory images, that message won't go away. I wonder what will happen when I sell it...
Click to expand...
Click to collapse
Don't worry about it. The nag warning is only present when your bootloader is unlocked, and you should leave your bootloader permanently unlocked. Eventually you won't even notice or care. If/when you return to stock, re-lock the bootloader and it will be gone.

richii0207 said:
Rooting back in the day (CM6 era) provided usefulness in providing features that were not available from factory.
Nowadays, OEM software has implemented many of those features to their devices which eliminates the need to root for a lot of people. Now that updates are once a month, it makes it an inconvenience to having to update properly. Safetynet doesn't pass without configurations and may fail in the future when the new exploits are patched. You'll also have to factory reset during version updates which make it a hassle.
IMO, rooting nowadays causes more of an inconvenience than purpose. I prefer getting updates quickly and easily without having to fiddle around and everything works as it should.
The main question is, what is the REAL reason why you're wanting to root? If it's solely for the purpose of feeling like you modified something your phone, then I would say keep it unrooted unless your willing to lose all your data when a major version comes out.
Click to expand...
Click to collapse
Some people prefer custom ROMs that give you features not included in stock Android. ROMs with Pixel features for instance are popular on the 6P and its unlikely most of those features will come to stock.

Someone Please Make A ROM!

I've been looking for a custom ROM for the OnePlus 7T Pro McLaren for some time now. I'm really hoping someone can do that as we can now unlock our SIM card lock, Root and put TWRP on our phones and get unlock tokens from OnePlus. I think we can all agree that getting better battery life is a must! I would also love having the customized feel of this phone. Let me know what y'all think, and let me know if your able to run the regular OnePlus 7T ROM's on this phone. I would love to meet someone with a ROM on the McLaren device.

Everyone wants that too. But it's not that easy. First we need to get a base software for the phone (international variant software or similar) and that isn't easy when we have different hardware and restrictions on software by OnePlus. Patience. It'll come at some point.
Tip: never buy a carrier based phone for the sole purpose of rooting or modifying. Things don't always go according to plan

I've said this before...I don't think the base for the 7T Pro McLaren is big enough for Dev's to devote the time needed to develop and maintain a ROM for us. This is a T-Mobile only variant only released in the US. Perhaps some of us who has one may take it on but I would not hold my breath. I do think we'll eventually get a TWRP that sticks once someone gets past the R/O for system.
I'm pretty happy unlocked with root for now.

Mike02z said:
I've said this before...I don't think the base for the 7T Pro McLaren is big enough for Dev's to devote the time needed to develop and maintain a ROM for us. This is a T-Mobile only variant only released in the US. Perhaps some of us who has one may take it on but I would not hold my breath. I do think we'll eventually get a TWRP that sticks once someone gets past the R/O for system.
I'm pretty happy unlocked with root for now.
Click to expand...
Click to collapse
That's what I'm thinking! My only issue with OxygenOS is the aggressive hibernation of apps in the background... At least with past OnePlus devices, trying to change every setting I could and using a custom kernel didn't always fix the problem.. however, I'm a bit of a noob when it comes to tweaking kernel settings, so that could have something to do with it. Any luck with adjusting this? I already requested my unlock token and I'm just waiting to hear back from OnePlus

champ784 said:
That's what I'm thinking! My only issue with OxygenOS is the aggressive hibernation of apps in the background... At least with past OnePlus devices, trying to change every setting I could and using a custom kernel didn't always fix the problem.. however, I'm a bit of a noob when it comes to tweaking kernel settings, so that could have something to do with it. Any luck with adjusting this? I already requested my unlock token and I'm just waiting to hear back from OnePlus
Click to expand...
Click to collapse
nope, we cant mount system rw so, rooting is sort of pointless

Has anyone found a solution for the excessive battery drain? I just got my token from OnePlus so I'm about to Root the phone and I'm hoping Greenify will work better once rooted. If anyone has any other tweaks to get better battery please don't hesitate to share!

If anyone has even tried. You can just take the source from lineage and build it.
Fix the bugs and there's your rom.
There's alot that goes on behind the scenes.
Ain't nothing on xda anymore but people demanding things instead of reading and learning.
Our device has different modem and that is one of our issues. Not to mention the fingerprint not working properly but apperantly nobody has tried to build it yet

I've been using Blu Spark's kernel and my battery life and performance increased tremendously.

Keepinitgreen said:
I've been using Blu Spark's kernel and my battery life and performance increased tremendously.
Click to expand...
Click to collapse
Is this the kernel you used ? https://forum.xda-developers.com/7t-pro/development/kernel-t4002711
Also is there a permanent twrp recovery ? You have a link ?

Mike02z said:
I've said this before...I don't think the base for the 7T Pro McLaren is big enough for Dev's to devote the time needed to develop and maintain a ROM for us. This is a T-Mobile only variant only released in the US. Perhaps some of us who has one may take it on but I would not hold my breath. I do think we'll eventually get a TWRP that sticks once someone gets past the R/O for system.
I'm pretty happy unlocked with root for now.
Click to expand...
Click to collapse
So should I buy this phone directly from one plus in stead on from t-mobile. Thanks In advance!!!
Sent from my [device_name] using XDA-Developers Legacy app

GDane1 said:
So should I buy this phone directly from one plus in stead on from t-mobile. Thanks In advance!!!
Click to expand...
Click to collapse
I just replied to your PM explaining this. Take a look whenever you get a chance. ??

champ784 said:
I just replied to your PM explaining this. Take a look whenever you get a chance. [emoji16][emoji16]
Click to expand...
Click to collapse
Sorry!!!
Sent from my [device_name] using XDA-Developers Legacy app