Hopefully we can get all this sorted out before too long and have working lineage builds quickly.ntzrmtthihu777 said:So, I've been doing some work on getting LineageOS to work on this device. No idea as of right now
if it will work on any other carrier variants (I think they don't allow for bootloader unlocking?).
Currently everything 'works' (some is buggy but that may be more to do with the fact that 17.1 is not
currently finished) with the exception of two things I've tested/noticed (other stuff may be broken
but I've not seen them yet): audio in calls (I can make/take calls but I can't hear or be heard. Audio
works as I can play music in the LineageOS music app and record/playback the recording in the app)
and the fingerprint sensor (pretty sure I'm just missing some part from the stock ROM).
What I'm asking is that all owners of stock (unlocked/rooted is probably fine, custom kernels prob
not) collect some logs for me during specific activities so I can determine what is missing and maybe
produce a rom for you guys to test out without losing some features.
I'd like three things:
1. Follow the instructions here and upload the oem_log folder to somewhere and share it.
2. A logcat of boot up through making a phone call and hang up. To take this, you'll need
developer mode and adb debugging enabled on the phone and the platform tools (adb
primarily) set up for your operating system. From either cmd.exe (windows) or Terminal.app (OSX)
or your preferred terminal emulator (Linux, too many options to list them all), enter this command:
Then, power your phone off, hook it up via USB to the machine, power it on, place the call,Code:
adb logcat > logcat.call.log
say a few words, hang up. Then press ctrl+c in the cmd/terminal/whatever window to
end the logging session.
3. A logcat of boot up through enrolling a fingerprint in the phone and unlocking via
the fingerprint. Same procedure, but the command is:
adb logcat > logcat.finger.log
Optionally, for those with rooted phones, I'd like these logs as well:
4. A dmesg during boot up through making a call and hangup. Same procedure as #2, but the
5. A dmesg during boot up through enrolling a fingerprint in the phone and unlockingCode:
adb shell su -c dmesg > dmesg.call.log
via the fingerprint. Same procedure as #3 but the command is
adb shell su -c dmesg > dmesg.finger.log
The files gathered from #2-5 will be in the current directory you executed the logcat command
from. On windows it will say this right before where you type the command, and on OSX/Linux
this will probably be in your home directory, unless you changed the directory first. I expect OSX
or Linux users to be a bit more savvy about this already.
The files may contain unique data to your phone (serial number, IMEI, other things) but android
filters out all but the last two numbers of the phone you are calling, so its generally ok. However,
I do not suggest posting links to these files here, but you can message me them directly here.
If/when you do this, please make note of the exact model number of your phone (not sure if
all 5g phones are HD1925 or not), current firmware version, and baseband version. These can
all be found in settings->about phone or so.
Thanks in advance and happy hacking!