Search results

The "phone is starting" issue has been plaguing LineageOS specifically for quite some time now if you use Magisk. On 17.1 there was a chance you could get stuck in a "phone is starting" loop and all you could do was hard reboot the phone and hope it works next time. Apparently it has something...

You need to format data again either in TWRP or via fastboot

And of course it's an anime picture :D

1) can't say anything since I'm still on Android 10 2) use NikGapps.. personally I don't use Gapps but I heard NikGapps supports Android 11 3) latest blu_spark TWRP works fine *Privacy Guard: this has been completely dropped by the LOS team as the revamped permission system since Android 10...

You can take logs with it

By first reading the documentation

It clearly says "format storage" in the instructions

And what does that have to do with custom ROMs on the OP5/t?

Fingerprint is fixed in ArrowOS according to reports, so you might want to take a look there (can't confirm since I'm still on 10 and will be for quite some time)

Vanced MicroG has nothing to do with the original MicroG and will work on any ROM

Bacon is the codename of the OnePlus One, that's why I was wondering. There is no other way with FDE devices other than removing the PIN/password/pattern before flashing a new ROM or doing a Nandroid backup. The zip you linked can be sideloaded, but it will not change anything on newer devices...

Builds are only available for devices that are officially supported by LineageOS

It will not work on devices with FBE. The bacon he mentioned is an old device that still used FDE.

- stop using battery sucking apps such as Facebook, Instagram, TikTok or Snapchat (also better for your mental health) - reduce brightness to the lowest possible for you to be able to see - stop playing games all day - switch to 2G when connected to WiFi - replace your battery. It's a 3 year old...

Performance and battery life are as good as they get on this device, of course it all heavily depends on your apps, signal strength and screen brightness and stuff. It does suffer from the infinite call bug where you can't hang up calls and need to force a reboot. (This was a few weeks ago when...

You're better off just using gapps. You also might wanna try using some proper punctuation.

Nice copypasta

this build reboots to recovery when I reboot after flashing EDIT: my mistake, I formatted data and flashed a ROM that doesn't force encrypt. Formatted again, flashed LOS and everything is fine now.

You can install the microg apk as a user app and it will work

How about you get used to not using Google Services at all? No GMS, no issues. Just flash the ROM and nothing else

Slaverynet has been broken for a while now on MicroG. I suggest you ditch apps that depend on it and stop worrying or use stock ROM on a locked bootloader

They won't be working for long once hardware attestation becomes a thing

Nobody cares about safetynet. If you want it to work properly, use stock ROM on a locked bootloader.

Thank you!!

Nothing to do with any of that.

The issues section of the ND documentation has now been updated to include this issue: https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/Issues.md#play-store

Nobody knows why this happens, I guess you will just have to live with it until it (unexplainably) starts to work.

Wait a day or two and it will work

No

You fell for the VPN meme

Weird but at least it works now

Sounds like a hardware defect

Wow I never realized that the 10 Version is still in active development. That's great to see! I thought it was dead since the thread became quiet and died down.

If you had read the documentation before asking, you would know

Whenever the proximity sensor is covered and the screen is switched off while listening to audio notes or making calls, the volume can't be adjusted, it changes the media volume instead of the call volume, having no effect on the volume through the earpiece. The (tedious) workaround is to go...

If you follow the guide for non-root version you will not have problems. Vanced works fine without Google Services, even notifications work. It must be something you are missing or doing wrong

Phones used to do this back in the day, I always wondered why "smartphones" didn't do this until recently

GPS has absolutely nothing to do with Play Services.

>barebones AOSP >includes Gapps Ok

Why would you install an app through the zip if you already have it? This makes no sense

It is working :confused: And it's easier than ever to configure it

Just a guess, but are you using the cable that came with the phone or a 3rd party one? 3rd party ones usually work fine, but there are some that have no data wire inside that can only be used for charging, so they will not be detected.

It didn't survive a dirty flash for me. After I flashed everything again, I had to set up everything again and uninstall/reinstall apps with GCM. Might be a ROM problem, but after dirty flashing an update, I couldn't find MicroG settings anymore and Play Store kept force closing.

This is a bug in the app and not ROM dependent

It does nothing if you don't have a corresponding app installed. It's how the API is designed

And you effectively just utterly destroyed your device security. Stop depending on safetynet instead of finding hacky and insecure ways to make it pass. If you want safetynet to pass, use stock ROM with locked bootloader.

Have you tried running npem as root in a terminal?

Cheeseburger

Does it work fine for you?

You are essentially ruining your device security and stability just to get rid of a message that literally takes one tap to remove?