Related
For those of you who do not know ART, please refer to this post (credits to OP):good:
Click to expand...
Click to collapse
Since we already have Kitkat and Android L is just around the corner, why don't we discuss ART and its impact on the performance of our phone?
I know this feature is HIGHLY experimental, but given that Kitkat is on its 4th update (4.4.4) already, I'm assuming that at least it will be more stable.
For me, i think the overall time for apps to open slightly became quicker that before and so far no problems on compatibility on apps. Xposed is still working. :good:
Can't wait for L
Hehe yeah ART is awesome.
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
Experts, once the Nexus 6 is rooted, would it be possible to roll it back to a KitKat firmware? I don't think I can live without Xposed, even more so with the gigantic screen of the Nexus.
I doubt anyone will look at this. Nexus 6 never came with kitkat. Unless it's ported rom or AOSP. Just wait and we will see.
Very doubtful... Would need too much work as it never had KitKat and wouldn't be worth the time/effort
This is likely never going to happen since there are no drivers and libs for kit kat for this device it would be a pain and probably be a buggy mess for a long time while it was figured out
We've a lot of devices updated to newer *unsupported* android versions therefore I think a downgrade is also possible but most will prefer L over Xposed+Kitkat anytime.
I don't see it happening.
When all is released and art is deemed final the dev of exposed said he would begin working again on getting exposed working on Lollipop and art ....he has done some work and said he had a build of exposed working on art so it may not be too long just have to have some patience. ..
This is not going to happen, it's wasteful resources to backport kit kat to the nexus 6 when this will take a lot of time to backport it. Xposed will simply need to adapt itself to work on Art in the long run.
Sent from my A0001 using Tapatalk
About that...
http://www.androidheadlines.com/201...d-found-it-running-android-kit-kat-4-4-4.html
In terms of Xposed all I want is system-wide Immersion mode. I want to make FULL use of this 5.96 inch display!!
U better off waiting for xposed to be updated
Gorjira said:
In terms of Xposed all I want is system-wide Immersion mode. I want to make FULL use of this 5.96 inch display!!
Click to expand...
Click to collapse
Can't use just edit the build prop and get rid of the nav buttons?
Gigahawk said:
http://www.androidheadlines.com/201...d-found-it-running-android-kit-kat-4-4-4.html
Click to expand...
Click to collapse
Crazy. Id be so pissed if I got a jacked up phone like that. Not so much if they were readily available in store and I could simply swap it out.
There's probably a better chance of somebody figuring out how to bake dalvik back into L.
Sent from my Nexus 6 using Tapatalk
If someone with one could rip the rom off one but that guy probably didn't know he had something worth it ....just for drivers etc then we could build aosp with dalvik if it was not there, just for exposed ...not to mention easier way to turn off encryption
I too hope Xposed come soons. I'm dying without some of the features I had on my S3!
It'll probably be better to backport dalvik library than downgrading to kitkat.
[ I looked and yeah I kinda posted this in the wrong spot but it's too late to change it so :/ ]
As you may or may not know there is a new version of android coming which is currently called Android O.
In my opinion it feels like they are trying to make android look more like iOS but it's alright..
What is your opinion? If a Android O ROM came out in the future would you get it? If yes, why? And if no, why?
Detailed video: https://www.youtube.com/watch?v=DJ-dOODlQgg
A new OS is always welcome the S1 is still the best for video.
John.
ZimriTech said:
What is your opinion? If a Android O ROM came out in the future would you get it? If yes, why? And if no, why?
Click to expand...
Click to collapse
The way I see it, if you made the decision to run a custom/AOSP ROM, then unless the O happens to be horribly broken in some way, clearly I'd grab the O over N when good ROMs become available. Having said that, I am still on the fence when it comes to custom ROMs. All my devices run their native ROM, but have custom recovery and are often rooted.
With Google looking to further push for a hardware access layer, an OS layer and an App layer we could start seeing bespoke roms a lot quicker, assuming everyone plays ball. I believe O is where this push is really beginning.