Related
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
mkanet said:
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
Click to expand...
Click to collapse
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
dwitherell said:
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Click to expand...
Click to collapse
My annoying fix...
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
I forgot to mention that lock screen prevents this bug from happenening. I'm guessing that's why not everyone has complained about the issue.. and why the bug somehow sneaked passed beta testing of 4.1.2. I would think this changed behavior was a new "feature" as horrible as it is, but it looks like it dad unintentional since its not consistent behavior.
I'm hoping that a kind android developer who also can't stand this problem, Kay offer a small script or app for rooted user to patch this problem.
mrtolles said:
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
Click to expand...
Click to collapse
mkanet said:
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
Click to expand...
Click to collapse
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
You did it! Your fix works perfectly! The bug is gone! ...like the bug was never there. My understanding is the fix prevents the phone from stupidly trying to launch the task manager when the screen wakes by the home button. I also donated for you time and effort. Thanks a million.
dwitherell said:
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
Click to expand...
Click to collapse
No, thank you for making me learn how to put an odexed mod together and testing it for me!
So this fix will work for anyone running a stock odexed version of 4.1.2 UVBMB4 - you just need to be rooted, and having a custom recovery would be nice so you could flash it but you could also just copy the files over. That being said - would this be worthwhile to post?
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
mkanet said:
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
Click to expand...
Click to collapse
The flashable zip is just one method to get the files where they need to go. Literally all it does is overwrite the 2 files in /system/framework by moving the 2 files over from the zip - but there are definitely other ways to do such things. Some are more comfortable with this route, others are more comfortable w/ getting /system to be rw and move the files manually.
I'll likely post this at some point in the next few days
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
Glad to hear
Is it possible that my phone isn't affected? If its a 4.1.2 bug, it should be in all phones with same version right?
This is not happening to my phone. Whether I have lock screen activated or not. I'm rooted but running stock ROM and I have Nova launcher installed if thats even important.
It's not all notes.
Sent from my SGH-T889 using xda premium
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Yes you'll need to be rooted unfortunately - sorry
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Absolutely. just PM me. Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
kabuk1 said:
...Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
Click to expand...
Click to collapse
^^^ THIS - a thousand times over
Since You know G2 supports tap to unlock, it would be cool if You could implement the same method in ParanoidAndroid ROM.
Since I found this video https://www.youtube.com/watch?v=DHXdnOnEr0o
it seems to be working fine, but I'm not sure how to implement new kernel without ruining my phone, so I taught you could implement it in ROM itself?
Oh, and yeah, YOU'RE AWESOME!
Thanks!
Ukiand1 said:
Since You know G2 supports tap to unlock, it would be cool if You could implement the same method in ParanoidAndroid ROM.
Since I found this video https://www.youtube.com/watch?v=DHXdnOnEr0o
it seems to be working fine, but I'm not sure how to implement new kernel without ruining my phone, so I taught you could implement it in ROM itself?
Oh, and yeah, YOU'RE AWESOME!
Thanks!
Click to expand...
Click to collapse
It's a kernel dependent feature.
There is nothing complex about installing a custom kernel... find one compatible to your device and flash it. Done
Just add the title says I've been having this issue ever since i started flashing custom ROMs. This only happens in custom ROMs with either custom kernel (flash) or built in kernel. At the most random times when i go to wake my device the screen will stay black but the phone is still responsive. Led light still flashing from notifications I'm trying to check i can still toggle flashlight but holding the power button and etc. It's just the dam screen refuses to wake until around 20/30 seconds!! No one else is having this problem in the rom threads which would be DU help thread, NOS, and AquariOS THREADS. I've tried everything to remedy the problem including clean flashes whipping caches no modifications. Nothing has worked. Just wondering if anyone experienced the same thing and how to solve the problem. Thanks in advance.
sharpz811 said:
Just add the title says I've been having this issue ever since i started flashing custom ROMs. This only happens in custom ROMs with either custom kernel (flash) or built in kernel. At the most random times when i go to wake my device the screen will stay black but the phone is still responsive. Led light still flashing from notifications I'm trying to check i can still toggle flashlight but holding the power button and etc. It's just the dam screen refuses to wake until around 20/30 seconds!! No one else is having this problem in the rom threads which would be DU help thread, NOS, and AquariOS THREADS. I've tried everything to remedy the problem including clean flashes whipping caches no modifications. Nothing has worked. Just wondering if anyone experienced the same thing and how to solve the problem. Thanks in advance.
Click to expand...
Click to collapse
I've seen the issue of which you speak several times in the threads. Unfortunately, I haven't seen a good solution to the problem. If it were me, I'd RMA that thing. Are you having the issue as well just running stock+root? ?
Badger50 said:
I've seen the issue of which you speak several times in the threads. Unfortunately, I haven't seen a good solution to the problem. If it were me, I'd RMA that thing. Are you having the issue as well just running stock+root? ?
Click to expand...
Click to collapse
That's why i posted here because i don't wanna keep spamming the threads. I would've thought to RMA but this never ever happens on stock+root+flash kernel. It's so frustrating because it's so hard to pin point what's going on so I'll try a clean flash tonight after work and then i will only install Flash kernel and magisk (those can't be the culprits and i would refuse to believe if anyone said otherwise) I'm also only gonna install my basic most needed apps it has to be one of my user apps not playing nice with custom ROMs but every single app i have running right now on AquariOS is the same exact apps and setup i have on my twrp backup of stock. This just don't make sense. Stock is really really nice on this phone but i still prefer custom ROMs for certain much needed features that i either can't get from stock or have to install some mod or something. Thanks for keeping tabs in me tho Badger!!?? Your a good man really appreciate your help bro
sharpz811 said:
That's why i posted here because i don't wanna keep spamming the threads. I would've thought to RMA but this never ever happens on stock+root+flash kernel. It's so frustrating because it's so hard to pin point what's going on so I'll try a clean flash tonight after work and then i will only install Flash kernel and magisk (those can't be the culprits and i would refuse to believe if anyone said otherwise) I'm also only gonna install my basic most needed apps it has to be one of my user apps not playing nice with custom ROMs but every single app i have running right now on AquariOS is the same exact apps and setup i have on my twrp backup of stock. This just don't make sense. Stock is really really nice on this phone but i still prefer custom ROMs for certain much needed features that i either can't get from stock or have to install some mod or something. Thanks for keeping tabs in me tho Badger!!?? Your a good man really appreciate your help bro
Click to expand...
Click to collapse
That's definitely an odd deal for sure. Like you, I run all my same apps on AquariOS as I do on stock+root, however I don't have the same problem as you. And don't worry bruh, I'm not keeping tabs on you. I just try to help with problems when I see them. Keep us posted on your findings my friend
Badger50 said:
That's definitely an odd deal for sure. Like you, I run all my same apps on AquariOS as I do on stock+root, however I don't have the same problem as you. And don't worry bruh, I'm not keeping tabs on you. I just try to help with problems when I see them. Keep us posted on your findings my friend
Click to expand...
Click to collapse
Your a good man. It has to be in my end one of my user apps has to be hopefully I'll figure this out
sharpz811 said:
Your a good man. It has to be in my end one of my user apps has to be hopefully I'll figure this out
Click to expand...
Click to collapse
I also saw it might be to do with smart lock, have you got any of them set? It is being looked into so dont worry you are not alone. Last time it happened to me I just added another fingerprint and then it was fine.
Just a thought, but this is known to be an issue with various immersive modes. Are using immersive modes on these custom roms, or is it already built in?
Sent from my Pixel 2 XL using XDA Labs
sharkie405 said:
Just a thought, but this is known to be an issue with various immersive modes. Are using immersive modes on these custom roms, or is it already built in?
Click to expand...
Click to collapse
IM is built in on some of the roms, however, you can choose to enable them or not. It's a feature I've never used, and haven't had any of these issues, so you may be onto something my friend ?
sharkie405 said:
Just a thought, but this is known to be an issue with various immersive modes. Are using immersive modes on these custom roms, or is it already built in?
Click to expand...
Click to collapse
Badger50 said:
IM is built in on some of the roms, however, you can choose to enable them or not. It's a feature I've never used, and haven't had any of these issues, so you may be onto something my friend ?
Click to expand...
Click to collapse
Ok ok you guys are probably right?? I always use immersive mode on all three custom ROMs and I also use it in stock ROM via custom navigation bar app but line I said stock ROM never produces these issues. So I will check smart lock but I've never used it and I will turn off immersive mode and I will add 1 or 2 more fingerprints and then report back. THANKS AGAIN GUYS.
sharpz811 said:
Ok ok you guys are probably right?? I always use immersive mode on all three custom ROMs and I also use it in stock ROM via custom navigation bar app but line I said stock ROM never produces these issues. So I will check smart lock but I've never used it and I will turn off immersive mode and I will add 1 or 2 more fingerprints and then report back. THANKS AGAIN GUYS.
Click to expand...
Click to collapse
The Custom Navigation Bar app dev has said that they identified and fixed that issue in their app. That would explain why you don't experience the issue while on stock using that app, but do have it on custom ROMs using some other immersive mode method.
Sent from my Pixel 2 XL using XDA Labs
sharkie405 said:
The Custom Navigation Bar app dev has said that they identified and fixed that issue in their app. That would explain why you don't experience the issue while on stock using that app, but do have it on custom ROMs using some other immersive mode method.
Click to expand...
Click to collapse
That explains so much! Thank you for clearing that up for me. I've already disabled immersive mode from Coral reef settings in Aquarius ROM and haven't had the issue all day. I hope devs can fix immersive mode in custom ROMs as well but i can live without it for now. Thanks again man.
Hi, I didn't know if this should be in Questions or Discussions, so apologies ahead of time.
I just got a Pixel 2 XL and recently unlocked the bootloader. I'm thinking about experimenting with some custom ROMs and tweaking some things, however I'm really digging the stock Pie experience. Is there really any super good reasons for installing any of the misc. ROMs out there? Or should I just stick to stock? Just looking for some opinions. Thanks!
jayyskittles said:
Hi, I didn't know if this should be in Questions or Discussions, so apologies ahead of time.
I just got a Pixel 2 XL and recently unlocked the bootloader. I'm thinking about experimenting with some custom ROMs and tweaking some things, however I'm really digging the stock Pie experience. Is there really any super good reasons for installing any of the misc. ROMs out there? Or should I just stick to stock? Just looking for some opinions. Thanks!
Click to expand...
Click to collapse
Personally speaking, I've tried most of the custom roms, and they're all great in their own way, with fantastic Dev & community support in all of them. Having said that, I like the simplicity, and ease of updating every month with the factory images when they come out. Just a few clicks here and there, and I'm running the latest software and security updates, with my magisk modules, root apps, and themes up and running in about 30 minutes. But again, that's just me
Badger50 said:
Personally speaking, I've tried most of the custom roms, and they're all great in their own way, with fantastic Dev & community support in all of them. Having said that, I like the simplicity, and ease of updating every month with the factory images when they come out. Just a few clicks here and there, and I'm running the latest software and security updates, with my magisk modules, root apps, and themes up and running in about 30 minutes. But again, that's just me
Click to expand...
Click to collapse
Hmm, thanks for the thought. I've been digging how fast the stock ROM is. As long as it's easy to go back to stock I might give it a go, I just don't wanna risk the out of the box experience lol
jayyskittles said:
Hmm, thanks for the thought. I've been digging how fast the stock ROM is. As long as it's easy to go back to stock I might give it a go, I just don't wanna risk the out of the box experience lol
Click to expand...
Click to collapse
No worries. With a little reading and some patience, you can usually always get back to stock. Course, ya never know when the gremlins will strike!
I've been on a major crack-flashing kick. I love the freedom. I've become very fond of a couple features some of the ROMS offer that are baked in. Stock is great, no doubt. Yet, the ROMS provided here are fantastic. Def worth a spin!
Badger50 said:
No worries. With a little reading and some patience, you can usually always get back to stock. Course, ya never know when the gremlins will strike!
Click to expand...
Click to collapse
TWRP still the recovery to use? Or can I finally just use stock to flash ROMs and the such lol?
jayyskittles said:
TWRP still the recovery to use? Or can I finally just use stock to flash ROMs and the such lol?
Click to expand...
Click to collapse
Twrp bruh
Badger50 said:
Personally speaking, I've tried most of the custom roms, and they're all great in their own way, with fantastic Dev & community support in all of them. Having said that, I like the simplicity, and ease of updating every month with the factory images when they come out. Just a few clicks here and there, and I'm running the latest software and security updates, with my magisk modules, root apps, and themes up and running in about 30 minutes. But again, that's just me
Click to expand...
Click to collapse
Yeah, me too...
Currently I'm running the 12/5 build of Liquid and I really dig it. The version that is newer seems to have some complaints. When the next monthly update comes along I'll prolly try to dirty flash but will be prepared to go back to stock on the January update. Lol I know how to deal with burps on stock most of the times...
Custom roms all the way lol but i wouldn't even mind a custom stock rom with a few minor tweaks and mods like the old Google devices had
Jiggs82 said:
Custom roms all the way lol but i wouldn't even mind a custom stock rom with a few minor tweaks and mods like the old Google devices had
Click to expand...
Click to collapse
Remember the ol Cataclysm mod? That was da bomb right there bruh :good:
Badger50 said:
Remember the ol Cataclysm mod? That was da bomb right there bruh :good:
Click to expand...
Click to collapse
Haha yup I sure do.. the good ol days
Personally, I went on a week kick of using custom ROMs. I love them. They generally perform great and have some useful features, for me, such as:
One-handed mode
Swipe left on nav bar to go back
Status bar customization
Quick and easy themes for dark mode
etc
However, there are just a few trade-offs, which could make it or break it for you.
No squeeze for Assistant. I use this not for assistant but with the Edge Sense Magisk module that lets you customize your squeezes to do literally anything lol.
LED Notification (I have not been able to get this working on any ROM but someone correct me if its just a "me issue".
No ambient display "Now Playing" text. Keep in mind it'll still pop up as a notification and there was one ROM I tried (Nitrogen possibly?) that allowed me to control music on Spotify via the ambient display and i LOVED that!
Those 3 reasons keep me on stock for now. I may switch back into the ROM scene if I could at least get the LED notification working lol. The active edge functionality is also something I use constantly but it's not the end of the world if it's gone.
Anyway, this is what Ive noticed! Hope others can chime in!
Edit: I use light manager on stock. I'm unsure if it works on custom ROMs. I should try it!
Darriousx said:
Personality, I went on a week kick of using custom ROMs. I love them. They generally perform great and have some useful features, for me, such as:
One-handed mode
Swipe left on nav bar to go back
Status bar customization
Quick and easy themes for dark mode
etc
However, there are just a few trade-offs, which could make it or break it for you.
No squeeze for Assistant. I use this not for assistant but with the Edge Sense Magisk module that lets you customize your squeezes to do literally anything lol.
LED Notification (I have not been able to get this working on any ROM but someone correct me if its just a "me issue".
No ambient display "Now Playing" text. Keep in mind it'll still pop up as a notification and there was one ROM I tried (Nitrogen possibly?) that allowed me to control music on Spotify via the ambient display and i LOVED that!
Those 3 reasons keep me on stock for now. I may switch back into the ROM scene if I could at least get the LED notification working lol. The active edge functionality is also something I use constantly but it's not the end of the world if it's gone.
Anyway, this is what Ive noticed! Hope others can chime in!
Click to expand...
Click to collapse
Have you tried using Light Manger for your led notifications? Used to work great on 8.1 with custom roms. Although 9.0 may be different.
Badger50 said:
Have you tried using Light Manger for your led notifications? Used to work great on 8.1 with custom roms. Although 9.0 may be different.
Click to expand...
Click to collapse
I use Light Flow for my notification light needs and haven't had any issues.
Sent from my Pixel 2 XL using Tapatalk
Badger50 said:
Have you tried using Light Manger for your led notifications? Used to work great on 8.1 with custom roms. Although 9.0 may be different.
Click to expand...
Click to collapse
localceleb said:
I use Light Flow for my notification light needs and haven't had any issues.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I use Light Manager on stock! I love it. You @localceleb use it on custom ROMs and it works? I'll admit that I have not tried it on custom ROMs but on stock it works swimmingly well! Haha
The beauty of these phones is you can always go to back to stock by just flashing the ota file in twrp.
So far my favourites are DU13 and Pixel dust.
I enjoyed Havoc AOSP. For now for me nothing beats stock with edge control. I use long squeeze for flashlight which is awesome for overnight piss breaks.
I never use squeeze nor care for the "Now Playing" on the lock screen (actually disabled both on stock).
I have been running stock for about a year with custom kernel, then found Havoc-OS and flashed that about 2 weeks ago. Don't have any complaints and absolutely love the customisation. Probably won't be going back to stock for awhile.
I prefer custom ROMs for minor tweaks such as status bar icon settings, lockscreen stuff and Substratum!
I've bought many themes so I'd rather have a device that has commits to make it work to its max potential (i.e. not having to reboot to enable overlays).
Updating process isn't difficult for custom ROMs either. Developers are usually pretty quick with updates once the Google images release every month. Just need to flash the new ROM zip, TWRP, kernel and root and you're golden!
As we all know, fullscreen gestures do not work on our devices (at least on mine they don't) if you are using anything other than the standard launchers, which is a complete no-go since they are devoid of a lot of features I regard as essential. Now I know no reason why gestures should not work on Custom ROMs but I have had no chance to try other ROMs yet (haven't unlocked my phone yet) but I figured i'd ask since the rom threads are pretty well populated and I don't want to ask on every single thread out there.
List what you use and if they are working, also maybe which launcher you are using
well on my ROM they do
Spuffyffet said:
well on my ROM they do
Click to expand...
Click to collapse
Which one are you using?
I think every AOSP ROMs do have working gestures. For MIUI ones I think it should be working too, it depends.
jadephyre said:
Which one are you using?
Click to expand...
Click to collapse
Pixel Extended 4.1 (Android 12)
Gestures work in any custom ROM, doesn't matter if it is Android 11 or 12.
You need to install a third party gesture app of your choice form google store, then hide navigation buttons using Magisk Manager. Look for "HideNavBar" module and install that.
That's all, enjoy