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
Related
Just one caveat: I have done searches (read: multiple).
How in the world does CyanogenMod get to all of the supported devices? All of a sudden once CM9 is released, for phones/tablets moving from CM7 to 9, does it go out to all devices or what? Does it need to get ported from the source for each and every individual device? In general, how is CM updated and how does it get out to the officially supported phones/tablets?
Cyanogenmod ROMs do indeed have to be ported to each individual device and maintained. Once a device receives official support from the Cyanogenmod team, daily changes made to the AOSP source code (tweaks and bugfixes by the various contributing devs) are automatically compiled by a "buildbot" and released at the end of each day (thus these builds are called "nightlies"). These nightly updates are then made available for download through the Cyanogenmod website and through ROM Manager. Once code updates reach a certain plateau, a "final release"-worthy balance of features and stability, the build is released separately as a "stable" build (such as CM7.1), though you can still download it from the website or from ROM Manager just as with the nightlies. CM9 will eventually receive the same treatment and be released in the form of nightlies and stable builds.
Further (highly recommended) reading can be found here: http://www.cyanogenmod.com/blog/the-current-and-future-state-of-cyanogenmod-nightlies
Has anyone seen John Connor?
so the nightlies don't have to be ported, but every major revision does?
hugabu said:
so the nightlies don't have to be ported, but every major revision does?
Click to expand...
Click to collapse
No.
"Porting" is just a word used for the process of making the rom work on any certain device.
So to answer your question, once the work of porting CM to the certain device is done, that port is used as the base for both the stable and nightly builds.
Look at the analogy of when a new phone comes out, case manufacturers create a mold to use to make their cases fit the certain phone, and that mold is used to make all kinds of cases. Same concept
Hi XDA!
I'm very confused about the newest happenings around AOSP but let me start a bit further.
As for my understanding is is essential to have literally all code, drivers and so on open source to build proper roms. Because of this all nexus devices are the perfect platform because all needed sources are made available by google throw AOSP.
BUT as I know: this isn't totally true because for example some of the drivers for the nexus4 are not available as open source.
With all this said I don't understand what it means if sony releases sources for their "Sony Xperia"-devices, or samsung with the S4.
Does that mean, that they become as suitable as the nexus-devices for creating custom roms?
Or are there still differences between a Sony Xperia and a N4??
In short: NEXUS = AOSP and AOSP = NEXUS ???????
Thanks for enlightening me
Hi,
Is CyanogenMod for Z3 tablet device using Sony's interface/widgets just with CM options or does it use its own? If the second, is there a way to install CM and keep Sony's look? I could not find information about it CM site is not clear to look at.
Im planning to root my device with this tutorial http://forum.xda-developers.com/z3-...-to-rooted-stock-sgp621-firmware-drm-t3015494
CyanogenMod doesn't use any of the Sony GUI stuff. It looks identical to stock Android like you would get on a Nexus device. If you like the widgets etc you may want to stick with the stock Sony ROM. Hopefully it wont be too long until Sony release Lollipop for our devices. I'm personally going to wait until then if I don't like what Sony have done I'll switch to CyanogenMod.
Please bew aware CyanogenMod may not be as stable or perform as well as the stock ROM.
Can i possibly know why devices owning the 6795 like the rn3 won't upgrade to CM13 ? What do the devs require so much that they can't port CM13 to the mediatek version ? I'm afraid i'm not aware of this version so much, but does it properly need android M in order to run ?
Mediatek phones are generally far more difficult to develop for because they don't like to release kernel sources and they are built for generic phones so they don't work as well
Mediatek development most currently are porting roms that is the same base as the original. If it came out with 5.0.2 then the max version for a custom rom is probably 5.1.1 and its harder to port higher android OS without any sources.
Oh, i see.. So mostly is because of the phone devs that won't release certain codes and whatever you need in order to develop the rom, right ?
Yeah blame the chipset manufacturer.
I'm no developer, but what about this info?
https://github.com/rmtew/MediaTek-HelioX10-Kernel
Hello!
I have been following annual Google I/O 2017 and heard about all the benefits of Google's Project Treble.
I cannot help but wonder how are developers (for example here at XDA) able to create custom roms or unofficial Android updates. Why Google can't make official Android Nougat update for Nexus 7 2013, but you here at XDA can. What is different between your work and Google's when it comes to these things, as far as neither has access to hardware manufacturer's code support.
I have to say I am not a professional software developer, so I understand if this topic is beyond my comprehension.
Thank you!
"Why Google can't make official Android Nougat update for Nexus 7 2013"
Planned obsolescence.
"neither has access to hardware manufacturer's code support"
Google is obliged to release kernel source code because Linux(the kernel powering Android) is released under the GPL. The kernel is responsible for letting Android "talk" to the hardware. Developers at XDA can then modify the open-source kernel to "fit" newer versions of Android.
I'd like to chime in on this.
Let's use the Nexus 7 2013 as an example. The difference between what an official build of Nougat from Google would be and what a build of Nougat from XDA is that the Google released one will have updated devices drivers that are made specifically for Nougat, while the XDA released one simply uses the older device drivers and hope they work. In some cases they work flawlessly (mostly on Nexus devices), however other times there are things that don't work so they either need to be disabled or worked around. So essentially a Google released OS has everything updated and tested to work with the new OS, while XDA releases are more 'hacked' together to work (simply because the device drivers aren't Open Source). Google may not have access to the hardware drivers, but they still get them updated.
Now let's touch on Project Treble (and why I am so excited about it). Instead of each and every device driver needing to be upgraded and tested for each new OS version, the OS version will specify which version of the drivers (HAL's) will work with the OS. This means there will be a separate space where all the device drivers will reside, and the OS will simply load those when booting (no more proprietary binary blobs to include in the ROM! hopefully...).
This means on any Project Treble compatible device (all phones that ship with Oreo, and some that update to Oreo) with an unlocked bootloader, a user can simply compile AOSP and flash it directly to the device with no modifications and have the device work. I believe this is actually a requirement to pass Google's certification process for new devices with Oreo. That means, say, with the LG v30 if the bootloader is unlocked, there can be an AOSP ROM on day one of its release.
So instead of Android being strictly a per device compile, it is just a general compile (sans device specific features). However, this doesn't remove the old driver issue. If the drivers in their respective partition no longer are updated by the manufacturer, the later AOSP code will need to be modified to work around these (and accept them). This is still easier in my opinion than the binary blobs.
As for official updates, Project Treble allows device hardware manufacturers to work on updating the device drivers while the OS Dev (Samsung, etc) works on updating their OS. So it is a parallel development instead of a serial one (hardware AND os instead of hardware THEN os).
A question.
Do the Nexus 5X devices have the Treble system or project incorporated with Oreo?
I do not understand the other manufacturers that cheaper excuses are giving, it is true that they are not obliged but I think it would be good practice, maybe they think as before that you will not buy them a phone.
Does someone make a Change.org or similar campaign to ask all Android manufacturers to make a minimum effort?