Related
Hi guys
After reading around the forum a bit, it seems some people were in similar situations as me, but I still don't have a definite answer.
I have been using a HTC Dream for about a year, and have been an avid fan of cyanogenmod. Although I like the fact that it's rooted and I can install any ROM i liked, I stuck with cyanogen because:
1. It's extremely stable
2. It's well established - they guys got their own site, a central location for all ROM info, all files are found in the same place, they continuously update the ROMs and it pretty much always gets better
The above points for me were reason enough to not even bother with any other ROM. I bought a HTC HD2 a few days back, and I now want to have the phone dual boot Android. What android rom is as good as cyanogen, where "good" is defined by my points above? I know there is a ported cyanogenmod rom, but how well does the port work, will it be updated often as new cyanogenmods get released, etc? Also, I'm no fan of nightly builds, so I don't want a port based on a nightly build - it must either be experimental, release candidate or stable. I also want to stick with the ROM I choose, so it should be continuously updated for the foreseeable future..
First of all, you say you don't want nightly builds, but experimental is okay? Not exactly following, but hey.
There are a couple of CM based roms, if i'm not mistaken 3 are still being maintained:
-JDMS
-HD2ONE
-Mychiprima's (not sure if I'm spelling his name right here) build, it doesn't really have a name (thread contains "htc_linux_wince" at the very beginning)
Mychiprima's builds are based on the autobuild, and are therefor not checked and may contain bugs. JDMS and HD2ONE however are being thoroughly checked & optimized by the respective chefs, so I don't really see a point in not trying them.
Still, if you really want builds based on CM-stable there's always shubcraft and hyperdroid, but both have been discontinued for some weeks already, so you won't get the recent optimizations.
yusufm786 said:
Hi guys
After reading around the forum a bit, it seems some people were in similar situations as me, but I still don't have a definite answer.
I have been using a HTC Dream for about a year, and have been an avid fan of cyanogenmod. Although I like the fact that it's rooted and I can install any ROM i liked, I stuck with cyanogen because:
1. It's extremely stable
2. It's well established - they guys got their own site, a central location for all ROM info, all files are found in the same place, they continuously update the ROMs and it pretty much always gets better
The above points for me were reason enough to not even bother with any other ROM. I bought a HTC HD2 a few days back, and I now want to have the phone dual boot Android. What android rom is as good as cyanogen, where "good" is defined by my points above? I know there is a ported cyanogenmod rom, but how well does the port work, will it be updated often as new cyanogenmods get released, etc? Also, I'm no fan of nightly builds, so I don't want a port based on a nightly build - it must either be experimental, release candidate or stable. I also want to stick with the ROM I choose, so it should be continuously updated for the foreseeable future..
Click to expand...
Click to collapse
check this out http://android.hd2roms.com/
StephanV said:
First of all, you say you don't want nightly builds, but experimental is okay? Not exactly following, but hey.
There are a couple of CM based roms, if i'm not mistaken 3 are still being maintained:
-JDMS
-HD2ONE
-Mychiprima's (not sure if I'm spelling his name right here) build, it doesn't really have a name (thread contains "htc_linux_wince" at the very beginning)
Mychiprima's builds are based on the autobuild, and are therefor not checked and may contain bugs. JDMS and HD2ONE however are being thoroughly checked & optimized by the respective chefs, so I don't really see a point in not trying them.
Still, if you really want builds based on CM-stable there's always shubcraft and hyperdroid, but both have been discontinued for some weeks already, so you won't get the recent optimizations.
Click to expand...
Click to collapse
Thanks for that info. When I said experimental, I meant their beta versions - maybe my terminology is a bit wrong, but I know with the Dream, sometimes they used to release a beta version, then a RC, then a stable. From my understanding nightly builds were often buggy as they weren't tested. I'l have a look at those ROMs you suggest though. Aside from cyanogen, are there any other ROMs you think fit my two point criteria I gave in my first post?
leon98408 said:
check this out - link
Click to expand...
Click to collapse
Thanks a lot. That's very helpful. I'll have a look through that
yusufm786 said:
Thanks for that info. When I said experimental, I meant their beta versions - maybe my terminology is a bit wrong, but I know with the Dream, sometimes they used to release a beta version, then a RC, then a stable. From my understanding nightly builds were often buggy as they weren't tested. I'l have a look at those ROMs you suggest though. Aside from cyanogen, are there any other ROMs you think fit my two point criteria I gave in my first post?
Click to expand...
Click to collapse
I assumed that's what you meant, but RC's and nightlies are both just called experimental.
It's true nightlies as such aren't tested, because they are autobuilt. But the code that goes into it (in modules) does get tested first, so you'll usually have a nice working rom. (I'm talking about officially supported CM devices now, I already said how we do it with HD2).
There are other established builds (on HD2, you don't call them Android ROMs, but builds, because they run from sd card. ROMs are WinMo) yes, MDJ's got a whole series but I'm not a big fan of Sense myself. They're pretty popular though!
StephanV said:
I assumed that's what you meant, but RC's and nightlies are both just called experimental.
It's true nightlies as such aren't tested, because they are autobuilt. But the code that goes into it (in modules) does get tested first, so you'll usually have a nice working rom. (I'm talking about officially supported CM devices now, I already said how we do it with HD2).
There are other established builds (on HD2, you don't call them Android ROMs, but builds, because they run from sd card. ROMs are WinMo) yes, MDJ's got a whole series but I'm not a big fan of Sense myself. They're pretty popular though!
Click to expand...
Click to collapse
Ah i see. Thanks man - I got a lot to learn
Here's what Cyanogen said on the Official CyanogenMod Forums.
http://www.cyanogenmod.com/home/a-note-on-unofficial-ports-and-how-to-get-it-right
With this said, why don't we jump on the bandwagon and just join the CM team? Why don't we make this thing official (if we haven't tried already)? Just a thought, so don't kill me with your opinions. The Devs here are freakin' legit here and I'd like to see 'em do some of the work on the CM Team.
I trust the devs I download from because I follow their work. I don't need it to be "official". Besides, I like the personal touch and one-on-one support I get right here on the xda eris forum. And there's variety.
We could debate the politics of branding and what is CM and what is not CM. But the devs here disclose their sources, changes, known issues and brand their roms as uniquely their own while providing the support and updates. I don't think there's any confusion as to what is 'official' and what is not as the Android Police article referenced in CM's statement implies.
+1. The devs here are excellent, and the devs that base there ROMs on CM list them as "based" on CM not the official CM ROM. I'm not aware of any confusion that this has caused. I'm also not sure what creative constraints would be put on our devs if they went CM. I like the way they individualize the roms for thier personalities and their audiences. I also am not sure what benefit would come with being an "official" CM rom. Just my 2 cents.
Don't get me wrong, I'm not discrediting the Developers that cook these ROM by ANY MEANS whatsoever. They do incredible work with what they push, but here's what I'm saying. The CM ROMS are based off of Official CM Source Code, yes, but I think we'd be making it way easier on ourselves and the developers if we were an actual part of CyanogenMod. If we were a part of CM, then we'd get the CM ROMS as perfect as they can get and THEN the developers can add their own customization to a ROM based off of the Eris Release of CyanogenMod. They all are already doing the work that it would take to actually /BE/ a part of the CyanogenMod team, so why not get on with CyanogenMod so we can be official, and THEN the devs can customize and tweak ROMS they way they see fit?
Once again, absolutely NO discredit to the developers here, and I understand what it takes to keep these ROMS current and I am very appreciative of their work.
The CM ROMs that we have are either built from CM source or ported from the Hero builds already. I'm not really sure what this would give us other than maybe a "go team go" feeling and maybe a little more help than we already get. But the Eris and CDMA Hero are so similar, that doesn't matter much in my opinion as long as any Hero issues get worked out.
The CM buildbots are just building from source and posting the results, much like you would get if you ran EasyDev or did it manually. Now, there's a lot of work going on before that with the code, of course. But... That's what we use too.
I'm not against this at all. It just means that someone will have to 1) want to do it 2) have the time 3) convince Team Douche to let them in. I seem to remember that someone asked early on and the response was that we had to send them an Eris. This might have changed.
This comes up every so often. I guess one of us can find out what we would need to do at least...
Nothing would really change for the end user if we became official cm at this point. Basically one of the devs here that builds from source would submit their vendor tree to the cm source and they would be responsible for maintaining it just like we do now. The only real difference would be that it would get built by the cm build bot and nightly's would be released. I tweeted to cyanogen about getting my 2.2 tree in there along time ago when 2.2 was new but either I did it wrong(not a twitter person lol) or it just got lost in the many many tweets that go through cyanogens account. I never really pushed the issue more because of the extra time it would take me personally and it was just easier to work on my own schedule.
The only added benefit would be that maybe if there was an issue we could not fix then the cm team would take an extra look at our specific phone to help out but really since our phone is so close to the hero and it has official support they sort of fix most of our bugs anyway. I've personally always tried to give the cm team all the credit they deserve(which is alot) and I think the other dev's do the same.
Here's what Cyanogen posted up to www.cyanogenmod.com a week or so again. It looks like we'd need an interested dev here to stop by #cyanogenmod-dev on Freenode to start the process.
I think (and I use xtrSENSE, so I could be wrong) that a lot of people would like and "official" CM port for the Eris, just so they'd have "peace of mind" knowing they've got something "official."
And again, as we've seen mentioned in this post, it couldn't hurt to ask. Provided Team Douche doesn't actually want an Eris, we only stand to gain extra help on our ports.
Cyanogen said:
There’s been some recent talk about unofficial versions of CyanogenMod being created and released on sites like XDA, with large amounts of missing features and broken functionality, and I just wanted to talk about our position on this.
An “official” CyanogenMod version is one that uses our code review system, our source repository, and our mirror network. It should look, act, and feel like CM on any other device, and more importantly, it should follow our release schedules (which is a “when it’s ready” kind of thing, but we do plan our final/RC releases when we feel it’s ready). Most importantly, no major hardware functionality should be broken.
We want to see CM available for every device out there, and our infrastructure (and our developer community) is there for anyone to use. We spend a lot of time making new releases of Android backward-compatible with devices that are not ready for them, and we also spend much time making all of these (sometimes not so pretty) changes co-exist together without breaking other devices. The more eyes on your code, the better it will be.
That said, as much as we’d like it to be, the CMSGS project is not yet an official part of CyanogenMod. There are also a number of other unofficial ports out there which haven’t been submitted to us that we’d love to include. If you’re interested, stop by #cyanogenmod-dev on Freenode. If you didn’t get it from our mirror network or the CM forums, don’t expect it to be up to our standards.
The biggest thing to keep in mind when porting to a new device is to think about how your change is going to affect other devices. This is the biggest reason why we aren’t supporting Samsung devices other than the Nexus S yet. Don’t change hardcoded default values just to suit your device. Use the configuration options available, or add new ones with the original values as defaults. Do a build for another unrelated device after you make your changes (it helps to have another device to test with, of course) and verify it as well. Android was made for this, so do it right.
Like I’ve said so many times before, CyanogenMod is all about the community. And our community can help you too. I’d love to see more of these ports contributed to the project- it’s only going to make things better. We’ve grown from just a mod to what I’d call an “Android distribution” and we need to keep our standards high.
Click to expand...
Click to collapse
Oh no, does this mean we're all running unofficial CM ROMs ?
Wait, everything is working fine though... Official, unofficial, pffft
hallstevenson said:
Oh no, does this mean we're all running unofficial CM ROMs ?
Wait, everything is working fine though... Official, unofficial, pffft
Click to expand...
Click to collapse
+1 10 char......
A dev would have to maintain the device and be committed to building it up, like Darchstar was (is?) for the Hero CDMA. It really all depends on the Dev/Devs for the device, for example I've seen Cyanogen say in his twitter that he would also like to see the Dream/Saphhire continue to be developed for but no one has stepped up to maintain it. I can also only imagine that there are some qualifications for someone to maintain a device. Here is a list of the current maintainers for the devices
https://github.com/cvpcs/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn
Yeah, I can understand that. That's all I was saying, though. If they were doing all of the same work anyway I just thought it would be nice to have. I also didn't know if anyone had pursued this in the past, but seeing as how Conap had already tried I think I'm good with that. I also have no problems running the unofficial ROMs, just so you know. Thanks, guys!
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Hungry Man said:
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Click to expand...
Click to collapse
the way i do it is best for me,,and seems to be going fine,,, the cm7 ports have been alot better then the froyo ,, and alot faster ,, look how long it took the froyo camera to work,, gb the camera works outta the box,,
Hungry Man said:
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Click to expand...
Click to collapse
There is more than one definition of porting that people are using around here.
1) Porting to an unsupported device = compiling source, building a vendor tree, and getting it to work on said device (This is basically what the CyanogenMod team would do to make it an official build, although they would integrate the changes into the main source. The changes would mostly still be in a separate vendor tree in the repo. And it would be 'official'. From a practical/technical view, what workshed is doing is the same thing that the CM team would do.)
2) Porting an existing build to an unsupported device = taking an existing, already compiled ROM and making it work on said device (This is what tazz is doing with the Heroc build. This works out well when going from the Heroc.)
Anyone, feel free to correct me if I'm wrong, but I'm pretty sure that I have that right.
The only downside that I see from either of these is MAYBE not getting quite the support that we would get if the Eris had an 'official' build. I really don't think it's affecting much of anything, IMHO. It might in the future as the Heroc and Eris become more and more dated devices. But then, many of you won't really care because you're kids will be using them as mp3 players anyway while you use your fancy, new quad core HTC Destroyer 6G. (What's a Beiber?)
gnarlyc said:
There is more than one definition of porting that people are using around here.
1) Porting to an unsupported device = compiling source, building a vendor tree, and getting it to work on said device (This is basically what the CyanogenMod team would do to make it an official build, although they would integrate the changes into the main source. The changes would mostly still be in a separate vendor tree in the repo. And it would be 'official'. From a practical/technical view, what workshed is doing is the same thing that the CM team would do.)
2) Porting an existing build to an unsupported device = taking an existing, already compiled ROM and making it work on said device (This is what tazz is doing with the Heroc build. This works out well when going from the Heroc.)
Anyone, feel free to correct me if I'm wrong, but I'm pretty sure that I have that right.
The only downside that I see from either of these is MAYBE not getting quite the support that we would get if the Eris had an 'official' build. I really don't think it's affecting much of anything, IMHO. It might in the future as the Heroc and Eris become more and more dated devices. But then, many of you won't really care because you're kids will be using them as mp3 players anyway while you use your fancy, new quad core HTC Destroyer 6G. (What's a Beiber?)
Click to expand...
Click to collapse
I thought it was a girl
tazzpatriot said:
I thought it was a girl
Click to expand...
Click to collapse
Its a dude.
http://www.youtube.com/watch?v=3zb64y6Nvs0
refthemc said:
Its a dude.
http://www.youtube.com/watch?v=3zb64y6Nvs0
Click to expand...
Click to collapse
nope still a girl
http://www.youtube.com/watch?v=vwIa2S0YQs4
FYI: http://twitter.com/cyanogen/status/45246447385452544
@cyanogen said:
@Algamer we don't officially support the eris, it would be nice if someone doing the porting joined up with us though
about 8 hours ago via web in reply to Algamerhttp://twitter.com/Algamer/status/45235578886815744http://twitter.com/Algamer/status/45235578886815744
Click to expand...
Click to collapse
I think OUR devs are doing just fine. Why change now?
wildstang83
wildstang83 said:
I think OUR devs are doing just fine. Why change now?
wildstang83
Click to expand...
Click to collapse
Our devs are doing more than just fine, especially considering the amount of development we STILL have going on even though the Eris was a short-lived device that was EOL'd after like 8 months, was mid-range compared to the original Droid, and is a pretty niche device being MDPI on Verizon...
Why change now? That's a good question and I don't have a great answer. Like some have said on this post, maybe we'll get more support with bugs, etc. Additionally, a lot of the users here on XDA are looking for consistency. Since many who read and post here lack the skill set to do any meaningful ROM development themselves, they rely on the kindness of willing devs. However, devs will often add their own "personal touches" to their ROMs, which is great and well within their right to do. Having said that, many users are just looking to for something where they know, "Oh OK, so this is the base CM ROM that's officially distributed."
Personally, I don't care whether we have an "official" CM build or not for the Eris. I'm pretty reserved when it comes to ROMs for everyday use and am still using xtrSENSE as my default. The only reason I posted up cyanogen's recent tweet was to show that cyanogen himself is well-aware of the Eris development, is personally following the Eris ports, and is open to a partnership. My hope is that, by bridging communication, I am doing my part in helping to expose any possible mutual benefit (Eris XDA devs, ROM end-users, and Team Douche at CM) that could be gained by considering an "official" build. Ultimately, I understand that this is a decision that can only be made by the devs and also, not fulling understanding ROM development or having the skill set myself, I believe they are in the best position to make that decision. Like I said, I'm merely acting as a messenger, bringing this communication to light on our forum.
Hey, sorry for the N00b question. I'm a software developer (among other things), but am just now delving into the world of custom ROMs for my EVO 4g. I've been looking at what's available and see a few that say either AOSP or NOT AOSP.
This leads me to a few questions.
1. What is AOSP?
- Is it a separate code base (other than 3.70.651.1 #15) from which to start customizing the code to create a custom ROM?
2. What are the main differences that are generally present between the normal code base and AOSP based?
3. Can you go back to a ROM based on 3.70.651.1 (or another base) if you go AOSP?
4. If it is a custom code base, whas it created from scratch or based on something else?
Thanks for your time in answering this. If I'm way off base on what AOSP is, just let me know. I appreciate your replies!
Simple, it is android without any overlay from different carriers. It is just bone stock android.
Android Open Source Project.
Edited because I fail!
Disclaimer: I'm not taking anything away from any of the Devs here. I can't do any of the stuff they do with any of the ROMs, so please, don't take the following as such.
Most of the non AOSP roms here are themed versions of the stock rom with performance increasing tweaks and what not. Not saying there's anything wrong with that, but it is what it is.
AOSP roms like Cyanogenmod are built from the source code. They are usually more bleeding edge because when the source is released from Google, they get to working on the update. Cyanogenmod 7 is already on 2.3.3, whereas most sense roms are still on 2.2.1
AOSP is short for Android Open Source Project. It's the source code for Android.
HTC takes the AOSP code and then adds Sense and their other tweaks to it. Basically all ROMs whether they are from HTC, Samsung, or who ever, is based on AOSP. The thing is that some of the OEMs modify the code so much that things start to become incompatible. Plus if you go straight to AOSP right now, the source code is up to Android 2.3.3, no OEM released ROM is up to that version. So that creates even more incompatibilities.
Some custom ROMs use AOSP and implement the code to devices from the ground up. That's what Cyanogen Mod does. MIUI also does this (and adds some heavy modifications to the code as well) but that ROM isn't specifically built for the EVO but is instead ported from the Nexus One ROM.
To keep it simple:
- AOSP is Android at it's most basic form, it's straight from Google and is pretty much what the Nexus devices use as final builds.
- OEM ROMs are based on AOSP but are usually outdated and heavily modified.
- You can go back and forth if you want, but if you do, you should wipe your cache as their are incompatibilities.
Wow, that's great everyone! I completely understand now. I really appreciate all the help and replies!
Could I ask what everyone's favorite AOSP & non-AOSP ROM is? I know this has been asked before, but I'd like the opinions of those that replied to this post, if they don't mind.
I'm looking for "bleeding-edge" technology, wireless tethering, hulu, etc. all the bells and whistles essentially. I don't care so much about how "pretty" it looks, just functionality and cool-gadgety-stuff. Thanks again!!!
ShadowCyborg said:
Wow, that's great everyone! I completely understand now. I really appreciate all the help and replies!
Could I ask what everyone's favorite AOSP & non-AOSP ROM is? I know this has been asked before, but I'd like the opinions of those that replied to this post, if they don't mind.
I'm looking for "bleeding-edge" technology, wireless tethering, hulu, etc. all the bells and whistles essentially. I don't care so much about how "pretty" it looks, just functionality and cool-gadgety-stuff. Thanks again!!!
Click to expand...
Click to collapse
i would definitely suggest you look at cyanogenmod. it is built straight from source but improved apon in many ways. you can think of cyanogenmod as a crowd sourced rom. meaning anyone can contribute and submit changes to it. it is governed and controlled by the core members of the cyanogenmod team (team douche) but open for anyone to modify. what this gets you is a rom as close to aosp but made better. things like the power bar widget in the notification menu, music controls on the lock screen, quiet hours (notifications are turned down or off as well as dimming leds during set hours so they do not wake if if you say get an email at 5am), etc etc. members of teamwin recently built 4g support from the ground up be themselves and it is now a part of cyanogenmod. besides adding in features they also do a great deal of optimizing creating one of the most streamlined, user friendly fastest roms available.
oh and one part of your question seems unanswered - the 3.70.x.x.x of sense based roms is just the numbering of the rom build from htc for sprint but will always be built off of an older version of android due to the amount of customization done to it.
It's soap spelled wrong.
Sent from my PC36100 using Tapatalk
As far as AOSP go I like Cyanogen CM7 or MIUI but if I want a sense type rom I typically run Mikfroyo or Fresh.
Thank you all very much, once again! I have so far tried the following ROMs.
- King's Ultra Unleashed R2
- Cyanogen Mod 6.1.2
I'm running Cyanogen Mod right now and it's pretty cool, but the problem is I really like different features of each. I do like how many features are built into the Cyanogen Mod ROM though. I have to say, I LOVE the quiet time feature a LOT! I've wished Android had that for a while now. Oh, and the increased battery life and decreased charge time of both is AWESOME!!! My phone had gotten to the point where it wouldn't even charge in the car. It just kept the battery at the level it was at. Now it will only drop 7% battery over the entire night, unplugged!
I'm contemplating trying the EVO Non-Sense right now. I am just trying many of them to see which I like the best. Thanks for all the advise everyone!
Koni Elite II has some really cool features in it. try them all, it's a lot of fun
It's soap spelled wrong.
Click to expand...
Click to collapse
i thought it was the name of an ancient greek writer?
ShadowCyborg said:
Thank you all very much, once again! I have so far tried the following ROMs.
- King's Ultra Unleashed R2
- Cyanogen Mod 6.1.2
I'm running Cyanogen Mod right now and it's pretty cool, but the problem is I really like different features of each. I do like how many features are built into the Cyanogen Mod ROM though. I have to say, I LOVE the quiet time feature a LOT! I've wished Android had that for a while now. Oh, and the increased battery life and decreased charge time of both is AWESOME!!! My phone had gotten to the point where it wouldn't even charge in the car. It just kept the battery at the level it was at. Now it will only drop 7% battery over the entire night, unplugged!
I'm contemplating trying the EVO Non-Sense right now. I am just trying many of them to see which I like the best. Thanks for all the advise everyone!
Click to expand...
Click to collapse
you can also try cm7, which is gingerbread based. cm6.x.x is froyo based. its in the rc1 stage meaning it is almost finalized. the rc1 does not have 4g but the nightlies do.
rc1
http://forum.xda-developers.com/showthread.php?t=956187
nightlies
http://forum.xda-developers.com/showthread.php?t=729802
the nightlies are also 2.3.3 which is the newest build. nightlies=bleeding edge. they, as the name implies, as released nightly and contain all the code submitted from that day. sometimes they are broken or even fail to build but such is the life of living on the edge!
Alanman, thanks! I was thinking about trying that one too and... I agree that this is a BLAST! I'm absolutely loving the custom features, software and abilities.
Digged up an old thread through search
I was wondering what AOSP meant as well, but thanks I now know and might try some of the suggested ROMs in here So far I had only tried a King ROM (Shooter) with Sense 3.0. I don't mind it, but currently I can't get Swype to behave for me so I was thinking about dropping it and moving onto another.
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....
Hello XDA'ers.
First let me say that this will be somewhat a post about frustration with Android devices, but it's not meant to be misconstrued as disrespect to those who contribute to the development community. I know you guys work hard at this and I do appreciate your efforts. Your ROMs have been lightyears ahead of what Samsung stock offers.
But with that said, here's my question: is there a single rom that will work properly, is stable, wont crash, etc? I have been through over a dozen different ROMs across two devices, and there's always been something small or large wrong with them. The one I'm using on my i9505 right now is by Antares One and yesterday it decided to show me three or four notifications that "Google Play Services has stopped working" per minute and today none of my SMS messages are being sent.
But it's not limited that, rather, there's always been something or other that the Android ROM didn't like, or I had to find a workaround, or had to completely reflash with something else.
Has anyone experienced this? Why can't Android just be a stable OS? I'm really thinking about switching to a Microsoft phone for my next upgrade.
DJ
Even stock roms have their problems and stability issues. If you look through the Q&A section you'll find several threads about stock rom issues.
It's not Android's fault entirely. It has to do with the phone too. Roms on my device are always stable. Yet another user running the same rom on the same device has various problems.
I am currently running AOSP Marshmallow by the JDCTeam, no problems. Bluetooth works, wifi works, mobile data works, battery is fine (I went to sleep with 70% left and when I woke up 8 hours later it still was at 70%).
the problem here is the impossible fix of many problems by developers..why? many developers are not soft engineer and maybe they dont even know how to program just know how to port and replace files and thats all..a big team for every single phone are just impossible..
so a stable rom will never come..just find the one "flawless" and keep it..
for me the stable roms are not cm..or aosp..stock rom debloated are very stable..like s6 port to s4 and debloated..is a good one
Use stock ROM for stability. Although they are not fast as AOSP but they dont exhibit strange behaviors.
Sent from my GT-I9505 using Tapatalk
DJRepresent said:
Hello XDA'ers.
First let me say that this will be somewhat a post about frustration with Android devices, but it's not meant to be misconstrued as disrespect to those who contribute to the development community. I know you guys work hard at this and I do appreciate your efforts. Your ROMs have been lightyears ahead of what Samsung stock offers.
But with that said, here's my question: is there a single rom that will work properly, is stable, wont crash, etc? I have been through over a dozen different ROMs across two devices, and there's always been something small or large wrong with them. The one I'm using on my i9505 right now is by Antares One and yesterday it decided to show me three or four notifications that "Google Play Services has stopped working" per minute and today none of my SMS messages are being sent.
But it's not limited that, rather, there's always been something or other that the Android ROM didn't like, or I had to find a workaround, or had to completely reflash with something else.
Has anyone experienced this? Why can't Android just be a stable OS? I'm really thinking about switching to a Microsoft phone for my next upgrade.
DJ
Click to expand...
Click to collapse
Like GDReaper said in his post. For us those roms run perfectly fine. Sure there are bugs, but most issues are known before you decide to flash the rom. Besides the obvious bugs that are present there is also the user. A lot of problems are caused by inexperienced users. They don't know how to set up their phone, they flash shady apps, or use modifycations of their own (Xposed for example).
Then they come to XDA and provide no usefull information at all. For example:
"The one I'm using on my i9505 right now is by Antares One and yesterday it decided to show me three or four notifications that "Google Play Services has stopped working" per minute and today none of my SMS messages are being sent."
- For example you say you use a rom by Antares One. This gives us no information at all. He has made like 4 roms for the I9505. What build? What android version?
- Google Play Services has stopped working. What gapps package did you use?
- Have you made modifications of your own?
- Are you running an up to date modem and bootloader?
Also keep in mind that if you use for example a MM build that it's a work in progress. It has to be coded from scratch. So surely there will be some bugs, but you will get the latest Android version in return with all the latest security patches.
This post is not intended to flame you in any way. I think most of your frustration comes from the expectations that you have. You cannot expect that a CM based rom will work flawlessly out of the box. It's a work in progress.
This is a very good observation. I was thinking to write this kind of post in december.
A lot of Roms are abandoned or never pass nightly and you have to flash and flash again. Then suddenly all people jump to MM as if the world is ending tomorow. It is hard to find a good rom starting with Lollipop. I see a lot of people crying after KK stability and downgrading.
People are in a hurry, devs too, to flash the newest rom.
I prefer stability. A phone is not a camera, nor a battle field for flashing.. My 2C opinion.
I like custom roms, but sadly i need stability before customisation or performance. The only rom that delivers in this is Stock TW 4.4.2. If you want to go back to Kitkat use the latest firmware for your region.
It's very hard to deliver stability with a custom rom as stability is achieved through manpower, time and resources, which can't be provided through just donations.
Roms are abandoned because people move to other devices at some point.
And you can't stay on the same android version. Most of the roms are built from other sources. Like Resurrection Remix. The developer is wescrip, and he owns an LG device. The version for our S4 is built from his sources by TJSteveMX. If wescrip switched to Marshmallow it's pretty much impossible to for TJ to keep it Lollipop.
DJRepresent said:
(...)Why can't Android just be a stable OS? I'm really thinking about switching to a Microsoft phone for my next upgrade.DJ
Click to expand...
Click to collapse
This is a more general answer:
In the Android world there is a huge diversity of devices (--> hardware) and Android versions. The next thing, you have to keep in mind: A lot of vendors and telecommunications companies include their modifications into the ROMs.
I think that due to the availability of new devices each year and all these modifications, which also include the full stop in official updates after 6 months after the release of the device, will lead to unstable (official) ROMs.
The community then tries to update the devices in their spare time to the newest versions. But they have to figure out some special settings and modifications per device. And this is a long way as it seems.
In my opinion, you should not blame the community and the developers. I think, it is more Google or the vendors that can´t agree on a good way to distribute newer Android versions (e.g. a new API layer between OS and Hardware).