Database Info

CyanogenMod - Moto G

What are the chances?

I waiting for too +1

It will come.
Sent from my XT1032 using xda app-developers app

I hope it will be officially supported!
Inviato dal mio Xperia U utilizzando Tapatalk

Flip a coin I'd say, not the most powerful device and not a nexus device either so I'm not sure but hopefully
Sent from my GT-N7000 using XDA Premium 4 mobile app

considering the price specs and unlocked bootloader it will almost definitely be supported
Sent from my HUAWEI U8950N-51 using Tapatalk

I hope CM's cozying up with Chinese manufacturers doesn't affect their motivation to support other brands. There's now business involved too.
On the other hand the latest Moto handsets are the closest thing to a Nexus without actually being one. Moto/Google's level of openness and the code they release should be telling. An interesting issue is also support for the dual-sim edition. I understand CM has been working towards it behind the scenes and shortly the first dual-sim device by Moto/Google themselves will be on sale. Will they or won't they release the code for dual-sim support for incorporation in parallel Android projects too?

myanogencod said:
I hope CM's cozying up with Chinese manufacturers doesn't affect their motivation to support other brands. There's now business involved too.
On the other hand the latest Moto handsets are the closest thing to a Nexus without actually being one. Moto/Google's level of openness and the code they release should be telling. An interesting issue is also support for the dual-sim edition. I understand CM has been working towards it behind the scenes and shortly the first dual-sim device by Moto/Google themselves will be on sale. Will they or won't they release the code for dual-sim support for incorporation in parallel Android projects too?
Click to expand...
Click to collapse
The model that probably will have the support of CyanogenMod will be the A 8GB chip, 2 chips but who knows Also gain support, This will depend on the developers. What remains is to wait
Sent from my GT-I9070 using xda app-developers app

myanogencod said:
I hope CM's cozying up with Chinese manufacturers doesn't affect their motivation to support other brands. There's now business involved too.
On the other hand the latest Moto handsets are the closest thing to a Nexus without actually being one. Moto/Google's level of openness and the code they release should be telling. An interesting issue is also support for the dual-sim edition. I understand CM has been working towards it behind the scenes and shortly the first dual-sim device by Moto/Google themselves will be on sale. Will they or won't they release the code for dual-sim support for incorporation in parallel Android projects too?
Click to expand...
Click to collapse
Cyanogen is still community based.... If there will be an developer who sync the cm repo with the device and fixes the bugs and offical submit it to cm there will be "official" cm support. Check out the CM Forum and the Rules to geht offical cm support then you can answer this question your own.
Gesendet von meinem Galaxy Nexus mit Tapatalk

arison1988 said:
Cyanogen is still community based.... If there will be an developer who sync the cm repo with the device and fixes the bugs and offical submit it to cm there will be "official" cm support. Check out the CM Forum and the Rules to geht offical cm support then you can answer this question your own.
Click to expand...
Click to collapse
What part of my message were you unhappy about again?
I can't see how The Rules would have anything to do with what I was wondering about.
Tschüss/Cheers

+1
need it!

me too

I'm confident the Moto G will be popular and there will be a wide variety of ROMs available, both stock and AOSP based should there be much difference (?).
I think the variety of ROMs will be more important than the presence or not of any specific ROM.
The $200 or less price point for the features has resulted in a LOT of online admiration by the sorts of people who root, ROM & customize.
Just convince ROM devs that it's a wonderful phone and the process will begin.
For those who prefer expensive flagships for their personal use, the Moto G is great for backup (after failed flashes etc, LOL) and great for the kids, grandma, and the rest of the family.

Now that it's been rooted (quite easily), it might not take too long till we see some custom roms popping aroud.

i don't understand why this device isn't more popular..
In the short time i had i've been very amazed at the pricepoint/performance, and on top of that the device is a google device with unlockable bootloader and android 4.4 promised, so i would've thought the developers would jump on board. Hopefully more developers will start working on this device :fingers-crossed:

Well, give it some time, this device is rather new, I am sure it will be popular, it's the cheapest quad-core around
Sent from my XT1032 using Tapatalk

First of all Motorola has to release the Blobs and Sources, which may happens next Week with Luck.

I've read somewhere that it's gonna get an update in January... maybe it's gonna be where everything will start.

Kameo said:
I've read somewhere that it's gonna get an update in January... maybe it's gonna be where everything will start.
Click to expand...
Click to collapse
It has already started.

theoneofgod said:
It has already started.
Click to expand...
Click to collapse
Source?

[EXYNOS7] [7420] Sources and Cyanogenmod builds

It's been a month plus and there isn't any signs of cyanogenmod development going on? what the big deal? No sources? or are there sources and devs can't figure out the complications? like it happened with the exynos 4 platform. I had a Galaxy S3 and there was reasonable support from the devs. Looks like the devs are just frustrated with the Exynos source.

Siddheshpatil said:
It's been a month plus and there isn't any signs of cyanogenmod development going on? what the big deal? No sources? or are there sources and devs can't figure out the complications? like it happened with the exynos 4 platform. I had a Galaxy S3 and there was reasonable support from the devs. Looks like the devs are just frustrated with the Exynos source.
Click to expand...
Click to collapse
I'm waiting for this myself.. hope they release soon because in all phones I had CM was running.

Didn't even care. I have sd801 on my klte return to stock rom after join cm bugwagon since it out till tw lp comes out. My n9505, and previous phone also got the same fate. Yeah, yesteryear is the last cm I used. My 920f is the first phone that I didn't even root. This is my opinion. Ignore it if hurt you. ?
Sent from my SM-G900F

I haven't been paying attention for a while, but last I knew, exynos sources are closed, as they are proprietary to Samsung. This is why there was a bunch of discussion prior to release of the device that CM would likely be very late to the party, if it shows up at all, because there would be a lot of reverse engineering required. This was also expected to make CM run comparatively poorly vs. Stock based ROMs.
Not sure if anything has changed in this regard in the last 6 weeks..

Ave666 said:
Didn't even care. I have sd801 on my klte return to stock rom after join cm bugwagon since it out till tw lp comes out. My n9505, and previous phone also got the same fate. Yeah, yesteryear is the last cm I used. My 920f is the first phone that I didn't even root. This is my opinion. Ignore it if hurt you. ?
Sent from my SM-G900F
Click to expand...
Click to collapse
Exynos is a very "proprietory" platform, the sources are most likely not made available and if they are , its not maintained like Qualcomm does. My point being, sooner or later by december this year samsung will out hints for the next flagship, and thus our updates will be killed. My s3 never got a taste of kitkat or lollipop officially. The sooner the source is available, the better it is. Devs can start working on it.

dandrumheller said:
I haven't been paying attention for a while, but last I knew, exynos sources are closed, as they are proprietary to Samsung. This is why there was a bunch of discussion prior to release of the device that CM would likely be very late to the party, if it shows up at all, because there would be a lot of reverse engineering required. This was also expected to make CM run comparatively poorly vs. Stock based ROMs.
Not sure if anything has changed in this regard in the last 6 weeks..
Click to expand...
Click to collapse
Even if it is proprietary they do release source. They did release code for Exynos 5. ( galaxy alpha is getting some cm treatment). The s3 had so many roms, yes the reverse engineering Codeworkx, Andrew and gokhanmoral had to do was messed up but amazing.

Popular question:
http://forum.xda-developers.com/galaxy-s6/help/curious-rom-development-t3108196
http://forum.xda-developers.com/galaxy-s6/help/question-exynos-rom-development-t3093581
http://forum.xda-developers.com/galaxy-s6/help/dev-s6-t3075461
BTW, per the sticky in the General section, questions should be posted there.

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-G920 we do have the source

Siddheshpatil said:
Even if it is proprietary they do release source. They did release code for Exynos 5. ( galaxy alpha is getting some cm treatment). The s3 had so many roms, yes the reverse engineering Codeworkx, Andrew and gokhanmoral had to do was messed up but amazing.
Click to expand...
Click to collapse
Thanks for this info. I've been very much out of the Samsung scene for a couple years - last Sammy device I had was an SGS2. Good to know there is hope for decent CM support. It's cool to see some of the same awesome devs in this community that i remember from the S2.

dandrumheller said:
Thanks for this info. I've been very much out of the Samsung scene for a couple years - last Sammy device I had was an SGS2. Good to know there is hope for decent CM support. It's cool to see some of the same awesome devs in this community that i remember from the S2.
Click to expand...
Click to collapse
The kind of effort andrew and codeworkx put to fix the emmc bug in s2 is amazing.. Hope something like that doesn't show up on the s6..

Snapdragon 820 = AOSP?

Quite simply, from what I'm reading about S6, and Exynos, the main reason for lack of major AOSP ROMS (CM13 has been finally ported), is the idea that Exynos is not documented so coding for it is difficult.
Knowing now that Snapdragon 820 is a Qualcom chip, which apparently is the most common SoC used for phones, should we expect to see a lot of AOSP based ROMs?
I am very used to Vanilla Android, and I don't think I could deal with TouchWiz, I like CM Theme Engine, and RRO Layers, so the big reason for my question is based on the hope that the probability of non-TouchWiz ROMs is high.
Also, I had a moto x 2014 and I've come to fall in love with AMOLED, and would like to stick to a small form factor 5 to 5.1 inches, combined with healthy ROM community, I'm kind of hoping S7 with SD820 might be the phone for me.
Please don't say "If you like Stock don't buy a Samsung", I get it, but it looks like maybe that stigma might not hold up soon if the ROM cookers are supportive.
Thanks!

I'm not sure on the international versions, but I know most carrier versions of the Note 4, S6, Note 5, etc. never got unlocked bootloaders in the first place, let alone custom ROMs. Knox is killer.

geoff5093 said:
I'm not sure on the international versions, but I know most carrier versions of the Note 4, S6, Note 5, etc. never got unlocked bootloaders in the first place, let alone custom ROMs. Knox is killer.
Click to expand...
Click to collapse
Tmobile variants of all the phones you listed are bootloader unlocked. Knox has never stopped anything.
@Shemploo yes more than likely AOSP roms will be available for the snapdragons. I'm betting even exynos variants will get it although probably a little later.

I don't do carrier contracts so I'd most likely look/hope for a developer/pure edition of the S7.
The Edge does not really interest me, unless they figured out some cool things to do with the curved screen that are actually useful.
I'd much rather have a fingerprint reader, and front sensors like the Moto's, I love waving my hand in front of the display to have it wake up and tell me the time.
People go... you are a Jedi!?

Airtioteclint said:
Tmobile variants of all the phones you listed are bootloader unlocked. Knox has never stopped anything.
@Shemploo yes more than likely AOSP roms will be available for the snapdragons. I'm betting even exynos variants will get it although probably a little later.
Click to expand...
Click to collapse
I know AT&T and Verizon are different stories, good to know it works for T-Mobile though.

Most if not all Sprint phones have unlocked bootloaders too. At least last time I checked!

Yes. However you got something wrong there. The reason why Qualcomm has all the fancy AOSP based ROMs (I say fancy because most people consider non aosp roms boring) is because of this. This is where QCOM releases their soruce code for the platforms. This makes fixing easier because you actually have the code. However exynos and all the other ones don't give a crap about the small percentage of their users that actually flash roms etc. Infact, they only want money. And guess what? ROMs = Longer device lifespan. That's why they don't release it. Thankfully enough there are some geniuses here on XDA that still are able to do the job for exynos! However, QCOM has allot better optimization with CM in terms of performance than with any other chipset. I live in the EU, which means Exynos. After already owning 2 exynos devices, I'm tired of the work that has to be done for them. I was lucky enough that both of them had Exynos chipsets that already had allot of devs mainly from other devices which made building possible for me.

@CTXz I suppose the closest thing to AOSP on Samsung devices QCom, or Exynos, is going to be Cyanogen right?
Would I be right to assume Cyanogen would be the first (possibly only) AOSP to build for Samsung?
In other words, would/could anyone build true AOSP based on Google's source code?
I understand both are considered AOSP, I'm asking cause from general experience with ROMs, when ROM is built on CM, they usually just build in the CM Theme Manager, and only the ROMs based on Google's code do things like RRO Layer support.

Shemploo said:
@CTXz I suppose the closest thing to AOSP on Samsung devices QCom, or Exynos, is going to be Cyanogen right?
Would I be right to assume Cyanogen would be the first (possibly only) AOSP to build for Samsung?
In other words, would/could anyone build true AOSP based on Google's source code?
I understand both are considered AOSP, I'm asking cause from general experience with ROMs, when ROM is built on CM, they usually just build in the CM Theme Manager, and only the ROMs based on Google's code do things like RRO Layer support.
Click to expand...
Click to collapse
Ofcourse, infact that is up to the devs, however CyanogenMod is usually recommended over pure AOSP due it's great documentation, common updates, it's optimizations and tweaks above stock AOSP. It's also the simplest to get the hands on.
EDIT: It's also important to know that CM isn't just AOSP with a few apps. While CM is based on AOSP, it still has it's own community and is still a different ROM than AOSP mainly when it comes to the internal changes.

..

CTXz said:
Ofcourse, infact that is up to the devs, however CyanogenMod is usually recommended over pure AOSP due it's great documentation, common updates, it's optimizations and tweaks above stock AOSP. It's also the simplest to get the hands on.
EDIT: It's also important to know that CM isn't just AOSP with a few apps. While CM is based on AOSP, it still has it's own community and is still a different ROM than AOSP mainly when it comes to the internal changes.
Click to expand...
Click to collapse
After Cm started trying to push that you make an acct with them I will never use CM again. I know that people say Inc has no relation to... whatever non-Inc calls themselves, but I no longer trust any of them and would rather buy a Windows phone or iPhone before I run them on any phone of mine again.

knitler said:
After Cm started trying to push that you make an acct with them I will never use CM again. I know that people say Inc has no relation to... whatever non-Inc calls themselves, but I no longer trust any of them and would rather buy a Windows phone or iPhone before I run them on any phone of mine again.
Click to expand...
Click to collapse
Um... CM =/= Cyanogen Inc
CM is a completely separate group that is not affected in any way. It's like XDA and GOogle. XDA is for developing and still both work on android. I know some people in the official CM group, all of them very friendly and none of it is affected by Cyanogen Inc. You're making yourself lies that aren't true. It's like blaming the entire CyanogenMod team because one dev for a specific device didn't fix the issue yet.

If CM is the main like, why not just get a Nexus and get it over with? You'll get CM right away.
Sent from my VIVO XL using Tapatalk

barondebxl said:
If CM is the main like, why not just get a Nexus and get it over with? You'll get CM right away.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
Because some people don't want a nexus

CTXz said:
Because some people don't want a nexus
Click to expand...
Click to collapse
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk

barondebxl said:
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
And cripple it with bad, forever-beta, with half the functionally misssing software.

Sure hope we get aosp!
Sent from my SM-N920T using Tapatalk

I thought it was primarily due to the 64 bit architecture that was the hold up with aosp on the s6. Buy I could be wrong. Been a while since I went looking.

barondebxl said:
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
That is a good argument, however many people DO actually go for the look/hardware and with that said. Afterall xda wouldn't be this big if you could use the word nexus for all excuses, right ?

CTXz said:
That is a good argument, however many people DO actually go for the look/hardware and with that said. Afterall xda wouldn't be this big if you could use the word nexus for all excuses, right ?
Click to expand...
Click to collapse
Might want to get used to it as sooner or later it will only be nexus devices that are worked on.
Also what's the point of getting the device fore the hardware when aosp doesn't take advantage of the hardware? Aosp drivers don't compare to the stock ones.

When, Why?

Hello
For over one year we have the S6 . We still expect that developers lay us an AOSP ROM. CyanogenMod but we dodge ! And AOKP ? It's over?
Have you any news? Thank you in advance!
I think I'll leave Galaxy for Nexus !

Why bother for a cm full of bugs..just use a tw rom debloated and with a custom launcher.
S6 wont get any stable cm even in a few years. So just move on

just change title mate, it's against the rules do something like this.
no opensource = no cyano. it's like trying to build a rom without codes.

slawl said:
Hello
For over one year we have the S6 . We still expect that developers lay us an AOSP ROM. CyanogenMod but we dodge ! And AOKP ? It's over?
Have you any news? Thank you in advance!
I think I'll leave Galaxy for Nexus !
Click to expand...
Click to collapse
Any device utilizing a Exyenos CPU is always a no-go for CM and never-ever good for any bug-free modding. Always & forever. I believe any rom Dev would tell you this.
Samsung's hardware imo is superior to Nexus, say what you will, but Samsung knows how to produce a quality handset. Too bad about the mod-ability! But hey, as you pointed out, there's always Nexus

The exynos chipset is always difficult to get a cyanogen build for, mainly cos Samsung never release sources which makes development very hard.
Sent from my SM-G920F using XDA-Developers mobile app

thundastruck said:
Any device utilizing a Exyenos CPU is always a no-go for CM and never-ever good for any bug-free modding. Always & forever. I believe any rom Dev would tell you this.
Samsung's hardware imo is superior to Nexus, say what you will, but Samsung knows how to produce a quality handset. Too bad about the mod-ability! But hey, as you pointed out, there's always Nexus
Click to expand...
Click to collapse
Except for the Nexus 10 which has an Exynos aswell.
Officially it has 5.1.1 but unofficial cm13, maybe Android N in the future.

XxM4tzexX said:
Except for the Nexus 10 which has an Exynos aswell.
Officially it has 5.1.1 but unofficial cm13, maybe Android N in the future.
Click to expand...
Click to collapse
I never argued Exyenos can't/won't run/didn't have decent builds of CM; simply said it's a no-go meaning the end-user experience is inferior to devices that run it well e.g. devices with Qualcomm's CPU's.
Devices with Qualcomm/Snapdragon CPU's are usually the ones to go for. Look at the thread and compare rom's/cm of i9500 vs i9505 - BIG difference! :highfive:

Why isn't there any development going on for the Xperia 5?

The phone is about 6 months old now and we barely have root available. Are developers just not interested in the Xperia 5? I was really hoping for someone to come around and fix the fingerprint scanner issue and maybe release an unofficial LineageOS. What are your thoughts on this?

I believe it's due to a lack of TWRP and root on Android 10, especially on Sony devices. Could also be that devs are on older devices and not on the 1 or 5.

fcb13 said:
I believe it's due to a lack of TWRP and root on Android 10, especially on Sony devices. Could also be that devs are on older devices and not on the 1 or 5.
Click to expand...
Click to collapse
To be honest, this is My first Device ever which isn't that much bloated with 3rd Party Apps from a OEM and other Stuff. Pretty clean Google like with smart additions. Good perfroming and with awesome Battery Life. Sound is awesome compared to previous SONY Devices over the Speakers and Root isn't a problem since You can edit Your Kernel Image with Magisk App even without TWRP. So at the end aren't there any efforts anymore to get TWRP (There was one on the Xperia 1 Forums that did not work right). Think that could be a thing once the new Xperia 1 (2) or even the next comes really out with new Software Gimmicks to port over or once we get outdated with official Updates from SONY (GSI/AOSP Development). I don't see a reason besides a Magisk Module with small additions and tweaks to make a Stock ROM for example atm. and to be honest again. Someone de-motivated me a bit some time ago with developing for SONY Devices. But who knows, maybe am i at least starting something again for the 1 and 5 Series (Don't know anything about a new 5 Model yet) if i get some free time again. Just use My Xperia 5 as daily atm. with a Module Prototype ported from My last Project...
Best Regards,
Miu
Ed. https://github.com/Miustone/XPIXELERIA

I hope development picks up soon. Its a brilliant phone. Would love to have LineageOS on it.

Params7 said:
I hope development picks up soon. Its a brilliant phone. Would love to have LineageOS on it.
Click to expand...
Click to collapse
I have my doubts because the last Sony phones that had decent development were the XZ1 and XZ1C. XZ2, XZ3, and 1 had little to no development.