Search results

That's an odd issue for sure. My only idea would be installing TWRP and maybe formatting from there and using fix permissions etc. to see if it has any effect.

Sounds like you're straight out of luck to recover any data if your device is completely stock, as to unlock your bootloader to access encrypted data would mean a factory reset. You could try try one of the unbrick tools using the guide here. You will lose your data.

I'd have to disagree with you there. Telegram has push notifications, vastly superior search functions, helpful bots which provide up-to-date information, doesn't take 5 seconds to load every page and have a much more active community. Is there a group for this device on TG? If so where could I...

Seems to be a bug at the moment with screen recording, casting and output to external devices (like android auto).

Also having issues here with Android Auto, dirty flashed over mid-august build.

Why do you want to OTA? You can follow the guide in the official thread here for a rooted device. From memory, the dirty flash also restores the stock recovery.

Why have you reposted a reddit thread here? Are you facing the exact same issue?

Backup your data (TWRP, Swift Backup, however you like) Boot into TWRP, format device, reboot into TWRP Flash latest OOS firmware (Hotfix 1 at this time) if you weren't already on it Flash ROM (Gapps are included unless you download the non-Gapps version) Flash Magisk if you want to pass...

I'm unable to reproduce this bug on dumpling. What's your Bluetooth device?

Nope, everything working well so far.

If you joined the telegram group like I suggested you could find out for yourself. Nikita also has his own GCam channel for updates and discussion. Snapcam for OOS, GCam for custom ROMs (although snapcam can also work on custom ROMs that have the right libs). They have the same functions.

You could check your battery health with accubattery or OnePlus diagnostic APK. If it is around or below 80% you could buy a new battery and replace it, it is quite easy. Software based solutions will not have a significant impact. Don't bother with undervolting, but underclocking is an...

Aux-Mod-2.1-Signed.zip magisk module by shadowstep (here on XDA). https://t.me/gcamOneplus/292061. That telegram is very helpful if you have any issues, and the bot there has all the information you need.

Flash latest Hotfix firmware first.

Nik v1.1 is working great for me. Although I did have to install Magisk + DotFix 5.6 (on dumpling) to get the main lens working.

Cheers for the update, everything working smoothly. What's the situation with the inline dotfix? It doesn't seem compatible with Nikita GCam, I have to install the magisk module to get the viewfinder working (it's black otherwise).

How did you flash the ROM and what were you using before? I'm using blu_spark TWRP 3.4 v9.115 and it's fine.

Works awesome so far! Cheers guys. Only bug I've noticed is that when turning off the +/- buttons for the brightness slider in quick settings, the panel updates and resizes to having the +/- again during while using the slider.

Did you maybe accidentally deny it microphone permissions somehow? Check the Google app's permissions in your device's settings.

Plenty of ROM support and easy methodology to tamper, if you aren't a fan of OOS which is quite good anyway. Updates are still being released quite frequently through the beta. Bought mine on release, coming up on 2 years ago now. Only complaints I have hardware wise: -charging port can...

If you want the smallest Google footprint possible then you can use MicroG instead of Gapps. There is even a LineageOS weekly build that comes with it preinstalled https://download.lineage.microg.org/dumpling/

Light percussive maintenance as previously suggested. If the button or internals aren't bent/broken you could also try getting a clean toothbrush's bristles in there. My volume buttons become quite stiff every now and then but they usually end up just fixing themselves through normal use anyway.

My USB A/C Sandisk is formatted as exFat and detected fine in codeworkx's latest TWRP. You deleting the System partition should not affect your device's ability to detect a USB. Just load OOS/your ROM onto your USB, press "Mount" on the TWRP main menu, press "Select Storage" then "USB Storage"...

If you were serious about protection you would be using a PIN. It is not possible to have that functionality with the pattern unlock on this ROM without some sort of external mod.

Have you tried a different firmware yet? Sounds firmware related - need the right firmware for the right ROM. OmniRom has that in the OP. Also just did some quick research on MicroG and found https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928 if magisk is...

?? no, try an OMS enabled ROM and use substratum to theme a ROM.

It's in the magisk app...

LCD burn-in? You need to use your phone less :P On a serious note: there are apps you can try to correct i believe. Also you could buy and install a new screen if you can't live with it.

Settings > SIM Cards > SIM 1 (or 2) > Toggle 'Enhanced 4G LTE Mode'

Issue sounds hardware related to the earphones. Do you have a case on your phone? Is the 3.5mm jack bent a bit by any chance? Maybe some pocket lint in the 3.5mm port? If all you've done software wise is updated MIUI it's highly likely it isn't going to do anything, you'd have to factory reset too.

Personally I can recommend NitrogenOS. It's what I settled on while all the ROMs were migrating to Nougat and NOS has just been rock solid for me. It seems to be one of the more popular ROMs on the Kenzo/Kate XDA too. With the latest MIUI Global Stable firmware Bluetooth is flawless for my...

AOSP Extended works fine for me. You could try giving your phone a full wipe (wipe /system /data /cache /dalvik and then format your internal storage) and then installing the latest MIUI ROM, let it boot the first time then do the standard wiping and try AEX again. However I do have to agree...

Just checking in to say thanks for the awesome ROM again xyyx! Was on a March build and updated to the latest test and my phone is nice and smooth again! For others that have issues with crashing apps: I encountered an issue where most apps would crash upon launch after installing Gapps and...

Just a quick review: wiped, flashed latest MIUI Dev, booted, wiped, flashed the 31/03/17 build with unroot ZIP, booted, flashed Magisk. I am now have passing safety net with play store and play services enabled in Magisk hide and have systemless V4A, plus Bluetooth connectivity in my car now...

Flash the xiaomi.eu ROM in TWRP? I have no issues with it on my phone.

Sounds very similar to what happened to me and it was because the bootloader somehow locked itself again. I just plugged it back into my computer and unlocked it again.

Install a kernel that supports it or find nicknitewolf's patch to fix it. Simple as that.

Radon Kernel.

V4A has always been chinese-owned...

Well that makes sense then... sorry I'm not experienced with mobile network issues - have to leave that up to someone else.

Have you tried to unlock bootloader? Perhaps install TWRP and do a system/dalvik/cache wipe and install MIUI through that?

Did you take backups in TWRP of every partition?

As above, flash the latest Radon Kernel. Also do not use the old snapshots of CM13 (they are now months old), nightlies are more stable and much more updated.

Did you install the CM firmware? Also that's a very old build of that ROM is it not?

Snapshots for this device are extremely old. DO NOT USE THEM. Use the latest updates. Same goes for you OP. Make sure you have firmware installed before flashing CM13.

Duplicate.

Oh okay, your OP was a bit confusing. Well since it is definitely the main board then I honestly don't know for sure, probably something to do with heat and I am no hardware expert. Moral of the story: don't use QC on a device that doesn't officially support it just because it's chipset does.

I second this.

Happened to me too after wiping one of the partitions I shouldn't have when reinstalling CM. I just re-unlocked using the Mi Unlock program on Windows and then flashed CM13 back. Booted perfectly.

Works for me with my Google Chromecast 2. I'm on 2016/09/23 nightly.