Ever since I've had this phone I've been experiencing the error in the title above. I've rooted, tried freezing apps I think might be the problem, and just tonight I unlocked the bootloader, which wipes everything, and was hoping the error would go away. It only happens the first time upon boot. I hit either Wait or OK and it goes away until next boot.
Not a big deal, but curious what's causing it. Just wondering if anyone has this issue.
This is the 16gb Prime version, rooted, debloated, unlocked bootloader.
Cheers!
joesee said:
Ever since I've had this phone I've been experiencing the error in the title above. I've rooted, tried freezing apps I think might be the problem, and just tonight I unlocked the bootloader, which wipes everything, and was hoping the error would go away. It only happens the first time upon boot. I hit either Wait or OK and it goes away until next boot.
Not a big deal, but curious what's causing it. Just wondering if anyone has this issue.
This is the 16gb Prime version, rooted, debloated, unlocked bootloader.
Cheers!
Click to expand...
Click to collapse
It's interesting. I just purchased another one for my wife and right out of the box it does the same thing. I guess this is just something that people deal with and don't talk about??
joesee said:
It's interesting. I just purchased another one for my wife and right out of the box it does the same thing. I guess this is just something that people deal with and don't talk about??
Click to expand...
Click to collapse
I have had my phone for almost 3 weeks BLU R1 HD Prime version, I get no error messages, system or otherwise. I Have rooted it, unlocked the bootloader and removed the ads.
joesee said:
It's interesting. I just purchased another one for my wife and right out of the box it does the same thing. I guess this is just something that people deal with and don't talk about??
Click to expand...
Click to collapse
Check your permissions
joesee said:
It's interesting. I just purchased another one for my wife and right out of the box it does the same thing. I guess this is just something that people deal with and don't talk about??
Click to expand...
Click to collapse
Never experienced that issue. That's odd it's occuring on two devices. Who is your carrier, could it possibly be a sim issue??
ariesgodofwar said:
Check your permissions
Click to expand...
Click to collapse
Which permissions would you be referring to? A fresh reboot after a factory reset does it.
kal250 said:
Never experienced that issue. That's odd it's occuring on two devices. Who is your carrier, could it possibly be a sim issue??
Click to expand...
Click to collapse
I thought about that too, but I've tried two different carriers.. T-Mo, and Cricket. Both do it, regardless if one is in one slot or both are in either.
Like I said, it only does it after the first reboot, then I never see it again.
joesee said:
Ever since I've had this phone I've been experiencing the error in the title above. I've rooted, tried freezing apps I think might be the problem, and just tonight I unlocked the bootloader, which wipes everything, and was hoping the error would go away. It only happens the first time upon boot. I hit either Wait or OK and it goes away until next boot.
Not a big deal, but curious what's causing it. Just wondering if anyone has this issue.
This is the 16gb Prime version, rooted, debloated, unlocked bootloader.
Cheers!
Click to expand...
Click to collapse
My LG G4 does this sometimes. Just click wait to avoid dropping a system process. It probably represents a random error during boot, but it never seemed to hurt anything enough to justify a full investigation.
Niki Kidman said:
Go to settings, and choose permission authority!
Click to expand...
Click to collapse
So are you just posting ramblings for the sake of increasing your post counter, or are you serious with these nonsense suggestions?? WTF is permission authority??!!??
Niki Kidman said:
Go to settings, and choose permission authority!
Click to expand...
Click to collapse
haha ... wow....
kal250 said:
So are you just posting ramblings for the sake of increasing your post counter, or are you serious with these nonsense suggestions?? WTF is permission authority??!!??
Click to expand...
Click to collapse
My HTC 10 just gave me this system stopped responding error right after rebooting - Now I'm beginning to think it's just a new "feature" in Marshmallow. When I have some extra time, I'd like to see if I can figure out what does this - more for the sake of learning than anything else.
Related
So, I rooted my last N7 to give the "washed out screen after video" fix a try (which worked great for me, btw). I decided that I couldn't live with the yellow tint to the screen, and the screen lift got worse on that unit while I owned it, so I processed it for a return and will wait a little awhile until stock is back in B&M stores (tired of the UPS shuffle).
Unfortunately, this was my first time rooting and I had the mistaken impression that performing a factory reset got rid of root. Oops. I therefore sent it back while still rooted.
What do you think the chances are that the tech who inspects it for the return will check it for root? If he does and they reject the return, so be it. I'm kind of inclined to think it's not really something they regularly check.
Thoughts? Just how much anxiety should I allow myself to feel over this screw up?
All they have to do is turn it on to see that it is rooted, which they will probably do to check out the yellowish tint. As for if they will decline your return or not, I have no idea. If you sent it to Google you should be ok but ASUS has a zero tolerance policy when it comes to rooting and warranty (They have denied legitimat physical issues due to rooting).
miketoasty said:
All they have to do is turn it on to see that it is rooted, which they will probably do to check out the yellowish tint. As for if they will decline your return or not, I have no idea. If you sent it to Google you should be ok but ASUS has a zero tolerance policy when it comes to rooting and warranty (They have denied legitimat physical issues due to rooting).
Click to expand...
Click to collapse
Not to highjack, but I think myself and wynand32 might share similar curiosity now that you brought that one point up - What did ASUS do in that scenario? Did they ship the unit back to the customer?
miketoasty said:
All they have to do is turn it on to see that it is rooted, which they will probably do to check out the yellowish tint. As for if they will decline your return or not, I have no idea. If you sent it to Google you should be ok but ASUS has a zero tolerance policy when it comes to rooting and warranty (They have denied legitimat physical issues due to rooting).
Click to expand...
Click to collapse
How can they tell it's rooted just by turning it on? I didn't mention that I was smart enough to re-lock the bootloader...
Oh, and yes, this was a return to Google Play. Note that it's the same facility where ASUS takes returns, however.
Well, whatever happens, keep us posted! I would be interested in knowing how this gets resolved.
I'll definitely report back. But if anyone wants to clarify that "they can tell it's rooted by turning it on" part, I'd appreciate it. I know there's an unlock icon when the bootloader's unlocked, but I wasn't aware of anything obvious when it's "just" rooted.
Thanks!
wynand32 said:
Thoughts? Just how much anxiety should I allow myself to feel over this screw up?
Click to expand...
Click to collapse
£159/$200 worth of anxiety...
wynand32 said:
I'll definitely report back. But if anyone wants to clarify that "they can tell it's rooted by turning it on" part, I'd appreciate it. I know there's an unlock icon when the bootloader's unlocked, but I wasn't aware of anything obvious when it's "just" rooted.
Thanks!
Click to expand...
Click to collapse
The booting up should look like stock but (s)he could see the superuser app
Thats the only difference visible from just going through
Jordanooo said:
The booting up should look like stock but (s)he could see the superuser app
Thats the only difference visible from just going through
Click to expand...
Click to collapse
The boot animation, going into "About Device" if you flashed a ROM/kernel, finding the superuser app. Any of the above.
I would think it wouldn't make a difference if you're returning it for hardware issues.
Sent from my Nexus 7 using Tapatalk 2
ExploreMN said:
I would think it wouldn't make a difference if you're returning it for hardware issues.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
As I stated above, ASUS has denied warranty returns for faulty charging ports because the tablet was rooted.
I'm pretty sure Asus has a problem with unlocked bootloaders, not root access. The OP should be fine.
Sent from my Galaxy Nexus using xda premium
Jordanooo said:
The booting up should look like stock but (s)he could see the superuser app
Thats the only difference visible from just going through
Click to expand...
Click to collapse
Well, since I'm new to all this stuff, here's what I think: I did relock the bootloader, so the unlock icon isn't there. I didn't install a different ROM, so it's just rooted stock. I did a factory reset, so there shouldn't be any obvious app loaded (should there?).
I'd hope that the tech would have to open a terminal and do an su command or somesuch, but that's really what I'm wondering now. Will a stock N7 that's been factory reset show anything obvious?
CrazyPeter said:
£159/$200 worth of anxiety...
Click to expand...
Click to collapse
Hee hee... Yeah, I was waiting for someone to say that. That's not precisely correct, though, because even if they refuse the return they'd just have to send it back to me (and charge me shipping) or maybe take it but charge a restock fee (which they're waiving because of the defects).
So, the cost would be at most about $37, or about $15 and I'd be stuck with a yellow tint and screen lift. Which is to put a precise price on the anxiety...
wynand32 said:
Well, since I'm new to all this stuff, here's what I think: I did relock the bootloader, so the unlock icon isn't there. I didn't install a different ROM, so it's just rooted stock. I did a factory reset, so there shouldn't be any obvious app loaded (should there?).
I'd hope that the tech would have to open a terminal and do an su command or somesuch, but that's really what I'm wondering now. Will a stock N7 that's been factory reset show anything obvious?
Click to expand...
Click to collapse
Nope. Just superuser app in the app draw
Jordanooo said:
Nope. Just superuser app in the app draw
Click to expand...
Click to collapse
Okay, so, sorry to be obtuse, but: there's a "superuser app" that's installed in the app drawer even on a stock device that's been factory reset? Now I'm just curious how all this stuff works. I had no idea that such an app was installed when I rooted the N7, and that the app would remain when it was reset.
Now I wish I had an N7 to play with to see how it all works.
wynand32 said:
Okay, so, sorry to be obtuse, but: there's a "superuser app" that's installed in the app drawer even on a stock device that's been factory reset? Now I'm just curious how all this stuff works. I had no idea that such an app was installed when I rooted the N7, and that the app would remain when it was reset.
Now I wish I had an N7 to play with to see how it all works.
Click to expand...
Click to collapse
It's in /system/app therefore considered a "factory" app and will not be affected by /data reset
Harry GT-S5830 said:
It's in /system/app therefore considered a "factory" app and will not be affected by /data reset
Click to expand...
Click to collapse
Okay, thanks. It'll be interesting to see if 1) the tech notices the app/rooting and 2) if they reject the return because of it. Of course, there's also the chance that they'll notice that it's rooted and not reject it, in which case we may never know.
I'll report back...
I can't comment personally but you may find this interesting: http://youtu.be/9YcIHaajda8
Actually, now that I think about it, the last time I RMA'd my Transformer Prime, I just wiped it and did not unroot. Asus didn't have a problem with it.
So, I made the mistake of uninstalling ItsOn on my Sprint HTC One M8. Now I am unable to use data, sms, make calls, wifi report it's unstable. What the hell is going on? I have attempted to reinstall an RUU and even after that I get the same errors. I am on the verge of going into the Sprint store tomorrow for a replacement. I called HTC and they think the SIM card might be bad. I checked it and it looks fine. Is there something I can reinstall to fix this or is my phone dead just from that one uninstall?
Try flashing a stock 4.4.4 rom it will come stock with itson. Then do a ##72786# reset to attempt to restore your original data settings. Which way did you remove itson?
I used ROM Toolbox to uninstall ItsOn. I have reinstalled a stock rom on my phone in the hopes it would restore, but I still can not use any of the radios. This is crazy.
Just speculating. I almost wonder if this ItsOn also handles the phones antenna encryption. Possible there is some partician this is saved on and by uninstalling it I also wiped the partician. Add in the RUU do not contain it. Either way, guess I have to stop in at the Sprint store today and get a replacement.
ItsOn is in the /carrier partition aswell you cannot simply remove it. To attempt to fix your problem can you go into ##3282# and enter your msl go into data profile and hit restore and reboot. Also to remove itson on a stock rom flash this in recovery https://www.dropbox.com/s/md83hn4um0i5p09/Remove_ItsOn.zip?dl=0
Crud, don't think I have the MSL number.
If you are s-off download msl reader from play store otherwise youll have to get it from sprint
EVOuser94 said:
ItsOn is in the /carrier partition aswell you cannot simply remove it. To attempt to fix your problem can you go into ##3282# and enter your msl go into data profile and hit restore and reboot. Also to remove itson on a stock rom flash this in recovery https://www.dropbox.com/s/md83hn4um0i5p09/Remove_ItsOn.zip?dl=0
Click to expand...
Click to collapse
Now that I think about it. I think Sprint tech support had me do this. I recall a menu where it did this last night.
Most techs will give you the ##786# code to do this. Try a simpler ##72786# that one wont require msl
Ok, got the code and ran what you said. Still dead. HTC just had me do a recovery wipe. I think this is hardware related now. Software would have been restored at some point. I would think it would have restored once I loaded the RUU stock ROM.
Possibly, You could always try to connect to a wifi and do a handsfree activation aswell
All these "fixes" are speculation, I couldnt know your exact problems unless i had the device in hand. Just know Im trying
EVOuser94 said:
Possibly, You could always try to connect to a wifi and do a handsfree activation aswell
All these "fixes" are speculation, I couldnt know your exact problems unless i had the device in hand. Just know Im trying
Click to expand...
Click to collapse
Tried the wifi route, but wifi is also messed up. It will connect to my wifi network, but reports the connection is unstable.
Cataract2 said:
Tried the wifi route, but wifi is also messed up. It will connect to my wifi network, but reports the connection is unstable.
Click to expand...
Click to collapse
Yeah, at this point id also agree its hardware. Getcha a replacement haha
EVOuser94 said:
Yeah, at this point id also agree its hardware. Getcha a replacement haha
Click to expand...
Click to collapse
Lol, I better hope it's hardware. I figured it best to come clean with HTC and let them know it was rooted. So, they will have their diagnosis team look at it and if they determine the root caused it then I might be out some $$$ for the repair of it.
Still don't see how the root could cause this in the end. Unless there is a section that the RUU doesn't get.
Cataract2 said:
Lol, I better hope it's hardware. I figured it best to come clean with HTC and let them know it was rooted. So, they will have their diagnosis team look at it and if they determine the root caused it then I might be out some $$$ for the repair of it.
Still don't see how the root could cause this in the end. Unless there is a section that the RUU doesn't get.
Click to expand...
Click to collapse
Id hold your tongue on that, HTC doesnt really care too much they just see it as a defective device and they RUU themselves and if that doesnt fix it they pretty much use it as spare parts or remelt and rebuild a new one that will work. silence and claiming ignorance is key to winning them over lol
EVOuser94 said:
Id hold your tongue on that, HTC doesnt really care too much they just see it as a defective device and they RUU themselves and if that doesnt fix it they pretty much use it as spare parts or remelt and rebuild a new one that will work. silence and claiming ignorance is key to winning them over lol
Click to expand...
Click to collapse
Bit late on that. I told the care personel over chat that I did. They still offered the swap program that they were offering in the beginning. We'll see what happens. Dunno if they tag my account with regards to it or not. I just was thinking since the bootloader says **relocked** they might notice that and freak.
Cataract2 said:
Bit late on that. I told the care personel over chat that I did. They still offered the swap program that they were offering in the beginning. We'll see what happens. Dunno if they tag my account with regards to it or not. I just was thinking since the bootloader says **relocked** they might notice that and freak.
Click to expand...
Click to collapse
Lol, nah, you got lucky but they hardly ever look at that stuff
EVOuser94 said:
Lol, nah, you got lucky but they hardly ever look at that stuff
Click to expand...
Click to collapse
First time warrantying a phone, let alone a smart phone. Wasn't sure. Will remember that in the future. Guess I should always remember the human condition. Everyone is lazy.
Lesson learned on this though. Do not uninstall ItsOn. Just in case this truly is a software issue. Though I doubt it.
BTW, does that uninstaller you sent me work? Is it based on the Bad Boyz uninstaller? I'm just a bit leary after this experience to attack that again. Though I do not like it using 40% of my battery.
Cataract2 said:
First time warrantying a phone, let alone a smart phone. Wasn't sure. Will remember that in the future. Guess I should always remember the human condition. Everyone is lazy.
Lesson learned on this though. Do not uninstall ItsOn. Just in case this truly is a software issue. Though I doubt it.
BTW, does that uninstaller you sent me work? Is it based on the Bad Boyz uninstaller? I'm just a bit leary after this experience to attack that again. Though I do not like it using 40% of my battery.
Click to expand...
Click to collapse
The one i sent you is for stock, bad boys is for his rom
EVOuser94 said:
The one i sent you is for stock, bad boys is for his rom
Click to expand...
Click to collapse
Just because I want to read up some more. Where did you get yours from? Is there a thread about it or a how to?
I was in settings/storage, and tapped on apps. The phone lagged then opened the apps section. I tapped the back button and then the phone shut off and restarted. I am rooted, twrp recovery, but using the stock rom.
Has anyone else experienced this at all? Wondering if it is a widespread thing, or not.
v8dreaming said:
I was in settings/storage, and tapped on apps. The phone lagged then opened the apps section. I tapped the back button and then the phone shut off and restarted. I am rooted, twrp recovery, but using the stock rom.
Click to expand...
Click to collapse
Cool story bro
I've been getting way too many random reboots. Something as simple as turning off wifi or turning it back on will cause it. I'm not sure why it does it and I'm fully stock, unrooted. I've seen suggestions about clearing the cache and I've done that, but the problem continues. I'd say it does it on average once every couple of days.
Now that's a cool story, bro.
v8dreaming said:
I was in settings/storage, and tapped on apps. The phone lagged then opened the apps section. I tapped the back button and then the phone shut off and restarted. I am rooted, twrp recovery, but using the stock rom.
Click to expand...
Click to collapse
That stinks huh?! Unfortunately though if you wanted someone to truly help figure that out you'd want to have a Log of some sort
dennistpm said:
I've been getting way too many random reboots. Something as simple as turning off wifi or turning it back on will cause it. I'm not sure why it does it and I'm fully stock, unrooted. I've seen suggestions about clearing the cache and I've done that, but the problem continues. I'd say it does it on average once every couple of days.
Now that's a cool story, bro.
Click to expand...
Click to collapse
Have you tried just saving all your stuff and wiping the phone clean and starting fresh?
Mistertac said:
That stinks huh?! Unfortunately though if you wanted someone to truly help figure that out you'd want to have a Log of some sort
Have you tried just saving all your stuff and wiping the phone clean and starting fresh?
Click to expand...
Click to collapse
I've thought about wiping and starting over, but I'd rather find out that it's a known issue with a fix before I go through all of that work. It's not like I've been flashing ROMS and messing around with the radios or anything like that.
Mistertac said:
That stinks huh?! Unfortunately though if you wanted someone to truly help figure that out you'd want to have a Log of some sort
Click to expand...
Click to collapse
I didn't think about that until after I posted. I totally spaced on that.
I was more wanting to know if it was a widespread problem. I didn't word my post very well.
DSA said:
Cool story bro
Click to expand...
Click to collapse
Thanks for your super-informative, helpful post.
v8dreaming said:
Thanks for your super-informative, helpful post.
Click to expand...
Click to collapse
The quality of my post was no less than yours...which you admit to other people, but took umbridge with mine...lol
Hypocrite much?
v8dreaming said:
I didn't think about that until after I posted. I totally spaced on that.
I was more wanting to know if it was a widespread problem. I didn't word my post very well.
Click to expand...
Click to collapse
Hey it's all good! I wasn't scolding you or something.. I've been there myself. Hop on here and try to explain something that just happened with my phone and while I'm writing it... Think to myself... Guess a log would have helped lol
RELEVANT TO US BECAUSE WHEN WE GET THE UPDATE, IT LOCKS THE BOOTLOADER.
IF THEY LOCK IT FOR THE S6 EDGE, THEY'LL LOCK IT FOR THE S6!
DO NOT TAKE THE OTA IF YOU DON'T WANT A LOCKED BOOTLOADER.
Unassuming Galaxy S6 edge users are in for a surprise, as T-Mobile appears to be rolling out a freshly cooked OTA based on Android version 5.1.1 Lollipop for the device. The catch, however, it is so far reported only on the T-Mobile network.
XDA forums user Sunderwear mentioned about the OTA a couple of hours back (at the time of writing this story). Urged by other users of the device, the poster also uploaded a video of his Galaxy S6 edge running the latest firmware. The video can be found at the end of this article.
As noted from the narration, the update also locks the bootloader on the device.
So, how many of you have already received the update? What do you think of it?
Source: http://www.sammobile.com/2015/04/29/android-5-1-1-ota-being-rolled-out-on-t-mobile-for-the-s6-edge/
Looks like someone in the Edge forum was able to downgrade the bootloader and flash TWRP but still, tread carefully.
Sunderwear said:
ok I downgraded the Bootloader ONLY and I was able to flash TWRP...dumping a system.img copy..
Click to expand...
Click to collapse
Honestly I'm caring less and less about roms but I like the option. Here is some possible good news from a trustworthy guy
jcase said:
Korean variants seem to be getting an app that unlocks the bootloader, I bet we start seeing that for other variants as well (except verizon/att).
This is a good thing, not a bad thing people!
Click to expand...
Click to collapse
ThePagel said:
Honestly I'm caring less and less about roms but I like the option. Here is some possible good news from a trustworthy guy
Click to expand...
Click to collapse
Coming from the ROM Flashing mecca of HTC and finding a place in Samsung is.. weird to say the least. I find that there are only minor things I need that require root but I no-longer need the overhaul that I needed with HTC. It's too weird.
nolimit78 said:
Coming from the ROM Flashing mecca of HTC and finding a place in Samsung is.. weird to say the least. I find that there are only minor things I need that require root but I no-longer need the overhaul that I needed with HTC. It's too weird.
Click to expand...
Click to collapse
I see you edited your signature!
If/when anyone gets this update try to grab the update before taking it. Also, the bootloader Doesn't actually get locked.
mikeyinid said:
If/when anyone gets this update try to grab the update before taking it. Also, the bootloader Doesn't actually get locked.
Click to expand...
Click to collapse
BOOM. Bootloader news is great news
Isn't it odd that just one guy has gotten the update? T-mobile has sold hundreds of thousands of these units and only one guy got an OTA?
I'll believe it when I see it.
Is it possible to do the update if we are rooted? And I mean UPDATE not flash the entire new release.
ipaq_101 said:
Isn't it odd that just one guy has gotten the update? T-mobile has sold hundreds of thousands of these units and only one guy got an OTA?
I'll believe it when I see it.
Click to expand...
Click to collapse
This type of thing might happen with a lot of updates. You need to remember the rooting/moding community is very small compared to the people who just use their phone as is. So if anything I think its weird that someone in this community got the update.
Hey I hope it's true, I for one hope it fixes the memory management and battery issues.
According to this guy, it looks like the XDA member was part of a "Soak Test", or he is a guinea pig. Hopefully it doesn't take months to test it.
http://www.forbes.com/sites/gordonk...5-1-1/?utm_campaign=yahootix&partner=yahootix
ipaq_101 said:
Isn't it odd that just one guy has gotten the update? T-mobile has sold hundreds of thousands of these units and only one guy got an OTA?
I'll believe it when I see it.
Click to expand...
Click to collapse
it's a leak...also camera is buggy...not a final version
ipaq_101 said:
Hey I hope it's true, I for one hope it fixes the memory management and battery issues.
According to this guy, it looks like the XDA member was part of a "Soak Test", or he is a guinea pig. Hopefully it doesn't take months to test it.
http://www.forbes.com/sites/gordonk...5-1-1/?utm_campaign=yahootix&partner=yahootix
Click to expand...
Click to collapse
Never.... EVER... take anything from that website serious.
JoeFCaputo113 said:
Never.... EVER... take anything from that website serious.
Click to expand...
Click to collapse
Haha yeah, tech reporters are a bunch of iMorons as it is and love iCrap over everything else. I was shocked that they even knew what xda was.
Someone has the balls to try it on the non-edge S6?
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/development/5-1-1-blck-tw-t3096994
timeToy said:
Someone has the balls to try it on the non-edge S6?
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/development/5-1-1-blck-tw-t3096994
Click to expand...
Click to collapse
I hope no one tries this. Both devices are TOTALLY different.
J-Hop2o6 said:
I hope no one tries this. Both devices are TOTALLY different.
Click to expand...
Click to collapse
They're really not, actually. I imagine it would boot. My guess is touch screen wouldn't work though.
mikeyinid said:
They're really not, actually. I imagine it would boot. My guess is touch screen wouldn't work though.
Click to expand...
Click to collapse
Yea, I remember reading about the touch screen not working or working in reverse.
J-Hop2o6 said:
Yea, I remember reading about the touch screen not working or working in reverse.
Click to expand...
Click to collapse
Really? So it might work but register touches opposite of our phone?
nolimit78 said:
I find that there are only minor things I need that require root but I no-longer need the overhaul that I needed with HTC. It's too weird.
Click to expand...
Click to collapse
This
Damn I wish this would leak for AT&T. 5.0.1 TW has a bigger memory leak than stock 5.0.1 on my Nexus. This needs to be rolled out ASAP, but I know it won't.
Got my phone delivered yesterday. So far very impressed. No issues, except for one app issue. Greenify behaves wonky on this handset. When I go in to hibernate apps, it seems to stall during the hibernation process. It *looks* like instead of force stopping the app, it does something with moving the app to SD card. I say that because I can "see" it pressing the move to sd button, instead of the force stop button. It's weird. Anyone else notice this?
Did you ever figure this out, I didn't notice any issues with it. I just rooted mine today and plan on using the Greenify rooted. I'll let you know if I see a difference.
ItGuyJax8430 said:
Did you ever figure this out, I didn't notice any issues with it. I just rooted mine today and plan on using the Greenify rooted. I'll let you know if I see a difference.
Click to expand...
Click to collapse
No. Never figured it out. I also posted on the Slickdeals thread and someone there confirmed the same thing. I just uninstalled it until someone finds a workaround. Honestly though, I'm not super worried about it. I'm getting between 5-6 hours of SOT without it.
ItGuyJax8430 said:
Did you ever figure this out, I didn't notice any issues with it. I just rooted mine today and plan on using the Greenify rooted. I'll let you know if I see a difference.
Click to expand...
Click to collapse
Can you give me the idea to root your phone? Is it Unlock bootloader, then twrp/cwm, then root?
Thanks
quyvinh said:
Can you give me the idea to root your phone? Is it Unlock bootloader, then twrp/cwm, then root?
Thanks
Click to expand...
Click to collapse
Check out the guides tab, it has a great guide in getting rooted and unlocked.
Sent from my VIVO XL using Tapatalk