Hello everyone! I've been using AEX 5.7 Oreo rom until now with no problems so far, I consider it the best Oreo for my X720. But recently I decided to test some Pie roms just out of curiosity, to see the development status, and in all of them (AEX 6.2, AICP 14, Lineage 16...) I found a nasty reiterative bug when I activate lockscreen pincode, doesn't matter if fingerprint is also active or not: after several reboots I'm not able to enter the system until I delete "locksettings.db". It seems that my pin code is correctly recognized, but after a black screen I get stuck in lockscreen again and again forever.
I've search the web for a fix and I haven't found any information related, it's so frustrating. Am I the only one in the planet with this problem???
I have same problem with aicp
By the way, I finally managed to solve this anoyance, a wheather widget that I used to use was to blame. There are lots of these available, so I simply got rid of it.
Same here (LineageOs 16, AOSIP Pie)
Related
Greetings. I've been trying to update my phone from SlimROM 6 to SlimROM 7, but after each install, I've noticed that the Tethering & Portable Hotspot feature is grayed out in the Settings menu (see attachment). The lack of this feature is a pretty big dealbreaker for me at the moment, so I've been staying back on Slim6 for awhile.
Initially, I thought the issue was with the ROM (SlimROM 7 beta 0.8 and below), but when other users reported they were having no issue with the feature, I started experimenting. I've tried multiple other 7.1.1 ROMs at this point, and the only one that allows me to access and use portable hotspots was OOS 3.5.6. Here are the steps I've tried so far to fix this:
Verify latest TWRP and try again
Install OOS 3.5.6 to ensure latest modem, then install Slim 7
Install Slim6 (with working hotspot), then dirty flash up to Slim7
Test LineageOS, AICP, XOS, and a few others (ROMs only, no GApps or anything else) to see if Slim7 was the issue
Bring phone completely back to stock, install OOS 2.2.0 and update to current, then reinstall TWRP and flash another ROM
None of these have provided any success, and at this point I've pretty much exhausted my knowledge base. Does anyone know what might be causing this, or have any other suggestions I might try?
I'm having the same issue, and it's really frustrating.
I'm on Resurrection Remix 5.8.0, running 7.1.1
Someone please find a solution!
avigloz said:
I'm having the same issue, and it's really frustrating.
I'm on Resurrection Remix 5.8.0, running 7.1.1
Someone please find a solution!
Click to expand...
Click to collapse
You will be happy to hear that, after an absurd amount of trial and error, I determined that the issue was with my carrier's provisioning, not my ROM or phone. Once I had that to go on, a bit of Googling found this excellent article, which details how to get tethering running again. I tried this yesterday evening, and it worked wonderfully. Not sure why my carrier has seen fit to disable tethering when I upgrade to 7.1.1, but this is a pretty straightforward workaround.
The only issue I've found with it so far, though, is that it reverts on new ROM flashes. I'm exploring creating a simple Magisk package as a more permanent fix, but this will at least get you going.
Ssayerr said:
You will be happy to hear that, after an absurd amount of trial and error, I determined that the issue was with my carrier's provisioning, not my ROM or phone. Once I had that to go on, a bit of Googling found this excellent article, which details how to get tethering running again. I tried this yesterday evening, and it worked wonderfully. Not sure why my carrier has seen fit to disable tethering when I upgrade to 7.1.1, but this is a pretty straightforward workaround.
The only issue I've found with it so far, though, is that it reverts on new ROM flashes. I'm exploring creating a simple Magisk package as a more permanent fix, but this will at least get you going.
Click to expand...
Click to collapse
Cheers man
Thanks so much.
I've been dragging my feet on upgrading from my old Galaxy S4 with CM12, and finally this weekend freshly installed TWRP and LineageOS 14.1 on an SM-900T.
On my old S4 with CM12, I could have a complex password for device boot, then a PIN for unlocking the screen lock. This seems like a very logical and convenient security configuration.
However, after enough googling, I'm finding that this feature is not present in LineageOS 14.1.
What I'm not clear on is whether or not this feature was something from original Android carried into CM, then deprecated, or if it was something that the CM team implemented, but Lineage has not.
(Please do not read this question as a "Is Lineage going to add feature X" question - I'm seeking clarification on where the feature comes from.)
To resolve this issue, I ended up using cryptfs password.
You're a power user. Can the Xiaomi Mi Mix 2 keep up? Rate this thread to express how "healthy" the development scene is for the Xiaomi Mi Mix 2. A higher rating indicates available root methods, kernels, and custom ROMs.
Then, drop a comment if you have anything to add!
The phone is excellent. One of the best designs I've ever seen on a phone. However battery life is okay for a power user like myself. Really hoping lineage OS or anything AOSP launches for better battery optimization.
I having it for one week and i love it already... 6.4" would have been nice to have, but it's awesome nevertheless.
At the moment i'm trying to build los15 from source for it, but the proprietary blobs are an issue i haven't figured out yet. If anyone has some pointers how to get them, i'd be three commands closer achieving it.
Happy Hunting.
Xiaomi phones usually have a rich custom ROM community as they are bootloader unlockable and they usually get the kernel and sources released in some months after launch. We already have alpha-ish ports of Mokee, ResurrectionRemix and Lineage for Mix2 and right now the ultrasonic proximity sensor and notification lights are the only major broken features which require some code from the kernel/source.
MIUI 9 - Epic ROM or the EU rom is not a bad first ROM to rock around until development catches up.
subashchandran said:
Xiaomi phones usually have a rich custom ROM community as they are bootloader unlockable and they usually get the kernel and sources released in some months after launch. We already have alpha-ish ports of Mokee, ResurrectionRemix and Lineage for Mix2 and right now the ultrasonic proximity sensor and notification lights are the only major broken features which require some code from the kernel/source.
MIUI 9 - Epic ROM or the EU rom is not a bad first ROM to rock around until development catches up.
Click to expand...
Click to collapse
Hi,
Sorry, but what you are writing is not perfectly accurate.
All the Custom ROMs (and not the MIUI derivatives like EPIC, Xiaomi.eu, mi-Globe, MultiROM or miuiPro) have a major problem and that is : they are assigning a random MAC Address to the device for Wi-Fi. Whci basically means that, if you're connecting to a secured router that identifies your device with it's MAC address, you won't have permissions to connect to that router...
Another thing that should be mentioned is that, except Mokee, the other customs ROMs also have a major problem : Bluetooth Audio is not working. We're digging into that problem to try to solve it (and it seems it is indeed solved in my latest own build of AquariOS that I will not publish until the MAC address problem isn't solved)... But that is quite a problem.
And mind you, but saying that the proximity sensor is the only thing not working and selling it as a "minor" problem... Well, on a tablet, maybe. But on a phone ? Unless, of course, you like your phone to hang up on your speaking partner because you accidentally pressed a button as the display didn't dim while you were in a conversation.
But I hope those problems will indeed soon be solved thanks to kernel sources being published by Xiaomi.
So far, I am running mi-Globe (7.11.9 at the moment) and it's quite a good ROM... I've hidden MIUI under a custom launcher and installed XPosed and Xposed Edge to be able to configure my fingerprint scanner as a home button (+2 other actions configured for the FP Scanner). Perfectly happy with it so far...
NexusPenguin said:
So far, I am running mi-Globe (7.11.9 at the moment) and it's quite a good ROM... I've hidden MIUI under a custom launcher and installed XPosed and Xposed Edge to be able to configure my fingerprint scanner as a home button (+2 other actions configured for the FP Scanner). Perfectly happy with it so far...
Click to expand...
Click to collapse
Xposed works for you on miui? Is mi-globe MIUI 8 or 9?
itsdan313 said:
Xposed works for you on miui? Is mi-globe MIUI 8 or 9?
Click to expand...
Click to collapse
Hi,
Yes, it works.
mi-Globe is MIUI 9 based on 7.9.11 China and 7.1.1 Android.
To use XPosed there's a simple trick. Jus follow these steps :
- 1°) download and install the "Xposed_installer" APK (latest is 3.1.2 I think) ;
- 2°) once it is installed, open it, go to "Settings" and check the "Disable resource hook" box ;
- 3°) reboot your phone to recovery and into recovery install the Xposed API 25 ;
- 4°) reboot your phone... launch XPosed Installer... Ta-Da... There you go
Works with SuperSU and with Magisk (if you take the correct sources for both of course !).
Regards.
Hello everyone,
Sorry if this is obvious or a known bug but i've searched through a dozen of AOSP threads and found nothing satisfying.
So here's the story :
- I have clean flashed LineageOS 14.1 official 20180110 a week ago but i have those distorted voices when called over any bluetooth device (tried car and BT Speaker). On their thread someone says that it actually has been fixed in 20180103 build but the problem is still present though we're already one build ahead since then.
- Anyway, I decided to change my rom and try out AOKP. I clean flashed it today. Working fine, except for that exact same bug.
- Tried AOSPExtended, same thing.
So do all AOSP roms have this bug? I can't believe it since apart from 1 or 2 posts in Lineage's thread nobody seems to care in any AOSP rom.
If (and i hope so) the answer is no : could a kind soul show me some good AOSP rom without this problem?
Thanks for caring
Same for me on Galaxy S7 (herolte G930F).
Tried newest LineageOS and AOKP - directly after setup. No other changes made. Music over bluetooth works as expected. Phone calls imposible.
I found a Video here which shows exactly what happens:
Google: "s7 edge lineageos bluetooth Youtube":
https://www.youtube.com/watch?v=utDsXrCY5N0
Also some other People seem to have the same problems. See other thread (Post #1999):
https://forum.xda-developers.com/ga...ial-lineageos-14-1-galaxy-s7-t3529197/page200
Thanks for the infos !
I didn't see the post 1999 is LOS thread, seems like the build.prop is a good fix but unfortunately it doesn't work on latest LOS build.
Will try on AOSPExtended with the same editing on audio_hal property.
EDIT : Works on AOSPExtended ! Didn't try AOKP yet
Hi can you please explain how did you fix this ? happen exactly the same for me, thanx
Apologies for cryptic title. My Mi A1 has multiple issues and a patchy update history. I don't know how to narrow this down to a single, simple question. Hope someone can help to make sense of this.
History: Bought new with stock Android One, Oreo. Few months later updated to Android One, Pie (official update). This caused big problems with wifi (connections constantly dropped and VERY slow downloads). Thought about reverting to Oreo, but decided to change to Lineage (which at the time was Oreo). So I downgraded from Android One Pie to Lineage 15 (Oreo). Generally worked OK, but with 3 big problems:
1. No sound during phone calls (I can't hear them, they can't hear me). Found a workaround involving editing the build.prop file (sorry, can't post link), but fix is temporary and needs regular re-boots.
2. Fingerprint sensor not working (no options to set fingerprint).
3. Camera app lost functionality related to dual lens.
I subsequently updated from LOS 15 (Oreo) to LOS 16 (Pie). Issues still there.
I wonder if I have some missing/incompatible vendor firmware components, but I don't really understand how this works. If I download and install, say, a LOS rom, does it contain EVERYTHING my phone needs to work, or do I need to already have some proprietary bits somewhere on the phone?
Is my best bet to start afresh (clean slate) and if so what would you recommend? Any help/insight greatly appreciated!
Hey pal, the Android Pie Firmware has some kind of anti-roll back protection, so when you install a non-pie ROM such as LOS 15 using Pie Firmware you'll have that problems like no-fingerprint, no incall audio, etc. If you install an Oreo Firmware with an Oreo ROM, you'll have fingerprint but no IMEI/Signal (and other problems).
You have 2 options:
1) Update your firmware to the latest Pie version and install a ROM like Pixel Experience or HavocOS (both Pie) and you're set, IMEI, Signal, Audio and Fingerprints will be working OK.
2) Install the latest Pie compilation using MiFlash and leave it stock.
Greetings.
Thanks for prompt reply! Can you spell something out for me please?
Regarding 1) I have already updated to LOS 16, which is Pie. Is that what you meant by "update your firmware to the latest pie"? Or do you mean a stock firmware? If the latter, then I could find a MIUI rom (from en.miui.com) but not Android One.
Regarding 2) Again, by "latest Pie compilation" do you mean the stock rom, like the MIUI mentioned above?
Thanks