[ROM]-[13]-[KIEV]-LineageOS-20-[OFFICIAL]

[LunchStrong5016]

If it is indeed a bluetooth stack issue, that would explain why it works on your desktop, but not on your device. As I am guessing the adb port forwards are probably sending the wireless communications over the usb cable for the emulated setup, which bypasses the bluetooth stack and thus wouldn't be affected by issues in that.

I'm leaning towards it not being a bluetooth issue based on a new workaround I found. From my open gitlab issue ticket:

Found a workaround by purchasing an AAWireless dongle and using wireless Android Auto with LOS19 build 20221001 and my GM-branded car.


Dongle would not work initially until I enabled its "GM Fix" setting which according to their FAQ in the background does essentially this:


adb shell setprop debug.car.skip_frx true

I do not know how to run that command on my LOS19 while it's connected to my car head unit and do not know if it will affect AA for other cars, but was hoping it would help developers narrow down the issue in my logcat logs. For now, I can live with using wireless Android Auto with LOS19 but would prefer using USB connection to my car.


Their FAQ: https://cpeb.freshdesk.com/support/...l-not-start-up-car-shows-searching-for-phone-


The above skip_frx appears to be the same thing as when I earlier tested LOS19 with the desktop-head-unit.exe where I enabled AA developer mode on the phone.

I wonder if this

skip_frx

property can be baked into LOS in future builds so they can work with GM head units. Unsure if this will negatively affect other brands of head units, though.

 

[meisanerd]

Interesting. If I run that in the terminal on my phone, it errors out trying to set the prop. But Im currently not at my vehicle, so not sure if that had an impact. I'll have to give it a try when I have a minute.

I am using a dongle to connect to mine as well, my HU runs Android, it isn't a certified unit built into a vehicle. So not sure if this potential fix helps with everything, but at least if it works for dongles we might have a usable solution.

 

[meisanerd]

Ok, disregard my previous error, I forgot to su to root before running setprop in the terminal. If I elevate to root, then run it, it accepts the command just fine. Now to just get out to my vehicle and see if AA connects.

 

[meisanerd]

OK, so with my carlinkit autokit, changing that android property, it seems to get a bit further, but doesn't actually work. It now just repeatedly connects, then disconnects, then connects, then disconnects.

 

[LunchStrong5016]

There are other settings that the AAWireless adapter supports such as passthrough (where the phone's ID is passed through instead of the dongle's ID) and other vendor-specific tweaks for various vendors' head units. I'm not familiar with the carlinkit dongle as I wanted a dongle that had lots of debug options and AAWireless had quite a few from what I saw on youtube and in their Android app. Could you perhaps return the carlinkit and get an AAWireless instead?

Maybe the FAQs from my link for AAWireless support can help you find a similar setting on your carlinkit dongle?

 

[meisanerd]

I think part of the difference is that my head unit doesn't natively support AA, it runs Android so it needs something that emulates AA to work, which is what the Carlinkit does. Now, I might be able to get it working by attaching an AAWireless unit to the carlinkit, and then attach that to the head unit (yay Frankenstein). For now, though, I seem to have gotten a wireless connection "working" via Headunit Reloaded over Wifi. It is buggy, so Im not sure if the setprop made it work, or it just randomly decided to start doing that on its own. It would be nice, though, if it all just worked properly from the get-go.

 

[Deleted member 10134073]

Building 18.1 as user build with a locked bootloader continues to work just fine as of Oct 19.

I pulled in the 19.1 commits from Oct 10 (repopick made light work of this chore). There was one build error related to audio_config_prop in the commit "kiev: sepolicy: address the remaining denials of MotCamera3". Adding a type entry in device/motorola/kiev/sepolicy/vendor/property.te like the moto_boot_prop fixed the build error for me (perhaps related to doing a user build? or am I missing some other 19.1 commit(s)?) Any event the camera is working fine after a few tests. Bluetooth also seems to be working after a quick test.

While I did pull in "kiev: Allow moto camera3 to skip stream size check", I did not pull in the possibly related 3 commits for the topic "twelve-camera-privapp" as the code appeared to be very different in those commits than what is in 18.1. I don't want to spend the time atm to see if this topic needs to be translated and imported for 18.1 (hopefully i get away with being lazy).

HTH anyone still building 18.1 for themselves.

EDIT: Out of happenstance, I missed a few commits from Oct 10. One of those included "Use USB audio policy configuration from AOSP" which was just reverted.

Last edit: I have gone back as far as the august 13 19.1 commits and attempted to repopick all or subsets of them. Aside from the kernel changes (I expect these likely do little other than fix minor bugs - perhaps not even relevant to 18.1) and sepolicy: fix property_contexts for MotCamera, I either run into build errors (especially around the power related changes), runtime errors (attempting to update bluetooth builds and loads but bluetooth does not function), or boot loops (i removed bluetooth related updates and attempted to keep the vendor interface updates).

Given the dev has suggested flashing an updated radio.img to fix some bootloops users are experiencing on 19.1 without booting to stock to "provision" the carrier as has been recommend before, I had hoped some of the vendor interface changes might make it possible to avoid "provisioning" on stock for 18.1. All I got was bootloops with the commit sets I tried so this remains unknown for me.

I dislike the 19.1+ "geriatric" UX enough to remain on 18.1 for a while. But maybe after 20 is stable for a few months, I'll break down and switch. A bunch of 20 commits just recently showed up so it's likely to come for kiev next year when lineageos 20 is released.

 

[meisanerd]

@LunchStrong5016 I just updated to LOS 19.1, including the firmware updates required to keep it from bootlooping, and my wired AA is working now. So not sure if it was a firmware fix, or something that they eventually fixed in LOS.

 

[zigxda]

Followed instructions as usual: https://wiki.lineageos.org/devices/kiev/upgrade.

Successfully and without incident upgraded directly —

from lineage-19.1-20221231-nightly-kiev-signed and MindTheGapps-12.1.0-arm64-20220605_112439

to lineage-20.0-20230114-nightly-kiev-signed and MindTheGapps-13.0.0-arm64-20221025_100653.

 

[SyberHexen]

Anyone who still plays ps3 and uses tether to connect ...this app "PS3 Proxy" is a life savor.. i only play socom confrontation since the servers was hacked and back online..

Also when tethering this app lets me know if im on a vpn or local host...local host 192.0.0.2 for some reason has no connectivity. but when its on lets say an address other than the local host then all devices have great tethered internet. just a jewel i found if any might wanna know.


P.S i can only tether h+ and lte only..
5G stays on local host 192.....xx.
The guy who made the boot img to override and modify the apn was only for stock..
if your reading this can you port the modified boot.img to lineage os 11..much thanks...

Do u have a link to thread of boot.img

 

[SyberHexen]

@LunchStrong5016 I just updated to LOS 19.1, including the firmware updates required to keep it from bootlooping, and my wired AA is working now. So not sure if it was a firmware fix, or something that they eventually fixed in LOS.

It's an unintended fixed by switching the device to qcom USB implementation VS aosp one

 

[fddm]

Do u have a link to thread of boot.img

That was me, but I stopped because my pc did not have enough ram to keep building Lineage and I was worried about killing my swap SSD. The kernels I posted were getting old so I eventually pulled them to prevent issues.

I build with

CONFIG_NETFILTER_XT_TARGET_HL=y

and used Magisk to add iptables rules to modify the TTL of outgoing tethering packets and block IPv6.

iptables -t mangle -A POSTROUTING -j TTL --ttl-set 64
ip6tables -t mangle -I PREROUTING -j DROP

It's unnecessary to modify APN settings for LOS since it does not include DUN APNs.

I also enabled these options to support NAT6 for an app I made that gives much more control than Android allows.

CONFIG_NF_NAT_IPV6=y
CONFIG_IP6_NF_NAT=y
CONFIG_NF_NAT_MASQUERADE_IPV6=y
CONFIG_IP6_NF_TARGET_MASQUERADE=y

And additionally the Wireguard module since I use it.

CONFIG_WIREGUARD=y

I also disable module signatures and module signature enforcement so existing modules are loadable without swapping them in the vendor image.

I attached the last kernel I built for myself, targeting lineage-20.0-20221231

 

[SyberHexen]

Thanks for the information, I had intended to enable wireguard for this family devices but I guess that I lost the change along the way.

I'll look into adding these to the production builds

 

[cidrepitra]

Question from a stupid person...

Can the boot loader be locked and what's the process?
The instructions make no mention of it.

 

[RETIEF]

Question from a stupid person...

Can the boot loader be locked and what's the process?
The instructions make no mention of it.

If you relock the bootloader you will likely brick the phone with only a service center that can help.

 

[Masterchief87]

Is there a reason why I can't get TWRP to boot ever since I installed this ROM? It worked fine prior to installing Lineage but now the only recovery that will work is the lineage recovery. I've tried:
[fastboot boot twrp.img]
[fastboot flash recovery twrp.img]
[fastboot flash recovery_a twrp.img]
[fastboot flash recovery_b twrp.img]

Every time I boot into TWRP it goes to the TWRP splash screen then the phone vibrates and shuts off. Please forgive me if this is a dumb question. I used to know what I was doing, but this is my first A/B device and I haven't really been active for the last few years.

 

[iPhonesSuck]

I've been out of the game flashing ROMs for a few years now but I did root this device when I first got it. Which was about a year ago I guess. I'm on the stock Android 10 build. I would like to update to lineage. I've downloaded all the files. I'm just curious if I could just boot into TWRP and do a full wipe and then just flash the ROM and Gapps and magisk like I'm used to doing in the past on Nexus devices? Would this work or would it brick? Thanks in advance! I'm praying this is possible because my laptop that I use to root this phone is a dinosaur and absolutely hate using it

 

[Masterchief87]

I've been out of the game flashing ROMs for a few years now but I did root this device when I first got it. Which was about a year ago I guess. I'm on the stock Android 10 build. I would like to update to lineage. I've downloaded all the files. I'm just curious if I could just boot into TWRP and do a full wipe and then just flash the ROM and Gapps and magisk like I'm used to doing in the past on Nexus devices? Would this work or would it brick? Thanks in advance! I'm praying this is possible because my laptop that I use to root this phone is a dinosaur and absolutely hate using it

The instructions say you have to update the stock firmware to android 11 before you install lineage.

 

[MindTrix]

I am on android 10 like above but I am looking for a copy of " lineage-18.1-20220813-nightly-kiev-signed.zip " because I lost my copy on a thumb drive.. I would just like this phone to be android 11.. or a few nightlies back is fine too if anyone has a copy

 

[Masterchief87]

Is there a reason why I can't get TWRP to boot ever since I installed this ROM? It worked fine prior to installing Lineage but now the only recovery that will work is the lineage recovery. I've tried:
[fastboot boot twrp.img]
[fastboot flash recovery twrp.img]
[fastboot flash recovery_a twrp.img]
[fastboot flash recovery_b twrp.img]

Every time I boot into TWRP it goes to the TWRP splash screen then the phone vibrates and shuts off. Please forgive me if this is a dumb question. I used to know what I was doing, but this is my first A/B device and I haven't really been active for the last few years.

Never mind. I was using h3xmind's TWRP which apparently is no longer supported. I just found SyberHexen's TWRP on the Havoc OS thread and it seems to work just fine so far. For whatever reason, I guess h3xmind's TWRP doesn't get along with LineageOS 20.