yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9  Questions & Answers] Devo7v:
No need to talk down to somebody, he may be genuinely trying to help.

That said, all the questions you are asking have been answered in various threads, I suggest searching in the future. If you flash anything that isn't signed by Samsung you will trip Knox. You can make the modifications you suggested to get rid of Facebook and anything else, but since you don't have the Samsung keys, once you flash it, you will trip Knox. There was some discussion that simply enabling the OEM unlock would trip Knox, but I haven't been able to verify that since mine is already tripped.

You can however use ADB commands to disable packages installed on your phone but once you update your phone they will be reenabled and you will have to run the ADB commands again. This may be a roundabout way of doing what you're trying to accomplish. Hopefully this is helpful.
[Samsung Galaxy S9  Questions & Answers] Youdoofus:
flashing a custom recovery triggers knox and its irreversible. flashing an official firmware will not reset the knox counter nor will it make the phone believe that knox isnt tripped

kinda snide, but ive seen worse especially considering the response he posted was rife with wrong stuff

enabling OEM unlock will not trip knox. personally verified on my A8. painstakingly went thru each step really slowly and deliberately to check that stuff out. XDA folks are posting more and more specific questions nowadays lol
[OnePlus 7 Pro Questions & Answers] valeriee:
I feel as if my phone isn't as snappy as it was before I rooted it. I'm running .11 with Renovate Ice and a few other magisk modules
[OnePlus 7 Pro Questions & Answers] Kaz205:
I bet its the magisk modules. They slow you down quite a lot depending on the size of them.
[OnePlus 7 Pro Questions & Answers] more_than_hater:
nothing here, vanced + viper
[OnePlus 7 Pro Questions & Answers] chazarss:
yes, i have always feel that rooting is slowing device. From OP 5, i use vanilla no root or else.
[OnePlus 7 Pro Questions & Answers] redpoint73:
Why would you feel that? Root is just a change to system rights. Root in itself doesn't slow the phone down. Mods made under root (such as Magisk modules) is another story.

Any number or reasons for a device to run the way it does. But folks suddenly start blaming "root" without any specific evidence.

To the top poster, it would seem disabling the modules would be an easy way to test the theory.
[OnePlus 7 Pro Questions & Answers] Paz9:
Magisk requires a daemon to run 24/7 it also hooks into logd process

So it is possible
[OnePlus 7 Pro Questions & Answers] galaxys:
Never noticed any slowness on my GM 2017! Rooted since day one...
[OnePlus 7 Pro Questions & Answers] DrMuhammadElHanafy:
I've come to that conclusion nearly 4 years ago, back in the days of Xposed.

I believe that altering system files in any way will have some effects on running speed and functionality in general.

Stock ATW.
[OnePlus 7 Pro Questions & Answers] intruda119:
I'm so confused.
[Nexus 6P Android Development] xmxrtyx:
[ROM][PIE-9.0][UNOFFICIAL] Cosmic-OS v4.0 - CORONA [Angler][2019/09/03]

/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Cosmic-OS is a Custom ROM based on Android Open Source Project (AOSP) with additional features, performance and battery life improvements.

Instructions for flashing:

Download ROM and GApps.

Copy ROM and GApps to internal storage.

Wipe /data, /system and /cache.

Flash ROM and GApps

Enjoy :P

Note: First boot and boots after every update can take some time. They may even loop a few times. We do not support custom kernels or mods like MultiROM. If you have an issue, make sure your edits aren't interfering with the issue you're reporting.

ROM

GAPPS

For GAPPS visit the site, select ARM64 in the Platform section, 9.0 in the Android section & in the Variant section choose the type of package you want to install.

Credits

- [MENTION=5863325]sagarshah1729[/MENTION] (Founder/Lead Developer)

- [MENTION=5842339]Sid_Sun[/MENTION] (Contributor)

- [MENTION=5834335]Agent_fabulous[/MENTION] (Contributor)

- Nitrogen Project

- LineageOS

- AOSCP

- OmniROM

- ABC ROM

- Dirty Unicorns

- Kabou Zeid for Phonograph

Have a feature request? Don't spam here. Visit our Google Plus community or Telegram group

Cosmic-OS Official Website:

Cosmic-OS

Cosmic-OS Google Plus community:

G+

Cosmic-OS Official Telegram group:

Telegram

Support Us

Hello, Gracious human! if you like our work, you may support us by donating:

Paypal

PayTM
​

XDA: DevDB Information

CosmicOS Pie, ROM for the Huawei Nexus 6P

ROM OS Version: 9.x Pie

ROM Firmware Required: TWRP, Unlocked bootloader

Based On: AOSP

Version Information

Status: Stable

Build Date:2019/09/03

Contributors

[MENTION=8086838]PixelBoot[/MENTION] (helping me out) [MENTION=7426783]beingmishra[/MENTION] (source and server) [MENTION=10096947]amallxw[/MENTION]

Rom Source: https://github.com/Cosmic-OS/
[Nexus 6P Android Development] xmxrtyx:
A few notes before you proceed:

Before going straight to the downloading, there’s something we would like to tell you. We have changed the default encryption method for the phone, migrating to File-Based Encryption (you can get more information from the official Google documentation page). In order to get this encryption mode working, you will need to use our custom recovery (compiled from the latest source) which is compatible with this encryption and, just for the first time, you will have to wipe your internal data, so backup your data before proceeding.
[Nexus 6P Android Development] xmxrtyx:
Installation Instructions:

Grab our recovery and install it.

Through TWRP Recovery:

Install Zip > Install Image > Choose ‘recovery.img‘ > Select partition ‘Recovery’ > Swipe to confirm flash

Through Fastboot:

fastboot flash recovery recovery.img

Install the ROM and then wipe your internal data partition.

Through TWRP Recovery:

Wipe > Format data

Through Fastboot:

fastboot -w

Reboot into system and wait until the process finishes, it could take a little bit. After the installation is done, I suggest waiting before using the phone because it usually goes into thermal throttling after installing a ROM.
[Nexus 6P Android Development] bigcelo75:
Is this system-as-root? I'm BLOD and patch won't work if it is!
[Nexus 6P Android Development] xmxrtyx:
This is system-as-root

we made a build for 4core devices with the patch but there few features which don't work.

I'll be building EvolutionX in few days.

I'll try not to make it SAR so that you can flash the blod patch :)
[Nexus 6P Android Development] bigcelo75:
I appreciate that my friend. Looking forward to it![emoji6]
[Nexus 6P Android Development] sage of six paths:
Installed it with no issues and so far so good. It's a complete rom, has everything i need even gray scale reading mode. Didn't notice any battery drain for now, but still i always enable agrressive sleep and standby. Will give any further thoughts after i used it for a while. The onyl thing is that the simple gapps do not work on this rom, had to use open gapps.
[Nexus 6P Android Development] xmxrtyx:
aight

?
[Nexus 6P Android Development] sage of six paths:
Oke so my review in short. The rom is as most roms just fine. For my usage i have no bugs to report. The only slight potential donwside might be that the battery life was not as good as on pixy or superior os, but its not far behind. However this might be due to, I've used a lot more lte with this rom than on those since I'm back to work form vacation, and second that my battery might be giving me slight signs it'll need a replacement soon. So take the battery thing with a grain of salt, try it your self first and compare.
[Nexus 6P Android Development] MaddScientist:
Is there a feature list for this rom?
[Nexus 6P Android Development] xmxrtyx:
check website?
[Nexus 6P Android Development] Steven_2302:
Hi, thanks for the ROM, runs great from the short time I had on it (forgot to get gapps package) when I got opengapps 9.0 stock it said that the ROM needed opengapps for 8.1, same with Pico, pretty confusing. Any help would be great
[Nexus 6P Android Development] kenetix:
Gapps issue

I even tried Simple Gapps, thinking maybe they would work. Will try 8.1, but it definitely won't use 9.0 gapps. BTW, I downloaded the nano gapps. Other than that, this rom is absolutely beautiful. It is fast, and it is just a very good-looking rom. So, I hope you keep working on this. I can't say enough about how quick it is. So, thanks, and I hope the gapp thing can be worked out. Okay, what ended up working was ARM 8.1 gapps. NOT arm 64. Not sure why or how. Just FYI. Thanks.
[Nexus 6P Android Development] sufy1000:
I shall be trying this ROM out soon. I have to flash gapps 9.0 arm 64?
[Nexus 6P Android Development] abdullahk6809:
Yes,,,flashed it today ,, Currently using it
[Nexus 6P Android Development] kenetix:
I just tried to flash 9.0 pico package. It said it was the wrong version, and I needed 8.1 gapps. What package did you use?
[Nexus 6P Android Development] kenetix:
9.0 Gapps not working

UPDATE. I did find a way that worked for me. https://xdaforums.com/nexus-6p/development/rom-dot-os-3-0-t3898420/page25

All credit goes to that guy for figuring this out.
[Nexus 6P Android Development] Skull2candy:
Can anyone help me here

I tried fashing the FBE recovery via fastboot and the cmd shows that it's finished flashing but I am not able to boot into recovery instead I stuck in GOOGLE logo
[Nexus 6P Android Development] abdullahk6809:
You are on custom rom(fde) before flashing it?It would be better if you explain your problem in detail.
[Nexus 6P Android Development] Skull2candy:
I don't have any rom installed and my phone is 4core
[Nexus 6P Android Development] Mr_Cyrus:
Can you kindly describe how you enable aggressive sleep?
[Nexus 6P Android Development] sage of six paths:
Check out the battery settings, inside you will find agrressive sleep and standby options.
[Nexus 6P Android Development] Mr_Cyrus:
Forgive me for being pesky, but I would like to know if this how you have setup aggressive battery.

I have enabled aggressive standby and aggressive idle & also toggled the setting to have them enabled when battery saver kicks in.

This okay?
[Nexus 6P Android Development] sage of six paths:
No because the battery saver doesnt work on pie, so turn it off and leave those two options on.
[Nexus 6P Android Development] Mr_Cyrus:
Okay.

Thank you very much. :)
[Nexus 6P Android Development] sage of six paths:
Anytime :)
[Nexus 6P Android Development] kenetix:
How did you get open gapps to work? I have tried a lot of packages ( pico,, nano,etc..), and cant get it to work.
[Nexus 6P Android Development] sage of six paths:
Sorry for the late reply i didnt check the site for a few days. I didnt really do anything special they just worked. Nano open gapps form 18.09.2019. Maybe try to format data and do a clean install.
[JAMin, XDA Neo, S200 ROM Development] yoozco:
hi, i found a solution and reason why opera quits esmertec java on windows 6.1 (tested on cloudyfa and gullum's rom).

if i set my own regional preferences (in my case Polish) then i can't launch operamini, if i set back to default english - opera works fine.

can anybody confirm that?

ps. i know that opera works fine on older version of jbed but there is no smooth scrolling :)
[JAMin, XDA Neo, S200 ROM Development] dioxda2:
TRY "JAVA MANAGER" http://v-dog.net/XDA/Esmertec JAVA Manager.cab, to see if you can run that smoothly without "sudden quit!"
[JAMin, XDA Neo, S200 ROM Development] TurasPl:
On Cloudyfa 19701 with Esmertec and Polish regional settings ...

Try not to install Polish versions. I have English Opera Mini and works like a charm. Got problems with Google Mail - couldn't even install - untill I decided not to use Polish version. English version wokrs with no problem.

Maciek
[ASUS ROG Phone II Questions & Answers] oryydin:
Can anyone confirm if the screen uses pentile subpixels or PWM dimming? None of the common reviewers mention the presence or absence of either unfortunately.
[ASUS ROG Phone II Questions & Answers] willhemmens:
Like almost all AMOLED panels (afaik) this will be a pentile panel and will most likely use PWM dimming, manufactures usually make a point of stating if they're using DC dimming and I don't have one to check yet.
[Google Pixel 2 XL Questions & Answers] Nightf0x_007:
this happens to me for the 2nd time, i clean reflashed factory image of android 10, then installed a kernel, twrp and magisk, after installing some magisk mods device bootloops in restarts directing me to twrp recovery, i deleted them using file manager but still the device bootloops and they are not the reason behind the bootloop as they we working before,

something to add is that device selinux is set to permissive and not enforcing, idk if this is the case or no
[Google Pixel 2 XL Questions & Answers] wolfeyes30:
Fastboot image first then boot the OS. Get back to the bootloader then fastboot twrp image. Flash the twrp installer zip when booted in the twrp image. Reboot to recovery and then flash kernel and magisk last.
[Google Pixel 2 XL Questions & Answers] Nightf0x_007:
not working still bootloops

something causing the device to bootloop even enabling core mode only in twrp doesnt work, im fed up i reclean flashed sotfware dozen times, when there was no twrp installed the device bootloops then returns you to stock reocvery or twrp, once i didnt flashed twrp yet so in factory recovery the error was that system cant read data partiton or something like that

latest canary build bootloops after installing any modules and if i installed twrp

im using the version before the latest i made the same behaviour after installing some modules

bootlogs attached in here
[Google Pixel 2 XL Questions & Answers] wgrant:
I don't know how to read android logs but my IT experience is telling me the OS is having problems with the hardware for some reason, lots of errors at the end freaking out about sensors and hardware.

I would suggest a clean start with just the OS to see if it bootloops before adding twrp or magisk. Use Deuces script to flash the factory image to both slots and get everything setup. Run that way for a day then move on to adding one or the other and gradually add things to see where the loops start. Also, be careful with modules since they aren't all updated for 10 yet.
[Google Pixel 2 XL Questions & Answers] Nightf0x_007:
this happens after installing modules they was working before, before all this happens

how to flash factory image to both slots using deuces
[Google Pixel 2 XL Questions & Answers] wgrant:
https://xdaforums.com/pixel-2-xl/de...tloop-recovery-flashing-t3704761/post74507988

Download the script, put it in your adb tools folder with the factory image then run it. It'll launch and proceed through the steps to flash the image. If you boot to bootloader before running the script you can hit enter when it says it can't find any adb devices, that's normal because you'll already be in fastboot which it checks next.

Also, I saw in your other thread that you're using the Canary builds. I'm using magisk 19.3 without issue and twrp 3.3.0 with the system mount error that comes up but it still flashes what ask it to. For twrp I flashes the img file to the recovery partition and it's working just fine, no need to use the zip.
[Google Pixel 2 XL Questions & Answers] Nightf0x_007:
yes i know all this and i used the script, but im asking about flashing to both slots should i do something in here or it is automatically done by the script
[Google Pixel 2 XL Questions & Answers] wgrant:
The script flashes to both slots instead of just the active slot like the flash-all file Google offers. They're essentially the same thing but Deuces automates a lot of the commands you would need to know and instead let's you reply yes or no to questions. I find it super handy and saves me time.
[Google Pixel 2 XL Questions & Answers] Nightf0x_007:
the script only flashes slot B in here is that normal ?
[Google Pixel 2 XL Questions & Answers] wgrant:
No, it's not. The script should flash your active slot then switch to flash the other. You could manually flash using the flash-all that Google gives and manually switch to the other slot. I believe the command is set active slot - a or set active slot - b then run the script while in each one. You may have to Google that command since I don't use it.
[Google Pixel 2 XL Questions & Answers] Nightf0x_007:
Yes i did this but then got error device is corrupted and wont boot, so i flashed the flash all file in the factory image it flashed slot b and flashed one thing only (system) in slot a, so thats right?

Or should i manually switch between slots and run the flash all ?
[Google Pixel 2 XL Questions & Answers] wgrant:
It seems like you're misunderstanding. The flash-all file that Google provides will only flash to one slot. So if you wanted to flash to both you have to switch slots manually then run it again. Deuces script does both slots, it won't do only one of them because of the way it is written. Since you can get into fastboot I would just use what comes from Google and flash it then switch and flash again. This should put you in a clean OS on both slots so no matter where you boot from its good. Once that is taken care of you can move on to other twrp and magisk.

All of this sounds like you have old stuff on one slot and keep ending up on there. The A/B structure of the pixel phones is supposed to allow see less updating of the OS so when an update is installed switches you to the new slot for active booting and then the next update it switches to the other slot so on and so on.
[Google Pixel 2 XL Questions & Answers] Nightf0x_007:
this is what i did, i flashed factory image in slot b then manually switched to slot a as active and reflashed image without -w, when booting os, phone shows corrupted device message and wont boot, reset active to b slot phone boots

i will try something now, will flash .019 in slot a then adb sideload .20 ota afaik it should install in opposite slot (b), and will see what happens
[Google Pixel 2 XL Questions & Answers] wgrant:
You data partition may be corrupt and needs to be wiped.
[Google Pixel 2 XL Questions & Answers] Nightf0x_007:
i flashed .19 to slot b with wipe userdata, then boot twrp sideloaded ota .20, then erased all data factory reset, setuping device now will see what happens
[Google Pixel 2 XL Questions & Answers] leqacy:
Did you manage to get it to work?
[Google Pixel 2 XL Questions & Answers] Nightf0x_007:
Yes, i flashed .19 image then sideloaded .20 ota, tell now things good returning my data step by step

But after i did this intalling twrp after that when i boot os then reboot phone bootloops so i didnt install twrp after that (reflashed .19 ........)
[Samsung Galaxy Note 10+ Accessories] mzsquared:
Pretty cool actually, I think it keeps the phone well protected in the pocket and it has some features I like: turns on/off the display and it provides steadier grip when taking pics and vids. They made it thinner than Note 9 or S10 S-View covers and no fingerprint mess on its matte finish. I am glad I turned my $50 bonus into something useful.

Here's a quick vid(zip)
[Samsung Galaxy Note 10+ Accessories] edwardob:
not as good as they used to make.....cant turn it into a stand
[Samsung Galaxy Note 10+ Accessories] mzsquared:
True, but an extra layer of plastic for the kickstand would make it much bulkier. I like it as is, giving the phone a nice, slim appearance and there are always some objects around to prop up the phone against, instead of having built-in kickstand. I used to buy some of those cases in the past and never had much use for the kickstand.
[Samsung Galaxy Note 10+ Accessories] kat3k:
I wish I had half the money back from all the cases I've bought over the years, and never really used - kickstands included.
[Samsung Galaxy Note 10 Themes, Apps, and Mods] clockedtouch:
Samsung has rolled out it's version of the camera ring notification. Can be found in the galaxy store or through Samsung good lock app. From my initial testing the notification work and offer color mods and choosing what applications use the notification.
[Samsung Galaxy Note 10 Themes, Apps, and Mods] bonerp:
Tried it last week can't get it to work. Tried a few other similar apps and they didn't either. Ring flashes on Face unlock so not sure whats not working correctly. Does aod needs to be on? I don't really want this on.
[Samsung Galaxy Note 10 Themes, Apps, and Mods] kshitij84:
Works fine , you have to go and specifically select the apps you want the notification for , just activating it won't help
[Samsung Galaxy Note 10 Themes, Apps, and Mods] ox_eye:
I cant find it in GalaxyStore. What is the exact name of this App?
[Samsung Galaxy Note 10 Themes, Apps, and Mods] bonerp:
Edgelighting +

I can't get it to work and prefer AODnotify
[Samsung Galaxy Note 10 Themes, Apps, and Mods] nycinsane01:
Need good lock app then edge laughing plus app works great with aod too
[LG V20 Questions & Answers] reptarien:
Hi. I'm just gonna say this first: I didn't know entirely what I was doing when beginning this operation. I was just trying to do something fun and new, and it didn't pan out. I fully acknowledge that I am an idiot.

Now, the story. I was attempting to root my LGV20 with this guide: https://xdaforums.com/v20/how-to/root-h910-v10m-t3664500 .

I have read over this thread more times than countable and thought I was doing everything correctly. I got to the "STEP3.BAT" portion of the guide and long story short, my phone crashed during it and somehow got foobarred.

It *kinda* works (as in it will boot for around a minute) and then blue/black screen into a reboot.

Is there any way I can save this phone? Hard resets, going into software, more dumb computer stuff, anything. I don't *need* to get this phone working again but it would be really preferable.

Simultaneously I fully accept the responsibility in failing the operations. I know that somewhere I must have messed up. If no-one wants/ can help me, tell me so. Just means new phone time.

If any more detail on what happened is needed, tell me.
[LG V20 Questions & Answers] MEMO#22:
First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model

and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic

Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.

Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.

I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic
[LG V20 Questions & Answers] reptarien:
Thanks so much. Freaked out over this for a good bit. Came back, did what you said and we're back at that step fully working. Life saver.

Now my first guess as to why step3 failed is that i didn't have the latest version of TWRP. How can I set that up?
[LG V20 Questions & Answers] MEMO#22:
Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img

What i did was downloaded a later version

(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again
[LG V20 Questions & Answers] reptarien:
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.