avlock[10] is a (the first?) real, *system-level* lock screen replacement for Android (CM 5.0.6).
it replaces the standard "connect the dots" behavior with pin-like mechanism. patterns can be arbitrarily large, and nodes can be repeated. also, there are no numbers -- just circles. definitely not for everyone, but i think some people may like it.
here's how it works:
http://files.clangen.org/avlock/avlock.m4v
if you want to try it you must have CM 5.0.6 installed, then:
1. reboot to bootloader
2. nandroid backup <-- do it. seriously. just in case.
3. flash avlock[x].zip
4. reboot
5. if you don't have a lock pattern already, set one: Home > Menu > Settings > Location and Security > Set Unlock Pattern
faq:
q: what happens if something goes really wrong and i can't log in?
a: i've been tweaking this mod for a long time and you shouldn't have any problems. BUT IF YOU DO:
* restore from nandroid backup made in step 2 above
OR
* if you know how to use adb, just delete the file pattern file and reboot:
adb remount
adb shell rm /data/system/gesture.key
adb shell reboot
q: what files are replaced by the patch?
a: framework.jar, framework-res.apk, android.policy.jar, Settings.apk
q: why not just distribute this as a simple .apk file?
a: this is a system-level mod because it replaces system-level components. it cannot be distributed as an .apk.
changelog:
avlock[8]:
* initial release
avlock[9]:
* added tactile feedback
* reduced login delay
avlock[10]:
* disabling "Use visible pattern" works now
* better integration with system and Settings.
* re-added drag lock option.
avlock[11]:
* added the ability to specify a pattern timeout
use at your own risk. i am not responsible for any damages caused by this software. MAKE A NANDROID BACKUP FIRST!
caution: if you update your rom, install a theme, or flash another mod that replaces framework.jar, framework-res.apk, or android.framework.jar, you may not be able to log in upon reboot (or even spin into a boot loop). either (1) make sure you disable your lock screen before flashing or (2) rm gesture.key as described in the faq!
download:
avlock[11]: http://droidbasement.com/db-blog/?p=202 (thanks, pershoot)
sources:
http://github.com/avatar5d
wow, nifty and works well enough
It'd be really nice if it was faster, there is close to a 2 second lag between entering and unlocking
Cool Thanks
Nice , i agree with the faster unlock and if it's possible to install it via apk or another methode than flashing in recovery mode.
Good work.
Thanks
imfloflo said:
Nice , i agree with the faster unlock and if it's possible to install it via apk or another methode than flashing in recovery mode.
Good work.
Thanks
Click to expand...
Click to collapse
You could always unzip the zip and push the files manually
adb shell stop
adb push these files to their respective places framework.jar, android.policy.jar, Settings.apk
adb shell start
If you forget the pattern, you can get it emailed to you right?
Looks awesome in the video, nice idea, better executed!
NICE MOD!
Nice work!!!
prettyboy85712 said:
Nice work!!!
Click to expand...
Click to collapse
+1 Nice ...
Good Job !
This looks awesome! Nice work
@ _avatar
Any chance to make this work with Enom's ROM ?
Nice work!
imfloflo said:
Nice , i agree with the faster unlock and if it's possible to install it via apk or another methode than flashing in recovery mode.
Click to expand...
Click to collapse
Unfortunately, because this is a system-level mod it cannot be installed as a simple .apk.
bobtentpeg said:
It'd be really nice if it was faster, there is close to a 2 second lag between entering and unlocking
Click to expand...
Click to collapse
The delay is there on purpose. Once you stop touching the circles for 2 seconds, the combination is verified. Without this delay, there would need to be some sort of "OK" button, which I think is undesirable. However, I'll look into making the delay shorter (1 second?) for future builds. The value needs to be long enough so people can still enter their combination relatively slowly, but fast enough so it's not annoying.
pvillasuso said:
Any chance to make this work with Enom's ROM ?
Click to expand...
Click to collapse
Possibly. Is Enom's source available, and easily buildable like Cyanogen's? I'm not super familiar with his project.
This is hot, installing now. My main complaint with the stock lock pattern was the inability to re-use points. just gotta set a good lock pattern and see how this works.
Thanks.
Wow.. this is pretty damned cool! Good job.
One thing, tactile feedback is not working with this, any way to restore that?
daveid said:
One thing, tactile feedback is not working with this, any way to restore that?
Click to expand...
Click to collapse
It's on my TODO list
EDIT: added to avlk[9] build. see original post!
Can you make a them of some sort and replace the dots with numbers?
Can it run on 1.8.1 rom
Re: [MOD] avlk[9], a real, system-level lock screen replacement
anyway to incorporate trackball wake-up in this for us desire port guys ;-)
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
_avatar said:
Possibly. Is Enom's source available, and easily buildable like Cyanogen's? I'm not super familiar with his project.
Click to expand...
Click to collapse
http://android.git.kernel.org/
You'll want to ask him which actual tag he's building for current versions. Also, since I'm not up on framework patching, it might be more complicated if you don't want to break the trackball-wake and/or notification features. Best to contact him @enomther or for someone to raise the suggestion in his thread.
Related
Google Maps 5.0 Fix - Two Finger Rotation for Cm 6.1.1 - distinct multitouch for passion + CM 7 nightlies
- [As CM 6.1.1 did not get the latest commits and #cm_nightly_296 failed here´s it]
- [you can use this for CM 7 nightlies till they get it by default ]
Now, there are 3 ways to install this select yours, according your experience! (...as surprisingly still, some got probs to copy/paste...)
1.)
How to:
- in ../system/etc/permissions/..
- exchange "android.hardware.touchscreen.multitouch.xml" with "android.hardware.touchscreen.multitouch.distinct.xml"
- set permissions:
Code:
adb shell chmod 644 /system/etc/permissions/android.hardware.touchscreen.multitouch.distinct.xml
- reboot
2.)
How-to:
1. - connect your device via usb
2. - put "android.hardware.touchscreen.multitouch.distinct.xml" into C:\AndroidSDK\tools\
3. - put "distinct_multitouch.bat" into C:\AndroidSDK\tools\
4. - run (doubleclick) "distinct_multitouch.bat"
5. - wait tills reboots, done
3.)
How-to:
1. - put "distinct-multitouch-signed.zip" on sdcard
2. - flash from recovery (if you have probs, toggle signature verification)
.
..more than 300 downloads here..so I had to do a new thread. So it does not get lost.
Trying it!
Sounds great!
Works* on rooted stock
*As well as the CP2K will let it, at least.
Awesome, works! But I can see why google disabled it by default.. not exactly the smoothest experience.
daisun said:
Awesome, works! But I can see why google disabled it by default.. not exactly the smoothest experience.
Click to expand...
Click to collapse
But Google could of kept the functionality for the N1 by using the trackball for rotation. (I can pan with the screen in the same way the Nx S does and use the trackball for rotation when in the 'perspective' mode).
It is weird that it works on Evil's Desire HD rom.
daisun said:
Awesome, works! But I can see why google disabled it by default.. not exactly the smoothest experience.
Click to expand...
Click to collapse
I think it's something to do with the crazy screen rather than smoothness.
When I installed Maps 5 on my phone I knew that I wouldn't get rotation due to HTC's superb choice of touch screen sensor (sarcasm). But what is weird to is that my girlfriend didn't get rotation either on her captivate. That's not normal is it? I though Samsung hardware was supposed to have great touch support. Or maybe the rotation is just in froyo? She running Eclair still...
Anyhow, I`ll try that fix for sure! Is that gonna work with CM 6.1.1 Stable?
vk2bea said:
But Google could of kept the functionality for the N1 by using the trackball for rotation. (I can pan with the screen in the same way the Nx S does and use the trackball for rotation when in the 'perspective' mode).
Click to expand...
Click to collapse
Can you, or would you like to?
Thanks Rori! It may not be the smoothest, but I am glad that there is an option to use it.
Getting permission error when trying to copy file to Permissions folder.
Any easier way to fix this?
BrumBrum74 said:
Getting permission error when trying to copy file to Permissions folder.
Any easier way to fix this?
Click to expand...
Click to collapse
adb remount
is this for MIUI Rom, too? has anyone tried yet?
Thanks rori. It works! It is not smooth, but at least I have an option to use when needed.
Works for me, great thanks!
Yep, works here.
Used Root explorer, moved over the file to the dir, deleted old file, set permissions.
Well it "works," but its really hard to get it working, and its not as accurate as my friend's evo or incredible
why is this necessary for CM6.1.1 again ?
i dont seem to have a problem with map5.0 rotation / 3d function
Great work! Works fine on my N1 with CM 6.1.1. Thanks!
lsxrx7 said:
why is this necessary for CM6.1.1 again ?
i dont seem to have a problem with map5.0 rotation / 3d function
Click to expand...
Click to collapse
3D? How did you get it work?
I know there are a couple posts out there on how to fix this, but this is one of the most legitimate ways to fix the multitasking issue we have all come to know and hate on Android devices running Sense. If you don't want to install a whole new ROM, such as MEANROM, you don't have to! This is a small guide to using the V6 SuperCharger script by Zeppelinrox. I know the amount of steps seems like a lot, but it's really not that many. Most of the steps will be followed by just reading what you see on the screen and accepting the recommended option!
Zeppelinrox said:
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
So fasten your seat belts and enjoy the ride!
Click to expand...
Click to collapse
So, everything you need to know or want to know can be found at Zep's original thread here. There is a lot of information, and because he is so technical, I think that sometimes his instructions can be hard to read for some, so I thought I would put together a VERY SIMPLE GUIDE to give you guys a hand. You can find the best instructions from him under Installing/Using.
http://forum.xda-developers.com/showthread.php?t=991276
On to the instructions...
How To Use Supercharger
Please only proceed if you are rooted and have busybox
Download script manager from the market: https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en
Download zep's latest V6 Script (V6_SuperCharger_for_Android-Update9_RC11_Test_6.sh.pdf): http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
remove the .pdf extension (should now end in .sh) and place on your phone /sdcard (you can use rom tool box or estrongs to rename the file)
At this point, I highly recommend you make a nandroid through TWRP or CWM. The script has a built-in undo feature, which works well, but I still think we all know this is best.
Open up Script manager on your phone. Make sure to check 'Browse as Root' Option
Navigate to the location wher you placed the V6 .sh script
Click the Skull/Crossbones to run as root. This should turn green. NOTE: DON'T USE THE BOOT OPTION
Hit Run
At this point, get ready for an onslaught of text. Don't be afraid and try your best to read even though much of it may not make sense!
You may be asked about your launcher. Answer the question correctly for your setup.
Any time you are asked to press Enter, go ahead and proceed. This is the last time I will tell you to hit Enter for most occasions.
Pick your scrolling speed. I recommend slow or normal the first time you do this, so you can keep up.
On the kernel panic screen, I recommend choosing the Rock(H)ard Option, so hit H and then enter
Accept the Misc and 3G tweaks by hitting Y
Feel free to keep or disable the annoying animation (the scrolling V6 at the beginning of the script)
Hit Y(es) for SuperMinFree Calculator settings. This is an automatic calculation. You can change this later when you get more confident. Many will choose the 1000HP option for our phone (based on available memory)
It will now backup your build.prop and some other system files.
ICS and newer Android services store a lot of the memory tweaks in services.jar. This script will now take you through an ICS patcher. Accept the Automatic Transmission. This will upload services.jar, and download the patched one.
It will eventually tell you that it needs to wipe your caches and restart. You will definitely want to do this. You will need to wait 4-5 minutes while it rebuilds your Dalvik Cache
Almost done! After your phone boots up and stabilizes, go back into Script Manager. Navigate to /data/99Supercharger script. Check the SU (skull/crossbones) and check the boot option.
Zepelinrox said:
- Stock ROMs - It also creates /data/99SuperCharger.sh which you can load up on boot (run as root) with Script Manager. The OOM groupings work as well since it happens on boot in local.prop or build.prop (18 entries added)
Click to expand...
Click to collapse
Reboot your phone and now your phone will run the supercharger script on startup. If you ever want to verify that your script is working, or if you want to mess with any of the extra options (including removal), run the original V6 shell script you downloaded as root, just like we did at the beginning. This will tell you if you are 100% optimized and give you a whole menu of options to play with!
I can actually open multiple apps now and go back to the first one without it having to reload. Waze is the best example. If I ever switched out and then back, it always had to reload...not anymore! Again, this all seems like a lot, but it's really pretty easy once you give it a shot!
Let me know if anything is unclear so that I can adjust this OP to help others.
Make sure to give Zep a 5 Star Rating in his OP and also give him thanks, he is the man!
Reserved just in case.
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
bog3nator said:
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
Click to expand...
Click to collapse
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
adma84 said:
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
Click to expand...
Click to collapse
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
bog3nator said:
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
Click to expand...
Click to collapse
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
adma84 said:
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
Click to expand...
Click to collapse
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
bog3nator said:
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
Click to expand...
Click to collapse
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
adma84 said:
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
Click to expand...
Click to collapse
1. open script manager
2. click menu
3. click more
4. click advanced options
5. click scheduler
6. click add new task
7. click select file
8. navigate to 99supercarger file the script created and click on it
9.you can from there click on boot (inside the file you just clicked on)
10. click save
it will boot the script after the phone is done booting, to prevent the possibility of boot looping. you can also create an event to do an engine flush however often you want (i do one at midnight everyday)
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
adma84 said:
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i thought you were saying click the boot thing during install ....i am sorry haha i got really tired all of a sudden and stuff wass getting jumbled together...
v6 works awesome though i have been using it for about 1 year now on this phone and my old evo
Also, for anyone that gives this a shot, please post back with your results!
Not to be "that guy" buuuut the effects of v6 at least from my experience with this phone (again fresh frombcustoms preorder release) the day i got it i was rooted and installed v6 because ive used it on all my prior evos since i found it probably right around when zep released lol...anyways on this phone its a strictly placebo effect and actually created more lag and launcher reloads...i was running the 1000hp option and tried the i believe 750hp whatever the one down from 1000 is anyways both of them gave me same results and once i removed the script all was good in the hood as they say lol...but if its working for yall then maybe zep fixed some ish for this problem and i didnt know about it...well this epic runon sentence is finished sorry for the length and useless points
Sent from the depths of hell
yea i also used it on my og evo and i just put it on last night again on this one, tried the 750 option and 1000 option. today at school my memory got so low it locked my phone, that never happened with mean rom and the tweaks he puts in. undoing the supercharge now.
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
adma84 said:
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
no thanks man for helping out, i just think this phone doesnt do well with it, and that may be because of how HTC changed the multitasking settings themselves. it may conflict with v6
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
wileout said:
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
Click to expand...
Click to collapse
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
bog3nator said:
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Im thinking its sonething stupid like a character in the code is supposed to be one way and its mirrored the other way lol
Sent from the depths of hell
It's definitely helps with multitasking. I can keep apps open in the background much easier. Problem is that it chokes out the available ram for running apps, so it can make it feel sluggish. I think it's overtweaking the mem settings.
Hey guys, this is just a version of @franciscofranco's kernel built with DoubleTap2Wake and Sweep2Wake from Bricked Kernel merged in.
(By downloading and installing the kernel you assume all responsibility for any damage to your device, but I don't post images with the intention of this occurrence and test them to the best of my abilities.)
Download:
r57
boot image - https://sundergaming.com/downloads/hammerhead/franco.Kernel/boot-franco.Kernel-r57-dt2w.img
md5 - 9ba11b4c3f5cd963c69d54bbfd919fe1
zip - https://sundergaming.com/downloads/hammerhead/franco.Kernel/zips/boot-franco.Kernel-r57-dt2w.zip
*Color tweak is integrated since r30, check 2nd post for information on how to enable.
Want a dedicated build for color tweaks because your boot animation isn't pretty enough? Build it yourself. Sources below.
**Test builds posted throughout the thread.
Kernel is for 4.4.1/2 since r19
Installation:
fastboot flash boot boot_name_img
or
flash the .zip in recovery
Sources
Kernel - https://github.com/PhantomGamers/hammerhead
Ramdisk - https://github.com/PhantomGamers/ramdisk_hammerhead
Credits
@franciscofranco for his kernel - http://forum.xda-developers.com/showthread.php?t=2508284
@show-p1984 for the dt2w and s2w additions - http://forum.xda-developers.com/showthread.php?t=2524557
@flar2 for his on-the-fly color tweak, power key touch to wake suspend, and other general dt2w improvements. - http://forum.xda-developers.com/showthread.php?t=2519607
I do accept and appreciate any donations but I urge you to first donate to the amazing developers listed above for their work because my contributions are minimal and without them this kernel variant would not exist.
Franco's original thread for reference only:
franciscofranco said:
Hi all.
Currently does not work with recent CyanogenMod nightlies or any rom has uses CM sources as a base because they made underlying changes that are now incompatible with Kernels that don't follow their path.
Installation:
fastboot flash boot boot_name_img
or
flash the .zip in the recovery
Changelog:
http://kernels.franco-lnx.net/Nexus5/4.4/appfiles/changelog.xml
franco.Kernel updater Free apk: http://forum.xda-developers.com/showthread.php?t=1867127
Nexus Display Control Free apk: http://forum.xda-developers.com/showthread.php?t=2424467
Got any questions that you couldn't find after searching?
FAQ: http://forum.xda-developers.com/showthread.php?t=2532422
Disclaimer to moderators:
Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.
Cheers!
Click to expand...
Click to collapse
XDA:DevDB Information
franco.Kernel+DT2W/S2W, a Kernel for the Google Nexus 5
Contributors
PhantomGamers, franciscofranco, show-p1984, flar2
Kernel Special Features:
Version Information
Status: Stable
Created 2014-02-06
Last Updated 2014-02-06
Kernel Settings
Disabled by default. To enable execute the code next to terminal in adb shell or terminal emulator as root.
If you wish for it to be automatically enabled on boot you can create the file named in the boot section.
After creating this file you can still execute the terminal code to enable it immediately or you can just reboot and have the kernel enable it for you.
[DT2W/S2W]
S2W
terminal -
Code:
echo 1 > /sys/android_touch/sweep2wake
boot - Create /sdcard/fkSettings/fks2w
DT2W
terminal -
Code:
echo 1 > /sys/android_touch/doubletap2wake
boot - Create /sdcard/fkSettings/fkdt2w
Bottom Half Screen DT2W (Only allows you to double tap bottom half to turn screen on, instead of above.)
terminal -
Code:
echo 2 > /sys/android_touch/doubletap2wake
boot - Create /sdcard/fkSettings/fkdt2wps
S2Sleep
terminal -
Code:
echo 1 > /sys/android_touch/s2w_s2s
boot - Create /sdcard/fkSettings/fks2s
PWRKEY_SUSPEND (Turns off touch to wake when display is turned off with power button, reenables when turned on, useful for long idle periods, unaffected by sweep to sleep)
terminal -
Code:
echo 1 > /sys/module/qpnp_power_on/parameters/pwrkey_suspend
boot - Create /sdcard/fkSettings/fkpwrks
Touch Wake Timeout
terminal -
Code:
echo 15 > /sys/android_touch/wake_timeout
(15 is an example, include the number of minutes you prefer)
boot - Create /sdcard/fkSettings/fkwt with number of minutes to delay timeout (IE: text file with "15" inside)
[COLOR]
*This tweak is experimental and you use it at your own risk.
**Breaks gamma calibration apps.
terminal -
Code:
echo 1 > /sys/module/mdss_dsi/parameters/color_preset
boot - Create /sdcard/fkSettings/fkcolor
[WIDGETS]
*Thanks to @JsChiSurf
http://forum.xda-developers.com/showthread.php?t=2626476
[App]
*Thanks to @casperpas
http://forum.xda-developers.com/showpost.php?p=51682981&postcount=839
just giving my 2 cents, franco's kernel intention is to deliver a stable, optimized and battery efficient kernel for the n5, by baking in these S2W/DT2W features into the kernel, aren't you defeating the purpose? If I would want those features built in, I could have flashed Elementalx, Bricked etc. No offense but that's what occur to me, to others, it may be godsend. :good:
kashix said:
just giving my 2 cents, franco's kernel intention is to deliver a stable, optimized and battery efficient kernel for the n5, by baking in these S2W/DT2W features into the kernel, aren't you defeating the purpose? If I would want those features built in, I could have flashed Elementalx, Bricked etc. No offense but that's what occur to me, to others, it may be godsend. :good:
Click to expand...
Click to collapse
Elementalx and Bricked don't have Franco's custom hotplug driver, personally that's the main selling point of his kernel to me.
I don't particularly care for these features anyway though and just used this as a learning experience to build kernels.
(I am currently running this build though to play around with it, haven't noticed a huge difference in battery life myself)
I am used to flashing zips, I guess I am not advanced enough to flash img files. Can I get more detailed instructions on how to flash this?
This is very tempting to try out.
Thank you!
---------- Post added at 07:57 PM ---------- Previous post was at 07:57 PM ----------
durhamite said:
I am used to flashing zips, I guess I am not advanced enough to flash img files. Can I get more detailed instructions on how to flash this?
Click to expand...
Click to collapse
Flashify seems like it'd do the trick, if original Franco kernels are any indication.
Well, I tried it, and it works!
Thanks OP!
Tip: if u have FKU, put the img in the franco.kernel_updater bkp folder and restore if it were bkp. Most easy!
Sent from N5
durhamite said:
I am used to flashing zips, I guess I am not advanced enough to flash img files. Can I get more detailed instructions on how to flash this?
Click to expand...
Click to collapse
Yeah Flashify seems like your best bet if you're rooted.
I might try and include zip releases in the future, sorry for the inconvenience.
grumphy said:
Well, I tried it, and it works!
Thanks OP!
Tip: if u have FKU, put the img in the franco.kernel_updater bkp folder and restore if it were bkp. Most easy!
Sent from N5
Click to expand...
Click to collapse
Thanks for the confirmation!
Thanks for doing this. Will you be updateing this to keep up with Franco's releases, or was this a one time experiment?
Nastybutler said:
Thanks for doing this. Will you be updateing this to keep up with Franco's releases, or was this a one time experiment?
Click to expand...
Click to collapse
Yeah that's my plan, I'll most likely keep this going until franco includes his own DT2W feature or unless I run into some technically difficulty.
Welp. I'm having trouble getting the dt2w working. Here's what I'm entering in terminal emulator (after "su" of course) without the quotation marks: "echo 1> /sys/android_touch/doubletap2wake"
Nothing happens in the terminal after I hit enter, it just goes to a new command line, and if I turn the screen off it won't wake back up with a double tap. Did I enter the command in wrong?
Nastybutler said:
Welp. I'm having trouble getting the dt2w working. Here's what I'm entering in terminal emulator (after "su" of course) without the quotation marks: "echo 1> /sys/android_touch/doubletap2wake"
Nothing happens in the terminal after I hit enter, it just goes to a new command line, and if I turn the screen off it won't wake back up with a double tap. Did I enter the command in wrong?
Click to expand...
Click to collapse
The space between the 1 and the > is essential.
PhantomGamers said:
The space between the 1 and the > is essential.
Click to expand...
Click to collapse
Eureka! That was my problem. Thanks! Works a treat.
Gonna give this a whirl
edit: works great thanks so much! for subsequent kernels you release, will one have to put in that command every time?
Also so glad you carried over francos screen calibration too! you rule! And so glad you'll be supporting until (if) franco implements it.
What are you guys doing to put the device to sleep without hitting that button? I'd like to do without it all together
tyrellcorpnexus said:
edit: works great thanks so much! for subsequent kernels you release, will one have to put in that command every time?
Click to expand...
Click to collapse
Currently you need to do it every time you reboot but you can put a file in /etc/init.d to do it automatically.
tyrellcorpnexus said:
Also so glad you carried over francos screen calibration too! you rule!
Click to expand...
Click to collapse
Yeah it's essentially a straight franco build so anything he implements will be included as long as he pushes it to github
tyrellcorpnexus said:
What are you guys doing to put the device to sleep without hitting that button? I'd like to do without it all together
Click to expand...
Click to collapse
This isn't currently a feature of the kernel but I do agree that doubletap2screenoff and sweep2screenoff would be really neat.
I'm going to TRY to implement this myself but I wouldn't hold my breath because I'm not really experienced with this level of coding.
PhantomGamers said:
Currently you need to do it every time you reboot but you can put a file in /etc/init.d to do it automatically.
Yeah it's essentially a straight franco build so anything he implements will be included as long as he pushes it to github
This isn't currently a feature of the kernel but I do agree that doubletap2screenoff and sweep2screenoff would be really neat.
I'm going to TRY to implement this myself but I wouldn't hold my breath because I'm not really experienced with this level of coding.
Click to expand...
Click to collapse
I see I see. Thanks again! Hitting that button one time to go to sleep is better than waking every time as well that is for sure!
I'm used to putting my device to sleep with a gesture on Activator with my JB'en iPhone 5. But I still have to wake it using home or lock button so I guess its still needed on that as well..
I don't think double tap to sleep would be the best, what about when getting text to fit the screen on Chrome and such? Double tap is a relatively common gesture once the device is awake.
Also, any way you can walk me through how to make sure it automatically kicks in on a reboot?
This is too good
tyrellcorpnexus said:
What are you guys doing to put the device to sleep without hitting that button? I'd like to do without it all together
Click to expand...
Click to collapse
I have the LMT Pie controls and one of buttons on my second row is a key that turns the screen off. So now, in theory, I'll hardly ever have to use the power button. :good:
---------- Post added at 11:47 AM ---------- Previous post was at 11:40 AM ----------
PhantomGamers said:
Currently you need to do it every time you reboot but you can put a file in /etc/init.d to do it automatically.
Click to expand...
Click to collapse
Would you be kind enough to walk noobs like me through how to set up that file? Right now I've got a note saved with the command that I copy & paste into the terminal each time now, but I can tell that's going to get old pretty quick.
Nastybutler said:
I have the LMT Pie controls and one of buttons on my second row is a key that turns the screen off. So now, in theory, I'll hardly ever have to use the power button. :good:
Click to expand...
Click to collapse
Do you have a link to the APK and maybe a screenshot of what it looks like? I'd only be interested in this toggle.
tyrellcorpnexus said:
I don't think double tap to sleep would be the best, what about when getting text to fit the screen on Chrome and such? Double tap is a relatively common gesture once the device is awake.
Click to expand...
Click to collapse
I meant like the G2 does it, where it's only when you double tap on the notification or nav bar in certain apps etc
tyrellcorpnexus said:
Also, any way you can walk me through how to make sure it automatically kicks in on a reboot?
Click to expand...
Click to collapse
Nastybutler said:
Would you be kind enough to walk noobs like me through how to set up that file? Right now I've got a note saved with the command that I copy & paste into the terminal each time now, but I can tell that's going to get old pretty quick.
Click to expand...
Click to collapse
Trying to figure this out now, it would appear that the kernel doesn't actually have init.d support as my script isn't working... maybe I'm doing something wrong here.
PhantomGamers said:
I meant like the G2 does it, where it's only when you double tap on the notification or nav bar in certain apps etc
Trying to figure this out now, it would appear that the kernel doesn't actually have init.d support as my script isn't working... maybe I'm doing something wrong here.
Click to expand...
Click to collapse
Ah, in that case, that'd be awesome!
No worries, appreciate your work thus far.
This is so great :highfive:
I don't know if anyone else tried and ran into the same issue...
After installing Android N (NPC56W build) on my 6P I wanted to have Viper4Android working, so I enabled permissive mode.
Booom. The phone rebooted itself, I needed a few seconds to realize, it was in "safe mode", and looked like after the first boot (after flashing the rom). I was wondering what the hell went wrong. After a reboot everything went back to normal. I thought it is because the kernel doesn't support permissive mode. So I tried 3 other kernels, always the same result. Then I started to look deeper, and found out, that there is a "system integrity check", which reboots the phone into safe mode on selinux mode change.
I found the part in the source code, and disabled it. After two days of compiling, I finally got the that little binary called "logd".
I replaced the original in /system/bin in recovery and rebooted and in a root shell ran "setenforce 0". And it worked! This time no reboot, and the command "getenforce" returns "Permissive". I'm a happy person now that Viper is working.!
It was damn straight worth the 2 days of s**ing!
I didn't test it for more than an hour yet, so use it at your own risk! I'm not responsible if you phone get's damaged, or broken....
If any of you know a better solution, I'm open for it!
Otherwise: enjoy it!
This worked for me. Although it doesn't seem permissive stays through a reboot. But it's easy enough to change back. And viper works. Thanks.
bamfsig45 said:
This worked for me. Although it doesn't seem permissive stays through a reboot. But it's easy enough to change back. And viper works. Thanks.
Click to expand...
Click to collapse
Yes, the setting resets on reboot. You could put a one liner shell script in /system/etc/init.d. Then it would be set during boot.
I'm glad it worked for you too!
Is this a flashable zip?
Hmm....I also noticed this, because restoring of apps in Titanium Backup on Dev Preview only work if the phone in permissive.
Will this work in the Dev Preview 2????
EDIT: Thanks, it works for Dev Preview 2 as well
duminduweera said:
Hmm....I also noticed this, because restoring of apps in Titanium Backup on Dev Preview only work if the phone in permissive.
Will this work in the Dev Preview 2????
Click to expand...
Click to collapse
Just tested it on preview 2 and it works
TBU now able to restore my apps
hermes2xgreat said:
Is this a flashable zip?
Click to expand...
Click to collapse
I made a flashable zip to make it easier for most. Thank @gubacsek for the logd file.
This one will copy the original logd to the root of your sdcard in case you want to restore it: http://www.mediafire.com/download/6i2rrgr4f5wc4ty/copy_logd_backup.zip
MD5Sum: 800b86bb130f7cc0f558944569d62891
This one will replace the current logd with the modified logd: http://www.mediafire.com/download/9uo1j6h88x8o8z0/logd_replacement_permissive.zip
MD5Sum: f0f219552ace44e5f12297403f5fc8e3
Side Note: If you want Permissive to survive a reboot you will have to run a script in /su/su.d to make it persist.
Side Note 2: Don't forget to go into terminal and type su for root acces, then type setenforce 0 to set as permissive. You could also do this in an adb shell. You can test to see if it's in Permissive mode by typing getenforce in terminal (this info. is in the OP, but people tend to skip OP's).
EDIT: If you guys want to add a script so that SELinux boots up as Permissive every time you reboot, then flash this file: http://www.mediafire.com/download/6klkabmpa5h5xbf/add_permissive_boot.zip
MD5Ssum: ab3584c4044659653d3ec30f9732a50f
bouchigo said:
I made a flashable zip to make it easier for most. Thank gubacsek for the logd file.
This one will copy the original logd to the root of your sdcard in case you want to restore it: http://www.mediafire.com/download/6i2rrgr4f5wc4ty/copy_logd_backup.zip
MD5Sum: 800b86bb130f7cc0f558944569d62891
This one will replace the current logd with the modified logd: http://www.mediafire.com/download/9uo1j6h88x8o8z0/logd_replacement_permissive.zip
MD5Sum: f0f219552ace44e5f12297403f5fc8e3
Side Note: If you want permissive to survive you will have to run a script in /su/su.d to make it persist.
Click to expand...
Click to collapse
You're welcome! I was too lazy to create a zip file.
I will update the thread title to say it works on npc91k build too.
And I didn't even notice that TB works in permissive. I always install the app from playstore and restore only the data afterwards, because that was working. Thanks for the tip!
This is awesome. Thanks guys
This work great with my Preview 2 build.:laugh::laugh::laugh:
bouchigo said:
I made a flashable zip to make it easier for most. Thank @gubacsek for the logd file.
This one will copy the original logd to the root of your sdcard in case you want to restore it: http://www.mediafire.com/download/6i2rrgr4f5wc4ty/copy_logd_backup.zip
MD5Sum: 800b86bb130f7cc0f558944569d62891
This one will replace the current logd with the modified logd: http://www.mediafire.com/download/9uo1j6h88x8o8z0/logd_replacement_permissive.zip
MD5Sum: f0f219552ace44e5f12297403f5fc8e3
Side Note: If you want Permissive to survive a reboot you will have to run a script in /su/su.d to make it persist.
Side Note 2: Don't forget to go into terminal and type su for root acces, then type setenforce 0 to set as permissive. You could also do this in an adb shell. You can test to see if it's in Permissive mode by typing getenforce in terminal (this info. is in the OP, but people tend to skip OP's).
EDIT: If you guys want to add a script so that SELinux boots up as Permissive every time you reboot, then flash this file: http://www.mediafire.com/download/6klkabmpa5h5xbf/add_permissive_boot.zip
MD5Ssum: ab3584c4044659653d3ec30f9732a50f
Click to expand...
Click to collapse
Thanks soo much. This is a great tool to get done what I need without all the frikkin hassle
Work well on NPC91K build. Thanks
@gubacsek
I was browsing the supersu forums earlier and you should be able to type this in terminal or adb shell:
Code:
stop logd
setenforce 0
This will allow you set as permissive without replacing logd, and without rebooting into safemode.
So, we can have a script with those lines in init.d or /su/su.d to run at boot without messing with logd...this is probably good since the logd you complied may not work on Preview 3, etc.
EDIT: Just wanted to let everyone know it works. Fastboot flashed system.img to make sure logd was working as intended, meaning that it will send you to safemode when attempting to change SELinux. Once I made sure it was working properly I applied the commands mentioned earlier, and...
Success :good:
bouchigo said:
@gubacsek
I was browsing the supersu forums earlier and you should be able to type this in terminal or adb shell:
Code:
stop logd
setenforce 0
This will allow you set as permissive without replacing logd, and without rebooting into safemode.
So, we can have a script with those lines in init.d or /su/su.d to run at boot without messing with logd...this is probably good since the logd you complied may not work on Preview 3, etc.
EDIT: Just wanted to let everyone know it works. Fastboot flashed system.img to make sure logd was working as intended, meaning that it will send you to safemode when attempting to change SELinux. Once I made sure it was working properly I applied the commands mentioned earlier, and...
Success :good:
Click to expand...
Click to collapse
Nice! There is only one question left... What the f* is this logd doing? What happens if you stop it?
Anyway! Nice out of the box thinking I didn't even think about stopping it...
A very very big thanks for your great work @gubacsek and @bouchigo
With your work now I've got ViperMod and OK Google working at my N6 with preview 2 at http://forum.xda-developers.com/nexus-6/development/rom-stock-flashables-t3348657
Gesendet von meinem Nexus 6
spevil07 said:
A very very big thanks for your great work @gubacsek and @bouchigo
With your work now I've got ViperMod and OK Google working at my N6 with preview 2 at http://forum.xda-developers.com/nexus-6/development/rom-stock-flashables-t3348657
Gesendet von meinem Nexus 6
Click to expand...
Click to collapse
You are welcome! I'm happy I could help!
And I know the feeling I was also damn happy when it worked. Viper is the most important mod for me. Once heard the music through it, I can't live without it anymore...
YEAEEEEAAAAAHHH its absolutly that what i need!!!!
With this music its absolutly obligation
https://soundcloud.com/toxic-sickness/doctor-terror-exclusive-guest-mix-on-toxic-sickness-april-2016
https://soundcloud.com/eargasmpodcastofficial/eargasm-podcast-2-by-unproven
spevil07 said:
A very very big thanks for your great work @gubacsek and @bouchigo
With your work now I've got ViperMod and OK Google working at my N6 with preview 2 at http://forum.xda-developers.com/nexus-6/development/rom-stock-flashables-t3348657
Gesendet von meinem Nexus 6
Click to expand...
Click to collapse
It works without any crashes and with the screen off?
gubacsek said:
Nice! There is only one question left... What the f* is this logd doing? What happens if you stop it?
Anyway! Nice out of the box thinking I didn't even think about stopping it...
Click to expand...
Click to collapse
It looks like logd is just a logging binary; it seems like logd monitors for changes to the system that Google wants to keep track of, be it for informational purposes or, to stop people from messing with SELinux like we are seeing in this case. In this case logAudit.cpp and logAudit.h look for changes specifically to SELinux, and if one is detected it will either boot you to SafeMode, or to recovery depending on how the change comes about.
Does logd really need to be running? I'm not sure the answer to that, but I've had it shut off for the past couple of days so far with no ill effects that I have noticed.
EDIT: I compiled a new logd with preview2 source, and though it's a bit smaller in size than the one you compiled for preview 1, the result is the same as the one you compiled. It should be easy enough to compile a new logd for preview 3 in case your current one stops working for preview 3...as long as the preview 3 source is released quickly...or still use the stop logd command to completely stop it from running :good:
bouchigo said:
It seems like logd is just a logging binary; it seems like logd monitors for changes to the system that Google wants to keep track of, be it for informational purposes or, to stop people from messing with SELinux like we are seeing in this case. In this case logAudit.cpp and logAudit.h look for changes specifically to SELinux, and if one is detected it will either boot you to SafeMode, or to recovery depending on how the change comes about.
Does logd really need to be running? I'm not sure the answer to that, but I've had it shut off for the past couple of days so far with no ill effects that I have noticed.
EDIT: I compiled a new logd with preview2 source, and though it's a bit smaller in size than the one you compiled for preview 1, the result is the same as the one you compiled. It should be easy enough to compile a new logd for preview 3 in case your current one stops working for preview 3...as long as the preview 3 source is released quickly...or still use the stop logd command to completely stop it from running :good:
Click to expand...
Click to collapse
sighs... I know security and all, but it is just exhausting to try and get around new restrictions google is building into android all the time. I know it is okay for the masses, but seriously, there should be a master switch in android, or a special developer version which allows us to do what ever we want with our devices.
Anyway. Android is still by far the best and "developer friendly" OS in my opinion, so I'm just shutting up.
Yes, I also compiled a new logd already, but there is no change in the source, so of course it is working with both N builds. And I hope it will stay so in future releases
For those that don't know, here's how to enable Power saver mode on the vzw model.
You need:
Root
Root browser/ root explorer/ etc.
Navigate to system/ customize/ CID/ Default.xml. scroll about 1/3 of the way down until you find "def_hide_ui_powersaver" >1</item<item> and change value to "0".
Reboot device, then go to home screen, long press to add widget, select shortcuts, then down to power saver. This will put a shortcut to the power saver menu that is hidden from us.
Note that you must mount R/W or the edit will not work. This will not enable the quick setting or for it to show up in the regular power options menu but this will work for now.
Good luck
Thanks to aer0zer0 for pointing me in the right direction.
I can verify that this can also be enabled on unrooted devices as well. Credit goes to user l7777 in this post: http://forum.xda-developers.com/verizon-htc-10/help/verizon-version-missing-options-t3376634.
For the powersaver mode, try this from a computer with working ADB
Code:
Code:
adb shell "settings list secure | grep power"
If it returns something that looks like this
Code:
Code:
hide_ui_user_powersaver=1
Then try
Code:
Code:
adb shell "settings put secure hide_ui_user_powersaver 0"
This does not require root if done from a computer. It will require root if done from a terminal on the device. This is what works on an M9 running Marshmallow. It may or may not work on the 10. You can also try
Code:
Code:
adb shell "settings list secure"
To get a list of all the settings.
Click to expand...
Click to collapse
I had to restart my phone after making the change in ADB. The only thing that doesn't seem to work correctly is when I click on the Battery Saver Mode to edit the settings, I will receive an error message. The Battery Saver Mode will turn on and off with no issue.
Must have missed that one. I went through that post a couple days ago. Guess this will work for those that can't or don't know how to setup and use adb
Sent from my HTC6545LVW using Tapatalk
Evocm7 said:
For those that don't know, here's how to enable Power saver mode on the vzw model.
You need:
Root
Root browser/ root explorer/ etc.
Navigate to system/ customize/ CID/ Default.xml. scroll about 1/3 of the way down until you find "def_hide_ui_powersaver" >1</item<item> and change value to "0".
Reboot device, then go to home screen, long press to add widget, select shortcuts, then down to power saver. This will put a shortcut to the power saver menu that is hidden from us.
Note that you must mount R/W or the edit will not work. This will not enable the quick setting or for it to show up in the regular power options menu but this will work for now.
Good luck
Thanks to aer0zer0 for pointing me in the right direction.
Click to expand...
Click to collapse
If it is like the M9 on marshmallow, after making that edit, if you factory reset it, the menu option should appear in the standard menu. its alot easier to either put it in as a shortcut, or use xtended settings, and add it to the power menu, or gravity box, and add custom quicksetting tiles (1 of which being battery, it will also show battery temp and mAh remaining).
Once we get a deodexed based, or even a stock odex flash, we can make those edits prior to flash and it will be in the menu as normal
edit, i also believe if you edit the next line (120) def_hide_ui_user_powersaver and set it to 0, this is what will enable the menu on factory reset
Note that this survives reboot and/or power recycle. Using the adb approach for unrooted handsets, got it working on both my own and a test device.
UPDATE: So far as I can tell, the latest OTA to 1.19.605.22 breaks this ability.
hgoldner said:
Note that this survives reboot and/or power recycle. Using the adb approach for unrooted handsets, got it working on both my own and a test device.
UPDATE: So far as I can tell, the latest OTA to 1.19.605.22 breaks this ability.
Click to expand...
Click to collapse
Can confirm that the latest update definitely does break this ability (no root). =(
im_high_tech said:
Can confirm that the latest update definitely does break this ability (no root). =(
Click to expand...
Click to collapse
I think the only way to do this is to write to \system; so for those who don't want to flash a custom ROM or write to \system, it's out of reach for now.
And especially galling because the 10's on all the other carriers have the feature. Verizon kills it.
@andybones has it in the stock deodex base, but if you are working off of the odex base, the easiest way is probably gravitybox, and using the QS tile to toggle it (still requires root). Just make sure you are using systemless xposed to not touch the system partition as @hgoldner pointed out, if you need it.
by stock base, i mean OTA to 1.19.605.22
Battery Saver Mode Settings
You can change the power saver mode settings if you install the apk from apk mirror http://www.apkmirror.com/apk/htc-corporation/power/
klarthur said:
I can verify that this can also be enabled on unrooted devices as well. Credit goes to user l7777 in this post: http://forum.xda-developers.com/verizon-htc-10/help/verizon-version-missing-options-t3376634.
I had to restart my phone after making the change in ADB. The only thing that doesn't seem to work correctly is when I click on the Battery Saver Mode to edit the settings, I will receive an error message. The Battery Saver Mode will turn on and off with no issue.
Click to expand...
Click to collapse
This modification can be done using Magisk, without editing /system. You need to cache-mount the edited default.xml using Magisk, and Magisk mount the patched SystemUI.apk and HtcPowerManager.apk from @andybones' deodexed stock ROM. HUUUGE thanks to @Captain_Throwback for helping me figure this out and tolerating all-too-frequent stupid mistakes getting to this point, and, of course, none of this would be possible without the amazing efforts of @topjohnwu in creating Magisk in the first place.
I will post detailed instructions if someone is interested.
jackebuehner said:
You can change the power saver mode settings if you install the apk from apk mirror http://www.apkmirror.com/apk/htc-corporation/power/
Click to expand...
Click to collapse
I just tried installing this on my stock, non-rooted Verizon HTC 10 and it didn't give me any new options for power saver mode. I installed the most recent version from apk mirror and then rebooted. Everything looks the same. I'm on version 3.057.92923
Sent from my HTC6545LVW using Tapatalk
Chewieez said:
I just tried installing this on my stock, non-rooted Verizon HTC 10 and it didn't give me any new options for power saver mode. I installed the most recent version from apk mirror and then rebooted. Everything looks the same. I'm on version 3.057.92923
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
You have to follow the steps in post #2 before installing the APK does anything. The APK just makes it so that power saver mode settings doesn't crash.
jackebuehner said:
You have to follow the steps in post #2 before installing the APK does anything. The APK just makes it so that power saver mode settings doesn't crash.
Click to expand...
Click to collapse
I believe he is referencing the fact that not all of the available settings are shown. From screenshots of the book on the HTC one there should be settings for what power saver does.
CPU
Display
Vibration
Data connection
Useful settings. I would like to be able to turn down the processor without turning off data.
mrbacks said:
I believe he is referencing the fact that not all of the available settings are shown. From screenshots of the book on the HTC one there should be settings for what power saver does.
CPU
Display
Vibration
Data connection
Useful settings. I would like to be able to turn down the processor without turning off data.
Click to expand...
Click to collapse
You'll likely need a custom kernel for that, which means root access and either unlocked bootloader or S-OFF. Once you're in that boat, you'll need Magisk to clear Safety.net. It's not otherwise doable on pure unrooted stock. FWIW, if you are rooted, you can use @flar2's ElementalX kernel which is quite good, especially when used with the helper app allowing you to tweak all settings.