As of now, development for marshmallow has begun. I will attempt to use a prebuilt kernel for cm-13 builds until the kernel source is released. If Alcatel refuses to release the source as CM team progresses, I will have no choice but to abandon the project. If everyone could contact Alcatel to see if they can get a response that would be great. I requested it the same day MM was made available and yet no response.
Sent from my 6045I using Tapatalk
Unjustified Dev said:
As of now, development for marshmallow has begun. I will attempt to use a prebuilt kernel for cm-13 builds until the kernel source is released. If Alcatel refuses to release the source as CM team progresses, I will have no choice but to abandon the project. If everyone could contact Alcatel to see if they can get a response that would be great. I requested it the same day MM was made available and yet no response.
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
The best News in Day...You are the Nice Bro......As for Alcatel i send more than 10-15 messages and they didn't reply....
It would be helpful to know where to forward the link request.
I ve also asked many times, but no reply, one mail returned telling that they have asked their devs for my query of unlocking bootloader.
Isn't there a "contact us" link on their webpage? Bury them in requests.
Ah this is something I have been dying to know, what we needed for cm13. I will send a request email as well. Just to be clear, what we want is the idol 3 marshmallow kernel source code?
I'm just going to politely mention I bought the older idol 3 over newer phones due to community projects like cm, and I would love it if the *whatever is needed* is released.
Side note, i thought the GPL required kernel source to be released?
Sent from my 6045O using Tapatalk
nekomancey said:
Ah this is something I have been dying to know, what we needed for cm13. I will send a request email as well. Just to be clear, what we want is the idol 3 marshmallow kernel source code?
I'm just going to politely mention I bought the older idol 3 over newer phones due to community projects like cm, and I would love it if the *whatever is needed* is released.
Side note, i thought the GPL required kernel source to be released?
Sent from my 6045O using Tapatalk
Click to expand...
Click to collapse
They have 3 months time to release it before they break the law
Here is the contact page
http://www.alcatel-mobile.com/global-en/company/contactus
Demetris said:
They have 3 months time to release it before they break the law
Here is the contact page
http://www.alcatel-mobile.com/global-en/company/contactus
Click to expand...
Click to collapse
So you are positive that they have to give out kernel source? They can't decide to not share kernel source?
I mean,MTK is another story,but in our case kernel source has to be given out unless they want to break the law?
The Marionette said:
So you are positive that they have to give out kernel source? They can't decide to not share kernel source?
I mean,MTK is another story,but in our case kernel source has to be given out unless they want to break the law?
Click to expand...
Click to collapse
While much of the android source uses the apache license and they can choose whether to release or not, the kernel is still GPL and as such they are required to release the source to the public in a "timely" manner. Now theoretically if they wanted to be real douche's they could print out the whole thing and release a stack of paper as high as a telephone pole to the public, so it's important to always be POLITE when requesting the source but in general it's released in a usable format.
MTK is not located in countries that you can fight them over GPL compliance
Request sent, good times
Sent from my 6045O using Tapatalk
Have in mind that 6045 EU variants dont have MM yet so until then they need to release nothing
Demetris said:
Have in mind that 6045 EU variants dont have MM yet so until then they need to release nothing
Click to expand...
Click to collapse
Definitely right about that. They most likely won't until all variants/carriers are up to date which makes since. But since 6039 and 6045 share the same source it means we have to wait for both devices.
Sent from my 6045I using Tapatalk
Unjustified Dev said:
Definitely right about that. They most likely won't until all variants/carriers are up to date which makes since. But since 6039 and 6045 share the same source it means we have to wait for both devices.
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
Hey unjustfied dev Did you tried to unpack the CM 13 kernel and Stock 6.0.1 kernel...and Copy some files of ramdisk and split img From MM STOCK TO CM 13 ??
Edit: I made test kernel modiffed with some files from stock and Cm 13
You can try it To test it
Download From here
Note:Be Careful because it's test kernel ..You can hardbrick your device.!
Alek Dev said:
Hey unjustfied dev Did you tried to unpack the CM 13 kernel and Stock 6.0.1 kernel...and Copy some files of ramdisk and split img From MM STOCK TO CM 13 ??
Edit: I made test kernel modiffed with some files from stock and Cm 13
You can try it To test it
Download From here
Note:Be Careful because it's test kernel ..You can hardbrick your device.!
Click to expand...
Click to collapse
It's not that simple unfortunately.
Sent from my 6045I using Tapatalk
So pretty much from what I'm reading Alcatel, if they are kind enough to release the source, probably won't do so until ALL variants have MM, which might take a good long time.
kingoftheafro said:
So pretty much from what I'm reading Alcatel, if they are kind enough to release the source, probably won't do so until ALL variants have MM, which might take a good long time.
Click to expand...
Click to collapse
Not necessarily. Although they waited a long time to release 6045i and other 6045 variants TCL released the source for it's rom on the i806 within a week of the product going live..so keep in mind there is alcatel which is the "us division" and TCL which is the parent company and handles the "chinese division".
famewolf said:
Not necessarily. Although they waited a long time to release 6045i and other 6045 variants TCL released the source for it's rom on the i806 within a week of the product going live..so keep in mind there is alcatel which is the "us division" and TCL which is the parent company and handles the "chinese division".
Click to expand...
Click to collapse
Well I hope the us division Alcatel releases the source soon. I have no plans to go to a different phone so I hope they enable developers to get the most out of their tech.
kingoftheafro said:
Well I hope the us division Alcatel releases the source soon. I have no plans to go to a different phone so I hope they enable developers to get the most out of their tech.
Click to expand...
Click to collapse
The i806 IS the same phone just like the "panasonic eluga switch" is the same phone, therefore their source will work just fine for what we want should it become available.
I send yesterday more than 5-6 messages via Contact us to ALCATEL..They are finally replied bur...I don't see more Stupid than Alcatel Support:crying:...I'm asking them When will be released Source code they told me that Idol 3 will be updated in second part in year....:crying:
ScreenShoot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Orginal Message by me
Related
I have seen a dozen threads about this ICS sourcecode release, i and probably many others with me would be grateful if we could collect all information about porting/modding/devving ICS to our beloved SGSII - Gt-i9100 here in this thread, so we could have some structure about this really exciting release..
I am a noob about porting but i hope all you devs out there could help me and make this thread useful for all of us..
Kind regards Andreas R Sweden
As I know:
Official ICS from Samsung: about QII-2012
MIUI ICS: In process (maybe release before Chirstmas or new year
CM ICS: In process (maybe release before new year)
......
langthang said:
As I know:
Official ICS from Samsung: about QII-2012
MIUI ICS: In process (maybe release before Chirstmas or new year
CM ICS: In process (maybe release before new year)
......
Click to expand...
Click to collapse
Bull's Eye
Build targets
Here's another noob question which is hopefully related....
There has been mention that the source code only contains a build target is maguro (i.e. Galaxy Nexus). I am guessing this is so Google can release the code early and the new Galaxy Nexus still gets a head start.
My question is, does this build target have to come from google? And even if it did surely a build target would be specific to a device rather than the version of android?
What i am basically getting at it, is there no posibility of ICS development for the galaxy s2 until the build target is available?
Cheers
Mali400 Driver
And what about the mali400 driver is that released now when the sourcecode is released?
graemefaulkner said:
Here's another noob question which is hopefully related....
There has been mention that the source code only contains a build target is maguro (i.e. Galaxy Nexus). I am guessing this is so Google can release the code early and the new Galaxy Nexus still gets a head start.
My question is, does this build target have to come from google? And even if it did surely a build target would be specific to a device rather than the version of android?
What i am basically getting at it, is there no posibility of ICS development for the galaxy s2 until the build target is available?
Cheers
Click to expand...
Click to collapse
From http://source.android.com/
"The source code for the Android 4.0 platform and software stack has been released! This release allows OEMs to begin preparing Android 4.0 for installation on new and existing devices, and allows hobbyists, enthusiasts, and researchers to develop custom builds."
Firstly ICS is already out...Check my sig beta version already up and running second you should post this in the General section...and third drivers are still closed source from sammy so the only port will be from CM9 or AOSP
Matriak31 said:
Firstly ICS is already out...Check my sig beta version already up and running second you should post this in the General section...and third drivers are still closed source from sammy so the only port will be from CM9 or AOSP
Click to expand...
Click to collapse
Damn...53+ Million views that topic... plus one on the general, this is not development, this is at its most, a development brainstorm...
Matriak31 said:
Firstly ICS is already out...Check my sig beta version already up and running second you should post this in the General section...and third drivers are still closed source from sammy so the only port will be from CM9 or AOSP
Click to expand...
Click to collapse
HURR DUUR IM GUNNA CLICK THAT LINK AND OWAIT.
*me gusta*
Firstly, ten chars... then:
lovidore said:
HURR DUUR IM GUNNA CLICK THAT LINK AND OWAIT.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Matriak31 said:
Firstly ICS is already out...Check my sig beta version already up and running second you should post this in the General section...and third drivers are still closed source from sammy so the only port will be from CM9 or AOSP
Click to expand...
Click to collapse
at least the threads give you a bit of a laugh when you need it
damn it.. i was rick roll'd....
jastonas said:
damn it.. i was rick roll'd....
Click to expand...
Click to collapse
im just like you mate..i want to have ics but i have to be patient about it till the superdevs work their magic on it
As usual..
This forum have lost a couple of REALLY good developers because of the ****ty people who searches after threads to play around in.. grow up...
Admin close and move this thread
slitex said:
This forum have lost a couple of REALLY good developers because of the ****ty people who searches after threads to play around in.. grow up...
Admin close and move this thread
Click to expand...
Click to collapse
Do not want to start anything here mate but first. This thread should of been in General section since it has nothing to do with development. you are not trying to make a rom you are not trying to port anything....Second if you actually took the time to search and read upon the facts of the source nothing can be done until the actual drivers source is released so devs can actually work there magic.
so yeah you are right this thread should be closed cause its basically pointless to have it...
And as regarding trying to port it through the source i am pretty sure the devs are one step ahead of us all in knowing when the sources are out and trying to port this over..so no need for us to tell them what to do and when
langthang said:
As I know:
Official ICS from Samsung: about QII-2012
MIUI ICS: In process (maybe release before Chirstmas or new year
CM ICS: In process (maybe release before new year)
......
Click to expand...
Click to collapse
In this pace of Samsung,they will be publishing final rom from XDA
langthang said:
As I know:
Official ICS from Samsung: about QII-2012
MIUI ICS: In process (maybe release before Chirstmas or new year
CM ICS: In process (maybe release before new year)
......
Click to expand...
Click to collapse
Really hope that's true
Anyway, good luck to the devs!
Matriak31 said:
Do not want to start anything here mate but first. This thread should of been in General section since it has nothing to do with development. you are not trying to make a rom you are not trying to port anything....Second if you actually took the time to search and read upon the facts of the source nothing can be done until the actual drivers source is released so devs can actually work there magic.
so yeah you are right this thread should be closed cause its basically pointless to have it...
And as regarding trying to port it through the source i am pretty sure the devs are one step ahead of us all in knowing when the sources are out and trying to port this over..so no need for us to tell them what to do and when
Click to expand...
Click to collapse
This thread belong here. This is not creation but building from ground to roof with an hostile environement.
Sent from my GT-I9100 using xda premium
chadouming said:
This thread belong here. This is not creation but building from ground to roof with an hostile environement.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
no this one belongs in general topic and i am sure there are others out there who agree the same thing...Bio has already opened one thread so the need of this one is pointless....for general chat and people having questions yeah this should be moved there but since Biohazard already opened a thread regarding work on the port again this is no point
Just a information I´m giving up of ICS rom´s I tried maybe 5 of them without success all had some problems and all of them freeze the screen or some application for those that use phone regularly no make sense to use it right now, I´m backing to GB.
[CyanogenMod] Official support for HONOR 6
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We started a Petition to ask official support to CM's staff, and obtain an official thread in their forum.
(We also opened a request here)
Help us by supporting our cause:
Please vote and share this petition on the web.
Thank you.
Click to expand...
Click to collapse
First of all I invite you to sign this petition and share it across your Social Networks and Forums.
Then I ask you to read this Opening Post and collaborate with suggestions.
Now I'm going to analyse PRO and CONS of this Petition, in in order to explain you what it aims to.
I started this petition for the following reasons:
Of course, obtain an official thread in CM forum
Move people in the same direction, and gain their interest and involvment
Encourage development and avoid devs abandon their projects after a long time with no activity
Find new developers and testers, and enhance collaboration
Get results.
Considerations: (Read)
@shubham412302
Someone needs to build a unofficial build for our device first. No cm employee will do it for us
@spanorg
this petition has no sense at all. CM's staff don't officially support if there is no CM build by anyone.
First, a working unofficial build should be built. Then, if this build is stable, CM may include Honor 6 in supported devices. We are far away from this.
@shubham412302
if one of the hisilicon kirin device gets a stable cm every one can get a port or as build from sources.
@flibblesan
The Honor 6 will only get CyanogenMod when people will the skills and know-how to build the ROM decide to do so. Or people decide to have a go and learn.There is a lot of information online for building CyanogenMod so have a read, set up a build environment and have a go. You may not succeed but you could encourage other people to join in and work together. Good luck.
Click to expand...
Click to collapse
[/QUOTE]
According to you, I understand we'll never have a CM rom by CM, but we have to build one.
Petition ends @1k signs, so we have more time to work on CM.
@shubham412302
if one of the hisilicon kirin device gets a stable cm every one can get a port or as build from sources.
Click to expand...
Click to collapse
This guy gets it. I highly doubt we will see any progress before Huawei releases Android L. Only thing we can hope on is Huawei releasing an AOSP Rom. btw a simple request at Huawei by all the people for a simple AOSP Rom would not only provide us an AOSP rom but also make it easy as **** to build a CM Rom. Asking for a CM rom without even an AOSP rom is retarded as ****
http://forum.xda-developers.com/ascend-p7/general/info-t2920377
This device has a HiSilicon Kirin 910T SoC and has a CM rom WIP. Nothing is released yet, but when it is, I think it can be useful for Honor 6 development too.
413 supporters by now. Shouldn't be more? I don't know how many devices as been sold by Huawei, but surely must be thousands...
Sent with Honor 6 using Tapatalk
HmMarques said:
413 supporters by now. Shouldn't be more? I don't know how many devices as been sold by Huawei, but surely must be thousands...
Click to expand...
Click to collapse
Lots of them sold in .. China...
I gone to Facebook page and sent a message to the owner asking to share this petition, the page got more than 3k likes so if he shares it maybe some more people will join.
Sent with Honor 6 using Tapatalk
I'm tempted but not sure if i'll spend money on a device with a not yet supported soc.
Can't find any usefull resources (sourcecode) about the kirin platform except for the kernel sources.
Will be a very hard game to support this phone.
codeworkx said:
I'm tempted but not sure if i'll spend money on a device with a not yet supported soc.
Can't find any usefull resources (sourcecode) about the kirin platform except for the kernel sources.
Will be a very hard game to support this phone.
Click to expand...
Click to collapse
Hi codeworkx, Kirin 920 is really a powerful processor, cpu is more powerful of Snapdragon 805, just see AnTuTu comparison, the GPU is not recent and powerful as adreno 330 but it works well.
Huawei in 2014 it became the world's third largest producer of smartphones, soon will come out with many other devices cpu kirin, Other manufacturers like Samsung, Sony, HTC and LG are all in slump because Huawei make cpu proprietary and can sell devices top at a price more affordable.
It would be really great if someone like you, began to support the development of this device, I personally believe that Honor 6 worth a rom CM because is a device many sold is very powerful.
Users all over the world want a rom CM
Thanks!
PS - Ascend P6 has the CPU Huawei and Dev surdu_petru has succeeded to get CyanogenMod 11 - Unofficial
http://forum.xda-developers.com/showthread.php?t=2642278
Sorry for my bad english
codeworkx said:
I'm tempted but not sure if i'll spend money on a device with a not yet supported soc.
Can't find any usefull resources (sourcecode) about the kirin platform except for the kernel sources.
Will be a very hard game to support this phone.
Click to expand...
Click to collapse
Just an idea I'm throwing out there, maybe people would donate some money for you to get the device ? I know I would ..!
Dervisk said:
Just an idea I'm throwing out there, maybe people would donate some money for you to get the device ? I know I would ..!
Click to expand...
Click to collapse
Would be possible but that's no 100% guarantee for a 100% working cm rom.
The kirin platform is completely unsupported und it will require a ton of work.
The bootloader can be unlocked?
Can unsigned boot images be booted?
codeworkx said:
The bootloader can be unlocked?
Can unsigned boot images be booted?
Click to expand...
Click to collapse
-yes
-yes
codeworkx said:
Would be possible but that's no 100% guarantee for a 100% working cm rom.
The kirin platform is completely unsupported und it will require a ton of work.
The bootloader can be unlocked?
Can unsigned boot images be booted?
Click to expand...
Click to collapse
Yes, you can unlock both
Sent from my H60-L04 using XDA Free mobile app
codeworkx said:
Would be possible but that's no 100% guarantee for a 100% working cm rom.
The kirin platform is completely unsupported und it will require a ton of work.
The bootloader can be unlocked?
Can unsigned boot images be booted?
Click to expand...
Click to collapse
@codeworkx It is really easy to unlock the bootloader and put the recovery, just go vmall Huawei http://en.club.vmall.com/emotiondownload.php?mod=unlock&action=pre and put Product SN, IMEI and Product ID to get the unlock code then with adb or HONOR 6 Multi-Tool by VirusPlus http://forum.xda-developers.com/showpost.php?p=57270618&postcount=1 (a file batch that using adb and fastboot) you can install the recovery and get the root. Procedure similar to the Sony Ericsson a few years ago.
The only problem is finding a great developer like you that has a Honor 6
anyone here who wants to be my tester?
you should know how to use fastboot and adb to get logs.
contact me via pm or #honor6-dev at freenode irc.
im ready to test any time you are ready
Fyi, CM development
http://forum.xda-developers.com/showthread.php?t=3011343
Sent from my H60-L02 using Tapatalk
PETITION:
We reached the 950 signatures!
I ask your opinion: What's better? move our goal to 1500/2000 signatures, or close it?
I'd like to reach 2000 signatures
aaaa00 said:
PETITION:
We reached the 950 signatures!
I ask your opinion: What's better? move our goal to 1500/2000 signatures, or close it?
I'd like to reach 2000 signatures
Click to expand...
Click to collapse
2000 would be better.
daudus said:
2000 would be better.
Click to expand...
Click to collapse
Check this http://forum.xda-developers.com/honor-6/orig-development/cm-development-started-money-collection-t3011343/page3
@codework is workig on it.
1.657! :|
if somebody from Russia, China, and other countries read this thread please share it in your native language across forums and sn!
thanks
Latest YotaPhone2 Kernel Sources - If you are developing for the YotaPhone 2 the latest kernel sources are now available in the form of a 100Mb download direct from their server. If you have been waiting for them, you can pick them up now! http://ow.ly/3145oN
Sent from my YD201 using Tapatalk
adamo86 said:
Latest YotaPhone2 Kernel Sources - If you are developing for the YotaPhone 2 the latest kernel sources are now available in the form of a 100Mb download direct from their server. If you have been waiting for them, you can pick them up now! http://ow.ly/3145oN
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
Yeah, that is the kernel source alright. I guess there was enough requests for it after all.
Now we just need to make it better. We have the technology.
We need a cyanogenmod rom
Sent from my YD201 using Tapatalk
Great news indeed. About a week ago I've requested XDA's OEM relations manager Jerdog to contact Yota, and today he sent me a message that they finally obliged. His action together with some social media attention and requests through other channels probably all added up.
I've put it on github: https://github.com/SteadyQuad/android_kernel_yotaphone2
There's still a lot of work to do however, it's not plug-and-play. As far as I can see there's no kernel config included, so that might take time to figure out. I'm not an experienced kernel dev, but I'll give it some attention to see how far I get with it. Anyone else interested to help out here?
Wish that I could help, but this is not something were I'm able to add value... :/
Best of luck to you and any other that may go down that road.
what about the progress
now?
Sent from my YD206 using XDA Free mobile app
Does anyone have a mirror for the original tarball?
SteadyQuad said:
Great news indeed. About a week ago I've requested XDA's OEM relations manager Jerdog to contact Yota, and today he sent me a message that they finally obliged. His action together with some social media attention and requests through other channels probably all added up.
I've put it on github: https://github.com/SteadyQuad/android_kernel_yotaphone2
There's still a lot of work to do however, it's not plug-and-play. As far as I can see there's no kernel config included, so that might take time to figure out. I'm not an experienced kernel dev, but I'll give it some attention to see how far I get with it. Anyone else interested to help out here?
Click to expand...
Click to collapse
Config is in arch/arm/configs and seems to already be set up with the EPD display, so likely the same that Yota is using:
https://github.com/SteadyQuad/android_kernel_yotaphone2/tree/lollipop5.0/arch/arm/configs
Do you still have the original tarball?
Amplificator said:
Config is in arch/arm/configs and seems to already be set up with the EPD display, so likely the same that Yota is using:
https://github.com/SteadyQuad/android_kernel_yotaphone2/tree/lollipop5.0/arch/arm/configs
Do you still have the original tarball?
Click to expand...
Click to collapse
Can't find the original tarball. Sources on Github are pretty close though (I think I only missed some firmware files on very first commit). You probably found it already, but Yota seemed to have adapted the standard arch/arm/configs/msm8974_defconfig file for yp2, which contains amongst other things the Epson EPD driver:
Code:
CONFIG_FB_EPSON_S1D13522=y
CONFIG_EPSON_13522=y
It's been some time, but I remember after some small tweaks (on github) the kernel actually built and booted.
I've never managed to get into contact with Yota directly, but if you're planning development work, maybe you should ask them for an updated tarball, might have updated EPD firmware, CVE fixes and other updates .
SteadyQuad said:
Can't find the original tarball. Sources on Github are pretty close though (I think I only missed some firmware files on very first commit). You probably found it already, but Yota seemed to have adapted the standard arch/arm/configs/msm8974_defconfig file for yp2, which contains amongst other things the Epson EPD driver:
Code:
CONFIG_FB_EPSON_S1D13522=y
CONFIG_EPSON_13522=y
It's been some time, but I remember after some small tweaks (on github) the kernel actually built and booted.
I've never managed to get into contact with Yota directly, but if you're planning development work, maybe you should ask them for an updated tarball, might have updated EPD firmware, CVE fixes and other updates .
Click to expand...
Click to collapse
I sent Yota a mail, so let's see if they care to share
Cool, It would be awesome to get some lovin' on this device....
Yota responded:
Unfortunately, nowadays our company does not provide access latest kernel sources for Yotaphone 2.
Click to expand...
Click to collapse
So apparently they don't care :-/
Amplificator said:
Yota responded:
Unfortunately, nowadays our company does not provide access latest kernel sources for Yotaphone 2.
Click to expand...
Click to collapse
So apparently they don't care :-/
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"GPL license terms don't apply to us, and please stop building a loyal community around our devices!" :silly:
SteadyQuad said:
"GPL license terms don't apply to us, and please stop building a loyal community around our devices!" :silly:
Click to expand...
Click to collapse
Exactly.. I sent a follow-up mail with a friendly reminder of the GPL license and some other "plz gib" attempts, but the response felt more like this:
So apparently they don't care :-/
Click to expand...
Click to collapse
Actaully Yota Devices cares about community
And shares the latest kernel:
https://srv-fs1.yotadevices.com/public/file/28nVYCsjTUGwylIFgokCqA/kernel_sep21.zip
(direct link)
andpotugin said:
Actaully Yota Devices cares about community
And shares the latest kernel:
https://srv-fs1.yotadevices.com/public/file/28nVYCsjTUGwylIFgokCqA/kernel_sep21.zip
(direct link)
Click to expand...
Click to collapse
How did you get it? An old KGB buddy or something?
And thanks for the pm
How did you get it? An old KGB buddy or something?
Click to expand...
Click to collapse
No KGB involved, comrade
It seems that YotaDevices is monitoring threads on XDA sometimes.
andpotugin said:
No KGB involved, comrade
Click to expand...
Click to collapse
..if you say so
But thanks for the link.. it's good to know that K... Yota is watching
Amplificator said:
..if you say so
But thanks for the link.. it's good to know that K... Yota is watching
Click to expand...
Click to collapse
You're welcome!
And keep in mind: not Yota (mobile carrier), but Yota Devices (SW team)
So, how hard is it to merge this old pile of sources into a newish CM13 branch? I've compiled a linux kernel before but never did any more involved stuff than that - Anyone with prior experience or a decent written guide on how to adapt CM to a device around?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Who's back? We're back.
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Downloads:
Get CarbonROM
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Moto Z
Contributors
Somcom3X
Source Code: https://github.com/CarbonROM
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Bootloader
Version Information
Status: Nightly
Created 2017-05-30
Last Updated 2017-05-29
Does this rom support moto mods?
wow,new rom:victory: can i use the efficiency mod?This is the reason that hinders me from using custom ROM
moto mod support or what? i relly need a rom that support all moto mods
britoskates said:
moto mod support or what? i relly need a rom that support all moto mods
Click to expand...
Click to collapse
+1
Why not flash the ROM and find out? Battery mod works for me.
Sent from my XT1650-03 using Tapatalk
Somcom3X said:
Why not flash the ROM and find out? Battery mod works for me.
Click to expand...
Click to collapse
I don't have a moto mod yet, I'm waiting until the keyboard mod will be shipped in August. I just got my Moto Z but I'd like to already use a compatible custom ROM. I'd just like to be prepared when the keyboard mod arrives.
Shani Ace said:
I don't have a moto mod yet, I'm waiting until the keyboard mod will be shipped in August. I just got my Moto Z but I'd like to already use a compatible custom ROM. I'd just like to be prepared when the keyboard mod arrives.
Click to expand...
Click to collapse
I legit have no way of testing it to make sure it works if it hasn't come out yet [emoji6] .
Should be a basic fix anyway.
Sent from my XT1650-03 using Tapatalk
Somcom3X said:
I legit have no way of testing it to make sure it works if it hasn't come out yet [emoji6] .
Should be a basic fix anyway.
Click to expand...
Click to collapse
Sorry, I assumed that all moto mods run on the same platform/driver, so that when one moto mod is working with it, all (future) moto mods should be supported.
Apparently that's not the case, but glad to hear it would be a basic fix.
i cant go in the web site and this rom support jbl mod ?
no jbl speaker mod dont work
I'll get those mod changes merged in soon enough.
Sent from my XT1650-03 using Tapatalk
404 on the weeklies. :/
nice bro, i'll flash and test the last build
continue supporting moto z and good chance
doree said:
404 on the weeklies. :/
Click to expand...
Click to collapse
Whenever you try to download it, it gives you a 404?
Can you try this again for me as I successfully downloaded the latest version.
Sent from my XT1650-03 using Tapatalk
I merged in the battery mod changes. Efficiency mode works as expected. One thing I've noticed is battery stats will show the phone is awake a significant amount of the time. Snapchat/camera apps no longer force close. I believe whenever the charge state is changed from the mod the kernel throws a wakelock that the framework interprets as "wake up."
Most likely will not have the speaker mod working right away as I'm redoing the audio policy and have nothing to test it with. I pushed a change to fix speaker audio using the backend (as originally intended). Mod zip it's included by default from now on.
Let me know if you have any other issues.
Sent from my XT1650-03 using Tapatalk
Wow,Hope that more and more developers to add this.:victory:
It is not rooted ?
jimdent said:
It is not rooted ?
Click to expand...
Click to collapse
You need to flash an su add-on in recovery.
E.g. Supersu, magisk, lineages.
Sent from my XT1650-03 using Tapatalk
It would be be better prerooted.
When I do flash Supersu, magisk it ends up deleting imei information on Moto Z.
Somcom3X said:
You need to flash an su add-on in recovery.
E.g. Supersu, magisk, lineages.
Sent from my XT1650-03 using Tapatalk
Click to expand...
Click to collapse
Hey xda,
It might be a good idea to sign this, we are heading towards 300 signatures in less than 2 hours,
Let's do this!
https://www.change.org/p/carl-pei-w...ium=email&utm_campaign=share_email_responsive
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With project treble rom development will become easy AF (we hope!). Please sign, it's an important improvement for our phone.
Can Treble feature be added to a phone after the choice is made not to support it right off the bat? I thought the treble setup requires two different partitions that need to be part of the factory original file structure of the phone.
Sent from my Nexus 6 using Tapatalk
Huawei did it with the Mate 9, so it should be possible for OP, too.
jackennils said:
Huawei did it with the Mate 9, so it should be possible for OP, too.
Click to expand...
Click to collapse
Yes but their 8.0 update already supported treble.
Guys I wouldnt be to excited about this. Here are a few reasons.
1. OEM will still be in charge of sending out updates. Which we all know will not change
2. This does 0 for custom rom development at all. Most devs have already stated they will not support it or even bother with it.
3. The petition means less then nothing really.
4. The Mate 9 update is broke and doesnt work nearly as well as they are claiming in the portal post. (If you go to thread you will see that it is still unstable and requires tons of work to make it work right)
5. Even if you did flash an aosp rom with Treble, you would lose all OEM features.
Maybe we don't need an official treble, seems op5 and maybe op5t has the proper hardware to support it non-officially.
Keep an eye here for info:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
zelendel said:
Yes but their 8.0 update already supported treble.
Guys I wouldnt be to excited about this. Here are a few reasons.
1. OEM will still be in charge of sending out updates. Which we all know will not change
2. This does 0 for custom rom development at all. Most devs have already stated they will not support it or even bother with it.
3. The petition means less then nothing really.
4. The Mate 9 update is broke and doesnt work nearly as well as they are claiming in the portal post. (If you go to thread you will see that it is still unstable and requires tons of work to make it work right)
5. Even if you did flash an aosp rom with Treble, you would lose all OEM features.
Click to expand...
Click to collapse
Could you provide a source for the point 2? Thanks in advance
Why it's not going to happen, petition or not:
OmegaHsu @oneplus.net said:
Project Treble requires a storage partition, by which the Android framework and vendor image are separated. However, because partitions were not required of Android N and previous versions of Android, all of our current devices do not feature a partition. According to our tests, if we were to modify the partition layout via OTA there is a risk that devices will brick during the partitioning. We feel this poses too great a risk for our community of users, which is why we have decided not to implement Project Treble on current OnePlus devices.
Click to expand...
Click to collapse
Source
I'm in, we need 2,058 more people.
x111 said:
I'm in, we need 2,058 more people.
Click to expand...
Click to collapse
Read the post above yours.
Sent from my ONEPLUS A5010 using Tapatalk
i guess we have to close the thread.
Really? Why can't we keep pushing and discussing it? First of all, oneplus could have easily implemented a second partition given that Oreo was already out of for months when the 5t was released. So this is excuse sounds a bit lame to me. Second, why not providing us with the vendor files so that developers can find a partitioning implementation that users use on their own responsibility?
No Treble support was well known before release. Not sure I understand why folks purchased it if they wanted Treble support.
The more thoughtful petition should be....
OnePlus plz give support of our 5T to android Q
RijuSarkar13 said:
The more thoughtful petition should be....
OnePlus plz give support of our 5T to android Q
Click to expand...
Click to collapse
I guess treble support won't be coming with whatever reason they have given about partition.
We should ensure that we get android Q atleast
I'm happy with the nougat build why think so much ahead?
Ranop11 said:
I'm happy with the nougat build why think so much ahead?
Click to expand...
Click to collapse
Because the lastest Android version is 8.1 lol we are three updates behind. While I'm not entirely pressed about Oreo (8.1 is nice I'll admit) OP could've AT LEAST shipped with 7.1.2
Sent from my ONEPLUS A5010 using Tapatalk
frozl said:
Really? Why can't we keep pushing and discussing it? First of all, oneplus could have easily implemented a second partition given that Oreo was already out of for months when the 5t was released. So this is excuse sounds a bit lame to me. Second, why not providing us with the vendor files so that developers can find a partitioning implementation that users use on their own responsibility?
Click to expand...
Click to collapse
Their software pipeline is definitely more than a few months long. I'd bet the Nougat build was already a ways into development before Oreo came out, and at that point starting over would have been silly.
So what? I don't care what software I'm on, if it's stable, battery life good, and there's not much change is android oreo, **** guys you are like bunch of kids, if it works why change?
I think our best bet right now is hoping someone will develop a 5T ROM with hacked in Treble Support so we can then use the upcoming unified Treble Updates. Not much hope we'll see any support from OnePlus and they are getting slower and slower with their Updates...