Database Users

[Q] Is it as simple as compiling cyanogenmod?

Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.

evodev said:
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
Click to expand...
Click to collapse
It is

XpLoDWilD said:
It is
Click to expand...
Click to collapse
Just a quick question,will it support mediatek devices?

s.sawrav said:
Just a quick question,will it support mediatek devices?
Click to expand...
Click to collapse
Yes.
We have early support for the r819.

I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.

Mayank7795 said:
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Click to expand...
Click to collapse
If you have a working AOSP, it should be available without problems.

@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers

What about devices that have CM10 only?

lozohcum said:
What about devices that have CM10 only?
Click to expand...
Click to collapse
You need at least an unofficial CM 10.2 / AOSP 4.3.

JoinTheRealms said:
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
Click to expand...
Click to collapse
Building is always worth an attempt...
I used to build my own CM, i'm gonna try to build my own omni too but i'm struggling. I must be doing something wrong with the repo init but I can't seem to find what... I'm gonna update my buildbot first because it's been awhile, and maybe try again tomorrow.

As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
That's why its worth scrawling through XDA, going through guides and learning to dev. Nothing wrong with a dev who decides to leave an older version for a newer version. They're doing it for fun and free.

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.

pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
As long as there is no hard reason to stop supporting a device and we have someone who is taking care of that device we will try
On the other side - there is constant evolution which sometimes will make it necessary to leave a device "behind" if the effort will become too large
Sent from my Find 5 using xda app-developers app

XpLoDWilD said:
It is
Click to expand...
Click to collapse
Not quite yet... Not until we have roomservice up and running.
(For those that didn't understand what I said - roomservice is the part of CM's repo management system that will automatically sync a device tree and all dependencies. roomservice is HEAVILY dependent on github's APIs, so we couldn't even start work on that particular piece of infrastructure until the project went public.)

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.

mattman83 said:
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
Click to expand...
Click to collapse
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance

pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
I hope the Acer IconiaTAB A5000 will get supported.

Please, support for RAZR i (x86)

lozohcum said:
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
Click to expand...
Click to collapse
Problem is, every device has its own pitfalls. Some are harder to overcome than others.
For example, the lack of NEON in tegra2 combined with the dependency of newer gapps on NEON really screws tegra2 devices, and there isn't much that can be done about it.
Also, in some cases, the things needed to get a device working aren't in the tree, but are in the frameworks to handle OEM-specific oddities (RIL hacking in opt/telephony, which I admit I'm not too familiar with...) or platform support. Sometimes, old devices get left behind simply because their platform overall is a ***** to support beyond a certain point. (See how MSM8660 devices have been lagging lately, due to Qualcomm pretty much sunsetting that chipset.)

[PETITION] Ask OnePlus to implement Project Treble on currently supported devices.

Project Treble, as you've heard, is an amazing new update structure for Android devices and also can affect the speed and stability of Android development.
OnePlus has decided not to implement the current OnePlus devices with Project Treble, and they haven't given an explanation as to why they decided not to.
Project Treble can help the 3/3T as they are almost out of the OEM support days. If they do implement this, you may be looking at Android P ROMs for your device within days of the release of the AOSP commits.
Stand UP for your device and our responsibility as the community should be to bring support for our device for as long as possible. If OnePlus implements this, our device will be future proof for the aeons to come.
Your vote counts.
Change Org - https://www.change.org/p/carl-pei-w...-ask-oneplus-to-support-project-treble-in-oos
Do your part as a OnePlus 3/3T user and VOTE!

What's your drug of choice?

suraj.das said:
What's your drug of choice?
Click to expand...
Click to collapse
What do you mean?

thes3usa said:
What do you mean?
Click to expand...
Click to collapse
He means that you must be high on something to think OP will give this petition any consideration. I don't think they will either, but I signed it anyway. It'd be nice if they did. It would certainly bolster consumer confidence in OnePlus if they supported such a game changing feature.

HampTheToker said:
He means that you must be high on something to think OP will give this petition any consideration. I don't think they will either, but I signed it anyway. It'd be nice if they did. It would certainly bolster consumer confidence in OnePlus if they supported such a game changing feature.
Click to expand...
Click to collapse
This really isnt that much of a game changer really. Dont let those on the portal make you think other wise. The rom developers are laughing at him as he has no real idea of how this is gonna work. In the end it will have 0 effect on roms or OEM updates.

zelendel said:
This really isnt that much of a game changer really. Dont let those on the portal make you think other wise. The rom developers are laughing at him as he has no real idea of how this is gonna work. In the end it will have 0 effect on roms or OEM updates.
Click to expand...
Click to collapse
How so?
Sent from my ONEPLUS A3000 using Tapatalk

HampTheToker said:
How so?
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Well the only this this allows is updated things from the SOC manufacturers. Making things for the oem faster, if they ran aosp. But they dont. Updates will be just as long If not longer now due to this. Why you ask. Well now the OEM has to build their entire OS completely differently now. This is from OEM changing the entire OS framework as well as every file google makes.
As for custom roms. Well this really means nothing as most custom roms are already on newer patches then even what google has pushed to aosp.

zelendel said:
Well the only this this allows is updated things from the SOC manufacturers. Making things for the oem faster, if they ran aosp. But they dont. Updates will be just as long If not longer now due to this. Why you ask. Well now the OEM has to build their entire OS completely differently now. This is from OEM changing the entire OS framework as well as every file google makes.
As for custom roms. Well this really means nothing as most custom roms are already on newer patches then even what google has pushed to aosp.
Click to expand...
Click to collapse
What? What even are you talking about? Project Treble is a huge step for AOSP ROM development.
Read here - https://www.xda-developers.com/stock-android-oreo-huawei-mate-9-project-treble/
Project Treble can bring quicker and more stable ROMs to devices faster and more efficiently.

HampTheToker said:
He means that you must be high on something to think OP will give this petition any consideration. I don't think they will either, but I signed it anyway. It'd be nice if they did. It would certainly bolster consumer confidence in OnePlus if they supported such a game changing feature.
Click to expand...
Click to collapse
OnePlus's rule is to listen to their community yeah? With the petition over 5000 signatures and the link booming on r/OnePlus, it'll make them look bad if they ignore the petition.

thes3usa said:
What? What even are you talking about? Project Treble is a huge step for AOSP ROM development.
Read here - https://www.xda-developers.com/stock-android-oreo-huawei-mate-9-project-treble/
Project Treble can bring quicker and more stable ROMs to devices faster and more efficiently.
Click to expand...
Click to collapse
Please. First of getting aosp to boot on that device is not that big of a deal. Rom devs do it all the time. The only reason those devices are left behind is because developers refuse to work with their chipset.
So explain how something only concerns the SOC manufacturer and the OEM will make roms faster?
If you really thiink this will make the OEMS update any more then they already do then you are sadly mistaken.
Thats the one that I mentioned that the devs are laughing at.
Also if you follow the thread linked you will see that things are still broken and causing issues. Nothing new.
Project treble means nothing for the average person and it is sad that the portal guys are not tech savvy, which leads them to making statements that are not even close to being true.

zelendel said:
Please. First of getting aosp to boot on that device is not that big of a deal. Rom devs do it all the time. The only reason those devices are left behind is because developers refuse to work with their chipset.
So explain how something only concerns the SOC manufacturer and the OEM will make roms faster?
If you really thiink this will make the OEMS update any more then they already do then you are sadly mistaken.
Thats the one that I mentioned that the devs are laughing at.
Also if you follow the thread linked you will see that things are still broken and causing issues. Nothing new.
Project treble means nothing for the average person and it is sad that the portal guys are not tech savvy, which leads them to making statements that are not even close to being true.
Click to expand...
Click to collapse
By your judgement, what is not true as explained by the portal guys?
Isn't the whole point of Project Treble making it easier for devs to work with chipsets such as MediaTek or Kirin?
Project Treble third party development is still early, you need to give it time. It's not like every new feature in Android sprung up to be in the top places at once. Things will be broken, and the devs will find a solution.
Also, the point of Project Treble will be having unified ROM files for many devices in a category ( eg: Same SoC, same OEM, etc), and also where the device trees have not been released, unlike OnePlus, who has their Day One project.
By your logic, you're saying that there's no use for Project Treble, and it's all a complete waste of time.
But hey, it's your opinion .
But you do have a point, the portal is not to be trusted too far, and I would wait until a developer has shown that Project Treble has been put to good use on a device. But, that does not mean that Treble support should not be given to a device like ours that's super powerful.

thes3usa said:
By your judgement, what is not true as explained by the portal guys?
Isn't the whole point of Project Treble making it easier for devs to work with chipsets such as MediaTek or Kirin?
Project Treble third party development is still early, you need to give it time. It's not like every new feature in Android sprung up to be in the top places at once. Things will be broken, and the devs will find a solution.
Also, the point of Project Treble will be having unified ROM files for many devices in a category ( eg: Same SoC, same OEM, etc), and also where the device trees have not been released, unlike OnePlus, who has their Day One project.
By your logic, you're saying that there's no use for Project Treble, and it's all a complete waste of time.
But hey, it's your opinion .
But you do have a point, the portal is not to be trusted too far, and I would wait until a developer has shown that Project Treble has been put to good use on a device. But, that does not mean that Treble support should not be given to a device like ours that's super powerful.
Click to expand...
Click to collapse
The portal guys will have you believe that this will help rom development. It wont.
The problem the devs have with the Kirin chip is that it is done in mostly Chinese and there is 0 documentation on how to work with the chips. as for MTK. Yeah that wont happen. There is a reason those chips are used mostly on devices that dont have google play services.
No that will not mean unified rom files. Another thing they lead to you believe. Even the dev doing the work (not the portal writer) has already said each device will still need its own kernel.
Project treble does have a use. Its just not something we can really use.
Project treble was made so OEM can update android without having to update their version of the android OS. Everything is between the SOC Oem and the device oem.
Now ask yourself this. What OEM is really gonna update a device without updating their OS version? Also you cant really seperate the OS framework from googles android and the OEM. This is due to the OEM changing or replacing completely every base android framework file that google releases. (another thing the portal has people not understanding. OEM do not skin android. They replace it with completely different versions of android. Like Linux distros.) Also even if you can boot AOSP on any device. Are you willing to lose all the features that Oem add to their devices? Take the one plus camera deal as a perfect example.

Quote from other thread:
regarding Project, it targets all devices launched with Android 8.x also It has almost nothing to do with Oneplus, if Qualcomm update the reference msm8996 kernel to linux 4.4 then its trivial to port oneplus modifications over. Qualcomm has practically zero motivation to do this, infact it works against their interests.
So better petition Qualcomm

Did Developers avoided this Device or work on custom roms on?

As we all know Mi a1 makes it difficult for custom rom building coz of A/B partitions ..
But i wanted to whether all the developers are in to make a lot of stable custom roms or they have moved away from the device.
I am not asking for customs roms now itself just wanted to know there is support and working on in the background or not.

I don't think they're avoiding it, it's just taking time to bring up the device tree.. I might dig into it a bit this weekend and try to bring up the device tree to 8.1, the problem is that even in 7.1.2 we don't have everything working. also, Xiaomi did a terrible job with the kernel, took them 4 months to release it and when they did they released an old 7.1.2 based kernel with the commits squashed into one commit over an older CAF tree

Developers are hampered by the lack of availability of source code that is yet to be released by xiaomi, (they have released the code, but not Oreo) otherwise we would have good ROMs by now

sooti said:
I don't think they're avoiding it, it's just taking time to bring up the device tree.. I might dig into it a bit this weekend and try to bring up the device tree to 8.1, the problem is that even in 7.1.2 we don't have everything working. also, Xiaomi did a terrible job with the kernel, took them 4 months to release it and when they did they released an old 7.1.2 based kernel with the commits squashed into one commit over an older CAF tree
Click to expand...
Click to collapse
Yes that ok .. Waiting is worth the wait . But can we expect stable custom roms within a month

Vibun said:
Yes that ok .. Waiting is worth the wait . But can we expect stable custom roms within a month
Click to expand...
Click to collapse
LineageOS is out. And I'll say yes.
Once LineageOS is perfectly stable you'll see many more ROMs.
No, developers are not purposely avoiding the device. On the contrary the day after the sources dropped we had 3 ROMs (broken nonetheless, only RIL worked) by three different devs.
As of right now, everyone has joined hands and are fixing LOS14.1
Even Francisco Franco said he's getting his kernel to this device, just be a bit patient.
Sent from my Mi A1 using XDA Labs

Ron1209 said:
LineageOS is out. And I'll say yes.
Once LineageOS is perfectly stable you'll see many more ROMs.
No, developers are not purposely avoiding the device. On the contrary the day after the sources dropped we had 3 ROMs (broken nonetheless, only RIL worked) by three different devs.
As of right now, everyone has joined hands and are fixing LOS14.1
Even Francisco Franco said he's getting his kernel to this device, just be a bit patient.
Sent from my Mi A1 using XDA Labs
Click to expand...
Click to collapse
Yes , I totally agree with u .. It's a new type of device (a/b partition ) it would take time .. just wanted to know that work is going around on it

Vibun said:
But can I expect stable custom roms within a month
Click to expand...
Click to collapse
Are you gonna pay them?

iMewo said:
Are you gonna pay them?
Click to expand...
Click to collapse
Dude !! Read my thread properly at the beginning. I said I am not asking for custom roms now ... Just wanted to know whether the device is under work or not ....

Vibun said:
Dude !! Read my thread properly at the beginning. I said I am not asking for custom roms now ... Just wanted to know whether the device is under work or not ....
Click to expand...
Click to collapse
Vibun said:
Yes that ok .. Waiting is worth the wait . But can we expect stable custom roms within a month
Click to expand...
Click to collapse
try give whoever it is an extra day or 2 maybe.just wait am sure were gonna see a lot of roms coming up

If your waiting for development then you have not done your research. Development devs dont buy from this oem. They even avoid it. The best you can hope for is some of the users porting the roms over but they will most likely be buggy as they always are with this oem.

zelendel said:
If your waiting for development then you have not done your research. Development devs dont buy from this oem. They even avoid it. The best you can hope for is some of the users porting the roms over but they will most likely be buggy as they always are with this oem.
Click to expand...
Click to collapse
Then what are your thoughts about Pixel Experience on Redmi Note 4? It has a very few bugs, and in fact gives better battery life than MIUI 9. That ROM isn't considered to be a port, right?

guy_infinity said:
Then what are your thoughts about Pixel Experience on Redmi Note 4? It has a very few bugs, and in fact gives better battery life than MIUI 9. That ROM isn't considered to be a port, right?
Click to expand...
Click to collapse
Any rom will give better batter battery life then miui. That is due to all the background syncing that it does in the back ground.
As for that rom. Any rom that brings over a pixel like rom is a port.
I wouldn't really know as this device isn't sold in my country nor does anyone I know even look twice at the oem.

Stop this A/B partitioning scheme BS. Of course, it does not make life easier for the developers but it certainly isn't the biggest obstacle.

gougous3 said:
Stop this A/B partitioning scheme BS. Of course, it does not make life easier for the developers but it certainly isn't the biggest obstacle.
Click to expand...
Click to collapse
Really. Ask the devs that got the pixel and after that won't touch a device with the partition setup. It makes things almost impossible to get working right. Me, I would just repatriation the device and remove the partition all together.

zelendel said:
Really. Ask the devs that got the pixel and after that won't touch a device with the partition setup. It makes things almost impossible to get working right. Me, I would just repatriation the device and remove the partition all together.
Click to expand...
Click to collapse
I'm not neglecting that but, in my opinion, it isn't that big of a deal anymore. I'm sure that even we if we didn't had it, things wouldn't be much better.

gougous3 said:
I'm not neglecting that but, in my opinion, it isn't that big of a deal anymore. I'm sure that even we if we didn't had it, things wouldn't be much better.
Click to expand...
Click to collapse
Well considering the oem you are right. But for normal devices those that don't have the partition are the more dev friendly. Just talk to some of the devs. Most have sworn off anything that uses the dual partition.

zelendel said:
Really. Ask the devs that got the pixel and after that won't touch a device with the partition setup. It makes things almost impossible to get working right. Me, I would just repatriation the device and remove the partition all together.
Click to expand...
Click to collapse
Absolutely true, it took months to see a stable release of TWRP for the Pixel. And there's still no official LOS as well.
However there are a few ROMs and more device with A/B are out like PH-1 and Moto Z2

For reals though, devs working on ROMs for this device, feel free to create/list your PayPal accounts for donations.
We ask so much of the devs it's only fair we buy them a drink/meal for all their hard work and persistence!
Sign me up for a donation

zelendel said:
If your waiting for development then you have not done your research. Development devs dont buy from this oem. They even avoid it. The best you can hope for is some of the users porting the roms over but they will most likely be buggy as they always are with this oem.
Click to expand...
Click to collapse
You are wrong.. mi phone's has great support on xda..look at rn3,4..and other mi phone threads

sooti said:
I don't think they're avoiding it, it's just taking time to bring up the device tree.. I might dig into it a bit this weekend and try to bring up the device tree to 8.1, the problem is that even in 7.1.2 we don't have everything working. also, Xiaomi did a terrible job with the kernel, took them 4 months to release it and when they did they released an old 7.1.2 based kernel with the commits squashed into one commit over an older CAF tree
Click to expand...
Click to collapse
eeeeeeeyyyyyyyyyy od israeli

Project treble

There are tons of android 8 and 9 GSI ROMs out there for devices with treble support. I know LG has decided not to add project treble support for the V20. Now, I wonder if any developer is working on this for this lovely phone. It will be nice to keep this phone for some time as long as there is is possibility to update the software to newer versions.

i95swervin said:
Your above quote has nothing to do with the LG V20.
If manufacturers shipped devices with 7.0 it is not required for them to add treble support in a future update. Your best bet is to wait and see what happens with AOSP roms. Not promising anything.
Click to expand...
Click to collapse
Uh they specifically asked if any devs are working on treble for the v20. which is possible seeing as we added support for it on the v30.

me2151 said:
Uh they specifically asked if any devs are working on treble for the v20. which is possible seeing as we added support for it on the v30.
Click to expand...
Click to collapse
The v30 isn't the v20.. right now x86cpu has it mostly working, but there's issues with the camera not playing well with the vndk (treble) restrictions and needing things on /system. He's been blocked on this for a bit, but sit tight and just generally watch the LineageOS 15.1 thread.

Phoenix591 said:
The v30 isn't the v20.. right now x86cpu has it mostly working, but there's issues with the camera not playing well with the vndk (treble) restrictions and needing things on /system. He's been blocked on this for a bit, but sit tight and just generally watch the LineageOS 15.1 thread.
Click to expand...
Click to collapse
If x86cpu succeeds with the V30, I guess it should not be too difficult to get it done for the V20 since each OEM usually has similar file structures for their phones.

lallolu said:
If x86cpu succeeds with the V30, I guess it should not be too difficult to get it done for the V20 since each OEM usually has similar file structures for their phones.
Click to expand...
Click to collapse
Let me put it another way, it IS done except the camera isn't playing nice. Read a few pages from the lineage thread starting about here.

Apparently, LG v20 is A only. But it should work. Can't comment on whether the camera would work or not though.
https://www.getdroidtips.com/lg-v20-android-9-0-pie/
I tested my lg v20 by using getprop ro.treble.enabled and it showed "true". Also tried the treble checker app and it is A only. not A/B.
Nevermind. It only appeared as A only when i was on RR 6. But that doesnt exactly makes it A

bit of update concerning kernel development

Hey there,
Most of you have noticed there is no to very low development for our devices.
For what is worth, there is development, and it is awesome.
We have a very nice device and with great kernel I can assure you that you will be amazed by the performances and battery life for this device.
*I'm currently testing a custom kernel (Hex), and even if it's still a bit of a pain to flash it (twrp need to be installed on one partition and kernel on the other "side") so you need a PC to get it flashed.
So. Please be a bit patient and it will be awesomely rewarded
I wrote this post to all fearing no dev. For the mia2, there is, and damn it's DDucking awesome
Have a nice day!
Regards,
H.

Thanks :good::good:

Wow! It's good to know this,

I would like to see the growing number on the development for this device to the point like other popular device such as my old Redmi Note 4 (its running awesome when installed LOS Oreo). The thing is this A/B partition on MiA2 seems to be complicated and have a high risk if you do wrong from my perspective. With that reason I still keep my phone as it is for now, looking forward for more development and tweaks tho

mark.dx said:
I would like to see the growing number on the development for this device to the point like other popular device such as my old Redmi Note 4 (its running awesome when installed LOS Oreo). The thing is this A/B partition on MiA2 seems to be complicated and have a high risk if you do wrong from my perspective. With that reason I still keep my phone as it is for now, looking forward for more development and tweaks tho
Click to expand...
Click to collapse
Yes, me too, even just try to unlock and just enable camera2api without root can turn in a briked device. So i will wait for an oficial TWRP that don´t transform my A2 in to a brick. like this user:
https://forum.xda-developers.com/showpost.php?p=77825415&postcount=13

ki69 said:
Yes, me to even just try to unlock and just enable camera2api without root can tur in a briked device. So i will wait for an oficial TWRP that don´t transform my A2 in to a brick. like this user:
https://forum.xda-developers.com/showpost.php?p=77825415&postcount=13
Click to expand...
Click to collapse
Mmh, it's definitely way too early to use any tool. God knows what the tool will do (it's just an automated batch based on ADB/fastboot aka. Platform tools) ?
Again, it's currently a pain to flash anything but at least, it's now 100% stable (if manually flashed with correct ADB (last) version.
?
Just a question of time that everything goes to the "noob-world" <- no offense we, just another way to say "bulletproof secure"

I got mine converted to Mi 6X (wayne) and I have only A partition slot. A/B it's ****. I also earned some internal storage space (around 4 Gigs) by doing this. I flashed back AEX and all is good! There is also a fixed vendor coming up which will allow to run every GSI image out-of-the-box without any bugs, thanks to Manish!

If you want guys, I can make a step by step guide on how to root and use magisk, substraum and gcam
It is very easy in my opinion, can be done in 5 minutes

I think that could be actually great. It took me some times to harvest all Infos and find a way which was making some sense. No rant on devs. But a clear way step by step would be great. At least to answer the 2000 message I get on "how-to do it" ????

For substratum not needs always root....Andromeda + substratum works very fine on stock devices(Andromeda cost is very small)
A2 certainly needs an official twrp,first than all....perhaps it will come soon, the device is still new...

mark.dx said:
The thing is this A/B partition on MiA2 seems to be complicated and have a high risk if you do wrong from my perspective.
Click to expand...
Click to collapse
It was an issue in the past, but now that there's wide support for the Google Pixel (which even has official LOS) things just got a lot easier. A/B is a non-issue for the end-user, the developer does need to check how things are done in the Pixel (which takes valuable time), but shouldn't be a deal breaker as everything is already public.
IMHO the real issue is the fact the Mi A2 wasn't really that popular to begin with (among the kind of enthusiasts that would only ever run a custom ROM, that is). When it launched, those enthusiasts preferred the whyred (which already had great support, namely official LOS). Shortly after, Poco happened.
I honestly think this device will be like most others, custom ROMs will either come straight from GSI (when vendor is fixed) or only after the Android One support ends (aka. when we'll be pressed to do something).
It's not too bad at all, it's just slightly disappointing because (1) Xiaomi timed their product releases poorly, not giving enough information to make an informed purchase; and (2) we kinda of expected a little more from Android One than to be grounded to stock or (now) a GSI.
At the end of the day it is up to us (everyone in this community) to do something about it (ie. start working on the device instead of expecting someone else to pick that job). Harsh words, but true nonetheless.

enapah said:
It was an issue in the past, but now that there's wide support for the Google Pixel (which even has official LOS) things just got a lot easier. A/B is a non-issue for the end-user, the developer does need to check how things are done in the Pixel (which takes valuable time), but shouldn't be a deal breaker as everything is already public.
IMHO the real issue is the fact the Mi A2 wasn't really that popular to begin with (among the kind of enthusiasts that would only ever run a custom ROM, that is). When it launched, those enthusiasts preferred the whyred (which already had great support, namely official LOS). Shortly after, Poco happened.
I honestly think this device will be like most others, custom ROMs will either come straight from GSI (when vendor is fixed) or only after the Android One support ends (aka. when we'll be pressed to do something).
It's not too bad at all, it's just slightly disappointing because (1) Xiaomi timed their product releases poorly, not giving enough information to make an informed purchase; and (2) we kinda of expected a little more from Android One than to be grounded to stock or (now) a GSI.
At the end of the day it is up to us (everyone in this community) to do something about it (ie. start working on the device instead of expecting someone else to pick that job). Harsh words, but true nonetheless.
Click to expand...
Click to collapse
This should be stickied somewhere, this is exactly what happened and what needs to be done. True words

by any chance will this work with mi 6x?

mugentech said:
by any chance will this work with mi 6x?
Click to expand...
Click to collapse
Some have tried, it doesn't unfortunately ?

Aww. Was hoping it would work on 6x since it's faster atm

Ähm.. mia2 + Hex Kernel is soooo faster than mi6xx ? and 6-7h of SOT on wifi (5-6h on 4g)
Again, a bit of patience, it will be all good. It is already for motivated flashers

dodjob said:
Ähm.. mia2 + Hex Kernel is soooo faster than mi6xx and 6-7h of SOT on wifi (5-6h on 4g)
Again, a bit of patience, it will be all good. It is already for motivated flashers
Click to expand...
Click to collapse
with this statement, will not buy 6x and wait for A2
saves me trouble of flashing PE on 6x
:fingers-crossed:

dodjob said:
Ähm.. mia2 + Hex Kernel is soooo faster than mi6xx and 6-7h of SOT on wifi (5-6h on 4g)
Again, a bit of patience, it will be all good. It is already for motivated flashers
Click to expand...
Click to collapse
Is the Hex kernel being done in collaboration with the X-team?
Their extreme kernel for the Mi A1 is crazy good.
Can you point me to the kernel file? I would like to test and report

enapah said:
It was an issue in the past, but now that there's wide support for the Google Pixel (which even has official LOS) things just got a lot easier. A/B is a non-issue for the end-user, the developer does need to check how things are done in the Pixel (which takes valuable time), but shouldn't be a deal breaker as everything is already public.
IMHO the real issue is the fact the Mi A2 wasn't really that popular to begin with (among the kind of enthusiasts that would only ever run a custom ROM, that is). When it launched, those enthusiasts preferred the whyred (which already had great support, namely official LOS). Shortly after, Poco happened.
I honestly think this device will be like most others, custom ROMs will either come straight from GSI (when vendor is fixed) or only after the Android One support ends (aka. when we'll be pressed to do something).
It's not too bad at all, it's just slightly disappointing because (1) Xiaomi timed their product releases poorly, not giving enough information to make an informed purchase; and (2) we kinda of expected a little more from Android One than to be grounded to stock or (now) a GSI.
At the end of the day it is up to us (everyone in this community) to do something about it (ie. start working on the device instead of expecting someone else to pick that job). Harsh words, but true nonetheless.
Click to expand...
Click to collapse
I agree with what you said. Its just unfortunate that this device got a lot of bugs despite its being an Android One phone. I'm sitting here just waiting for October update or Android Pie update so I can use my device without worries.