So our phone, is really good, we got cm 11 and cm 12 running, so why don't we have the more special roms? Like flyme os (http://www.flyme.cn/en/) or ubuntu touch? Sailfish os. Most of these, roms have their source released, so for people to pick it up, shouldn't be hard right?
Sailfish os - https://sailfishos.org/develop/hadk/
Ubuntu touch - https://wiki.ubuntu.com/Touch/Building
Flyme os - Well it's builded for the nexus 5, but aren't we able to port it? http://forum.xda-developers.com/google-nexus-5/development/official-flyme-nexus5-kk-4-4-flyme-3-8r-t2875908
And admins, please do not movie this topic, as it won't get as much focus.
bump!
I'd be interested too, what comes to mind is hardware limitations and lack of sources from LG to build on? I have for a couple of months and I still haven't wrapped my head in all the info, but I think we have some limitations as I mentioned above. Someone who's more informed can correct me tho
But aren't we able to port from nexus 5?
MidnightDevil said:
I'd be interested too, what comes to mind is hardware limitations and lack of sources from LG to build on? I have for a couple of months and I still haven't wrapped my head in all the info, but I think we have some limitations as I mentioned above. Someone who's more informed can correct me tho
Click to expand...
Click to collapse
But aren't we able to port from nexus 5?
theonlykamph said:
But aren't we able to port from nexus 5?
Click to expand...
Click to collapse
nexus 5 has a completely different chipset SD800 Nexus 5 Vs SD801 in the LG G3
sofir786 said:
nexus 5 has a completely different chipset SD800 Nexus 5 Vs SD801 in the LG G3
Click to expand...
Click to collapse
So let me get this straight, are we able to port any rom, from a phone as long as the cpu is 810 snapdragon?
theonlykamph said:
So let me get this straight, are we able to port any rom, from a phone as long as the cpu is 810 snapdragon?
Click to expand...
Click to collapse
The issue is that LG does not release the source code for LG G3, whereas the nexus 5 even though it is manufactured by LG, people have the sources for it. So developing all these different roms is not as easy as you think, we have only just got MIUI rom for this device and it is not even official. its not a SD810 btw.
sofir786 said:
The issue is that LG does not release the source code for LG G3, whereas the nexus 5 even though it is manufactured by LG, people have the sources for it. So developing all these different roms is not as easy as you think, we have only just got MIUI rom for this device and it is not even official. its not a SD810 btw.
Click to expand...
Click to collapse
I don't get it, can't we take the roms from another phone using our cpu, and just port it from there?
theonlykamph said:
I don't get it, can't we take the roms from another phone using our cpu, and just port it from there?
Click to expand...
Click to collapse
Lol you are not understanding, its not as simple as you think. Anyway i shall leave you with that.
sofir786 said:
Lol you are not understanding, its not as simple as you think. Anyway i shall leave you with that.
Click to expand...
Click to collapse
Okay, why so mean?
theonlykamph said:
Okay, why so mean?
Click to expand...
Click to collapse
Im not being mean at all, you're failing to understand that its not easy to just port roms, and its not even about porting roms, there has to be enough demand for it, devs need to have the device and not all devs do because they move to other devices, if it was an easy process then there would be loads of other roms, but the majority of roms are now Cyanogen and aosp based because thats the easiest way to as they have the sources for that.
sofir786 said:
Im not being mean at all, you're failing to understand that its not easy to just port roms, and its not even about porting roms, there has to be enough demand for it, devs need to have the device and not all devs do because they move to other devices, if it was an easy process then there would be loads of other roms, but the majority of roms are now Cyanogen and aosp based because thats the easiest way to as they have the sources for that.
Click to expand...
Click to collapse
I never ported a rom, but i saw some guide on porting a rom, where you would take something from the rom you want to port, and some from the base. So i thought it was like that! I'm so sorry, if i said anything mean to you Hope you have a great day :highfive:
Porting isn't the way you would want to work. For the best results you would need all sources and complete documentation of the hardware to be able to build a rom for a device from scratch.
Robin2 said:
Porting isn't the way you would want to work. For the best results you would need all sources and complete documentation of the hardware to be able to build a rom for a device from scratch.
Click to expand...
Click to collapse
But what if i just want to port a simple rom, is it just the cpu that has to be the same?
theonlykamph said:
But what if i just want to port a simple rom, is it just the cpu that has to be the same?
Click to expand...
Click to collapse
There is no "simple" ROM.
You can't just put another phone's ROM to G3, it doesn't work like that.
In PC world, you can install Linuxes and Windows operating systems mostly as you want, but in mobile, things are different.
So if there is no port for the custom ROMs then why not features like Download Booster from the Galaxy S5, this is a possibility maybe it is hard to do but give it a chance, just an idea that I like
TonzaTheChosenOne said:
There is no "simple" ROM.
You can't just put another phone's ROM to G3, it doesn't work like that.
In PC world, you can install Linuxes and Windows operating systems mostly as you want, but in mobile, things are different.
Click to expand...
Click to collapse
What i mean was, would i be able to follow some of those porting guides. Where you take a bit from the lg g3 rom, and then some from the rom you want to port?
theonlykamph said:
What i mean was, would i be able to follow some of those porting guides. Where you take a bit from the lg g3 rom, and then some from the rom you want to port?
Click to expand...
Click to collapse
As Robin2 put it ealier, you would need sources that aren't available.
The Rom porting procedures have been becoming more and more complex with time. Elements like drivers, framework, and so forth are much more complex comparing with Gingerbread. A rom by then used to be 300mb (stock), nowadays we got 1gb roms, much more "little things", overal, it's a lot harder and more complex. You can easily compare, there used to be more ports with gingerbread and ICS than with KK and L. It's a lot of work required to make things happen, even with the same chipset, there's still a lot left to do, specially when we're talking about lack of sources available to make a porting happen and much more complete.
Also, when we're talking about porting a stock rom from HTC to LG, gets worse. manunfactures put a lot of customization (not only GUI) into their firmwares, much more proprietary stuff, much more complexity comparing with a "simple" CM12. It's porting 200mb comparing with 1gb of custom elements. You get the picture. Unfortunatly it's harder than ever and so time consuming and not always with good results. Sources are literally a requirement these days and we don't have them (or don't have them all).
Related
Sorry for noob question (and PLEASE DONT FLAME ME BECAUSE OF THIS) but will roms/kernels for other devices work with the incredible? just wondering\
AND PLEASE, IF YOU THINK I AM A COMPLETE IDIOT FOR POSTING THIS THEN JUST KEEP IT TO YOURSELF
pretty sure they won't or people would be posting about which ones worked well and which ones didnt.
i think a rom has to have a certain amount of customization for the actual device it is going to be loaded on before it will work.
JustinD2473 said:
pretty sure they won't or people would be posting about which ones worked well and which ones didnt.
i think a rom has to have a certain amount of customization for the actual device it is going to be loaded on before it will work.
Click to expand...
Click to collapse
Thank you
How is your froyo port going to work if you didn't know this? Just wondering.
Sent from my ADR6300 using XDA App
grape ape---i did know, just confirmiing
rr12106 said:
will roms/kernels for other devices work with the incredible? just wondering
Click to expand...
Click to collapse
No, if you try to flash a rom or kernel made for another device you can brick your phone.
Captchunk said:
No, if you try to flash a rom or kernel made for another device you can brick your phone.
Click to expand...
Click to collapse
Or get stuck in boot loops
TNS201 said:
Or get stuck in boot loops
Click to expand...
Click to collapse
or explode in a ball of flame...
oh wait... that was mixing gasoline with new roms... and fire...
But yea, should probably avoid flashing roms for other devices without properly porting them.
Never flash a ROM that was meant for another device. You risk not being able to use the phone again.
And if anyone were to flame you for posting this questions they'd take a lot of crap from a lot of people for being a douche.
Don't ever be afraid to post a question
hexto said:
And if anyone were to flame you for posting this questions they'd take a lot of crap from a lot of people for being a douche.
Click to expand...
Click to collapse
Usually this is true, but the OP knew he was risking flame because he's claimed in other threads to be an experienced in building ROMs and knew how to port Froyo to the Incredible.
That doesn't really mesh well with his noob question here.
Reported. This again BELONGS IN GENERAL...man the second post in like 3 hours to be in the wrong section..
elborak said:
Usually this is true, but the OP knew he was risking flame because he's claimed in other threads to be an experienced in building ROMs and knew how to port Froyo to the Incredible.
That doesn't really mesh well with his noob question here.
Click to expand...
Click to collapse
However, he knows, as well as we, that he was over exaggerating on his original claims. We did encourage him to ask questions and learn, can't flame him for making an effort to go down the right path, ask questions, learn, experiment. I'd rather him ask questions, then post falsified claims of froyo builds etc. Much rather.
CaptainTaco said:
We did encourage him to ask questions and learn, can't flame him for making an effort to go down the right path, ask questions, learn, experiment. I'd rather him ask questions, then post falsified claims of froyo builds etc. Much rather.
Click to expand...
Click to collapse
True. Very true.
Thread moved to General.
rr12106 said:
Sorry for noob question (and PLEASE DONT FLAME ME BECAUSE OF THIS) but will roms/kernels for other devices work with the incredible? just wondering\
AND PLEASE, IF YOU THINK I AM A COMPLETE IDIOT FOR POSTING THIS THEN JUST KEEP IT TO YOURSELF
Click to expand...
Click to collapse
I've watched your posts, I know a few folks who are ambitious and think this whole "programming thing" is easy. I'll try to make this simple.
Think of it like this... I compiled an ultra small Kernel of Linux, I only compiled it for a specific computer so I built as much as I could for this specific computer into the kernel, AMD MP, Intel GPU and northbridge, USB 2.0... this way I didn't have to load Modules, it was part of the kernel.
When you install Unix, old school anyway, you are prompted for computer specs so it knows which pre-compiled kernel to select (AMD versus i586 versus i386... etc.) to run the best on your machine. These days it autodetects and makes it easy.
Android is a form of *nix so behaves the same... manufactures compile kernels specific to their devices so that they perform better.
Now, If I used an old Kernel that didn't support USB2 and only supported USB1 then I would be running slow at USB1 or would have to compile without USB at all and load a module that enabled support for USB2...
Android versions are being released with updated kernels for greater support of a wider variety of devices at the kernel level, less modules to load means a faster machine. Some functions still work better with poer saving setups as a module (802.11b/g/n for instance will almost always be a module).
"ROM" which means Read Only Memory are copies of modified kernels from the same device. If I copied the kernel from my machine to another it wouldn't work unless it was identical specs, even one item off and you get kernel dumps, it doesn't know how to talk to your hardware.
Get an idea of what is involved in compiling a kernel here: http://www.linuxforums.org/forum/linux-kernel/55612-mini-howto-compile-linux-kernel-2-6-a.html
I hope this helps you to see that even someone who knows BSD, Linux and Unix... with multiple certifications for Linux (and countless other platforms) and more than 20 years as an engineer... I won't touch making a ROM or trying to modify the bootloader. I wait for the people who know Android's OS, the way it's built, the way it functions... I allow these geniuses to build cool ROMs. I send them donations for their time as some have sent me donations on other forums for my time on other subjects.
It's not as easy as dropping "som 1337 romz" into some folder and presto, "i'z rokn FroYo homz"... it's so much more than that. Someone has to compile the kernel and get the hardware working... it's just easier to wait for the manufacturer to release an update and then find a way to gain root access to do what we want with it.
Additional note:
Check the latest kernel version of Linux here: http://www.kernel.org/
Go into settings and see what version your Doid's Kernel is.
I am going on a limb here but I'm pretty sure there is a correlation.
compnird said:
It's not as easy as dropping "som 1337 romz" into some folder and presto, "i'z rokn FroYo homz"... it's so much more than that.
Click to expand...
Click to collapse
LMAO!! Nice explanation, though.
compnird said:
I've watched your posts, I know a few folks who are ambitious and think this whole "programming thing" is easy. I'll try to make this simple.
Think of it like this... I compiled an ultra small Kernel of Linux, I only compiled it for a specific computer so I built as much as I could for this specific computer into the kernel, AMD MP, Intel GPU and northbridge, USB 2.0... this way I didn't have to load Modules, it was part of the kernel.
When you install Unix, old school anyway, you are prompted for computer specs so it knows which pre-compiled kernel to select (AMD versus i586 versus i386... etc.) to run the best on your machine. These days it autodetects and makes it easy.
Android is a form of *nix so behaves the same... manufactures compile kernels specific to their devices so that they perform better.
Now, If I used an old Kernel that didn't support USB2 and only supported USB1 then I would be running slow at USB1 or would have to compile without USB at all and load a module that enabled support for USB2...
Android versions are being released with updated kernels for greater support of a wider variety of devices at the kernel level, less modules to load means a faster machine. Some functions still work better with poer saving setups as a module (802.11b/g/n for instance will almost always be a module).
"ROM" which means Read Only Memory are copies of modified kernels from the same device. If I copied the kernel from my machine to another it wouldn't work unless it was identical specs, even one item off and you get kernel dumps, it doesn't know how to talk to your hardware.
Get an idea of what is involved in compiling a kernel here: http://www.linuxforums.org/forum/linux-kernel/55612-mini-howto-compile-linux-kernel-2-6-a.html
I hope this helps you to see that even someone who knows BSD, Linux and Unix... with multiple certifications for Linux (and countless other platforms) and more than 20 years as an engineer... I won't touch making a ROM or trying to modify the bootloader. I wait for the people who know Android's OS, the way it's built, the way it functions... I allow these geniuses to build cool ROMs. I send them donations for their time as some have sent me donations on other forums for my time on other subjects.
It's not as easy as dropping "som 1337 romz" into some folder and presto, "i'z rokn FroYo homz"... it's so much more than that. Someone has to compile the kernel and get the hardware working... it's just easier to wait for the manufacturer to release an update and then find a way to gain root access to do what we want with it.
Click to expand...
Click to collapse
Thanks...that helped alot
Sent from my Incredible using XDA App
heres a link to the new meizu m9 rom, could some one start porting this?
http://www.megaupload.com/?d=J3ZZ3AA2
thanks!
I don't think that's very likely to happen. You'll notice that most of the "ported" ROMs here came from the DX; same manufacturer, incredibly similar hardware so there's less fighting and testing to be done. There hasn't been a fully functional and stable AOSP ROM to hit yet (that I've found) much less a successful port from another, very dissimilar handset.
stupidpopmediareference said:
I don't think that's very likely to happen. You'll notice that most of the "ported" ROMs here came from the DX; same manufacturer, incredibly similar hardware so there's less fighting and testing to be done. There hasn't been a fully functional and stable AOSP ROM to hit yet (that I've found) much less a successful port from another, very dissimilar handset.
Click to expand...
Click to collapse
Actually there is a fully stable AOSP rom right now, it was just released.
In terms of porting this rom over. If you give me a link to some screenshots and/or a thread about this rom I can take a look at it and see if I would even want to port it over.
If you just give me a download where I don't know what I am downloading I am not even going to start looking at it.
ljbaumer said:
Actually there is a fully stable AOSP rom right now, it was just released.
Click to expand...
Click to collapse
Where is it?
UrbanBounca said:
Where is it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=891465
Just got released in a mostly stable beta....
heres a link to what it looks like
http://micgadget.com/7635/meizu-m9-is-the-next-big-thing/
i think its sick.
ljbaumer said:
http://forum.xda-developers.com/showthread.php?t=891465
Just got released in a mostly stable beta....
Click to expand...
Click to collapse
It was taken down shortly after due to a recovery issue. I'll probably try it out, but it's going to be hard to get me off my Fission addiction.
ljbaumer said:
Actually there is a fully stable AOSP rom right now, it was just released.
In terms of porting this rom over. If you give me a link to some screenshots and/or a thread about this rom I can take a look at it and see if I would even want to port it over.
If you just give me a download where I don't know what I am downloading I am not even going to start looking at it.
Click to expand...
Click to collapse
Tried it. Clunky, no cellular radio activation, and got into a boot loop at reboot. That's why cvpcs released it in beta. His twitter and site both listed it as buggy.
Once one is released I'll happily eat my words on the AOSP statement but a port at this point is highly unlikely. THank Moto and their damned eFuse chip. I'd LOVE to see more ROMs of any origin but we're a long way away, still, from even having a good AOSP base to build a kitchen from.
Once someone releases a good, stable, everyday, AOSP ROM for the D2 then I think it's likely that we'll see ports from other devices start popping up using said ROMs as the basis for said ports. I'm seriously hoping to see the awesome results from blackdroid, cvpcs, and (if he gets back into it) Matt4542 toward this end.
i can pretty much guarentee you gotta be a super dev to port that rom
Hi,
Many custom ROMs, like CyanogenMod, AOKP, Slim etc. are ROMs made for a wide range of devices, and are therefore not suited perfectly for the Nexus 4. These ROMs are great, of course, but after flashing lots of them I understood I want a ROM that is made specifically for the Nexus 4, as I think they would function better.
For example, I understood there is a thing called Krait optimization and I don't believe any of the ROMs I listed above have it.
I would appreciate if anyone could recommend such a ROM,that is also very customizable (well it is a Nexus...). I'm talking in a CM + AOKP level of customization
From my searching I have found two ROMs, would also appreciate if you could give me opinions about them/compare them:
PACman ROM - http://forum.xda-developers.com/showthread.php?t=2146879
PUB - http://forum.xda-developers.com/showthread.php?t=2146885
Thanks!
you are looking for any aosp(android open source project) based rom, based on pure android. the nexus 4, as well as all other nexus, are aosp devices. rasbean jelly is one of the best, if not the best http://forum.xda-developers.com/showthread.php?t=2028025
aokp is good man...there is no difference
I guess you should understand that all of the Roms you have mentioned are actually built from the Nexus Software. PAC and PUB are basically offshoots of AOSP /AOKP /Cyanogen / Paranoid. The nexus is the test bed, if you will. These ROMS are specifically for our phone, built from our phones ROM, with additions in order to better them. That is as straightforward of an answer as I can get you. You should give ALL of the roms a try and see what fits your taste best, hope this helps.
TheeWolf said:
Hi,
Many custom ROMs, like CyanogenMod, AOKP, Slim etc. are ROMs made for a wide range of devices, and are therefore not suited perfectly for the Nexus 4. These ROMs are great, of course, but after flashing lots of them I understood I want a ROM that is made specifically for the Nexus 4, as I think they would function better.
For example, I understood there is a thing called Krait optimization and I don't believe any of the ROMs I listed above have it.
I would appreciate if anyone could recommend such a ROM,that is also very customizable (well it is a Nexus...). I'm talking in a CM + AOKP level of customization
From my searching I have found two ROMs, would also appreciate if you could give me opinions about them/compare them:
PACman ROM - http://forum.xda-developers.com/showthread.php?t=2146879
PUB - http://forum.xda-developers.com/showthread.php?t=2146885
Thanks!
Click to expand...
Click to collapse
Pac(Vertigo & Blue) has Linaro, Krait, and whatever the A15 patches are called(memspy?).
Thanks everyone.
simms22 said:
you are looking for any aosp(android open source project) based rom, based on pure android. the nexus 4, as well as all other nexus, are aosp devices. rasbean jelly is one of the best, if not the best http://forum.xda-developers.com/showthread.php?t=2028025
Click to expand...
Click to collapse
I have to say that in my opinion, this ROM looks somewhat unprofessional. Its not that I tried it, but I can't understand the basic things from the OP as I should, for example the ROM's features, bugs, screenshots...
[email protected] said:
I guess you should understand that all of the Roms you have mentioned are actually built from the Nexus Software. PAC and PUB are basically offshoots of AOSP /AOKP /Cyanogen / Paranoid. The nexus is the test bed, if you will. These ROMS are specifically for our phone, built from our phones ROM, with additions in order to better them. That is as straightforward of an answer as I can get you. You should give ALL of the roms a try and see what fits your taste best, hope this helps.
Click to expand...
Click to collapse
Yes but I mean that all these ROMs are ports. Cyanogen, for example, exists for almost every device out there. Look at its changelog, you'll see every bit of change incorporated in the ROM's version for every device. What I mean is, they have not done anything (correct me if I'm wrong) to optimize their ROM for the Nexus 4. The ROM exists and functions the same for the S1, the Galaxy Nexus, the Nexus 4 and the HTC Sensation. Again, I may be wrong so correct me if this is the case.
Ace42 said:
Pac(Vertigo & Blue) has Linaro, Krait, and whatever the A15 patches are called(memspy?).
Click to expand...
Click to collapse
Vertigo is the username of the Pac ROM developer as I can see. Is there a version of a developer Blue? I don't really understand.
And what is memspy?
the information is there, screenshots arent needed. but you should stay with cm then, if youre looking for an op and not a rom.
anyways, you do realize that all the nexus 4 roms are built from source? there no need to port roms to any nexus since all the sources are available for every nexus. so to say, all nexus roms are built specifically for the nexus 4, even cm. just because a rom exists on multiple devices, doesnt mean that its ported. most non nexus roms are ported to non nexus devices because they dont have sources available. this doesnt happen to nexus devices.
this is identical with a thread i remember seeing in the gnex forums a while back. anyways, they are all made for the nexus 4. they use drivers that are specific to our phone. if you flash it on another device, it wont work. AOSP is AOSP, that's the point of it. you won't get any extra device specific features if a rom is only built for the nexus 4 vs cyanogenmod which is out for a bunch of phones. the only way that happens is if your phone has a hardware feature another one doesn't ie: NFC.
TheeWolf said:
Hi,
Many custom ROMs, like CyanogenMod, AOKP, Slim etc. are ROMs made for a wide range of devices, and are therefore not suited perfectly for the Nexus 4. These ROMs are great, of course, but after flashing lots of them I understood I want a ROM that is made specifically for the Nexus 4, as I think they would function better.
For example, I understood there is a thing called Krait optimization and I don't believe any of the ROMs I listed above have it.
I would appreciate if anyone could recommend such a ROM,that is also very customizable (well it is a Nexus...). I'm talking in a CM + AOKP level of customization
From my searching I have found two ROMs, would also appreciate if you could give me opinions about them/compare them:
PACman ROM - http://forum.xda-developers.com/showthread.php?t=2146879
PUB - http://forum.xda-developers.com/showthread.php?t=2146885
Thanks!
Click to expand...
Click to collapse
Hi. There are many things to argue here is this post but I will try to help to get you some information to get you on the right track. First off there are two versions if you will of Android, one being "AOSP" or the "Android Open Source Project" and "Google Android". Google Android is what shipped with your device, and has Google owned proprietary in it that is closed sourced, most of the development done in a Nexus forum will come from using AOSP Android. Its the same Android that ships with your device but it does not contain any of Google's proprietary and its completely open-source, however some of the coding needed for a specific devices hardware is not open-source, there's more I can go into on that but I'll stop in short by saying the Nexus4 is probably one of the best devices to be working on platform level coding since all of the binaries needed are properly licensed and most of the hardware coding is open-source. So now that's out of the way. Most of the roms here are forks of AOSP with some being forked from AOKP, CyanogenMod and PA, in order for a developer to build a Nexus4 rom they have to use the provided hardware binaries in combination to the software coding to produce said roms, so ALL of the roms here are built directly for this device. Where confusion come in at is that some of the developers do not have a Nexus4 and build based of the availability of someone being a guinea pig. Also you will have to know whats in you device, such words as "krait optimizations" should not be a hook to get you to try a rom nor should a screen shot since most of the roms look stock besides the few that are themed, ok if they're themed they probably should have a pic, but seriously know your hardware so that you are not just letting a buzzword give you a placebo effect, and remember a roms OP most times doesn't do any justice for the experience you will have from that rom so its best to just try what ever sounds interesting blindly...
TheeWolf said:
Yes but I mean that all these ROMs are ports. Cyanogen, for example, exists for almost every device out there. Look at its changelog, you'll see every bit of change incorporated in the ROM's version for every device. What I mean is, they have not done anything (correct me if I'm wrong) to optimize their ROM for the Nexus 4. The ROM exists and functions the same for the S1, the Galaxy Nexus, the Nexus 4 and the HTC Sensation. Again, I may be wrong so correct me if this is the case.
Click to expand...
Click to collapse
you can't really optimize a rom for a specific device.
they are nearly the same for all devices, and there is no point in optimizing it for specific hardware.
what you can optimize is the kernel, the part that contains the device specific drivers and basically controls the hardware. these are already built and optimized for the nexus 4.
but that doesn't mean that fixes and improvements for other devices have negative effects on the nexus 4.
also, device specific changes in changelogs are mostly kernel related.
TheeWolf said:
Thanks everyone.
I have to say that in my opinion, this ROM looks somewhat unprofessional. Its not that I tried it, but I can't understand the basic things from the OP as I should, for example the ROM's features, bugs, screenshots...
Yes but I mean that all these ROMs are ports. Cyanogen, for example, exists for almost every device out there. Look at its changelog, you'll see every bit of change incorporated in the ROM's version for every device. What I mean is, they have not done anything (correct me if I'm wrong) to optimize their ROM for the Nexus 4. The ROM exists and functions the same for the S1, the Galaxy Nexus, the Nexus 4 and the HTC Sensation. Again, I may be wrong so correct me if this is the case.
Vertigo is the username of the Pac ROM developer as I can see. Is there a version of a developer Blue? I don't really understand.
And what is memspy?
Click to expand...
Click to collapse
Dude, first try and test a rom before you form and vent your opinion based on nothing.
Thank you everyone for the explanations.
gee2012 said:
Dude, first try and test a rom before you form and vent your opinion based on nothing.
Click to expand...
Click to collapse
As I have said, I have already flashed many ROMs, I am not basing my opinion on nothing. I have not opened this thread is not to find out "what is the best ROM" - more than a year of messing with Android and being here in XDA got me understanding there is no such thing, no best ROM. The purpose of this thread is get me some answers, to see if what I am saying is even true.
If Cyanogenmod is the same for every device then riddle me this:
Why is there a different .zip for each device?
You are not going to find a better all around ROM than CM dude. In CM each device has its own tree with many device specific commits and custom changes. You sound very ill-informed asking the questions you are asking; I am surprised you haven't received a lot more flame for it.
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
evodev said:
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
Click to expand...
Click to collapse
It is
XpLoDWilD said:
It is
Click to expand...
Click to collapse
Just a quick question,will it support mediatek devices?
s.sawrav said:
Just a quick question,will it support mediatek devices?
Click to expand...
Click to collapse
Yes.
We have early support for the r819.
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Mayank7795 said:
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Click to expand...
Click to collapse
If you have a working AOSP, it should be available without problems.
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
What about devices that have CM10 only?
lozohcum said:
What about devices that have CM10 only?
Click to expand...
Click to collapse
You need at least an unofficial CM 10.2 / AOSP 4.3.
JoinTheRealms said:
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
Click to expand...
Click to collapse
Building is always worth an attempt...
I used to build my own CM, i'm gonna try to build my own omni too but i'm struggling. I must be doing something wrong with the repo init but I can't seem to find what... I'm gonna update my buildbot first because it's been awhile, and maybe try again tomorrow.
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
That's why its worth scrawling through XDA, going through guides and learning to dev. Nothing wrong with a dev who decides to leave an older version for a newer version. They're doing it for fun and free.
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
As long as there is no hard reason to stop supporting a device and we have someone who is taking care of that device we will try
On the other side - there is constant evolution which sometimes will make it necessary to leave a device "behind" if the effort will become too large
Sent from my Find 5 using xda app-developers app
XpLoDWilD said:
It is
Click to expand...
Click to collapse
Not quite yet... Not until we have roomservice up and running.
(For those that didn't understand what I said - roomservice is the part of CM's repo management system that will automatically sync a device tree and all dependencies. roomservice is HEAVILY dependent on github's APIs, so we couldn't even start work on that particular piece of infrastructure until the project went public.)
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
mattman83 said:
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
Click to expand...
Click to collapse
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
I hope the Acer IconiaTAB A5000 will get supported.
Please, support for RAZR i (x86)
lozohcum said:
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
Click to expand...
Click to collapse
Problem is, every device has its own pitfalls. Some are harder to overcome than others.
For example, the lack of NEON in tegra2 combined with the dependency of newer gapps on NEON really screws tegra2 devices, and there isn't much that can be done about it.
Also, in some cases, the things needed to get a device working aren't in the tree, but are in the frameworks to handle OEM-specific oddities (RIL hacking in opt/telephony, which I admit I'm not too familiar with...) or platform support. Sometimes, old devices get left behind simply because their platform overall is a ***** to support beyond a certain point. (See how MSM8660 devices have been lagging lately, due to Qualcomm pretty much sunsetting that chipset.)
Hi everyone,
I currently found an AOSP 6.0 Marshmallow port for the OnePlus One. I'm a slight new to this but im ready and willing to learn how to do all of this from source. The OnePlus One has the same chipset, cpu, and gpu so it shouldnt be impossible to get this up and running. Anyone interested in contributing to the cause pm me or post on this thread .
Once I am interested in such things , but later I found it is too hard and lack of info :<
free2ing said:
Once I am interested in such things , but later I found it is too hard and lack of info :<
Click to expand...
Click to collapse
Well its all plain experience and trying and trying over and over till it works. Its quite a lot of work its possible just to wait for everything to happen from the cm team but thats really gonna take a while and im sure with enough knowledge and enough hard workers its possible to pull it off. Especially since a device with near the same hardware has marshmallow ported
CurbThePain said:
Well its all plain experience and trying and trying over and over till it works. Its quite a lot of work its possible just to wait for everything to happen from the cm team but thats really gonna take a while and im sure with enough knowledge and enough hard workers its possible to pull it off. Especially since a device with near the same hardware has marshmallow ported
Click to expand...
Click to collapse
I still remember there once be a man wanna port UBUNTU TOUCH to Xiaomi 2 (Mi Two), he choose Nexus 4 with the same 8064 CPU & 9615 chipset, but he still failed and unreged from the forum after 1-year-attemptaion... After all, Im also wondering how marshmallow taste like : ) I support you
free2ing said:
I still remember there once be a man wanna port UBUNTU TOUCH to Xiaomi 2 (Mi Two), he choose Nexus 4 with the same 8064 CPU & 9615 chipset, but he still failed and unreged from the forum after 1-year-attemptaion... After all, Im also wondering how marshmallow taste like : ) I support you
Click to expand...
Click to collapse
Well he was probably trying to kang port it. You need to build it from the source. Port the kernel from source and the same with the source for the rom itself. Its not easy but it can be done. I may give it a go myself even if no one can help or wants to.