Search results

Updated Marble to 1.0.12 yesterday and noticed that long press on navigation buttons no longer functions. (Was working on 1.0.9) Only tested them due to receiving a message in the Google app to inform that circle to search was finally available. Is this a likely issue with the launcher we use...

addon.d support would enable the automation of patching the boot image after a dirty flash but I haven't seen this raised, (and just as quickly dismissed), here for a few years.

Didn't experience call drops on A13 myself so was only casually following the reported issues. (My device is a Poco F5 Global) Best to wait for feedback from those who were impacted.

Thought you guys may be looking for some early feedback from Marble users, so can confirm that updating to HyperOS on model 23049PCD8G is up and running. Manual download from sourceforge, package selected through the updater app, installed via open script recovery within OrangeFox. Appreciate...

Yeah it's strange that a mature solution like Magisk is getting hate from some people. I mean it still works perfectly when setup correctly.

Correct. But you probably already know this by now. (Apologies for the late reply).

A rom based solution is being implemented at the moment anyway. So installing the new build for your device, (once available), will mean you won't have to play around with Magisk.

Because you don't need, or want, to.

The Mi Flash tool provides the method for reverting from a custom rom to the stock rom as well.

Yeah. I just replaced my battery last week after experiencing the same. Wanted to blame software because it started happening after upgrading to miui 13.x a couple of months back, (and continued on 14.x), but the new battery has been good so far. My device was a May 2020 batch so pretty much 3...

This isn't a forum for the "official" rom as you appear to be trying to upgrade. This forum is for a modified version of the official rom which has a few improvements and benefits, but also makes it difficult to help you as they're not natively interchangeable. If I were in your shoes, I'd be...

As long as you flash the right rom, you shouldn't have any issues.

Thanks for the update.

The test that I would do though, (and I may because I haven't upgraded yet), would be to check the behaviour of OrangeFox after a clean install, (via the fastboot rom), using the update.bat.

Yeah I get the upgrading part. But if you use the install.bat from the fastboot rom, it's a clean install as opposed to an upgrade. So no issue of soft bricking there. The upgrade process would be no different to switching to one of our other custom ROMs that already utilise fbev2. But I'm...

Yeah the issue is clear but the fix is not so clear. At least it sounds like all the functionality is there though. I've been resisting the upgrade for not wanting to run into little issues like this one. Do you know if the fastboot rom, (using install rather than update), uses fbev1 or fbev2...

I see. I haven't updated to A12 yet, but doesn't it use fbev2?

What's the full error msg form Orangefox? I had this a long time back but it was for user 99, (I think), which is what miui uses for second space.

Exactly what I wanted to hear. Thank you.

The .bat file does a format though like previous fastboot files right? I suspect this one will need to as well in order to update to fbev2, so was wondering if there's any strong reason to update.