yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BlueSwordM:
One last problem I got.

I flashed 3.2.1.8 of course, flashed The Axon 7 GPT ADD VENDOR partition file, but no vendor partition appeared.

I then tried Oki's command, but it didn't work. Is that normal?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
No sim detected can be easily solved. Just go to settings > network > SIM cards and select your sim card as the preferred one for sms, calls and data. I only saw face unlock not supported in the latest treble implementations that worked before. Sim was working fine.

To revert back just flash the previous rom. It doesnt matter whether it is a treble rom or a full rom just flash the zip as usual. You can keep the latest TWRP if you want.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DarkQuark:
I am not sure why you decided to jump into a small fire with a can of gas but I disagree. Nfound has been doing great work here for some time and deserves some respect. I am not certain what the scuffle is about but let's all just be respectful and not fan the flames. My 2 cents.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] alwynjoshy:
Hi on Rr or Aex none of the bank applications workng, for TCf bank app only shows white screen. on discover credit card application waning shows OUTDATED OS DETECTED
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Vaga Liki:
[MENTION=5492451]NFound[/MENTION] is there any way we can get file-based encryption (direct boot) instead of full-device encryption?

My company policy requires encryption but full-encryption is annoying and means alarm clock doesn't work if phone is dead.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choobilsky:
Updated my A2017CN to Havoc Treble today without issues; restored data following [MENTION=319057]Oki[/MENTION]'s guide. Thx [MENTION=5492451]NFound[/MENTION] and [MENTION=319057]Oki[/MENTION]. You're a great team ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Are you referring to this guide? I thought I had lost my time and no-one benefited from keeping the data and internal storage while Treblerizing their Axon 7.

---------- Post added at 09:33 ---------- Previous post was at 09:13 ----------

I haven't seen the source of any Oreo ROM in this thread, not even the old releases.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choobilsky:
Yes, I was referring to this water-proof guide. Great job! Had to wipe dalvik/cache only after formatting data and vendor partition - in addition to your steps - to go on, but it felt like on autopilot.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Thanks for the missing step. Added to the guide.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Spooderman46:
A Virtual Machine might be your safest bet mate.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Did you flash using MiFlash? Did it complete the operation?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TPMJB:
Hey, sound is broken again with encryption on latest AEX

Edit: Havoc just doesn't even boot at all with Treble either.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BlueSwordM:
Ok. Now I was able to install everything for some reason.

Wonder what I did wrong. MiFlash worked fine twice, but the 1st time did something to **** something up.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Infy_AsiX:
well there's the extra 50% cpu load on headphones with builds for over a month, related to the same process. Been discussed, search the thread. Unsure if it causes RAM issues with a memory leak too, first anyone's reported so. Personally I stopped using new builds because of the wired audio bug so wasn't long enough to notice memory issues.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] messi2050:
I hope NFound will release it when he think it's ready for share, he made great work so far and of course it's his own work and he have the right to share it or not.., there are some simple bugs such as the headphone high cpu usage that I believe he can get help with it if he shared the trees so he can concentrate on fixing the vendor partition treble hals.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] 2CanSan:
I wonder if someone thought to insure there is a method to repartition the system back to normal?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ramnkc:
your follow [MENTION=5492451]NFound[/MENTION] steps completely? flash treable recovery then flash the vendor partition with miflash and format it to ext4 in the recovery? Mine was working fine even i did not flash the havoc treble version, but i decided to give it a go and its working fine. You need to format all partition and then flash everything again, havoc treble and opengapps then reboot and see it works
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Yes, there are several methods, all of them involve EDL packages EDL repartition package, custom FULL_EDL or STOCK_FULL_EDL. I have done experiments resizing other partitions and went back to "normal" without any issue. Nonetheless, why would you want to disable the treble support? When the device is repartitioned (AKA treblerized), it supports both the non treble and treble roms. There is no need to disable this feature.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choobilsky:
Is the feature to activate/deactivate SIM cards missing in Havoc, latest build? In the SIM card setting I can just edit name, Color etc but not entirely switch on or off.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TPMJB:
*ahem*

ENCRYPTION

Encryption broke sound on an earlier version of AEX (before June?) Much before that, encryption would not boot. Encryption has broken sound again in the latest AEX build, and Havoc just won't boot. Same issue as before.

So I'm back on the 7/11 build. With encryption.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
[MENTION=5492451]NFound[/MENTION]

I know you have much work to do with treble at the moment. However I'd like to give feedback on the issue with not being able to mount /system writable. We have 3 Axon7 A2017G here (2,5 to be exact). Two of them, the grey ones, have not problem with mounting /system writable. One of them, however, broke in a half :( so I've bought 2 days ago a gold one. The gold one has indeed a problem with mounting /system rw. I can't find the error. I've tried all combination of the b12-bootloader and all twrp available, while wiping and formatting data. It just won't mount rw. When I restore a backup from a grey one to the gold one rw works, however it crashes from time to time. When I install a fresh system, mounting rw doesn't work. Switching to universal bootloader fixes the problem. Please check it out in a free minute. Thanx in advance.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ibphantom:
Power-Off at 25>%

My phone will turn off when there's still around a quarter of battery left if I'm using multiple heavy power apps. I can stretch the power usage out sometimes by only using text based apps, but the furthest I've made it is around 5%.

If this is not a ROM issue(I have the 07/27 release) then...,

What kernel is the best for on demand, almost all day use? What other mods can be made?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] messi2050:
this can be selinux related, i hope nfound would share the source so we can look into it..
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] christoophat:
Maybe Try...

https://xdaforums.com/oneplus-3/how-to/advanced-interactive-governor-tweaks-t3476589

our phone uses same cpu as one + 3 (820)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] messi2050:
you have tried it ? does it make any difference to battery life ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] christoophat:
Yes allows you to try different profiles, some for better battery, some for better performance, etc. You just install the .apk then select the one plus 3 option (820), then just pick a profile to load and try it.

Read thru some of the thread gives you some info one what each profile does.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TPMJB:
Not sure. I know it was fixed in Lineage OS a while ago and then shortly after it was fixed in AEX/Nfound's roms.

Not sure that Treble will really revolutionize this rom. I just was curious on running it. Back to the 7/11 build and working fine.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
[MENTION=5492451]NFound[/MENTION] would you please publish source? I really like your work and AospExtended works well for me but I cannot continue to run closed source OS.

Thank you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Spooderman46:
Agreed. Love the ROMs but getting a bit suspicious why Nfound is so reluctant to share the source.

And I'm no expert on AEX or open source software licensing, but by using their code isn't it required to open source it?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
No, not everything.

But since he deleted the tree, yeah, that can't be done.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
Deleted the tree?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Infy_AsiX:
lol at all the misinformed sudden calls for open source because Oki the expert is asking for them. Open source ensures no guarantee the given build matches the provided code. The same goes for all builds whether they're ROM, kernel or app. The trust goes to the build provider, for example trusted providers are official LineageOS, F-droid, etc. If sensitive data security matters to you, use official built LOS14.1 or build open source yourself.

As for Nfound's choice to go closed. The motive is likely to keep his unique original work so no one can simply copy it. It changes nothing in terms of what you're likely getting in the builds. Odd that people were never concerned before when the risk hasn't changed.

Last time I posted this reply for awareness, the bunch of related posts were deleted without notice. Waste of everyone's time because some moderator is trigger happy. Yet two days later the same unanswered questions are reappearing. Got to save posts now to be able to repost in case of sudden deletion.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
https://github.com/NFound/android_device_zte_axon7

That tree/branch/repository.

Sorry for the confusion.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Infy_AsiX:
it exists on LOS15.1, can be fixed open source there, that's if it's not a ZTE B12 closed source issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
Same issue here. Gold A2017U. Use universal boostack from lineage thread or update to treble aex using oki's guide. Been trying to work out why other A2017U users don't have the same problem, maybe colour means more than we think. It's definitely related to bootloader versions though.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] messi2050:
No i can't find 15.1 tree only up to 14.1..
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Infy_AsiX:
oh sorry yeah the sources aren't shared there yet because of devs wary of ZTE or something.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rzarectha:
Hey guys,

Sorry to be dense in this situation but I haven't stayed up to date with the latest developments.

It appears that NFound basically ragequit and all his ROMs are now discontinued? Is this a fair assessment of what is going on?

I was checking daily because I'm excited about treble, I was holding on until this weekend to convert my phone. If development is now at a halt I'd rather wait a while longer.

Thanks a lot in advance!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TPMJB:
Dunno. I'd say hurry up and wait. There's a lot of drama going on regarding whose girlfriend is whose (code) and other such tomfoolery.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BomboPAPA:
Hi !

Could anyone say, what is the main difference between AEX and Havoc rom?

The main that I need in rom is: max battery life, android pay, google camera hdr+ and dolby sound.

Which rom to choose?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] beastobadness:
I have to say that I am at a loss at what actually happened. NFound mentioned about taking a spectator stance in one of his last comments, not sure if that means he is watching the threads for reaction or for some sort of change. Whatever it is, he has definitely gone off grid the last few days. Telegram, 4pda, XDA, YT have all gone quiet. Maybe he just needs a timeout!

Personally I hope he does return as he introduced treble to the axon 7 and has been doing great work with this device...would be a shame not to continue as he has gained the respect of many in the axon 7 community.

I have been watching the 'project treble' section on XDA and it is getting very interesting and gaining plenty of momentum.

I seen no reason not to convert my axon 7 to treble for future proofing as you can always roll back to a non-treble custom ROM anyway.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] NFound:
I repeat for everyone! :)

The source code for the device tree, kernel and vendors belongs to the OrdenKrieger. I can not take and put someone else's work in the public domain. If you want him to publish it, then write to him. I do not have the right to publish someone else's source code on my own behalf.

Someone write the moderator and he wrote to me that if I do not upload the source code, then he will close the branch of AOSP Extended. But at the same time, according to the logic, the LineageOS 15 branch should be closed, because the source code is not provided in it. - you need to close all the branches on the basis of Oreo, because the source code was not provided in any of them. Did you achieve this? Stay without support? Then I congratulate you.

Now about the Android P.

I already wrote that in the posted on the forum. These sections were also compiled on the basis of the AEX|Havoc source code, which is not ported. Hence, logically, this thread also needs to be closed, with everything that Oki wrote is an absolute lie. This is not a ported firmware, but an image of the GSI, based on my Treble-versions ROMs.

Well, in conclusion, I ask you not to start a stupid holivar any more, since all you are trying to achieve is the closure of this branch. Be patient and we will certainly post the source code after we wait for the official release from the manufacturer and eliminate the existing bugs.

All that we do is for you. It is for this reason that I did not want to upload the alpha versions of the Roms.

I've said everything.

All good and good mood :cowboy:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rzarectha:
Hey NFound. Thanks a lot for taking the time to answer and clarify the situation. Cheers^^
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amaury48:
From all of us that greatly appreciate the work you do for us I just want to say THANK YOU....NFound !!!!!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Completely agree on all except on the unfortunate reference to me. Thanks for showing up, we were missing you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Ok, are we done with all of the politics now? As if this thread wasn't long enough already.

There is no more drama folks, nothing more to see here. Everyone is in a productive mood, the dev has not bailed, and there is still support from other devs and knowledgeable testers.

So, to all of the testers still looking for flames in all of the smoke. Quit posting your theories and conclusions about the situation that you've come up with based on partial information.

Seriously, I've just been sitting back and watching. At first shocked at [MENTION=5492451]NFound[/MENTION], upset and confused with [MENTION=319057]Oki[/MENTION]. Then later understanding [MENTION=319057]Oki[/MENTION], and questioning [MENTION=5492451]NFound[/MENTION]. Now relieved that they were able to resolve within days, what was only a misunderstanding.

All the while, not posting my every thought that no one here gives two poops about. Because it's not productive, and chances were I didn't have all of the information. It's always best to be patient and see how it plays out, but some people want to chime in and get their participation trophy.

In conclusion, just stop. Stop your ignorance from becoming attacks. Everything is as it should be. If you don't like it, you don't have to be here, there are plenty of other options.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] NFound:
I understood you. As you wish.;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Lol, i was referring to the testers, not you. I wasn't telling you to go somewhere else, in your own thread. Don't be silly.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LenAsh:
Keep matters on topic please...

Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] NFound:
It is not nice to call me stupid on your part. English is not my native language, I do not understand some words, so I use an translator. Perhaps the translation is not correct, but I think it's not right to call a stupid man because of this.

In any case, let's stop the holivar and listen to what the moderator said, he said it right. We continue the discussion on the topic without deviating.

Thank you :o
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] samo_lego:
Ahem, I am a bit confused :) ...

Anyway;

I would also say thanks to [MENTION=5492451]NFound[/MENTION] for all the hard work he's done.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Maybe not epic, but yeah, there was and still some. Mostly due to people posting their thoughts instead of what they can honestly say are truths. People were directly attacking the dev and trying to get involved (participate) in something they only knew a fraction of the facts about, and you claim there wasn't and isn't any disrespect being thrown around that needs to stop.

It needs to stop, I pointed that out, and instead you do exactly what I'm talking about.

---------- Post added at 07:01 PM ---------- Previous post was at 06:57 PM ----------

Yes, i understand. Bad translation. Don't be silly = stop joking. Not saying you're stupid, sorry. Yes, let's move forward. Only respect.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] paketjabbe:
Havoc os treble

Hallo [MENTION=5492451]NFound[/MENTION], I have havoc os treble install on my axonn 7 gold and no problem what so ever. Use it for daily use en every thing works fine. Waiting for new surprises ??
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] NFound:
Hey, you yourself asked to share the developments with other developers. Not everything is solved by the source code, some libraries simply do not have sources and they have to fix the hex editor.

Dirty hack tfa9890 for treble + changes path tfa9890 in audio_amplifier + move amplifier to /vendor + move /etc/settings/ *.cnt to /vendor/sound = work audio on treble :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ramnkc:
This brings back my old save game file hacking days ! :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] samo_lego:
Hi (again)!

I have treblerized my Axon 7 yesterday, everything went smoothly. Thanks for great guide.

As I have very little knowledge when it comes to such things; I would like to ask some things. If someone could explain them, I would be really grateful.

I came from RR 6.1, so I had Oreo bootstack already installed. I didn't mind installing it again, but what do these different Bootstacks do? I found one here, one in the other thread ... Is any of them "better"? I heard some of them support VolUp+VolDn+Pwr to access EDL, or do all of them support it?

And when you have treble, does that mean you can literally flash ANY GSI? And boot it with small amount of luck (but there's no guarantee that everything will work)? Or are/will be there different GSIs for similar phones?

Thank you so much!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] P650SE:
You have to keep another app running in the background as well for the bug to happen, apologies for the confusion. Just open an app such as Google Play and then open something else like Boost for Reddit. When you press the recents button with Boost still in fullscreen, you should notice that it will completely disappear and only display Google Play in the multitasking menu. :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] srr71:
Few issues with this ROM

Clean install. Seeing few issues.. Any suggestions?

1) when i use Video mode in google camera app (About Phone --> AEX updates --> Addons), phones ringer goes to silent mode. Annoying and may miss calls because phone is not ringing

2) Fingerprint sensor is still flaky when phone is locked and screen is turned-off. Anyone seeing this?

3) Not able to silence notification when charger is plugged in the phone even when i selected notification sound is Silent. I want vibration but not sound.. Annoying.

Thanks for your help.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] P650SE:
^^^I've switched to LineageOS for the moment because that problem above was bugging the hell outta me. Hopefully it'll get patched when the ROM is updated to Oreo.

I had the same problem with the fingerprint scanner, it was very slow and unresponsive on this ROM when the screen was switched off. :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Chiko-HH:
yes,Same here
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ShiverStorm:
Does anyone have a preference for kernels?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcdw:
I flashed AEX just so I could try to reproduce. Never lost the foreground app in Recents. It would drop to far bottom of Recents screen but still visible.

The background app. Any app or something that's doing something like playing music?

Kept messing around but didn't get the disappearing app.

ZTE Axon 7 A2017U, VertexOS Carbide-v3.6 ROM, Tapatalk 4.9.5
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] P650SE:
Well first of all, thanks for going to the effort of flashing the ROM just to try and reproduce this issue. I really appreciate that. :) It's unusual how you weren't able to encounter the issue despite following the same steps I mentioned previously. I was running a few mods with the ROM but nothing that should affect the multitasking menu; for example the camera port from MiFavor B32 and a custom font in Substratum. I have used these mods in various other ROM's and have not experienced any issues, so I strongly doubt those are to blame.

However, one thing I remember having to do with AospExtended on this phone was flash the 'Patch Stock Keys' ZIP from earlier in this thread in order to enable the back button functionality, and then swap the buttons around in the 'Extensions' menu so that the Recents Menu =

Back Button

and Back Function =

Recents Button

. (The reverse of what the buttons actually do in reality!) Maybe this somehow affects the multitasking/recents menu and causes the bug where the newly-opened app will not appear when the menu is opened for the first time. :confused:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] awsomjgp:
I have the exact same setup as you (stock cam, subs themes, normal keys) and it looks completely fine. The most recent app goes to the very bottom with the title bar barely showing (because it assumes you don't want to go back to the app you were just looking at).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcdw:
[MENTION=5393119]P650SE[/MENTION],

Decided to have another go at it. Messed around, played with related settings, went back and forth between Card, Grid, and Slim, threw in a SubS theme, just because. Also flashed the buttons patch which I didn't do the last time. Still, no problems with Recents. Earlier I thought maybe the foreground app had gone too far below but that's not it either. It behaves normally as [MENTION=7409375]awsomjgp[/MENTION] pointed out.

So the Recents issue can't really be a bug since the rest of us aren't experiencing it. I forget, you tried without any themes applied, right? So strange.

LG G3 D851, LiquidSmooth v4.1 ROM, MultiROM, Tapatalk 4.9.5