Database Users

[DEV DISCUSSION/Explanation] MIUI

The reason I am writing this thread is because of this:
http://forum.xda-developers.com/showthread.php?t=883222
The OP raised his concern regarding Cyanogenmod not being the biggest concerns for the Dev's. But I honestly think that during the times of CM6 the Dev's could have played a bigger role of bringing it to our Vibrant. I know Eugene tried to do something with it, but i think the release of Gingerbread 2.3 made his work not worthwhile because it was based on 2.2.I am aware that CM7 is in"heavy development cycle" due to Gingerbread 2.3, and most likely will be coming to our Vibrant. With that being said, I feel it is necessary because since we were not able to get CM6 to our phones then why not go for MIUI.
Honestly it is one of the greatest ROMS out there and sometimes i feel that our Vibrant should be getting some more love.Keep in mind that I am in no way bashing TW/Eugene or any other Dev's. Their work is nothing short of quality since I have been a very heavy user of both the Nero and Macnut Series. But I am sure that most people wouldn't mind having MIUI on their phones since its the best of both worlds. (Iphone/Android) Also, I wouldn't know the full process porting such a ROM because it is not an easy task and I am in no way a developer. Maybe it is being worked on with a 2.3 Base? Idk? I am just seeking for answers as I am sure most of other people are as well. I really hope that MIUI really comes to our phone and it becomes one of those projects where many Dev's were in the process to port the SenseUI (back in the day). Just trying to make our community better.
For Those who are unaware of MIUI ROM, here's a demo:
http://www.youtube.com/watch?v=G0U8ISI8YXM
Flame me, Hate me, w.e.. I just think its a debatable subject.
Ty.

What is this? A new trend?

hopefullu for the good.

Here is why, in my opinion.
If 25% of the masses want cm or miui, 25% want 2.2.1, and the rest want 2.3 - 2.3 it will be.
I like miui, I even had a barely working version of it for a little while. But, the guys who use my releases know what they want, those who use TW want their roms bionic, etc for master, eugene et al.
Nowdays, with leaks once a week, I think it will be tough to get a dev to drop everything else and start a port like miui.
But, if I could do it, I would, I think.

jellette said:
Here is why, in my opinion.
If 25% of the masses want cm or miui, 25% want 2.2.1, and the rest want 2.3 - 2.3 it will be.
I like miui, I even had a barely working version of it for a little while. But, the guys who use my releases know what they want, those who use TW want their roms bionic, etc for master, eugene et al.
Nowdays, with leaks once a week, I think it will be tough to get a dev to drop everything else and start a port like miui.
But, if I could do it, I would, I think.
Click to expand...
Click to collapse
Wow, that was the exact answer I was looking for. Like I mentioned before I am no Dev and you being here longer than me and more experienced I will take yourword for it. Your also right about these leaks coming very fast. Hopefully after a full port of 2.3 is done maybe just maybe we can get MIUI.
Thx Alot.

Yeah I Was Gonna Start Working On MIUI But I Need A Cyanogen Source, There Isn't One So I Kinda Hit A Wall
Maybe If Jellette Can Send Me What He Started I Can Just Port MIUI

Erickomen27 said:
Yeah I Was Gonna Start Working On MIUI But I Need A Cyanogen Source, There Isn't One So I Kinda Hit A Wall
Maybe If Jellette Can Send Me What He Started I Can Just Port MIUI
Click to expand...
Click to collapse
There are some serious problems with it but I think it is still on my computer, I'll let you know
Later.

Its Cool If Theres Some Problems, All I Need Is A Starting Point And I'd Be Able To Go From There

Does any other dev have a working cyanogen source??
Sent from my SGH-T959 using XDA App

What's MIUI?
Couldn't figure out what MIUI is from this post or the one linked in the OP.

Its A Chineese Rom
Its Basically The Best Rom Ever
I Have It On My Droid Incredible Its Super Quick And Looks Like Iphone Kinda

os2baba said:
Couldn't figure out what MIUI is from this post or the one linked in the OP.
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=G0U8ISI8YXM
Demo of the ROM.

Roms on the EVO not exciting

I have been on XDA since I bought my fist G-1 way back in the fall of 08. Cyanogen was a budding star, and Android was thought of as the "IPHONE killer". I have seen many developments since my first incursion into these forums. With that said, I would like to KNOW why someone cant come up with a ROM on the evo that could be based on Android, yet be completely skinned to give a more exciting experience. The thing is most ROMS are built on many others DEV's works, but nothing but theming is added to make them look different from each other. Yes, I know that there are a lot of under the hood changes going on to make their Roms faster, but nothing to make any Rom look different. I see some launchers out there that are awesome, but why cant someone come up with something that will really show off "Something different"
Before you go on about me and that you don't like what I am saying, point me to SOMETHING ANDROID, really different and don't attack me or this thread. I appreciate all of the hard work put into changing the Roms into your own, I have flashed most of the Roms built for the Evo and earlier Android devices. What I want is something that looks and act different, built on Android. I am hoping that I have just missed a posting, or some cool thread that someone has left. I strongly dislike IPHONE and its simple stupid approach, so please don't bring that platform into this discussion. Waiting to see!

Try MIUI. Its in the Development section.
You can also take a swing at compiling a ROM yourself, I've been considering it given the tools are free.
MIUI in its native form: http://www.youtube.com/watch?v=Or-9T44Bt7M

mr.bill said:
With that said, I would like to KNOW why someone cant come up with a ROM on the evo that could be based on Android, yet be completely skinned to give a more exciting experience.
Click to expand...
Click to collapse
Go ahead.
Great thing about Android...you don't like it...you can change it...for free!
It's easy to criticize.
Little harder to actually do.

mattykinsx said:
Go ahead.
Great thing about Android...you don't like it...you can change it...for free!
It's easily to criticize.
Little harder to actually do.
Click to expand...
Click to collapse
Your right, about asking me to go ahead, all the tools are there. I think what I will use this discussion for, is compling info for doing just that. I am not KNOCKING anyone elses work.....

Noiro said:
Try MIUI. Its in the Development section.
You can also take a swing at compiling a ROM yourself, I've been considering it given the tools are free.
MIUI in its native form: http://www.youtube.com/watch?v=Or-9T44Bt7M
Click to expand...
Click to collapse
Exactly the kind of answer I am looking for, thanks for taking the time to reply.....

I just started using MIUI yesterday and it is an eye opening experience. So many nice features that are built right in. If you haven't tried it... give it a go.
Besides roms like MIUI and MYMs warm 2.2, dev's leave the theming to you! You can load the rom you would like and then find a theme that fits you.

http://forum.xda-developers.com/showthread.php?t=870944&highlight=liquid+rush
this is a port from the acer liquid metal, i think you will find it interesting/different.

Is there a dev working on a ROM like MIUI that completely changes the UI? I do agree with the OP because all the ROM are pretty much the same except for the color theme.
I think we will have to wait until SPB drops their software for customizing.

thedudejdog said:
http://forum.xda-developers.com/showthread.php?t=870944&highlight=liquid+rush
this is a port from the acer liquid metal, i think you will find it interesting/different.
Click to expand...
Click to collapse
Agreed, this is something completely different than what you're used to.
Sent from my PC36100 using XDA App

+1 for MIUI. Been running it since the beginning of November and I must say it's pretty awesome.

I totally agree. I have seen many roms for the evo, but many of them look very similar to each other. I'm glad this topic is being discussed in a rational matter. I hope new ideas will come from it.

I remember seeing a few articles about a mobile OS on engadget a few times before it was announced that it was killed off. It was minimalistic to its roots. The video demo I saw of it activated the menu when you slid your right thumb(right-handed demo i guess) and a arched menu would pop up. You would be able to dig deeper by going through the brances of the arcs. I for the name of it but the name "Elise" or something like it comes to mind.

If anything is lacking it's kernels for the Evo.
We have like one choice for sense based and like two for AOSP based.
The Epic has more choices... [and that's saying something]

MIUI, Liquid rush, and to be honest there are some nice sense roms out there. i like sense , also if the new launchers that are being created come out, that can give you a new look as well. There is probably a significant amount of changes, however with this being aftermarket and not supported by OEM's and sprint i think that kind of limits your choices

You might like myn's warm two point two, it still retains the sense features from htc but has a totally different look and feel to it. Also checkout virus rom, those are pretty nice. A lot of people here are into switching roms each week to keep things interesting.
The two big ones that are not sense based are miui and cyanogen. I think the reason they take so long to make and that there is so few is the complexity of starting from scratch. At least I think, but I'm not a programmer.
Sent from my hand.

mattykinsx said:
If anything is lacking it's kernels for the Evo.
We have like one choice for sense based and like two for AOSP based.
The Epic has more choices... [and that's saying something]
Click to expand...
Click to collapse
Thats because the mods keep on banning our best kernel makers.
Hero_over and Kingslik(sp?) both made the best kernels during their time on XDA/Evo.

King was a hack, hero was a beast
jerryparid said:
Thats because the mods keep on banning our best kernel makers.
Hero_over and Kingslik(sp?) both made the best kernels during their time on XDA/Evo.
Click to expand...
Click to collapse

jerryparid said:
Thats because the mods keep on banning our best kernel makers.
Hero_over and Kingslik(sp?) both made the best kernels during their time on XDA/Evo.
Click to expand...
Click to collapse
I know. I'm just making an observation on the current reality

I can't really disagree with you but I think the reason why lots of the ROMs look alike is Sense. That said, I've been on MIUI since it came out. While others will scream that it's just copying iPhone, maybe it is but the ROM still retains all the benefits of android underneath.
Also, if it's just the launcher, I've tried out the Go Launcher and liked it the best. Again, it's not the same-old same-old.

gqstatus0685 said:
Is there a dev working on a ROM like MIUI that completely changes the UI? I do agree with the OP because all the ROM are pretty much the same except for the color theme.
I think we will have to wait until SPB drops their software for customizing.
Click to expand...
Click to collapse
I agree with you on SPB, it's a wait and see, I tried to be a bete tester for them, but I didnt get accepted. I have used it on my winmo devices in the past. Not sure what kind of experience though maybe just a nice launcher. I have to admit though I haven't tried MIUI, I do believe I will flash it later tonight.

Why the epic 4g CyanogenMod port is not backed by the CM team my opinion.

Hello,
This was brought up in another thread that is now locked.This post asked the question.
http://forum.xda-developers.com/showpost.php?p=11287492&postcount=40
and this is the blog post by Cyanogen
http://www.cyanogenmod.com/home/a-note-on-unofficial-ports-and-how-to-get-it-right
From what I can make from the blog post that Cyanogen put up on the CM website the Epic 4g as well as the other Galaxy S CM ports are not backed by Cyanogen because they do not go through the normal chain of how they add their code into their source code tree.The Galaxy S CM github has many changes to the stock android code that could possible and probably does break the code from being compiled for other phones. The framework is modified to work with the Samsung RIL that our phones use. The CM team will make additions to the stock android code not modifiy the stock code itself. So from my understanding of thing this is why Cyanogen does not consider what the CMSGS team has done as a part of the mainline CM code base. I believe this goes for all the Galaxy S phones not just the Epic.

Does being backed by the CM team make it get done any quicker? If so....
Sent from my SPH-D700 using XDA App

Being backed by the Cm team would definitely speed up the porting process, Cyanogen had the Evo Release Client up and running in a little over a month without source

So its a matter of pulling the source together and prperly placing it into their source control so their build bot can properly dov what build bots do...build...then CM helps with the port process?
If I think I'm following that right...somone better start uploading code to Cyanogens t&c's(terms and conditions) so we can have some epic awesomesauce.
Sent from my SPH-D700 using XDA App

Most importantly, no major hardware functionality should be broken.
Click to expand...
Click to collapse
What this statement implies is that no Cyanogenmod port is ever gonna be official right away; there's always an in-progress period where major functions are broken. Regardless of other issues, that's where our Epic port is at right now and part of the reason why it's not official.

Poryhack said:
What this statement implies is that no Cyanogenmod port is ever gonna be official right away; there's always an in-progress period where major functions are broken. Regardless of other issues, that's where our Epic port is at right now and part of the reason why it's not official.
Click to expand...
Click to collapse
True but there is code that is changed in the Galaxy S port that doesn't get changed at all in other CM ports as far as I know.

If we had HTC Epic's instead of Samsung Epic's and still identical devices... CM would officially support the Epic.
Period. They can say whatever they want but we all know this to be the case. You can't tell me Samsung changes their code that much more then HTC... last I checked Sense was a much more in depth overall to the underlying OS then Touchwiz is.. but maybe not.

The thing is, HTC uses the same hardware across the board (snapdragon processors, same camera etc.) which makes Rom ports much much easier to pull off, whereas the Hummingbird in the Galaxy S is only in the Galaxy S and only the Unlocked Galaxies and Gsm have froyo source so far.

Thanks for osting this skeeter
Android Creative Syndicate- From spontaneous ingenuity, comes creative brilliance

063_XOBX said:
The thing is, HTC uses the same hardware across the board (snapdragon processors, same camera etc.) which makes Rom ports much much easier to pull off, whereas the Hummingbird in the Galaxy S is only in the Galaxy S and only the Unlocked Galaxies and Gsm have froyo source so far.
Click to expand...
Click to collapse
The changes in the code have nothing at all to do with the cpu its all for the radio which even having froyo source will not help a bit with.Its all in the way the code changes were done. Rather then adding to the base code in CM the code was directly changed which is what Cyanogen has an issue with doing so basically could and probably has broken the radio code for other cdma phones, I don't know what or if any of the code in the frameworks was changed for the gsm Galaxy S phones so I can't say for sure that it the source from the CMSGS github wouldn't work on another GSM phone I only know that changes were made to get it working on the Epic and Fascinate.I don't think what the CMSGS team did was wrong they did what they had to do to get things working and from the time I spent working on it it didn't seem like there was much input from the CM team at all but that was probably happening in another irc channel that I was not invited into if they were involved.I was hoping that the Galaxy S would have had more interest from the CM team as a whole I know a phone or two was collected and donated to at least one dev and i also heard that Koush was supposed to take over the Captivate port of CM I am not sure if that ever happened or not but the Epic and Fascinate were from the beginning the red headed step children of the Galaxy S line it really is too bad that there wasn't for developers around to help work on it and make an offical Cyanogen backed CM port.I blame it all on the Evo personally if the Epic came out first it would be the Epic sporting all the kernel and roms that you can find in the Evo forum instead we are left with a handful or less of devs and a phone that is far from the potential that it has.

This statement brings up one of my biggest questions I have for the epic forums that I have yet to understand. If a lack of devs are the biggest problem for the epic why is it they are not attempting to train anyone else. Here's my point. I have cataloged every bit (and still am) of info I know about themeing android and the samsung epic. I wrote guides breaking down every part of installing the tools necessary and using them so anyone just sitting down with a fresh windows and their first android phone would understand. Where are our dev guides besides "read developer.android.com". I've read it, I've set everything up. I've downloaded source, I've even ran make with success. But it does nothing without proprietary files. How do you plug them in. extract files.sh dont work without cm6 running on my phone. Where do we learn how to edit our build.prop, init.rc, compile drivers and modules. Joey krimm it's a great beginners source but what about updates since the stall between ubuntu 10 64 support, and 64 becoming the default. I feel like not only it's sammy and sprint at fault, but so are devs that arent open with their knowledge. The best gift this community could have gotten in all of this "down time"waiting was time spent learning. Devs stuck waiting on modems and source, start writing and teaching so when you get that source, you'll have a team behind you. That's the spirit of linux and it dont exist on xda's Samsung Epic Development section!
Sent from my SPH-D700 using Tapatalk

dreamsforgotten said:
This statement brings up one of my biggest questions I have for the epic forums that I have yet to understand. If a lack of devs are the biggest problem for the epic why is it they are not attempting to train anyone else. Here's my point. I have cataloged every bit (and still am) of info I know about themeing android and the samsung epic. I wrote guides breaking down every part of installing the tools necessary and using them so anyone just sitting down with a fresh windows and their first android phone would understand. Where are our dev guides besides "read developer.android.com". I've read it, I've set everything up. I've downloaded source, I've even ran make with success. But it does nothing without proprietary files. How do you plug them in. extract files.sh dont work without cm6 running on my phone. Where do we learn how to edit our build.prop, init.rc, compile drivers and modules. Joey krimm it's a great beginners source but what about updates since the stall between ubuntu 10 64 support, and 64 becoming the default. I feel like not only it's sammy and sprint at fault, but so are devs that arent open with their knowledge. The best gift this community could have gotten in all of this "down time"waiting was time spent learning. Devs stuck waiting on modems and source, start writing and teaching so when you get that source, you'll have a team behind you. That's the spirit of linux and it dont exist on xda's Samsung Epic Development section!
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Where's the thank spam? hah.
I've slowly been dipping myself into the Developer 'pool' for the epic if you will..and at first when I started working nobody really ever helped out..they just threw me a link and was like..start reading blah blah blah..
Reading only gets you so far; Imho you learn better when you've got the experience of working first hand with the material you're trying to learn.

dreamsforgotten said:
This statement brings up one of my biggest questions I have for the epic forums that I have yet to understand. If a lack of devs are the biggest problem for the epic why is it they are not attempting to train anyone else. Here's my point. I have cataloged every bit (and still am) of info I know about themeing android and the samsung epic. I wrote guides breaking down every part of installing the tools necessary and using them so anyone just sitting down with a fresh windows and their first android phone would understand. Where are our dev guides besides "read developer.android.com". I've read it, I've set everything up. I've downloaded source, I've even ran make with success. But it does nothing without proprietary files. How do you plug them in. extract files.sh dont work without cm6 running on my phone. Where do we learn how to edit our build.prop, init.rc, compile drivers and modules. Joey krimm it's a great beginners source but what about updates since the stall between ubuntu 10 64 support, and 64 becoming the default. I feel like not only it's sammy and sprint at fault, but so are devs that arent open with their knowledge. The best gift this community could have gotten in all of this "down time"waiting was time spent learning. Devs stuck waiting on modems and source, start writing and teaching so when you get that source, you'll have a team behind you. That's the spirit of linux and it dont exist on xda's Samsung Epic Development section!
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
When it comes to working on CM most of the work that needs to be done is all coding which we have very few if anyone java coders. Also you can use extract-files.sh on a phone running straight DK28 to get the propietary files needed to build CM with.When it comes to everything else most of the devs have taught themselves how to do the things they so by trial and error and alot of reading the internet. I know I have little coding skill so its would be hard to teach someone something you don't know how to do yourself and alot of the other things like putting togther device files to build android even on the google site has no real information on how to do it at all the best way I think is to just compare what the other phones use and piece it together from that.

Yet it still makes me wonder; why no epic/galaxy s support? Virtually every other phone, and even some tablets like the gtab, have CM support and even CM7 support. Even the HTC Hero, with obviously no source code for 2.2 or 2.3 and no official 2.2 ever to be released, has a working build of CM7. Is it pure incompetence of Epic developers? Is it a lack of interest? Is it simply cyanogen not wanting to support galaxy s devices? I really don't know, but I'd really like to.

theimpaler747 said:
Yet it still makes me wonder; why no epic/galaxy s support? Virtually every other phone, and even some tablets like the gtab, have CM support and even CM7 support. Even the HTC Hero, with obviously no source code for 2.2 or 2.3 and no official 2.2 ever to be released, has a working build of CM7. Is it pure incompetence of Epic developers? Is it a lack of interest? Is it simply cyanogen not wanting to support galaxy s devices? I really don't know, but I'd really like to.
Click to expand...
Click to collapse
From what I can see its not that Cyanogen doesn't want to support the galaxy s devices its that it seems they don't give any input to the devs that are working on CM for the galaxy s. They have basically split off from the main CM source tree itself and run their own source tree. It seemed like (and this is from the limited amount I saw on irc) that there was no input from the CM team they just let them work on their own. CM has ways to setup the code so the source tree remains workable across the board on all the devices it supports, the cmsgs team has just taken a different route on things and gone their own route thus making it not backed by cyanogen, was it the right way to do it who knows but it has made all the galaxy s devices redheaded step children in the eyes of Cyanogen and the CM team as a whole by the looks of it. I know from the point of view of having an Epic the major hold up to it is having coders with the proper skills to do the coding in general we had one coder working on it I don't know if he is still involved or not at this point. All I know is to make is a backed by Cyanogen CM port the coding that has been done so far would have to be completely redone in the ways that the rest of the CM team adds code to the CM source tree with as little to no modification of the stock CM code as possible.
Also I would like to add that I am not trying to put anyone down that is working on the CMSGS team they have done CM working on these devices and am in no way bad mouthing the work that has been done. This is just my view on things and why Cyanogen doesn't back the galaxy s CM ports.
Sent from my SPH-D700 using Tapatalk

theimpaler747 said:
Yet it still makes me wonder; why no epic/galaxy s support? Virtually every other phone, and even some tablets like the gtab, have CM support and even CM7 support. Even the HTC Hero, with obviously no source code for 2.2 or 2.3 and no official 2.2 ever to be released, has a working build of CM7. Is it pure incompetence of Epic developers? Is it a lack of interest? Is it simply cyanogen not wanting to support galaxy s devices? I really don't know, but I'd really like to.
Click to expand...
Click to collapse
Well, trying to comprehend everything that is going on here, I feel like the CMTeam does not feel the Epic is worth porting to CM7 due to it's delay on a FroYo source, which I am positive would make the Epic's porting much easier.
However, it still makes me wonder why they could not have used 2.1 to port to CM7, as like you said, the Hero has been able to do.
It also confuses me that the Captivate has even been able to run a Gingerbread port (I believe cyanogen) then. I realize that the Captivate has no 4G or a slide or anything, but the fact that they were willing to work off of 2.1 I assume gets me wondering why no one has tried making a CM port for the Epic's 2.1
I am trying to understand this as best as I can, so please forgive me if I seem to be giving false input on this conversation.

Its the time taken to port a phone, combined with the number of phones above yours on their list. The fact is they have a list of other phones they feel like investing their time in over the galaxy s line in general which is even more of a reason all knowledge of development on the Epic should be layed out even in pieces like the rest of the information here. Honestly thinking "leak it to noobnl, then we'll get all the goods" isn't going to cut it. Java coders, ubuntu fanatics who have compiled a few apps, and new people willing to learn should be putting heads together compiling new ****. If we dont start a group effort of making a bone stock aosp froyo altering the existing drivers were not going to be much further with source code. And it should be layed out here irc dont work for everyone.
Sent from my SPH-D700 using Tapatalk

acer1096xxx said:
Well, trying to comprehend everything that is going on here, I feel like the CMTeam does not feel the Epic is worth porting to CM7 due to it's delay on a FroYo source, which I am positive would make the Epic's porting much easier.
However, it still makes me wonder why they could not have used 2.1 to port to CM7, as like you said, the Hero has been able to do.
It also confuses me that the Captivate has even been able to run a Gingerbread port (I believe cyanogen) then. I realize that the Captivate has no 4G or a slide or anything, but the fact that they were willing to work off of 2.1 I assume gets me wondering why no one has tried making a CM port for the Epic's 2.1
I am trying to understand this as best as I can, so please forgive me if I seem to be giving false input on this conversation.
Click to expand...
Click to collapse
But like I said, there's CM7 (Android 2.3 if you don't know) for the HTC hero, with no 2.2 or 2.3 source code. So why not us?

theimpaler747 said:
But like I said, there's CM7 (Android 2.3 if you don't know) for the HTC hero, with no 2.2 or 2.3 source code. So why not us?
Click to expand...
Click to collapse
Alright, this is what I believe.
The Hero does not have 4G, or a QWERTY keyboard, two things the Epic does have that could make a pure AOSP port more difficult without a source. Also, HTC runs Snapdragon throughout the whole system, making tweaks a lot more simpler than SGS's Hummingbird Processor, which uses something else (I can't remember) with their system as well.
The last part I'm not sure if that makes a big deal or not, since I have seen a (what I think) CM7 port for the Samsung Captivate, so it may simply be because of 4G and the QWERTY keyboard.
I see what you're saying though. I guess the CMTeam should have no problem making a CM7 port based off of the Epic's 2.1 source...maybe they're just waiting because 2.2 might make it easier and supposedly 2.2 is coming soon so there'd be no point in starting now...otherwise I have no clue.

acer1096xxx said:
Alright, this is what I believe.
The Hero does not have 4G, or a QWERTY keyboard, two things the Epic does have that could make a pure AOSP port more difficult without a source. Also, HTC runs Snapdragon throughout the whole system, making tweaks a lot more simpler than SGS's Hummingbird Processor, which uses something else (I can't remember) with their system as well.
The last part I'm not sure if that makes a big deal or not, since I have seen a (what I think) CM7 port for the Samsung Captivate, so it may simply be because of 4G and the QWERTY keyboard.
I see what you're saying though. I guess the CMTeam should have no problem making a CM7 port based off of the Epic's 2.1 source...maybe they're just waiting because 2.2 might make it easier and supposedly 2.2 is coming soon so there'd be no point in starting now...otherwise I have no clue.
Click to expand...
Click to collapse
I think we also have 'limited functionality' w/ 2.1 as far as the phone's full capability.
2.2 will unlock some hidden potential IMO. Could be the reason why all the hubbub to 'wait for 2.2'.. again, just speculating.

[Q] Adding Eris to CyanogenMod Supported Devices?

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.

Spam Cyanogen?

My cousin recently put his Streak to rest because he upgraded to the Motorola Atrix, he was saying how the Streak became the forgotten golden child. I was thinking why not Spam Cyanogen on Twitter and ask for Streak development? Maybe someone would be bold enough or kind enough to offer him a an old Streak to work on? Long shot but I don't think it would hurt to try.
Just trolling out loud is all lol
http://twitter.com/cyanogen

cyanogenmod is overrated imho

aaronv89 said:
cyanogenmod is overrated imho
Click to expand...
Click to collapse
As Much as I miss Cyanogenmod on my HTC ARIA I would not trade it for for my Simple streak 1.2!

refthemc said:
. . . . because he upgraded to the Motorola Atrix, . . . .
Click to expand...
Click to collapse
I would not call anything with MotoBlur an upgrade.

marvin02 said:
I would not call anything with MotoBlur an upgrade.
Click to expand...
Click to collapse
atrix is beast tho

Don't spam Cyanogen, they are willing to make rom for Streak (actually DJ_Steve tried it), but nobody can because we don't have all drivers for Dell Streak (audio driver was not released and Dell won't release it in the future).
But if you want to spam something, check this:
http://www.ideastorm.com/ideaView?id=087700000008XYuAAM#comments

marvin02 said:
I would not call anything with MotoBlur an upgrade.
Click to expand...
Click to collapse
+1. Motoblur is the worst android coding I've ever seen. It doesn't even run well on many dual core phones.

Revin said:
Don't spam Cyanogen, they are willing to make rom for Streak (actually DJ_Steve tried it), but nobody can because we don't have all drivers for Dell Streak (audio driver was not released and Dell won't release it in the future).
Click to expand...
Click to collapse
CM7 isn't overrated, its AOSP with tweaks, built-in overclocking settings, status-bar tweaks, unlock screen tweaks, DSP manager, all built from source, no bloat, very fast and compatible... nothing to not like about it.
As far as audio drivers not working, Fards seems to have it working just fine in his fork of the 'alpha' gingerbread source code that Dell released, so I'd say that's patently false... Although his kernel is still quite buggy (certain sensors not working, wakelock issues, etc)... I'd say his kernel fork is probably the closest thing to getting CM working on our Streaks.
The work Fards/AWD_Maniac have done is phenomenal, that being said, I have no idea how much work would need to be done to make the kernel work with a CM7 userland.
*edit*, the Atrix blows, also being obnoxious never got anyone anywhere.

I too think that Fards/AWD_Maniac did great job, but just check the forums with CM6.1 alpha and MIUI alpha from DJ_Steve. He stopped the development because audio was not working and he needed audio drivers for Dell. I believe, that if there will be some way he will make it. I am not sure if you can make driver for something you know nothing about and without support.
But of course it will be nice to have CM/MIUI for our devices.
Anyway, please comment and vote, if you check page 3/4, there are people asking for Gingerbread. Actually Amy from Dell wrote on twitter that who wants Gingerbread should vote/post there:
http://www.ideastorm.com/ideaView?id=087700000008XYuAAM#comments
So I am asking everyone - please go there and give there as many votes as possible. Create another accounts, ask your friends etc.
We can have at least Gingerbread officially!

Revin said:
I too think that Fards/AWD_Maniac did great job, but just check the forums with CM6.1 alpha and MIUI alpha from DJ_Steve. He stopped the development because audio was not working and he needed audio drivers for Dell. I believe, that if there will be some way he will make it. I am not sure if you can make driver for something you know nothing about and without support.
Click to expand...
Click to collapse
Maybe you're not getting what I'm saying, Fards is already compiling kernels for gingerbread... FROM SOURCE, even if binary blobs are being used for audio libraries, they were compiled for Linux kernel 2.6.35, the version needed by GB. I don't think this is a stumbling block for anyone anymore since we now have a working kernel from source for gingerbread.
It seems that DJ_Steve never had too much luck compiling the Android userland for the Streak, in fact, I don't think anyone really has, except for those TERRIBLE MIUI/CM ports, but I'm thinking even those were binary rips. All the Streakdroid versions (sans 2.0.0) used pre-compiled files from official dell builds for the Android userland.