Hey guys,
I'm a developer for the Optimus Black p970 and the creator of Aeroi rom. I am getting this phone soon and plan on developing it, any news from sources from Motorola? Have they released them yet?
The LTE model is known as Styx LTE. It's sources are available on GitHub:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/lollipop-5.0.2-release-styxlte
The LTE model uses an MSM8916, so use the msm8916_defconfig.
The 3G model is similar to the Moto G and previous Moto E. It uses a MSM8212 SoC. Motorola hasn't released a kernel for the 3G variant, but the previous Moto E's kernel sources might work. They haven't released Lollipop sources specifically for the old E either, but this kernel *might* work when built for msm8610_defconfig:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/lollipop—5.0.2-release
I'm working on a kernel for the LTE model, but I don't have anything that I consider worth releasing yet.
Should we be seeing better dev support for the LTE model soon?
Any news / expected availability of official CM/PAC for the LTE model?
Official CM doesn't mean better support.
I'm the maintainer of the moto E 2014 with @percy_g2.
Once I have a fully working CM for moto E 2015 build I'll push for getting the device official. The only change will be that the builds will be done by CM servers and you'll have the updates form CM. Also pushing changes to the repo will have to go through the grit system.
This is the same for PAC. PAC device tree and kernel can be easily done based on cm one.
I really hope that CM and PAC become official. Thanks for helping out.
Related
Hi all,
Been a while since I really looked into some of the OG development. But I have noticed there are seemingly kernel differences (which affect the ROM's support for xxx-kernel) in the forms of CAF, Gproj, etc.
I have a basic understanding of CAF being Qualcomm's development branch. From what I understand, AOSP doesn't use CAF updates. But CM does (at least, some stuff is integrated). So CM based ROMs are automatically CAF? Or is that up to the devs?
I do not really know what Gproj is, I think it is something for the Optimus G (Gproj = G Project?) variant development, but I may be wrong here.
I know the Mako is the name for the N4, but what are mako based kernels? CAF, Gproj? Something different, either or?
Anybody mind sorting out this information for me? Or pointing out a place where it already is spelled out? I did search Google and XDA but can't seem to find helpful information.
Thanks.
@bleached45
As far as i know ;
Gproj=CAF = Official and E975 sources
mako= Nexus 4 sources
All official roms uses Gproj E975 sources so only gproj kernel will work here.
As for example = CM 11 , mokee etc
All roms which uses makoo sources for rom uses ported mako kernel
I hope you got all your answers
ShoaibAhmed said:
@bleached45
As far as i know ;
Gproj=CAF = Official and E975 sources
mako= Nexus 4 sources
All official roms uses Gproj E975 sources so only gproj kernel will work here.
As for example = CM 11 , mokee etc
All roms which uses makoo sources for rom uses ported mako kernel
I hope you got all your answers
Click to expand...
Click to collapse
Then why do we see so many GEEB instead of GPROJ? My phone is Mako (based on info in recovery) but doesn't work at all with GEEB (mako), only GPROJ.
Guys,
I recently bought a Moto E(XT1022). Being the curious tinkerer that I am, I started poking around the forums here for custom ROMs. Found quite a lot of them. One of the devs released an unofficial port of Carbon ROM for moto e. Cybojenix recently released an early build of of Slimkat ROM based on Android KitKat4.4.4. He also said that he will release an unofficial build of CM11 for moto e. But the problem with all of these ROMs is that they work only on single sim variants of moto e. I tried PMing dhacker29 the official dev of CM11 for Moto G unified Build about help to get these working on dual sim variants but to no avail. Same with JackpotClavin. So are there any other devs willing to take this up for us. Also I read on the Moto G forums about flashing XT1032 firmware on XT1033 to get only one working sim and to use single sim supported Roms. Is it anyway possible to do this with Moto E and is it practicak . The main problems being faced here are SystemUI crashes, not working radio etc.. There must be some work around.Hope we find it real soon.
yeah me too waiting for that but many users flashed the us moto e rom and result was none of the sims are working hope so we get some help
I asked cybojenix about it. He said that dual sim sources are pretty messed up. That's the reason devs are hesitant in supporting them.
Sent from my XT1022
subham99 said:
I asked cybojenix about it. He said that dual sim sources are pretty messed up. That's the reason devs are hesitant in supporting them.
Sent from my XT1022
Click to expand...
Click to collapse
BTW @cybojenix just released a cm11 fix for dual-sim versions. Single-sim works for me.
:good:
Check cm11 thread for more info.
I saw this
http://www.cyanogenmod.org/blog/expanding-the-cm-device-family
What do they mean by R5Plus?
Edit. Now corrected for all R5 devices
Yep. There probably should be another thread for OPPO R5s as the specs are quiet different from regular R5.
I can see some action here ...for R7 devices
https://github.com/CyanogenMod?utf8=✓&query=oppo+
Well, any other news, like an ETA for this ? I am so interested, in a custom ROM, this one from OPPO is kinda boring.
R5S
I've been watching this thread since the announcement and am hoping there is someone taking on the R5/S. Color OS is really stable and Oppo did a great job on it but a few options would be nice.
Heya!
I just ordered a R5s for one simple reason... AOSP is coming!!!
http://www.gizchina.com/2015/10/23/...s-for-its-phones-plus-details-of-a-new-phone/
I smell something is coming from Paranoid
https://github.com/AOSPA-L/android_device_oppo_r5
PA
Paranoid.... my fav rom. No movement yet
Waiting very2 long but why this r5 not popular
Good news.
https://github.com/CyanogenMod/android_device_oppo_r5
Will this ROM work on Oppo R5s?
Nexus1688 said:
Will this ROM work on Oppo R5s?
Click to expand...
Click to collapse
I'm interested in that too.
I noticed that for the R7 and the R7Plus there are two different repositories. That could mean that a bit more work needs to be done to get CM working on the R5S.
To give a status update on that R5 repo: It essntially is nightly ready. All hardware that I'm aware of works just fine. There's only one caveat: It's based on the binary blobs of Oppo's Project Spectrum release, which means one has to flash Spectrum before installing CM. Problem: Spectrum includes a locked bootloader :-/ We're currently talking to Oppo and are trying to get an unlockable bootloader. Once we have hashed out that issue, nightlies will start.
marius.muntean said:
I'm interested in that too.
I noticed that for the R7 and the R7Plus there are two different repositories. That could mean that a bit more work needs to be done to get CM working on the R5S.
Click to expand...
Click to collapse
R7 and R7Plus are quite different, starting from the softkeys thta r7plus doesn't have, over the fact that they have vastly different partition sizes (which prevents 64 bit builds for r7) to the fact that there's no 5.1 stock ROM for the r7 (a big problem due to firmware issues). r5 and r5s are not that far apart. Chances are high that r5s will just work with the r5 repo (the Spectrum build is unified as well, after all), but I have no chance of testing that. I'd need a knowledgable r5s owner to verify that after the bootloader issue is resolved.
@maniac103
Thanks for the info and your efforts. I can assist you for testing only since I don't have any clue about development.?
I own oppo R5& F1
Sent from my F1f using XDA-Developers mobile app
@maniac103 I'd also like to offer my support with CM13 for the R5S.
First nightly
I just saw that there is a nightly for our R5 on cmxlog.com
Did anyone tried it? I'm really curious if it works on the R5S
June 2016
There is a nightly build on https://download.cyanogenmod.org/?device=r5 for international oppo R5/R5s
I'm wondering if the similarities between Surnia and Osprey will allow us to benefit from the work that Motorola is doing to bring Marshmallow to the Moto G 2015? It looks like a Marshmallow soak test was just started for the Moto G 2015 (Droid Life 11/4/2015), and it is rumored to have LTE band 12 support enabled, which would imply that VoLTE is also supported. I think it's very likely that in order for VoLTE to work it would need specific support for it in the baseband software. I have read that there are other SD410 phones that support VoLTE, so at this point it just seems like we have an issue where decent hardware is being held back by poor software from Motorola. Since it seems like Motorola has decided to abandon us, hopefully the XDA community will be able to step up and fill in some of these gaps in functionality. Here are a few questions that I have about the similarities between these two devices.
Are Surnia and Osprey similar enough that Surnia can run Osprey baseband software? Has anybody heard of any attempts to flash an Osprey baseband on Surnia? Would this be limited only because of code signing issues and not hardware limitations?
Surnia and Osprey use very similar kernels, so would this also make it easier to port anything related to VoLTE from the stock Osprey kernel back to Surnia?
When the stock Marshmallow update for Osprey is released would the similarities between the two phones make it more likely that somebody would be able to port it to Surnia?
Any thoughts on this?
I saw ROMs for Osprey that are based on Surnia's device tree, so why not? I don't think flashing a Osprey ROM on surnia will work, but what about flashing it with a Surnia kernel? I'll try it, can simply solve a bootloop!
Tried that, caused bootloop, but while downloading a backup ROM, I suddenly saw this:
It looks like Surnia and Osprey probably have different sized /system partitions. I tried flashing this http://forum.xda-developers.com/2015-moto-g/orig-development/caf-6-0-osprey-t3229378 and when it was verifying /system it gave an error message. I next flashed the squid2 kernel and it just bootlooped.
I know Sony has a very advanced open source support for their devices and an united core to easily make updates for every model (also the older models) but why the CM development is so difficult?
The only one Sony phone officially supported from CM13 is the Xperia M...
In the Sony's site instead I can find updated AOSP rom for near every model. With an official AOSP support is should be easier to develop CM roms, why it isn't?
For example in the Cyanogenmod site I can find a lot of Samsung (bad opensource support from Samsung!) and just one device Sony officially supported by CM13...
I don't want to troll, I am just searching for an alternative to Nexus for my next device with the best AOSP/CM support and compatibility possible.
Many thanks!
Axl