Yep. I dont care about the data on my phone enough to try dirty flashing android 11 roms, so I back up configs and pull apps needed, clean flash (removing all user data partitions) and restoring after testing clean build.
Yep. I dont care about the data on my phone enough to try dirty flashing android 11 roms, so I back up configs and pull apps needed, clean flash (removing all user data partitions) and restoring after testing clean build.
Thanks for your feedback.So, im checking the rom out and I must say its super slick. I have found that everything works, except for double tap to wake. Ive tried rebooting, toggling multiple times, etc and nothing seems to work.
Update**
-Also, there is no option to auto unlock on correct pin
-Im on 14.4 but system update available notification still shows on every reboot
-Raise to pulse notifications is hit or miss
-Just got booted into recovery randomly after 3rd reboot like others reported.
-Status Bar hide battery doesnt hide battery or give option to only show percentage (happened on DotOS for me as well, not sure if its an android 11 specific bug)
Still, a great rom, FAR more stable than most other android 11 roms ive tried and even alot of the android 10 roms lol
This will be fixed in the next releaseStatus Bar hide battery doesnt hide battery or give option to only show percentage (happened on DotOS for me as well, not sure if its an android 11 specific bug)
The developers are aware of this and are working on fixing it.Im on 14.4 but system update available notification still shows on every reboot
Some users question if it has something to do with the latest official twrp. I'm still using the old twrp and haven't experienced this yet.Just got booted into recovery randomly after 3rd reboot like others reported.
Thanks for your feedback.
This will be fixed in the next release
The developers are aware of this and are working on fixing it.
Some users question if it has something to do with the latest official twrp. I'm still using the old twrp and haven't experienced this yet.
Thanks for your feedback.
This will be fixed in the next release
The developers are aware of this and are working on fixing it.
Some users question if it has something to do with the latest official twrp. I'm still using the old twrp and haven't experienced this yet.
Darn! Sorry I missed that. Things changed in the sources. I will bring it back on my next build.With the 14.5 update i no longer have access to the smart charging settings. It shows up when searching for it but when you go to where the setting search points it isn't there.
all good, it happens :3 also the battery icon when set to text is intermittently not showing up. probably some more source change weirdness. Otherwise stable and solidDarn! Sorry I missed that. Things changed in the sources. I will bring it back on my next build.
this is fixed in july build 14.5
I still have this problem, even with that build.
i had clean flashed 14.5 and I didnt face any issue so far (previous build i too had that)
Did that, even using the current version of TWRP and still the same issuei had clean flashed 14.5 and I didnt face any issue so far (previous build i too had that)
donno dude i guess none facing this issue after 14.5 wait a week for 14.6 and check once, is this the case in other roms too for uDid that, even using the current version of TWRP and still the same issue
It's clearly still there, that problemdonno dude i guess none facing this issue after 14.5 wait a week for 14.6 and check once, is this the case in other roms too for u
- Make sure you're on the latest OOS 10 firmware
- Install latest TWRP
- Flash BlissROM
- Flash TWRP
- WIPE DATA
- Reboot to TWRP
- Reboot to System and #StayBlissful
- If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you and our team quite some time.
- Download the Matlog app from the Play Store.
- Clear all previous logs and take the exact steps to produce the error you are receiving.
- As soon as you receive the error (probably a force close), go straight into Matlog and stop the log recording.
- Copy and paste the entire log either to Dogbin
- Save the log, and copy and paste the link into the forum with a brief description of the error.
[COLOR=DeepSkyBlue][B]
@Jackeagle
@electrikjesus
@Rohanpurohit
@rwaterspf1
@ideaman924
@Makaveli_da_dev
@ElfinJNoty
@BitOBSessiOn
@customworx
@nilac
@sixohtew
@aclegg2011
@Roger.T
@T.M.Wrath
@kanttii
@rev3nt3ch
@techfreak243
@SuperDroidBond
@USA_RedDragon
@bcrichster
@deadmanxXD
@krittin98
@BlackScorpion
@techexhibeo
@droidbot
@siphonay
@pacer456
@nitin1438
@theGeekyLad
@kunalshah912
@lordarcadius
@AryanAA
[/B]
[/COLOR]