Try using that basic attestation setting to change the model number to LE2127. That's the TMO model#.
Try using that basic attestation setting to change the model number to LE2127. That's the TMO model#.
Go for Gcam, a lot better than de stock oneJumping in with a OP9 - wondering if this build of LineageOS has a fully functioning camera that is on par with stock ?
Thanks, In Advance, for any Input !
The driver supplied by oneplus for charging and battery doesn't actually work properly, it's just a bunch of hard coded values. The full battery life is still available, just not fully visible in software.Cool stuff but kinda ****ty battery life or is it only me? Accubattery calculates 2000 mAh as compared to 4500 mAh which is the real level?
Do you have a link to read more about this somewhere? I noticed the driver issue a little, for example it keeps showing the same time to charge no matter what the %.The driver supplied by oneplus for charging and battery doesn't actually work properly, it's just a bunch of hard coded values. The full battery life is still available, just not fully visible in software.
I don't have a link, but basically most battery and charger related values are hardcoded in the oplus_chg driver, hence why charging always shows 1h24m (5000 seconds, to be precise) and why tools like Ampere and Accubattery produce seemingly nonsensical results. Other values like voltage, current, etc. are also hard coded to weird values. OOS doesn't use the provided driver, it's there for compatibility with AOSP but the values are all useless.Do you have a link to read more about this somewhere? I noticed the driver issue a little, for example it keeps showing the same time to charge no matter what the %.
I don't have a link, but basically most battery and charger related values are hardcoded in the oplus_chg driver, hence why charging always shows 1h24m (5000 seconds, to be precise) and why tools like Ampere and Accubattery produce seemingly nonsensical results. Other values like voltage, current, etc. are also hard coded to weird values. OOS doesn't use the provided driver, it's there for compatibility with AOSP but the values are all useless.
Not sure why you'd specifically look at git merge b-but ok. https://github.com/LineageOS/androi...pack/oneplus/power/oplus_chg/oplus_chg_intf.c is where you want to look.
Can you please point to what line of code you are referring to? I'm having a look and i can't find anything to support your claim.
Thank you!Not sure why you'd specifically look at git merge b-but ok. https://github.com/LineageOS/androi...pack/oneplus/power/oplus_chg/oplus_chg_intf.c is where you want to look.
Yes, though you'll need the MagiskHide Props Config and Universal SafetyNet Fix Magisk modules.Does root works and passes safetynet? I'm still in line for the Pixel 6 pro but this is taking forever and there's a sweet deal on the OP9Pro.
Do you have wireless calling or it's also not available for you? I ask because I can't get it to work on my op 9 pro, I'm also with VerizonI'm on Verizon, and I don't see the 5G icon on my status bar when connected to NR. I know it's working because apps like Network Signal Guru correctly show that I'm connected to 5G NR, and I am getting 5G speeds. I read that this is due to Verizon not sending something called an UpperLayerIndicator signal, however some phones show the 5G icon when connected to NR regardless of the presence of that signal. I was wondering if this could be fixed so that the status bar shows the 5G icon when connected to NR
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:
~/android/lineage$ breakfast lemonadep
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
frameworks/native/build/phone-xhdpi-6144-dalvik-heap.mk:19: error: _nic.PRODUCTS.[[device/oneplus/lemonadep/lineage_lemonadep.mk]]: "vendor/oneplus/sm8350-common/sm8350-common-vendor.mk" does not exist.
16:44:52 dumpvars failed with: exit status 1
Device lemonadep not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_oneplus_lemonadep
Default revision: lineage-19.1
Checking branch info
Checking if device/oneplus/lemonadep is fetched from android_device_oneplus_lemonadep
LineageOS/android_device_oneplus_lemonadep already fetched to device/oneplus/lemonadep
Syncing repository to retrieve project.
Fetching: 100% (1/1), done in 0.303s
Garbage collecting: 100% (1/1) finished LineageOS/android_device_oneplus_lemonadGarbage collecting: 100% (1/1), done in 0.004s
repo sync has finished successfully.
Repository synced!
Looking for dependencies in device/oneplus/lemonadep
Looking for dependencies in device/oneplus/sm8350-common
Looking for dependencies in hardware/oneplus
hardware/oneplus has no additional dependencies.
Looking for dependencies in kernel/oneplus/sm8350
kernel/oneplus/sm8350 has no additional dependencies.
Done
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
frameworks/native/build/phone-xhdpi-6144-dalvik-heap.mk:19: error: _nic.PRODUCTS.[[device/oneplus/lemonadep/lineage_lemonadep.mk]]: "vendor/oneplus/sm8350-common/sm8350-common-vendor.mk" does not exist.
16:44:54 dumpvars failed with: exit status 1
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
frameworks/native/build/phone-xhdpi-6144-dalvik-heap.mk:19: error: _nic.PRODUCTS.[[device/oneplus/lemonadep/lineage_lemonadep.mk]]: "vendor/oneplus/sm8350-common/sm8350-common-vendor.mk" does not exist.
16:44:54 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_lemonadep'
** Do you have the right repo manifest?
Yes.
There's always night somewhere in the world during the time they are compiled.Anyone know why the builds are still called "nightly" when you're lucky if you get more than one a week now?
We only claim to support retail devices. While carrier branded devices will likely work just fine, we don't have instructions for these nor do we guarantee them working.I noticed in the wiki that my LE2127 is not on the list of supported OP 9 Pro's. Any reason for this? Thanks