Related
1- why can't I run stock Google android on my phone ala Nexus one- and update as a nexus one would . A link as i am not afraid to read.
2- what happened to the guy who's video I saw that was close to running stock android on his vibrant.
chkn said:
1- why can't I run stock Google android on my phone ala Nexus one- and update as a nexus one would . A link as i am not afraid to read.
2- what happened to the guy who's video I saw that was close to running stock android on his vibrant.
Click to expand...
Click to collapse
You need drivers.
The CM6 project is dedicated to getting relatively stock Android running on the Vibrant.
chkn said:
1- why can't I run stock Google android on my phone ala Nexus one- and update as a nexus one would . A link as i am not afraid to read.
2- what happened to the guy who's video I saw that was close to running stock android on his vibrant.
Click to expand...
Click to collapse
1). As reuthermonkey stated, it's down to hardware drivers. Even though AndroidOS itself is open with source code available, this is not always the case with the drivers the OS needs to access functions on a given phone. Most of the drivers for any device (phone or otherwise) are proprietary. Samsung, HTC, Motorola, Huawei, LG, Sony...these companies have to PAY for drivers from chipset/soc manufacturers to integrate them into their devices and as such the code for those drivers isn't necessarily freely available. To gain access to these proprietary drivers is a tedious process of reverse engineering.
2). The process of getting most phones "close to running stock android" is a careful process of ripping apart a given phone's OS and cobbling together 3rd party or AOSP project tools/apps to approach being a "vanilla android" feeling experience. Many of these "custom roms" are great, but it can equally be said that most of them are personal projects made by people who love to tweak things to their liking, and not necessarily made to be great for everyone. And most of these stay in a perpetual state of beta-ness. Cyanogenmod CM6 is really the only well developed project dedicated to truly bringing the vanilla android experience to phones at the moment, and then only to phones that CM devs actually have in hand as it's an entirely volunteer project. Be grateful our phone is soon to be blessed with CM6.1.
chkn said:
1- why can't I run stock Google android on my phone ala Nexus one- and update as a nexus one would . A link as i am not afraid to read.
2- what happened to the guy who's video I saw that was close to running stock android on his vibrant.
Click to expand...
Click to collapse
Basically what would need to happen is someone take the source from Google. With that source you need to find a way to basically make all of your drivers (Samsung's Galaxy S Vibrant drivers) work with the android platform. It's not an easy process of adapting drivers to something else, it sounds like oh yeah include the drivers and you'll be good right? Unfortunately it's not as easy as just plug and play.
On the second note, i'm pretty sure what your thinking of is Eugene's Vanilla Rom he's been putting together.
http://forum.xda-developers.com/showthread.php?t=757000&highlight=Vanilla
It looks like he's got some good progress and there is a download going for it. I don't think it's something he's focusing on either. I think the main reason why is with Froyo coming sooner or later there's really no reason to invest time in a 2.1 vanilla rom with as much work that goes into building it from source.
Hope this answers your questions. BTW, as a reference, there is a Q&A forum which would be a better place to put this Question.
Eugene's AOSP 2.1 Port is dead. And rightly so, no need wasting time getting 2.1 AOSP running on the device.
On a side note however, another developer has jumped in to help CM 6.1 reach Vibrant. And it might take a long long time before G2 has any kind of custom rom support.
So, let me start off by saying that I have searched, read and spent time trying to understand this... but still don't. Which answers why I'm posting this question.
First, what exactly is the reason that an AOSP rom is being developed and a Vanilla Froyo ROM is being developed?
Is the AOSP rom the important one here? Does the working AOSP rom with working kernel mean that we would have 2.2, 2.3.... and so on supported regardless of Samsung?
I understand that Samsung has not supported tremendously up to this point, I understand 2.2 has not been released for the CDMA version yet, and I understand the code they have released is "crappy." When I hear everyone talk about the great work the devs are doing, are they referring to mainly working on the AOSP? If this rom is built, will we be able to just keep developing it for the new versions of Android?
Sorta like in Back to the future when they break off the real timeline and go into the alternate 1985?
Samsungs Android - 2.1, 2.2.... EOL
Dev's Android - 2.1, AOSP, 2.2, 2.3?
Is this how it works? Basically just trying to understand what needs to happen for the Fascinate to get to at least 2.3... not WHEN or even IF it'll get to 2.3.
Thanks
AOSP means Android Open Source Platform.
It's a version of Android built entirely from sources provided by Google. It's completely Vanilla and comes with zero customer or manufacturer customizations. It's easily root-able, and able to be customized completely by the user if desired.
AOSP ROMs are desirable because they tend to be a bit faster and lighter due to their lack of crapification.
AOSP builds are only distributed in their complete and compiled form by Google for their developer handsets (Currently the Nexus One and Nexus S), and not by any carrier or manufacturer.
Okay, I appreciate that definition... I think I've gotten what AOSP is exactly... but I guess my question is does AOSP have any involvement in a future for this phone if Samsung decides to close its doors. Is a working AOSP, radio, kernel... whatever basically devs developing a future of this phone parallel to whatever Samsung does for it?
Like, I see from other threads that the ROM for Froyo and Gingerbread isn't necessarily the problem, its the radio and the RIL? If that is the case, what needs to happen for everything to figured out and for us to have a bright future for the Fascinate? Samsung has to release code for the RIL and radio? Are we SOL without Samsung helping here or will the devs definitely figure something out to get 2.2, 2.3... and so on for the Fascinate?
Bwangster12 said:
Okay, I appreciate that definition... I think I've gotten what AOSP is exactly... but I guess my question is does AOSP have any involvement in a future for this phone if Samsung decides to close its doors. Is a working AOSP, radio, kernel... whatever basically devs developing a future of this phone parallel to whatever Samsung does for it?
Like, I see from other threads that the ROM for Froyo and Gingerbread isn't necessarily the problem, its the radio and the RIL? If that is the case, what needs to happen for everything to figured out and for us to have a bright future for the Fascinate? Samsung has to release code for the RIL and radio? Are we SOL without Samsung helping here or will the devs definitely figure something out to get 2.2, 2.3... and so on for the Fascinate?
Click to expand...
Click to collapse
It's kinda like building an office park, or strip mall or something. You toss up the basic vanilla buildings, and when it's finally done, companies move in and tweak it how they deem fit.
With a working ASOP build, it'll remove some of the shackles of Samsungs bs code.
So... the AOSP build IS THE KEY here? I understand it isn't working yet, but if the devs get AOSP working, does that mean we will get a 2.2, 2.3 and so on regardless of what is released by Samsung?
I'm just trying to figure out what is happening to keep the G1, Droid, Droid 2... supported by ROMs like Cyanogenmod and others, that hasn't happened yet for the Samsung Fascinate.
I'd like to get the Fascinate, but am sorta waiting because I don't wanna be stuck with a phone for the next 2 years that will max out at MAYBE 2.2 if we are lucky.
I don't know where to start with your confusion.
Samsung has not given 2.2 to us. This means that we do not have froyo...
The RIL is an interface layer between the os and the radio. I'm not too sure about it, but anyways...
The developers are working around the fact that samsung has not given further tools that they need to get froyo ported over. Currently they are working on a 1.6 RIL to get froyo working. On another note, vanilla aosp is a good thing because it gives developers more freedom to customize the roms. It also allows for them to be able to port over other roms.
I really don't understand your confusion. If you want a better explanation , I recommend getting on irc.
If I were you, I'd wait. Next gen phones are coming from vzw in the next few months which will essentially blow the existing tech soon.
Bwangster12 said:
So... the AOSP build IS THE KEY here? I understand it isn't working yet, but if the devs get AOSP working, does that mean we will get a 2.2, 2.3 and so on regardless of what is released by Samsung?
I'm just trying to figure out what is happening to keep the G1, Droid, Droid 2... supported by ROMs like Cyanogenmod and others, that hasn't happened yet for the Samsung Fascinate.
I'd like to get the Fascinate, but am sorta waiting because I don't wanna be stuck with a phone for the next 2 years that will max out at MAYBE 2.2 if we are lucky.
Click to expand...
Click to collapse
Basically, that's the hope at least. If there are changes in say, 2.4 that require something that couldn't be hacked around with ASOP, we'll be stuck waiting for Samsung. But with a working ASOP, the groundwork is laid for updates to be ported over a bit more quickly by the devs.
Regardless of the future of this device, the Fascinate is one of the better Android handsets on the market. The screen is brilliant, it's the perfect size, and it's damn fast. The only thing that drags it down is the factory setup (although I personally think it's idiotic to ding the phone because of the inclusion of Bing like some people/reviewers have.)
I'm trying to understand what is going on instead of being one of the millions to ask about updates for this phone. I see phones like the droid series and read that they basically are being supported forever and then I see the Samsung Fascinate, and while I understand that the code is crappy/not released to community... I'm trying to figure out what needs to happen for it to be a supported device like the droids have been.
Bottom line, nothing at all is going to happen unless Samsung releases more than just a 2.2 update? If I see 2.2 drop like tomorrow, does that mean anything for a future, or is it just 2.2 update and we will just get devs releasing their versions of 2.2 roms?
RacerXFD said:
I really don't understand your confusion. If you want a better explanation , I recommend getting on irc.
Click to expand...
Click to collapse
I read his questions as:
"Will a working ASOP build mean better developer support/faster developer released updates?"
I did skim them though.
RacerXFD said:
If I were you, I'd wait. Next gen phones are coming from vzw in the next few months which will essentially blow the existing tech soon.
Click to expand...
Click to collapse
This is a good point. There's an LTE Samsung handset coming out soon, so it might be worth holding out for a little.
Although the Fascinate is no slouch.
Pretty much what I am asking. Like of everything that could possibly happen, Samsung releasing 2.2, AOSP being finished, blah blah what is the key that a consumer should look for to say...
"Well, now the Fascinate has no negatives to it and I have no fear that in a year, we won't still be stuck on 2.1 or 2.2 because Samsung screwed us."
Doesn't necessarily seem like Samsung needs to do MUCH to future this phones life and turn over the keys to the devs (like HTC seemingly has done), but I'm trying to understand what that thing is they need to do. Release a newer kernel, RIL, 2.2 ROM, some code that magically allows devs to port over future roms eternally...
I don't think I care if the phone has LTE capability. I won't get LTE and a regular 3G phone is beyond enough for me. LTE is zero impact for me.
Bwangster12 said:
Pretty much what I am asking. Like of everything that could possibly happen, Samsung releasing 2.2, AOSP being finished, blah blah what is the key that a consumer should look for to say...
"Well, now the Fascinate has no negatives to it and I have no fear that in a year, we won't still be stuck on 2.1 or 2.2 because Samsung screwed us."
Doesn't necessarily seem like Samsung needs to do MUCH to future this phones life and turn over the keys to the devs, but I'm trying to understand what that thing is they need to do. Release a newer kernel, RIL, 2.2 ROM, some code that magically allows devs to port over future roms eternally...
I don't think I care if the phone has LTE capability. I won't get LTE and a regular 3G phone is beyond enough for me. LTE is zero impact for me.
Click to expand...
Click to collapse
What does SAMSUNG need to do? Release their source code, and not just incomplete parts of it.
Will that happen? I doubt it, but it might. Clearly the companies ears are perking up with all the yelling by the consumers.
What can we do in the meantime? Support the devs and wait for them to crank out a working ASOP build and Froyo.
Yes, would be nice to have a fully working AOSP build, and then Froyo... but they are seperate from each other right?
AOSP build is being done for 2.1? It can't just be magically updated to 2.2 can it? Does Froyo have to be officially released for them to update it to AOSP 2.2?
Basically... AOSP will only be updated to whatever version Samsung has released?
Bwangster12 said:
Yes, would be nice to have a fully working AOSP build, and then Froyo... but they are seperate from each other right?
Click to expand...
Click to collapse
No. Android Open Source Project means "Android" in general. It can be 2.1, 1.6, 2.3, whatever. The devs elected to start with 2.1.
AOSP build is being done for 2.1? It can't just be magically updated to 2.2 can it? Does Froyo have to be officially released for them to update it to AOSP 2.2?
Click to expand...
Click to collapse
If you've followed anything in the dev folders, clearly not. JT's "Vanilla" Froyo looks like an AOSP build.
Basically... AOSP will only be updated to whatever version Samsung has released?
Click to expand...
Click to collapse
No. At least not our version.
Bwangster12 said:
Yes, would be nice to have a fully working AOSP build, and then Froyo... but they are seperate from each other right?
Click to expand...
Click to collapse
It's hard to answer your question because AOSP and Froyo refer to two completely different things, which can be the same or separate.
AOSP is basically Android, built from clean, unmodified source code directly from Google, without any changes by carriers or manufacturer.
Froyo is simply the 2.2 version of Android.
So, you can have Froyo that's modified by a carrier and/or manufacturer. This wouldn't be AOSP. And you can have Froyo, built directly from Google code. This would be AOSP. You can also have Eclair (Android 2.1), or any other version of Android that's AOSP or not AOSP depending on whether it was built directly from Google code, or modified by a carrier or manufacturer.
AOSP doesn't refer to a single, particular version of Android, but the state of the code that was used to compile whatever version you want to talk about.
Bwangster12 said:
AOSP build is being done for 2.1? It can't just be magically updated to 2.2 can it? Does Froyo have to be officially released for them to update it to AOSP 2.2?
Click to expand...
Click to collapse
A lot of the issue surrounds the kernel. When Google releases a new version of Android, it runs on a particular version of the kernel, which supports it's particular features. Manufacturers have to modify the kernel to support their particular hardware. So, since Samsung has only released source code for the kernel for Android 2.1, we're stuck on 2.1.
The versions of 2.2 from Kaos and JT are running on the Android 2.1 kernel that's been hacked to enable 2.2 to boot and run correctly. It works, but it's far, far from ideal. It doubles (if not more) the amount of work necessary to get 2.2 running, which is the reason for the rather slow pace of development.
So for your question, once Samsung releases 2.2 (the system and kernel), it'll be much easier to get an AOSP build of Android running, since the devs will only need to worry about the system instead of hacking together a kernel and RIL (radio interface layer) as well.
At least this is my understanding of the situation. I'm sure people with more knowledge and experience can correct me where I'm wrong, but I think this is the basic gist of it.
ChrisDDD said:
It's hard to answer your question because AOSP and Froyo refer to two completely different things, which can be the same or separate.
AOSP is basically Android, built from clean, unmodified source code directly from Google, without any changes by carriers or manufacturer.
Froyo is simply the 2.2 version of Android.
So, you can have Froyo that's modified by a carrier and/or manufacturer. This wouldn't be AOSP. And you can have Froyo, built directly from Google code. This would be AOSP. You can also have Eclair (Android 2.1), or any other version of Android that's AOSP or not AOSP depending on whether it was built directly from Google code, or modified by a carrier or manufacturer.
AOSP doesn't refer to a single, particular version of Android, but the state of the code that was used to compile whatever version you want to talk about.
A lot of the issue surrounds the kernel. When Google releases a new version of Android, it runs on a particular version of the kernel, which supports it's particular features. Manufacturers have to modify the kernel to support their particular hardware. So, since Samsung has only released source code for the kernel for Android 2.1, we're stuck on 2.1.
The versions of 2.2 from Kaos and JT are running on the Android 2.1 kernel that's been hacked to enable 2.2 to boot and run correctly. It works, but it's far, far from ideal. It doubles (if not more) the amount of work necessary to get 2.2 running, which is the reason for the rather slow pace of development.
So for your question, once Samsung releases 2.2 (the system and kernel), it'll be much easier to get an AOSP build of Android running, since the devs will only need to worry about the system instead of hacking together a kernel and RIL (radio interface layer) as well.
At least this is my understanding of the situation. I'm sure people with more knowledge and experience can correct me where I'm wrong, but I think this is the basic gist of it.
Click to expand...
Click to collapse
Okay, thank you for this answer... this makes sense to me.
So, have HTC and Motorola released newer kernels for the devs of roms like Cyanogemod to update their ROMs, despite HTC and Motorola not actually releasing newer versions? I mean, how is the G1 updated as far as it has. Did HTC release a 2.2 kernel to allow devs to put 2.2 on it?
That's were I'm start confused as well.
I understand that Samsung has some proprietary kernel level code and drivers.
But, I'm curious what is the difference between Linux kernel versions used for different versions of Android. It doesn't sound like major version change and hence should not change anything dramatically. It should be mostly bug fixes. That's why jt was able to get kernel work.
As in relation to ASOP for SF, I see it like attempt to adapt Samsung code to current android interfaces. Once again, these interfaces should not change dramatically between versions, because these are evolutionary. So, I assume when done it is pretty much paved road up to 3.0 at least. That said some new features might not work at all, because we do not have working initial binaries from Samsung.
By the way mrbirdman has GB in progress.
Alright... so this may sound like I'm oversimplifying it, but I don't mean to.
Why can't the dev community just create a "custom" kernel to work with their versions of 2.2, 2.3 and so on? You say that they are working to hack the 2.1 kernel Samsung has released so it allows 2.2 to run on the Fascinate... but why can't they just make a 2.2 kernel? Is that sorta what Cyanogenmod is doing to get a 2.2 Froyo build to work on a G1?
Based on the amazing things I've seen the dev community do, building ROMs from scratch, I guess I don't understand how the kernel can't be built specifically for each new version... forgetting about what Samsung releases.
Bwangster12 said:
Why can't the dev community just create a "custom" kernel to work with their versions of 2.2, 2.3 and so on?
Click to expand...
Click to collapse
Theoretically they could, it would just be a lot of work. Hardware drivers might not be compatible with the kernel version designed for 2.2 or 2.3. I don't think manufacturers are required to release the code for their drivers, so if a driver wouldn't work, one would need to be written from scratch, and without the detailed knowledge of the hardware itself, that is very difficult.
Hardware support is very integral to the kernel, so a kernel for one phone wouldn't run at all on another. So in addition to the difficulty of putting together a totally independent kernel, it would need to be done separately for each and every phone out there, and how many versions of the Galaxy S alone are there? How many HTC phones, how many Motorola and LG and Sony and so on.
It's just not realistic for people doing this, essentially, in their spare time.
So, what the devs generally do is wait until a carrier releases a version of Android (System, kernel, radio, etc.), and with all the hardware support in place and working, they can focus on building custom or AOSP versions of the system.
It's not that they couldn't build their own kernel, it's just a matter of practicality, audience and the shelf live of the particular phone. As it is, a new generation of phones are already either coming out or on the near horizon... and our phone is what, 4 to 5 months old?
Bwangster12 said:
Based on the amazing things I've seen the dev community do, building ROMs from scratch, I guess I don't understand how the kernel can't be built specifically for each new version... forgetting about what Samsung releases.
Click to expand...
Click to collapse
The misunderstanding is in the complexity of compiling a custom system, and developing a custom kernel. They are hugely different in terms of complexity.
Think of a ROM as taking Windows 3.1 and simply tweaking the components that are installed by default - what accessories are installed, what wallpaper is selected, the color scheme of the windows. Not terribly complicated.
Think of the kernel as having to compile DOS, complete with custom drivers for all the hardware - CPU, graphics, memory, storage, multitouch, sound, radio, modem, WiFi, networking, power management, USB support, file system support, etc. all by hand.
hi everyone,
As you see the topic its about AOKP team which they have a new version of ICS porting method. First they started moding the devices like Nexus-S and Galaxy nexus. After succeding they came up with other new devices and ported ICS base rom to other devices such as HTC, Xoom,Galaxy Tab.Today i talked to Roman the Dev guy from this team about our beloved TF.Unfortunately he said they wont port this rom to TF. I just started this thread to ask this team for porting this rom. I think if they see our requests they might put their efforts to make it work on our devices. Im currently using build 23 of this rom on my Nexus-s.it comes with lots og built in features.
here is the link for the website.Head over it might be interesting for you.
http://aokp.co
Sent from my Nexus S using xda premium
You said yourself they already said no. Respect their decision and leave them alone; if you don't like the decision you can port it yourself.
From their point of view, I can see why they said no. We will--eventually, one day--get an update from Asus themselves, which will satisfy 99% of users. The remaining 1% will get mods based on the Asus stock roms, just like they do now. There's also already a partially completed port underway by somebody else.
Why would they waste their resources on the TF101 when there are plenty of other devices that have no ICS port, and no chance of getting one from their manufacturer, which they could work on?
Actually, the correct guy to ask for a port is this guy @ProTekkFZS . He recently went on a spree porting aokp to many devices. Roman only port to devices that he is currently using which are gal nexus, nexus s and gal tab.
Sent from my Galaxy Nexus using XDA App
if they dont want to port it got to respect that decision but if they would i would be sooooo happy a really great rom would use it
roman recieved a htc sensation from rootzwiki and he hasnt even ported it there yet so i wouldnt hold my breath dude... although it would be epic...
Sent from my Revolver Powered Asus Transformer
there is a plan for cm this is nothing compared to that and then there will be miui
pashinator said:
there is a plan for cm this is nothing compared to that and then there will be miui
Click to expand...
Click to collapse
1, MIUI won't come to tablets until Xiaomi makes a tablet UI version
2, CM is nowhere yet for the TF
3, Currently AOKP provides more control and access to things than CM. It was stated Cyanogen by himself that CM9 will NOT contain the old CMParts style settings, but rather have them in their respective submenus. AOKP goes on the CM7 way, having a separate app what can switch controls on-off. I'm already using it on my phone (ZTE Blade), and it's currently more stable than CM or even an AOSP build.
fonix232 said:
1, MIUI won't come to tablets until Xiaomi makes a tablet UI version
2, CM is nowhere yet for the TF
3, Currently AOKP provides more control and access to things than CM. It was stated Cyanogen by himself that CM9 will NOT contain the old CMParts style settings, but rather have them in their respective submenus. AOKP goes on the CM7 way, having a separate app what can switch controls on-off. I'm already using it on my phone (ZTE Blade), and it's currently more stable than CM or even an AOSP build.
Click to expand...
Click to collapse
1, Miui for tablets could become a reality without Xiaomi since they decided recently to change their code in Open source...so maybe one day
2, not yet, sure, even if CM has already talked about TF cm9 to come
3, here i think it really depends on the phone : with my Nexus S, aokp is pretty stable and smooth, but not as some other aosp (Pete Alfonso's) or CM (fitsnugly's kangs) for example.
Let's first get next Paul's builds, Asus's release then, and CM9 eventually.....at this point we all should be Fulfilled.
kptnk said:
1, Miui for tablets could become a reality without Xiaomi since they decided recently to change their code in Open source...so maybe one day
2, not yet, sure, even if CM has already talked about TF cm9 to come
3, here i think it really depends on the phone : with my Nexus S, aokp is pretty stable and smooth, but not as some other aosp (Pete Alfonso's) or CM (fitsnugly's kangs) for example.
Let's first get next Paul's builds, Asus's release then, and CM9 eventually.....at this point we all should be Fulfilled.
Click to expand...
Click to collapse
1. First of all, they haven't gone totally open source yet. And to include a tablet overlay, that would be a huge work. Not just graphics, but compatibility, screen issues, alignments, and such.
2. There will be a CM9 build, but only after CM9 is stable enough, and Asus released theirs so Bumble-Bee, RaYmAn, Roach, and the others can make a working one. So no CM9 for now
3. Yes it depends on that too, but show me any point of CM9 having more feature than AOKP. AOKP derives directly from CM9 sources, with the additional apps and features, plus fixes. So I consider it more mature.
Paul already published his sources for the TF, so we could easily grab his tree, change some stuff for AOKP, and make a build. I don't have quite the PC for such building processes, it would take days, and my electricity bill is already over the limit - so I can't do it definitely. But if there's someone else willing, everything can be made
fonix232 said:
1. First of all, they haven't gone totally open source yet. And to include a tablet overlay, that would be a huge work. Not just graphics, but compatibility, screen issues, alignments, and such.
2. There will be a CM9 build, but only after CM9 is stable enough, and Asus released theirs so Bumble-Bee, RaYmAn, Roach, and the others can make a working one. So no CM9 for now
3. Yes it depends on that too, but show me any point of CM9 having more feature than AOKP. AOKP derives directly from CM9 sources, with the additional apps and features, plus fixes. So I consider it more mature.
Paul already published his sources for the TF, so we could easily grab his tree, change some stuff for AOKP, and make a build. I don't have quite the PC for such building processes, it would take days, and my electricity bill is already over the limit - so I can't do it definitely. But if there's someone else willing, everything can be made
Click to expand...
Click to collapse
1 & 2, i agree, that's sure.
3, aokp has indeed for now more features than cm9 and kept cm7 idea with nominated menu, which is more than rich of full customization possibilities. My point was in fact on the stability, efficiency and smoothness : there are, for nexus s at least, aosp roms and some cm9 builds which are better than aokp. So not in terms of "quantity" but of a certain idea of quality. Certain idea, because it is of course a question of point of view. That said, i love Roman's work.
I wish i could build on Paul's and Roman's sources for our beloved TF, but even if my electricity bill could eventuelly bear it (for a time), i have neither the pc, nor the knowledge to do so, which is worse .....here's just a very greatful and curious user....
What is the Difference between an AOSP experience ROM and a NO AOSP ROM?
Also what is the difference between the : Android Develoment Forum and the ORIGINAL FORUM?
Hey
AOSP ROMs are Android Open Source Project Roms, so they don't have any of the HTC Sense, Touchwiz, Motoblur bullcrap (IMO) on them and are pretty much a pure google experience e.g similair to the stock firmware on a galaxy nexus/nexus 7 but most are tweaked e.g CM gives you additional mods and things
And for the second question. I think this post explains it better than i can
http://forum.xda-developers.com/showthread.php?t=1219612
dinesh690 said:
Hey
AOSP ROMs are Android Open Source Project Roms, so they don't have any of the HTC Sense, Touchwiz, Motoblur bullcrap (IMO) on them and are pretty much a pure google experience e.g similair to the stock firmware on a galaxy nexus/nexus 7 but most are tweaked e.g CM gives you additional mods and things
And for the second question. I think this post explains it better than i can
http://forum.xda-developers.com/showthread.php?t=1219612
Click to expand...
Click to collapse
Thank you , you amazed me with the difference of the 2 forums, ( that was the best EXPLANATION I have ever encounter):highfive:
I thought that nexus devices are aosp!?
There are no ASUS additions!?
Cetin said:
I thought that nexus devices are aosp!?
There are no ASUS additions!?
Click to expand...
Click to collapse
Asus didn't add anything significant to the Nexus 7. They add a few apps to their transformer series tablets and tweak the UI a little, but it's pretty close to stock as well when comparing to what Samsung and HTC do. I will only buy Asus or Nexus brand in the future because of this.
Tbh im just going for google only phones even if asus is close to vanilla from now on, don't care about how vanilla it is because most popular phones have atleast Cyanagonmod ROMS for that but I just want fast updates, good dev community and easy unlocking unlike s-off and all this other crap which is a pain in the ass
Xentar712 said:
Asus didn't add anything significant to the Nexus 7. They add a few apps to their transformer series tablets and tweak the UI a little, but it's pretty close to stock as well when comparing to what Samsung and HTC do. I will only buy Asus or Nexus brand in the future because of this.
Click to expand...
Click to collapse
That's why I don't understand why we have android development here too? It's all original here.
Cetin said:
That's why I don't understand why we have android development here too? It's all original here.
Click to expand...
Click to collapse
well, there are multiple ways you can do ROMS:
1. "I downloaded source from google.com and just hit compile without any changes whatsoever (aside from whatever was needed to get it working, like drivers etc)."
2. "Long time ago I had downloaded from google.com, but since then i have added MANY MANY of my own cool changes (like `long press volume to skip to next song'), of course I make sure i pull in whatever latest changes google made to their source too"
3. "there were 2 or 3 ROMs from the above 2 that i liked and i combined them"
#1 is `AOSP',
#2 is `NO AOSP', the person making these "drastic changes" can be HTC (in the case of senseui) or just some dude/team of dudes (in the case of CyanogenMod). This is basically `original work', in the sense that, aside from google's source which i obviously must have taken from, a lot of the stuff is my own. CyanogenMod for instance has immense amount of changes, not sure how it works, but just consider that JB for CyanogenMod is not even beta yet, even though google has stable JB obviously. Meaning their changes are so immense that they had to start from scratch and do all the cool changes to the new JB source (or smthg to that effect).
#3 is regular 'non original' roms, since there is very little 'originality' in these roms. CAn be anything from "All im doing is compiling CM10 and putting it up, although im not officially CM" to "I just added some cool stuff from CM to AOSP and compiled it".
--
I'm unsure as to the line between #2 and #3 ofc, it can get a little confusing/fuzzy at times.
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.