I hope @blacksuan19 will make us some pie rom. He was the winner on oreo 
Make it yourself if you can't waitHope DotOS have Pie 9.0 soon because a lot of AOSP rom having Pie already for test.
What does kernel has to do with alarms?
Never had any issues with alarms on any rom
Also this device doesn't have black box kernel
No "tweaking" whatsoever
Use a diff kernel and test then
Also we need logs if you expecting something to be fixed
I'm experienced this too, dev. My alarm doesn't ringing.
Latest build (13/9) with dark ages kernel.
My bad.
Hi...one doubt !
Existing center clock in status bar or not ?
Thanx
Enviado de meu Redmi 5 Plus usando o Tapatalk
Thank you my friend. Downloading now.My bad.
---------- Post added at 01:37 AM ---------- Previous post was at 01:34 AM ----------
Yes it's available and much more. Go to settings, dot extras. And there you can customize anything.
It's different. But what's the custom DPI in those screenshots of the first page. They look really cute and lovely.Would appreciate if I get to know. Thank you
Just flash DA. It's for both treble and non. Or zuccVersion 2.5 not boot, but is 2.4 OK. I must install another kernel, but i dont know if treble or not.
Are u an official member to say or confirm that
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
[LIST]
[U][B]STATUSBAR:[/B][/U]
[*]Battery Icon Style
[*]Clock and Date
[*]Statusbar icons
[*]Traffic indicators
[*]Brightness Control
[*]Show data disabled icon
[*]Roaming Indicator
[*]Battery Bar Customisation
[*]Misc
[U][B]Navigation Bar:[/B][/U]
[*]Navbar modes(Stock, Smartbar, Fling)
[*]Smartbar tweaks
[*]Navbar Pulse
[*]Fling mode gestures
[*]All DUI nav tweaks
[U][B]QUICK SETTINGS:[/B][/U]
[*]Brightness slider toggle
[*]Titles visibility
[*]Tiles track accent color toogle
[*]Quick pulldown
[*]Smart pulldown
[*]Rows and columns tweaks
[U][B]RECENTS:[/B][/U]
[*]Memory bar
[*]Immersive recents
[*]Clear all fab
[*]Clear all fab location
[U][B]LOCKSCREEN:[/B][/U]
[*]Double-tap to sleep
[*]Lockscreen Tuner
[*]Charging info
[*]Media cover art toggle
[*] Lockscreen Visualizer
[*] New Set Lockscreen Clocks
[*]Face auto unlock
[*]Fingerprint Authentication Vibration
[*]Lockscreen Tuner
[*]hide Clock and date widget
[*]Hide status bar items
[U][B]BUTTONS:[/B][/U]
[*]Powermenu tweaks
[*]H/W keys customisation
[*]Volume button tweaks
[U][B]MISC:[/B][/U]
[*]Launch music app on headset connection
[*]Battery light charging customisations
[*]App Ops
[U][B]DotUICenter:[/B][/U]
[*]Accent Color Manager
[*]Qs panel Customisation
[*]Misc features
[/LIST]
Sure, after it burned the display of some people. Now those people have a broken phone.
Can you trust for things like that to not happen again? A lot of developers here (a lot of them are kids) love to put some new drivers and "cutting edge" kernels without testing it, just to be cool. This will eventually happen again if this goes on. And what is worse is that these so called "official" roms doesn't have anything that makes them more trustworthy than any other rom. These developers put what they want there without researching and testing first.
The "official" branding just tells you that the maintainer will keep updating, but it doesn't have any indication that the code is safe, verified and consistent between all the releases.
I had a Moto G 2015 for a long time, i lost it at a festival these days. I used the official LineageOS from their homepage all these years without a single problem, because they are a trustable source, the code is transparent and they play it safe.
There is a reason why MIUI and other companies don't update to Oreo so fast. They beta test it for a long time. A lot of things goes wrong if you keep pushing forward. And i'm talking about companies with a lot of people.
Now imagine one kid doing this alone, using "alternative" drivers and kernels. It's a recipe for disaster, which we saw in this thread.