Rooting - Asus ZenWatch 2

I have rooted every phone that I have owned including tablets.
Could some one explain what the value is in rooting a watch?

Basically none. You could get a custom kernel and a recovery to backup your device, but I think it's a bit overkill.

If you're rooted you can disable system apps (useful for disabling Zenwatch Manager and getting rid of the annoying charging animation), as well as use Kernel Auditor to try to either speed up the watch or conserve a little more battery. Nothing earth-shattering but somewhat useful.

A question:
Why would you want to disable the zenwatch manager? I thought this was something of a very useful app?

I haven't found much use for it personally, I don't use any of its watch faces and most of the other functions are something that's already built into Android Wear by now. Mainly though, it's just that annoying charging animation that I can't disable. It's bright and it keeps me up at night.

Related

Want performance

Hi guys,
New android user here and using the P500. Just rooted my phone and only used a cpu overclock app on it. I want my phone to have better performance, I noticed this phone keeps running programs like settings, messaging apps, etc even though I never touched them, using up the ram pretty fast. Killed them with taskiller and other task manager apps but still they autostart after awhile.
How do I permanently disable them when not in use?
What other ways can I do to improve the performance?
I've read some threads here but as a noob android user I'm still lost. Hope to someone can guide me here and teach a thing or two.
From what I understand, those tasks running in the background will actually save you battery and memory. It has something to do with how the OS deals with many tasks at once. I'm not an expert at that so try reading a few articles on the android's task killing. There are pros and cons on both sides. I try not to mess around with my task killer anymore unless an app freezes on me.
Oh and the only way you can get rid of some is to uninstall the useless ones via root + root explorer or to use one of the many custom ROMs that have done away with bloatware. Most custom ROMs have the usual performance tweaks anyway so choose whichever has the least unnecessary apps (i went with the void-base ROM, almost zero apps then I manually installed the ones I will be using)

[Q] How to Disable Settings menu?

My children (twin boys) have phones (samsung i5500) and I'd like to be able to remove access to the settings option, mainly to prevent them messing around with passwords which they often forget. Tried searching google etc, but not seeing a solution (or anyone else asking)
Any idea how to do this? Both phones currently stock.
Thanks
You could try one of these:
https://play.google.com/store/apps/...51bGwsMSwxLDEsImNvbS5kb21vYmlsZS5hcHBsb2NrIl0.
https://play.google.com/store/apps/details?id=com.sp.protector.free&feature=search_result
https://play.google.com/store/apps/details?id=com.thinkyeah.smartlockfree&feature=search_result
Although note that Android is fairly "open" and there are probably ways around these. (I haven't tried any of them personally, nor have I tried to get around them. If your sons learn how to root the phones, they could probably easily remove any protection app you install. It may even be possible to just kill them from a task manager - you may want to block access to the Play Store also so that you must approve any apps they want to install)
EDIT: Just tried the first, seems to do the job well. I'd advise enabling the lock on "Settings" in the General tab and everything other than "incoming calls" on the Advanced tab. Haven't found anyway to get round it, so it seems to do the job.
EDIT: Having left it on my phone for a sort time, I noticed an increased battery drain (even just in half an hour). Not sure if others will be the same, or if this app always behaves like this, but if you notice battery draining quicker after installing one of these apps, you may want to try a different one.
Thanks, I've just found the same direction, it hadn't occurred to me earlier that settings was an app.
If you hit disable on settings app how do enable it back?

[Q] low battery (almost sleep) mode?

Hey guys,
I had an idea - since I'm really not "using" my Android S3 phone all day long, it gets frustrating when the bettery runs at 30% at 2pm, without any real use.
So the concept would be:
1) either a "ROM" of Android, which would be seriously minimal - like the device is not a smartphone - so only wake up on incoming call or text message
2) or an app, which does the same thing - suspends the phone completely, and wakes it up only on the incoming call or text message
I was just curious - does something like this exist? I don't care about apps, notifications, wifi or sync, I was thinking more along the lines of would it be possible to use your smartphone like a typical "cell phone", and when you need other apps or full features (GPS navigation with maps, or Shazam, or whatever it is you need) - you just "reboot" or do a qucik switch to "full Android" mode, and use those features.
Does any of this makes any sense?
I feel that the battery life should be at least 5 days in that mode, with light usage?
Anyway, I apologize if I got the wrong subsection of the forum, but I was just curious to see if anybody else already though of this, or if they didn't, would it be plausible? I'm a web developer, but I would maybe even try to make something like this in case there's a big need..
It's called deep sleep. Basically, your phone is always in deep sleep when the screen is off, unless there's an active wakelock. Usually, apps request those (or the kernel.) What you can do is to remove (or freeze) apps that request too many wakelocks… You can search around for more detailed info.
In your case, since you only want to use your smartphone as a phone, you could remove all the user apps. You can also remove Google services APKs from /system/app (root required.) To check what apps are requesting wakelocks, you can use Better Battery Stats (read the tutorial inside the app.)
Oh wow, cool! So someone though of this before me. Awesome!
Hey thanks so much for your quick reply, I'll read into the "deep sleep" logic, and I'll take a look at the app right away..
Thanks again man!
Some additional things to help:
Greenify (requires root for most effectiveness) - lets you hibernate apps
https://play.google.com/store/apps/details?id=com.oasisfeng.greenify
There's also the Donate package that will let you hibernate system apps.
That combined with something like this:
http://forum.xda-developers.com/showthread.php?t=2743316
or
https://play.google.com/store/apps/details?id=com.dianxinos.dxbs
Might help without having to do a bunch of crazy stuff.

Fixing a brightness issue

I have a weird problem with brightness on one of my devices. Bear with me while I explain.
The device in question is a Nexus7 v2. Android 4.4.4. It's unlocked and rooted, but otherwise stock.
I have this automation app installed called "Llama" - it let's you run certain actions conditionally(kinda like Tasker, but free). (I've looked at both and it seems Tasker is probably more powerful, but I only needed it for a few trivial things like making sure my devices are quiet at night, so I never looked further. Anyway, back ontopic.)
Recently I toyed around with this app and looked at what actions it could do - one of those being Adjust Brightness.
The problem is ever since the first time the app executed this action Android is basically internally always on manual brightness mode even when it's set to automatic.
This is becoming a rather significant usability issue because two of my main use cases for the device are reading books and watching media(videos). Both of these require the app to be able to force brightness levels.
Now however they refuse to do so because they think that Android is on a manual brightness setting.
See the screenshot to get an idea of what I'm talking about.
Things I've tried in increasing order of radicality are: Toggle auto-brightness manually, set brightness to auto via Llama, restart tablet, uninstall Llama.
I've also received no response from the developer, so by now I'm becoming open even to the idea of reinstalling the whole OS.
Of course I'd rather it not get to that as it's rather involved. So I'm open to other ideas.
Bumpity-bump-bump.
martixy said:
I have a weird problem with brightness on one of my devices. Bear with me while I explain.
The device in question is a Nexus7 v2. Android 4.4.4. It's unlocked and rooted, but otherwise stock.
I have this automation app installed called "Llama" - it let's you run certain actions conditionally(kinda like Tasker, but free). (I've looked at both and it seems Tasker is probably more powerful, but I only needed it for a few trivial things like making sure my devices are quiet at night, so I never looked further. Anyway, back ontopic.)
Recently I toyed around with this app and looked at what actions it could do - one of those being Adjust Brightness.
The problem is ever since the first time the app executed this action Android is basically internally always on manual brightness mode even when it's set to automatic.
This is becoming a rather significant usability issue because two of my main use cases for the device are reading books and watching media(videos). Both of these require the app to be able to force brightness levels.
Now however they refuse to do so because they think that Android is on a manual brightness setting.
See the screenshot to get an idea of what I'm talking about.
Things I've tried in increasing order of radicality are: Toggle auto-brightness manually, set brightness to auto via Llama, restart tablet, uninstall Llama.
I've also received no response from the developer, so by now I'm becoming open even to the idea of reinstalling the whole OS.
Of course I'd rather it not get to that as it's rather involved. So I'm open to other ideas.
Click to expand...
Click to collapse
Just wipe data from tablet's recovery mode.

[Q] greenify with edge

So i have my tmobile edge for a couple of days now and im not really impressed with the battery life so i installed greenify however its not showing me all the bloatware that came preinstalled, anyone else having these issues?
peste19 said:
So i have my tmobile edge for a couple of days now and im not really impressed with the battery life so i installed greenify however its not showing me all the bloatware that came preinstalled, anyone else having these issues?
Click to expand...
Click to collapse
Do you have experimental mode enabled? I think you need the donation pack as well as root to greenify system apps.
didnt know about that, i tried going to experimental features and you are right donation package is needed however it says xposed is needed also, is xposed compatible with s6 edge? afraid of installing stuff to brick my device. I was trying to avoid rooting it for now since i see alot of people are bricking their devices, waiting for a fix.
Has anyone noticed some improvements using greenify with s6?
peste19 said:
didnt know about that, i tried going to experimental features and you are right donation package is needed however it says xposed is needed also, is xposed compatible with s6 edge? afraid of installing stuff to brick my device. I was trying to avoid rooting it for now since i see alot of people are bricking their devices, waiting for a fix.
Click to expand...
Click to collapse
You don't need Xposed to greenify system apps. There are some other features in the experimental section that it enables, but you don't need them. (And you are right that xposed is not compatible with the edge).
However, if you are not rooted the System freezing doesn't work very well in my experience. It freezes them but they often start running again on their own. Thus you wind up with it trying to close them all down each time you turn off the phone. You might be better off disabling what apps you can manually instead.
Overall I didn't find Greenify to be great when not rooted - sometimes it gets stuck pressing the keys to force close the apps. The best way I found was to use tasker to trigger the hibernation when the phone has been idle for ~10minutes, but it was still a bit iffy.
It will probably be good enough to get you by for now if you think you will root later, but I am not sure I would bother if you probably won't ever root.
isangelous said:
You don't need Xposed to greenify system apps. There are some other features in the experimental section that it enables, but you don't need them. (And you are right that xposed is not compatible with the edge).
However, if you are not rooted the System freezing doesn't work very well in my experience. It freezes them but they often start running again on their own. Thus you wind up with it trying to close them all down each time you turn off the phone. You might be better off disabling what apps you can manually instead.
Overall I didn't find Greenify to be great when not rooted - sometimes it gets stuck pressing the keys to force close the apps. The best way I found was to use tasker to trigger the hibernation when the phone has been idle for ~10minutes, but it was still a bit iffy.
It will probably be good enough to get you by for now if you think you will root later, but I am not sure I would bother if you probably won't ever root.
Click to expand...
Click to collapse
how did you use tasker to enable the hibernation? i am a bit new at this
peste19 said:
how did you use tasker to enable the hibernation? i am a bit new at this
Click to expand...
Click to collapse
I just had a look but unfortunately I don't have the profile anymore to export it for you.
Doing it from scratch would be a bit daunting if you have never used Tasker before.
You basically need to:
1. Set a variable for the display state (ie, on, off and unlocked). %DisplayState
2. Have a task for the screen unlock which sets a variable %NeedToGreenify or similar.
3. Have a task for the when screen off event triggers and %NeedToGreenify is set. This task waits 10 minutes. Then check if the screen is still off - this is what %DisplayState is for (Stop if it is not). Clear %NeedToGreenify. Trigger Hibernate (Greenify is a 3rd Party Plugin). Wait 30 seconds. Turn the screen off "SecureSettings - LockDevice".
I think I may have also used SecureSettings to keep the screen on while the process is running. You will also need to set the task options to "abort existing task" if it is already running.
I think this is how it worked, but it was a while ago :/

Categories

Resources