yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S22 Plus] jagan2:
Download now from Google Play Store! And if you like, please leave a rating. :)

This is the original battery indicator around punch hole cameras, Energy Ring.

With the latest update, Energy Ring can glow up when any App/System accesses camera / microphone / GPS, this is courtesy of Access Dots App integration.

Energy Ring + Access Dots = Access Rings!

Energy Ring is custom calibrated for every new device released with a punch-hole camera. If you have a device with punch hole camera, reach out via email to get support added!

Similar App for other Devices:

Energy Bar

View attachment 5555035 Adds a configurable Energy Ring around the camera lens indicating current Battery level. Dive into the various configuration options, not only you can quickly glance and get the battery info but, Energy Ring adds an accent to your phone's camera lens.

Got a full charge? The Ring will be a 360 degree wrap around the front camera lens.

Battery depleting? So will the arc of Energy Ring.

Out of the box features:-

✓ Energy Ring can be configured from a width of 1 pixel to a donut thick ring

✓ Energy Ring puts almost 0% load on CPU, as it wakes up only to reflect any change in battery level

✓ Energy Ring's direction can be configured as clockwise/bidirectional/anti-clockwise

✓ Energy Ring can hide on fullscreen content (apps, videos, images, games etc)

✓ Energy Ring can be configured to change colors automatically depending on the live battery level

✓ Energy Ring could have a mono color/multiple color segments/gradient (pro)

✓ You can literally assign any color in the world for your favorite configuration

✓ Energy Ring has a number of cool animations whenever a power source is plugged into your device

The App in action on a Galaxy Z Flip, Fold 3, Pixel 5a: (Looking for photos of your device, please attach them!)

View attachment 5555037

All that is cool! But what about Energy Ring consuming Battery?!

This is one of the most exciting question for me to answer. Energy Ring more than anything understands that you need to utilize your battery efficiently (after all, that's why you installed the App, right? ;) .) Energy Ring sits on the screen silently putting almost 0% load on CPU, if battery level changes, Android wakes up Energy Ring. Once awake, Energy Ring quickly updates itself and goes back to sleep. And to be that extra efficient, the Ring goes on deep sleep when you turn off the screen, meaning it doesn't even read changes in battery level when the screen is off.

Accessibility Service Requirement:

Android requires Energy Ring to run as an Accessibility Service, to be able to display on Lock Screen. It does not read/monitor any data, whatsoever. This is especially useful for people who have disability to read numbers and work better with visual data.

Download now from Google Play Store! And if you like, please leave a rating. :)
[Samsung Galaxy S22 Plus] Jay_B:
Is there any way to keep the ring on till the notification are read and not a fixed time?
[Magisk] geekborg:
Hi,

I just discovered Shamiko which apparently is the successor of Riru-momohider and that it works in Zigysk mode.

I installed it on Magisk 24.1 and I activated the zigysk mode but I don't know how to add applications to hide.

On Riru-momohider it was enough to add them in the magiskhide list but it doesn't work anymore.

View attachment 5555053
[Magisk] Lord Sithek:
Shamiko uses the app list from the Enforce DenyList, but to activate Shamiko, you have to disable Enforce DenyList itself. So: 1) Flash Shamiko on reboot, 2) enable Zygisk, enable Enforce DenyList and configure it - mark all the apps you want to hide root from, 3) DISABLE Enforce DenyList and reboot. Now on, Shamiko takes over the job
[Magisk] geekborg:
This is what i did but Shamiko does not gives me the list of hidden apps in its description text

Here is what I expected to get :

View attachment 5555645

I added 4 apps to the list but I got :

View attachment 5555647
[Magisk] Lord Sithek:
In the latest Shamiko versions there is no indication about number of the blacklisted processes. It was removed for some reasons unknown to me, but from the second screenshot it is obvious that Shamiko is working fine for you.

By the way, if you want a user to be notified about your reply, you have to use "Reply" button directly in the previous message. I wasn't notified and almost forgot about your question ;)
[Magisk] locolyric:
shamiko method not working on the latest banking app since i accidentally update that app last night.
[Magisk] Lord Sithek:
Shamiko isn't a universal solution for everything. It hides Zygisk traces, but there are many other things that a bank app can look for, like TWRP files, app with root access installed, USB debugging enabled, etc.
[Magisk] locolyric:
i found that latest app can be simply block by using v23 magisk hide ....but deny list can't stop it...
[Magisk] brenosnt:
use Shamiko along with Universal SafetyNet Fix and be happy
[Magisk] locolyric:
not work for that app.

currently only v23 magisk hide is working.
[Magisk] kenshinta:
Sir jumping in as there isn't much reference to shamiko, but after that initial setup, what's the correct way to add new items to the deny list?

IE do I toggle magisks "enable denylist", do I reboot somewhere in between or...?
[Magisk] Lord Sithek:
Reboot always welcome if you add new app to the list (although Im not sure if necessary). So just add an app to Configure DenyList and then reboot
[Magisk] Duvel999:
I want to update shamiko in magisk stable, but it askes for canary?

Is this right?
[Magisk] ProtoAES256:
Newest shamiko (1.1) requires Magisk 27003+, which is canary only as of writing. I recommend using that too as that fixes some problems like the unable to find preinit dir error, and fixed the potential leak of unique identifier.
[Samsung Galaxy S22 Ultra] Osushi:
Question!

How do you charge your phone? What type of charging do you have selected?

-fast charging

-super fast charging.

I use a 25W charger and I have super fast chargers selected. I try to charge the phone in the range from 30% to 85%. I also have the battery protection option selected
[Samsung Galaxy S22 Ultra] larryk:
I always use wireless charging, and I place it on the charger when I go to bed, and pick it up when I get up, as I have for the previous S20 Ultra, and before that the S10+, and the S5 before that. I have never had a battery problem, don't baby it, use it!
[Samsung Galaxy S22 Ultra] joancolmenares:
I use the 45W (SUPER FAST CHARGING 2.0) and of course enable all options for battery health.
[Samsung Galaxy S22 Ultra] sactownbwoy:
I do the same as you. Have wireless charger on my bedside table and one in my car. That's all I use and don't worry about battery dying on me.
[Samsung Galaxy S22 Ultra] Deiota77:
I bought an Anker 45W charger, and I have a question.

On my first days, should I use it or use a normal charger? Use health protection or not?

After those few days, I have a meross Smart Power strip , WIFI, that I can schedule each plug individually, even the USB ports. I usually put 2 hours charging for my actual phone and 1 hour for my Galaxy Watch 4. Is this ok? Can I keep the 2 hours for the s22 ultra or reduce the time, since I'll use a 45w?

Thanks for the advice!
[Samsung Galaxy S22 Ultra] pcriz:
I plug it into a 25 watt charger at night. Unplug it when I wake up. Charge as needed throughout the day.
[Samsung Galaxy S22 Ultra] Craig_D:
Currently on my 3 year old Note 9, awaiting delivery of my S22U, as with previous phones, I disable fast charging, if the phone has the feature, as it generally isn't good for battery life expectancy. I always plan to keep my phone longer than the one or two years many people do, so battery health/life is important to me. I have a timer-socket adapter, like this, I use for through-the-night charging, whereby, I set a timer duration, depending on the battery level at bedtime. I'll perhaps set the timer to be on and charging the phone between 4 & 5:30am. Apart from the first few charging cycles of a new phone, I don't like to fully charge/discharge the phone often, only occasionally. I top the charge up during the day, if need be, in the car etc but I never use wireless charging even though my car has the ability to. I'll probably start using the wireless charging with my S22U though, as not using it probably doesn't lengthen the expectancy by much. I appreciate battery charging technology has improved greatly recently, I'm just stuck in my ways I guess.
[Samsung Galaxy S22 Ultra] ‬1‬:
Everybody is talking about charging the phone between 20% and 80% but what about the result? What would the capacity of the phone be in the end of three years of usage if someone charges his phone in that range? and another thing, when you charge your phone, from 20% to 80%, you charge your phone more often than compared to 0-100%. It's said that If you charge your phone more often it's battery will wear off faster, in the other hand you will charge it less with 0-100 but this time your battery will wear of faster because of the known reasons. I'm a bit confused here. Is there any data compares the result of the both cycles after some time?
[Samsung Galaxy S22 Ultra] Chavannigans:
Baseus 65W GAN charging brick. Bixby Routines set to disable super fast charging at night and enable Battery Protection. I have another automation that reverses that before my wake up alwarm so it's still full when I wake up but stressed the battery less.
[G1 General] hkfriends:
I know it is in US telephone format (dailing or in contact)

but how can I change to other country format?

thanks
[G1 General] demontefixo:
Since this thing syncs to google, you may have to set it there... so far for other than US numbers I enter the country code +886, +XX, etc. followed by a space and whatever format I want... seems to 'stick'...most of the time. ;)

--M
[OnePlus Nord N100 Guides, News, & Discussion] cell2011:
11.0.4 be82cb android 11 n100 TMobile? I just got it. Seems to be better than previous update with the lag. It's the 2-01-22 security update
[OnePlus 7 Pro Questions & Answers] NitayMa'ah:
Hello, I had my OP7P rooted on android 11, but after updating to 11.0.6.1.GM21AA, I just couldn't get root to work.

I downloaded the OxygenOS 11.0.6.1.GM21AA from oneplus.com, extracted the boot.img, downloaded the new (supposedly with Android 11 support) TWRP (twrp-3.6.0_11-0-guacamole.img), booted to the TWRP, and installed root using the magisk APK, when I booted the phone had "Android Intellegnce stopped working" all sort of apps stopped working as well and some also crashed when I tried to open them, I flashed the original boot image and after some research I saw that using Magisk Canary build might help, so I tried with it too and same result.

I tried installing root using Magisk.apk, I tried patching a boot image using Magisk (both versions) but to no avail.

Some notes:

-Using the Canary build actually rooted my phone unlike the normal Magisk, but with problems still.

-When trying to use TWRP's "Flash Current TWRP" option, it overwrite my boot image and when trying to boot to fastboot or system it booted to recovery instead.

I will be glad for any help because having an unrooted device sucks.

Thanks in advance and sorry for any grammar mistakes (English is not my first language)
[OnePlus 7 Pro Questions & Answers] wugga3:
May be the first thing I'd think of trying it to disable any/all Magisk module installed.

Then, with the full OTA ROM stored in the main storage directory of your device... Basically a dirty Flash using the same OOS version you are using now and that should save the wipe/reset...

OTA Flash that and do not reboot and in Magisk manager check to see if manager is able to install Magisk as in install after OTA (?). That should work and then reboot device then verify. Don't forget to re-enable and Magisk modules...

Hope that can and will point you into the right direction.

I've not bothered with TWRP since I installed it then the next OTA went back to stock recovery. So, might be worth skipping TWRP for root as is not required so far as I can tell ... But I also have a Windows computer set up to flash via adb command alternatively.

Edit:. Think I forgot to say that the OTA update changed my TWRP back to stock recovery... But that's easy enough it change if desired
[OnePlus 7 Pro Questions & Answers] NitayMa'ah:
Hello, thanks for the reply, I wanna get a few things straight before doing anything that have the potential to brick my phone.

1. My phone rn isn't rooted, so I cant uninstall or disable Magisk modules, I CAN root my device but it is very unstable and im not sure doing it is a good idea, maybe there's another way to disable them?

2. What do you mean by dirty flash? Using the device update section and selecting the official OOS version I downloaded from OnePlus.com?
[OnePlus 7 Pro Questions & Answers] wugga3:
1) may be forget about root for now as that's probably not the priority at this time. Getting a stable operating system is the priority. And skip TWRP (don't see the point of if being needed at this step either).

2) my best guess is that I've used oxygen updater from the play store to download the full update (not incremental update) that exactly matches the one you have installed now - or search here and find the match to download or used the OnePlus cite to get the file. Then once that is downloaded to your device - go to settings/system/system updates/local update and install and reboot. That's the dirty Flash as in don't wipe/reset your device either before/after the installation. I'm hoping that this method will clean up both the recovery and boot images to stock and hopefully restore stability to your device without the wipe/reset.

Hope that helps and restore the device stability without TWRP nor root.
[OnePlus 7 Pro Questions & Answers] NitayMa'ah:
Hi wugga3, thanks again for your time, unfortunately a stable device is not my problem, I have managed to make a stable boot image by downloading the OOS version from the Oneplus website and flashing the boot image after attempting to root my device unsuccessfully.

My problem right now is that my device isn't rooted and I can't manage to root it using the methods I mentioned above, I currently have an unrooted stable OOS version 11.0.6.1.GM21AA.
[OnePlus 7 Pro Questions & Answers] hammered58:
How about installing just the magisk APK then taking the exctracted boot.img patching it in magisk APK, then disabling all security , take the patched boot.img and flash it in fast boot ( fastboot flash boot boot.img) reboot to system .
[OnePlus 7 Pro Questions & Answers] NitayMa'ah:
Ill try it now thank you
[OnePlus 7 Pro Questions & Answers] Littlemether:
Here's a image file you can flash in fastboot. It's

Here's an Orangefox prerooted OxygenOS 11 boot.img that works on 11 and 12. Just boot to fastboot, connect to a PC open a command prompt in the same directory and type..

fastboot flash boot boot-v9-root24.img...

Also it's easier to just flash both slots by this commands..

Fastboot flash boot_a boot-v9-root24.img and then fastboot flash boot_b boot-v9-root24.img...

I dual boot with this version of twrp and here's a solid boot img. You can flash it also in recovery or with "partition manager off play store. Check it out.
[OnePlus 7 Pro Questions & Answers] NitayMa'ah:
Fixed!

Thanks so much for the suggestions, which I might didn't fully consider in a rush...

The solution was to root my phone, reboot it all shaky and try to disable all Magisk modules (took me 2 tries because of the crashes and stuff), then flash again the original boot image, rebooting, creating a rooted boot.img using Magisk and flashing it.
[OnePlus 7 Pro Questions & Answers] NitayMa'ah:
First of all thanks for the help but I ended up fixing it in another way.

Second of all, not really related but do you know if I can use this recovery on OP7Pro A12 custom Rom? (and flash it)
[General Topics] Viva La Android R.I.P.:
Your issue sounds exactly like a driver issue -- and that is very common with Allwinner devices. In the above instructions I've included a guide for updating the USB drivers. Just because PhoenixSuite initially recognized your device does not mean it will also be recognized when it boots to download mode and begins the flash. It sounds like yours is first recognized fine and then when the flash begins, sync between the tablet and the flashing tool is lost. Follow my update USB drivers section above and see if that fixes your issue. Remember, your tablet needs to remain in download mode and connected to your PC when you follow the update USB drivers steps.
[General Topics] Shady8550:
so i have come to the conclusion that i might have left usb debugging off i have tried everything i can think off to get my device recognized by phoenix suit is there anything i can do
[General Topics] Viva La Android R.I.P.:
You are not alone in your difficulties. Almost every member who has used PhoenixSuit has encountered device recognition issues. I have a section in the instructions above titled UPDATING USB DEVICE DRIVERS which is specifically for troubleshooting device recognition issues. Follow the steps exactly and you should be okay.

To clarify, did PhoenixSuit recognize your tablet during the initial syncing phase, but did not recognize it when attempting to flash the firmware? Also, did you install the 15-Second ADB utility from the rooting thread?

In fact, after reading @13lack13ox's tip over in the other thread, I'm inclined to agree. Try the PhoenixUSBPro_v4.0.0 tool. I'll get you a link to the utility.

File on MEGA

mega.nz

Here is a resource guide on using the PhoenixUSBPro tool. https://androidmtk.com/flash-stock-rom-using-phoenix-usb-pro
[General Topics] Shady8550:
no it hasnt recognized it what so ever and ive gone over those instructions 3 times thanks for the link
[General Topics] Viva La Android R.I.P.:
You definitely need to use PhoenixUSBPro if those instructions didn't work. With it, you don't need ADB Debugging to be enabled, nor do you need to manually.configure drivers. I plan on revising this guide later today with inclusion of PhoenixUSBPro v4.0.0, replacing PhoenixSuit.
[General Topics] comm-ents:
After trying all the software in Windows and in Linux, I
[General Topics] comm-ents:
After trying the various tools in Windows and Linux I have determined that there is no way to actually flash the firmware to the tablet I have. I was able to unlock the bootloader so it is rooted, but flashing just doesn't work. I don't know if all the tablets are able to go into recovery mode, but I can by holding the volume up/down buttons and power until it boots recovery. I tried to flash from sdcard and adb and failed in recovery too.

After all testing the only thing I noticed is that it may be a different version than the v1 and v2 that are pictured so I will just set it aside for awhile.

If anyone wants to try the Linux based LiveSuit version, I could probably set it up on a flash drive and image it .
[General Topics] Viva La Android R.I.P.:
Okay, since you can confirm ADB & Fastboot working properly, you can use fastboot mode to restore your device to working order. From this link, you need to download two images: super.img and boot_a.img. https://mega.nz/folder/cVh0SbgZ#ZJe6bC-jjamKsmUF3V44hw

Save both files in your ADB/Fastboot directory on your PC. Put your tablet in fastboot mode, connect to your PC with a data sync cable, and open a command window. After executing the fastboot devices command to confirm proper connectivity, enter these commands:

fastboot flash boot_a boot_a.img
fastboot flash super super.img
fastboot erase UDISK
fastboot reboot

Note: super.img is a large raw image. As such, fastboot will automatically sparse the image and flash it in a series of incremental segments. This will take a few minutes but you will see the progress in the command window. Good luck. This should get you booted up. Note that the erase UDISK command will erase all data saved on your device. The boot_a.img file has already been patched with Magisk, so you should be rooted after flashing these images and booting up.
[General Topics] Viva La Android R.I.P.:
It sounds as though you correctly extracted the v9 firmware image. The result is a plethora of .fex files and a config (.cfg) file. Ok once you extract the firmware image using imgRepacler for Windows, simply rename the .fex files to an .img extension, just as you done with the boot.fex file. The .fex files are nothing more than a particular type of sparse image. These can readily be coinverted to sparse .img files merely by renaming the extension. In the extracted firmware, you will see a file called sys_partition.fex. Read this file using Windows Notepad and it will give you every partition name along with the corresponding .fex image; e.g. /bootloader_a = boot-resources.fex, /super = super.fex, etc. This gives you the correct partition label when flashing with fastboot.

For clarify, here is an example index from the sys_partition.fex file:

...........................>boot
[partition]
name = boot_a
size = 131072
downloadfile = boot.fex
user_type = 0x8000

Note that "name" is the exact label name of the device partition, and "downloadfile" refers to the corresponding .fex image to be flashed to said partition.

Regarding UDISK, as you've probably learned, this is simply your /userdata partition. Erasing UDISK when flashing with fastboot is not necessarily required, but it will help ensure a good clean flash and prevent potential issues from corrupt or mismatched data. If your tablet booted okay after using fastboot, and you're not experiencing apps crashing or force closing, you're fine.
[General Topics] Viva La Android R.I.P.:
Update: I am diligently working on the TWRP port for the Sceptre 8. Android 11 support for TWRP (primary, the dynamic partitioning scheme) is an absolute nightmare. Because A/B devices do not utilize an actual /recovery partition, TWRP must be installed to /boot. Although my TWRP port is booting and the touch GUI is functional, I am trying to iron out some mounting issues and decryption of some key partitions. I am hoping to get some one-on-one aide from a TeamWin dev and maintainer later this week. Once I iron out these issues, I'll be posting the TWRP build.
[General Topics] Viva La Android R.I.P.:
Exactly. I need to take the time to write a flash-all batch file for fastboot installations. A flash-all batch script executes the fastboot commands and acts as an auto installer. Takes the work out of executing back-to-back fastboot commands. Your reasoning is correct.
[General Topics] pyrohydrosmok:
Hmm. So I had to do this all because I was in the same boat. Device gets to unlock screen. Hangs for a moment and doesn't let me unlock. Then boot loops. Trying to flash Boot_a and Super again did nothing.
[General Topics] Viva La Android R.I.P.:
I'll need some more info. What exactly did you perform that caused the hang up at the lock screen?
[General Topics] pyrohydrosmok:
Edited build.prop. I was overconfident and didn't back it up. Lol. First time for everything.
[General Topics] Viva La Android R.I.P.:
When you flash the super.img and boot_a.img, be sure you also enter the commands

fastboot erase userdata
fastboot erase UDISK

This will wipe all saved data from your device, but is often necessary when restoring dynamic partitions.
[General Topics] deceit:
The v9 link is dead, does anyone have another link?
[General Topics] mdtryme:
since i use linux mint cinnamon should i assume i dont need etcher or the live usb ? cant i do the same job without doubling up on the obvious if not let me know ok. thank you
[General Topics] mdtryme:
i just used it Use the mega app
[General Topics] Viva La Android R.I.P.:
If you already have a preferred Linux distro, you don't need the FWUL.
[General Topics] Viva La Android R.I.P.:
You don't need dual boot with WSL2. You can run a full Linux distro within the Windows OS. In other words, Windows now includes fully operational Linux. I realize you prefer Linux over Windows, but this is a Windows-based guide. Linux installations can't be discussed in this thread, but instead must be discussed in the general info & discussion thread. Those are the mod's rules, not mine.