Thanks for the update. I'm following and waiting for this to be resolved before I can comeback from stock. Otherwise I totally loved this lineageos rom.
Sent from my moto g(7) plus using Tapatalk
Sent from my moto g(7) plus using Tapatalk
[ROM][OFFICIAL] LineageOS 17.1 [nightlies]
- Thread starter Jleeblanch
- Start date
The below mentioned beta seems to solve the speaker issue for me. Hopeing for VoLTE and WLAN-Call.
Question (not in relation to the above!): I have problems with recognition of my sim + data; which must have to do with some fiddling from my side when flashing the stock. do i have to erease the carrier or reflash baseband or something to resolve?
Question (not in relation to the above!): I have problems with recognition of my sim + data; which must have to do with some fiddling from my side when flashing the stock. do i have to erease the carrier or reflash baseband or something to resolve?
When will the Android 11 (R) be released on lake? I am looking forward to installing LineageOS on my moto g7 plus. Because now I am using 6+128 performance with LineageOS 17.1 , it's very smooth. You could not believe that why the 636 CPU could be so smooth.
Again, asking for ETAs is forbidden, read the goddamn forum rules.
Re; Speakerphone Low Volume
XT1965-2, 2020 10 20 Top/upper speaker still not working, volume still low.
(Speakerphone working good on Pixel XL 2020 10 24 and earlier).
XT1965-2, 2020 10 20 Top/upper speaker still not working, volume still low.
(Speakerphone working good on Pixel XL 2020 10 24 and earlier).
Patience, Lineage 17.1 builds are still rolling. Lineage 18.0 will come soon enough. I have successfully built and ran 18.0 and will post some test builds in the coming weeks.
Yes, I'm aware. We're switching to prebuilt audio blobs and the next build will will make all your dreams come true! And who knows, may even get lucky that day cuz you'll be able to hear clearly now xD
For real tho, this change also addresses all the audio recording issues in probably every app [emoji14]
Nice! Thank you for your work. Was waiting for the audio / speakerphone fix before coming back to LineageOS. Looking forward to to the next build.
Sent from my moto g(7) plus using Tapatalk
Sent from my moto g(7) plus using Tapatalk
SIM recognition + DATA
I have problems with recognition of my simcard + data (not working and gets switched off); which must have to do with some fiddling from my side when reflashing the stock.
do i have to try to erase the carrier image or reflash baseband or something to resolve?
any idea is highly appeciated
I have problems with recognition of my simcard + data (not working and gets switched off); which must have to do with some fiddling from my side when reflashing the stock.
do i have to try to erase the carrier image or reflash baseband or something to resolve?
any idea is highly appeciated
As a workaround for the current audio recording issue, you can install open camera which lets you select an audio recording source. Set it to "device default", and the audio will record with videos.
I assume the usual option when recording video comes from the camera API, whereas this takes audio from the audio recording API directly.
It will hold us over until the official fix comes through
I assume the usual option when recording video comes from the camera API, whereas this takes audio from the audio recording API directly.
It will hold us over until the official fix comes through
Looks like the speakerphone issue is fixed in this latest release. Thank you!
Sent from my moto g(7) plus using Tapatalk
Re; Speakerphone Low Volume
XT1965-2 los 2020 11 17 Lower speaker volume now nice and loud. Perfectly usable. (Top speaker still not working).
Re; Speakerphone
XT1965-2 los 2020 11 17 Lower speaker volume now nice and loud. Perfectly usable. (Top speaker still not working).
Last edited:
I've just gotten a new G7 Plus direct from Motorola and am having several issues with it. It's an XT1965-T, but branded as a pure G7 Plus. From everything I can tell, Motorola may just be clearing out stock on REVVLRY+ devices by selling as a native G7 Plus. Perhaps the custom init handling of XT1965-T may have something to do with some of these issues? In either case it'd be nice to have it displayed as a G7 Plus device instead of forcing the REVVLRY+ branding, but I'm not sure if there's another prop to use for keying off of.
I started testing using the
I started testing using the
lineage-17.1-20201201-nightly-lake-signed.zip build and the two biggest issues I'm having are below. I'll next test with the oldest build currently available (20201110) to see if it may be related to the recent HAL changes.- Ironically with this being a T-Mobile device, I don't have any data service (calling, SMS, MMS, LTE data) with a T-Mobile sim inserted. When connected to wifi I am able to make calls. With stock (originally and when restoring to it) I do have full mobile services, so it doesn't appear to be a hardware fault.
- The phone reboots almost immediately upon being disconnected from USB. In initial logcat investigation, being connected to USB inhibits RescueParty from getting triggered. It is slated to be triggered because
org.lineageos.settings.deviceis continually crashing with the stacktrace/logcat snippet below.
Code:
12-01 02:52:56.469 11065 11065 E SensorManager: sensor or listener is null
12-01 02:52:56.470 11065 11065 D AndroidRuntime: Shutting down VM
12-01 02:52:56.471 11065 11065 E AndroidRuntime: FATAL EXCEPTION: main
12-01 02:52:56.471 11065 11065 E AndroidRuntime: Process: org.lineageos.settings.device, PID: 11065
12-01 02:52:56.471 11065 11065 E AndroidRuntime: java.lang.RuntimeException: Unable to create service org.lineageos.settings.device.ServiceWrapper: java.lang.RuntimeException: Failed to registerListener for sensor null
12-01 02:52:56.471 11065 11065 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:3965)
12-01 02:52:56.471 11065 11065 E AndroidRuntime: at android.app.ActivityThread.access$1500(ActivityThread.java:219)
12-01 02:52:56.471 11065 11065 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1875)
12-01 02:52:56.471 11065 11065 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
12-01 02:52:56.471 11065 11065 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
12-01 02:52:56.471 11065 11065 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7356)
12-01 02:52:56.471 11065 11065 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-01 02:52:56.471 11065 11065 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
12-01 02:52:56.471 11065 11065 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
12-01 02:52:56.471 11065 11065 E AndroidRuntime: Caused by: java.lang.RuntimeException: Failed to registerListener for sensor null
12-01 02:52:56.471 11065 11065 E AndroidRuntime: at org.lineageos.settings.device.SensorHelper.registerListener(SensorHelper.java:105)
12-01 02:52:56.471 11065 11065 E AndroidRuntime: at org.lineageos.settings.device.actions.CameraActivationSensor.<init>(CameraActivationSensor.java:47)
12-01 02:52:56.471 11065 11065 E AndroidRuntime: at org.lineageos.settings.device.LineageActionsService.<init>(LineageActionsService.java:81)
12-01 02:52:56.471 11065 11065 E AndroidRuntime: at org.lineageos.settings.device.ServiceWrapper.onCreate(ServiceWrapper.java:48)
12-01 02:52:56.471 11065 11065 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:3953)
12-01 02:52:56.471 11065 11065 E AndroidRuntime: ... 8 more
12-01 02:52:56.474 1495 4189 V RescueParty: Disabled because of active USB connection
12-01 02:52:56.475 1495 4189 W ActivityManager: Process org.lineageos.settings.device has crashed too many times: killing!I tested both the 20201110 and 20201124 builds and both seem to work fine and not have the issues, so it appears to be a newly introduced issue in the 20201201 build.
(I can't find any way to edit a post in the upgraded XDA forum software, if I'm missing the option then sorry for multiple posts).
Interestingly enough, I found that clean installation of the 20201201 ROM causes the issues above, however a clean installation of 20201124 and then upgrading to 20201201 does NOT result in the same issues and seems to work fine on an initial check.
Interestingly enough, I found that clean installation of the 20201201 ROM causes the issues above, however a clean installation of 20201124 and then upgrading to 20201201 does NOT result in the same issues and seems to work fine on an initial check.
Hey, I'm sorry to hear you're having said issue. I was curious about that, the variant you bought. So it is a -T variant, which is technically the same sku as the TMO branded REVVLRY+. If that is the case, I'll have to rethink how we detect which variant is which, because as you found out, the current check is for matching sku XT1965-T. Not a big deal.
Regarding your LineageActions (Moto Actions) crash, there hasn't been any changes there since we dropped 17.1 except for the icons, which coincidentally did happen within the last few weeks. But from what I'm seeing in your log, Moto Actions is crashing due to not being able to register a sensor that's reading as "null". CameraActivationSensor.java implies it's your camera not activating. Can you grab a full log? Or do you have the rest of the above log?
For the crashing issue, for whatever reason I'm unable to reproduce the same issue with the 20201201 build. Perhaps it was something related to a particular order in which I restored stock and then reinstalled LineageOS, or a mixture of TWRP versions? I do still have the full logcat dump available if it'd be of use, perhaps at least to better catch the error and more sanely continue. I've now updated to the 20201208 build and everything appears to be working swimmingly, even after a factory reset and clean install.
As for the phone identification, I don't have a REVVLRY+ phone for comparison to know for sure if there's anything different, but from the full bootloader getvar output, perhaps
The full output of `fastboot getvar all` is
[1] https://www.androidpolice.com/2020/...nes-to-android-10-after-almost-yearlong-wait/
As for the phone identification, I don't have a REVVLRY+ phone for comparison to know for sure if there's anything different, but from the full bootloader getvar output, perhaps
version-bootloader or ro.carrier would be usable to distinguish the actual REVVLRY+ from the retail XT1965-T as a branded g7 plus? In particular, at least in the stock ROM listings there is a separate "TMO" variant software channel, but I don't know if the reported carrier at the bootloader level is different. Moreover, with the T-Mobile carrier REVVLRY+ having recently received the Android 10 updates [1], is there still much of a reason to forcably override the fingerprint and build description even on those devices?The full output of `fastboot getvar all` is
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-200929
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: TMO
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (2)
(bootloader) serialno: XXXXXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: XXXXXXXX
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 11-06-2020
(bootloader) sku: XT1965-T
(bootloader) carrier_sku: XT1965-T
(bootloader) battid: SB18C53460
(bootloader) battery-voltage: 4291
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10/QPWS30.6
(bootloader) ro.build.fingerprint[1]: 1-21-18-3/67563:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
(bootloader) version-baseband: M636_21.71.02.66R LAKE_TMO_CUST
(bootloader) kernel.version[0]: Linux version 4.4.192-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Thu O
(bootloader) kernel.version[3]: ct 1 03:52:06 CDT 2020
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9489-200929
(bootloader) git:xbl: MBM-3.0-lake_retail-efaf0cccb-200929
(bootloader) git:pmic: MBM-3.0-lake_retail-efaf0cccb-200929
(bootloader) git:rpm: MBM-3.0-lake_retail-0dc899d-200929
(bootloader) git:tz: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:hyp: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:devcfg: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:cmnlib: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:keymaster: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:prov: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:storsec: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retla
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 1PHONE CALL NOT STARTING (20201215)
After initial system startup, phone will not make call from Contacts, reverts back to Contacts list.
Works normally after awhile. Anyone else experiencing this?
After initial system startup, phone will not make call from Contacts, reverts back to Contacts list.
Works normally after awhile. Anyone else experiencing this?
Hi ,
I have the same issue. When I flashing Lineage OS 17.1 latest version in Dec. Then facing no service problem and then I tried Mokee Rom, they have the same issue of no service.
Another issue is random rebooting.
But When I flash back to moto retail rom. The phone has sevice.
The model on the box is : XT1965-T moto G7 PLUS. When I flash the these two ROM, system shows: REVVLRY+
This phone bought from AMAZON this month which produced in 2020-11-05 in india.
What I found out is Since my phone is 1965-2 my radio is LATM even tho I live in the US....and sometimes when I flash my network shows it is LTE GSM.....my phone won't dial out unless I have it set to Global
Hello,
G7 Plus 1965-3
Tried both LOS 2020-12-15 and 2020-12-08 both versions
no cellular network, "no service" message.
SIM card is detected, IMEI is there, NFC+wifi is working, but no phone calls / cellular networking
Baseband problem? Before I had stock Moto ROM, installed LOS as recommended in the blog.
fastboot erase modemst1 +2 makes things worse
Thanks for any hint
G7 Plus 1965-3
Tried both LOS 2020-12-15 and 2020-12-08 both versions
no cellular network, "no service" message.
SIM card is detected, IMEI is there, NFC+wifi is working, but no phone calls / cellular networking
Baseband problem? Before I had stock Moto ROM, installed LOS as recommended in the blog.
fastboot erase modemst1 +2 makes things worse
Thanks for any hint
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone