Yes, I'm using official LineageOS.
Could this be a kernel problem?
With Stock ROM Bluetooth is working fine.
[ROM][UNOFFICIAL][kane][11] LineageOS 18.1
- Thread starter Stricted
- Start date
Could this be a kernel problem?
With Stock ROM Bluetooth is working fine.
Well, if I had this phone, then I could test it out; it doesn't really appear to be a kernel problem. If it is confirmed to be an issue of custom ROM, maybe report it to maintainers of LineageOS for this device.
Can you help me, where I have to report it for maintainers of LineageOS for this device?
Is there a special site?
r/LineageOS
wiki.lineageos.org
Oh, and by the way, why can't you search for thing so simple like bug report? I'm using Linux (not Arch btw) and I asked for help with things only twice, rest of things I "googled" (quotation, because I'm not using Google) and fixed without any help.
How to submit a bug report | LineageOS Wiki
Oh, and by the way, why can't you search for thing so simple like bug report? I'm using Linux (not Arch btw) and I asked for help with things only twice, rest of things I "googled" (quotation, because I'm not using Google) and fixed without any help.
Sorry ... but simply because I didn't feel like it anymore (after all the fruitless search).
I switched back to the stock ROM yesterday after many days of unsuccessful experiments.
Bluetooth works fine on the stock ROM.
But thank you for your help ... and kindness.
I switched back to the stock ROM yesterday after many days of unsuccessful experiments.
Bluetooth works fine on the stock ROM.
But thank you for your help ... and kindness.
Please excuse the irony ... I couldn't help it ;-) ... You're right ... I was too lazy at that moment to search. :-(
Can moto p50 repair cell phone signal?hey, for everyone that have problems with that calls, here's way to fix this:
- download modem image from attachment below
- use dd or fastboot to flash this (dd: type in terminal emulator or adb shell [on phone] the following: su -c dd if=/path/to/modem.bin of=/dev/block/by-name/modem_a [just in case also flash modem_b], fastboot: fastboot flash modem_a [optionally modem_b] /path/to/modem.bin)
- reboot and enjoy normal calls
another workaround would be just updating to latest stock
modem.bin - AnonFiles
anonfiles.com
LineageOS 19.1 runs good. Magisk works fine. Which gapps package runs on lineage 19.1? Flamegapps not working.
The thread for Lineage 19 is this: https://forum.xda-developers.com/t/...r-the-moto-one-action-one-vision-p50.4436985/
As for the Gapps package, I'm running NikGapps, but you mustnt boot the ROM before flashing Gapps, otherwise flash everything again from the start.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
7
LineageOS is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Bugs :
- Hotspot
- Casting
Instructions :
- Download the latest build and gapps
- Boot to recovery
- Flash the latest build
- Boot to recovery again
- Flash gapps
- Reboot
Downloads :
- kane (Motorola One Vision):
- troika (Motorola One Action):
Reporting Bugs
- DO NOT Report bugs if you're running a custom kernel or you installed Xposed
- Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
- If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
- If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
If you like my work then consider making a donation.
https://www.paypal.com/donate/?cmd=_donations&[email protected]
Contributors
@Stricted, @npjohnson
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 10 Firmware
Based On: LineageOS
Version Information
Status: Beta2
Hello! I don't know if you've ever been on a forum before, but you should know that this is not instant messaging or an IRL conversation. If you want to ask a question, you're expected to make a comprehensive post with details on what's your hardware, software and what you're trying to achieve. Rooting is not universal - there's no single rooting method that can work for any "old tablet", you have to be more specific. Also, please don't use ALL CAPS, you have no reason to be screaming -that's what it looks like - since we have no obligation to help you either, especially if we can't understand what you mean. Thank you in advance!1hey, for everyone that have problems with that calls, here's way to fix this:
- download modem image from attachment below
- use dd or fastboot to flash this (dd: type in terminal emulator or adb shell [on phone] the following: su -c dd if=/path/to/modem.bin of=/dev/block/by-name/modem_a [just in case also flash modem_b], fastboot: fastboot flash modem_a [optionally modem_b] /path/to/modem.bin)
- reboot and enjoy normal calls
another workaround would be just updating to latest stock
modem.bin - AnonFiles
1I have flashed vbmeta a and b and booted into temporarily twrp.
I used adb sideload to flash lineage.zip but I get this error (in the attached files)
I tried installing twrp into recovery and rebooted but that didn't fix it.
That's the attached file I think it glitched idk
That's the attached file I think it glitched idk1i said use stricted's twrp, because official is trash
yeah forum for devs, but with people that can't read and download simple thing
