yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Edge Questions and Answers] Stevica Smederevac:
Can you try fastboot format data and fastboot format cache commands and see what's happening?
[Samsung Galaxy S7 Edge Questions and Answers] smaberg:
i can format data partition no problem, even in twrp, but all apps dissapear as i tought. and then i even didnt bother to try and boot as i want to do a full nandroid.
[Samsung Galaxy S7 Edge Questions and Answers] peachpuff:
If you thought you could install twrp and do a backup of the stock phone you were wrong, twrp can't read the data partition since its encrypted, you have to format data and then you can do a backup, but since there's nothing there then there's no point.

Get a stock image for your phone from http://updato.com/firmware-archive-select-model?q=g935f
[Samsung Galaxy S7 Edge Questions and Answers] smaberg:
Thank you, finally an answer
[Samsung Galaxy S7 Edge Questions and Answers] smaberg:
then another quesstion....

best and fastest way to rooted SU stock ROM preferable my carriers one, and how to do it?????
[Xiaomi Redmi 2 Questions & Answers] AkMunjal:
can anyone tell me about marshmallow rom which gives positive safetynet test ?
[OnePlus 3T Questions & Answers] sakumaxp:
Hey everybody I rooted my device this morning, and I was setting everything up again since it gets wiped during the process. So finally I come and try to login in to Snapchat and it says something similar to "log in has failed please try again later" anybody have this problem or a way to fix it? Thanks in advance!
[OnePlus 3T Questions & Answers] Anova's Origin:
Snapchat checks for root and purposely prevents you from logging in if it find it. If you rooted with SuperSU, try installing Chainfire's SUHide. Otherwise, if you rooted with Magisk, enable MagiskHide in Magisk Manager.
[OnePlus 3T Questions & Answers] martinsavvy:
I usually unroot with SU and login while unrooted, then flash whatever SU zip used to root again. It should work and you'll stay logged in.
[OnePlus 3T Questions & Answers] sakumaxp:
so i just do the full unroot option, sign in, then just flash the SU again?
[OnePlus 3T Questions & Answers] martinsavvy:
Yeah that's what works for me.
[OnePlus 3T Questions & Answers] sakumaxp:
OMG thank you so much that was so easy!!!!
[OnePlus 3T Questions & Answers] EuEra:
magisk is better though because you can still use android pay and mobile banking applications.
[OnePlus 3T Questions & Answers] sakumaxp:
If I throw on a custom ROM after wiping will I need to do this process again?
[OnePlus 3T Questions & Answers] Anova's Origin:
Yes. Unless the custom ROM has built-in root, you will have to flash SuperSU or Magisk every time you flash a ROM (including updating the same ROM to a newer version). Flashing a ROM replaces the files required for root in the /system or /boot partition.
[OnePlus 3T Questions & Answers] sakumaxp:
I shouldnt brick if i have to loose root and reflash super SU when I'm running a rom right? Sorry for all the questions
[OnePlus 3T Questions & Answers] Anova's Origin:
Suddenly losing root without a reasonable explanation would be a cause for concern and should merit further investigation.

However, simply flashing SuperSU after flashing a ROM (dirty or clean flash) shouldn't cause any issues.
[OnePlus 3T Questions & Answers] sakumaxp:
Yeah cos I would need to flash the ROM, then sign in to Snapchat, then go back to TWRP and flash super SU
[OnePlus 3T Questions & Answers] Anova's Origin:
Honestly, I would just recommend you to use Magisk to root. You can have it hide both root and itself from apps like Snapchat. Better yet, since Magisk Manager is not a system app, it will survive updates through dirty flashes. This means that after the initial set up, any time you dirty flash a ROM and then Magisk immediately afterwards, root is already set up and hidden from Snapchat the first time you boot up.

Also, be careful with flashing a ROM without rooting immediately. ROMs like OOS will either replace TWRP with stock recovery or trigger dm-verity if you don't root immediately after clean flashing.
[OnePlus 3T Questions & Answers] sakumaxp:
So I just have to download magisk manager and it should re-do everything for me if I understand correctly right?
[OnePlus 3T Questions & Answers] Anova's Origin:
You will have to remove all traces of SuperSU before flashing Magisk. If Magisk detects systemless SuperSU already present on your phone, it won't root it with its own method (and therefore cannot hide root from other apps). The easiest way to install Magisk over SuperSU is just to dirty flash your current ROM and then immediately flash Magisk v11.1 (don't forget to wipe cache/dalvik). After you boot, you will have to install the Magisk Manager app from the playstore if the Magisk.zip didn't already do so automatically. Then enable Magisk Hide and reboot your phone. Root should be hidden now. You will have to regrant root permissions for all of your root apps.
[OnePlus 3T Questions & Answers] sakumaxp:
I'm on stock ROM, so I guess I can go into super su and loose root then download magisk and get it that way
[OnePlus 3T Questions & Answers] mjuggle:
Thanks mate, it took forever to find this solution, it worked!

I use SU and it was simple to "unroot" from within the SU# app

1. settings scroll down to the "cleanup" section, select full unroot, accept all the warning messages, the phone will reboot into recovery and then reboot the phone after it finishes. Your phone may cycle through the reboot process a couple of times

2. log back into your phone, then you can log into the Snapchat app.

3. now you can re-root your phone, if you want to.

Cheers.
[Ubuntu Touch Q&A, Help & Troubleshooting] kennymc666:
Hi there

i try to install Ubuntu touch with the Multi ROM app. files downloaded successfully but when the installation boots into Recovery i get the error "system image upgrader failed" (see screenshot). after that i reboot to Multi ROM boot screen and select ubuntu installation to boot. that results in a bootloop of course because the installation is not completed/successfull and i end up in Multi ROM boot screen again.

i tried different versions of ubuntu touch but get the same error everytime.

is there a solution for this issue?

thanx for helping ;)

Sent from my One
[Ubuntu Touch Q&A, Help & Troubleshooting] Mr.Ak:
What is "Akku"?
[Ubuntu Touch Q&A, Help & Troubleshooting] kennymc666:
battery ;)

Sent from my One
[Ubuntu Touch Q&A, Help & Troubleshooting] Mr.Ak:
Ohh which language is this?
[Ubuntu Touch Q&A, Help & Troubleshooting] kennymc666:
german ;)

Sent from my One
[Ubuntu Touch Q&A, Help & Troubleshooting] kennymc666:
a recharchable battery is called "akku" in german language. but the word itself is not originally german. latin maybe? ;)

little off topic ;)

any idea how to solve the issue?

Sent from my One
[Xiaomi Redmi Note 3 Questions & Answers] EP21:
How to fix "Google license error" for paid apps that you've paid w/out gapps?

My problem is this – Google play services has a ****load of wakelocks and i want to remove the need of flashing gapps from my flashing experience. I have found a successful guide on how to get everything working, but as i have bought an app on the play store i now have to use it's servers to verify the validity of my purchase. So my question is has anyone found a way to verify such purchases without the play store?
[Samsung Gear S3] tamanaco:
While I had my my AT&T S3 Frontier LTE watch set to "Always On" I was getting something like a "Screensaver" which consisted of just the hour and minutes hands in white on a black background. It came on after the watch display dimmed and after the display time out. This happened while using the Chronograph+ (default) watch face. It was a distinctive + useful screen face that probably saved me some battery life. Now the displays dims after the time out and then it turns completely off (black). After I power cycled the S3 yesterday, I stopped getting this "Screensaver" and can't find the settings combination that will get this "screensaver" back. Does anyone know what I'm talking about and how to get it back?
[Samsung Gear S3] 10urshin:
Enable Settings -> Style -> Watch Always On
[Samsung Gear S3] Tel864:
I don't think I've really ever used the default faces. I know in a lot of the Watchmaker faces you can get a toned down face with maybe just the numbers and hands glowing when using AOD mode but I don't know about the default faces. In display settings there's a setting for auto low brightness that may affect that.
[Samsung Gear S3] tamanaco:
If you read the first sentence of my post you'd see that I'm already using this setting.
[Samsung Gear S3] 10urshin:
Yea i have read it. Not just first sentence but I also read the whole thing, you must admit it is not really making much sense. "Screensaver"? There is no such thing on this watch, only AOD and "Now the displays dims after the time out and then it turns completely off (black)." this sentence perfectly describes the AOD off behavior. So i thought it worth mentioning.

Only other thing that comes to my mind is default analog AOD watchface(attachment) which is something watch shows if the current watchface does not support AOD. But since you stated that you were getting your "screensaver" on Chronograph+ which supports AOD, it doesn't really make sense either.

Anyway hope you'll find your answer.
[Samsung Gear S3] tamanaco:
I also saw this "screensaver" mode in a review video somewhere, but I have not been able to locate it again. Once I find it, I'll post a screenshot of it.
[Samsung Gear S3] Tel864:
Thinking more about it, I don't think the AOD is even supposed to remain on all the time. That has been a major complaint, the AOD mode not being actually AOD. What you're experiencing now isn't normal and there should be no setting to change that. If you want to set up the watch again, you might try resetting it. That's assuming you've already tried just restarting it.
[Samsung Gear S3] boogisha:
What comes to my mind with "Watch always on" (or "Always On Display", AOD) and having screen completely black is if watch thought at some point that you weren`t wearing it - only in that case should the screen go completely black with AOD set, otherwise it should, well, keep "always on display", that`s the point of the setting :)

When you take the watch off your hand, then it goes blank even though AOD setting is still active - watch is "playing it smart" to preserve battery life in case where you`re not actively using it.

But, it`s possible for the watch to (wrongly) think that you`re not wearing it even when you do, thus turning the screen off when it should otherwise be in AOD mode (as set). For example, it can happen when your wrist band is a bit loose so the heart rate sensor has issues reading your pulse, or when the heart rate sensor itself is smudgy or otherwise blocked to make the valid reading - some people with tattoos reported that AOD doesn`t really work for them, having the screen constantly turning off (tattoo effectively confusing the heart rate sensor reading).

This is especially troublesome if you`re using "Samsung Pay", where the watch asks for you PIN in order to unlock itself every-single-time, as it`s thinking that you didn`t wear it in the meantime...

All this said, from what you described, it looks like AOD doesn`t work for you at all anymore, as what you seem to call "Screensaver" is actually AOD - a dimmed and more simple version of the watch, whose main purpose is to spare the battery while still providing a bit more realistic feel, having the watchface shown all the time.

There is additional "trick" to trigger AOD mode (once you have the setting configured), besides simply waiting for some (configured) time to pass by - just cover the watch with your palm for a few seconds, and it should fall back to AOD mode. If the screen goes blank instead, you might have an issue with the watch.

It would be good to have some default watchface in use when you`re trying AOD (like mentioned Chronograph+), just to opt out a possibly "broken" third-party watchface, and you could also check if "S Health" heart-rate reading works for you, starting a heart-rate readout manually (you can use a widget for that as well).

If the issue is still there, you may try restarting the watch again, or eventually soft (or factory) resetting might be a thing to go for, too, though you`ll have to setup the watch again, as already mentioned.
[Samsung Gear S3] annulation:
I have seen the exact same behavior. My AOD will suddenly become black and white, while normally it is full color, and any app icons that are usually on the AOD disappear. When the watch is active (by turning wrist or touching the screen), the full color face returns and looks normal - it is only the AOD that is always B&W. The difference for me is that I don't like it and I would like to figure out how to get it to stop happening.

I've had the watch for about 2 months and it has happened to me 3 times with different watch faces. It lasts from several hours to more than a day. I have changed every related face setting, changed faces, changed face settings, AOD settings, restarted, and reset the watch completely (and restore), but it still happens. The only thing that I've noticed may help (may be coincidence) is that it will stay indefinitely until I power cycle the watch. After restarting, the AOD remains black and white for a few hours and then suddenly the color AOD will return. Next time it happens I will take a pic.

I'm actually somewhat relieved that I'm not the only one who has seen this because my googling revealed next to nothing. I don't know if I would call this a screensaver, but it would be nice to be able to control it.
[Samsung Gear S3] tamanaco:
I knew I was not seeing things... please take a picture if it happens again, so that we can have a reference image. I'll do the same if it happens to me again. In certain situations... I actually like just having the hour and minute hands in "brightish" white on black background. Like you, I would also like to control it. I thought it was a "screensaver-like" feature as the watch face turns mostly black. But as you say, it might be a glitch... it has not happened to me since I last power cycled the S3.
[Samsung Gear S3] annulation:
Low Color AOD

I finally figured it out.

The behavior is called "Low Color AOD" and "High Color AOD". It is controllable by swiping from the right side of the screen near 5 o'clock straight up. This consistently toggles it for me, and a popup message shows a message saying either "Low Color AOD" or "High Color AOD". See pics attached (sorry, don't know how to rotate them).

Pics:

1. Low Color AOD

2. High Color AOD

3. popup message Low Color AOD

4. popup message High Color AOD

Only some faces support this behavior. For me, "Low Color AOD" always means monochrome B&W and no app icons.

PS - this face is called "Stylish Set" and the creator gives free coupons for it if you email him. It is one of the few faces I've found that shows day/date, with temperature and battery.
[Samsung Gear S3] scott14719:
As mentioned, the function described is dependent on the functionality of each watch face independent of the watch itself. If a given watch face supports it, it can be accessed. The "always on" function also depends on the capabilities of each watch face. Some have customized always on displays, and some do not (generic). The watch will go black if it senses it is not against the skin (the sensor on the back). This will also cause the watch to lock again and require the security code to re-activate. If a band is too loose, the watch can falsely think it has been taken off. The time that the watch face itself is on can be extended with an app called "Flaunt" available from the Galaxy app store. It can extend the original watch face active time to 30 minutes. It can then be re-activated to extend for other 30 minute time periods. Of course it does impact the battery life.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] ZeroInfinity:
ANNOUNCEMENT 14/01/18 PLEASE READ!

This kernel is based on 100% latest HTC official source. EAS was ported from scratch using [MENTION=5438598]RenderBroken[/MENTION] 's commits (with permission from him).

THIS KERNEL IS BATTERY ORIENTED! DO NOT EXPECT AMAZING PERFORMANCE FROM THIS KERNEL! PERFORMANCE IS DECENT ENOUGH FOR NORMAL USAGE! If you are here to try out performance then this is not the kernel for you. Do not go complaining about performance unless it is extremely bad.

Posts #3 and #4 are very irrelevant now, you can ignore these 2 posts.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] p50kombi:
Magisk version of HelixKernel PME EAS v012

AS OF V013 ALL VERSIONS ARE INTEGRATED INTO ONE SINGLE FLASHABLE ZIP, NO NEED TO FLASH SEPERATE FOR MAGISK SYSTEMLESS USERS

I will keep this post up for users of v012 for now.

MAGISK USERS USE INFORMATION AND DOWNLOADS BELOW

If you use magisk, you need to flash the following two files to keep your system untouched and systemless.

TO BE CLEAR, THESE FILES ARE MEANT TO BE USED ON A STOCK ROM

These files are meant to be used on stock rom, either with or without the magisk version of a rom from your favorite rom developper (Like Leedroid Magisk or Viper Magisk).

If you use a custom rom and or your system is not read only, there is no reason to use these files and it could cause conflicts with custom roms.

If you are running a custom rom and not a stock rom, please use the normal kernel file as per post #1 of this thread.

HelixKernel PME EAS Systemless V012

https://drive.google.com/open?id=0B9-84MJYFzJWMElyRGhvdTMyb2M

- The kernel only, system less so your system does not get tampered with.

HelixKernel PME EAS v012 ROM SUPPORT MODULE

https://drive.google.com/open?id=0B9-84MJYFzJWaUJtRC03Y3VpWVE

- The rom support module flashes the rom files as a magisk mod, so your rom uses them as a magisk module.

Without the rom support magisk mod, the kernel will not work optimal.

Flash both in twrp or the kernel in twrp and then the module in magisk manager, it's up to you, easiest is to flash both in twrp one after another.

The rom support file module should then show up in magisk manager, which means it works as should.

For more info on why to flash this version of the kernel, please check this post:

https://xdaforums.com/showpost.php?p=71552602&postcount=252
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Kyuubi10:
To understand Helix_schedutil you must first understand the original schedutil algorithm.

Here it is:

next_freq = maxfreq + (maxfreq >> bitshift) * util/maxcapacity

Explanation:

The most obvious difference of this algorithm is that it moves away from the idea of scaling frequencies up or down which were used in previous generations of governors.

Instead the aim of the above algorithm is to calculate the most appropriate frequency for the TOTAL CPU load.

NOTE: This is TOTAL load on CPU, not just load for the current frequency step as Interactive used to calculate with.

Now, for you numberphiles like myself that like understanding algorithms... Let's break it down:

Helix_schedutil -

UPDATE 20/3/17 (v008)

:

Correcting a misconception:

Some people describe tipping point as the load threshold which the governor uses to decide whether to ramp up or down.

While if you look into the behaviour of the governor it may appear that it behaves in such a way, it is technically incorrect.

As I mentioned previously this new algorithm moves away from the behaviour of legacy governor algorithms which focus on the current frequency load.

This governor does no ramping up or down.

It isn't even aware of the current frequency load, as it only knows the load relative to max capacity.

The misconception appears based on a property of the algorithm that results in a consistent load at any chosen frequency. This is a coincidental result of the algorithm, even though the algorithm is completely unaware of it.

Tipping point is in fact the load percentage at which the CPU reaches max frequency and any increase in load forces it to wake up a new core.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Mostafa Wael:
A collection of useful informative links about EAS:

1- My insight about schedutil, sched and HMP's Interactive governor behaviour. Despite the fact that my write up was dependent on the EAS implementation in my OnePlus 3, I think it is fairly relevant since I wasn't having any extra boost drivers or any PowerHAL changes at the time. In fact, I need to rewrite my analysis for the OnePlus 3 now since I got some powerHAL changes :o

More to come
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] DeeZZ_NuuZZ:
F.A.Q.

1. Will this kernel work with LOS/AOSP-based roms?

A. Yes, starting from version v18 we support AOSP/LOS-based roms. We've tested LOS and AOSP Nougat and Oreo roms and they like they should.

2. I have corrupted SDcard!

A. A temporary fix would be to reboot to recovery, mount USB storage, un-mount and reboot to system. Might be an issue with the exFAT nofuse driver.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] CharliesTheMan:
Reserved
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] TotallyAnxious:
There's nothing that should prevent Verizon support correct? Or at least I couldn't see anything on your git. If it's more of the issue of having no Verizon testers, then I'd be happy to clean flash my rom to test it.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] ZeroInfinity:
If you want to test it for me you may, I don't have any Sprint of Verizon users available but if the kernel is bugged on those devices then it may take some time for me to support them.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] antonio82:
I installed it and I have the corrupt card problem
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] ZeroInfinity:
what format is your card? exFAT, nor FAT32 formats should have problems with the kernel as it is based on the official source, I have not touched exFAT at all in fact.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] DeeZZ_NuuZZ:
Provide more information​ like ROM, recovery and everything else you've installed. And like zero said, there should be no problem as it is based on stock source and no exfat stuff touched

and please get us a log!
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] ZeroInfinity:
Right, [MENTION=4645599]DeeZZ_NuuZZ[/MENTION] confirmed exFAT not working even though I didn't even touch anything exFAT related in the kernel... Will try to find a solution for this.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] antonio82:
The format of the card I do not know because I put the card and I have not modified the card, I have the rom ice and the twrp 3.0.3-9
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] ZeroInfinity:
yeah it must be exFAT. Don't worry though, your card isn't actually corrupted, just the OS could not read it due to something wrong either in kernel or something wrong with texfat module. I advise you restore to your previous kernel until I've fixed this.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Haldi4803:
Please do! I didn't really understand much in #2 Post
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] antonio82:
I will keep it installed to see the operation and when it is corrected I will install it again
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] munkyvirus:
So I installed the kernel and rebooted and Magisk said it was uninstalled. I reinstalled the Magisk zip and everything was working again, but EXKM didn't pick up any EAS governor's beside the Helix one. I then ran the EAS tuning script from totally_anxious and it couldn't find any of the EAS tunables. Is this what the Magisk version will be for?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] ZeroInfinity:
Magisk versions in post 3 as said below the download link which I'm still waiting for [MENTION=271041]p50kombi[/MENTION] to upload when he's free.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] aer0zer0:
VZW HTC 10 here, good so far, no SD card problems, magisk is fine, gonna run it and see how it does battery wise.
[Tilt, TyTN II, MDA Vario III General] Yannn:
Everything is in the title !

I'm using the q-mobile 1.11 rom... and I have some informations in a reg files.

How can I lunch it ???