yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dr3am_r:
Does anyone have these problems related to Bluetooth ? :

1. While phone is connected to car bluetooth, car is getting information about battery level and cellular signal.

On Official Nougat, had no problems and worked perfectly.

On current rom and also AEX seems that phone is randomly sending cellular signal data, which translates to showing, on car Navigation, "searching for signal" although the phone has cellular signal. Problem is that sometimes car ends the phone call as it thinks phone has no signal.

2. Wear application connects properly to my Huawei watch, but as soon as I try to transfer my google account to the watch so that I can install applications on watch, wear application reports failure. Retries also fail.

Thanks for your inputs.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
This is incredible! I'm guessing that your implemention is different than the one currently posted?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Ugh, I was hasty. I feel confused today, please move this if it's not appropriate for here (it probably isn't), but I got stuck and I need to figure this out.

I installed TWRP 3.2.1-8-TREBLE despite having no intention of actually using Treble for now, because otherwise the latest (20180809) LineageOS 15.1 by Unjustified Dev was refusing to install on my previous TWRP. I assumed that it simply wouldn't use the vendor partition as I followed none of the steps to set it up.

Instead, it seemed to install a vendor partition too, and in the TWRP "Wipe" screen a Vendor partition was shown, but I couldn't install Unjustified Dev's vendor.img there by using Install Image, as the partition was not listed there (assuming that's the thing one is supposed to do, anyway), so I did nothing.

The ROM appeared to install successfully, but then I would be dumped back to the bootloader. I tried installing the official TWRP from twrp.me and then it would not even see my data partition. I tried NFound's TWRP 3.2.1-8-Oreo (i.e. not the Treble version?) and I could again "successfully" install the ROM, but then I'm dumped to the bootloader again.

I cannot install an older ROM (like 20180723) because it fails with error 7. Restoring a nandroid backup of the system image I used to have resulted in being dumped to the bootloader, too.

Is it that my (too small for Treble, but I guess existing) vendor partition was overwritten with stuff from the 20180809 ROM and now I simply lack some important stuff to boot?

Right now this phone is important because it's my primary means to access the internet. Yes, I know, I shouldn't have done this at 3am.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Always ask first the folder is explicitly named Ln15-treble. I'm not exactly sure why you're looping is the ROM the only thing you're flashing? If you never had a vendor partition prior to installing this update you should be ok and the vendor image is not needed I have it in case I messed up my vendor and needed the original files. Installing the ROM also extracts the vendor files to /vendor for you. If anyone else jumps, I'm sorry weren't ready to share it. It does work though for 8.1 builds we'll have a new vendor for P images with selinux enforcing on vendor image.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Selinux enforcing on 8.1 GSI.View attachment 4568404
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Encryption has always worked for me from the beginning that's why I got selinux enforcing before porting treble. Remember our implementation is different from his. And as far as I know all 8.1 GSI work I'm not using those P ROMs we'll build our own P that will support GSI with selinux enforcing.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
The GSI has nothing to do with selinux since they both have their own separate policy now since they split.

System has it's sepolicy and vendor has it's sepolicy. That's why I was so big on SELinux before treble because if we didn't fix it, that'll mean you'd always have to be permissive every GSI and that wouldn't make sense if we're enforcing on Lineage we want to be enforcing on a GSI as well even if it's P which is why we are providing a separate image for P.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
Agree - selinux and encryption are very important.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] okmikel:
Installed lineage-15.1-20180810-UNOFFICIAL-axon7.zip right now (created ventor partition before via AXON7_GPT_ADD_VENDOR_800MB.zip in EDL mode), and it boots and looks good so far with everything I tried till now. I have a A2017G. Next I will try is encryption :)

---------- Post added at 11:00 AM ---------- Previous post was at 10:08 AM ----------

Encryption is also working :)

But every time I boot, I get a message because of an outdated vendor partition. Reflashed lineage-15.1-20180810-UNOFFICIAL-axon7.zip and magisk again and message still there. But everything works so far, so I don't care about this message.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
Question for you-I'm on the build (thank you for your work!) and I'm getting a weird red/orange border flash up occasionally. I thought it was from strict mode or an accessibility setting, but none of those are on. Any ideas?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
It's an engineering build for me to debug wasn't a release. I've since uploaded a userdebug version if you want to dirty flash that one on top of it. The name didn't change
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
Got it! Have you had an opportunity to look into that Verizon volte question? It works in the beta but I can't get it to work with los. I can do any texting you need as I realize you aren't on Verizon.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Depends on how everything goes this week I may be able to squeeze in getting straight talk under Verizon. Pretty much budgeting my *donkey* off. That's the cheapest service I could find $35.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
I get the same outdated vendor partition message as well.

---------- Post added at 01:00 PM ---------- Previous post was at 12:59 PM ----------

Let me know. I can send you the $35. Does volte work on Verizon mvno partners now? I think it didn't work initially.

Revised used my brain and Google and found out it works. Let me know if the donation will help.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Talked to pageplus and total wireless they both do.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
Need to put your lingo in simple words. Does that mean you will be providing an Android pie ROM with enforcing mode that supports treble to make upgrade easy? That d be awesome
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Spudlinator:
Please help someone, may have bricked my phone!

So after stupidly trying to update twrp through twrp instead of fastboot, I can only access fastboot and the universal bootloader installed on the phone. If I don't do anything, the phone simply goes through universal bootloader and I see a small penguin before the screen goes back and I need to restart the phone again. However, in the bootloader I can select to go to fastboot which does work. I've tried flashing TWRP through fastboot (fastboot flash recovery twrp...) and it said success however after clicking 'reboot to recovery', the phone once again just boots to the bootloader and I'm back at square one. I've also tried this: https://xdaforums.com/android/software-hacking/guide-how-to-reboot-to-edl-fastboot-t3394292 tutorial on how to flash to edl however when I attempt it the phone still reboots to universal bootloader. No matter what I try everything always reboots to the bootloader and I'm always back at square one.

Thank you so much if someone here can help
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Yes, we will provide a Pie ROM and Pie vendor. You will be enforcing even after flashing a GSI.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
I didn't see the folder name, I got it from the "new uploads" list, call me dumb but AFH's layout has always confused me and I'm not very clear how things are organized.

I never knowingly had a vendor partition before this update, but I did install NFound's TWRP 3.2.1-8-TREBLE... I assumed that wouldn't, by itself (i.e. without doing any of the the EDL stuff), create a vendor partition, but maybe it does? because in the "Wipe" menu, a Vendor partition is listed with that version of TWRP.

Since I can access my data from recovery using either version of NFound's TWRP (by the way, the latest official TWRP, which I also tried, now doesn't recognize my data partition at all... not sure if that provides any hint on the situation), I will take a backup to the computer now, and then I guess I can try flashing your image from today... if that fails, any idea why trying to go back and flash older images (namely 7/23) gives me error 7 now?

I'm sorry; I know I shouldn't really have installed a random ROM that you didn't announce, especially not randomly in the middle of the night without a lucid mind. I don't fully know why I did it, honestly.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
no that wouldn't create a vendor partition. flash the provided vendor partion zip through miflash, then you can flash this rom. i ended up doing a complete wipe, doing the vendor miflash, and then flashing.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
The lineage zip itself already partitions the device for you. If you have a vendor partition already it skips creating one for you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Wolfblade1215:
Is the 20180810 build stable?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I wouldn't flash it is you don't want a vendor partition. Shouldn't be much different from previous release
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Well, I didn't/don't really want to repartition and create a Vendor partition, I'm not ready for that right now, especially not to wiping Data... I simply thought this would work without one, too, but it looks like I was wrong.

Do I have a realistic chance to just go back to the 23/7 build and undo whatever damage I did? If I simply try installing that from NFound's TWRP now (either the -Oreo or the -Treble version), I get error 7, and neither did trying to restore my Nandroid backup result in a working phone. Right now I'd just like to know a way to go back to where I was before I did this.

---------- Post added at 07:51 PM ---------- Previous post was at 07:49 PM ----------

Confirming: does that mean that unless I want to manually "un"-partition now, my best chance now to get anything to boot is to use your build from today, rather than attempting to go back to the 23/7 build or another build prior to Vendor stuff?

And if so, anyway, which TWRP version would you favor using for that?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Try the new build out what is your base stack? B12?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
The new build didn't do the trick, either, at least when installed from TWRP 3.2.1-8-Oreo (I suppose I'm going to try 3.2.1-8-TREBLE next). My bootstack is, err... the one linked at the start of this thread, i.e. I got it from here, but I'm not entirely sure the files currently there are the ones that were there originally? (especially ZTE_A7LOSv1_UniversalBootStack.zip which says it was uploaded in June). My model is A2017G, I can at least tell that much, and I have a file named ZTE_A7_UniversalBootStack.zip in my downloads dated 7 June (and also a A2017X_B15_Universal_Bootloader.zip but that's from January so I assume that's not it).

Is there a reliable way to know the installed version of this stuff (modem, bootstack...) from recovery or fastboot? I've googled a bit but couldn't figure it out.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
And you never installed any other treble builds before?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
No, I've been on this thread's LineageOS 15 (lately your 23/7 build) for a while, and before that, I was on the official LineageOS 14.1. The only "Treble"-thing I installed was NFound's Treble-enabled TWRP before installing your debug build from yesterday.

My fastboot, on the emergency boot screen, does list "BOOTLOADER VERSION" and "BASEBAND VERSION" but they're, well... empty. They don't actually mention a version. :eek:

Namely, in case this has anything useful, what it says in full is:

Press volume key to select, and press power key to select

FASTBOOT MODE

PRODUCT_NAME - AILSA_II

VARIANT - MTP eMMC

BOOTLOADER VERSION -

BASEBAND VERSION -

SERIAL NUMBER - [withheld]

SECURE BOOT - enabled

DEVICE STATE - unlocked

... ah, there is hope! I wiped /system a bunch more times (I had it mounted, then unmounted, I'm not really sure which way it should be, but after I wiped it in both states, your ROM from today installed).

Now it booted and it's about to ask me for the PIN, but it says "Android system: A vendor image mismatch has been detected. Typically this means your vendor image is out of date. Please ensure your vendor image matches OPR1.170623.032."

Maybe this is to be expected, but worth mentioning. Anyway I just hit OK and I'm in my system with data intact.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Did you factory reset (not wipe data)? How long does it take to go back into the bootloader? Is it instantly? Are you flashing the ROM with read only system checked under mount?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Well, now it's working (see previous post, which I edited to update), so I can't answer all those questions anymore maybe, but:

I did not factory reset; what I usually do is go to Advanced Wipe and select Dalvik / ART, System, and Cache. Factory reset or data wiping was something I was wanting to avoid if possible (it doesn't wipe internal storage but it does still wipe data, right?)

It went to the bootloader instantly, provided we aren't counting the ~5 seconds it takes to warn me I'm unlocked.

No, "Mount system partition read-only" isn't selected, but right now, System is not selected for mounting in the first place (Cache and Data are), and I think that before when things weren't working, it was... or, well, or the other way around :confused:

I'm just answering anyway in case it helps clarify things for you and others, as I'd say my personal emergency is over. I just get that "vendor image mismatch" message on every boot, for now that seems to be the only indication of anything unusual.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I'll work on fixing that message soon enough and glad you got it working you are now treble enabled and if you want you can install other 8.1 GSI. It's still a WIP though I had no issues with RR GSI.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Well, thanks for helping me. I was intending to make a small donation (unemployed here) only once this gets upgraded to official LineageOS, but I guess it's fair that I should take the chance now while I'm not breaking my phone/internet yet again to open PayPal.

One thing I'm not sure I understand about GSI because I haven't really followed Treble closely: is the general idea that, eventually, LineageOS itself (and other ROMs) will be GSIs, and device-specific maintainers like you will eventually just release appropriate Vendor partitions (if/when needed at all because of important changes between major versions)? And, basically, LineageOS itself will become just one download, or at most one per arch type?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kleva94:
I tried out todays build as well. Only thing i noticed so far is the way to strong vibation on incoming massage notifications.

Thanks a lot for your work [MENTION=4911249]Unjustified Dev[/MENTION] and the others who are involved. You help me to keep this phone for as long as i never did with another one.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
Thank you for all your work. I am getting confused a bit. It seems we now have 2 ways to treblerize our A7: your's and NFound's. If I understand correctly, with the correct bootstack (12) and the latest official twrp, flashing your latest zip will create the vendor partition. This will support selinux enforced and encryption, even on RR GSI?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
I don't know why this is or if it's something that can be a problem for others, but since you mention the official TWRP, I want to restate that after using NFound's versions (not blaming them, no idea what the reason is, just saying I've used them), now the latest official TWRP simply sees my Data partition as 0 bytes, and won't mount it, so it's more or less unusable for anything. Maybe it'd work after I reformat it from there, though, but that's not something I'm going to try right now.

Saying just in case you get scared seeing a seemingly empty data partition! Going back to the NFound TWRP made it reappear, so it definitely wasn't gone, so it shouldn't be dangerous to install the official one over NFound's ones, I guess, as it's reversible at worst.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Yes, the way they are doing the vendor is creating an 800mb partition that's way too much ours is only 512mb and if you tried to flash his full image in bytes it wouldn't work since it would copy the full 800mb and try to fit in our 512mb partition.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
Fascinating stuff. So, we now need to start comparing vendor partitions for size, selinux support, encryption support, bugs?

After next week I have time to start treblerizing my pbone. Anytbing in particular I need to test? I have a A2017G with dual sim and 128G sdcard.

Also, if I first create a 800 MB vendor partition, will your zip just write 512M of that or will it shrink it?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Maybe nobody else cares about this because you're all using GMail or K-9 Mail, but, for me, there's a small gem in this 8.1 that I've wanted for a really long time: the standard Email app supports IMAP Push!

I found out because you get a prompt to let it run in the background to allow that. Then when you set up an account you also have to explicitly set it to "Automatic (Push)" instead of the default 15 minutes check.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Zobat:
So this means i dont need edl (windows) and i can create trebble (vendor) partion from within twrp and it will boot?

Thank you!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
Does the zip carve vendor out of system or out of data?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
System that way you don't have to lose data.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
If anything I'll have it check the size of vendor first and fail to install if it's not 512mb.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] atakan33:
if you want 800 mb vendor partition ,nobody has a problem :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
Anyone have an issue getting safetynet to pass with magisk 16.7 on the new release?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Shouldn't need more space we barely use any now and we'll probably be cleaning up more unused arch blobs like some services run in 32 bit and some 64 you don't need both 32 and 64 libraries to run that said service. And ZTE will never provide a new bootloader with fastboot I'm the only reason we have an Oreo bootloader with fastboot or vendor support. I got it from a Dev build ZTE sent when Oreo first went beta. Talking with R&D they don't plan on shipping fastboot or anything else again they are pretty much locking down the device. You won't even be able to oem unlock anymore if you never did.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Wow... the ban got them upset even if it was (maybe) lifted, didn't it?!

So wait... if you're shipping something that ZTE gave you but aren't themselves planning to ship or support, doesn't that pretty much mean that they won't give you permission to publish whatever source is needed to make this LineageOS official? As I understood it you were still waiting for a "go ahead" from them for some things...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] AxonVeezy:
OK so... Sorry I'm a little lost. Does this mean I can now install treble after installing the 8-10 build?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] AxonVeezy:
I get the same menu after installing Magisk. Had to do a wipe to get back.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Raffikie:
Where are these treble files, not seeing what you guys are talking about with the vendor files and the latest build. Can someone point me to the files, thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
https://androidfilehost.com/?w=files&flid=280287
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Raffikie:
Thanks mate, where is the post that deals with deals files that indicate the instructions and explanations?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Guido83:
Do I understand it right that this treble method which is used here differentiate from the one that was initiated by NFound? from my understanding nfounds method uses 800mb for vendor partition from the sd card storage wheras here it is taken from the system partition. Am I right?

If so, it is better to switch?

I am a little confused.. thanks for clarifying i. a.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
So far, it seems there are at least 3 differences:

Size: this one: 520MB; Nfound: 800MB.

selinux: this one: can enforce. NFound: cannot.

encryption: this one: supports. NFound: does not.

Not clear to me:

a) how can you switch if you wanted to. I am not even sure if you start with, say, 520MB, whether you can then change to 800MB or vice-versa.; and if so, what is the method?

b) Also not clear: if you install this vendor partition, then can you run an NFound ROM?

c) For both vendor partitions: which GSIs will run without too much problem?

d) whether you need the -treble TWRP or whether the latest standard one is OK?

Maybe better to start a separate Q&A thread as this is slightly OT for lineageos15.1.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] blu3wh0:
FYI, I had to use Magisk 16.7 to consistently boot into the ROM. Unfortunately, this version doesn't pass SafetyNet and I haven't figured out a way to fix that yet.

I ran into numerous random reboots on the July versions of LineageOS 15.1, most frequently when it's under heavy use (Waze + Audible) and charging, so I decided to try this not-ready-for-release version with Treble. I haven't had the chance to use it like I regularly do for when it reboots, but I'm hoping that problem is alleviated. Are there kernel fixes with the latest ZTE delivery in this build? I remember some mentions that the kernel had to be hacked together for it to work for us.

Thank you for Treble and your continuous work on this project!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
I did originally have Magisk installed, so it might have been that... it's just that I thought I had wiped /system so many times, Magisk could no longer be there, plus that this ROM formatted /system to make space for /vendor anyway... but now I'm no longer so sure. Either I completely can't use TWRP, or Magisk is... very persistent. :eek:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Because Magisk also patches the boot.img.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Raffikie:
Any instructions on how to install the vendor file and image?