Hi alltogether.
Im not a developer or something, but i am wondering whether it is possible to port/ flash the Nougat Developer Preview 5 to a Moto X Pure?
If yes, why didnt somebody try to build a rom for us already?
If no, what are the restrictions?
It's not fully release yet, why would a developer put all their efforts on a preview when the full release is not even 2 months away
well, i know, but i always thought during the time period from the first developer preview why no one tried to port ist, or didnt even mention it. Its because i cannot imagine how much effort it takes to do this I mean if it wasnt much, why shouldnt it be made, just to give some Pure owners the possibility to try Nougat as well?
It's not really feasible. Until Google releases the actual source code for Nougat, preview or otherwise, trying to decompile and rebuild compiled Roms for completely different devices is not something likely to happen for any phone.
Sent from my XT1575 using Tapatalk
Silarn said:
It's not really feasible. Until Google releases the actual source code for Nougat, preview or otherwise, trying to decompile and rebuild compiled Roms for completely different devices is not something likely to happen for any phone.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Thats an answer i was looking for..this explains a lot to me..thx!
Related
I'm curious, now that the developer preview ROM is out for the Nexus 5:
Will it be possible to adapt the Nexus 5 image to work on the Moto G?
Does someone already have a plan to do it?
There is no point in using Android L until it's release, it is just a developer preview, to allow devs to make the apps compatible faster.
If you are desperate to try it, you could always use the Android sdk tools and try it in adt.
Sent from my XT1032 using Tapatalk
A port would be awesome though! Just tried Android L on the nexus 7 and it's really nice! Feels much better
vlt96 said:
There is no point in using Android L until it's release, it is just a developer preview, to allow devs to make the apps compatible faster.
If you are desperate to try it, you could always use the Android sdk tools and try it in adt.
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
I know it's only a preview, but it would be nice to try it, and maybe it works better that one would think.
I guess my main question is if we have to wait until Google releases the source code, or if there's any possibility for ROM-devs to do something with the Nexus 5 ROM for other devices.
Why would devs waste time on such a useless endeavour? Your question really puzzles me…
Google isn't releasing the source for 'L' until the public release so the ROM from a Nexus 5 is likely to be of much help. Plus, the developer preview is pretty unfinished and buggy so I don't know the point.
There already is a thread about this here: http://forum.xda-developers.com/moto-g/general/discussion-google-announces-android-l-t2794615
Thread closed.
Just wanted to know why this variants is not getting Roms/love from Dev's be it sense based or GPE Rom come to think of it M7 and M7C are pretty identical in hardware SOC,we used to have Sense based Rom from maximus HD but that has been abandoned we even have a great kernel thanks to @bgcngm we also have Sense 7 port thanks to @artur0588.
I'll be willing to be a tester if anyone would be kind enough to venture into it.thanks to all who have made contributions to M7C development thus far:good:
Although I can't promise it will be officially supported by CM because I obviously can't maintain a device without having it, I'll give it a look today to see if I can come up with an alpha release. Please remind again, which variant do you have, is it 802w?
bgcngm said:
Although I can't promise it will be officially supported by CM because I obviously can't maintain a device without having it, I'll give it a look today to see if I can come up with an alpha release. Please remind again, which variant do you have, is it 802w?
Click to expand...
Click to collapse
802w
Sent from my HTC One dual sim using Tapatalk
Nahhhh, forget it. There are huge differences in source code and I have only looked into kernel code. Merging source for dug, dwg and dtu is not an easy task, even more without having the device for testing.
bgcngm said:
Nahhhh, forget it. There are huge differences in source code and I have only looked into kernel code. Merging source for dug, dwg and dtu is not an easy task, even more without having the device for testing.
Click to expand...
Click to collapse
Can't you look into dug first then later the rest? as for testing just tell me what to do anyways thanks for your help
Sent from my HTC One dual sim using Tapatalk
Of course, I looked first into M7CDUG. Adding the source code over actual CM's kernel is a hell. Nothing compared to M8DUG, where one just need to pull in the additional DTSI files.
bgcngm said:
Of course, I looked first into M7CDUG. Adding the source code over actual CM's kernel is a hell. Nothing compared to M8DUG, where one just need to pull in the additional DTSI files.
Click to expand...
Click to collapse
So basically you mean it's difficult for M7CDUG and possible for M8DUG?,but i haven't seen any aosp Rom on M8DUG or even GPE
Sent from my HTC One dual sim using Tapatalk
Beforehand thanks to all developers, I have never set to investigate how to develop on android or anything like that, but I like to have my smartphone updated and with roms.
I would like to propose the beta channel, create a rom without modifications as is the pixels, with the most current version of Android that is the "O"
I know it's beta, but the developers here are the best, literal a bug comes out and fix it that day
Thanks for reading, I would really like a rom with Android O and pure
Good luck with that
FerVillanuevas said:
Beforehand thanks to all developers, I have never set to investigate how to develop on android or anything like that, but I like to have my smartphone updated and with roms.Thanks for reading, I would really like a rom with Android O and pure
Click to expand...
Click to collapse
Hope is a fortune
FerVillanuevas said:
Beforehand thanks to all developers, I have never set to investigate how to develop on android or anything like that, but I like to have my smartphone updated and with roms.
I would like to propose the beta channel, create a rom without modifications as is the pixels, with the most current version of Android that is the "O"
I know it's beta, but the developers here are the best, literal a bug comes out and fix it that day
Thanks for reading, I would really like a rom with Android O and pure
Click to expand...
Click to collapse
Someday. You friend someday... When South Korea and real Korea are united
I do not understand why it would be so crazy, I've seen roms in weeks, I do not know, I guess I'm not the only one who wants something like this
I think the reason is that here on XDA, you don't ask things like that but you try to learn to do it yourself. Once you do the effort to make it happen, even if you're not an expert, then you will get kind replies and some people will certainly help. If you just say "hey I would like that to happen" and sit back and wait for other people do the work, than you're not taken seriously.
Try and make a new thread, where you ask "what would I need to learn and do to make an android O beta channel", you'll see that you will get positive feedback. (If you also show that you actually follow the advice and do effort)
I do not have the slightest idea how to do, compile, edit etc a rom, look for tools but it only comes out like changing the icons, of course I would like to learn and I would like to do it for myself, I know I have a lot to contribute I do not know how to do it, I have looked for tutorials and nothing, I do not even know why there are errors in the camera or something like that if it were supposed to be compatible with all types of Windows or linux, change system but everything works the same, and in android I do not know and I do not understand
Maybe because of the translation they took it wrong or not, I assumed that this was a community where they could plumb projects and that the people start to participate, maybe it's because I come from cominities where everyone contribute say that it is interesting some begin to work and Begins to create something of an idea, but here is not so I guess
FerVillanuevas said:
I do not understand why it would be so crazy, I've seen roms in weeks, I do not know, I guess I'm not the only one who wants something like this
Click to expand...
Click to collapse
i would want it too but its developer software already got bugs then on top of bugs the moto g5 would have it would make the rom unstable and no suitable as a daily driver also the source code for android O hasn't been released
wait for atleast end of 2017
Sent from my Moto G (5) Plus using Tapatalk
sudhir7777 said:
wait for atleast end of 2017
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
Or 2018! It's Lenovo now, not Motorola anymore.
Send from my Motorola Moto G5 Plus (XT1685) using Tapatalk
And if that's impossible , can someone kindly explain why? Thanks
Absolutely no.
HatRiGt said:
Absolutely no.
Click to expand...
Click to collapse
Yeah, I searched in forum and everyone says no, I'm just curious about the technical reason
Technically it's not impossible but the real problem is that the OnePlus 5 has never had a Marshmallow so there's no kernel source or device tree for Marshmallow on the 1+5. Developers use these things because it contains all the lines of codes needed to tweak and compile their own custom ROMs, having the original code is very important because it has all the necessary APIs needed to interact with every piece of hardware on the device. Since the 1+5 never had Marshmallow built for it that means in order for you to have a seamless experience like the one you expect from stable software, you have to build it from scratch or you could borrow the source from a similar hardware, like 1+3t. Problem is if you go that route, there are many hardware differences so you still have to spend a lot of time rewriting code, debugging, testing, and repeating all that over and over again and even then you probably won't get a couple of things working properly.
In simple terms, it would take an awful lot of time to port a software version that for many of us is already outdated for a device that never had that version and that would probably not run as smoothly as Nougat based Roms.
HueleSnaiL said:
Technically it's not impossible but the real problem is that the OnePlus 5 has never had a Marshmallow so there's no kernel source or device tree for Marshmallow on the 1+5. Developers use these things because it contains all the lines of codes needed to tweak and compile their own custom ROMs, having the original code is very important because it has all the necessary APIs needed to interact with every piece of hardware on the device. Since the 1+5 never had Marshmallow built for it that means in order for you to have a seamless experience like the one you expect from stable software, you have to build it from scratch or you could borrow the source from a similar hardware, like 1+3t. Problem is if you go that route, there are many hardware differences so you still have to spend a lot of time rewriting code, debugging, testing, and repeating all that over and over again and even then you probably won't get a couple of things working properly.
In simple terms, it would take an awful lot of time to port a software version that for many of us is already outdated for a device that never had that version and that would probably not run as smoothly as Nougat based Roms.
Click to expand...
Click to collapse
Get it, thanks very much my friendSo seems I have to wait for the Xposed for Noughat.Well, be patient
HueleSnaiL said:
Technically it's not impossible but the real problem is that the OnePlus 5 has never had a Marshmallow so there's no kernel source or device tree for Marshmallow on the 1+5. Developers use these things because it contains all the lines of codes needed to tweak and compile their own custom ROMs, having the original code is very important because it has all the necessary APIs needed to interact with every piece of hardware on the device. Since the 1+5 never had Marshmallow built for it that means in order for you to have a seamless experience like the one you expect from stable software, you have to build it from scratch or you could borrow the source from a similar hardware, like 1+3t. Problem is if you go that route, there are many hardware differences so you still have to spend a lot of time rewriting code, debugging, testing, and repeating all that over and over again and even then you probably won't get a couple of things working properly.
In simple terms, it would take an awful lot of time to port a software version that for many of us is already outdated for a device that never had that version and that would probably not run as smoothly as Nougat based Roms.
Click to expand...
Click to collapse
Well said. Thanks fur the explanation. I don't even own an OP5 but was considering it..... Might have to give up Xposed finally
Ramaness said:
Get it, thanks very much my friendSo seems I have to wait for the Xposed for Noughat.Well, be patient
Click to expand...
Click to collapse
Unfortunately I don't think Xposed will ever make it to Nougat, and as for android O, I wouldn't bet on it being released anytime soon after O's official release.
The closest thing to Xposed modules that work on Nougat are the Magisk modules, Magisk is a type of systemless root that has support for modules that work similarly to Xposed. I suggest you read up on it and se if it is something that can work you.
lmao no not really. Nobody is going to make anyone a KitKat ROM.
But holy crap, I forgot just how much I *LOVE* and *MISS* KitKat.
That was the last great Android platform for all-out customisation.
It's been all downhill since then.
Google has said "FU" to customisation in support of higher security and a whole lot of other stuff we don't need. Or uh,, that I don't need.
You sure as heck won't catch me banking on a freaking cellphone even if I were running stock unrooted.
I'm setting up an Odroid XU4 (think Raspbery Pi, but more bad-ass).
And its stock ROM is a currently developed KitKat 4.4.4.
And I'm having a bunch of fun installing all the COOL old apps I used to use.
I've already installed like 25 Xposed modules. Many of which can't be used on Lollipop or newer, let alone Nougat.
SOoooooo much customisation can be done to KitKat.
And even a default black theme. How cool was that. :good:
Theoretically speaking, would it be possible to build a KitKat ROM for the Pixel XL? Or any device for which the oldest source code available is newer that 4.4.4?
I would never actually install KitKit on my Pixel XL, but I'd be interested to know if there is a process for this sort of thing.
I'm not a dev but what little I've dabbled around with ROM's tells me that your source code needs to match the OS version you're trying to port (or at least be similar).
I'm sure someone may come along and tell me I'm wrong though.
CZ Eddie said:
I'm not a dev but what little I've dabbled around with ROM's tells me that your source code needs to match the OS version you're trying to port (or at least be similar).
I'm sure someone may come along and tell me I'm wrong though.
Click to expand...
Click to collapse
I'm here to tell you that you are wrong. XD - In all seriousness, you could with enough time and backporting probably make a 4.4 ROM for the Pixel using the drivers from whatever it came with ?7.0?. It wouldn't be easy and I can't say I have the skills and I don't have the time or willpower, but that's essentially what they did for some of the OG android devices to get them running on newer versions than what was released. The Motorola CLIQ comes to mind, they ported 2.1 on to the 1.6 drivers.
I'd give it a run, if some genius made one.
Sent from my Pixel XL using Tapatalk
Definitely possible, but nobody with the skills has time for that. Lol