[Q] CM12.1 and Tap to Pay

[Q] CM12.1 and Tap to Pay - Moto X Q&A

First off, let me say: I am in no way asking for an ETA, just feasibility.
With the official update to 5.1 coming "Soon", is there a potential for the Cyanogenmod team to incorporate the necessary components to active the Tap-to-Pay feature for Google Wallet? My understanding was there are proprietary softwares not available once we left Kitkat for Lollipop ahead of Motorola. I freely admit my understanding of rom-building is as weak as it comes, but my imaginary setup has us able to take the required file from a Moto X running the official 5.1 and drop it into a CM12(.1) build for maximum profit.
So, am I indulging in pipe dreams out in left field?

Related

When Xposed for ART?

When Xposed available for ART? Today has left the Android SDK 5.0

Available whenever you make it work. We are all waiting on you. Hurry please.
Sent from my Nexus 5 using Tapatalk

Nice initiative Sheyla96. Do you have an ETA? I'm waiting too

It isn't an nice initiative at all. @rovo89 has said several times that it will come when it will come, he's doing this on his free time, jeez some people should just take a chill pill. ART hasn't been the official runtime for longer than 3 days and you're already starting, there isn't even a device running lollipop yet for god's sake! Sit down relax and wait for rovo to make his magic! @Sheyla96 @respider

I haven't seen any final version of ART yet, all just beta and preview versions. Even the version included in the latest emulator image (labeled "Android 5.0 / API 21") is at least a month old, or at least didn't include some of the commits of the master branch. Speaking of source code: It's still changing a lot. I wasn't able to build libart.so from source for the emulator as the included commit range is unclear (actually their Lollipop branch might be different from master, so knowning a date might not be enough). It's pretty hard to shoot such a fast-moving target. I hope that once a final version is out and the source code for is published (with a proper branch), changes will slow down a bit - and hopefully, vendors will use it pretty much unmodified.
I think I mentioned before that I had an early proof of concept for ART working in December. As I expected, many things had to be changed for the first L preview, and even then it didn't work. ART != ART. You may also have noticed that I haven't been here and didn't work on Xposd for the past three months for various reasons. I still don't have time and motivation to work on Xposed as I used to, but I'm slowly starting again (no promises though).
Last weekend, I started to try out a different approach, where I would make a few changes in the ART source code directly. This seems to be working much better and cleaner than trying to hack it from outside (especially because ART is much more complex and using many classes, templates etc. which are hard or impossible to work with). It also ensures control over the many variants it can be compiled with. The downside is that this would require replacing libart.so and libart-compiler.so on the system, and nobody knows whether vendors will build their ROMs with source code that is similar enough to AOSP to make this exchange possible. Then again, a library compiled against AOSP source probably wouldn't work with those ROMs either, as offsets etc. would be different.
Keep in mind that most of you are mainly interested in getting Xposed for Lollipop. ART is not the only new thing there, also SELinux is much stricter there, blocking many things required for Xposed. Not sure if there will be a different solution than disabling SELinux or exchanging the policy, both of which would probably require flashing a custom bootimage/kernel. But I'm not even thinking about this in detail yet, nor about different ways of installing Xposed (might be rather manually for the beginning). And I have no plans to use the Material Design anytime soon.
When I find the time and motivation, I will try to work on ART support. I will probably not be here and report about it though. When I think the time is right, I will publish my work-in-progress source code for others to help me (which requires a good understanding of advanced topics such as assembler/bytecode, so I'm afraid there won't be many people who can help). I consider everything I have done with ART so far as training - getting familiar with the source code, experimenting a lot, getting frustrated because it doesn't work most of the time. On Kitkat, ART is more or less a gimmick, most important it's optional. I might build an Xposed version that supports ART on Kitkat later if it can be maintained with little additional effort. If it's too different from the final ART, it will stay a proof of concept.
So in short: Wait until the final images and source code drop. Then wait again until it's ready. I can't give any estimation when that will be the case, it depends much on my personal situation. Chance are pretty low that it will be within a month after Lollipop release, and will get higher once I start thinking about flashing a Lollipop ROM myself (which would probably be CM12, and I think these guys won't give us a timeline either, for good reasons). I'm still not 100% sure Xposed for Lollipop will work, but I hope that in some way it will, even if it might not be as compatible with most ROMs and as easy to install as it is for Android 4.x.

TheHawk002 said:
It isn't an nice initiative at all.
Click to expand...
Click to collapse
I was just continuing @beren28 's joke assuming @Sheyla96 would implement it
sorry if looked like I was really asking for ETA

respider said:
I was just continuing @beren28 's joke assuming @Sheyla96 would implement it
sorry if looked like I was really asking for ETA
Click to expand...
Click to collapse
FWIW, I thought yours and @beren28's posts were hilarious, and surprised that they could be misunderstood.
@rovo89: Thanks a lot for giving it to us straight and taking the time to explain. Xposed is a miracle that has allowed great customization, even on stock ROMs, and it will be hard to give up. Knowing where we stand at least let's us make informed decisions about whether to upgrade to Lollipop or not.
On the positive side, several of the Xposed modules I use, are for tweaks and features that are included in Lollipop, so there is that too.

Is there any possibility of asking Google for official help on this project. I'd imagine with the help of some Android engineers, things would become a lot simpler. That is of course if Google even agrees in the first place, I don't know their stance on projects like this.
IMO Xposed is the shining highlight of dev projects on Android, it opened up so much for so many without needing a whole new rom, and Rovo89 cannot be expected to shoulder the burden himself now that L makes things much harder. We have so many talented devs here, can we have a call to arms in the open source community to help out?

ECrispy said:
Is there any possibility of asking Google for official help on this project. I'd imagine with the help of some Android engineers, things would become a lot simpler. That is of course if Google even agrees in the first place, I don't know their stance on projects like this.
IMO Xposed is the shining highlight of dev projects on Android, it opened up so much for so many without needing a whole new rom, and Rovo89 cannot be expected to shoulder the burden himself now that L makes things much harder. We have so many talented devs here, can we have a call to arms in the open source community to help out?
Click to expand...
Click to collapse
I think any help from Google would at best be hard to get. But if it works I think it would make integration with 5.0 easier.

rovo89 said:
So in short: Wait until the final images and source code drop. Then wait again until it's ready.
Click to expand...
Click to collapse
First I just want to say thank you so much for all the work you've done! Xposed has turned my Moto G into an even more awesome device.
But to clarify: if we decide to upgrade to Lollipop, does that mean we need to only disable the activated Xposed modules in the meantime, or do we need to completely uninstall the Xposed framework?

But to clarify: if we decide to upgrade to Lollipop, does that mean we need to only disable the activated Xposed modules in the meantime, or do we need to completely uninstall the Xposed framework?
Click to expand...
Click to collapse
With Xposed Installer on Neuxs 5, I never could use OTA updates, so when you flash the factory image, it overwrite the system partition, so Xposed is uninstalled. And when you'll try to reinstall it, it will display an error message.

rovo89 said:
... So in short: Wait until the final images and source code drop. Then wait again until it's ready. I can't give any estimation when that will be the case, it depends much on my personal situation. Chance are pretty low that it will be within a month after Lollipop release, and will get higher once I start thinking about flashing a Lollipop ROM myself (which would probably be CM12, and I think these guys won't give us a timeline either, for good reasons). I'm still not 100% sure Xposed for Lollipop will work, but I hope that in some way it will, even if it might not be as compatible with most ROMs and as easy to install as it is for Android 4.x.
Click to expand...
Click to collapse
Thanks for the update. Note that current ART has still not compiled for older armv6 architecture. It will have to in order to port Lollipop to such devices. Unless it will still be possible to use a Dalvik JVM in which case, good old Xposed will still be available.

Hello rovo89!
I just wanted to let you know that Xposed is genius and, unfortunately essential for me.
I'm one of the few unlucky people who are using Android with a MVNO, so I need to use XPosed with the National Roaming module to be able to use my Smartphone without the annoying roaming messages.
So with this post I want to say thank you for all the work you did yet!
Of course I'm hopeing that Sony will bring out 5.0 soon to my Z1 and I'm also hopeing that you will find a solution for all the upcoming problems with ART and I'm pretty sure you'll gona solve them!

Probably stay with 4.4.4 and xposed
I have my Nexus 4 set up just the way I want with xposed, gravity box and a couple other modules along with a slew of paid programs that open up lots more functionality that rooting affords . Battery life is as good as it will ever be and when the battery needs replacing, then I will replace it as I have no plans on getting a N6 any time soon. Even though I cheated by rooting with towel-root, I have grown accustomed to using the extra functionality that xposed and rooting has given me. Going to 5.0 will be a royal PITA to get the darn phone back to the way I want, if ever and I don't like the new material theme either - blech! I like xposed and am not truly convinced that lollipop will be better than what I have now.
However, I am an old timey linux user and I have learned long ago, to let others do the "bug-testing" and wait for the first update to the new OS before upgrading, so (5.1?). I remember the chorus of howls that went up when KK came out.
Now I do have a bone-stock unrooted Nexus 7 that will get upgraded to lollipop, so at least I have that to play with and if the new OS is that spectacular, then I will go the route of upgrading (maybe?).

@rovo89
Thanks so much for that clarification of the current status of things. I know what the deal is with Xposed development and would never have dreamed of querying (nagging) you for a status update, though I must admit I have been googling "ART xposed" quite frequently for the past months'ish, eager for any progress reports/updates. Sort of hoping that I would be able to hold off for ~"a couple of weeks" with upgrading to L and then do so with xposed running on ART. Knowing now that it'll be substantially(?) more than the aforementioned couple of weeks, I'll go ahead and take the leap once the final/public release of L drops (since I'm a latest-version-junkie, ho, hum), and I've got until then to adjust to the idea of not having my oh so beloved Xposed modules that have become an integral part of my Android experience. While I'll keep googling "ART xposed", I'll now (soon) be doing so not stuck on KitKat.
And I offer you my respect, admiration and gratitude for what you have created with Xposed (along with the module developers), for what it has done for my stock Nexus 5 and how it has changed my user experience. If Xposed for ART takes a month, a year, or never materializes, I applaud and salute you (and the module developers) for the work you have done so far. Thank you, most sincerely, thank you!
And should you change your policy on taking donations for Xposed, I've got some beer money with your name on it (unless you already have, in which case, what's your paypal?).. Regardless of what the future holds.
While this might probably be one of those posts that could fall under the category of "pressing the thanks button instead of writing a post that spams the thread when the thanks button would have been sufficient", I feel that this is a case of when the thanks button won't express my gratitude enough. And so I'll take my chances.

BathroomTile said:
But to clarify: if we decide to upgrade to Lollipop, does that mean we need to only disable the activated Xposed modules in the meantime, or do we need to completely uninstall the Xposed framework?
Click to expand...
Click to collapse
Definitely uninstall the framework (and anything else you may have installed on /system) if you'll be running the Lollipop OTA.
Personally I'll be using the opportunity to do a clean install. This is a big update.

Sorry for the spam, @rovo89, but I just wanted to thank you personally in words - I literally cannot use a device without Xposed any more! Guys like you inspire me to hack a bit on my own too! Cheers!

rovo89 said:
I still don't have time and motivation to work on Xposed as I used to, but I'm slowly starting again (no promises though).
When I find the time and motivation, I will try to work on ART support. I will probably not be here and report about it though.
Click to expand...
Click to collapse
What if there were some sort of donations available for your work on updating Xposed?. I know xposed is free, but could you set up a donation by app in Google Play store or through PayPal which would be directly for the work of xposed for Android L/ART? I'm sure there would be a lot of people who would be willing to put in some support for the work that you do. Just a suggestion

Give us Xposed now! No excuses! Just kidding, take your time but as mentioned many times, some people (including myself) only need the art framework to completly switch to art, that's the only thing what's holding us back. I not understand the argument art is beta, I guess if you see it that way the whole android is beta because there are almost daily changes.
If you need any help, testers and such let us know, but it's hard without any concept, so I hope you can show us some source and concepts soon.
Thanks for your hard work. We all waiting for 'final' sources to get our hands on.

Well, whether or not we'll ever see Xposed from Lollypop on, I must say that I understand your demotivation, and as much as I'd love to see it going forwards, what I have to give you is nothing but a big and warm thank you for giving Andoid users even more power over their phones and creating the most flexible framework there is. Kudos.

Android 5.0.1 (Pure edition)

For all of those who have the pure edition, shouldn't we already have 5.0.1 update? My understanding was that that the updates on the pure edition should be just like the nexus devices. Is this not the case?

No, updates on pure edition are not just like nexus devices . You've been misled. However, the moto x does get updates quicker than most other devices. Again, however, It all depends on the update.
For instance, I heard/read somewhere that the fixes in 5.0.1 are not needed for the moto x because Motorola had already squashed them themselves in the 5.0 update. So Motorola has no incentive to work on releasing a 5.0.1 update. Take that with a grain of salt. I have no sources, (can't remember where I heard it) but someone may chime in with more info supporting that or rebuking it.
But, no, nexus devices will always see updates first.

There was a second build of 5.0 pushed to the PE, but it doesn't fix the problems with Attentive Display or the ringer volume changes on Moto Voice (among other things).

Well, 5.0.1 hasn't even rolled out for the nexus 5 yet, they're still fixing things. Motorola has already released 5.0.1 for the Moto G, so we can expect it soon enough for our moto x as well, once they finish squashing all the bugs. They need to work on Moto Assist, Moto display etc to play well with lollipop so might take some time compared to the moto g which doesn't have any of these additional features

Demand for a new next level of rom!

As of every hour and every minute now we seeing new ROMs popping up for various devices now and but seems that the development for our ghost has come to end??
Well something requested by us is simply rejected by the senior members with all due respect.
For example:I recently demanded for a stock like Marshmallow based rom coming with all the special moto features like display,voice,etc.. but they rejected and recommended to try the cm 13 which loses all the Moto functionalities!?
Hence I finally put a request for one more time to build special type of ROMs for our moto devices just like the XOSP(Xperia open source project) and honourable name it as "MBOSP"(MotoBlur Open Source Project).

As much as i would love to have such rom, Moto X is 3 years a old device and I don't think anyone will work this much for an older device. I am using official CM13 by @Megatron007 and it is great. Maybe you should request the devs of existing roms to add Moto functionalities in their roms.

There can't be a Marshmallow stock rom, because there isn't a Marshmallow stock rom to start with.

There can be if built from aosp

LOL no

There can be atleast a stock like!

At this point I just want to have my verizon 1060 bootloader unlocked. I got it after it had been updated with no chance of putting cyanogen on it

I demand a working Nougat rom right now!
Those damn developers should do something to earn those salaries paid by XDA.

minimum a donation xD by users

"For example:I recently demanded for a stock like Marshmallow based rom..."
What are you paying?

ROMs

Questions....
I am currently running the Brazilian Stock Moto Android 6.0 ROM and I am loving it. However, I find myself missing the VoLTE from Verizon. That got me wondering about the available ROMs for the Turbo. If I understand correctly,
- If I want Android 6, my only options are this one, Kang, and CM-based ROMs, including ComputerFreek and Bliss. And those two ARE CM-based, correct? There are no other Marshmallow ROMs with stock Moto software, right? Chop chop for flashlight, etc?
- If my assumptions are right in that first part, I should ask: which ROMs include VoLTE?
Thanks for your help!
Sent from my XT1254 using Tapatalk

Marshmallow ROMs (I'm too lazy to provide links because XDA's app would make it a pain, but they're basically the at the top of the Droid Turbo/Moto Maxx Android Development forum):
AOKP
CM13
RR 5.7.X
Brazilian ROM (Stock Based)
Unofficial CM 13
MoKee 6.0
Bliss 6.4
Nexus Experience (NX)
AICP (in the AOKP thread)
(I think that's all of them.) All are CM based except for my Brazilian ROM.
VoLTE:
@computerfreek274's modified stock (Lollipop)
Stock Lollipop
Currently no CM based custom ROM supports VoLTE, nor my Brazilian ROM (stock based)

Thanks!
Sent from my XT1254 using Tapatalk

iiWoodstocK said:
Marshmallow ROMs (I'm too lazy to provide links because XDA's app would make it a pain, but they're basically the at the top of the Droid Turbo/Moto Maxx Android Development forum):
AOKP
CM13
RR 5.7.X
Brazilian ROM
Unofficial CM 13
MoKee 6.0
Bliss 6.4
(I think that's all of them)
VoLTE:
@computerfreek274's modified stock (Lollipop)
Stock Lollipop
Currently no CM based custom ROM supports VoLTE, nor my Brazilian ROM (stock based)
Click to expand...
Click to collapse
You left off Nexus Experience.
We have 8 Marshmallow ROMs currently if we count yours. It's not really a "custom" ROM -- except you customized it to work on all Quarks! (and did a good job)
Current custom Marshmallow ROM list for Droid Turbo/Moto Maxx/Moto Turbo
http://forum.xda-developers.com/showpost.php?p=68810980&postcount=39
None of the Quark Marshmallow ROMs at this point in time allow Verizon VoLTE.

ChazzMatt said:
You left off Nexus Experience.
We have 8 Marshmallow ROMs currently if we count yours. It's not really a "custom" ROM -- except you customized it to work on all Quarks! (and did a good job)
Current custom Marshmallow ROM list for Droid Turbo/Moto Maxx/Moto Turbo
http://forum.xda-developers.com/showpost.php?p=68810980&postcount=39
None of the Marshmallow ROMs give Verizon VoLTE.
Click to expand...
Click to collapse
DARN. I had an inkling I was missing one (actually 2 if I found AICP, though it doesn't have its own thread..)

iiWoodstocK said:
DARN. I had an inkling I was missing one (actually 2 if I found AICP, though it doesn't have its own thread..)
Click to expand...
Click to collapse
Right. I left off AICP ROM because
1) it doesn't have Ambient Display (which makes it a non-starter for most), and
2) the ROM maintainer (who also has Bliss and AOKP) isn't really actively supporting it with a separate thread like the other two.
It may be an interesting "project" but without Ambient Display (or the Moto Display in your stock Marshmallow ROM) what unique feature does AICP ROM have the other 8 Marshmallow ROMs do not? (For instance the Quark Resurrection Remix and Bliss ROMs have the ability to use most Moto apps. Your own stock-based ROM can use all Moto apps by default. AICP does not have that functionality.) And if you don't like Ambient Display/Moto Display, you can just turn it off on any of those 8 ROMs; you don't need to install a ROM with that feature lacking.

arizonaomnia said:
I am currently running the Brazilian Stock Moto Android 6.0 ROM and I am loving it. However, I find myself missing the VoLTE from Verizon. That got me wondering about the available ROMs for the Turbo. If I understand correctly,
- If I want Android 6, my only options are this one, Kang, and CM-based ROMs, including ComputerFreek and Bliss. And those two ARE CM-based, correct? There are no other Marshmallow ROMs with stock Moto software, right? Chop chop for flashlight, etc?
- If my assumptions are right in that first part, I should ask: which ROMs include VoLTE?
Thanks for your help!
Click to expand...
Click to collapse
@iiWoodstocK answered this, but I'm going to differentiate slightly.
There are two stock-based ROMs --
@iiWoodstocK Marshmallow Motorola ROM adapted from the XT1225 which will run on all Quarks, since he added CDMA prop lines and used custom kernel from @bhb27.
ComputerFreak274 Lollipop ROM based on Verizon's stock firmware. (Verizon has not released the XT1254 Motorola Marshmallow ROM yet, and may never do so.)
Neither of those ROMs are "CM-based". @bhb27 kernel is based on CM kernel, yes, but @iiWoodstocK's ROM is otherwise pure Motorola Marshmallow for Quark.
Currently, only ComputerFreak274 Lollipop ROM allows Verizon's VoLTE because it hews very closely to Verizon's firmware.
In another post higher up I gave a link to all the Marshmallow ROMs. No Quark Marshmallow ROM currently has Verizon VoLTE. @bhb27 (official Quark TWRP dev, Resurrection Remix & Mokee ROM maintainer, dev for several Quark apps) is still working on it, but with Verizon it's not something you just turn on and turn off -- there's also something on the carrier side that also allows it. @bhb27 is also limited in that he lives in Brazil, has an XT12225 and does not use Verizon. Somehow ComputerFreak274 ROM has it, and either he's not sharing the secret or maybe he doesn't even know why.

ChazzMatt said:
@iiWoodstocK answered this, but I'm going to differentiate slightly.
There are two stock-based ROMs --
his Marshmallow Motorola ROM adapted from the XT1225 which will run on all Quarks since he added CDMA prop lines and used custom kernel from @bhb27.
ComputerFreak274 Lollipop ROM based on Verizon's stock firmware.
Neither of those ROMs are "CM-based". @bhb27 kernel is based on CM kernel, yes, but @iiWoodstocK's ROM is otherwise pure Motorola Marshmallow for Quark.
Currently, only ComputerFreak274 Lollipop ROM allows Verizon's VoLTE because it hews very closely to Verizon's firmware.
In another post higher up I gave a link to all the Marshmallow ROMs. No Quark Marshmallow ROM currently has Verizon VoLTE. @bhb27 (official Quark TWRP dev, Resurrection Remix & Mokee ROM maintainer, dev for several Quark apps) is still working on it, but with Verizon it's not something you just turn on and turn off -- there's also something on the carrier side that also allows it. @bhb27 is also limited in that he lives in Brazil, has an XT12225 and does not use Verizon. Somehow ComputerFreak274 ROM has it, and either he's not sharing the secret or maybe he doesn't even know why.
Click to expand...
Click to collapse
CF's ROM has it because his ROM is built on stock. I don't believe he had to add it in especially since one of his more recent posts he stated he's been able to port the settings for VoLTE to his WIP Marshmallow ROM, but not functioning VoLTE itself.

iiWoodstocK said:
CF's ROM has it because his ROM is built on stock. I don't believe he had to add it in especially since one of his more recent posts he stated he's been able to port the settings for VoLTE to his WIP Marshmallow ROM, but not functioning VoLTE itself.
Click to expand...
Click to collapse
Then there must be some "flag" , some piece of code, in Verizon's firmware that says "this is a Verizon phone" or something. By him porting just the VoLTE settings to a Marshmallow ROM and VoLTE is not working means even he doesn't know what that "secret" piece of code is.
Back in the Microsoft DOS days when they were battling DR-DOS, Caldera who owned DR-DOS accused Microsoft of stealing DR-DOS code. (of course they did). Microsoft denied, denied, denied. Caldera file a lawsuit . In the final stage of the lawsuit, DR-DOS creator Gary Kildall had a card up his sleeve which he did not reveal until then. A demo in front of a judge. Microsoft technicians set up a custom built pristine PC with ONLY Microsoft DOS software. Microsoft oversaw all the installation and made sure no one else touched the computer.
Dr. DOS creator Gary Kildall then sat down at the "Microsoft" PC and typed in a simple keyboard command. In HUGE LETTERS a splash screen appeared which said displayed his name and copyright notice. He had hidden that in their code just for this kind of PROOF. Microsoft lawyers immediately requested a recess, followed by a generous multi-million dollar settlement offer tied to non-disclosure agreement. (No one has been able to find it since, because allegedly part of the agreement was to "license" the code and remove that notice.) Press reported $150 million, but allegedly it was actually even higher.
Part of the lawsuit also focused on anti-competitive measures from Microsoft, that Microsoft also purposely made PCs malfunction if Dr-DOS was installed, so people would thing Dr-DOS was buggy. Microsoft executive emails were found discussing this very tactic. But they weren't above STEALING code from Dr-DOS to put into Microsoft DOS. So, even though Dr-DOS was not installed on that demo PC, still the founder was able to call up a DR-DOS splash screen.
And yes, I read all this in a article years ago, which I cannot find now because maybe Microsoft lawyers are very zealous?
My point is something like that may be in Verizon firmware to allow VoLTE for Verizon devices? Some hidden code.

ChazzMatt said:
Then there must be some "flag" , some piece of code, in Verizon's firmware that says "this is a Verizon phone" or something. By him porting just the VoLTE settings to a Marshmallow ROM and VoLTE is not working means even he doesn't know what that "secret" piece of code is.
Back in the Microsoft DOS days when they were battling DR-DOS, Caldera who owned DR-DOS accused Microsoft of stealing DR-DOS code. (of course they did). Microsoft denied, denied, denied. Caldera file a lawsuit . In the final stage of the lawsuit, DR-DOS creator Gary Kildall had a card up his sleeve which he did not reveal until then. A demo in front of a judge. Microsoft technicians set up a custom built pristine PC with ONLY Microsoft DOS software. Microsoft oversaw all the installation and made sure no one else touched the computer.
Dr. DOS creator Gary Kildall then sat down at the "Microsoft" PC and typed in a simple keyboard command. In HUGE LETTERS a splash screen appeared which said displayed his name and copyright notice. He had hidden that in their code just for this kind of PROOF. Microsoft lawyers immediately requested a recess, followed by a generous multi-million dollar settlement offer tied to non-disclosure agreement. (No one has been able to find it since, because allegedly part of the agreement was to "license" the code and remove that notice.) Press reported $150 million, but allegedly it was actually even higher.
Part of the lawsuit also focused on anti-competitive measures from Microsoft, that Microsoft also purposely made PCs malfunction if Dr-DOS was installed, so people would thing Dr-DOS was buggy. Microsoft executive emails were found discussing this very tactic. But they weren't above STEALING code from Dr-DOS to put into Microsoft DOS. So, even though Dr-DOS was not installed on that demo PC, still the founder was able to call up a DR-DOS splash screen.
And yes, I read all this in a article years ago, which I cannot find now because maybe Microsoft lawyers are very zealous?
My point is something like that may be in Verizon firmware to allow VoLTE for Verizon devices? Some hidden code.
Click to expand...
Click to collapse
I wonder which Verizon devices have volte capability on custom roms. I was going to do a spreadsheet, but I haven't had time.

koftheworld said:
I wonder which Verizon devices have volte capability on custom roms. I was going to do a spreadsheet, but I haven't had time.
Click to expand...
Click to collapse
On various devices, I can't find any for Verizon with VoLTE that are not just stock modified ROMs.
The Nexus devices are the exception, like the Nexus 6.
My brother is getting an LG G3 VS985 for Verizon. I would love to root it and put on custom ROM like Resurrection Remix, but I can't find that VoLTE/Advanced Calling works with custom ROMs. I either get "no" or no answer when I ask the question in various forums.

ChazzMatt said:
On various devices, I can't find any that are not just stock modified ROMs.
The Nexus devices are the exception, like the Nexus 6.
My brother is getting an LG G3 VS985 for Verizon. I would love to root it and put on custom ROM like Resurrection Remix, but I can't find that VoLTE/Advanced Calling works with custom ROMs. I either get "no" or no answer when I ask the question in various forums.
Click to expand...
Click to collapse
Hopeful bb can find the right info from the logs that were provided. Would a huge win for those of us with Verizon as a network.

I *think* I've read Victara CM has Verizon VoLTE. Not 100% sure...

Any developers starting to tackle 7.1.2 AOSP build for Nexus 6?

I know that 7.1.2 on the Nexus 6 is not supported by Google, but anyone know if any of the developers tried incorporating based on the AOSP 7.1.2 chain?

You realize those are preview builds for the other devices right? Code isn't pushed to AOSP yet AFAIK. I think the highest is 7.1.1_r22
edit: maybe it is? https://android.googlesource.com/platform/system/core/+/android-n-mr2-preview-1

Not worth trying at the moment. The source will change from preview to the final build. It's better to wait until the final build gets pushed out and the full source code reaches aosp. In other words, patience, young grasshopper. We will get custom Roms based on 7.1.2 ?

Arju said:
Not worth trying at the moment. The source will change from preview to the final build. It's better to wait until the final build gets pushed out and the full source code reaches aosp. In other words, patience, young grasshopper. We will get custom Roms based on 7.1.2
Click to expand...
Click to collapse
Thanks gentlemen! I understand you want to base on the final build to hopefully get rid of most of the bugs..

and the big improvements between 7.1.1 and 7.1.2 are what?

Personally I think we all get too excited by these updates. Me, I struggle to see the major differences between Kitkat and 7.1.1 (I'm pretty unobservant, but hey, it's just a communication/entertainment device, yeah?) so although I look forward to playing with the new version I raraly see any killer difference. Android, to my eyes, is about as advanced as it can get until it can actually give me a backrub and a cup of fresh-brewed coffee in the morning. I'm not holding my breath...

dahawthorne said:
Personally I think we all get too excited by these updates. Me, I struggle to see the major differences between Kitkat and 7.1.1 (I'm pretty unobservant, but hey, it's just a communication/entertainment device, yeah?) so although I look forward to playing with the new version I raraly see any killer difference. Android, to my eyes, is about as advanced as it can get until it can actually give me a backrub and a cup of fresh-brewed coffee in the morning. I'm not holding my breath...
Click to expand...
Click to collapse
Are you also blind? Because Kitkat and Nougat are miles apart.

I'm short-sighted. No need to be offensive.
Examples? I can play videos, talk to people, text. What major (and I mean major) differences are there then? It's a phone and communications device. Kitkat did that. Nougat is just icing.
Go on, justify your statement rather than just being offended and offensive.

@admiralspeedy: No, @dahawthorne is right in that the changes in Android recently have been more evolutionary than revolutionary. The last really significant change in Android was switching from Dalvik to ART, which was experimental in Android 4.4.x and enabled in Android 5.x. and up.
Note that Material Design isn't a significant change, and neither is SEAndroid enforcement.

Strephon Alkhalikoi said:
@admiralspeedy: No, @dahawthorne is right in that the changes in Android recently have been more evolutionary than revolutionary. The last really significant change in Android was switching from Dalvik to ART, which was experimental in Android 4.4.x and enabled in Android 5.x. and up.
Note that Material Design isn't a significant change, and neither is SEAndroid enforcement.
Click to expand...
Click to collapse
Everything can't be "revolutionary" and being evolutionary hardly means that there are very few big changes. KitKat is the last iteration of Android to use the Holo theme and now through Lollipop, Marshmallow and Nougat we've had several major improvements to the entire Android interface through material design. The interface changes alone are enough to consider KitKat and anything newer, vastly different. You also mentioned Dalvik to ART, which is a huge change, but you failed to mention proper 64-bit support (beginning with Lollipop), more customization (such as the notification tray toggles), native multi-window, the official fingerprint API, and when the next iteration is released, KitKat will probably be dropped from security patches unless a ton of people are still hanging on to it.
Really the list goes on but I think it's quite ridiculous to say that the evolutionary changes made from KitKat to Nougat are hardly substantial.

But @dahawthorne never said there were no significant changes. All he said is he couldn't see them. As for what you've listed, nothing there is truly significant, not even 64-bit computing. That's not to say they're not welcome or anything like that, but Dalvik to ART is significant because it fundamentally changed how Android worked under the hood.
P. S. Calling other posters blind because you can't see their point? Ironic.

admiralspeedy said:
Everything can't be "revolutionary" and being evolutionary hardly means that there are very few big changes. KitKat is the last iteration of Android to use the Holo theme and now through Lollipop, Marshmallow and Nougat we've had several major improvements to the entire Android interface through material design. The interface changes alone are enough to consider KitKat and anything newer, vastly different. You also mentioned Dalvik to ART, which is a huge change, but you failed to mention proper 64-bit support (beginning with Lollipop), more customization (such as the notification tray toggles), native multi-window, the official fingerprint API, and when the next iteration is released, KitKat will probably be dropped from security patches unless a ton of people are still hanging on to it.
Really the list goes on but I think it's quite ridiculous to say that the evolutionary changes made from KitKat to Nougat are hardly substantial.
Click to expand...
Click to collapse
I think that my point would be best-illustrated by handing two phones (Kitkat & Nougat) to a "normal" user (i.e. non-XDA person interested in using the phone and uninterested in the technology). I can easily imagine the scenario because I'm married to one. She might say that the new icons look nice, and the design is easy on the eye. Dalvik/ART? Couldn't care less. 64-bit? Even *I* couldn't care less. Multi-window? Impractical even on my N6's large screen, and effectively a tech showpiece, a solution looking for a problem. My N6 and my wife's N5 don't have a fingerprint reader, and in any case that's more of a hardware feature requiring software rather than a software feature in its own right. And persuading her to let me install new security versions is like pulling teeth.
I therefore stand full-square behind my original "little difference" statement, because to the "normal" user that's exactly the case.

this thread actually is about differences between 7.11 and 7.12
and, whether you think there are major differences between lollipop, kitkat and nougat, I think we ALL can agree that the differences between a 7.11 os and a 7.12 os will hardly be worth anyone's time to get excited about.
maybe when it moves to 8.0 it will be significant, but a one dot move in ANY OS generally means absolutely nothing

dahawthorne said:
I think that my point would be best-illustrated by handing two phones (Kitkat & Nougat) to a "normal" user (i.e. non-XDA person interested in using the phone and uninterested in the technology). I can easily imagine the scenario because I'm married to one. She might say that the new icons look nice, and the design is easy on the eye. Dalvik/ART? Couldn't care less. 64-bit? Even *I* couldn't care less. Multi-window? Impractical even on my N6's large screen, and effectively a tech showpiece, a solution looking for a problem. My N6 and my wife's N5 don't have a fingerprint reader, and in any case that's more of a hardware feature requiring software rather than a software feature in its own right. And persuading her to let me install new security versions is like pulling teeth.
I therefore stand full-square behind my original "little difference" statement, because to the "normal" user that's exactly the case.
Click to expand...
Click to collapse
Agreed. The average person couldn't care less or even really tell a difference. My gf is the same way. She doesn't even Ike doing the monthly security updates to the point she made disable it lol. As long as it makes calls, texts, Facebook and a few websites then she is happy.

wase4711 said:
this thread actually is about differences between 7.11 and 7.12
and, whether you think there are major differences between lollipop, kitkat and nougat, I think we ALL can agree that the differences between a 7.11 os and a 7.12 os will hardly be worth anyone's time to get excited about.
maybe when it moves to 8.0 it will be significant, but a one dot move in ANY OS generally means absolutely nothing
Click to expand...
Click to collapse
l2tp protocol should be fixed in 7.1..2 according to issue #196939. it is something i was waiting for almost two years.

never heard of that, never read about that, have no clue about that, and you wont find any discussion about it on XDA, so, its not an issue that is at the forefront in anyone I knows mind...

wase4711 said:
never heard of that, never read about that, have no clue about that, and you wont find any discussion about it on XDA, so, its not an issue that is at the forefront in anyone I knows mind...
Click to expand...
Click to collapse
This is true that you are not seeing talks about it but just because you dont see anything said about it on XDA doesnt mean it is not in the forfront of anyones mind.
Talks like that really arent dont in the threads anymore but in private chats. 99% of any real development talks are done away from users these days.
As for 7.1.2 this will start to get really hard as this is when 32bit support dies and all of Google code is for 64 bit chips. Developers are already starting to see the change over and soo it will be true death for 32 bit devices. As porting it backwards is almost not conceivable.

To be honest, 32-bit supports won't go away, in fact it's required. Why? ARM Cortex A35 and A7 CPUs which will be here to stay, even though it's obviously true that industry and ROM developers are moving to 64-bit support (ie. AARCH64 AKA ARM64 mode) - ie. Cortex A53 and up to A73, the 32-bit ARM processors will still be used for many years to come, obviously for embedded battery life reasons, like Android Wear.
Otherwise, Nexus 6 will be my last 32-bit device (I know Android Oreo will still come onto Nexus 6 via Lineage OS, obviously because it will still support 32-bit mode for some reasons - Android Wear is based on full-blown Android OS, so if you remove 32-bit mode support, you risk breaking the watch ecosystem). I am kind of torn between ASUS ZenFone AR or Pixel 2. Hard choice.

Dr. Mario said:
To be honest, 32-bit supports won't go away, in fact it's required. Why? ARM Cortex A35 and A7 CPUs which will be here to stay, even though it's obviously true that industry and ROM developers are moving to 64-bit support (ie. AARCH64 AKA ARM64 mode) - ie. Cortex A53 and up to A73, the 32-bit ARM processors will still be used for many years to come, obviously for embedded battery life reasons, like Android Wear.
Otherwise, Nexus 6 will be my last 32-bit device (I know Android Oreo will still come onto Nexus 6 via Lineage OS, obviously because it will still support 32-bit mode for some reasons - Android Wear is based on full-blown Android OS, so if you remove 32-bit mode support, you risk breaking the watch ecosystem). I am kind of torn between ASUS ZenFone AR or Pixel 2. Hard choice.
Click to expand...
Click to collapse
Just because those chips are here doesnt mean the OS has to support it. Plus with the adaption rate of devices, by the time that it would matter 99% of devices will already being running a 64 bit chip.
Look at it this way. Google only works on code for their base devices. All 64bit.
As of LOS. If they dont have a base to work from then it will be very hard indeed.
They will not risk that. It is already in the works if you think about it. Only the n6 is a 32bit device that google supports. So they already have it setup for 64bit to work with the watch.
If you watch google source code you will see the transition.

True, but who knows, as of now? Google occasionally pull the surprises (I don't trust commit notes from certain companies such as Google, they occasionally put too much eggs into a basket - recent Nexus and Pixel muck-ups proves that), so it's possible they would either continue with transition or just cancel it and stick with hybrid builds. It's now more of a wait and see thing.

Database Develop

welcome