Search results

What I'm saying isn't android 11 specific, but counts for every instance in which a new android release comes out. It has been the same with android 6 and 7, then with 7 and 8 and so on. Android 11 might bring functionality, stability and smoothness. But it is too early in development to expect...

Well, in the first phase of a new android release all ROMs - Are basically the same (pure aosp with different branding) - Have no additional features to pure aosp - Will have many issues to sort out in general and for the respective device (like bugs, fast draining, random reboots...

is your bootloader unlocked? If so, have you tried booting latest twrp image from fastboot? fastboot boot twrp.img Sounds like you may at least have to try to wipe and format your phone at the cost of all data. But then you could use the situation to install a good custom ROM..

If you need a stable daily driver, I can only advise you to stay on Android 10 until 11 gets out of alpha phase. Slowly features will come to 11, of which you for now will probably miss one or another in comparison to your Android 10 ROM also. Switching to a ROM in such an early stage isn't...

With R Roms magisk canary is recommended at the moment

If you can reproduce it, grab logs and send them here, so OP has a chance to fix this, if it even is ROM related

Yes, most probably. You will often see that when a new android version comes out, releases slow down for a while. When everything is ready for 11, frequency usually increases again (although ofc I cannot speak for the OP - I'm just guessing).

For me ota updates never worked well on this device. I would recommend either a clean flash ofc, but otherwise I ran fine so far with a semi-clean variant: - Wipe dalvik, cache, system, vendor (and boot partition if present) in active slot, - Reboot to inactive one to flash the ROM. - Reboot...

The slot thing (start in a go to b or vice versa) doesn't matter at all. Your previous proposition that slots are supposed to be declined as their opposite is simply wrong. A ROM is always being flashed into the opposite slot is all you need to know and why you need to change slots after...

Sorry for the late reply. Kindly check your private messages. Please tell us whether this newer firmware I sent you solves your issue.

Firmware maybe

Might be, yey You could also perform a "semi-clean-flash" (= wiping dalvik, cache, system, vendor in both slots before flashing and leaving data and internal storage untouched - remember, you'll need to install gapps and magik in opposite slot, too). Maybe this will do as well.

Clean flash if you don't use any mods messing with deep sleep, or remove anything alike if you do (like xposed, greenify, etc). Also make sure your phone is updated in all other ways (firmware, twrp, magisk, ...).

Check your private messages

Are you using telegram?

Yeah, this is so quietly lying around in here somewhere, and just is the most perfect thing for our device. Rock stable, fast, smooth, incredible battery, feature-rich. And very frequent updates (unannounced). I was totally surprised as I realized that this project wasn't abandoned whatsoever!

Latest version (20.4 at the moment) always worked for me with this ROM. Did you clean flash? Do you use latest firmware and latest twrp?

You probably got no answer, because you don't describe enough. Nobody can solve an issue without knowing anything. So, tell us your installation method, which firmware, mods etc you use and so forth. Then maybe someone can think of something.

As far as I know, official lineage builds where always weeklies. Which is very frequently btw. Monthly is actually a good frequency for most to fix some things and include latest security patches and so forth. With nightlies you'll get many builds in which close to nothing has changed, which is...

You did check under "Settings", did you?

Idle and display off task battery life is unreal!

For me this did actually work, thanks! I deinstalled amazon, did your stuff, and reinstalled it after the reboot. Maybe that did the trick?

+1. The ROM is very very smooth and a lot of fun to use. I'm also experiencing the screen flickering from time to time though (latest fw). Thanks for shipping this ROM to the A2! I'm excited about what new updates will bring. Nice work!

If you wipe internal storage anyway, you can try formatting data (where you need to approve with "yes"). Do this in addition to all other wipes (also caches and vendor!) under the advanced menu in both slots, then reboot to recovery and try again. On this phone I already had the situation a...

Thanks a lot for the informative answer! A lot I missed actually : ) But indeed, it seems like all of the downsides seem acceptable to me, and I think I cannot help myself from testing on the Mi A2 to see what it does to battery life. I'll report back my experiences in a few days.

Hi, is it correct that current Q Go package content reflects the omni version? And are there experiences or expectations towards downsides the Go versions can bring? For what I've read so far, they just seem like a win for every phone, but I don't know whether I'm missing something.

The higher refresh rate should result in smoother transitions and maybe a little less potential stuttering during game play or similar tasks with more frequent frame updates. You will not be able to see any changes to still images. Also the increase is not that high, so this probably is a...

Very light usage, but still look at that drain!

I can recommend UltraCam by UltraM8. If you wanna try it, don't forget to load the Mi 9 SE config (you can see the configs link next to the download link with the cam's version number).

For the third party app video call issues: Just flash B - B-Kernel-N-[2019-10-18]-[14_11]-Mi5 from kernel_only folder under OP's download section for now. I will try to provide an upstreamed kernel having this issue solved with the next ROM release.

That's strange since others downloaded and tested already, so there should not be a problem with the upload... Have you tried downloading from your pc and then copying it over to the phone?

Hi, is kangmeng the default kernel in this ROM?

As always with these issues: Do you use the latest fastboot and adb version from sdk or some others like "minimal"? Make sure you got the sdk version and execute all commands as root (linux) or admin (windows).

Thanks, that's really helpful! I'll investigate

From which ROM version on do you experience the problem? Was is there in the previous build already? And did you clean or dirty flash?

Did you clean flash? Maybe also uninstalling and reinstalling WhatsApp might help, but don't know. Any confirmation of this by someone else? (I don't even use the Mi 5 anymore since a while)

I highly doubt someone is going to take responsibility for your choice to either believe it's secure enough or not.

So here we are yet again, to continue keeping the deprecation going on. Lineage indeed has released a Nougat security patch this month. So, if this keeps happening, you might just get more updates. One from today is uploaded 20.03.2020 March 2020 security updates from LineageOS Synced...

Haha, maybe, yeah

Usually you can solve something like this by a) Using the fastboot and adb versions from sdk (no "minimal" or alike) b) Executing fastboot as root (linux) or opening cmd as admin (Windows) c) In case fastboot works, but you still can't get your system fixed: fastboot -w Which will wipe your...

About a/b and so forth: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375

Use the .img files with fastboot only to boot into recovery. Then use the .zip recovery file from within the booted recovery to flash permanent twrp, after the ROM installation.

I use the_dise - working perfectly on derpfest

Hey, yes, I deleted everything I implemented from the list, so what's still on it (and not under 'done') is not implemented.

My gf bought the Mi 9 SE (as a Mi 5 replacer) and it is actually the only new(ish-er) phone that is still comparably compact, but still not quite like the Mi 5, because our phone is also that unbelievably slim. I would still advise you to check out the 9 SE if you wanna buy a new phone in Mi 5...

Clean, clear and nice set of features. Really like this one, thanks! Hm, but I really do miss the option to wipe vendor. Not possible, also not after mounting.

Flash it in the active slot, at any time before installing the ROM (as the ROM is checking for a minimum fw version it requires and fails to install if it is not present). It also doesn't get wiped btw. There's a separate hidden fw partition not affected by anything you do, except flashing...

So true ;) Strangely satisfying this build success feeling, hehe.

Hey you guys, I couldn't leave it as it was - one more final update, but that's it. 2020-03-02: Security bulletins up to Februrary 2020 (no more source.android updates coming from here on) Updated everything in aosp.xml to latest android tag r39 Updated HALs and all externals under CAF to...

Latest developer firmware as stated in the original post is good in either case. So flash it if you are on a lower version, or leave it as is if not. Don't forget to format data though (type "yes" way), after saving your external storage content externally, in case you don't wanna lose it.