Database Users

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

CM port

Hi everyone,
I have juste created a thread asking for the official port of CM on this device (I can't post the link because I'm new....), section device requests.
Be free to comment the post (even a +1) , I am sure you can find the link we google, and we have to prey that they will take a look at it
Kisses

Won't happen until Alcatel releases the source code and given that the phone was just released to canada as recently as June 30th you can expect to wait a couple of months for that.

Just want I want a bug filled rom that gets rid of one problem and another pops up. I just love when we all use cm and the Bluetooth crashes all the time, disconnects, and overall bearly works. I love when the wifi disconnects and you have to restart the phone just to get it to work.
Sorry I'll stick to the stock rom where everything works perfectly fine.

Wont be any cm roms until we get twrp first. Im shocked more devs dont own this device.

fix-this! said:
Wont be any cm roms until we get twrp first. Im shocked more devs dont own this device.
Click to expand...
Click to collapse
It hasn't even been out 2 months yet. It's an off name most are not familiar with and alcatel's first true shot at an enterprise/flagship level device. It has threads on slickdeals.net advertising it's low price...it will eventually get support by either the source being released or a new exploit being found that can be used to provide temp or perm root...once someone has root they can pull the recovery and boot partitions and development can begin.
It's unrealistic to expect developer's to be jumping all over this phone so soon. I'd never even heard of it till I was looking to buy a zen phone 2 and found so many articles comparing it to the idol 3.

Woukd be nice to have it or either dirty unicorns crdroid or omnirom ^^ now that we have a working TWRP

gecko702 said:
Woukd be nice to have it or either dirty unicorns crdroid or omnirom ^^ now that we have a working TWRP
Click to expand...
Click to collapse
it really would xD. Although, I feel like Id miss the stock rom. Even though it is quite slow. TWRP works amazingly!

capeorigins said:
it really would xD. Although, I feel like Id miss the stock rom. Even though it is quite slow. TWRP works amazingly!
Click to expand...
Click to collapse
yeah id miss it too but meh lol but theres the dolby atmos app that has been ported from a lenovo ROM that should work with our speakers and also there can be a way to port the colorOS camera app from oppo phones those can take up to 50mp shots because they use sony sensors even on the one plus one has been achieved an yet it has the same sony sensor also hopefully xposed framework could work on us because of the adaway for youtube ^^

Well if someone's working on a CM port I'd be interested in helping to test it.

Thatd be nice id help too for testing purposes im a very heavy user and this phone has been keeping up with me lately

I'll throw my vote in for a cm port. as well as another tester if needed. Dont have tons of experience, but I'll be happy to help where I can.

well im pretty sure theres going to be a bounty thread for it or any other rom ^^

hi guys,
i just ordered this phone and soon within this month hopefuly will land in my hands in india.
my question is cant we use sources of other SD 615 phones like MI4I, YUreka and TCL M3G to develop rom for our device/ or cant we use their roms with our stock kernel ???
as TCL M3G is already having cm 12.1 and MIUI V6 and several other roms on movilesdualsim forum

yash_rathore25 said:
hi guys,
i just ordered this phone and soon within this month hopefuly will land in my hands in india.
my question is cant we use sources of other SD 615 phones like MI4I, YUreka and TCL M3G to develop rom for our device/ or cant we use their roms with our stock kernel ???
as TCL M3G is already having cm 12.1 and MIUI V6 and several other roms on movilesdualsim forum
Click to expand...
Click to collapse
Can you use the computer chip from a v8 chevy in a v8 ford? The software has to match to the hardware. How is the software going to control the screen when they have different digitizers? Different sound cards. Just as with your pc the drivers have to match the hardware.

Just pray to the phone Gods they roll out a 5.1 update and release it...

neilownz said:
Just pray to the phone Gods they roll out a 5.1 update and release it...
Click to expand...
Click to collapse
hahaha praying here too but we need their source code so that someone can work on a ROM for us

One of the CM maintainers, contacted me here on a PM today and requested files from the device. The work on the CM port will be started probably the next week. I will not disclose his ID for now in order to save him from possible questions on PMs. Probably CyanogenMod soon will be available for the Idol ... I just spread the news.

Cool, looking forward to it!

petrov.0 said:
One of the CM maintainers, contacted me here on a PM today and requested files from the device. The work on the CM port will be started probably the next week. I will not disclose his ID for now in order to save him from possible questions on PMs. Probably CyanogenMod soon will be available for the Idol ... I just spread the news.
Click to expand...
Click to collapse
Thanks for the update! It's been quiet for a little bit regarding a CM port. Good to see it's still WIP.

While I look forward to having trees to build with, I find it kinda funny that they asked for files when a couple of them have the device already. Unless the files are from a different version?
Sent from my 6045I using XDA Premium HD app

Sony releases concept software kernel sources

available here: http://developer.sonymobile.com/dow...hives/open-source-archive-for-mob30m-z1-3636/

Still doesn't do us much good as long as they're keeping the proprietary features under lock and key. For as much as Sony tries to "support developers and open source software," giving us a neutered ROM doesn't get us much farther than we already are.

hikihibiki said:
Still doesn't do us much good as long as they're keeping the proprietary features under lock and key. For as much as Sony tries to "support developers and open source software," giving us a neutered ROM doesn't get us much farther than we already are.
Click to expand...
Click to collapse
they do that so you will be forced to buy their next flagship phone that includes the next android upgrade, hence the z3c not getting nougat. It's plain to see....otherwise a lot of users wouldn't buy the same exact phone with minimal hardware upgrades every few months they release a new phone. I'm just fine with MM here and i will prob keep my z3c for the next few years unless the horrible build quality catches up to me.

Fictional Reality said:
they do that so you will be forced to buy their next flagship phone that includes the next android upgrade, hence the z3c not getting nougat. It's plain to see....otherwise a lot of users wouldn't buy the same exact phone with minimal hardware upgrades every few months they release a new phone. I'm just fine with MM here and i will prob keep my z3c for the next few years unless the horrible build quality catches up to me.
Click to expand...
Click to collapse
Probably the Z3 and the Z3C won't get Nougat is because of data encryption and because Qualcomm stopped making Adreno 330 drivers there won't be Vulkan support,and I am not sure would it be easy to make Nougat anyways without GPU drivers

With this sources, we can make a cleaner rom (like SLiMM), near AOSP and with great stability. I will take a look at the code. I invite @Wajk, @Gustavo RD78 and @Marília de Oliveira to look at it too.
The kernel source can be downloaded here
The rom itself can be found here

juliopw said:
With this sources, we can make a cleaner rom (like SLiMM), near AOSP and with great stability. I will take a look at the code. I invite @Wajk, @Gustavo RD78 and @Marília de Oliveira to look at it too.
The kernel source can be downloaded here
The rom itself can be found here
Click to expand...
Click to collapse
Ehh seems like a more out of date kernel when compared with the .291 source, which is almost fully up to date with branch LA.BF.1.1.3_rb1.13 (latest supported codeaurora branch for msm8974) whilst Concept is quite behind on many newer commits.
Other notable differences are like commits from AOSP such as partial resume support already included, and seccomp used instead of Sony RIC (obviously, being based on AOSP).

@tomascus can these features be ported to this kernel or is it too much trouble?

juliopw said:
@tomascus can these features be ported to this kernel or is it too much trouble?
Click to expand...
Click to collapse
Yeah just simple cherry picking:silly:

thanks

They posted the code of the 3657 build
http://developer.sonymobile.com/downloads/all-downloads/open-source-archive-for-mob31e-z1-3657/

Why are there no Android 8.0 Custom ROMs out yet?

If I remember correctly, Android Nougat Custom ROMs were out withing weeks of official release of it.
I'd like to know why there is delay for Android Oreo

TJ_bab said:
If I remember correctly, Android Nougat Custom ROMs were out withing weeks of official release of it.
I'd like to know why there is delay for Android Oreo
Click to expand...
Click to collapse
There are some out. They are just in alpha testing mainly. Although there are some daily driver ready ones out. The delay is likely that I think not all the sources and device trees for updated to the AOSP project as quick and all in one go as nougat. I built a rom a couple of days ago and had some issues but after an AOSP update I was able to build an Oreo ROM fine with no issues.

TJ_bab said:
If I remember correctly, Android Nougat Custom ROMs were out withing weeks of official release of it.
I'd like to know why there is delay for Android Oreo
Click to expand...
Click to collapse
I just posted this elsewhere lol when a new version of Android drops, custom roms take quite awhile to update.
If you follow specific dev teams, you'll notice they take their time to release after new Android updates. Others, have fewer features or use AOSP, and they'll be quicker to update. Dev teams are testing features, seeing what code is deprecated, what features can be dropped due to low use, etc. A minimum of two to three month wait is normal for some roms to update. If you think they are taking awhile, help them out. Otherwise, enjoy the wait cuz this is a hobby for everyone.
Sent from my Nexus 5X using Tapatalk

DEVILOPS 007 said:
There are some out. They are just in alpha testing mainly. Although there are some daily driver ready ones out. The delay is likely that I think not all the sources and device trees for updated to the AOSP project as quick and all in one go as nougat. I built a rom a couple of days ago and had some issues but after an AOSP update I was able to build an Oreo ROM fine with no issues.
Click to expand...
Click to collapse
SlimSnoopOS said:
I just posted this elsewhere lol when a new version of Android drops, custom roms take quite awhile to update.
If you follow specific dev teams, you'll notice they take their time to release after new Android updates. Others, have fewer features or use AOSP, and they'll be quicker to update. Dev teams are testing features, seeing what code is deprecated, what features can be dropped due to low use, etc. A minimum of two to three month wait is normal for some roms to update. If you think they are taking awhile, help them out. Otherwise, enjoy the wait cuz this is a hobby for everyone.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
thank you both. I guess I'll have to wait more patiently like I've been waiting for xposed
I was particularly looking for something similar to S-AOSP as that won't be continued to Oreo

TJ_bab said:
thank you both. I guess I'll have to wait more patiently like I've been waiting for xposed
I was particularly looking for something similar to S-AOSP as that won't be continued to Oreo
Click to expand...
Click to collapse
Superxe ROM sounds good for you.

Stay tuned for Nitrogen'O'! They have a nice working beta ROM if you can't wait....

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