Related
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.
I wonder if someone could port dalvik over to Lollipop, as a stop gap until xposed is ported to ART
btw is xposed open source?
Im not gonna say its not possible... But its gonna be extremely difficult, and I don't think any devs are going to hop on anytime soon. Especially because it won't make Xposed work, since it's as much the SELinux restrictions as it is ART.
ya thats totally gonna be easier, porting an entire runtime to an operating system that doesnt even support it instead of porting an app.
Dalvik has been ported to other os's, lollipop is just a version bumb of android. On kitkat you could switch between the 2, i doubt that code is gone...
This is stupid
jawz101 said:
This is stupid
Click to expand...
Click to collapse
Well... That's a bit rude, but I must agree that this is something that would not be worth the effort.
jawz101 said:
This is stupid
Click to expand...
Click to collapse
Necessary? At all?
This is equivalent to saying why don't we port a 1991 Toyota Camry engine into a Ferrari just so we can get easier oil changes.
BTT8 said:
This is equivalent to saying why don't we port a 1991 Toyota Camry engine into a Ferrari just so we can get easier oil changes.
Click to expand...
Click to collapse
more like a celica. Dalvik has been ported to many other platforms and os's, so it should be relatively easy to port dalvik to lollipop. @rovo89 might not be able to make xposed compatible with art for many more months but in the mean time we could still enjoy most of lollipop but with xposed. I don't think the performance difference, if we can get the qualcomm optimized versions to run, to be significantly different.
Sorry if I offended but I'm really not sorry.
ART, SELinux enforced and device encryption on by default are what make Android L what it is. Any option that cripples any one of those things isn't what you want. I'd just keep those things in mind. If something comes along that works within those constraints (Cydia Substrate/XPosed) I'd respect the work because it would be the elegant solution.
I respect @rovo89 's stance so if he didn't say one more word about Android L I'd understand.
The best thing we users can do is leave it alone so some inspired developer can have a shower thought that is a good compromise.
I'd just think anything else would be a KitKat that looks like a Lollipop.
people really need to just let xposed for lollipop go. Seriously, it will get here when it gets here, making 1000 threads asking for "stop gaps" and time frames isnt going to make it come sooner. Either chill on kitkat for the time being, or chill on lollipop without xposed. those are your only two options. rovo even said that its likely to take months to port, if he ports it at all. Its been a week, id say check back in january
I understand why some are saying just wait or why do that its just a stop gap but Android is open source, there has to be commits that have notes as to when dalvik was removed. ART has been an option in KitKat. Android can switch between the two. Maybe even having possibly both running at the same time so new apps built just for ART continue working. If developers look through the changes to Android from KitKat to Lollipop, they could take what was removed and add it back in. Maybe it won't be that simple but Android is open source, when Windows lost its start menu, third party developers could put it back in. Others made their own variation of it that was different but there were ways of putting the Windows 7 start menu back in on Windows 8. I know the two aren't the same but everything Android is made of is available online for public use. Look right before it was taken out, take that, and put it right back in and make some changes for Android to see that. And yes Dalvik has been ported to other platforms, if Windows Phone eventually runs Android apps or its been experimented on internally, they ported Davlik too.
Considering that with the Surface for example people wanted Win32 support for Windows RT, even though they knew WinRT apps were the future, they still did it and we could run .NET apps on the desktop. Sure it was an old runtime but it was a mature runtime. Again we really don't know if xposed will make it to the ART runtime...
On Samsung phones, SELinux is enforced already long time (since 4.3, IIRC). And it was changed to permissive or even completely disabled (as i did on my device). Thus, it's not a problem at all. Encrypting the storage is not a mandatory thing as well and can be disabled as well.
Actually, i see a real demand of dalvik on Android 5.0. All these security things are not deal-breaker. Having a root and talking about security is a lame, IMHO.
The only real thing to sacrifice is the ART. Well, at least you will be able to choose between XPosed versatility and ART speed.
Actually, i'm running Android 4.4.2 without ART and don't see any special need of ART.
For those who are using current devices, it's easy to stay on 4.4 and continue to use XPosed. But for future devices with Android 5.0 out of the box, there won't be a chance to use XPosed without such dalvik port.
I think, it won't be so hard to port the dalvik to 5.0, since it's just couple of libs/binaries. At least for AOSP. With may be some more work for OEM ROMs.
godutch said:
I wonder if someone could port dalvik over to Lollipop, as a stop gap until xposed is ported to ART
btw is xposed open source?
Click to expand...
Click to collapse
sorry to see that instead of an exchange of info you get treated rudely by some who think they swollowed wisdom with a spoon
here is my answer:
the idea itself is IMO not stupid at all, albeit i think like others that it will probably be easier to make xposed work on LP. why ?
a) rovo89 already had a trial version on art about 10 months ago, so i do not believe that it will be impossible to port XF to ART
b) selinux can be set to permissive with an app as well as kernel side, as simple as that, and should this be necessary and the choice of some, no problem
c) i stick to KK until either XP will come to LP or most of the keyfeatures i want under all circumstances will be available through other means, partly they are already.
d) i don't know if it's open source, you will probably have to search a bit
i believe that there are 2 big question marks behind the question whether we shall get XF for LP:
1) if the dev has time and energy ( is motivated ) to go there
2) for which devices it will be available, because for some reasons you can get from his various statements it will certainly not be as cross-rom as it was before LP
"1)" was answered by rovo89 with a tendency to a no, but that can change, "2)" is not predictable but most probably the closer to vanilla android the higher the chance that it will be compatible if ever
as i said, i shall stick to kitkat for many reasons, want dark UI, want by app dpi settings like earlier PA-ROMs had and app settings is doing for me. for the rest there are apps and mods mostly so and
the only thing which i don't like compromises is UI-Appearance, wasted space, ugly colors and chaotic animations and pop-ups. so let's see, keep watching regularly and there is still hope. should you have specific needs which you now use xposed modules for, search for apps and mods with the same or similar effects. mostly one can get or make a flashable zip for mods so to flash them with nightlies like i do by now with the xposed installer and a few helpers which have to be system apps, no problem.
the fact that many things are possible to get with other means might even be an obstacle for xposed to be ported to LP, it's not so that xposed does a lot which cannot be had by other means, just that it's so easy and cross rom, cross oem etc. i hope that is a useful input for you and feel free to pm me because i will not further follow this thread, last but not least because of the general tone and attitude of some individuals.
sionicion said:
I understand why some are saying just wait or why do that its just a stop gap but Android is open source, there has to be commits that have notes as to when dalvik was removed. ART has been an option in KitKat. Android can switch between the two. Maybe even having possibly both running at the same time so new apps built just for ART continue working. If developers look through the changes to Android from KitKat to Lollipop, they could take what was removed and add it back in. Maybe it won't be that simple but Android is open source, when Windows lost its start menu, third party developers could put it back in. Others made their own variation of it that was different but there were ways of putting the Windows 7 start menu back in on Windows 8. I know the two aren't the same but everything Android is made of is available online for public use. Look right before it was taken out, take that, and put it right back in and make some changes for Android to see that. And yes Dalvik has been ported to other platforms, if Windows Phone eventually runs Android apps or its been experimented on internally, they ported Davlik too.
Considering that with the Surface for example people wanted Win32 support for Windows RT, even though they knew WinRT apps were the future, they still did it and we could run .NET apps on the desktop. Sure it was an old runtime but it was a mature runtime. Again we really don't know if xposed will make it to the ART runtime...
Click to expand...
Click to collapse
Its not just ART that is the issue. 5.0 has many new security features that block its use. You have have to revert alot of the entire OS to work with Delvic. Just like ART caused issues with the OS when it was still being worked on.
And not completely as for Android being open source. AOSP is open source (Which Google doesnt push all the code to, You can see this with many of the apps in 5.0 The messaging app is not in AOSP as an example) but not everything android does from Google is not open source. Only the kernel is fully open under the GPL. The rest is under the apache license.
sorg said:
On Samsung phones, SELinux is enforced already long time (since 4.3, IIRC). And it was changed to permissive or even completely disabled (as i did on my device). Thus, it's not a problem at all. Encrypting the storage is not a mandatory thing as well and can be disabled as well.
Actually, i see a real demand of dalvik on Android 5.0. All these security things are not deal-breaker. Having a root and talking about security is a lame, IMHO.
The only real thing to sacrifice is the ART. Well, at least you will be able to choose between XPosed versatility and ART speed.
Actually, i'm running Android 4.4.2 without ART and don't see any special need of ART.
For those who are using current devices, it's easy to stay on 4.4 and continue to use XPosed. But for future devices with Android 5.0 out of the box, there won't be a chance to use XPosed without such dalvik port.
I think, it won't be so hard to port the dalvik to 5.0, since it's just couple of libs/binaries. At least for AOSP. With may be some more work for OEM ROMs.
Click to expand...
Click to collapse
if it isnt hard than why dont you do it?
you already seem to know more about dalvik than anyone posting in this thread, please save all new devices running 5.0.1 and port dalvik to 5.0.1
seriously whats so hard about people waiting for xposed to be ported if it ever gets ported, and if it doesnt, who cares, just install a custom rom, thats how it was done before xposed was even created
luigi90210 said:
if it isnt hard than why dont you do it?
you already seem to know more about dalvik than anyone posting in this thread, please save all new devices running 5.0.1 and port dalvik to 5.0.1
seriously whats so hard about people waiting for xposed to be ported if it ever gets ported, and if it doesnt, who cares, just install a custom rom, thats how it was done before xposed was even created
Click to expand...
Click to collapse
None of device i use got Android 5.0. So, it's hard to port without having it yet, isn't?
Reading rovo89 posts, i'm not so optimistic about it happen at all. Actually, i'm not depend much of XPosed (and i'm happy that i didn't move all my custom ROM patches to XPosed). Only one security module i've wrote is very important and vital for me and potential deal-breaker from migrating to 5.0. Actually i can rewrite it to patches which is not so elegant solution but a real solution. When Samsung will release 5.0 (or i will buy a new device), i will check all possibilities.
Actually, i have an idea for system similar to XPosed. May be it's not so elegant as XPosed, but it's 100% compatible with 5.0.
Anyway, i'm waiting for 5.0 first.
sorg said:
None of device i use got Android 5.0. So, it's hard to port without having it yet, isn't?
Reading rovo89 posts, i'm not so optimistic about it happen at all. Actually, i'm not depend much of XPosed (and i'm happy that i didn't move all my custom ROM patches to XPosed). Only one security module i've wrote is very important and vital for me and potential deal-breaker from migrating to 5.0. Actually i can rewrite it to patches which is not so elegant solution but a real solution. When Samsung will release 5.0 (or i will buy a new device), i will check all possibilities.
Actually, i have an idea for system similar to XPosed. May be it's not so elegant as XPosed, but it's 100% compatible with 5.0.
Anyway, i'm waiting for 5.0 first.
Click to expand...
Click to collapse
well if xposed dies than it dies, i really think people should either way for it to be ported or just let it die, threads like these are annoying, pointless, and do absolutely nothing to further porting xposed to android L
luigi90210 said:
well if xposed dies than it dies, i really think people should either way for it to be ported or just let it die, threads like these are annoying, pointless, and do absolutely nothing to further porting xposed to android L
Click to expand...
Click to collapse
Then you've misused this topic. This topic is about dalvik for Lollipop, not about porting XPosed.
sorg said:
Then you've misused this topic. This topic is about dalvik for Lollipop, not about porting XPosed.
Click to expand...
Click to collapse
which someone wants to do because they dont have xposed
like i said, if you want to port dalvik to lollipop than do it since you think its so easy, if you are confident in your knowledge why not get a tester with a lollipop phone or better yet buy a used nexus 4 to work on, that has lolllipop and runs about $100 used
Hi. I'm thinking of getting a Nexus 6. One thing I'm curious is how are people coping with not have Xposed modules. Are you depending on custom roms and themes to make up the difference? Currently on my Note Edge I use App Settings, Heads Up Notifications, Multiwindow plus. Notifly Clean, Swipeback and YouTube Adaway among others. For example App Settings really comes in handy for changing look of apps and such (can give more of a tablet UI). I'd especially like to hear from folks that heavily used Xposed in the past to get their impressions. Anyways, I might get a N6 or wait a bit more to see what comes out at CES. Thanks!
mscion said:
Hi. I'm thinking of getting a Nexus 6. One thing I'm curious is how are people coping with not have Xposed modules. Are you depending on custom roms and themes to make up the difference? Currently on my Note Edge I use App Settings, Heads Up Notifications, Multiwindow plus. Notifly Clean, Swipeback and YouTube Adaway among others. For example App Settings really comes in handy for changing look of apps and such (can give more of a tablet UI). I'd especially like to hear from folks that heavily used Xposed in the past to get their impressions. Anyways, I might get a N6 or wait a bit more to see what comes out at CES. Thanks!
Click to expand...
Click to collapse
I have adaway on my Nexus 6 and it works great. It's part of the LS ROM. The Nexus 6 is fine without xposed even after using it heavily on all of my other phones. If you want a tablet UI then you can change the DPI on your phone to 320 (560 is stock) and most people seen to like 460-480dpi. It's well worth the upgrade if you love to flash. Anything from CES (LG, ASUS, Samsung etc..) Won't have nearly as much development if any compared to a Nexus device. I like to flash ROM's and kernels so rather than deal with the hassle of unbricking a LG or Samsung with factory tools I can flash the stock ROM via fastbokt with my nexus easily. It's all up to what you plan to use the phone for. Any new phone debuting this year won't have xposed anyway because they will have lollipop
Your problem is not the Nexus 6, your problem is with Lollipop. Due time, Xposed will be made to work with ART.
Regardless of whatever phone you're using, if it has Lollipop, Xposed will not work.
Pilz said:
I have adaway on my Nexus 6 and it works great. It's part of the LS ROM. The Nexus 6 is fine without xposed even after using it heavily on all of my other phones. If you want a tablet UI then you can change the DPI on your phone to 320 (560 is stock) and most people seen to like 460-480dpi. It's well worth the upgrade if you love to flash. Anything from CES (LG, ASUS, Samsung etc..) Won't have nearly as much development if any compared to a Nexus device. I like to flash ROM's and kernels so rather than deal with the hassle of unbricking a LG or Samsung with factory tools I can flash the stock ROM via fastbokt with my nexus easily. It's all up to what you plan to use the phone for. Any new phone debuting this year won't have xposed anyway because they will have lollipop
Click to expand...
Click to collapse
zephiK said:
Your problem is not the Nexus 6, your problem is with Lollipop. Due time, Xposed will be made to work with ART.
Regardless of whatever phone you're using, if it has Lollipop, Xposed will not work.
Click to expand...
Click to collapse
Thanks for your replys. I was wondering if folks could change dpi on apps individually instead of globally.
Clearly lollipop is inevitable. I've tried a recently released developers version of lollipop on my former dd (Note 3) and it has some nice features plus some Note 4 multiwindow improvements. But I also missed my Xposed mods when using it. The main problem I'm having with the EDGE is that I'm not sure how much development will continune on it. Currently there are two very nice roms (I'm refering to tmobile here variant) but no custom kernels. So I guess I'm suffering from developer envy lol... CES should be interesting in that more devices should be introduced with 64 bit processors along with, perhaps some of the larger screen sony devices. At lest that is the hope!
If it's possible to get kitkat on our device with dalvik run time, please someone port it.
I hate lollipop. why? almost all the apps on the play store aren't optimized for ART/lollipop.
It's just pain to see my new nexus 6 stutters on apps that can run on my old 5S smoothly
No it is not possible. Someone can't just port Kit Kat because there are a lack of drivers and binaries for it.
Apps will just have to get to the times and update to make it more optimized for Lollipop, or get "better" or more frequently updated apps to follow with the times.
zephiK said:
No it is not possible. Someone can't just port Kit Kat because there are a lack of drivers and binaries for it.
Apps will just have to get to the times and update to make it more optimized for Lollipop, or get "better" or more frequently updated apps to follow with the times.
Click to expand...
Click to collapse
That is actually quite a silly statement.
It actually would NOT be all that much work to build 4.4 for this hardware.
For one, all of the blobs needed can be pulled from Droid_turbo / Moto_maxx. They are basically the same hardware, and ship with 4.4.
Second, qualcomm supports the apq8084 platform on 4.4 directly. I have a liquid 8084 tablet with 4.4 on my desk right next to me right now.
Having said that... I'm not going to build 4.4, because it is pointless.
---------- Post added at 06:49 PM ---------- Previous post was at 06:38 PM ----------
dustin4vn said:
I hate lollipop. why? almost all the apps on the play store aren't optimized for ART/lollipop.
Click to expand...
Click to collapse
What exactly do you mean by "aren't optimized"??? As a developer, I have to say that this statement is completely meaningless. There is nothing special that need be done from a software developer point of view to take account for ART, as long as you aren't doing weird and unsupported hacks (which very very very few people actually do).
It's just pain to see my new nexus 6 stutters on apps that can run on my old 5S smoothly
Click to expand...
Click to collapse
What do you mean by "stutters"? Is there heavy I/O happening when it is "stuttering"? Do you realize the serious impact that forced encryption has on the device's I/O and CPU performance? Do you realize that the display on N6 has nearly TWICE as many pixels as your "old" S5? That means that it is GOING to take a lot more to keep things fluid on N6 than S5. Something that will be helped when software starts to take advantage of the newer OpenGL available on 5.0. NONE of this will be improved by downgrading to 4.4. In fact, because 4.4 will NOT be taking advantage of the newer OpenGL, doing this downgrade will make certain, even after software starts to make use of it, that you WON'T be able to benefit from it.
doitright said:
That is actually quite a silly statement.
It actually would NOT be all that much work to build 4.4 for this hardware.
For one, all of the blobs needed can be pulled from Droid_turbo / Moto_maxx. They are basically the same hardware, and ship with 4.4.
Second, qualcomm supports the apq8084 platform on 4.4 directly. I have a liquid 8084 tablet with 4.4 on my desk right next to me right now
Click to expand...
Click to collapse
If it's not that much work then why you don't do it and prove me wrong? You'd need proprietary vendors, drivers for 4.4 and not to mention you'd need a backward port of dalvik.
Just because they share similar hardware doesn't mean you can just pull blobs from another phone with similar hardware specifications from the same manufacturer then hope that it works because development doesn't work that way
Even if it was possible no one would do it because its a step backwards and it would be a dirty hack.
i would have chimed in a while ago, but for certain reasons i didnt. normally, id say that it wont happen, since there arent any binaries for kitkat and the nexus 6. but guess what, there are! they arent anywhere where the public has access to them, but they do exist. as google had kitkat on the n6 before lollipop. and a very few people have even gotten their n6 with kitkat(when they just selling the n6). so, in the future, we might be able to see a kitkat build on our n6
zephiK said:
If it's not that much work then why you don't do it and prove me wrong? You'd need proprietary vendors, drivers for 4.4 and not to mention you'd need a backward port of dalvik.
Click to expand...
Click to collapse
I'm not going to, because it is a waste of time and I have no interest in having a **** measuring contest with some random person on the internet.
Just because they share similar hardware doesn't mean you can just pull blobs from another phone with similar hardware specifications from the same manufacturer then hope that it works because development doesn't work that way
Click to expand...
Click to collapse
That's hilarious. Especially since hardware wise, the only real difference between those phones I mentioned and Nexus 6 is the screen size. In fact, we know for a fact that those two devices very nearly WERE stamped "shamu" and sent out AS Nexus 6. Something happened between Google and Verizon that decided what size went under whose label. Also, you should see all the Sony blobs I used on my Samsung phone... also a bunch from LG.
But just to make things even more interesting, on what grounds do you claim that Android 4.4 won't run on blobs from 5.0? That same Samsung phone I referred to above running on Sony and LG blobs... is running 5.0 on such mishmash of blobs pulled out from 4.[0-4]. And perfectly happily at that. Blobs DO NOT HAVE an intrinsic "works with Android version X and nothing else" stamped on them.
Even if it was possible no one would do it because its a step backwards and it would be a dirty hack.
Click to expand...
Click to collapse
THAT is essentially what I am saying. Not the "even if" (because it *IS* possible), or the dirty hack part, because though it may make you FEEL dirty to downgrade, it wouldn't actually be a hack. I'm saying that nobody WILL do it, because it is pointless and backwards.
dustin4vn said:
If it's possible to get kitkat on our device with dalvik run time, please someone port it.
I hate lollipop. why? almost all the apps on the play store aren't optimized for ART/lollipop.
It's just pain to see my new nexus 6 stutters on apps that can run on my old 5S smoothly
Click to expand...
Click to collapse
This phone would have been awesome on Kitkat. I also do not like Lollipop. It burns the eyes and there are too many bugs. I don't think anyone is going to go to the trouble though.
Evo_Shift said:
This phone would have been awesome on Kitkat. I also do not like Lollipop. It burns the eyes and there are too many bugs. I don't think anyone is going to go to the trouble though.
Click to expand...
Click to collapse
As far as bugs go, its no different than any previous version. They patched a bunch of bugs that were there before, and added a few new ones. I wonder though, what bugs you think you've spotted? List them, and tell me why you believe that they are bugs...
Just port android 1.5 cupcake and call it a day lol
md1008 said:
Just port android 1.5 cupcake and call it a day lol
Click to expand...
Click to collapse
haha, lol. Now that... might actually not be possible.
doitright said:
haha, lol. Now that... might actually not be possible.
Click to expand...
Click to collapse
Time to do a change petition from google to make official cupcake ROM lol
zephiK said:
If it's not that much work then why you don't do it and prove me wrong? You'd need proprietary vendors, drivers for 4.4 and not to mention you'd need a backward port of dalvik.
Just because they share similar hardware doesn't mean you can just pull blobs from another phone with similar hardware specifications from the same manufacturer then hope that it works because development doesn't work that way
Even if it was possible no one would do it because its a step backwards and it would be a dirty hack.
Click to expand...
Click to collapse
I am gonna go ahead and just attach it to your post. There is a port being worked on as I post this, yes there are people who want kit kat on the phone and there are other reasons than running cm, aosp or stock. Enough said and more will be revealed in the nexus 6 forums hopefully within the next week we will see how bad it really gets
fun..
to bad kitkat will not work on the n6 without drivers for kitkat. unless its a lollipop rom thats just themed like kitkat.
simms22 said:
fun..
to bad kitkat will not work on the n6 without drivers for kitkat. unless its a lollipop rom thats just themed like kitkat.
Click to expand...
Click to collapse
You may be right and I might be wasting time. Something to do though
jhr5474 said:
You may be right and I might be wasting time. Something to do though
Click to expand...
Click to collapse
i actually think you should keep trying, seriously. maybe it is possible to modify the lollipop drivers for kitkat, or modify the n5 drivers for kitkat for the n6. anyways, it woukd be neat to try kitkat on the n6
I thought the Nexus theory was to have the latest and greatest and never look back. Time would be better utilized squashing bugs in M.
prdog1 said:
I thought the Nexus theory was to have the latest and greatest and never look back. Time would be better utilized squashing bugs in M.
Click to expand...
Click to collapse
it is.. but we also cant forget about nostalgia D
my n5 died this week, after flashing m, seriously. andvi found my old sgs4 that hasnt been powered on in nearly 2 years, its running android 4.3
simms22 said:
it is.. but we also cant forget about nostalgia D
my n5 died this week, after flashing m, seriously. andvi found my old sgs4 that hasnt been powered on in nearly 2 years, its running android 4.3
Click to expand...
Click to collapse
My son got robbed of his S6 by knifepoint. Ran my S3 4.3 for a couple days. Verizon Samsung on ATT not a beautiful experience. Lol Ran an old HTC Inspire on 2.3 Ginger for a week or so. Sister gave him Note 3 so he back to Lolli now.
prdog1 said:
My son got robbed of his S6 by knifepoint. Ran my S3 4.3 for a couple days. Verizon Samsung on ATT not a beautiful experience. Lol Ran an old HTC Inspire on 2.3 Ginger for a week or so. Sister gave him Note 3 so he back to Lolli now.
Click to expand...
Click to collapse
i actually rooted it and flashed safeline recovery, first time ever! lol. i used kingsroot, a one click app to root. its a verizon phone, so i cant ever use it on a provider. but makes good calls over hangouts
simms22 said:
i actually rooted it and flashed safeline recovery, first time ever! lol. its a verizon phone, so i cant ever use it on a provider. but makes good calls over hangouts
Click to expand...
Click to collapse
Why can't use it on provider. He has used Verizon Rezound on TMO and S3 on ATT. Not perfect but they work. He bad about breaking **** and never buys insurance.
Given the fact that Xposed does not work on art how will that affect your decision to upgrade to Android L?
Comments should include lots of beer for Rovo89.
Due to xprivacy needing xposed it's the only thing that makes me still use kitkat..
Sent from my GT-i8190 using XDA Free mobile app
Aren't "no" and "I will wait until Xposed works with ART" the same answer? If you won't upgrade without Xposed ("No"), that seems to imply you would upgrade if it works with ART.
I'm willing to wait, there are a few Xposed mods I really care about like Xposed call block, full use of Greenify, MinMinLock and RootCloak, and others I could probably learn to live without but still find convenient like Chrome New Tab, CrappaLinks, Play Store link in App info, PlayPermissionsExpoxed, Statusbar Scroll to Top, and Swype Tweaks.
I upgraded my Nexus 7 to Lollipop (on Purity ROM) without Xposed, but I don't use that daily like my phone, so on that I'm wiling to wait, and even stay on KitKat indefinitely.
I can stick with KK for many more years.... Until Xposed come for LP, I WIL NOT have LP... Simple...
Perhaps it's just me, but, I'm also still on win7, until...
You may stick with KK and Xposed for years, but devs probably no. They would slowly abandon their modules, if Xposed framework development stopped.
Nah I will wait. There isn't single feature in Lollipop that isn't in KitKat.
I've been holding out, but just last night I decided to try out CM12 through MultiRom and now I'm completely torn.
On one hand, I have my beloved Xposed modules which add awesome functionality as well as some fantastic visuals (Flat Style Keyboard is the most difficult to give up...) and on the other hand is the absolutely beautiful experience of using Lollipop. I hadn't used it first-hand until now, and I was honestly blown away, and still am after using the rom all day today. Everything is just so much smoother and feels like it is working the way it should. I feel that with material design, Android finally stands up to iOS in terms of visual appeal, fluidness, and consistency.
*sigh* I suppose I'll find myself switching off between the two roms for a while, unable to choose one.
Still on 4.4.4, cause xposed isn't compatible with lollipop yet :-/
Sent from my Nexus 5 using Tapatalk
Sublation said:
...upgrade to Android L? ...lots of beer for Rovo89.
Click to expand...
Click to collapse
Rovo developes Xposed for other reason, not beer, not money. Let us hope he still has reason strong enough to open up ART so Xposed modules will work on Lollipop.
Point of clarification: "Android L" is an early version of Lollipop. Since then, we have seen Android 5.0, Android 5.0.1, and the latest is Android 5.0.2, which is the only Lollipop I have tried. After trying it for about 2 days, I went back because I felt need for my Xposed modules. But, after only a few hours off Lollipop, I went back to it! And then, began finding work arounds for missing features. ART is so smooth and responsive, and Lollipop has a great new recent apps switcher 'Rolodex' that is wonderfully fluid, useful, and fun. I love these and other things Lollipop brings. Found ways to deal with all desired features. Even Xprivacy issues have work arounds, thanks to App Ops in CM-12. None the less, while using and enjoying Lollipop, I am keeping up hope that Rovo brings Xposed to ART.
using CM12 without xposed
Please, that is exactly the reason why the dev have no motivation to spend energy in this project any more.
No question, exposed is a revolutionary mod for android geeks like us.
Don't put pressure on the dev!
Thanks for attention
Still on KitKat. Mainly because it allows me to continue maintaining and supporting my xposed modules.
Would be too uncomfortable to switch ROMs everytime I need to test stuff.
I decided to pull the plug on kitkat and upgrade my exynos S5. I'm definitely missing the xposed experience on my phone. Starting from the full use of greenify ( especially wake-up tracker and cutoff) to all the small tweaks and quirks we're doing to our UI, and the whole OS.
It made me not take for granted the huge amount of work put into the framework itself, and the work put in by the devs of all the modules that we use daily. Huge thanks to all the developers out there and I hope one day we will have a working version of the xposed framework for the new Android iteration.
I'm on my way to make a donation to the xposed framework Dev and I encourage others to do so too.
Plan on staying with KitKat unless I decide to switch to Cyanogen. Being on a Note 3 I kinda have mixed feelings missing some S-Pen functionality.
I had to make the jump, at least temporarily. . Definitely missing some things, but nothing I can't live without.
I've upgraded to Lollipop several times now, but have reverted to KitKat each time. Not specifically because of the XPosed incompatibility, although that affected my decision. Mostly because the ROM I'm using now on my i9300 has so much extra functionality. Secondarily, Lollipop simply isn't giving me the battery life I've been getting on the KitKat I'm using--and that's something I find very important in a ROM.
That being said, again today I've tried a newer version of what's billed as one of the better Lollipop ROMs for my set; we'll see if I stay with it.
I only have one XPosed module that I use, and it's visual, so...although I miss it, I can live without it.
Yep still on kitkit cm11, mostly because of xposed and XMG compatibility not present on cm12. stupid ART!
i would like to hit over to android 5, for the fact that call sound actually works with latest Google Play Services... but its a minor setback sticking with kitkat... not like i get called enough that it bothers me much, #foreveralone :crying:
still sucks that i cant use most gapps cause of this =/ (i restored factory version, which doesn't self update)
ah well will have to wait a few months to see the progress of xposed and xmg ART runtime compatibility
adrscu said:
I decided to pull the plug on kitkat and upgrade my exynos S5. I'm definitely missing the xposed experience on my phone. Starting from the full use of greenify ( especially wake-up tracker and cutoff) to all the small tweaks and quirks we're doing to our UI, and the whole OS.
It made me not take for granted the huge amount of work put into the framework itself, and the work put in by the devs of all the modules that we use daily. Huge thanks to all the developers out there and I hope one day we will have a working version of the xposed framework for the new Android iteration.
I'm on my way to make a donation to the xposed framework Dev and I encourage others to do so too.
Click to expand...
Click to collapse
What about the hard work of developers who've been toiling away hard on the Lollipop ROMs bringing you various mods without xposed?
Kryten2k35 said:
What about the hard work of developers who've been toiling away hard on the Lollipop ROMs bringing you various mods without xposed?
Click to expand...
Click to collapse
I'm modifying my own system files for lollipop. As an IT engineer I know my way around how Linux/Unix systems work, and have a bit of programming language background.
I was solely referring that we should support what we are using (as I used xposed and decided to support it into further development), but I'm not using any other "mods" from other developers.
Unlike the vast majority of Android users, I buy all my software.
But I believe that the users should support the work of their devs, or if you're developing something, I hope your users will support whatever it is you're working on (I've seen you have clearly taken offense)
No offense taken