[ROM][UNOFFICIAL] Lineage OS 16.0

Search This thread
By:
Advanced…
Jleeblanch

Jleeblanch

Senior Member
Feb 6, 2012
2,024
5,739
Colchester, VT
Moto G4 Plus
Moto G6
P6tVwPF.jpg


Code: 
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */

LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), 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.

[size=+2]Introduction:[/size]

This is the unofficial Lineage OS thread for the Moto G7 Plus, codename lake.

We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.

[size=+2]Downloads:[/size]

[size=+1]ROM[/size]
[size=+1]Recovery[/size]
[size=+1]GApps[/size]
  • OpenGApps || arm64 - nano version recommended
[size=+2]Installation:[/size]
  • Download the ROM and GApps from the links above.
  • Boot the latest twrp.img (or reboot the bootloader and then to twrp if already installed).
  • IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL THE copy-partitions-AB.zip (to avoid bricking)
  • In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
  • Flash latest build of lineageos
  • Flash latest twrp-installer zip (to keep twrp installed, it'll flash to both slots)
  • Reboot and let ROM boot once (It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
  • Reboot back to the bootloader and then recovery
  • In TWRP, click "Wipe", "Format Data", then type "yes" as prompted
  • Flash GApps (and Magisk if you want root) and Reboot
  • Profit :p
[size=+2]Notes:[/size]
  • Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine, though is not supported.)

XDA:DevDB Information
Lineage OS 16.0, ROM for the Moto G7 Plus

Contributors
Jleeblanch, erfanoabdi
Source Code: https://github.com/LineageOS

ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Official Pie
Based On: Lineage

Version Information
Status: Stable

Created 2019-09-08
Last Updated 2019-09-29
 
  • Like
Reactions: edenist, enilkcals, artmandorz and 11 others
H

hkzlab

Member
Jun 2, 2013
7
1
Great! Can't wait to try this....
...And to be able to build it on my own too, so I can patch it for microg (and wireguard) natively :)

Thanks for your work.
 
  • Like
Reactions: Jleeblanch
Dahenjo

Dahenjo

Senior Member
Oct 18, 2014
686
335
CT
Many thanks @Jleeblanch!

It's definitely faster & smoother than stock, and everything is working fine except for passing ctsProfile in safetynet as noted, also keep getting the SD card setup notification on every reboot, but very minor stuff for an initial release of the first ROM created for the G7 Plus. Camera works with no errors, there are several Moto gestures, advanced reboot & other useful customization, really a nice job! I don't currently have a SIM in it so can't speak to call quality & such.

Since July my device was stuck either in a damaged bootloader with fastboot commands not working (thus unable to flash any firmware) or an early version of TWRP without touch working, also couldn't boot to system so was basically dead in the water. ADB still worked in recovery however, and I recently found a 'adb reboot sideload' command that starts an ADB sideload session without needing any touch, then I was able to sideload twrp-installer-3.3.1-v6.0-lake.zip to get a functional TWRP again! The device could then boot to system again but it was still on 29.98.66-2 that I couldn't update either by OTA or with fastboot since commands still not working. Apparently I can install ROMs with no problems in TWRP.
 
  • Like
Reactions: Jleeblanch and nabi81
Jleeblanch

Jleeblanch

Senior Member
Feb 6, 2012
2,024
5,739
Colchester, VT
Moto G4 Plus
Moto G6
Not sure if anyone noticed, but I posted a new build earlier today (updated the Latest build in the OP ?

It was discovered that the touchscreen wasn't working in Android 10 based GSI's, so I've fixed at least that issue in the new update! However, there are still other issues that need resolving, so use at your own risk.
 
  • Like
Reactions: steven360 and victorockers
Xharos

Xharos

Senior Member
Dec 27, 2010
252
32
Canary Islands
Wow, this came out of nowhere! Do you plan on getting it to official status eventually? If so I will migrate to this as soon as the Moto update support ends!
 
  • Like
Reactions: Jleeblanch
Jleeblanch

Jleeblanch

Senior Member
Feb 6, 2012
2,024
5,739
Colchester, VT
Moto G4 Plus
Moto G6
jamesladderton said:
Mobile Data does not appear to work.
Click to expand...
Click to collapse

Guessing you figured out the LED light situation? Should only be on when device is plugged in. You can also changes that in > Apps & notifications > Notifications > Battery light/Notification light

Mobile data works for me and everyone else. Would need more information including at minimum a radio log to debug. Have you checked to make sure your APN settings are correct?
 
J

jamesladderton

Member
Sep 12, 2019
5
1
Jleeblanch said:
Guessing you figured out the LED light situation? Should only be on when device is plugged in. You can also changes that in > Apps & notifications > Notifications > Battery light/Notification light

Mobile data works for me and everyone else. Would need more information including at minimum a radio log to debug. Have you checked to make sure your APN settings are correct?
Click to expand...
Click to collapse

Apologies about that, yes figured that one out, still working on this one. I should have said its not working for me. Im new to all of this. The was very log so I did last 100 lines or so. Let me know if there's a better command. I played around with APN setting but wasn't much to do from what I know...

Any help would be appreciated! thanks.

Code: 
--------- beginning of main
09-11 21:38:56.234  2700  2874 I libnfc_nci: [INFO:nfa_dm_main.cc(121)] event: NFA_DM_API_RESUME_P2P_EVT (0x0b)
09-11 21:38:56.234  2700  2874 I libnfc_nci: [INFO:nfa_dm_act.cc(1137)] nfa_dm_act_resume_p2p
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:NativeNfcManager.cpp(249)] nfaConnectionCallback: event= 39
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:NativeNfcManager.cpp(596)] nfaConnectionCallback: unknown event ????
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:nfa_sys_main.cc(77)] NFA got event 0x0204
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:nfa_ee_main.cc(635)] Event API_SET_TECH_CFG(0x204), State: INIT_DONE(1)
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:RoutingManager.cpp(617)] RoutingManager::nfaEeCallback: NFA_EE_SET_TECH_CFG_EVT; status=0x0
09-11 21:38:56.235  2700  2700 I libnfc_nci: [INFO:nfa_ee_api.cc(370)] handle:<0x0>protocol_mask:<0x8>/<0x0>/<0x0><0x8><0x0><0x0>
09-11 21:38:56.235  2700  2700 I libnfc_nci: [INFO:nfa_ee_main.cc(401)] nfa_ee_find_ecb
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:nfa_sys_main.cc(77)] NFA got event 0x0205
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:nfa_ee_main.cc(635)] Event API_SET_PROTO_CFG(0x205), State: INIT_DONE(1)
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(200)] nfa_ee_update_route_size nfcee_id:0x0 size_mask:15
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(293)] nfa_ee_total_lmrt_size size:20
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:nfa_dm_main.cc(192)] flags:0x5
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:nfa_sys_ptim.cc(128)] nfa_sys_ptim_start_timer 0x7412e38290
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:nfa_sys_ptim.cc(133)] ptim timer start
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:RoutingManager.cpp(624)] RoutingManager::nfaEeCallback: NFA_EE_SET_PROTO_CFG_EVT; status=0x0
09-11 21:38:56.235  2700  2700 I libnfc_nci: [INFO:nfa_ee_api.cc(303)] handle:<0x1>technology_mask:<0x4>/<0x0>/<0x0><0x4><0x4><0x4>
09-11 21:38:56.235  2700  2700 I libnfc_nci: [INFO:nfa_ee_main.cc(401)] nfa_ee_find_ecb
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:nfa_sys_main.cc(77)] NFA got event 0x0204
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:nfa_ee_main.cc(635)] Event API_SET_TECH_CFG(0x204), State: INIT_DONE(1)
09-11 21:38:56.235  2700  2874 I libnfc_nci: [INFO:RoutingManager.cpp(617)] RoutingManager::nfaEeCallback: NFA_EE_SET_TECH_CFG_EVT; status=0x0
09-11 21:38:56.236  2700  2700 I libnfc_nci: [INFO:nfa_ee_api.cc(370)] handle:<0x0>protocol_mask:<0x4>/<0x0>/<0x0><0x0><0x0><0x0>
09-11 21:38:56.236  2700  2700 I libnfc_nci: [INFO:nfa_ee_main.cc(401)] nfa_ee_find_ecb
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_sys_main.cc(77)] NFA got event 0x0205
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_ee_main.cc(635)] Event API_SET_PROTO_CFG(0x205), State: INIT_DONE(1)
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(200)] nfa_ee_update_route_size nfcee_id:0x0 size_mask:15
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(293)] nfa_ee_total_lmrt_size size:20
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_dm_main.cc(192)] flags:0x5
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_sys_ptim.cc(128)] nfa_sys_ptim_start_timer 0x7412e38290
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:RoutingManager.cpp(624)] RoutingManager::nfaEeCallback: NFA_EE_SET_PROTO_CFG_EVT; status=0x0
09-11 21:38:56.236  2700  2700 I libnfc_nci: [INFO:RoutingManager.cpp(402)] RoutingManager::commitRouting
09-11 21:38:56.236  2700  2700 I libnfc_nci: [INFO:nfa_ee_api.cc(654)] NFA_EeUpdateNow
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_sys_main.cc(77)] NFA got event 0x020B
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_ee_main.cc(635)] Event API_UPDATE_NOW(0x20b), State: INIT_DONE(1)
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_sys_ptim.cc(156)] nfa_sys_ptim_stop_timer 0x7412e38290
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_sys_ptim.cc(163)] ptim timer stop
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2538)] nfa_ee_rout_timeout
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2498)] ee_cfged: 0x91 ee_cfg_sts: 0x10
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2509)] 0: ecb_flags  : 0x04, mask: 0x10
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2664)] nfa_ee_update_rout ee_cfg_sts:0x10
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_ee_main.cc(635)] Event CFG_TO_NFCC(0x219), State: INIT_DONE(1)
09-11 21:38:56.236  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2609)] last_active: 0x1
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2631)] nfa_ee_lmrt_to_nfcc --add the routing for NFCEEs!!
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2393)] nfa_ee_route_add_one_ecb_by_route_order - max_len:860, cur_offset:0, more:1, num_tlv:0,rout_type:- 1
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(451)] nfa_ee_add_aid_route_to_ecb - No AID entries available
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(293)] nfa_ee_total_lmrt_size size:20
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2431)] ee_cfg_sts:0x10 lmrt_size:20
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2639)] nfa_ee_lmrt_to_nfcc --add the routing for DH!!
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2393)] nfa_ee_route_add_one_ecb_by_route_order - max_len:860, cur_offset:0, more:1, num_tlv:0,rout_type:- 1
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(451)] nfa_ee_add_aid_route_to_ecb - No AID entries available
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(293)] nfa_ee_total_lmrt_size size:20
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2431)] ee_cfg_sts:0x11 lmrt_size:20
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2631)] nfa_ee_lmrt_to_nfcc --add the routing for NFCEEs!!
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2393)] nfa_ee_route_add_one_ecb_by_route_order - max_len:860, cur_offset:0, more:1, num_tlv:0,rout_type:- 2
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2416)] nfa_ee_route_add_one_ecb_by_route_order -  Route type - NA:- 2
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(293)] nfa_ee_total_lmrt_size size:20
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2431)] ee_cfg_sts:0x11 lmrt_size:20
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2639)] nfa_ee_lmrt_to_nfcc --add the routing for DH!!
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2393)] nfa_ee_route_add_one_ecb_by_route_order - max_len:860, cur_offset:0, more:1, num_tlv:0,rout_type:- 2
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2416)] nfa_ee_route_add_one_ecb_by_route_order -  Route type - NA:- 2
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(293)] nfa_ee_total_lmrt_size size:20
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2431)] ee_cfg_sts:0x11 lmrt_size:20
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2631)] nfa_ee_lmrt_to_nfcc --add the routing for NFCEEs!!
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2393)] nfa_ee_route_add_one_ecb_by_route_order - max_len:860, cur_offset:0, more:1, num_tlv:0,rout_type:- 3
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(504)] nfa_ee_add_sys_code_route_to_ecb - No SC entries available
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(293)] nfa_ee_total_lmrt_size size:20
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2431)] ee_cfg_sts:0x11 lmrt_size:20
09-11 21:38:56.237  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2639)] nfa_ee_lmrt_to_nfcc --add the routing for DH!!
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2393)] nfa_ee_route_add_one_ecb_by_route_order - max_len:860, cur_offset:0, more:1, num_tlv:0,rout_type:- 3
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(504)] nfa_ee_add_sys_code_route_to_ecb - No SC entries available
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(293)] nfa_ee_total_lmrt_size size:20
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2431)] ee_cfg_sts:0x11 lmrt_size:20
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2631)] nfa_ee_lmrt_to_nfcc --add the routing for NFCEEs!!
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2393)] nfa_ee_route_add_one_ecb_by_route_order - max_len:860, cur_offset:0, more:1, num_tlv:0,rout_type:- 4
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(293)] nfa_ee_total_lmrt_size size:20
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2431)] ee_cfg_sts:0x11 lmrt_size:20
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2639)] nfa_ee_lmrt_to_nfcc --add the routing for DH!!
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2393)] nfa_ee_route_add_one_ecb_by_route_order - max_len:860, cur_offset:0, more:1, num_tlv:0,rout_type:- 4
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(385)] nfa_ee_add_proto_route_to_ecb - NFC DEP added for DH!!!
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(293)] nfa_ee_total_lmrt_size size:20
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2431)] ee_cfg_sts:0x11 lmrt_size:20
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2631)] nfa_ee_lmrt_to_nfcc --add the routing for NFCEEs!!
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2393)] nfa_ee_route_add_one_ecb_by_route_order - max_len:860, cur_offset:15, more:1, num_tlv:3,rout_type:- 5
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(293)] nfa_ee_total_lmrt_size size:20
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2431)] ee_cfg_sts:0x11 lmrt_size:20
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2639)] nfa_ee_lmrt_to_nfcc --add the routing for DH!!
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2393)] nfa_ee_route_add_one_ecb_by_route_order - max_len:860, cur_offset:20, more:0, num_tlv:4,rout_type:- 5
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(293)] nfa_ee_total_lmrt_size size:20
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2431)] ee_cfg_sts:0x11 lmrt_size:20
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2442)] nfa_ee_route_add_one_ecb_by_route_order : set routing num_tlv:5 tlv_size:20
09-11 21:38:56.238  2700  2874 I libnfc_nci: [INFO:NfcAdaptation.cc(583)] NfcAdaptation::HalWrite
09-11 21:38:56.238   801   801 D NxpExtns: find found MIFARE_READER_ENABLE=(0x1)
09-11 21:38:56.239   801  2884 D NxpTml  : PN54X - Write requested.....
09-11 21:38:56.239   801  2884 D NxpTml  : PN54X - Invoking I2C Write.....
09-11 21:38:56.241   801  2884 D NxpNciX : len =  30 > 21011B000501030001030103000104010300010500030101020003000100
09-11 21:38:56.241   801  2884 D NxpTml  : PN54X - I2C Write successful.....
09-11 21:38:56.241   801  2884 D NxpTml  : PN54X - Posting Fresh Write message.....
09-11 21:38:56.241   801  2884 D NxpTml  : PN54X - Tml Writer Thread Running................
09-11 21:38:56.241   801  2886 D NxpHal  : write successful status = 0x0
09-11 21:38:56.241  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2686)] nfa_ee_update_rout ee_cfg_sts:0x10 ee_cfged:0x11
09-11 21:38:56.242   801  2883 D NxpTml  : PN54X - I2C Read successful.....
09-11 21:38:56.242   801  2883 D NxpNciR : len =   4 > 41010100
09-11 21:38:56.243   801  2883 D NxpTml  : PN54X - Posting read message.....
09-11 21:38:56.243   801  2886 D NxpHal  : read successful status = 0x0
09-11 21:38:56.243   801  2883 D NxpTml  : PN54X - Read requested.....
09-11 21:38:56.243   801  2883 D NxpTml  : PN54X - Invoking I2C Read.....
09-11 21:38:56.243  2700  2874 I libnfc_nci: [INFO:nfc_ncif.cc(383)] NFC received rsp gid:1
09-11 21:38:56.243  2700  2874 I libnfc_nci: [INFO:nfa_dm_act.cc(268)] NFC_SET_ROUTING_REVT(0x500a)
09-11 21:38:56.243  2700  2874 I libnfc_nci: [INFO:nfa_ee_main.cc(357)] nfa_ee_proc_evt: event=0x500a int_event:0x216
09-11 21:38:56.243  2700  2874 I libnfc_nci: [INFO:nfa_ee_main.cc(635)] Event NCI_WAIT_RSP(0x216), State: INIT_DONE(1)
09-11 21:38:56.243  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2079)] ee_wait_evt:0x30 wait_rsp:1
09-11 21:38:56.243  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2052)] nfa_ee_report_update_evt ee_wait_evt:0x30 wait_rsp:0
09-11 21:38:56.243  2700  2874 I libnfc_nci: [INFO:RoutingManager.cpp(704)] RoutingManager::nfaEeCallback: NFA_EE_UPDATED_EVT
09-11 21:38:56.243  2700  2700 I libnfc_nci: [INFO:NativeNfcManager.cpp(2029)] startRfDiscovery: is start=1
09-11 21:38:56.243  2700  2700 I libnfc_nci: [INFO:NativeNfcTag.cpp(1753)] nativeNfcTag_acquireRfInterfaceMutexLock: try to acquire lock
09-11 21:38:56.243  2700  2700 I libnfc_nci: [INFO:NativeNfcTag.cpp(1756)] nativeNfcTag_acquireRfInterfaceMutexLock: sRfInterfaceMutex lock
09-11 21:38:56.243  2700  2700 I libnfc_nci: [INFO:nfa_dm_api.cc(691)] NFA_StartRfDiscovery
09-11 21:38:56.243  2700  2874 I libnfc_nci: [INFO:nfa_sys_main.cc(77)] NFA got event 0x010E
09-11 21:38:56.243  2700  2874 I libnfc_nci: [INFO:nfa_dm_main.cc(121)] event: NFA_DM_API_START_RF_DISCOVERY_EVT (0x0e)
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:nfa_dm_act.cc(1228)] nfa_dm_act_start_rf_discovery
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:nfa_dm_discover.cc(910)] nfa_dm_start_rf_discover
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2315)] 1
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:nfa_ee_act.cc(2339)] 0x0, 0x0, 0x1, 0x0
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:nfa_dm_discover.cc(1038)] nfa_dm_cb.disc_cb.entry[0].selected_disc_mask = 0x40000
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:nfa_dm_discover.cc(1038)] nfa_dm_cb.disc_cb.entry[1].selected_disc_mask = 0x3d7f
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:nfa_dm_discover.cc(1038)] nfa_dm_cb.disc_cb.entry[2].selected_disc_mask = 0xc400000
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:nfa_p2p_main.cc(524)] nfa_p2p_set_config
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:llcp_api.cc(231)] LLCP_GetDiscoveryConfig
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:nfa_dm_main.cc(220)] nfa_dm_check_set_config
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:nfa_dm_main.cc(220)] nfa_dm_check_set_config
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:nfa_dm_discover.cc(1076)] dm_disc_mask = 0xc443d7f
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:nfa_dm_discover.cc(281)] tech_proto_mask = 0x0C443D7F
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:nfa_dm_main.cc(220)] nfa_dm_check_set_config
09-11 21:38:56.244  2700  2874 I libnfc_nci: [INFO:NfcAdaptation.cc(583)] NfcAdaptation::HalWrite
09-11 21:38:56.244  2622  3657 I CastDatabase: Opening the database
09-11 21:38:56.244   801   801 D NxpExtns: find found MIFARE_READER_ENABLE=(0x1)
09-11 21:38:56.246   801  2884 D NxpTml  : PN54X - Write requested.....
09-11 21:38:56.246   801  2884 D NxpTml  : PN54X - Invoking I2C Write.....
09-11 21:38:56.250   801  2884 D NxpNciX : len =   7 > 20020401500102
09-11 21:38:56.250   801  2884 D NxpTml  : PN54X - I2C Write successful.....
09-11 21:38:56.250   801  2884 D NxpTml  : PN54X - Posting Fresh Write message.....
09-11 21:38:56.250   801  2884 D NxpTml  : PN54X - Tml Writer Thread Running................
09-11 21:38:56.250   801  2886 D NxpHal  : write successful status = 0x0
09-11 21:38:56.250  2700  2874 I libnfc_nci: [INFO:nfa_dm_discover.cc(396)] nfa_dm_set_total_duration
09-11 21:38:56.250  2700  2874 I libnfc_nci: [INFO:nfa_dm_main.cc(220)] nfa_dm_check_set_config
09-11 21:38:56.250  2700  2874 I libnfc_nci: [INFO:nfc_main.cc(888)] NFC_DiscoveryStart
09-11 21:38:56.250  2700  2874 I libnfc_nci: [INFO:nfc_main.cc(908)] NFC_DiscoveryStart status: 0xe3
09-11 21:38:56.253   801  2883 D NxpTml  : PN54X - I2C Read successful.....
09-11 21:38:56.253   801  2883 D NxpNciR : len =   5 > 4002020000
09-11 21:38:56.253   801  2883 D NxpTml  : PN54X - Posting read message.....
09-11 21:38:56.253   801  2886 D NxpHal  : read successful status = 0x0
09-11 21:38:56.253   801  2886 D NxpHal  : phNxpNciHal_print_res_status: response status =STATUS_OK
09-11 21:38:56.253  2700  2874 I libnfc_nci: [INFO:nfc_ncif.cc(383)] NFC received rsp gid:0
09-11 21:38:56.253   801  2883 D NxpTml  : PN54X - Read requested.....
09-11 21:38:56.253   801  2883 D NxpTml  : PN54X - Invoking I2C Read.....
09-11 21:38:56.254  2700  2874 I libnfc_nci: [INFO:nci_hrcv.cc(62)] nci_proc_core_rsp opcode:0x2
09-11 21:38:56.254  2700  2874 I libnfc_nci: [INFO:nfa_dm_act.cc(268)] NFC_SET_CONFIG_REVT(0x5002)
09-11 21:38:56.254  2700  2874 I libnfc_nci: [INFO:NfcAdaptation.cc(624)] NfcAdaptation::HalPrediscover
09-11 21:38:56.254  2700  2874 I libnfc_nci: [INFO:NfcAdaptation.cc(583)] NfcAdaptation::HalWrite
09-11 21:38:56.254   801   801 D NxpExtns: find found MIFARE_READER_ENABLE=(0x1)
09-11 21:38:56.254   801   801 D NxpHal  : > Polling Loop Started
09-11 21:38:56.254   801  2884 D NxpTml  : PN54X - Write requested.....
09-11 21:38:56.254   801  2884 D NxpTml  : PN54X - Invoking I2C Write.....
09-11 21:38:56.256   801  2884 D NxpNciX : len =  26 > 2103170B00010101020103010501800182018301850106017001
09-11 21:38:56.257   801  2884 D NxpTml  : PN54X - I2C Write successful.....
09-11 21:38:56.257   801  2884 D NxpTml  : PN54X - Posting Fresh Write message.....
09-11 21:38:56.257   801  2884 D NxpTml  : PN54X - Tml Writer Thread Running................
09-11 21:38:56.257   801  2886 D NxpHal  : write successful status = 0x0
09-11 21:38:56.259  1478  2487 I WifiService: startScan uid=10086
09-11 21:38:56.260   801  2883 D NxpTml  : PN54X - I2C Read successful.....
09-11 21:38:56.260  2622  2622 I DiscoveryManager: WifiGuestModeDeviceScanner enabled.
09-11 21:38:56.260   801  2883 D NxpNciR : len =   4 > 41030100
09-11 21:38:56.261   801  2883 D NxpTml  : PN54X - Posting read message.....
09-11 21:38:56.262   801  2886 D NxpHal  : read successful status = 0x0
09-11 21:38:56.262  2622  3657 I SQLiteCastStore: 0 CastNetworkInfo instances loaded, 0 CastDeviceInfo instances loaded, 0 paired guest mode devices loaded.
09-11 21:38:56.262  2700  2874 I libnfc_nci: [INFO:nfc_ncif.cc(383)] NFC received rsp gid:1
09-11 21:38:56.262  2700  2874 I libnfc_nci: [INFO:nfa_dm_discover.cc(3038)] returning TRUE
09-11 21:38:56.262  2700  2874 I libnfc_nci: [INFO:nfa_dm_discover.cc(720)] event:0x4000
09-11 21:38:56.262  2700  2874 I libnfc_nci: [INFO:nfa_dm_discover.cc(2529)] state: IDLE (0), event: DISCOVER_RSP(1) disc_flags: 0x31
09-11 21:38:56.262  2700  2874 I libnfc_nci: [INFO:nfa_dm_discover.cc(1711)] old_state: IDLE (0), new_state: DISCOVERY (1) disc_flags: 0x11
09-11 21:38:56.262  2700  2874 I libnfc_nci: [INFO:nfa_dm_act.cc(1554)] event:0x00
09-11 21:38:56.262  2700  2874 I libnfc_nci: [INFO:nfa_p2p_main.cc(104)] event:0x00
09-11 21:38:56.263  2700  2874 I libnfc_nci: [INFO:NativeNfcManager.cpp(249)] nfaConnectionCallback: event= 30
09-11 21:38:56.263  2700  2874 I libnfc_nci: [INFO:NativeNfcManager.cpp(274)] nfaConnectionCallback: NFA_RF_DISCOVERY_STARTED_EVT: status = 0
09-11 21:38:56.263  2700  2874 I libnfc_nci: [INFO:nfa_dm_discover.cc(2582)] new state: DISCOVERY (1), disc_flags: 0x1
09-11 21:38:56.263  2700  2700 I libnfc_nci: [INFO:NativeNfcTag.cpp(1771)] nativeNfcTag_releaseRfInterfaceMutexLock: sRfInterfaceMutex unlock
09-11 21:38:56.263  2700  2700 I libnfc_nci: [INFO:PowerSwitch.cpp(258)] PowerSwitch::setModeOn(activated=0x1) : mCurrActivity=0x1
09-11 21:38:56.263  2700  2700 I libnfc_nci: [INFO:NativeNfcManager.cpp(1226)] nfcManager_enableDiscovery: exit
09-11 21:38:56.263  2700  2700 I libnfc_nci: [INFO:NativeNfcManager.cpp(1754)] nfcManager_doSetScreenState: state = 8 prevScreenState= 2, discovry_param = 1
09-11 21:38:56.264   801  2883 D NxpTml  : PN54X - Read requested.....
09-11 21:38:56.264   801  2883 D NxpTml  : PN54X - Invoking I2C Read.....
09-11 21:38:56.269  2700  5520 D NfcService: Discovery configuration equal, not updating.
09-11 21:38:56.554   790  4194 D msm8916_platform: platform_set_channel_map mixer_ctl_name:Playback Channel Map13
09-11 21:38:56.555   790  4194 D msm8916_platform: platform_set_channel_map: set mapping(1 2 0 0 0 0 0 0) for channel:2
09-11 21:38:56.556   790  4194 D audio_hw_primary: start_output_stream: exit
09-11 21:38:56.576   818  1779 W AudioFlinger: write blocked for 366 msecs, 12 delayed writes, thread 0xe7f83d00
09-11 21:38:58.339   810   831 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
 
Jleeblanch

Jleeblanch

Senior Member
Feb 6, 2012
2,024
5,739
Colchester, VT
Moto G4 Plus
Moto G6
jamesladderton said:
Apologies about that, yes figured that one out, still working on this one. I should have said its not working for me. Im new to all of this. The was very log so I did last 100 lines or so. Let me know if there's a better command. I played around with APN setting but wasn't much to do from what I know...

Any help would be appreciated! thanks.
Click to expand...
Click to collapse

Unfortunately, what you did post of the log is mostly just about NFC ?. Check the Lineage Wiki section "how to capture a log" which explains how to get a log on the device or using ADB. Either one will work.

As far as APN settings go, you just wanna make sure it's the same as on stock
 
J

jamesladderton

Member
Sep 12, 2019
5
1
Jleeblanch said:
Unfortunately, what you did post of the log is mostly just about NFC . Check the Lineage Wiki section which explains how to get a log on the device or using ADB. Either one will work.

As far as APN settings go, you just wanna make sure it's the same as on stock
Click to expand...
Click to collapse

Ok thanks. It says LTE but the bars have a little x on it. Not sure what stock APN was but it is using pda.bell.ca which is my provider.

I cant upload a external link link to radio.txt yet. ill have to wait/make more posts. Thanks!

---------- Post added at 02:36 PM ---------- Previous post was at 01:43 PM ----------
Jleeblanch said:
Unfortunately, what you did post of the log is mostly just about NFC . Check the Lineage Wiki section "how to capture a log" which explains how to get a log on the device or using ADB. Either one will work.

As far as APN settings go, you just wanna make sure it's the same as on stock
Click to expand...
Click to collapse

I also only have the option to "Reset to default" in APNs. There isn't an option to edit or add new. Is this normal or is there a setting I need to change?
 
Jleeblanch

Jleeblanch

Senior Member
Feb 6, 2012
2,024
5,739
Colchester, VT
Moto G4 Plus
Moto G6
jamesladderton said:
Ok thanks. It says LTE but the bars have a little x on it. Not sure what stock APN was but it is using pda.bell.ca which is my provider.

I cant upload a external link link to radio.txt yet. ill have to wait/make more posts. Thanks!

---------- Post added at 02:36 PM ---------- Previous post was at 01:43 PM ----------



I also only have the option to "Reset to default" in APNs. There isn't an option to edit or add new. Is this normal or is there a setting I need to change?
Click to expand...
Click to collapse

I got your log, thanks. I'll take a look and let you know if I need any more info.

If you're able to edit your APN settings on stock, I would assume you'd be able to on custom ROMs too.
 
You must log in or register to reply here.

Similar threads

Jleeblanch
[ROM][OFFICIAL][LAKE] LineageOS 17.1 for Moto G7 Plus [weeklies]
Replies
412
Views
55K
J
jc56au
Jleeblanch
[ROM][UNOFFICIAL] Resurrection Remix v7.0.2
Replies
24
Views
11K
X
xth88312
jeffreyvh
[RECOVERY][UNOFFICIAL] TWRP-3.2.3-x [lake]
Replies
43
Views
15K
zfk110
zfk110
Jorge Lucas
[ROM][10.0] Evolution X 4.1.69 for the Moto G7 Plus [UNOFFICIAL]
Replies
31
Views
10K
N
N3r1xx
N
[OFFICIAL] LineageOS 18.1 for the Moto G7 Plus
Replies
334
Views
39K
Tiki Thorsen
Tiki Thorsen

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 14
    Jleeblanch
    Jleeblanch
    P6tVwPF.jpg


    Code: 
    /*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */

    LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), 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.

    [size=+2]Introduction:[/size]

    This is the unofficial Lineage OS thread for the Moto G7 Plus, codename lake.

    We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.

    [size=+2]Downloads:[/size]

    [size=+1]ROM[/size]
    [size=+1]Recovery[/size]
    [size=+1]GApps[/size]
    • OpenGApps || arm64 - nano version recommended
    [size=+2]Installation:[/size]
    • Download the ROM and GApps from the links above.
    • Boot the latest twrp.img (or reboot the bootloader and then to twrp if already installed).
    • IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL THE copy-partitions-AB.zip (to avoid bricking)
    • In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
    • Flash latest build of lineageos
    • Flash latest twrp-installer zip (to keep twrp installed, it'll flash to both slots)
    • Reboot and let ROM boot once (It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
    • Reboot back to the bootloader and then recovery
    • In TWRP, click "Wipe", "Format Data", then type "yes" as prompted
    • Flash GApps (and Magisk if you want root) and Reboot
    • Profit :p
    [size=+2]Notes:[/size]
    • Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine, though is not supported.)

    XDA:DevDB Information
    Lineage OS 16.0, ROM for the Moto G7 Plus

    Contributors
    Jleeblanch, erfanoabdi
    Source Code: https://github.com/LineageOS

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 4.x
    ROM Firmware Required: Official Pie
    Based On: Lineage

    Version Information
    Status: Stable

    Created 2019-09-08
    Last Updated 2019-09-29
    View
    4
    Jleeblanch
    Jleeblanch
    LineageOS 16.0

    Download -> lineage-16.0-20200116-UNOFFICIAL-lake.zip

    Changes:
    -> SELinux Enforcing
    -> Security Patches thru Dec
    -> Blobs updated to PPWS29.98-111-9
    -> Audio changes

    NOTES:
    -> This is a debugging build (eng) and if needed, adb should be available during boot. If you guys could please test audio and daily usage. This is the last hurdle before we can go official :)
    View
    2
    Jleeblanch
    Jleeblanch
    BUGS
    • The mic is muted (meaning the other person can't hear you) when using Speaker phone in Calls <- FIXED
    • Low in-call volume <- WIP
    • SELinux is Permissive Enforced
    View
    2
    Dahenjo
    Dahenjo
    Many thanks @Jleeblanch!

    It's definitely faster & smoother than stock, and everything is working fine except for passing ctsProfile in safetynet as noted, also keep getting the SD card setup notification on every reboot, but very minor stuff for an initial release of the first ROM created for the G7 Plus. Camera works with no errors, there are several Moto gestures, advanced reboot & other useful customization, really a nice job! I don't currently have a SIM in it so can't speak to call quality & such.

    Since July my device was stuck either in a damaged bootloader with fastboot commands not working (thus unable to flash any firmware) or an early version of TWRP without touch working, also couldn't boot to system so was basically dead in the water. ADB still worked in recovery however, and I recently found a 'adb reboot sideload' command that starts an ADB sideload session without needing any touch, then I was able to sideload twrp-installer-3.3.1-v6.0-lake.zip to get a functional TWRP again! The device could then boot to system again but it was still on 29.98.66-2 that I couldn't update either by OTA or with fastboot since commands still not working. Apparently I can install ROMs with no problems in TWRP.
    View
    2
    Jleeblanch
    Jleeblanch
    Not sure if anyone noticed, but I posted a new build earlier today (updated the Latest build in the OP ?

    It was discovered that the touchscreen wasn't working in Android 10 based GSI's, so I've fixed at least that issue in the new update! However, there are still other issues that need resolving, so use at your own risk.
    View

New posts