Database Users

[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.

Welcome to B2G!! (boot to gecko)

Boot to Gecko is coming! if you haven't heard of b2g, its a web based replacement OS designed to take on android, apple and WP7, the exciting thing is, to speed up the release, it is relying on similar linux based processes to run. see here ;
https://wiki.mozilla.org/B2G
I'm in no way associated with this project, just wanted you guys to see it. Some industrious developers are already working at a port for the galaxy s2 and the nexus. I know we have talented dev's right here, can we be far behind?
exciting yes??!!

Ava.tar said:
Boot to Gecko is coming! if you haven't heard of b2g, its a web based replacement OS designed to take on android, apple and WP7, the exciting thing is, to speed up the release, it is relying on similar linux based processes to run. see here ;
https://wiki.mozilla.org/B2G
I'm in no way associated with this project, just wanted you guys to see it. Some industrious developers are already working at a port for the galaxy s2 and the nexus. I know we have talented dev's right here, can we be far behind?
exciting yes??!!
Click to expand...
Click to collapse
Yeah, true, we really have quite wonderful devs for our G3 community, it shall just be a matter of time, I think

I'm pretty sure that rubbensolie will look forward to boot gecko to our phone ;P

Darius_AWS said:
I'm pretty sure that rubbensolie will look forward to boot gecko to our phone ;P
Click to expand...
Click to collapse
I already did look into it actually xD. But no progress, because i think we need another kernel for it.

Ava.tar said:
Boot to Gecko is coming! if you haven't heard of b2g, its a web based replacement OS designed to take on android, apple and WP7, the exciting thing is, to speed up the release, it is relying on similar linux based processes to run. see here ;
https://wiki.mozilla.org/B2G
I'm in no way associated with this project, just wanted you guys to see it. Some industrious developers are already working at a port for the galaxy s2 and the nexus. I know we have talented dev's right here, can we be far behind?
exciting yes??!!
Click to expand...
Click to collapse
As it is not a different Android version, but a totally different system, it will require developing a new kernel, whole new drivers and of course porting the system.
Kernel and driver developing are much a pain in the a*s, so it won't be "easy" like porting MIUI (i do not mean to offend anyone).
I think it will require months of hard work from a c/c++ skilled dev....
Of course, i would be more than happy if someone is able to state the opposite!

I did a bit more poking around and found that mozilla marketplace (the boot to gecko play store) is now open to devs!
Admittedly this wont be an easy port but the similarities between b2g and android will surely put our devs here ahead of the pack in the race to port b2g. And they are already having a good try on other android devices. I have so much faith in our devs!

https://marketplace.mozilla.org/en-US/login?to=/en-US/developers/
Heres the link

Well, i know how to develop web apps but i don't get the point on mozilla choice...
And performances of webapps in mobile phones are VERY low. I mean REALLY VERY low. At least, they are low until you provide optimized code for the underlying hardware but if you do so, you will need to provide a different interface for every kinf od hardware, ie: you will need to build a kernel with proper dirvers...
I'm not saying it can't be done, of course it can be, but as i stated before, it will be a major work from a skilled dev.
From my point of view, having CM7 /and then 9) fully working is much more interesting than trying to port mozilla OS.

andreapier said:
Well, i know how to develop web apps but i don't get the point on mozilla choice...
And performances of webapps in mobile phones are VERY low. I mean REALLY VERY low. At least, they are low until you provide optimized code for the underlying hardware but if you do so, you will need to provide a different interface for every kinf od hardware, ie: you will need to build a kernel with proper dirvers...
I'm not saying it can't be done, of course it can be, but as i stated before, it will be a major work from a skilled dev.
From my point of view, having CM7 /and then 9) fully working is much more interesting than trying to port mozilla OS.
Click to expand...
Click to collapse
Well looking at the work already being done it doesnt look slow, it looks blazing fast! the interface looks brilliant and incredibly user friendly. I am pretty excited about a finished cm9 too but chasing released android firmwares to port is surely not as fun for talented devs as getting in on something at ground level? this isnt even out yet! its not even a blip on apple or androids radar, it is exciting!
its just another option. Im sure it will be something being discussed more and more in the very near future

Updates
https://wiki.mozilla.org/Gaia/Hacking
http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central/
Very exited about this project. Even if takes a year to get it working on our phones.

In my opinion I don't think you should over work devs because they work in their own time and users expect them to be robots who just port roms and develop day and night. Let our devs work on their current projects and finish them to a high standard. Its quality over quantity right?
I don't mean to offend anyone. Just voicing my opinion.
Sent from my GT-I5800 using xda app-developers app

[Q] Is it as simple as compiling cyanogenmod?

Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.

evodev said:
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
Click to expand...
Click to collapse
It is

XpLoDWilD said:
It is
Click to expand...
Click to collapse
Just a quick question,will it support mediatek devices?

s.sawrav said:
Just a quick question,will it support mediatek devices?
Click to expand...
Click to collapse
Yes.
We have early support for the r819.

I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.

Mayank7795 said:
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Click to expand...
Click to collapse
If you have a working AOSP, it should be available without problems.

@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers

What about devices that have CM10 only?

lozohcum said:
What about devices that have CM10 only?
Click to expand...
Click to collapse
You need at least an unofficial CM 10.2 / AOSP 4.3.

JoinTheRealms said:
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
Click to expand...
Click to collapse
Building is always worth an attempt...
I used to build my own CM, i'm gonna try to build my own omni too but i'm struggling. I must be doing something wrong with the repo init but I can't seem to find what... I'm gonna update my buildbot first because it's been awhile, and maybe try again tomorrow.

As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
That's why its worth scrawling through XDA, going through guides and learning to dev. Nothing wrong with a dev who decides to leave an older version for a newer version. They're doing it for fun and free.

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.

pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
As long as there is no hard reason to stop supporting a device and we have someone who is taking care of that device we will try
On the other side - there is constant evolution which sometimes will make it necessary to leave a device "behind" if the effort will become too large
Sent from my Find 5 using xda app-developers app

XpLoDWilD said:
It is
Click to expand...
Click to collapse
Not quite yet... Not until we have roomservice up and running.
(For those that didn't understand what I said - roomservice is the part of CM's repo management system that will automatically sync a device tree and all dependencies. roomservice is HEAVILY dependent on github's APIs, so we couldn't even start work on that particular piece of infrastructure until the project went public.)

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.

mattman83 said:
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
Click to expand...
Click to collapse
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance

pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
I hope the Acer IconiaTAB A5000 will get supported.

Please, support for RAZR i (x86)

lozohcum said:
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
Click to expand...
Click to collapse
Problem is, every device has its own pitfalls. Some are harder to overcome than others.
For example, the lack of NEON in tegra2 combined with the dependency of newer gapps on NEON really screws tegra2 devices, and there isn't much that can be done about it.
Also, in some cases, the things needed to get a device working aren't in the tree, but are in the frameworks to handle OEM-specific oddities (RIL hacking in opt/telephony, which I admit I'm not too familiar with...) or platform support. Sometimes, old devices get left behind simply because their platform overall is a ***** to support beyond a certain point. (See how MSM8660 devices have been lagging lately, due to Qualcomm pretty much sunsetting that chipset.)

Support Xiaomi Mi2/2S please

Hi devs... it is a sincere request from you all...
Here in XDA, we dont have any thread related to Xiaomi's Mi2/2s.
I hope by now people have heard enough about Xiaomi as their latest flagship model is getting shipped soon... Mi3
I request the developers of Omni ROM to support Xiaomi devices, especially Mi2/2S pls just like other CM , AOSP & AOKP ROMs r doing...
Waiting for your reply... Thanks in advance....

plikmuny said:
Hi devs... it is a sincere request from you all...
Here in XDA, we dont have any thread related to Xiaomi's Mi2/2s.
I hope by now people have heard enough about Xiaomi as their latest flagship model is getting shipped soon... Mi3
I request the developers of Omni ROM to support Xiaomi devices, especially Mi2/2S pls just like other CM , AOSP & AOKP ROMs r doing...
Waiting for your reply... Thanks in advance....
Click to expand...
Click to collapse
Xiaomi are notorious for being flagrant GPL violators, so - highly unlikely.
Just like CM, the real deciding factor for support is, "will a maintainer pick it up?"

Entropy512 said:
Xiaomi are notorious for being flagrant GPL violators, so - highly unlikely.
Just like CM, the real deciding factor for support is, "will a maintainer pick it up?"
Click to expand...
Click to collapse
Oh come on... please don't punish the users based on company's attitude...
It is a great phone with great UI. just like Nexus 4 it has similar hardware.
All we request here is where ever a new developer wants to build a open sourced ROM, they say not to touch Xiaomi... & everybody wants to build a ROM for Nexus & other phones where they have too many options already...
This is not fair & is not necessary for Nexus & other phone models where they already have too many options available.
I am not saying that you shouldn't , but think in my way also pls.... As you may be aware of there are so many Xiaomi Mi2/2S users alone in Europe & other countries also... but the main problem is lack of good development support. only we should depend on the MIUI developers who keep releasing new build with minimal features based on 4.1.1 version. I mean , we are expecting 4.4 release soon & MIUI is still based on 4.1.1
come on man what the heck is going on... right ?i think always the same like this.... but what to do.. who will listen to our outcry ?
I thought atleast devs here care for our requests.... hence i gave it a go.... I really hope you understand our problem & support this device....
atleast consider from the users aspect pls... Thanks for understanding..... Take care.
I dont have any intention of being rude or arrogant here, i am just expressing my helplessness & pleading the devs for the betterment of android on all Xiaomi devices....
thats all... Thanks once again....

plikmuny said:
Oh come on... please don't punish the users based on company's attitude...
It is a great phone with great UI. just like Nexus 4 it has similar hardware.
All we request here is where ever a new developer wants to build a open sourced ROM, they say not to touch Xiaomi... & everybody wants to build a ROM for Nexus & other phones where they have too many options already...
This is not fair & is not necessary for Nexus & other phone models where they already have too many options available.
I am not saying that you shouldn't , but think in my way also pls.... As you may be aware of there are so many Xiaomi Mi2/2S users alone in Europe & other countries also... but the main problem is lack of good development support. only we should depend on the MIUI developers who keep releasing new build with minimal features based on 4.1.1 version. I mean , we are expecting 4.4 release soon & MIUI is still based on 4.1.1
come on man what the heck is going on... right ?i think always the same like this.... but what to do.. who will listen to our outcry ?
I thought atleast devs here care for our requests.... hence i gave it a go.... I really hope you understand our problem & support this device....
atleast consider from the users aspect pls... Thanks for understanding..... Take care.
I dont have any intention of being rude or arrogant here, i am just expressing my helplessness & pleading the devs for the betterment of android on all Xiaomi devices....
thats all... Thanks once again....
Click to expand...
Click to collapse
I think you misunderstood. Without the kernel source it is pretty much impossible to support the device regardless of whether a dev wants to or not - we can't change that.

plikmuny said:
Oh come on... please don't punish the users based on company's attitude...
It is a great phone with great UI. just like Nexus 4 it has similar hardware.
All we request here is where ever a new developer wants to build a open sourced ROM, they say not to touch Xiaomi... & everybody wants to build a ROM for Nexus & other phones where they have too many options already...
This is not fair & is not necessary for Nexus & other phone models where they already have too many options available.
I am not saying that you shouldn't , but think in my way also pls.... As you may be aware of there are so many Xiaomi Mi2/2S users alone in Europe & other countries also... but the main problem is lack of good development support. only we should depend on the MIUI developers who keep releasing new build with minimal features based on 4.1.1 version. I mean , we are expecting 4.4 release soon & MIUI is still based on 4.1.1
come on man what the heck is going on... right ?i think always the same like this.... but what to do.. who will listen to our outcry ?
I thought atleast devs here care for our requests.... hence i gave it a go.... I really hope you understand our problem & support this device....
atleast consider from the users aspect pls... Thanks for understanding..... Take care.
I dont have any intention of being rude or arrogant here, i am just expressing my helplessness & pleading the devs for the betterment of android on all Xiaomi devices....
thats all... Thanks once again....
Click to expand...
Click to collapse
Without kernel source and either platform reference sources, or a good idea of them...you simply can't go making ROMs...
That's why you don't have any. If you really care about custom ROM support, I'm afraid you need to ensure you only buy from GPL compliant suppliers, who use chip sets with good support in open source projects.
Also the prevalence of the device is significant, and I'm yet to see any of those devices in real life...ever... And I'm a phone geek...
If there aren't many out there, the chance of a developer inclined to get it working on any ROM is lower, as they are less likely to even have one.

pulser_g2 said:
Without kernel source and either platform reference sources, or a good idea of them...you simply can't go making ROMs...
That's why you don't have any. If you really care about custom ROM support, I'm afraid you need to ensure you only buy from GPL compliant suppliers, who use chip sets with good support in open source projects.
Also the prevalence of the device is significant, and I'm yet to see any of those devices in real life...ever... And I'm a phone geek...
If there aren't many out there, the chance of a developer inclined to get it working on any ROM is lower, as they are less likely to even have one.
Click to expand...
Click to collapse
Yup. If you want a device that has good developer support, do research before buying it. If it's a company that flagrantly violates the GPL on a regular basis - why are you giving them your money?
Basically, I am not spending my volunteer spare time to support a company that is engaging in the practice of managing to steal that which is practically given to them for free.

But seems that Xiaomi will set the kernel source free soon.
At least they said that..
http://miuiandroid.com/2013/09/17/exclusive-xiaomi-mi-device-kernel-will-open-sourced/
They are great phones with a great software/hardware optimization,

Without kernel source and either platform reference sources, or a good idea of them...you simply can't go making ROMs...
That's why you don't have any. If you really care about custom ROM support, I'm afraid you need to ensure you only buy from GPL compliant suppliers, who use chip sets with good support in open source projects.
Also the prevalence of the device is significant, and I'm yet to see any of those devices in real life...ever... And I'm a phone geek...
If there aren't many out there, the chance of a developer inclined to get it working on any ROM is lower, as they are less likely to even have one.
Click to expand...
Click to collapse
I have an update for you ! Xiaomi releases their source code on 25th October .
Also there is one more hard working developer who without the Xiaomi's sources, has achieved what you are calling as unlikely & next to impossible... only problem for his ROM is camera driver.
He has a thread here in XDA also...
Fine if you all developers have already decided that you only develop or cook ROM for the well known models... it is ur wish. My wish i expressed & likewise you have also done your part.
And to all those who think Xiaomi is not a major player in Mobile industry & who have a false impression that it is just an another Chinese company... should do their research on their different models, their softwares , their track records & demand for their phone models & excellent hardware at best price. I agree they are not bigger than Google, but they are growing at a faster pace. I am not here to boast about that company, but i just shared my 3 months knowledge after buying Xiaomi Mi2S for the first time. Before that i was unaware of this company & had a same opinion like many of the people here have it....
Anyway... if Xiaomi releases for sure on 25th & my favorite developer releases his complete ROM.... pls delete this thread & i don't bother you guys also. It is almost perfect without camera.... thats why i am not using it for daily purpose.... may be you all should take a look at his work once.... AWESOME !
OK guys, dont think that i am trolling here or boasting here or something else.. i am just telling you the facts about my phone & the company which makes it....
Hoping to get a good & positive response from you all...

If Xiaomi makes major changes to their policy of rampant intellectual property theft, maybe things will change.
But in general, for a developer, our most limited resource is time. As a result, it's far better to work with a company that cooperates with the community and treats them with respect (Oppo, Sony, Google's Nexus devices) than one who constantly treats them like ****.
There's also the principle of the thing. I absolutely 100% refuse to work with the devices of any company that commits frequent GPL violations. Even if Xiaomi finally stops violating the GPL, they'll have to work hard for their long-standing track record of extremely poor behavior.
Same reason Samsungs are currently near the very bottom of my priority list, despite them having lots of users. Being lied to shamelessly on a regular basis (such as claiming that N8013 UEALGB was a "leak" and they didn't have to provide kernel source matching that build, despite it being preinstalled on every N8013 sold in the USA) leaves a lasting negative impression.

We should soon see a forum on here. The only reason it wasn't is because they want the source code and we should have that Oct 25 the can't wait.
Ive had my xiaomi mi2 for a little over a month and really like it. Can't wait til we see a forum Here.
Sent from my MI 2 using Tapatalk 4

And do you think once the kernel is released some dev could enable the LTE in Mi2S?
Seems that the processor Snapdragon 600 has LTE integrated.
But maybe is not that easy...

cregi said:
And do you think once the kernel is released some dev could enable the LTE in Mi2S?
Seems that the processor Snapdragon 600 has LTE integrated.
But maybe is not that easy...
Click to expand...
Click to collapse
Its not possible. Its not set up for it. Its a hardware change to get lte. The mi3 is 3g only so the earliest I see lte is mi3s.
Sent from my MI 2 using Tapatalk 4

A hardware change?? But the snapdragon 600 has not the LTE chip integrated? Samsung S4 has the same processor and has LTE...
I am not an expert, just wondering...

Yes, the S600 does have LTE built-in.
But if the device does not have LTE amplifier on board, you could enable/use LTE, but you'll get really poor network reception.
It's already been done on the Nexus 4, but was not really usable as-is. The lack of amplifier makes it a bad idea. It's only good for the proof-of-concept.

I understand now.. it's a pity... Thank you for the info.
Now the question is, would you buy a phone like Mi2S without LTE,?
now that the 4g is extending more and more, and thinking that the phone should last at least 2 years... I am not sure if i should buy it or not...

cregi said:
A hardware change?? But the snapdragon 600 has not the LTE chip integrated? Samsung S4 has the same processor and has LTE...
I am not an expert, just wondering...
Click to expand...
Click to collapse
http://www.anandtech.com/show/6541/the-state-of-qualcomms-modems-wtr1605-and-mdm9x25
Pay close attention to the RFFE block in the first diagram.
The Snapdragon 600 has NO integrated modem. The MDM9xxx does support LTE, IF paired with a WTR1605L - not every device has an L variant, and even if it does, band support requires the right components (PAs, filters) in the RFFE chain.

Yes, seems clear that Xiaomis Mi22s/a will never support LTE.
Waiting for Nexus 5 to choose my next phone...!

Ok guys, is there any point in maintaining this thread ?
when no dev is really interested in working on this one of the best hardware phone ?
I mean other than off topic discussion, nothing really in particular to ROM Dev for Mi2/2S going on in this thread especially.
It is upto the Moderator to decide what best can be done for the fate of this thread & hence Xiaomi Mi2/2S !!!
Thanks a lot for your precious time.
Take care.

OK guys so the Xiaomi kernel is already open sourced. That's a good new.
Will we see a forum here soon??

Hi
I think this might attract the attention of developers especially Entropy, Pulsar & other prominent persons...
waiting for their final word on the development of Omni ROM for Mi2....

Did Developers avoided this Device or work on custom roms on?

As we all know Mi a1 makes it difficult for custom rom building coz of A/B partitions ..
But i wanted to whether all the developers are in to make a lot of stable custom roms or they have moved away from the device.
I am not asking for customs roms now itself just wanted to know there is support and working on in the background or not.

I don't think they're avoiding it, it's just taking time to bring up the device tree.. I might dig into it a bit this weekend and try to bring up the device tree to 8.1, the problem is that even in 7.1.2 we don't have everything working. also, Xiaomi did a terrible job with the kernel, took them 4 months to release it and when they did they released an old 7.1.2 based kernel with the commits squashed into one commit over an older CAF tree

Developers are hampered by the lack of availability of source code that is yet to be released by xiaomi, (they have released the code, but not Oreo) otherwise we would have good ROMs by now

sooti said:
I don't think they're avoiding it, it's just taking time to bring up the device tree.. I might dig into it a bit this weekend and try to bring up the device tree to 8.1, the problem is that even in 7.1.2 we don't have everything working. also, Xiaomi did a terrible job with the kernel, took them 4 months to release it and when they did they released an old 7.1.2 based kernel with the commits squashed into one commit over an older CAF tree
Click to expand...
Click to collapse
Yes that ok .. Waiting is worth the wait . But can we expect stable custom roms within a month

Vibun said:
Yes that ok .. Waiting is worth the wait . But can we expect stable custom roms within a month
Click to expand...
Click to collapse
LineageOS is out. And I'll say yes.
Once LineageOS is perfectly stable you'll see many more ROMs.
No, developers are not purposely avoiding the device. On the contrary the day after the sources dropped we had 3 ROMs (broken nonetheless, only RIL worked) by three different devs.
As of right now, everyone has joined hands and are fixing LOS14.1
Even Francisco Franco said he's getting his kernel to this device, just be a bit patient.
Sent from my Mi A1 using XDA Labs

Ron1209 said:
LineageOS is out. And I'll say yes.
Once LineageOS is perfectly stable you'll see many more ROMs.
No, developers are not purposely avoiding the device. On the contrary the day after the sources dropped we had 3 ROMs (broken nonetheless, only RIL worked) by three different devs.
As of right now, everyone has joined hands and are fixing LOS14.1
Even Francisco Franco said he's getting his kernel to this device, just be a bit patient.
Sent from my Mi A1 using XDA Labs
Click to expand...
Click to collapse
Yes , I totally agree with u .. It's a new type of device (a/b partition ) it would take time .. just wanted to know that work is going around on it

Vibun said:
But can I expect stable custom roms within a month
Click to expand...
Click to collapse
Are you gonna pay them?

iMewo said:
Are you gonna pay them?
Click to expand...
Click to collapse
Dude !! Read my thread properly at the beginning. I said I am not asking for custom roms now ... Just wanted to know whether the device is under work or not ....

Vibun said:
Dude !! Read my thread properly at the beginning. I said I am not asking for custom roms now ... Just wanted to know whether the device is under work or not ....
Click to expand...
Click to collapse
Vibun said:
Yes that ok .. Waiting is worth the wait . But can we expect stable custom roms within a month
Click to expand...
Click to collapse
try give whoever it is an extra day or 2 maybe.just wait am sure were gonna see a lot of roms coming up

If your waiting for development then you have not done your research. Development devs dont buy from this oem. They even avoid it. The best you can hope for is some of the users porting the roms over but they will most likely be buggy as they always are with this oem.

zelendel said:
If your waiting for development then you have not done your research. Development devs dont buy from this oem. They even avoid it. The best you can hope for is some of the users porting the roms over but they will most likely be buggy as they always are with this oem.
Click to expand...
Click to collapse
Then what are your thoughts about Pixel Experience on Redmi Note 4? It has a very few bugs, and in fact gives better battery life than MIUI 9. That ROM isn't considered to be a port, right?

guy_infinity said:
Then what are your thoughts about Pixel Experience on Redmi Note 4? It has a very few bugs, and in fact gives better battery life than MIUI 9. That ROM isn't considered to be a port, right?
Click to expand...
Click to collapse
Any rom will give better batter battery life then miui. That is due to all the background syncing that it does in the back ground.
As for that rom. Any rom that brings over a pixel like rom is a port.
I wouldn't really know as this device isn't sold in my country nor does anyone I know even look twice at the oem.

Stop this A/B partitioning scheme BS. Of course, it does not make life easier for the developers but it certainly isn't the biggest obstacle.

gougous3 said:
Stop this A/B partitioning scheme BS. Of course, it does not make life easier for the developers but it certainly isn't the biggest obstacle.
Click to expand...
Click to collapse
Really. Ask the devs that got the pixel and after that won't touch a device with the partition setup. It makes things almost impossible to get working right. Me, I would just repatriation the device and remove the partition all together.

zelendel said:
Really. Ask the devs that got the pixel and after that won't touch a device with the partition setup. It makes things almost impossible to get working right. Me, I would just repatriation the device and remove the partition all together.
Click to expand...
Click to collapse
I'm not neglecting that but, in my opinion, it isn't that big of a deal anymore. I'm sure that even we if we didn't had it, things wouldn't be much better.

gougous3 said:
I'm not neglecting that but, in my opinion, it isn't that big of a deal anymore. I'm sure that even we if we didn't had it, things wouldn't be much better.
Click to expand...
Click to collapse
Well considering the oem you are right. But for normal devices those that don't have the partition are the more dev friendly. Just talk to some of the devs. Most have sworn off anything that uses the dual partition.

zelendel said:
Really. Ask the devs that got the pixel and after that won't touch a device with the partition setup. It makes things almost impossible to get working right. Me, I would just repatriation the device and remove the partition all together.
Click to expand...
Click to collapse
Absolutely true, it took months to see a stable release of TWRP for the Pixel. And there's still no official LOS as well.
However there are a few ROMs and more device with A/B are out like PH-1 and Moto Z2

For reals though, devs working on ROMs for this device, feel free to create/list your PayPal accounts for donations.
We ask so much of the devs it's only fair we buy them a drink/meal for all their hard work and persistence!
Sign me up for a donation

zelendel said:
If your waiting for development then you have not done your research. Development devs dont buy from this oem. They even avoid it. The best you can hope for is some of the users porting the roms over but they will most likely be buggy as they always are with this oem.
Click to expand...
Click to collapse
You are wrong.. mi phone's has great support on xda..look at rn3,4..and other mi phone threads

sooti said:
I don't think they're avoiding it, it's just taking time to bring up the device tree.. I might dig into it a bit this weekend and try to bring up the device tree to 8.1, the problem is that even in 7.1.2 we don't have everything working. also, Xiaomi did a terrible job with the kernel, took them 4 months to release it and when they did they released an old 7.1.2 based kernel with the commits squashed into one commit over an older CAF tree
Click to expand...
Click to collapse
eeeeeeeyyyyyyyyyy od israeli