yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi A1 Guides, News, & Discussion] TheButti:
The Same as Initial

Do a repo Sync !

type "rm -rf out"

then brunch again
[Xiaomi Mi A1 Guides, News, & Discussion] ManojNairOnline:
Getting an error after downloading the files mentioned above.....

including vendor/lineage/vendorsetup.sh

build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/xiaomi/tissot/lineage.mk]]: "vendor/xiaomi/msm8953-common/msm8953-common-vendor.mk" does not exist. Stop.

Device tissot not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).

Found repository: android_device_xiaomi_tissot

Default revision: android-8.1.0_r33

Checking branch info

Default revision android-8.1.0_r33 not found in android_device_xiaomi_tissot. Bailing.

Branches found:

lineage-15.1

Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.

build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/xiaomi/tissot/lineage.mk]]: "vendor/xiaomi/msm8953-common/msm8953-common-vendor.mk" does not exist. Stop.

build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/xiaomi/tissot/lineage.mk]]: "vendor/xiaomi/msm8953-common/msm8953-common-vendor.mk" does not exist. Stop.

** Don't have a product spec for: 'lineage_tissot'

** Do you have the right repo manifest?

No such item in brunch menu. Try 'breakfast'

Please can you let me know what is it that I am missing?

thanks in advance

Manoj
[Xiaomi Mi A1 Guides, News, & Discussion] arunassain:
Its error due to official tree of tissot available in los so it will replace one posted in OP and so better use official tree for ur use

i will update the tree now
[Xiaomi Mi A1 Guides, News, & Discussion] ManojNairOnline:
Thanks Arun. Appreciate the response :)

Manoj.
[Xiaomi Mi A1 Guides, News, & Discussion] ManojNairOnline:
Finally built my first custom ROM, flashed it on my MiA1 and it runs!!!! :D A big thanks to Arun for all the support and the instructions.
[Xiaomi Mi A1 Guides, News, & Discussion] ManojNairOnline:
Hi,

Had a query if we build a ROM using this method can we share it with our friends having the same mobile phone - MiA1. Does the build require to be signed or is any process to be followed before sharing with others.
[Xiaomi Mi A1 Guides, News, & Discussion] arunassain:
Yup u can share this ROM but don't share it in XDA bcz these builds are already done by many developers and u will face issue this thread for reference of building ROMs and los is easy to build but others source errors will occur so u need to fix that and build so better learn first

Thanks:)
[Xiaomi Mi A1 Guides, News, & Discussion] ManojNairOnline:
Thanks for the response Arun. Will follow your advice.
[Xiaomi Mi A1 Guides, News, & Discussion] dback31:
Hey, I'm currently trying to build unofficial LOS 15.1 with the device tree and kernel source from the Lineage GitHub.

https://github.com/LineageOS/android_device_xiaomi_tissot

https://github.com/LineageOS/android_device_xiaomi_msm8953-common

https://github.com/TheScarastic/proprietary_vendor_xiaomi (not sure if this is needed, however I cloned it into vendor/xiaomi :))

After I type "brunch tissot" I get the following error

[44/44] bootstrap /home/luis/android/l...ut/soong/.minibootstrap/build.ninja.in
[4/4] /home/luis/android/lineage/out/s...neage/out/soong/.bootstrap/build.ninja
[872/873] glob vendor/qcom/opensource/interfaces/wifi/*/Android.bp
[56/56] /home/luis/android/lineage/out.../android/lineage/out/soong/build.ninja
/home/luis/android/lineage/out/build-lineage_tissot.ninja is missing, regenerating...
[133/1084] including ./device/xiaomi/tissot/Android.mk ...
[B]build/core/base_rules.mk:238: [COLOR="Red"]error:[/COLOR] device/xiaomi/tissot/rootdir: MODULE.TARGET.ETC.init.tissot.rc already defined by device/xiaomi/tissot/rootdir.[/B]
17:45:20 ckati failed with: exit status 1

[COLOR="red"]#### failed to build some targets (34 seconds) ####[/COLOR]

Can you help me to fix this please? :)

Edit: In ~/android/lineage/device/xiaomi/tissot/rootdir/android.mk I changed

include $(CLEAR_VARS)
LOCAL_MODULE := init.tissot.rc
LOCAL_MODULE_TAGS := optional eng
LOCAL_MODULE_CLASS := ETC
LOCAL_SRC_FILES := init.tissot.rc
LOCAL_MODULE_PATH := $(TARGET_OUT_VENDOR_ETC)/init
include $(BUILD_PREBUILT)

to

#include $(CLEAR_VARS)
#LOCAL_MODULE := init.tissot.rc
#LOCAL_MODULE_TAGS := optional eng
#LOCAL_MODULE_CLASS := ETC
#LOCAL_SRC_FILES := init.tissot.rc
#LOCAL_MODULE_PATH := $(TARGET_OUT_VENDOR_ETC)/init
#include $(BUILD_PREBUILT)

and now it seems to work :)

Edit 2: Now I'm getting this error

[ 5% 5085/99598] Lex: applypatch <= bootable/recovery/edify/lexer.ll
FAILED: /home/luis/android/lineage/out/target/product/tissot/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp
/bin/bash -c "prebuilts/misc/linux-x86/flex/flex-2.5.39 -o/home/luis/android/lineage/out/target/product/tissot/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp bootable/recovery/edify/lexer.ll"
flex-2.5.39: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
Aborted (core dumped)
[ 5% 5090/99598] target StaticLib: libv8src (/home/luis/android/lineage/out/target/product/tissot/obj/STATIC_LIBRARIES/libv8src_intermediates/libv8src.a)
ninja: build stopped: subcommand failed.
20:37:34 ninja failed with: exit status 1

[COLOR="Red"]#### failed to build some targets (11:44 (mm:ss)) ####[/COLOR]

Edit 3: Seems like this is an issue with Ubuntu 18.04 which is fixed by entering "export LC_ALL=C" before the build command.
[Xiaomi Mi A1 Guides, News, & Discussion] ahadrox:
Just wanted to know that can I build Oreo roms properly / without any problems in this pc configuration?

intel i7 8700 (Non K)

gigabyte aorus B360M gaming 3 motherboard

8GB DDR4 2400MHz RAM

1TB 7200 RPM Hard Drive

120GB SSD (For installing the OS)
[Xiaomi Mi A1 Guides, News, & Discussion] dback31:
I'm building with

i5-4670

8GB DDR3

250GB SSD

1TB HDD

If you want to build on your SSD you might need more disk space, but if you build on your HDD then go for it :)

First build takes about 4-5 hours for me, after that around 2 1/2 hours :)

Edit: I recommend you to build on Ubuntu 16.04 as I had errors on 18.04
[Xiaomi Mi A1 Guides, News, & Discussion] ahadrox:
So, if I go with HDD, how many hours do I gona needed?
[Xiaomi Mi A1 Guides, News, & Discussion] dback31:
Can't tell you, I built on my SSD without ccache compression and had about ~20GB space left.

I first tried to build on my HDD but had errors with 18.04 and started clean on my SSD with 16.04

From what I observed it was significantly faster on my SSD though
[Xiaomi Mi A1 Guides, News, & Discussion] ahadrox:
Okay, thanks for the information :)
[Xiaomi Mi A1 Guides, News, & Discussion] ManojNairOnline:
Update: [MENTION=6768248]arunassain[/MENTION] Please ignore my question below. I was able to get my build working with the latest source code. Looks like some test keys have been added in the source which lets the ROM boot.

Thanks all the same for this wonderful article. I learnt my abc of ROM building from this article!!!.

regards,

Manoj

[MENTION=6768248]arunassain[/MENTION] had a question. I was trying to build this ROM again with the latest source code. The build completes successfully the ROM booted but it does not go into the setup screens. The lineage animation keeps looping. Is it not possible to build unofficial versions of the ROM after it has been made official. I was wondering if the code is now checking if the ROM is signed before starting the setup. Never had this problem earlier...before July 21 (i think it went official around then). The earlier builds from the same source used to work perfectly for the tissot.

Thanks in advance.
[Xiaomi Mi A1 Guides, News, & Discussion] KiD3991:
How do you make it flashable though?

Like just find a zip file and just throw all the .img from the out folder? Or what? I am very new to this.
[Xiaomi Mi A1 Guides, News, & Discussion] saski4711:
Trying to compile current Resurrection Remix ROM for TISSOT. Had no problems building the ROM so far. After epo sync now I get this when I breakfast :

build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/xiaomi/tissot/rr.mk]]: "frameworks/native/build/phone-xxhdpi-3072-hwui-memory.mk" does not exist. Stop.

build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/xiaomi/tissot/rr.mk]]: "frameworks/native/build/phone-xxhdpi-3072-hwui-memory.mk" does not exist. Stop.

** Don't have a product spec for: 'rr_tissot'

** Do you have the right repo manifest?

Any Idea what happened?
[Xiaomi Mi A1 Guides, News, & Discussion] ProchyGaming:
I've been getting this, tho I'm sure it has nothing to do with the rom not building "Trying dependencies-only mode on anon-existing device tree?" What does this even mean? And another thing I'm getting all the time is this "/root/simplix/out/build-simplix_tissot.ninja is missing, regenerating..."
[Xiaomi Mi A1 Guides, News, & Discussion] Anticolick:
How can i fix it ?

build/core/base_rules.mk:238: error: device/xiaomi/msm8953/data-ipa-cfg-mgr/hal: MODULE.TARGET.SHARED_LIBRARIES.liboffloadhal already defined by device/xiaomi/msm8953-common/data-ipa-cfg-mgr/hal.

23:52:20 ckati failed with: exit status 1

#### failed to build some targets (02:02 (mm:ss)) ####
[Xiaomi Mi A1 Guides, News, & Discussion] arunassain:
There is two data-ipa-cfa-mgr so better remove one and build it
[Xiaomi Mi A1 Guides, News, & Discussion] Mirdeusz:
Is it possible to build older versions of android? My fav cm 11 for ex. Thanks.

Wysłane z mojego MI A1 przy użyciu Tapatalka
[Xiaomi Mi A1 Guides, News, & Discussion] arunassain:
Not even possible and KitKat in a1?
[Xiaomi Mi A1 Guides, News, & Discussion] sdeft:
[MENTION=6768248]arunassain[/MENTION]

Just want to clarify the differences between android_device_xiaomi_msm8953-common and android_device_xiaomi_tissot.

Are you building crdroid with both trees or only one of them ?
[Xiaomi Mi A1 Guides, News, & Discussion] arunassain:
See there is two DT one which is official and another made by team Oreo and now official tree mentioned in OP

crDroid was build by team Oreo tree
[Xiaomi Mi A1 Guides, News, & Discussion] sdeft:
Yes I understant this but do you also use msm8953-common ?

Can you post your roomservice file here for reference.
[Xiaomi Mi A1 Guides, News, & Discussion] arunassain:
https://github.com/arunassain/local_manifest/tree/tissot?files=1
[Xiaomi Mi A1 Guides, News, & Discussion] Doom_94:
Hi [MENTION=6768248]arunassain[/MENTION], one question: why did you write for the kernel part in the op "kernel/xiaomi/msm8953 and in your manifest you wrote kernel/xiaomi/tissot? Thank you :)

Inviato dal mio Mi A1 utilizzando Tapatalk
[Xiaomi Mi A1 Guides, News, & Discussion] Doom_94:
Btw, i'm trying to build crDroid Pie for tissot. It's building now, it is at 7%. It is normal that it generates some warnings?

Inviato dal mio Mi A1 utilizzando Tapatalk
[Xiaomi Mi A1 Guides, News, & Discussion] arunassain:
Yeah its Normal but don't use my tree for pie bcz I didn't update for pie in OP so use official tree from los
[Xiaomi Mi A1 Guides, News, & Discussion] Doom_94:
I'm using the lineage-16.0 tree from the scarastic (abhishek987). It is ok? Btw my build gives error at 99%, could you help me out? Thank you :)

Inviato dal mio Mi A1 utilizzando Tapatalk
[Xiaomi Mi A1 Guides, News, & Discussion] arunassain:
Source error so I can't help but post ur error in crDroid community in telegram lead dev will help you
[Xiaomi Mi A1 Guides, News, & Discussion] Doom_94:
Ok, thank you:)

Inviato dal mio Mi A1 utilizzando Tapatalk
[Xiaomi Mi A1 Guides, News, & Discussion] sdeft:
ok so you don't use the crdroidandroid/android_device_xiaomi_msm8953-common at all. Just your own device tree.

Is there any reason why you use the TissotDevelopment vendor tree and not yours ?
[Xiaomi Mi A1 Guides, News, & Discussion] arunassain:
Wait u can use my vendor tree and device tree but not kernel tree bcz I made a derp over it
[Xiaomi Mi A1 Guides, News, & Discussion] sdeft:
if I use your vendor tree there are errors ...fixable of course..

how does your device differ from the other one you posted ?
[Xiaomi Mi A1 Guides, News, & Discussion] saski4711:
Hi there,

I've been trying to build LOS16 from source with flex911's sources however I've hit a snag about missing header files like:

hardware/qcom/audio-caf/msm8996/hal/platform_api.h:22:10: fatal error: 'sound/voice_params.h' file not found
hardware/qcom/audio-caf/msm8996/hal/acdb.h:24:10: fatal error: 'linux/msm_audio_calibration.h' file not found

so I guess something is missing im my roomservice.xml

<manifest>
<!-- Default -->
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0"/>
<project name="Flex1911/android_device_xiaomi_tissot" path="device/xiaomi/tissot" remote="github" revision="lineage-16.0-4.9"/>
<project name="Flex1911/android_device_xiaomi_msm8953-common" path="device/xiaomi/msm8953-common" remote="github" revision="lineage-16.0-4.9"/>
<project name="Flex1911/android_kernel_xiaomi_msm8953-1" path="kernel/xiaomi/msm8953" remote="github" revision="lineage-16.0-4.9"/>
<!-- Xiaomi Proprietary Blobs -->
<project name="Flex1911/proprietary_vendor_xiaomi" path="vendor/xiaomi" remote="github" revision="lineage-16.0"/>
</manifest>

First thought was about missing commons:

<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-16.0"/-->

but after adding this to my roomservice shows that LOS doesn't seem to have this branch anymore:

Fetching projects: 99% (709/716) Fetching project LineageOS/android_hardware_qcom_audio
Fetching project LineageOS/android_hardware_qcom_display
Fetching project LineageOS/android_hardware_qcom_audio
Fetching project LineageOS/android_hardware_qcom_display
Fetching project LineageOS/android_hardware_qcom_audio
fatal: Couldn't find remote ref refs/heads/lineage-16.0

Any idea what I've been missing? Probably something stupid I guess ;)
[Xiaomi Mi A1 Guides, News, & Discussion] saski4711:
Ok I am one step closer. It seems my roomservice was missing some entries:

<!-- Remove Default projects -->
<remove-project path="hardware/qcom/audio-caf/msm8996" name="LineageOS/android_hardware_qcom_audio"/>
<remove-project path="hardware/qcom/display-caf/msm8996" name="LineageOS/android_hardware_qcom_display"/>
<remove-project path="hardware/qcom/media-caf/msm8996" name="LineageOS/android_hardware_qcom_media"/>

<!-- Default -->
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0"/>
<project name="Flex1911/android_device_xiaomi_tissot" path="device/xiaomi/tissot" remote="github" revision="lineage-16.0-4.9"/>
<project name="Flex1911/android_device_xiaomi_msm8953-common" path="device/xiaomi/msm8953-common" remote="github" revision="lineage-16.0-4.9"/>
<project name="Flex1911/android_kernel_xiaomi_msm8953-1" path="kernel/xiaomi/msm8953" remote="github" revision="lineage-16.0-4.9"/>
<!-- Xiaomi Proprietary Blobs -->
<project name="Flex1911/proprietary_vendor_xiaomi" path="vendor/xiaomi" remote="github" revision="lineage-16.0"/>

<project path="hardware/qcom/audio-caf/msm8953" name="Flex1911/android_hardware_qcom_audio" revision="lineage-16.0" remote="GitHub"/>
<project path="hardware/qcom/display-caf/msm8953" name="Flex1911/android_hardware_qcom_display" revision="lineage-16.0" remote="GitHub"/>
<project path="hardware/qcom/media-caf/msm8953" name="Flex1911/android_hardware_qcom_media" revision="lineage-16.0" remote="GitHub"/>

No Idea if the removal of default projects is needeed but with that setting the ROM builds without errors. After flashing unfortunately it doesn't boot up at all.

It seems that there are still some msm8996 SOONG namespaces selected and I cannot figure out how to set them to our msm8953 profile:

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
LINEAGE_VERSION=16.0-20181201-UNOFFICIAL-tissot
TARGET_PRODUCT=lineage_tissot
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=cortex-a53
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.20.0-rc4-drmtip+-x86_64-Gentoo/Linux
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=PQ1A.181105.017.A1
OUT_DIR=/mnt/extended/android/lineage-16/out
PRODUCT_SOONG_NAMESPACES= hardware/qcom/audio-caf/msm8996 hardware/qcom/display-caf/msm8996 hardware/qcom/media-caf/msm8996
TARGET_USE_SDCLANG=true
============================================

I'm out of ideas :(.

Never mind got it working :)
[Xiaomi Mi A1 Guides, News, & Discussion] bluejeans117:
Can we use the device tree from the above links, to build an AOSP ROM, instead of Lineage? :confused: I'm trying to compile a ROM, which isn't Lineage :/
[Xiaomi Mi A1 Guides, News, & Discussion] babakhad:
hi

where i could found the device-specific code for line age 17 unofficially

should i use it from lineage 16???

thanks
[Lenovo ZUK Z2 (Plus) Guides, News, & Discussion] NetsKing:
Great info , thanks :fingers-crossed:
[Lenovo ZUK Z2 (Plus) Guides, News, & Discussion] sanketp60:
Cypher OS Oreo download link please! :)
[Lenovo ZUK Z2 (Plus) Guides, News, & Discussion] Avan7:
Sure! It has the 'Now Playing' feature, really neat.

Download

Thanks to the Lenovo ZUK Z2 - Portal Telegram group for the link.
[Lenovo ZUK Z2 (Plus) Guides, News, & Discussion] STARK0711:
Any bug around there in that rom?
[Lenovo ZUK Z2 (Plus) Guides, News, & Discussion] amit gaikwad:
suggestion for best gaming and battery friendly rom.
[Lenovo ZUK Z2 (Plus) Guides, News, & Discussion] Avan7:
Actually I just installed and ran the benchmarks right away, so I couldn't really say about bugs or share an overall experience.

I think the most battery friendly ROM would be stock. However custom ROMs keep improving, so that's awesome. Other than that, this was just an experiment to get some numbers therefore I can't really say about battery.

There are so many factors, like battery drain on light and moderate usage and heavy CPU and/or GPU usage, deep sleep, hpereat, stability, user experiencie, etc.

It is hard to measure these with benchmarks alone.
[Lenovo ZUK Z2 (Plus) Guides, News, & Discussion] crazyguns:
Fascinating post, thank you for doing this!! I just bought this device for 7k refurb (approx 100$), should easily last a year or more.

Would it be possible to do a run with the Pixel Experience rom? Or is that one similar to the other ones you've already done? Just doing my research on this device and the various roms, its blowing me away how much horsepower exists in this thing for the low price!
[Lenovo ZUK Z2 (Plus) Guides, News, & Discussion] sanketp60:
Whats Citrus 3.5 OC?

Link Anyone?
[Lenovo ZUK Z2 (Plus) Guides, News, & Discussion] frozenfirevr:
Thanks for the comparison. But I was wondering, AEX is arguably the most popular ROM for Z2, so why skip that one?
[Lenovo ZUK Z2 (Plus) Guides, News, & Discussion] seking:
+1
[Lenovo ZUK Z2 (Plus) Guides, News, & Discussion] Avan7:
Citrus 3.5 by miju but with an OC applied with the custom Kernel Adiutor for the Z2 :)

I understand and the reason is that I decided to try a batch of ROMs I hadn't tried before. I wanted to try many more, but time didn't allow it. Perhaps sometime close I'll do another run :fingers-crossed:
[Lenovo ZUK Z2 (Plus) Guides, News, & Discussion] Glifaus:
Very interesting! Thanks for your time.

Im considering to flash jaguar... im now on aex 5.2 but seems that jaguar is smoother and run good. Waiting for new latest builds to test this two and decide.
[Lenovo ZUK Z2 (Plus) Guides, News, & Discussion] frozenfirevr:
Cool, thanks. :D Mind sharing your experience with each of the ROM also, if you spent any time with them? Have you chosen any one?
[LG V30 Questions & Answers] KanBorges:
I'm so tired of LG putting the same damn code name for different reasons. So I'll just ask here. I know the v30+ from B&O is the US998. But US Cellular also has their own US998. My question is, Is the US Cellular one already unlocked or do I have to pay for the unlock? Also, is the bootloader unlockable? I've seen the US998 unlock and root thread but does that work on the US Cellular one? I remember the whole G5 debacle where LG gave the same code name to 2 different carriers and one was unlockable and the other was not. Thanks in advance, this is just very frustrating for me. I love LG but sometimes....
[LG V30 Questions & Answers] Septfox:
The US Cellular one is SIM-locked as I recall, and like any carrier phone would need to be paid off and an unlock requested. The bootloader is not unlockable officially and no exploit has been found to do so, though people are looking into it.

The Open Market US998 should be SIM unlocked from the start, and the bootloader can be unlocked on the LG dev site (though last I heard, you need to temporarily edit the page to add the phone model to the drop-down list).

So yea, exact same model number idiocy as before.

The US998+ is not yet bootloader-unlockable, it's currently in the same boat as the USC US998. If you want bootloader unlock for sure, grab yourself the normal Open Market V30. Spend the extra money you would have given LG and get a big SD card and decent case, instead.
[LG V30 Questions & Answers] ChazzMatt:
No, the U.S. Cellular V30/V30+ is not sim-card locked/carrier locked/network locked. It's the "unofficial" carrier unlocked model. It's identical to the open market US998 in every respect except not eligible for bootloader unlock. (Well, neither is the open market V30+ at this point in time.)

Many people in this forum have bought the U.S. Cellular US998 and are not on U.S. Cellular. No unlock codes needed. See

this thread, and search for "Cellular".

I've posted about it since October...

LG V30 Sim Unlock Code

https://xdaforums.com/lg-v30/help/lg-v30-sim-unlock-code-t3665928/post74146985#post74146985

https://xdaforums.com/showpost.php?p=74198864&postcount=45

But unless you were getting a fantastic deal on an U.S. Cellular model and you didn't care about bootloader unlock at all (even in the future), the best bet is the open market US998 V30.
[LG V30 Questions & Answers] KanBorges:
Can confirm it is sim unlocked as said by [MENTION=3250376]ChazzMatt[/MENTION]. I wanted the open market US998, but I could not pass up the deal on this brand new one. Thank you guys for the help. I'll just wait patiently until this bootloader gets unlocked. Or maybe never. :rolleyes:
[LG V30 Questions & Answers] darkthugs:
so they are coming out the box sim unlocked right?also they are saing that models newer than the s6 come unlocked,any experience with it?
[LG V30 Questions & Answers] KanBorges:
I bought the US Cellular version and I'm using it for ATT straight out of the box.
[LG V30 Questions & Answers] darkthugs:
Does anyone believe esn status could affect it ?? Since i am looking to buy one on ebay New but bad esn ,since they are not released on my country ,obviusly i have checked bands
[Nexus 6P Q&A, Help & Troubleshooting] UgiPletzet:
Hi,

I've recently upgraded from N to O (8.1 OPM5, rooted), and ever since then I have no LED notifications at all.

Things done:

1. Enabling "Blink light" in notification settings.

2. Enabling/Disabling the "Ambient display" setting.

3. Checking w/ GravityBox' UNC (I have the pro version).

4. Checking w/ 3rd parties like LightFlow and Light Manager.

None of these worked, and the LED was never on at any color. When using Nougat I had no problem with it.

Any ideas?

Thanks.