Yea thats y hotfix fw is implemented afaikThankfully, everything seems to be working with OK Google enabled.
Yea thats y hotfix fw is implemented afaikThankfully, everything seems to be working with OK Google enabled.
I'm kinda hitting in the dark here, but your flashing process looks solid. It must be the migrate.zip. I assume you're on the correct firmware. Try without flashing migrate.Hey guys, I clean flashed this ROM and i really like it, but I can't use it for more than 5-10 minutes without it randomly rebooting... I must have done something wrong in the flashing. I did a clean wipe, then ROM, migrate.zip, magisk, then no-verity. Maybe the migrate restore messed everything up? Any suggestions?
Hmm.... what kind of problems? I don't believe I've had any problems with blu_spark twrp 3.4 (v9.116).And make sure you're not on twrp 3.4. Many cause problems.
Sent from my OnePlus 5T using XDA Labs
I just started using it yesterday, it's looking good. Had an issue with 9.115.Hmm.... what kind of problems? I don't believe I've had any problems with blu_spark twrp 3.4 (v9.116).
What was the issue with 9.115? I have successfully backed up and restored so many times with it I lost count. However, I do run decrypted which may be the reason for my success.I just started using it yesterday, it's looking good. Had an issue with 9.115.
Sent from my OnePlus 5T using XDA Labs
Yeah, backup restore, some had flashing issues. Varied ones. 9116 is good.What was the issue with 9.115? I have successfully backed up and restored so many times with it I lost count. However, I do run decrypted which may be the reason for my success.
We never had this. Calls work with no issue what so everit already fix the call issue? like you need to reboot the phone to hear a sound from caller?
Most probably migrate. Maybe a magisk module. Please clean flash with no mods what so ever. This is not a technical support page. Please do your reading and flash correctly. If something is messed up and it's not because of us - It doesn't belong here.Hey guys, I clean flashed this ROM and i really like it, but I can't use it for more than 5-10 minutes without it randomly rebooting... I must have done something wrong in the flashing. I did a clean wipe, then ROM, migrate.zip, magisk, then no-verity. Maybe the migrate restore messed everything up? Any suggestions?
What does not go here (by far an uncomplete list, just some examples for topics that are not tolerated)
- Everything prohibited by above linked forum rules.
- The forum rules apply so that means no trolling/arguing etc. will be accepted.
- "What was your last phone/will be your next phone" (Off-Topic to this phone, post that in OT-Forum)
- "Hello"/"Goodbye"/"Merry Christmas,Easter,Hannukkah, whatever" (Obviously OT, just imagine every user posts that)
- "I'll never buy HTC again", "Why HTC/Samsung/whoever sucks" and all other "hate"-threads (Tell that those guys, not us)
- "Help!", "How do I...", "Why..." and all other Questions (belong in Q&A)
I also had a problem with twrp 3.4 two weeks ago (but I don't know which was the version). I dirty updated Derpfest, system went to recovery, I tried to restore backup (just made with same twrp), system went in fastboot mode. I had to install twrp 3.3 to restart the phone.. Maybe new version solved the problem. I'm decrypted too. Sorry if this is OT, just to advise.What was the issue with 9.115? I have successfully backed up and restored so many times with it I lost count. However, I do run decrypted which may be the reason for my success.
Yes, had a dirty flash issue installing last Derp update. Kept rebooting to twrp. I could usually reflash if I had that issue, but only thing that solved it for me was going back to 3.3.1. Backup and restore was fine on both.What was the issue with 9.115? I have successfully backed up and restored so many times with it I lost count. However, I do run decrypted which may be the reason for my success.
I also had a problem with twrp 3.4 two weeks ago (but I don't know which was the version). I dirty updated Derpfest, system went to recovery, I tried to restore backup (just made with same twrp), system went in fastboot mode. I had to install twrp 3.3 to restart the phone.. Maybe new version solved the problem. I'm decrypted too. Sorry if this is OT, just to advise.
I haven't encountered that update issue probably because I've been clean flashing a lot lately.Yes, had a dirty flash issue installing last Derp update. Kept rebooting to twrp. I could usually reflash if I had that issue, but only thing that solved it for me was going back to 3.3.1. Backup and restore was fine on both.
Ok, switched from Bare to Main, clean flash. Twrp 3.4 didn't work, had to go back to 3.3.1 to get it to boot to system. Kept saying to use a decrypted twrp, I was using latest BS. Other than that went well.I haven't encountered that update issue probably because I've been clean flashing a lot lately.
Okay, for VoWiFi/VoiP, if you face issues again, just delete the google video folder from Internal/Android, turn on Airplane and reboot. This should be a 1 time task, if and up until you face again, which should not be soon.Ok, switched from Bare to Main, clean flash. Twrp 3.4 didn't work, had to go back to 3.3.1 to get it to boot to system. Kept saying to use a decrypted twrp, I was using latest BS. Other than that went well.
First thing I noticed is I can't make a VOIP call on WiFi with airplane mode on (Google Voice). Works with airplane on Bare. I have no cell signal at home so I have airplane mode on all the time. May switch back to Bare because of this. Going to stay for 1 cycle. Love the QS icon options!
Edit: a reboot fixed the GV problem, so all good!
Likewise it does not have customisation. It is bare bone. But it is more stable.Am I right, this Rom does NOT have face unlock and navbar cusomization (long press and double press options)?
Turn off OK GOOGLE detection reboot and see if that fixes itThe issue with mic loss at random become annoying.
I'm going to restart my phone daily as a preventative measure.
What could help eradicate this?
I assume a logcat at time it apparently muted is already too late.