Poweroff Alarm form Xiaomi MIDO - LineageOS Questions & Answers

Sorry for me being a "forever newbe",
my question is: will someone ever develop the "scheduled power on" feature on Lineage for Xiaomi MIDO? (I'm interest for this feature inbuild into the Alarm Clock)
I know it needs some part of kernel remaining on even if the smartphone is off (of course), but this feature is useful when phone is in charge so it doesn't matter. I know also that some other Lineage release for other Xiaomi Phone models have it!
If not (it seems no developer is interested in it) does it exist some custom rom which can do it? I really don't want to return to MIUI (it's too "toy like", and the last release caused me a lack of performances even after an hardware reset), but I would like to use the poweroff alarm! Why it is such a problem to have it?!
Thanks!!

How about a workaround? You can define a duration for do not disturb. Should make no difference, if you are charging anyway.

Related

[Q] optical trackball problem - any way to disable the sensor?

After some water exposal, bottom hardware buttons (along with optical trackball) refused to work.
I have fixed them with some precise inside cleaning, but the optical function (not the button himself) continues malfunctioning, which is not a big deal for me, but..
The exact problem: i spotted in dark environment, that the sensor inside continuously glimmers in all modes - scren-off, scren-on (without puting finger over him), etc.. In return, my battery drains extra aprox. 10-12 mA!
I have observed, that in healthy device, sessor glimms only when interacting with him..
Is there a chance to disable this sensor to avoid this? I hope in software manner
I don't think there is anything out there that will disable the optical pad. You could give HTC a call or your carrier and see what they say.
There is this thread on the forums about turning off the backlights.
Should work for trackball as well? Probably. Something about LED Hack on the first or second page. Seems to be something on the 3rd page as well.
Go have a read over here (I just skimmed. its 2am lol) http://forum.xda-developers.com/showthread.php?t=704977
@formformer
If you tell me your kernel version I will try to build a kernel without trackpad support!?
@Meaple 's post was sadly adequate and rips best hope in me ;( ..
@eden2812 I have using 2 led hacks from previous attempts to minimize energy consumption & eye comfort, and they shurely don't do the "trackpad sensor shutting" job..
@AndroidJaspie
it's so damn cool to offer this kind of experience. salute!
i have likely using latest Ginger Villain's compilation, but any recent rom-kernel set, with weak appetite fits my best.
i will be very patient to hear from you..
my current setup is:
OK I built a new kernel from the cyanogenmod sources now without trackball support. I tested it with GingerVillain 1.4 and it worked.
please make a backup and then give the update.zip a try.
Tell me if the new kernel solved your problem or not.
Jasper
Yes Jasper, obviously the sensor is shutted (no glimmering observes) and the xtra drain is all gone now!! I'm so pleased.
But i have found, that the bottom buttons (including the button under the optical trackpad) not waking the phone any more. Is this issue related?
And another, not so important question: Would be this kernel compliant with other Gingerbread releases? or.. could you give me some hint, if is possible to transform your "surgery" into a some kind of a patch, that will give me opportunity to enjoy any feature kernel/roms?
Again, BIG 10x for your respond in this custom problem so far! You make my life happier
karel
No problem i like it to work with things like that. So it's a good chance to improve my knowledge about linux and help other people at the same time.
Are you talking about the all buttons or only about the button around the optical sensor?
If you are talking about the one around the sensor then it's normal that it won't wake up the phone any more. But the others(home, menu, back and search) should work like before.
This kernel works only with cyanogenmod and GingerVillain. On other rom's like Oxygen it doesn't work. But you i can compile you the kernel you want.
At the moment it's only possible to disable the trackball only by editing the kernel configuration. But i will try to get it working without changing the kernel so that you can use every kernel you want.
Jasper
i told so, about the relation of shutted sensor and not working buton.., but yes, others buttons also not working in lockscreen-off mode, where they should or at least worked before. (volume butts still works for wakening..)
ps. a have barely no linux skills, but its interesting for me either!
and if editing & compiling is not so high level task, im going to try first steps right now!
Any way, disabling track sensor without editing kernel settings sounds like a dream..
k
hi, my fried
could you tell me, where in the config I can find the exact setting and how to change it?
hi
if you got the kernel source you can make menuconfig to configure the new kernel. To disable the trackball go to "Device Drivers" --> "Input device support" --> "Opticaljoystick". To disable the joystick press "n" to enable it press "y"
Don't know how to comile your own kernel?
here is a useful links that helped me, too:
-[HOW-TO] Build your own kernel package from source
huh.. 10x 4 the guides, they light me enough to get started week ago, but i get stuck just in the beginning (problems with MBR or something..). and at this moment i have absolute lack of time to deal with this interesting stuff. However.. can i have one more last ask from you: to compile for me an updated kernel.. (they says he has the ability to record 2way call conversations..)
Using the Ginger Villain rom, suppose with this richardtrip kernel. Guess CM will worx too..
Thanks anyway!
ok
a bit late but here it is
a new kernel version 2.6.37.2 from the richardtrip-sources.
kernel features:
-disabled trackball
I don't know anything about "Two-way call recording kernel support" but i will try to find out as much as posible to configure a kernel with it.
jasper
Hi AndroidJaspie, i've the same problem with the optical trackball of my desire. I use the miui rom with the kernel 2.6.37.6-cyanogenmod-g8913be8. Can i use the kernel in your last post? thx bye
Please use the Q&A Forum for questions Thanks
Moving to Q&A

Question Any Custom ROM with AOD, dt2w and pocket detection working properly?

Hey! So, I've tried some AOSP ROMs and I encountered with the same problem in all of them. AOD, dt2w and pocket detection are BATTERY KILLERS. Specially AOD, because, when it's activated, the device doesn't enter into deep sleep.
Don't get me wrong, they work as they should, maybe pocket detection with better results in some ROMs than other.
You can easily say "Turn them off" and yeah, I disabled them and the battery drain is almost nothing, no matter what ROM I'm into.
But, I really like having AOD, enjoy my AMOLED panel and squeeze as much as I can, but not in behalf of HUGE battery drain.
And it sucks, because, in MIUI you can have them enabled and working with less battery draining, but I don't like MIUI like many of us here.
I use BBS app to check the draining, and there is Wakelock named PowerManage.SuspendLockout, that is always active when I have AOD enabled, to consider...
Is it related to Xiaomi not releasing the code or whatever is call, or some hardware issue, or maybe a poor ROM optimization?
Have you find any ROM where these features, specially AOD, are not battery killers?
PS: In every ROM I do a clean install, no backup restore, and almost 0% background apps consumption, so, no, it's no a setting or app related issue...
DotOS 5.12
I tested only 3 AOSP roms (crdroid, havoc and evoX) and they all have this issue. The MIUI didn't. I'm also wondering why that is and I would really like to use AOD. As you said, we have an AMOLED panel and not being able to use it fully kinda sucks no matter if is is just a gimmick. Not sure if it's a kernel issue or a rom issue but it definitely isn't a hardware issue since it's working without flaws on MIUI. Would be great to hear from some rom maintainers about this.
Can someone confirm if it's really working with deep sleep on DotOS? I won't flash it, even if that's true but maybe the maintainer can share the fix with the other roms?
REDOTHELLO said:
DotOS 5.12
Click to expand...
Click to collapse
Have you tried? Does this ROM solve this issue?
I am not using AOD and pocket mode and dt2w is on statusbar DotOS use pixel launcher
REDOTHELLO said:
I am not using AOD and pocket mode and dt2w is on statusbar DotOS use pixel launcher
Click to expand...
Click to collapse
So, how can you recommend the ROM if you are not using what I need? xD
Oxnap said:
So, how can you recommend the ROM if you are not using what I need? xD
Click to expand...
Click to collapse
I tried so many kernels and specific fixes that claims to fix the issue all ended up in failure, like you I love to have AOD but not at the expense of huge battery loss.
Just my opinion. I think there is nothing we can do about the battery. Its a hardware/quality issue. I mean, the battery of poco f3/mi 11x is not good as you see from other giant brand like samsung.
maybe we need a special Kernel for the best result between AOD and Battery
I did a clean flash of my own Lineage rom as something got screwed while trying fixes for AOD, this is a week ago, brightness was being reset to lowest on each wake up.
So, I decided to try AOD just now to see if it works, and it does!
For the first time the cpu goes to deep sleep even though AOD is switched on.
I have built and flashed no less than 80 builds, It pays to do a clean flash once all source code have settled.
This is the Commit that I believe fixed the issue:
alioth: Enable config_powerDecoupleAutoSuspendModeFromDisplay · AliothDevelopment/[email protected]
Contribute to AliothDevelopment/android_device_xiaomi_alioth development by creating an account on GitHub.
github.com
As I said above, I dirty flashed with the commit above and still with AOD on no sleep, so only after a clean flash it is working perfectly, Clean flashing is important if you have flashed many builds with many changes in the Kernel/device trees.
cheers
-GREY said:
Just my opinion. I think there is nothing we can do about the battery. Its a hardware/quality issue. I mean, the battery of poco f3/mi 11x is not good as you see from other giant brand like samsung.
Click to expand...
Click to collapse
You trolling, for sure. My battery is great, better or the same as s21++++
LiNe1771 said:
You trolling, for sure. My battery is great, better or the same as s21++++
Click to expand...
Click to collapse
I could not agree more, I never get less than 10 hours SOD, usually I charge my phone once every 50 hours. Best battery on a Smart phone I have ever had.
Barracuda77777 said:
I did a clean flash of my own Lineage rom as something got screwed while trying fixes for AOD, this is a week ago, brightness was being reset to lowest on each wake up.
So, I decided to try AOD just now to see if it works, and it does!
For the first time the cpu goes to deep sleep even though AOD is switched on.
I have built and flashed no less than 80 builds, It pays to do a clean flash once all source code have settled.
This is the Commit that I believe fixed the issue:
alioth: Enable config_powerDecoupleAutoSuspendModeFromDisplay · AliothDevelopment/[email protected]
Contribute to AliothDevelopment/android_device_xiaomi_alioth development by creating an account on GitHub.
github.com
As I said above, I dirty flashed with the commit above and still with AOD on no sleep, so only after a clean flash it is working perfectly, Clean flashing is important if you have flashed many builds with many changes in the Kernel/device trees.
cheers
Click to expand...
Click to collapse
Cool, did you make your own LOS ROM?
Oxnap said:
Cool, did you make your own LOS ROM?
Click to expand...
Click to collapse
Yes, I have been since i got the phone more than two month ago.
I am an open source advocate/fanatic
Barracuda77777 said:
Yes, I have been since i got the phone more than two month ago.
I am an open source advocate/fanatic
Click to expand...
Click to collapse
Why don't you start your own ROM thread? Maybe I could help you on testing
Oxnap said:
Why don't you start your own ROM thread? Maybe I could help you on testing
Click to expand...
Click to collapse
I am not sure many would like the fact that mine runs on MicroG, I have many of the apps that usually comes with the ROM taken out and replaced with other better open source alternatives.
Gallery, messages, music to name a few
As I am 100% self dependent on my services, I don't rely on anyone else:
I run and maintain. The following services:
1) XMPP secure and fully encrypted chat server (prosody) for family and friends)
2) run my own VPN server when out of the house.
3) run my own email servers since 2008
4) Run my own password manager server (Bitwarden)
5) run Synching server to keep all my Linux servers, Linus PCs and Android Live Backed up.
6) Run my Own Cloud Server ( NextCloud)
7) My own Music personal server I use Gelli (open Source) to listen.
8) my own open source router (pfsense)
9) my own DNS server ( Pihole )
I also build most of the apps I use :-]
Everyone needs differ than others, my sources for building my ROM are here, feel free to download, use or fork.
barracuda777 - Repositories
barracuda777 has 116 repositories available. Follow their code on GitHub.
github.com
Happy building.

Development [ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonadep][FINAL][08/09/2022]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey another day another rom, that's what you might be thinking. but we at stag aim towards elegance. We are learners just like everyone out there, This is small project we have started which helps us learn every single day. Why Stag, you might question, my answer would be why not. After all Harry's patronus was a stag(pun intended). After having a couple of iterations, we still intend to stick to our roots, and keep refining what we have. With Android 12, Stag would still be aiming at an elegantly beautiful close to stock experience, that satisfies just the features and customisations you'd crave for (nothing more, nothing less), at the same time being blazing fast and silky smooth. You'll have to try it to believe it .
~Sic Parvis Magna~
PS: for people wondering what sic parvis magna is, it translates to great endings from small beginnings, Something i picked up while playing a game.
Credits where they are Due:
Google(No explanation needed n this regards)
Lineage(For starting of the custom rom war)
Code:
[SIZE="4"]/*
* 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.
*/[/SIZE]
This Build is a Beta Build, I will not be responsible for any kind of issues that might come up (while flashing)
​
Pristine Build - Non Gapps: Download Here
Gapps Build: Download Here
Bugs
You tell me ​
Features​
Refresh rate switch
Advanced Reboot
Google Style monet made better thanks to ProtonAOSP and kdragon
OOS Style Screen Recorder (Check qs tiles)
Enforcing Build
CTS Passes
Unlimited Google photos backup (Fingerprint spoofed)
CTS Passes sucessfully
Face Unlock
Less Annoying Notifications
Working Gcam Pre Installed
Ambient Display Gestures
Off Screen Getures
OTA Support
And much much more, hope you all love the build.
The build will be updated with bug fixes, but please don't ask ETA.
Hope you like it.
Please follow the instructions properly.
**Make sure your boot loader is unlocked**
Spoiler: If you are on OOS 11 or OOS 11 based ROM
Follow These Instructions if you are on OOS 11 or OOS 11 Based ROM
Download the boot.img from here
Reboot to bootloader
Use the following command to flash boot.img to both slots
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Reboot to recovery
Format Data (Optional if already on Stag)
Select Apply update
Run the following command
Code:
adb sideload romname.zip
Spoiler: If you are on OOS 12 or OOS 12 based ROM
Follow These Instructions if you are on OOS 12 or OOS 12 Based ROM
Download the boot.img, vendor_boot.img, debt.img from here
Reboot to bootloader
Use the following command to flash boot.img to both slots
Code:
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Reboot to recovery
Format Data (Optional if already on Stag)
Select Apply update
Run the following command
Code:
adb sideload romname.zip
If none of the above methods work, please use the following.
Spoiler: If nothing works
Beware this is OOS 12 C.48 based build so it is important that you follow instructions properly and that you are own OOS 12 C.48.
All builds can be found here
The Proper due credits will be updated promptly, A huge thanks to the Lineage team and luk for bring up of OnePlus 9 Pro trees.
A huge huge thanks to everyone who helped me test it, and develop:
@chandu dyavanapelli for helping me with 12 bringup
and
@aswin_a_s forhelping me deal with some huge issues, and stabilizing source (both rom and device)
@Libra420T For having my back testing builds for stag os ever since A11, has been a super huge help.
@YouLop09, @Jhoopes517, @Anonymouze for always being up for testing builds
This release would have been super difficult without your help. Thanks a lot.
I am extremeley sorry if I forgot someone, please dm me and I will promptly add your names.
and currently this build is work in progress.
ROM
Kernel
Device Tree
​I work on this project as a hobby, and the money for the servers completely go out from my pocket.
If you like my work it'd be great if you could: https://buymeacoffee.com/vjspranav
I would really appreciate it.
Thanks and hope you enjoy the build
ROM OS Version: Android 12.1
ROM Kernel: Linux 5.4.x GKI
Based On: AOSP
Version Information
Status: OFFICIAL
Current Build Version: 12.1
Build Release Date: 2022-09-08
Reserved for SS
Changelog - 08/09/2022
Hey everyone, this update took a bit longer. I have been super busy with life. I'll keep changelog this time short and concise.
1. OOS Cam is finally here, everything works.
2. A Resolution changer (in Horns > System), use it for saving battery when needed, It is a work in progress feature and hence fingerprint is unusable when you change resolution.
3. Build is based on August Patch
4. Added volte icon
5. And some stability fixes .
Hope you enjoy this release, this will be the final A12 release for OP9 series, see you in A13
Changelog - 20/07/2022
Hola, We're here quicker then before. This stag build is a simple elegant build that has some beautiful additions. Firstly the build is updated to July Security Patch. Up to date AF.
I'll directly jump on to changelog:
1. Now you have multiple options in alert slider, it's a waste just using alert slider for silent, sound and vibrate. Let's use it for a lot more than that. We call it the Awesome Alert Slider.
2. Added option for higher touch sampling rate.
3. We have an OOS style clear all icon in notifications, it's boring to see clear all text.
4. Now you can flaunt android 12L in your version hehe.
5. We have a screen off fod now, you can use fingerprint when screen is off. You can find the option in Settings > System > Gestures.
6. And many crashes fixed internally )
Changelog - 23/06/2022
Guys this is a small hot fix build that ensures that sensors are fixed. The older update had a bug due to which all sensors stopped working
Changelog - 21/06/2022 - Sensors Broken
Hiya, This time the changelog might turn out pretty long, so yup stay tuned. Before anything else, Yes I realise the time between updates is kinda long, honestly I really try had to get it to you guys much sooner, but this is the best I can do. Another factor that comes in is, every time I add a new feature or fix a bug, I feel like there's something else that can be better, and I go on to fix/work on that, this cycle keeps happening because come on guys, I want to ship out nothing but the absolute best for you guys to use.
And this time with the OOS 12 base, a lot of things broke, and I had to work on fixing things from around up, so without further ado I'll jump right into the changelog. As always, will start with what's bad
Assuming not everyone will read through, please follow the install instructions carefully, as mentioned in OP. else you might end up in brick
So there are two known bugs which I really couldn't fix at this point:
1. Low mic volume in recording apps, calls are perfectly fine (some reported that if you turn on speaker in call once after every reboot, the mic seemingly becomes better)
2. Speaker starts crackling in specific audio (only on max volume) otherwise it's absolutely fine as long as you don't hit the absolulte max.
Ok that aside, now let's get into the good news, the juicy part :
Device Specific:
1. Ok the biggest change, Now the builds are going to be OOS 12 based, partly the reason why there was an even bigger delay, but man o man, the build just flies, you'll forget using any other OS.
2. Biggest challenge was to get the haptics right, the vibrations you feel when you touch your keyboard, or the the haptics when there's a notification, OOS 12 base created a huge mess with them but guess what, you'll not have to worry about them because the haptics are much much better than ever, you'll just fall in love with how your phone vibes (literally hehe).
3. On a few requests, I've decided not to include Gcam in this build, whoever wants are free to install whichever version you want to go with .
4. Verizon sims should finally work, Had multiple tests this time so you should have it working for sure, here's to everyone waiting with a Verizon sim.
5. And everything else that yo love and remember from previous version exactly as they were, if not better
Rom Side:
So here's a lot more magic this time, about time I felt the need of a few essential and good to have feature additions without in the slightest compromising how the usability feels.
1. We now have a working GameSpace dashboard, like for every gaming enthusiasts, finally you can game with the full power without any disturbance of notification.
2. Again for all the gamers out there, we have added some props to allow a game to unlock the maximum FPS possible, for more info:
Spoiler: Click Here
* Free Fire - Spoof Asus ROG Phone 1 will unlock 90 FPS
* COD Mobile - Spoof Xperia 5 || will unlock 120 FPS (only on multiplayer mode)
* PUBG Mobile - Spoof OnePlus 8 Pro will unlock 90 FPS
* Wild Rift - Spoof OnePlus 8 Pro will unlock 120 FPS
* Cyber Hunter - Spoof OnePlus 8 Pro will unlock 90 FPS
* Fortnite - Spoof OnePlus 8 Pro will unlock 90 FPS
3. For apps builds, now we ship a modded Pixel Launcher (credits: source). Gone is the pain of using a half baked custom icons. This is a much more optimised pixel launcher with a lot more goodies (like upto 6x9 grid in launcher)
4. A small aesthetic change, re arranged the layout of qs tiles, gone are the tiles which you rarely used and a rather depreciated wifi/mobile data tile. Now we have separate tiles for mobile data and wifi just like we remember and love from Android 11, and that's what is default.
5. Ohh and on the note of QS tiles, Hasn't it been annoying when you long tap on wifi just to be able to quickly connect but you are having to change the screen, now a small panel pops up as an overlay on the existing screen allowing you to work without leaving whatever you were doing.
6. A proper lock screen charging info, Instead of the boring wrong display, the estimate and wattage have now been fixed, and as multiple people questioned, yes Warp Charging does work .
7. And a highly requested feature (and I can see why), long press power button to turn on torch. You ask and thee shall receive, this build comes with the said feature.
8. Now we allow you to have a haptic feedback on QS tiles, when you tap on that, you know want that, don't you.
9. Some over the hood source changes, that'll make scrolling and animations go whoosh (faster and smoother), especially optimising the download and upload animations.
10. And a huge addition to feature list, Network traffic on status bar. For everyone who have been asking it is finally here.
11. Making life easier with this one, giving you an option to complete pull down the quick status bar either from left side or right side, depending on what you select. So you select, let's say right side, now if you pull down from left you'll have notifications. and if you pull down from right side you'll have the QS tiles. pretty handy right .
12. Added an Ambient music ticker, that'll flash new songs on ambient display, I personally love this, happy to finally be able to have it on stag .
13. Ok finally everything bugging with lock screen pin and pattern has been fixed, which allows to have scrambled pin layout back ).
14. Now directly delete a screenshot if you do not like it, directly from the preview when you take a new screenshot.
15. That's not all, now you can directly feed a screenshot into google lens, isn't that cool.
16. Added font customisation and a huge bunch of fonts, you'll absolutely love it. (We also have status bar, launcher icon customisations) you can find them in Horns > System.
17. Don't like watching '!' when mobile data is off ? worry not you can disable that now. see super thoughtful of me (just kidding)
18. If you are like me, you just want to watch the battery percentage on quick header and not something like "6 hours remaining", so like any sane person would do, I have added an option for you guys to be able to delete it.
Well that's all the changes for this update people....
oops spoke too soon, there's,more
19. Here's a little gesture touch, we now give you an option to turn of sleep either by double tapping on status bar or double tapping on Lock Screen. Use both or use neither upto you.
20. Wanna wake up your device using volume keys instead of power button. Just like shenron would say: "Your wish has been granted"
21. Ever seen a Samsung phone, Noticed their pop up notification (click here for reference), See how non intrusive and beautiful they look, don't be sad, you can have a very similar experience in stag, just go ahead and enable reticker from Horns. yay!!!
22. Ever see all the real estate in the status bar being wasted, the clock being so annoyed stuck beside camera, now you have the ability to customise it's location and the control that gives is amazing.
23. Made battery settings beautiful, added battery health info and capacity info so you also know what you have.
24. Added data usage panel.
25. Nav bar inversion, used to inverted back and recents layout, fear not when stag is here.
26. Smart auto-rotate, i.e. you rotate the phone by mistake when auto rotate is on, and phone just annoyingly rotates? not gonna happen that often anymore, phone will keep a track of your face and rotate only when it deems necessary based on orientation of your phone. (Will lead to higher battery consumption)
I could go on, but that's about most of it, there's still tiny under the hood improvements which aim at making stag ever better,
A huge change set this time, so I really am looking forward for you guys to try this build out, I really really wish you would love it and never want to leave ..
Happy Flashing
~Sic Parvis Magna~
Changelog - 10/04/2022
Hola guys long time no see, I know I promised monthly updates, but this one stretched far too long. The reasons include my college and android 12.1, which was a huge pain for me. But nevertheless here we are as stable as ever ).. Ok as always
Without further ado, I'll quickly list down the Changelog.
Bad news first:
1. We won't be having OOS camera anytime soon, Almost everything works except for rear normal photo, I need some help for fixing hence I am not including it in release builds. If anyone wants to try it out, feel free to pm me on telegram: @vjspranav.
Ok that was it, everything further just keeps getting better.
Device Specific
* Tweaked the position of alert slider UI to make it feel more natural.
* There was a small chance of sim not being detected on first boot, that has been fixed.
* Issues with Verizon have been fixed. A few devices report it as working, a few report it as broken, so you can probably just try it out and let me know.
* Wait must have been super annoying to see wrong charging info on Lock Screen, stuck at some 1hr 24 mins always. Now your phone works as it should have! Lock-screen charging info now shows correct estimates.
* One of the biggest things, we no longer spoof our whole device as pixel, It detects as a oneplus and that helps a great deal with refresh rate in a few apps. And guess what!?
CTS still successfully passes ).
* Added a bit of optimised charging support, although you can't control start stop percentage, your phone will still make sure to stop charging after a certain point. This will be adapted based on your usage.
* Finally for everyone not being able to flash gapps on pristine build, Now you can do so and much more, The issue has been fixed. You can flash any and every apps package, be it micro, mini, full or stock.
Rom
* Updated to Android 12.1 with April security patch, nothing but the latest and the best.
* Added back charging animation ripple removed as part of 12.1 by Google.
* Temporarily removed pocket lock as it is causing issues with device wake.
* Added quick unlock with pin, many have asked for it.
* Added option to enable always on display on charging only.
* Added options to customise fonts and styles of status bar.
* And a lot of under the hood changes thanks to both android 12.1 and also things we at stag do.
As always, stag is as good as you last remember it if not better. I really hope you enjoy the build, and keep showing the love!!.
Cheers
Changelog - 25/02/2022
Hello everyone, first of all, sorry for the delay of two months. I was super busy with life and had covid and college and stuff, secondly I am super happy and thrilled for the support everyone has been giving. I really hope you find this build and also the next exactly to your liking if not more .
Without further ado, I'll quickly list down the changelog.
Device Specific
* Firstly The clock being overlapped by camera cut out, padding issue has been fixed.
* On Lock Screen, you must've seen FP icon and charging info overlapping each other, this issue has also been fixed.
* You must've loved the new unlock animations of A12 right?, But I'm sure everyone felt, the power button location of animation is off, guess what we've got that fixed too!
* Ohh how could I forget, the dreaded ring issue, you won't have to face it anymore, every call you do will for sure have a ring giving you the peace of the call being connected and not having to face surprises.
* We Added OnePlus Specific Settings, That let you select Hyper Touch, Edge touch etc.
* Added Touch screen gestures, these are just love (we also support single tap for ambient display )
* Wake device on pick up, and a couple more ambient display options have been added.
* Build comes with a pre installed working GCam on gapps build.
* Wanted to share your battery to your friends? We have power share toggle added, you can wirelessly or through wire charge your friends phone or any chargeable device!
If you think those are good, wait till you see, what the ROM brings
Rom
* Updated to February patch.
* Ever wanted to look at your phone, and just wanted it to unlock, no sweat, stag has the long awaited face unlock support now.
* We have ota support now, all further builds can be downloaded and installed seamlessly over OTA.
* Added an idle battery manager, this helps in saving idle battery.
* Guess what ever wanted too listen to your class and YouTube, and wanted to decrease volume of your class/meeting only ? It's now possible, we have per app volume control, let your meeting run in silence and let the music begin!. (just kidding, we have the feature but don't miss out on classes )
* I believe there was an issue with no default notification or ringtone in the last build, worry not we got you covered!
* And remember that annoying screenshot sound ? I don't, because we don't have it anymore.
* And And, Live translate works, Complete the initial setup and update all apps, and you're all set.
* For all the enthusiasts, we have an amazing black theme, I know you are there and you are going to love it!
* You scared your phone gets unlocked in your pocket? Well just a toggle and your phone can be smart enough to not unlock as long as it's in your pocket! with pocket lock.
* You like your brightness slider at the bottom? Do not want to see the auto brightness icon ? Or don't want to see the bar at all ? Well you can do all of them now.
* We have saner heads up now, if you are constantly annoyed by every notification pop up on your screen! Explore it to know it.
Upcoming
* We are working on OOS Cam, we have potrait pro mode etc working, so expect to see the next build with OOS Cam .
and too much more, small changes and tweaks to make your experience the best possible!!.
Due to the volume of changes, it is highly recommended to clean flash for the best experience.
Hey! Thanks for the work!
Possible to confirm that these items work?
- Fingerprint sensor
- Face unlock
- 5G
- Bluetooth?
- Flash from A11 or A12?
- Gcam or Oneplus Camera?
- What is this recovery?
- The battery is ok?
- Stable enough to work with?
Thank you !
Hypnoz69 said:
Hey! Thanks for the work!
Possible to confirm that these items work?
- Fingerprint sensor
- Face unlock
- 5G
- Bluetooth?
- Flash from A11 or A12?
- Gcam or Oneplus Camera?
- What is this recovery?
- The battery is ok?
- Stable enough to work with?
Thank you !
Click to expand...
Click to collapse
1- Fingerprint Works
2- Nope, no Face unlock (Yet)
3- No one who tested reported 5g as broken, we don't have 5g at my place, but it should be working fine.
4- Bluetooth works just fine, I have usedi it for music and calls didn't face issue.
5- Gcam works, The one pre installed crashes, just uninstall it and install a compatible one, you'll be good to go.
6- A11 to A12 flash should be fine, but you'll have to wipe which technically is a clean flash.
7- It's just stock AOSP recovery based off on lineage recovery.
8- I have been using it as daily driver, Personally felt the battery has been kind to me.
9- And I prefer it over OOS
Cheers! Hope you check it out
~sicp parvis magna~
Thanks, i will give it a try in a couple of days
Nice, will give it a try later
Is there a tg group?
BobAzzon said:
Is there a tg group?
Click to expand...
Click to collapse
Stag-OS
Instagram : http://instagram.com/stag_os Source : https://github.com/StagOS Channel : t.me/HornsUpdates Wallpapers : t.me/Horns_Walls Feature request : t.me/stagos_bot
t.me
Good ROM
pranavasri said:
Stag-OS
Instagram : http://instagram.com/stag_os Source : https://github.com/StagOS Channel : t.me/HornsUpdates Wallpapers : t.me/Horns_Walls Feature request : t.me/stagos_bot
t.me
Click to expand...
Click to collapse
Guess I should have clarified lol, I meant device specific group as I consider your testers good friends...
BobAzzon said:
Guess I should have clarified lol, I meant device specific group as I consider your testers good friends...
Click to expand...
Click to collapse
XD, I guessed as much, but nah, we only have a testing group, no device specific group for rom.
ping me up on tg : @vjspranav if you are up for testing future builds.
Is there any possibility to get official OP9Pro stock camera on board for this rom??
And I have question, is Dolby Atom installed on the rom?
break.cold said:
Is there any possibility to get official OP9Pro stock camera on board for this rom??
And I have question, is Dolby Atom installed on the rom?
Click to expand...
Click to collapse
Nope, OOS Cam is a distant possibility as of now.
Don't have dolby atmos yet, looking into adding it in future builds.
pranavasri said:
Nope, OOS Cam is a distant possibility as of now.
Don't have dolby atmos yet, looking into adding it in future builds.
Click to expand...
Click to collapse
Can you plz direct which camera should be installed on this rom. There are so many Gcam's, but you can you please be more specific which one would be highly recommended for this rom since OOS Cam is lost hope!!!
break.cold said:
Can you plz direct which camera should be installed on this rom. There are so many Gcam's, but you can you please be more specific which one would be highly recommended for this rom since OOS Cam is lost hope!!!
Click to expand...
Click to collapse
I would suggest using this (as everyone who tested found this to work quite well): https://www.celsoazevedo.com/files/android/google-camera/dev-bsg/f/dl61/
The snap version apk here
Hi,
I hope this is an okay question to ask. How often can we expect updates?
lukehong9 said:
Hi,
I hope this is an okay question to ask. How often can we expect updates?
Click to expand...
Click to collapse
No, this question is NEVER OK. Don't ask the devs for ETA or how often will they update. They'll do it whenever they feel it and have time. They're doing this for free, remember that!
ekin_strops said:
No, this question is NEVER OK. Don't ask the devs for ETA or how often will they update. They'll do it whenever they feel it and have time. They're doing this for free, remember that!
Click to expand...
Click to collapse
Oh yeah I'm appreciative of them doing it for free. But I'll keep this in mind thank you!!
Wonderful work SIR!
So far running quite well.
I'm aware that this is the initial user build (beta), but I was wondering if the Color profiles will be added at a later time? At the moment there are the stock Android profiles present "Natural-Boosted-Saturated-Adaptive", which work fine if you select them. Just curious if the ones from OOS will be added "sRGB-WideGamut-DCI-P3"...
Thanks and keep up the good work!
Btw, I own multiple devices (Xiaomi ones), and I'm still part of "many" different testing groups, I flash my phones quite often (sometimes daily, or multiple builds per day when testing), so if you need a tester, I'm around, and I can, of course, take logs, and all whats needed.

Question A few questions from a new owner.

Hello everyone, I'll be getting my Poco F3 tomorrow and I have a few questions. Most of them were asked already but they're relatively old already and I'm unsure whether it got fixed or not. Anyways, here are my questions.
1) Was the proximity sensor issue patched/fixed? Is it any better than the release? I've seen quite a few commentaries regarding it's poor quality.
If it didn't get fixed, what are some workarounds?
2) In Samsung phones (at least a few years back) your camera quality used to be ABSOLUTELY TRASH if you used an AOSP ROM. Does the same happen with this phone? If so, GCam is the only workaround?
3) Is the real world performance (gaming, scrolling, app loading times) lower in AOSP ROMs?
Please reply to this one only if you have measured the performance on both ROMs yourself instead of repeating what somebody else said (we don't know the variables they had during testing).
4) Is it possible to flash an official recovery ROM with a locked bootloader? If so, would this tool be the safest way to do?
GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot - GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
github.com
5) Is it possible to downgrade a update through flashing a recovery ROM? (e.g. 12.5.7 to 12.5.6).
6) Is the screen dimming when gaming still an issue? If not, are there any workarounds?
7) Are there any other issues that I didn't mention or things you'd like to say?
Notes:
- When I say "AOSP ROMs" I'm mainly thinking about Lineage and MicroG for Lineage.
- Feel free to only reply to one or two of them, I'll be happy as long as the information is legitimate.
1. ROMs based on the ROM that was banned from here due to its name trees generally don't have much issue with it, as long as the hardware goes - it is as inaccurate on MIUI. With some lower quality ROMs it may be better or worse, as with anything else
There was one workaround with disabling the proximity sensor and turning off the screen when in-call, but that's rather a half measure.
2. There is MIUI camera port for Alioth somewhere, but as now most ROMs are based on A12 the compatibility may vary.
Gcam by BSG works well even with default settings and it supports all the hardware, so there's that. Needless to say, it doesn't support upscaling present in MIUI cam (so the front camera will take ~5 Mpix photos, compared to the fake 20 Mpix in MIUI).
3. I've used MIUI and some AOSP/Pixel ROM for some time and although benchmarking apps indeed show a little lower scores on AOSP (at least the few I've tried), AOSP ROMs generally feel more snappy - the difference may stem from the UX itself tho (i.e. janky MIUI gestures vs AOSP gestures).
4. I'd say it's always safer to go with official fasboot ROMs. Alioth is a bit messy when it comes to recovery in general; some ROMs work only with their own recovery images, some are recommended to use with the AOSP recovery, and both official and unofficial TWRPs aren't stable enough (or really worth it, IMO).
5. No idea; I believe Alioth has ARP, so you may need a workaround for it.
6. Never happened to me (MIUI or AOSP), it may be either vendor or screen panel specific.
7. Some people report slow charging speeds, which (as long it doesn't take over two hours) may be considered a feature as constant charging with full power is known to exhaust PMIC chips leading to hardware failures in the long run.
Apart from that, there is the green tint, which may happen in 120 Hz mode on some panels, but it is calibrated in some ROMs. It does occur on MIUI too.
EDIT: Also idle drain, but that's again ROM specific. Iirc LineageOS is generally stable when it comes to that.
Thank you very much for your reply, I have the device for a day and I have no issues with it.
My only qualm is the display panel on low brightness which looks rather bad (colors seem to shift only on certain areas, probably because it's not dimming it evenly) but that's fair considering the price point of the phone.
Also, the camera isn't even as bad as I thought, a happy surprise.

Question Are apps like Naptime and Servicely relevant anymore in Android 12?

Some people are still arguing about this purely from anecdotal experiences.
That's a very good question and now I want to find this out as well... I've installed Gsam Battery Monitor, Greenify, Servicely and Naptime.
I'm on Xiaomi.eu Custom ROM (Stable). I used to have better battery life (especially on Standby!) when I was still on an AOSP-based Custom ROM (ArrowOS). I have a feeling that the MIUI Always-On-Display causes Android Doze to not activate and that my device is essentially awake the whole time. I'm not sure about this observation, but Settings > Battery > Sort by "Details" tells me that my device is on. The whole time...
I've unrestricted the Battery monitoring apps I've installed, I'll leave AOD enabled, and see for another night if it is actually preventing my phone from going into Doze Sleep. Next night I'll disable AOD, and the night after that I'll enable Extreme Doze-Mode in Naptime and see the behaviour then.
Rant about Xiaomi LOL:
One thing I know for sure is that MIUI is so horribly coded. I don't need to be an OS developer to know this, you can just feel how dirty their custom implementations are. Ranging from their AOD, their Navbar/Gesture Controls, to the Adaptive Refresh rate.
It's like Xiaomi is trying to make the software deliberately feel cheap, because otherwise their phones would be too good, because their hardware is really good for the price. You can't just make a Poco F3 300€. The hardware is insanely good, but the Stock ROM is crap.
cyanGalaxy said:
I've installed Gsam Battery Monitor, Greenify, Servicely and Naptime.
Click to expand...
Click to collapse
I have stop using Greenify (it has not updated for 2 years) and lately have also replaced Naptime and Gsam/AccuBattery for BatteryGuru which combined both the main features (battery monitoring and aggressive Doze function).
I'm on ArrowOS 12.1 now, it seems Android11 gave me the best battery life, A12 was horrible and A12L is bearable.
I think it's time I stop worrying about battery and just replace the damn thing every 3 years lol.
mocmocmoc said:
I have stop using Greenify (it has not updated for 2 years) and lately have also replaced Naptime and Gsam/AccuBattery for BatteryGuru which combined both the main features (battery monitoring and aggressive Doze function).
I'm on ArrowOS 12.1 now, it seems Android11 gave me the best battery life, A12 was horrible and A12L is bearable.
I think it's time I stop worrying about battery and just replace the damn thing every 3 years lol.
Click to expand...
Click to collapse
I don't think Battery Life is related to the Android Version you're using, but more which brand's ROM you use. For example Samsungs OneUI seems more trustable than MIUI in terms of Reliability.
But you're likely best served on Clean Vanilla Android, in terms of Battery Life at least.
But also make sure to use a trusted and genuine AOSP ROM. Not one of those, where the Main Dev can't write proper English and uses some obscure Custom Kernel or whatever.. Use one that's known and popular.
I did figure out that MIUI's Always-On-Display kept the CPU awake at all times. I could see it in Settings > Battery, and changing "Ranking" to "Details".
I don't know if that's normal for AOD or if it's MIUI's implementation of AOD, but my god.. AOD shouldn't drain that much. But now my battery life is normal again. ^^
cyanGalaxy said:
I don't think Battery Life is related to the Android Version you're using, but more which brand's ROM you use. For example Samsungs OneUI seems more trustable than MIUI in terms of Reliability.
But you're likely best served on Clean Vanilla Android, in terms of Battery Life at least.
But also make sure to use a trusted and genuine AOSP ROM. Not one of those, where the Main Dev can't write proper English and uses some obscure Custom Kernel or whatever.. Use one that's known and popular.
I did figure out that MIUI's Always-On-Display kept the CPU awake at all times. I could see it in Settings > Battery, and changing "Ranking" to "Details".
I don't know if that's normal for AOD or if it's MIUI's implementation of AOD, but my god.. AOD shouldn't drain that much. But now my battery life is normal again. ^^
Click to expand...
Click to collapse
For all practical purposes, the best/definitive experience of Android is obtained on a Samsung device nowadays. So much so that Google released certain new features in some of their apps on Samsung devices ONLY to begin with, not even their own Pixel devices. And Pixel software experience is terrible. And Samsung has innovated so many new features that Google slowly incorporates into stock Android. Samsung Dex is still unparalleled. I personally don't like some aspects of Samsung UI. The squircle icons, the excessively round UI elements with large paddings.. Sadly, Google seems to have incorporated some of this into Android 12's Material You styling. Android 12 looks more like a Samsung One UI skin. That was my FIRST impression when I played around with Material You, i.e. how much it reminded me of Samsung's style.
I agree that Xiaomi's MIUI has a load of flaws in them. The latest is their custom per-app dark mode override has been broken since they released MIUI 13 and before that you had to do some funky things to make it show the list of apps. They never allowed us to see notification history for some strange reason. These are two issues I can think off right away. But otherwise I feel that the software is pretty decent and I had no major issues with it and the battery life with Stock ROM is quite good. I personally don't understand the vehement negativity towards MIUI. Perhaps in the past it was attrocious, but now it is decent. Just like Samsung's One UI. Remember the awful TouchWiz days!? I still have an old tablet with Samsung's touch wiz on it! Bottom line, MIUI is nothing exemplary, but definitely usable and fine, with some minor issues.
In fact, I do like some of the things in MIUI versus stock. I like the fact that the Settings button is immediately visible in the notification shade (like it USED to be on Stock Android) rather than having to swipe again to reveal the quick toggles. I do like some of their built in apps, like the Clock, Calculator (which is very feature rich) and Compass app. So, overall not too shaby.
But I ranted a lot in this thread and none of this is relevant for this topic! So back to relevance...
I do use GSam battery monitor and after a lot of usage I feel like my battery life on Stock MIUI is similar to Arrow OS. I used Arrow OS 11, I used MIUI 12 and 13 and the battery life on all of them was very similar. Arrow OS 11 had some weird bugs with incoming phone call sound and Bluetooth when using Navigation. But Stock MIUI has no such issues. I've slowly decided to stop paying close attention to battery life as it is mostly very good for my usage.
litetaker said:
For all practical purposes, the best/definitive experience of Android is obtained on a Samsung device nowadays. So much so that Google released certain new features in some of their apps on Samsung devices ONLY to begin with, not even their own Pixel devices. And Pixel software experience is terrible. And Samsung has innovated so many new features that Google slowly incorporates into stock Android. Samsung Dex is still unparalleled. I personally don't like some aspects of Samsung UI. The squircle icons, the excessively round UI elements with large paddings.. Sadly, Google seems to have incorporated some of this into Android 12's Material You styling. Android 12 looks more like a Samsung One UI skin. That was my FIRST impression when I played around with Material You, i.e. how much it reminded me of Samsung's style.
...
Click to expand...
Click to collapse
For me the hate for MIUI stems from all the little things.
Notification History & Log being hidden (Can be accessed through an Activity Launcher),
Holding a notification and clicking "More" doesn't bring to you to the specific notification channel,
No Gestures on 3rd Party Launchers,
Recents-Animations broken on 3rd Party Launchers,
Dolby Atmos Sound effect doesn't apply to the first volume step.
Touch Sounds are way too loud, regardless of users volume,
For Google Clock to work properly, you need to disable MIUI Battery Saver,
MIUI Boot Sound is way too loud, also regardless of users volume,
Annoying additional restrictions/permission-manager which cannot be turned off anymore,
Fullscreen Pop-Up with user-unfriendly 10 second timer when trying to change sensitive permissions,
Adaptive Refresh Rate only activating when Screen-brightness is >80%, and only after 2 second delay,
YouTube, Games etc are forced to 60 Hz,
MIUI Camera doesn't respect Default-Gallery setting and always uses MIUI Gallery,
Default Camera cannot be changed,
Monet Colours cannot be customised,
Almost all apps used to get forcibly themed dark (even when the app already had Dark Mode), and you had to individually disable it for all apps. This made text from some apps unreadable.
I do like a few changes Xiaomi has done to Android with MIUI, like bringing back down the Brightness-bar (retarded change from Google), Custom Fonts, the really cool Live Wallpapers, its Dolby Atmos and much more...
I also do like many of their apps like Mi Fitness and the Calc...
But all the little issues give me micro-aggression. It's not a 100% reliable OS in my opinion and I'm still a tiny bit concerned about its Privacy & Tracking.. it's still a chinese company and China is ruled by CCP. The chinese Gov't can control their Tech companies.
Samsungs OneUI does indeed seem like a good and stable experience. But I'm also not a fan of goofy rounded corners and padding.
I bought my Galaxy Note 8 when TouchWiz was still a thing. Then a System update came and upgraded me to OneUI 1.0 and I kinda didn't like it all that much. TouchWiz looked a bit more professional to me, but that's just personal preference.
I'm more into Edgy than Curvy ;D
Yes, Naptime still makes quite a difference with its agressive dove settings and disabling sensors.
Even with how optimized Android 12 is you cannot escape bad programmed third party apps, so use something like IceBox to freeze not often used apps too
cyanGalaxy said:
For me the hate for MIUI stems from all the little things.
Notification History & Log being hidden (Can be accessed through an Activity Launcher),
Holding a notification and clicking "More" doesn't bring to you to the specific notification channel,
No Gestures on 3rd Party Launchers,
Recents-Animations broken on 3rd Party Launchers,
Dolby Atmos Sound effect doesn't apply to the first volume step.
Touch Sounds are way too loud, regardless of users volume,
For Google Clock to work properly, you need to disable MIUI Battery Saver,
MIUI Boot Sound is way too loud, also regardless of users volume,
Annoying additional restrictions/permission-manager which cannot be turned off anymore,
Fullscreen Pop-Up with user-unfriendly 10 second timer when trying to change sensitive permissions,
Adaptive Refresh Rate only activating when Screen-brightness is >80%, and only after 2 second delay,
YouTube, Games etc are forced to 60 Hz,
MIUI Camera doesn't respect Default-Gallery setting and always uses MIUI Gallery,
Default Camera cannot be changed,
Monet Colours cannot be customised,
Almost all apps used to get forcibly themed dark (even when the app already had Dark Mode), and you had to individually disable it for all apps. This made text from some apps unreadable.
I do like a few changes Xiaomi has done to Android with MIUI, like bringing back down the Brightness-bar (retarded change from Google), Custom Fonts, the really cool Live Wallpapers, its Dolby Atmos and much more...
I also do like many of their apps like Mi Fitness and the Calc...
But all the little issues give me micro-aggression. It's not a 100% reliable OS in my opinion and I'm still a tiny bit concerned about its Privacy & Tracking.. it's still a chinese company and China is ruled by CCP. The chinese Gov't can control their Tech companies.
Samsungs OneUI does indeed seem like a good and stable experience. But I'm also not a fan of goofy rounded corners and padding.
I bought my Galaxy Note 8 when TouchWiz was still a thing. Then a System update came and upgraded me to OneUI 1.0 and I kinda didn't like it all that much. TouchWiz looked a bit more professional to me, but that's just personal preference.
I'm more into Edgy than Curvy ;D
Click to expand...
Click to collapse
I guess these can be frustrating issues for some, but none of this is an issue for me. I tend not to get overly worked up by minor software issues. In fact I do not mind the additional 10 second delay for sensitive permissions. For power users it maybe too annoying, but for ordinary users it is useful to show such warnings to help them avoid making big mistakes and messing up their phones or falling for scams. And anyway, it is just an extra 10 seconds delay. I do admit that blocking access to notification history is annoying but I have learned to live with it. Having the per app dark mode option is genuinely useful as it allows me to force dark mode on only some apps that I use that don't have a dark mode built in, rather than forcing it on all apps via Developer tools. Although this is not working anymore on MIUI 13.
litetaker said:
I guess these can be frustrating issues for some, but none of this is an issue for me. I tend not to get overly worked up by minor software issues. In fact I do not mind the additional 10 second delay for sensitive permissions. For power users it maybe too annoying, but for ordinary users it is useful to show such warnings to help them avoid making big mistakes and messing up their phones or falling for scams. And anyway, it is just an extra 10 seconds delay. I do admit that blocking access to notification history is annoying but I have learned to live with it. Having the per app dark mode option is genuinely useful as it allows me to force dark mode on only some apps that I use that don't have a dark mode built in, rather than forcing it on all apps via Developer tools. Although this is not working anymore on MIUI 13.
Click to expand...
Click to collapse
I think the Warning with 10 sec-timer is the most infuriating one. :x
About Notification History, you can download Activity Launcher, search "Notification History" and make a shortcut for that hidden Activity to your Home screen!
That's what I did, because I use Notification Log & Notification History regularly.
However Notification-History on MIUI is a bit broken. You have to enable Light Mode to see the text properly
cyanGalaxy said:
I think the Warning with 10 sec-timer is the most infuriating one. :x
About Notification History, you can download Activity Launcher, search "Notification History" and make a shortcut for that hidden Activity to your Home screen!
That's what I did, because I use Notification Log & Notification History regularly.
However Notification-History on MIUI is a bit broken. You have to enable Light Mode to see the text properly
Click to expand...
Click to collapse
Thanks a lot for the tip on how to get Notification History! That is very useful! It is stupid that Xiaomi blocks us from accessing this useful information natively and we need to use a third party app to expose this activity, but at least now I can see the history and get some info! Sometimes I get a ping on my phone and I am not sure which notification caused it. Now I can get more clarity! Yay!
BrokeBloke1969 said:
Yes, Naptime still makes quite a difference with its agressive dove settings and disabling sensors.
Even with how optimized Android 12 is you cannot escape bad programmed third party apps, so use something like IceBox to freeze not often used apps too
Click to expand...
Click to collapse
We are now 1 year on, and Naptime + Servicely doesn't matter one bit on new devices. I've been running Android 13 for a while now and have never felt the need to install these two apps.
With Android 14 around the corner, app efficiency will be addressed even further by TARE and the introduction of new background APIs.
I'm still using naptime since a9/10. And see no reason to not use it. Induce deep sleep faster.
BTW, anyone noticed that naptime was removed from play store?
lapirado said:
I'm still using naptime since a9/10. And see no reason to not use it. Induce deep sleep faster.
BTW, anyone noticed that naptime was removed from play store?
Click to expand...
Click to collapse
Yup i think Naptime and Servicely do improve my battery life! I can see from the Naptime Doze-logs that my phone goes to Deep Doze faster and the battery life does seem improved.
I just checked, and Naptime seems to be gone from Play Store, tho not Servicely. I think Google are being twats again...
cyanGalaxy said:
Yup i think Naptime and Servicely do improve my battery life! I can see from the Naptime Doze-logs that my phone goes to Deep Doze faster and the battery life does seem improved.
I just checked, and Naptime seems to be gone from Play Store, tho not Servicely. I think Google are being twats again...
Click to expand...
Click to collapse
Hi, I could not run Naptime on Oxygen OS without Root. Did you find a solution? It worked fine on OOS11.
skyNET said:
Hi, I could not run Naptime on Oxygen OS without Root. Did you find a solution? It worked fine on OOS11.
Click to expand...
Click to collapse
Does the app not start for you? You don't need Root, you can grant the permissions via ADB.
cyanGalaxy said:
Does the app not start for you? You don't need Root, you can grant the permissions via ADB.
Click to expand...
Click to collapse
First of all thanks for your answer.
Yes, of course, it doesn't start properly, it shuts down quickly. I gave permissions with adb in OOS11 and it was doing its job really well (Naptime). But after I upgraded to OOS 12, I saw that the following command string "adb -d shell pm grant..." did not work and gave an error. I can't get around this problem, have you tried it? Naptime is a really successful app and OOS needs it.
skyNET said:
First of all thanks for your answer.
Yes, of course, it doesn't start properly, it shuts down quickly. I gave permissions with adb in OOS11 and it was doing its job really well (Naptime). But after I upgraded to OOS 12, I saw that the following command string "adb -d shell pm grant..." did not work and gave an error. I can't get around this problem, have you tried it? Naptime is a really successful app and OOS needs it.
Click to expand...
Click to collapse
What error?
Enable USB debugging, connect your phone to PC, get the Google SDK Platform Tools, open the folder in Terminal, and type the commands exactly as written.
If you are on MIUI, you also have to enable "USB Debugging (Secure Settings)"
cyanGalaxy said:
What error?
Enable USB debugging, connect your phone to PC, get the Google SDK Platform Tools, open the folder in Terminal, and type the commands exactly as written.
If you are on MIUI, you also have to enable "USB Debugging (Secure Settings)"
Click to expand...
Click to collapse
Let me show you the simplest with BBS!
skyNET said:
Let me show you the simplest with BBS!
Click to expand...
Click to collapse
Try "adb shell" -> "pm grant ..........."
cyanGalaxy said:
Try "adb shell" -> "pm grant ..........."
Click to expand...
Click to collapse
Like this?

Categories

Resources