http://developer.sonymobile.com/201...-aosp-for-xperia-on-github-video-open-source/
Enjoy
I wonder if camera and modem will be supported in the future.
well thats good news
I love how people Hage such amazing text interpretation skills. The device tree was added to Github. There are lots of resources there for third party devs to work on and build their own AOSP, or AOSP based ROM.
But this isn't a official release. There never was. This is meant for developers and developers only.
Sent from my SGP311 using Tapatalk
Yeah we already knew because author already posted here http://forum.xda-developers.com/showthread.php?t=2907471
Sent from my D6503 using Tapatalk
Felimenta97 said:
I love how people Hage such amazing text interpretation skills. The device tree was added to Github. There are lots of resources there for third party devs to work on and build their own AOSP, or AOSP based ROM.
But this isn't a official release. There never was. This is meant for developers and developers only.
Sent from my SGP311 using Tapatalk
Click to expand...
Click to collapse
I'd argue it's an official release - a release for developers, but it's still official.
XDA is starting to be "Vanity Fair"...
Check your informations before you decide to post sensationalistic title like this one...
funky0308 said:
XDA is starting to be "Vanity Fair"...
Check your informations before you decide to post sensationalistic title like this one...
Click to expand...
Click to collapse
I see this too much... Aka agreement on ur post
And secondary point,
Not a rom, its neither a aosp rom
Yes official but its purely there for CM11, AOSP and any deviant developers to correct problems with their builds or correcr sonys problems
Its a greed thing sony is doing, it will benefit sony as well as xda devs
So... I wont be able to have AOSP rom with locked bootloader on my Xperia?
Cigaras said:
So... I wont be able to have AOSP rom with locked bootloader on my Xperia?
Click to expand...
Click to collapse
Unlocked bootloaders ONLY. If you still had a locked bootloader and ran AOSP, then your warranty wouldn't be void, thus creating problems for Sony, with non Devs users returning phones and help queries etc...
waynekirby said:
If you still had a locked bootloader and ran AOSP, then your warranty wouldn't be void
Click to expand...
Click to collapse
But if AOSP is provided by Sony themselves, why would they threat it as warranty voiding?
Lets take for example Xiaomi, for Mi3 and Mi4 gsmarena.com said that You could choose either MIUI or AOSP, and You get OTA updates for both (I am not sure if that is official, I do not own a Xiaomi device). Would be great if Sony would do something similar, Google Play Edition would also work for me, as long as I get to keep all the Bravia Engine and X-Reality goodness
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
funky0308 said:
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
Click to expand...
Click to collapse
I highly doubt this. If it's true, you should be able to show that, though...
funky0308 said:
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
Click to expand...
Click to collapse
There is a difference between google play editions and kernel source. If the source is precompiled, its as good as stock. Uncompiled source can be edited to cause serious hardware damage resulting in the void of warranty clause.
Xiaomi is yet to release kernel source for Mi3 and Mi4.
adyscorpius said:
There is a difference between google play editions and kernel source. If the source is precompiled, its as good as stock. Uncompiled source can be edited to cause serious hardware damage resulting in the void of warranty clause.
Xiaomi is yet to release kernel source for Mi3 and Mi4.
Click to expand...
Click to collapse
I don't understand your point here...
I know there are differences, that's why Sony works on this, officially.
We have CM and AOSP ROMs for Z1/Z2 but Sony now hired guy from here to help them in building AOSP that'll work on LB and is released by Sony.
That way, they still can control and approve what will go to device abd what won't...
Maybe I'm wrong but what's the point of releasing AOSP without kernel support from bootloader?
We already have that..
My guess would be - they want us to use AOSP but they don't want us to unlock bootloader and mess with DRM keys.
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Envious_Data said:
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Click to expand...
Click to collapse
Exactly...that's the whole point.
Finally, someone who understand what I'm trying to say and what's the whole purpose of that project
funky0308 said:
Exactly...that's the whole point.
Finally, someone who understand what I'm trying to say and what's the whole purpose of that project
Click to expand...
Click to collapse
Would be nice if instead of your warrenry being voided, its changed
So free repairs for sony fauls so long as its not caused by you rom
Envious_Data said:
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Click to expand...
Click to collapse
AOSP compiled ROM from sony ?
i tought we'd only get the source code and nothing more on AOSP ?
Haldi4803 said:
AOSP compiled ROM from sony ?
i tought we'd only get the source code and nothing more on AOSP ?
Click to expand...
Click to collapse
We only are getting source it seems but to have this for locked bootloaders sony must compile and sign a rom and kernel
Related
My question is can I use a devices stock kernel to create a build for said device?
My T-Mobile Sony Xperia Z has a locked bootloader and can only run roms using the stock kernel. I've seen other AOSP looking roms run off a devices stock kernel so I was hoping it possible.
Can anyone guide me in this? I would love for my phone to have HALO and different modes like phablet or tablet mode from Paranoid Android. Is this possible with a stock kernel or would features like that require a custom one? I assume it could be run just like Facebook Messenger does it..just as an app I mean.
knightsray said:
My question is can I use a devices stock kernel to create a build for said device?
My T-Mobile Sony Xperia Z has a locked bootloader and can only run roms using the stock kernel. I've seen other AOSP looking roms run off a devices stock kernel so I was hoping it possible.
Can anyone guide me in this? I would love for my phone to have HALO and different modes like phablet or tablet mode from Paranoid Android. Is this possible with a stock kernel or would features like that require a custom one? I assume it could be run just like Facebook Messenger does it..just as an app I mean.
Click to expand...
Click to collapse
Why do you think this isn't done already if it was this easy? The PA, CM framework and such needs code in the kernel and the stock kernel can't be remade because nobody's got the signing code for it, except Sony.
You'll need a unlocked bootloader for Omni ROM.
@MikeChannon, I think this thread can be closed.
Skickat från min C6603 via Tapatalk 2
TheHawk002 said:
Why do you think this isn't done already if it was this easy? The PA, CM framework and such needs code in the kernel and the stock kernel can't be remade because nobody's got the signing code for it, except Sony.
You'll need a unlocked bootloader for Omni ROM.
@MikeChannon, I think this thread can be closed.
Skickat från min C6603 via Tapatalk 2
Click to expand...
Click to collapse
You're wrong. It's not impossible to use stock kernel with a custom ROM, sometimes it's even inevitable, because there are no kernel sources available or the bootloader cannot be unlocked.
Adam77Root said:
You're wrong. It's not impossible to use stock kernel with a custom ROM, sometimes it's even inevitable, because there are no kernel sources available or the bootloader cannot be unlocked.
Click to expand...
Click to collapse
It's pretty much impossible to do so with an AOSP-based firmware. Occasionally it's tried, but always leads to poor results (see CM9 ICS builds for I9100 prior to kernel source release that used an initramfs repack.)
At a minimum it requires initramfs changes, and since the initramfs is signature-checked as part of the kernel image on every device I know of, it's not possible without terrible terrible hacks. Personally, I would prefer to not bother at all supporting any locked device that requires workarounds in the build. It leads to difficult to maintain code, and if people want to run an open source firmware, they should just not buy a locked (or non-unlockable) device in the first place.
Entropy512 said:
It's pretty much impossible to do so with an AOSP-based firmware. Occasionally it's tried, but always leads to poor results (see CM9 ICS builds for I9100 prior to kernel source release that used an initramfs repack.)
At a minimum it requires initramfs changes, and since the initramfs is signature-checked as part of the kernel image on every device I know of, it's not possible without terrible terrible hacks. Personally, I would prefer to not bother at all supporting any locked device that requires workarounds in the build. It leads to difficult to maintain code, and if people want to run an open source firmware, they should just not buy a locked (or non-unlockable) device in the first place.
Click to expand...
Click to collapse
I also prefer having sources and building kernels rather than doing bad hacks, I just pointed out that it's possible and sometimes is a must (Not talking about Omni, just in general.), there are devices without unlockable BL. E.g. we were using 2nd-init method on p880 before official JB came out and BL unlock became possible.
Adam77Root said:
I also prefer having sources and building kernels rather than doing bad hacks, I just pointed out that it's possible and sometimes is a must (Not talking about Omni, just in general.), there are devices without unlockable BL. E.g. we were using 2nd-init method on p880 before official JB came out and BL unlock became possible.
Click to expand...
Click to collapse
May I ask if you ever had a AOSP based firmware or just remakes of the stock ROM to look like AOSP? Because there you've the big difference. It's (obviously, because Entropy is Entropy ) just like @Entropy512 said.
Skickat från min C6603 via Tapatalk 2
TheHawk002 said:
May I ask if you ever had a AOSP based firmware or just remakes of the stock ROM to look like AOSP? Because there you've the big difference. It's (obviously, because Entropy is Entropy ) just like @Entropy512 said.
Skickat från min C6603 via Tapatalk 2
Click to expand...
Click to collapse
Yes, I did. I know the difference between a themed and a real AOSP rom. If I didn't, I wouldn't be a RD. What I wrote is totally possible and legit.
Sent from my OmniROM-powered LG Optimus 4X HD
Maybe I missed some annoucement... does anyone know if Sony will release sources for 12.0.A.2.254?
Seems to me that development for custom kernels (like Doomlord's) have stalled because there are no sources available.
omoithesane said:
Maybe I missed some annoucement... does anyone know if Sony will release sources for 12.0.A.2.254?
Seems to me that development for custom kernels (like Doomlord's) have stalled because there are no sources available.
Click to expand...
Click to collapse
Not available yet... :crying::crying::crying::crying::crying::crying::crying:
Rajeev said:
Not available yet... :crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
I know :crying:
But does anyone know if Sony will release the sources? How long does this usually take? I think FW .254 was released a month ago...
omoithesane said:
I know :crying:
But does anyone know if Sony will release the sources? How long does this usually take? I think FW .254 was released a month ago...
Click to expand...
Click to collapse
As I understand it they have no choice but to release the kernel source as it's linux and the licensing requires that it be made available. That said, the proprietary blobs for the cameras, wifi, etc. aren't generally licensed the same way so they don't normally get released, at least in source form.
I've requested Sony to provide the source and they will do that really soon
eagleeyetom said:
I've requested Sony to provide the source and they will do that really soon
Click to expand...
Click to collapse
Nice! :good: :fingers-crossed:
Just out of curiosity:
I had an Xperia Arc. My perception was that Sony released the kernel sources (including proprietary modules and everything else which is necessary to build a working custom kernel) relatively quickly and without anyone asking for it. Has this policy changed, did they just forget in case of the Xperia SP/.254 kernel sources or did I just perceive this wrong?
Finally Sony releases .254 kernel sources
Sent from my C5303 using Tapatalk
Here is a diff if anyone wants to view
Siddhesh said:
Finally Sony releases .254 kernel sources
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
I know. I was the one who asked the right person to do it
https://github.com/uberlaggydarwin/...mmit/0dd49c41698a82b77f32ac80e8caef80eba09142
GitHub may have derped.
Here is a diff between previous kernel sources and now
That's the most recent kernel source
https://github.com/uberlaggydarwin/sonystockkernelxperiasp
uberlaggydarwin said:
I know. I was the one who asked the right person to do it
https://github.com/uberlaggydarwin/huashan-kernel/commit/1c8ff356025e1e66142d0ce431c73cc2a57f4e58
GitHub may have derped.
Here is a diff between previous kernel sources and now
That's the most recent kernel source
https://github.com/uberlaggydarwin/huashan-kernel
Click to expand...
Click to collapse
So that means, the CM 10.1 kernel will be updated, right? :good:
sarkar1990 said:
So that means, the CM 10.1 kernel will be updated, right? :good:
Click to expand...
Click to collapse
Yes
Sent from my C5303 using Tapatalk
Probably not, the kernel used for 10.1is not related to the Sony kernels as I ported the drivers to a newer kernel version. We already have any changes that may be in the 2.254 kernel and more. (I didn't notice any changes to the Sony drivers).
Sent from my C5303 using XDA Premium 4 mobile app
Won't rebase off this.
sarkar1990 said:
So that means, the CM 10.1 kernel will be updated, right? :good:
Click to expand...
Click to collapse
Finally had a chance to look at them as I got home from work only just before...
Just left my computer to push them today so didn't get a chance to check them but adfad666 is right and not much actual changes changed though which are useful for us.
Just some general CAF / kernel updates so not too important.
A panel driver was updated but I'm doubt we we will use it as our kernel is not based off stock.
Probably not. . Let's wait for 4.3 kernel from Sony as it will be worth rebasing off that
Thanks for the link to sources....
Hi guys
We heard you! Sony kernel sources now available on GitHub
Read more here
http://developer.sonymobile.com/2014/06/27/we-heard-you-sony-kernel-sources-now-available-on-github/
If you have dev questions contact me
Enjoy!
J
sp sources are up
Hope sony hear us for some other things too.. with us sony can make the Android for us even better /o/
Very good thank you!!!
jerpelea said:
Hi guys
We heard you! Sony kernel sources now available on GitHub
Read more here
http://developer.sonymobile.com/2014/06/27/we-heard-you-sony-kernel-sources-now-available-on-github/
If you have dev questions contact me
Enjoy!
J
Click to expand...
Click to collapse
As I see the 201 kernel available for SP. Why not the 205?
air001 said:
As I see the 201 kernel available for SP. Why not the 205?
Click to expand...
Click to collapse
With the exception of the ram disk, they are identical.
https://github.com/sonyxperiadev/kernel-copyleft/tree/12.1.A.1.xxx
Btw thanks @jerpelea
Perhaps someone can finaly take a proper look to the annoying RAM issue
Opening the camera api to allow 3rd party apps to set ISO etc would be the cherry on the top...
Well, now that the kernel is up - how about a service that allows to create signed kernels so that locked BL can also benefit from custom kernels?
mick232 said:
Well, now that the kernel is up - how about a service that allows to create signed kernels so that locked BL can also benefit from custom kernels?
Click to expand...
Click to collapse
It's impossible to do without Sony private keys/signing tools leak. This is just a kernel source, it doesn't contain them. So even if you build the kernel from source, it will only work on UBL.
Also, to all: moving source to github won't solve anything, and doesn't change anything, it's now just easier to obtain the source for devs. Previously the source was released in the form of open-source tar packages on Sony site...
MrSteve555 said:
It's impossible to do without Sony private keys/signing tools leak. This is just a kernel source, it doesn't contain them. So even if you build the kernel from source, it will only work on UBL.
.
Click to expand...
Click to collapse
That is why I said "service" - Sony doesn't have to hand over the keys. They can provide a service, you upload your custom built kernel, Sony signs it, you download the signed kernel.
mick232 said:
That is why I said "service" - Sony doesn't have to hand over the keys. They can provide a service, you upload your custom built kernel, Sony signs it, you download the signed kernel.
Click to expand...
Click to collapse
Oh, so I misunderstood you. Your idea is really good, but I don't think Sony would ever think about it. So it's just a miracle...
Signing a custom kernel is endorsing it. How can they know if it's broken or something messed up.
Releasing the keys and signing package is better option with declaration or warning for no liability in case of damage
neXus PRIME said:
Signing a custom kernel is endorsing it. How can they know if it's broken or something messed up.
Releasing the keys and signing package is better option with declaration or warning for no liability in case of damage
Click to expand...
Click to collapse
They will never release the keys. However, they, themselves, can sign it if we give it to them. And we can provide them with sources so that they know everything is working fine.
shahrukhqasim said:
They will never release the keys. However, they, themselves, can sign it if we give it to them. And we can provide them with sources so that they know everything is working fine.
Click to expand...
Click to collapse
They dont have enough resources & time to release proper and quick updates. You really think with the NUMBER or devices with locked bootloaders and estimated number of submissions of custom kernels will be possible???
Think about it first. At least dozen models within 18 months time fframe, tens and hundreds of custom ROMs and kernels for each devices.
And its not like one kernel dev will only go once. Be reasonable bro.
Companies only provide services which can be automated. or require a suitable amount of debugging. Bootloader unlocking is IMEI based and database can be automated. So millions of users can use it without issues.
Much better would be they just release the keys in spirit of open source or maybe give some unlock mechanism for permanent locked BLs.
jerpelea said:
Hi guys
We heard you! Sony kernel sources now available on GitHub
Read more here
http://developer.sonymobile.com/2014/06/27/we-heard-you-sony-kernel-sources-now-available-on-github/
If you have dev questions contact me
Enjoy!
J
Click to expand...
Click to collapse
We need solution for locked blootloaders! Development is so hard on locked bootloaders. Give us signing keys or make a site to get kernels signed or anything. LBL are lagging behind UBL a great deal. We need signing facility.
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
neXus PRIME said:
They dont have enough resources & time to release proper and quick updates. You really think with the NUMBER or devices with locked bootloaders and estimated number of submissions of custom kernels will be possible???
Think about it first. At least dozen models within 18 months time fframe, tens and hundreds of custom ROMs and kernels for each devices.
And its not like one kernel dev will only go once. Be reasonable bro.
Companies only provide services which can be automated. or require a suitable amount of debugging. Bootloader unlocking is IMEI based and database can be automated. So millions of users can use it without issues.
Much better would be they just release the keys in spirit of open source or maybe give some unlock mechanism for permanent locked BLs.
Click to expand...
Click to collapse
Then lets just contact Sony what solution do they propose? They should at least respond.
Hi friends. Can you check this kernel source's is real or useless?
https://github.com/nofearnohappy/android_vendor_xiaomi_hermes
https://github.com/lbule/android_device_xiaomi_hermes
This isn't a kernel source, it's a device tree for build CyanogenMod
~ Xiaomi Redmi Note 2 Prime ~
SkiFire13 said:
This isn't a kernel source, it's a device tree for build CyanogenMod
~ Xiaomi Redmi Note 2 Prime ~
Click to expand...
Click to collapse
ho great so cyanogenmod is comming?
tailslol said:
ho great so cyanogenmod is comming?
Click to expand...
Click to collapse
We will see, it is very hard to port when kernel is not given. There are people working on it and doing a very good job!
Sadly, the complete kernel (custom kernel with drivers) was leaked for a short period and a few devs have it.. but they are afraid to use or publish it because they don't want to be sued.
tailslol said:
ho great so cyanogenmod is comming?
Click to expand...
Click to collapse
For now someone built it but it's very unstable
~ Xiaomi Redmi Note 2 Prime ~
Sad news about this device's kernel source.
is this usefull?
http://forum.xda-developers.com/cro...al/marshmallow-source-codes-mediatek-t3218602
chris5932 said:
We will see, it is very hard to port when kernel is not given. There are people working on it and doing a very good job!
Sadly, the complete kernel (custom kernel with drivers) was leaked for a short period and a few devs have it.. but they are afraid to use or publish it because they don't want to be sued.
Click to expand...
Click to collapse
Wow didnt know that, really the full source kernel was leaked??? And some devs have it D:?. If its true i hope they decide one day to make a nice ROM build, i guess everyone of us would wait for that
chris5932 said:
We will see, it is very hard to port when kernel is not given. There are people working on it and doing a very good job!
Sadly, the complete kernel (custom kernel with drivers) was leaked for a short period and a few devs have it.. but they are afraid to use or publish it because they don't want to be sued.
Click to expand...
Click to collapse
Sued? The ones to be sued are mediatek and/or xiaomi for not complying gpl license
adaltavo said:
Wow didnt know that, really the full source kernel was leaked??? And some devs have it D:?. If its true i hope they decide one day to make a nice ROM build, i guess everyone of us would wait for that
Click to expand...
Click to collapse
At least someone has it.. I am not so sure on how many have it. Don't be too excited yet, we might not get it (soon). The source can not just be published to the public, the one who does will face some problems.. (see what happened to incomplete source).
chris5932 said:
At least someone has it.. I am not so sure on how many have it. Don't be too excited yet, we might not get it (soon). The source can not just be published to the public, the one who does will face some problems.. (see what happened to incomplete source).
Click to expand...
Click to collapse
May i ask what happened?. And i know is not that easy, what i meant is that he (or they) could make a nice ROM build with that source, maybe as an anonymus guy or something like that, is not necesary to publish full source code. Our another hope is wait for MTK to release it , but it wont be soon, even could never happen
adaltavo said:
May i ask what happened?. And i know is not that easy, what i meant is that he (or they) could make a nice ROM build with that source, maybe as an anonymus guy or something like that, is not necesary to publish full source code. Our another hope is wait for MTK to release it , but it wont be soon, even could never happen
Click to expand...
Click to collapse
We can build roms ourselfs, just need proper kernel. Just let me say that much: I have a reliable source that told me someone has it. I don't think (anymore) it was leaked to the public ever, all kernel leaked on git were incomplete.
All kernel sources I've seen for X10 are not for our device. Another thing is the AOSP sources are very buggy and unfinished.
I finally made progress on my AOSP 5.1 and fixed the slow app launch (maybe you've seen one youtube video posted here - this is my build).
Unfortunately I don't have kernel source for Redmi Note 2 and it is impossible to build a custom kernel, so I'm trying to finish the ROM and will use prebuilt kernel.
If you think it is easy as porting, then you're wrong. Compiling something from source and fixing all bugs is completely different animal.
CM 12.1 also booted, but a lot of work needs to be done there too.
https://github.com/omlet05/MediaTek-HelioX10-Kernel
yay?
tailslol said:
https://github.com/omlet05/MediaTek-HelioX10-Kernel
yay?
Click to expand...
Click to collapse
Check the date and please stop posting same thing again and again. This is the original broken half source that was leaked over 2 months ago now.
I.nfraR.ed said:
All kernel sources I've seen for X10 are not for our device. Another thing is the AOSP sources are very buggy and unfinished.
I finally made progress on my AOSP 5.1 and fixed the slow app launch (maybe you've seen one youtube video posted here - this is my build).
Unfortunately I don't have kernel source for Redmi Note 2 and it is impossible to build a custom kernel, so I'm trying to finish the ROM and will use prebuilt kernel.
If you think it is easy as porting, then you're wrong. Compiling something from source and fixing all bugs is completely different animal.
CM 12.1 also booted, but a lot of work needs to be done there too.
Click to expand...
Click to collapse
What is time to wake? On miui time is long :/ On our last phone (A820) time to wake is much better.
How aboute "tap to wake"? What is result on antutu? When you publish rom?
AOSP boots up and works faster than MIUI and also has much much better ram management, although it would be good if we could make a custom kernel.
Tap to wake normally needs to be supported in kernel, so the answer is "no".
Antutu score is irrelevant, but normally I get about 48K with the basic model. I've seen higher, seen lower.
It also depends on kernel.
Don't forget that for A820 I have a custom optimized kernel.
Hello
When you share rom? How to progress?
Known XDA rule, don't ask for ETA He'll tell us when ready
bumcykcyk said:
Hello
When you share rom? How to progress?
Click to expand...
Click to collapse
It will be shared when it is done.. Ussd/BT working but camera still doesnt
Hey guys was just wondering if there any developers who are working on some new ROMS for our MXP as it seems very quiet in the development sections of the forums, couple of variations of stock rom and that's pretty much it.
Was expecting for development to pick up after the MM but its been VERY quiet.
Not a complaint just wondering if there are things going on behind the curtains like development being done or some CM13 or anything along those lines.
djsynth said:
Hey guys was just wondering if there any developers who are working on some new ROMS for our MXP as it seems very quiet in the development sections of the forums, couple of variations of stock rom and that's pretty much it.
Was expecting for development to pick up after the MM but its been VERY quiet.
Not a complaint just wondering if there are things going on behind the curtains like development being done or some CM13 or anything along those lines.
Click to expand...
Click to collapse
Having MM OTA out is not enough.
Not much can be done until Motorola will release the kernel source
nimrodsv said:
Having MM OTA out is not enough.
Not much can be done until Motorola will release the kernel source
Click to expand...
Click to collapse
Any idea if its going to get released and if yes then when ?
and out of self interest what does the kernel source enable developers to do ?
djsynth said:
Any idea if its going to get released and if yes then when ?
and out of self interest what does the kernel source enable developers to do ?
Click to expand...
Click to collapse
It's totally depended on Motorola.
The source enable developers to release AOSP roms and custom kernels.
nimrodsv said:
It's totally depended on Motorola.
The source enable developers to release AOSP roms and custom kernels.
Click to expand...
Click to collapse
Has Motorola been known to release kernel sources before for previous flagships ?
Would love for them to release the binaries and device tree for AOSP builds...
djsynth said:
Has Motorola been known to release kernel sources before for previous flagships ?
Click to expand...
Click to collapse
They are required to release any changes to the kernel they have made due to the GPL license that the linux kernel is protected by. so its not a matter of if but when.
MM and now kernel source released, and still, slow as hell. Sucks. I thought this phone would be one of the most active in development, was i wrong.
Sent from my XT1575 using Tapatalk
I'm on retail Asia variant which leaves me with 1 rom. And I can't even get mm for my variant let alone custom roms.
What happened to this phone?
Please go to http://forum.xda-developers.com/moto-x-style/help/happened-to-phone-t3283551
to continue this topic if possible, thank you