Related
Just saw Google has released "Android Wear".
http://www.xda-developers.com/android/google-unveils-android-wear-forums-added/
Hoping someone with more android knowledge than me could take a look and see what we'd need to get this running on the gear.
Developer Preview here:
http://developer.android.com/wear/preview/start.html
oh yeah that would be nice.
odie69 said:
Just saw Google has released "Android Wear".
http://www.xda-developers.com/android/google-unveils-android-wear-forums-added/
Hoping someone with more android knowledge than me could take a look and see what we'd need to get this running on the gear.
Developer Preview here:
http://developer.android.com/wear/preview/start.html
Click to expand...
Click to collapse
I don't see the problem although I am NOT a developer But these Guys here are just plane awesome I have no doubt but if they are offering the SDK already that these guys will take off with it.I just don't know how our screens resolution would be compared to these watches lol that is if they don't make some kind of update that locks are bootloaders on the watch lmao. go Samsung!
I immediately thought the same thing...
"we need that aosp style wear Android ported to the Gear".
That'll be gorgeous.
We already have custom recovery, and a first (and good) custom rom with Null_rom.
If the wear OS is to watches what aosp is to smartphones, that would be pretty easy to do for our skilled devs here
How Samsung can still win the looming smartwatch wars in an Android Wear world..
http://www.techhive.com/article/210...smartwatch-wars-in-an-android-wear-world.html
http://forum.xda-developers.com/showthread.php?t=2977026
Sent from my SM-N900W8 using Tapatalk
The title says it all
Please stay on topic
Keep all android L talk in here to avoid confusion
When? *-*
Velcis Ribeiro said:
When? *-*
Click to expand...
Click to collapse
6 months to 1 year later since the day the Google officially rolled out L version
Velcis Ribeiro said:
When? *-*
Click to expand...
Click to collapse
Probably around 3 months after Google releases it, but they say they changed the release method to this new one to allow faster updates for OEMs.
babygau said:
6 months to 1 year later since the day the Google officially rolled out L version
Click to expand...
Click to collapse
Nice try, troll.
This is my first SamSung phone. If the phone doesn't get supported for at least 3 years, this will be my last SamSung phone for sure
babygau said:
This is my first SamSung phone. If the phone doesn't get supported for at least 3 years, this will be my last SamSung phone for sure
Click to expand...
Click to collapse
You may start thinking about other manufacturers at this time. 2 years max you may get for any mobile in today's market.
http://www.candywarehouse.com/assets/item/regular/nestle-lion-bar-131851-im.jpg Android Lion mabie?
Random news about L version i just read. Posting as there aint much in this thread.
http://www.pcworld.com/article/2391020/google-paves-way-for-64bit-android-l-devices-by-year-end.html
babygau said:
This is my first SamSung phone. If the phone doesn't get supported for at least 3 years, this will be my last SamSung phone for sure
Click to expand...
Click to collapse
Not even Nexus devices get support for such a long time. You can't be for real.
dandroid13 said:
Not even Nexus devices get support for such a long time. You can't be for real.
Click to expand...
Click to collapse
That's what I literally mean :silly:
I question mark the Android lifecycle support policies generally and SamSung specifically. As you're all aware of that if you're Windows Phone or iOS user, you will get the best of it for at least 4 years :good:
In terms of visual design, what is most likely going to change when Samsung puts Touchwiz on it? Do you think most of the card style interface will remain? what about the bright contrasting colour theme?
babygau said:
This is my first SamSung phone. If the phone doesn't get supported for at least 3 years, this will be my last SamSung phone for sure
Click to expand...
Click to collapse
I accidentally hit the thanks button...
You should probably get an iPhone
Sent from my SM-G900T using Tapatalk
Hellscythe said:
In terms of visual design, what is most likely going to change when Samsung puts Touchwiz on it? Do you think most of the card style interface will remain? what about the bright contrasting colour theme?
Click to expand...
Click to collapse
I assume not much since Google is doing its best to limit OEM skinning on android
Guys its too soon to talk about Android L now cuz it is still under development from google and after its release in Fall as they assume, Samsung will then take it and develop it itself to be compatible with touchwiz and all bloat ware then test and then release to public and in phases not all at once.
I assume it will take 6 to 7 months, maybe when S6 arrives will arrive with new android L.
I plan to start development for auto extension of L. However I am curious about supporting it from car makers. Did Google already shared info which maker will make HU compatible with Android L? What kind of interface do they plan to use? I assume BT isn't sufficient for transferring video.
1. Brightness slider in notification bar
2. Battery saver
3. Pop-up notification
4. DND
5. Knox
^^ All these above are already present in many Samsung phone. Stock Android have lot of catching up to do with OEM software in terms of actual usability.
UI tweaks for me is the last thing I am worried about.
Zachinater said:
I assume not much since Google is doing its best to limit OEM skinning on android
Click to expand...
Click to collapse
This is only for Android Wear, TV and Auto.
dandroid13 said:
This is only for Android Wear, TV and Auto.
Click to expand...
Click to collapse
However they are requiring all OEMs to have all the features from android L present in their skins. This might transfer over to the new layering design of android L
Zachinater said:
However they are requiring all OEMs to have all the features from android L present in their skins. This might transfer over to the new layering design of android L
Click to expand...
Click to collapse
Sure but Google's still playing catch up with OEMs' skins. My guess is that we won't see much of a difference in appearance, but we'll have awesome performance on Samsung's top hardware.
"Android L Lets You Keep Your Home Wi-Fi Password Secret"
http://www.tomsguide.com/us/android-l-secure-wifi-sharing,news-19079.html
babygau said:
That's what I literally mean :silly:
I question mark the Android lifecycle support policies generally and SamSung specifically. As you're all aware of that if you're Windows Phone or iOS user, you will get the best of it for at least 4 years :good:
Click to expand...
Click to collapse
Which windows phones have been proven to be updated for such a long time? If I remember correctly none of their phones could go from 7 to 8 lol. Anyway, most people only keep their phones for 2 years, so the requirement of 4 years is a bit mad....
Sent from my SM-G900F using XDA Free mobile app
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
Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.
David B. said:
Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.
Click to expand...
Click to collapse
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.
zelendel said:
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.
Click to expand...
Click to collapse
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.
David B. said:
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.
Click to expand...
Click to collapse
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.
zelendel said:
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.
Click to expand...
Click to collapse
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?
David B. said:
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?
Click to expand...
Click to collapse
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.
zelendel said:
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.
Click to expand...
Click to collapse
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.
David B. said:
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.
Click to expand...
Click to collapse
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.
zelendel said:
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.
Click to expand...
Click to collapse
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.
David B. said:
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.
Click to expand...
Click to collapse
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have
zelendel said:
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have
Click to expand...
Click to collapse
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?
David B. said:
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?
Click to expand...
Click to collapse
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0
zelendel said:
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0
Click to expand...
Click to collapse
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.
David B. said:
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.
Click to expand...
Click to collapse
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things
zelendel said:
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things
Click to expand...
Click to collapse
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.
David B. said:
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.
Click to expand...
Click to collapse
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.
zelendel said:
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.
Click to expand...
Click to collapse
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?
David B. said:
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?
Click to expand...
Click to collapse
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.
zelendel said:
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.
Click to expand...
Click to collapse
Really? What doesn't work with the unlocked bootloader?
David B. said:
Really? What doesn't work with the unlocked bootloader?
Click to expand...
Click to collapse
Things like android pay and saftynet. They are now starting to look for unlocked bootloaders. then you have those that are blocking apps due to root or xposed.
Hey guys,
Long time xposed module user from android 4 through 6. I just got a new (used) Nexus 5X and am considering downgrading to Marshmallow so that I can get xposed back.
Why do people even bother hacking 7.0+ if you can't run xposed? I get that you can use custom firmware with some nice customization, but I feel like 90% of the value of rooting my phone is in xposed. Minminguard, for example, is something I can't live without; adblocking apps is probably the nicest feature I can imagine. Several other custom xposed-only apps as well.
So... what do you all think? Run android 7+ without xposed while waiting for someone kind enough to release xposed module for it, or stay android 6.0 forever to take advantage of the amazing app library within xposed module?
Plenty of advantages. The Google assistant is available without xposed on 7.0 and 7.1 roms. You can now reply to text messages from your notification screen, and delete emails even when you have multiple messages there. Xposed will be great once we get it, but there's plenty of stuff about nougat that makes it worth it.
hooks024 said:
Plenty of advantages. The Google assistant is available without xposed on 7.0 and 7.1 roms. You can now reply to text messages from your notification screen, and delete emails even when you have multiple messages there. Xposed will be great once we get it, but there's plenty of stuff about nougat that makes it worth it.
Click to expand...
Click to collapse
Any other benefits? Im on the same boat as OP, dont see much benefit without xposed atm.
This is why...
image hosting adult
CZ Eddie said:
This is why...
image hosting adult
Click to expand...
Click to collapse
Hello, I´m on the same boat than you, I updated to Nougat just to give it a try but I come back to Marshmallow only for Xposed, all the features from Nougat are not enough for me without Xposed.
Yeah, yeah, wait for Xposed Nougat. Will be realeased in 2195.
People, let's get real! There won't be any Xposed for Nougat. Even if will be released, it will happen so late it would be useless - Android 8 will be the word by then and everyone will ask for Xposed Oreo.
varioventus said:
Yeah, yeah, wait for Xposed Nougat. Will be realeased in 2195.
People, let's get real! There won't be any Xposed for Nougat. Even if will be released, it will happen so late it would be useless - Android 8 will be the word by then and everyone will ask for Xposed Oreo.
Click to expand...
Click to collapse
People have been saying this since 5.0. Xposed for Nougat is basically done already, just needs small fixes.
CZ Eddie said:
This is why...
image hosting adult
Click to expand...
Click to collapse
Wow.. How did you take such a long screenshot? Looks awesome!
Greatness_GH said:
Wow.. How did you take such a long screenshot? Looks awesome!
Click to expand...
Click to collapse
ABotelho23 said:
People have been saying this since 5.0. Xposed for Nougat is basically done already, just needs small fixes.
Click to expand...
Click to collapse
Small fixes every month.
Greatness_GH said:
Wow.. How did you take such a long screenshot? Looks awesome!
Click to expand...
Click to collapse
With S7 is also possible.
Sent from my S7.
---------- Post added at 04:15 PM ---------- Previous post was at 04:10 PM ----------
varioventus said:
Yeah, yeah, wait for Xposed Nougat. Will be realeased in 2195.
People, let's get real! There won't be any Xposed for Nougat. Even if will be released, it will happen so late it would be useless - Android 8 will be the word by then and everyone will ask for Xposed Oreo.
Click to expand...
Click to collapse
There will be an Xposed for Nougat! You think it's easy to make Xposed working on new Android versions why don't you make it yourself then? Even Samsung and other manufacturers need months to update to new Android versions because of the many changes Google added. If it works good Rovo release it if you don't want to wait no problem but then why are you in an Xposed thread? You have no respect to Xposed dev while he does it for free.
Sent from my S7.
robuser007 said:
Small fixes every month.
Click to expand...
Click to collapse
You do understand the source code is out there right? If you're so impatient you should to and make it compatible yourself. This isn't a paid product from a commercial company; you literally have NO right to complain.
FlemishDroid said:
There will be an Xposed for Nougat! You think it's easy to make Xposed working on new Android versions why don't you pake it yourself then? Even Samsung and other manufacturers need months to update to new Android versions because of the many changes Google added. If it works good Rovo release it if you don't want to wait no problem but then why are you in an Xposed thread? You have no respect to Xposed dev while he does it for free.
Click to expand...
Click to collapse
Thank you. Couldn't have agreed more.
There will be an Xposed for Nougat!
Click to expand...
Click to collapse
Not very probably. Google constantly makes changes against Xposed and other hacking tools...
FlemishDroid said:
With S7 is also possible.
Sent from my S7.
---------- Post added at 04:15 PM ---------- Previous post was at 04:10 PM ----------
There will be an Xposed for Nougat! You think it's easy to make Xposed working on new Android versions why don't you make it yourself then? Even Samsung and other manufacturers need months to update to new Android versions because of the many changes Google added. If it works good Rovo release it if you don't want to wait no problem but then why are you in an Xposed thread? You have no respect to Xposed dev while he does it for free.
Sent from my S7.
Click to expand...
Click to collapse
Please, keep your respect lessons for your kids.
I presume you're personal with Robert, you've called him and he told you he's working hard on Xposed Nougat.
Robert have the right to live a life, outside of xposed. That means he have the right to NOT realese any new version of the framework if that would require an amount of work too heavy for one single developer.
If anyone is interested you could use DualBootPatcher to test things out. I'm using DualBootPatcher with stock MIUI based on MM as primary ROM and Lineage 14.1 as data slot ROM, so I can test it out. So far Lineage seems nice but a lack of Xposed is very limiting.
ABotelho23 said:
People have been saying this since 5.0. Xposed for Nougat is basically done already, just needs small fixes.
Click to expand...
Click to collapse
ABotelho23 said:
You do understand the source code is out there right? If you're so impatient you should to and make it compatible yourself. This isn't a paid product from a commercial company; you literally have NO right to complain.
Click to expand...
Click to collapse
I mean google makes (security) changes every month.
The dev's have to face new issues every month this way!
robuser007 said:
Small fixes every month.
Click to expand...
Click to collapse
You know it was hollydays for christmas and new year, right?
Rovo have a life outside Xposed...
Just wait by march tops it's out..
ABotelho23 said:
People have been saying this since 5.0. Xposed for Nougat is basically done already, just needs small fixes.
Click to expand...
Click to collapse
...and you would know this how?
justaway2 said:
...and you would know this how?
Click to expand...
Click to collapse
Devs last update stated hooks were generally working, which is the core function of what Xposed offers to modules. Of course it's partially an assumption, but we also have to consider he's got a life and isn't getting paid for Xposed.