Lollipop Kernel sources released - Moto G General

Motorola has taken some heat for not pushing Lollipop kernel source as required, even though it started updated its devices to Android 5.0 way back in late 2014. Well, it's doing so now. Developers, head to Moto's GitHub to download.
Here is the link
https://github.com/MotorolaMobilityLLC/kernel-msm/tags

Old news..

Most of DEvs are notified now
sanchit0403 said:
Motorola has taken some heat for not pushing Lollipop kernel source as required, even though it started updated its devices to Android 5.0 way back in late 2014. Well, it's doing so now. Developers, head to Moto's GitHub to download.
Here is the link
https://github.com/MotorolaMobilityLLC/kernel-msm/tags
Click to expand...
Click to collapse
well now you ask the moderator to lock this thread. Most of the devs are notified regarding this.

Related

finally cm9 stable version not nightly

i was checking cm9 website and i found under stable first cm9 in stable check it up http://get.cm/?device=crespo&type=stable
link for rom direct download http://get.cm/get/3qC
here lastest gapps for ics 20120429 http://goo.im/gapps
cm9 team said
ICS, we hardly knew ye.
Builds for CyanogenMod 9 stable will be rolling out to our servers tonight. As noted before, this will be the end of the line for the ICS branch of our code; only critical bug fixes will be merged moving forward.
As a note, the maguro build from this morning was not meant to be linked publicly. Maguro’s build this evening will be marked 9.0.0.1 to be on par with the other 9.0.0 releases.
Tonight’s release is for the majority of our ICS supported devices, the stragglers will catch up, and we will leave the door open for merging in additional devices from maintainers, external and internal. The team itself, will focus solely on Jelly Bean and maintenance of the CM 7 codebase.
Many have wondered why we bothered to finish CM 9 when we are already active in CM 10 development. To that, our answer is: we don’t like to leave things incomplete. There is no profit gained from what we do, so the satisfaction of completing a goal is our only reward. This release also serves as a release suitable for the masses, especially those who won’t have 100% functioning releases of CM 10 immediately or are averse to anything branded as ‘preview’, ‘alpha’, ‘beta’ or ‘nightly’.
On the topic of nightlies, this release also serves as an end to our CM 9 nightlies, to make way for nightlies chock full of Jelly Bean goodness. A follow-up post will be made when we enable those builds.
Smh. And this in development why?
Good job
Sent from my Nexus S using xda premium
albundy2010 said:
Smh. And this in development why?
Click to expand...
Click to collapse
And you had to post and why? Really sick of the smart asses who think they are the post police. Does it really bother you people that bad that you can't just ignore things and mind your own?
LibertyMonger said:
And you had to post and why? Really sick of the smart asses who think they are the post police. Does it really bother you people that bad that you can't just ignore things and mind your own?
Click to expand...
Click to collapse
Says the smart ass replying to a post.
Where can I find latest gapps?
here last gapps for ics
massalim said:
Where can I find latest gapps?
Click to expand...
Click to collapse
here lastest gapps for ics is 20120429 http://goo.im/gapps
JB nightlies start today !!

Android lollipop 5.0 aosp released!!

Hey everyone, couldnt find an announcement thread so I started one myself.
Android 5.0 Lollipop AOSP has just been released! Anyone who cant wait to get there hands on it here you go! Droid-Life was so kind to post links!
http://www.droid-life.com/2014/11/03/aosp-aosp-lollipop-time/
Now within 90 days CM will release Android 5.0 so we'll have to be patient for an official version otherwise beta builds should be out soon
and within days we will have a custom rom
---------- Post added at 10:30 AM ---------- Previous post was at 10:29 AM ----------
Renosh said:
Now within 90 days CM will release Android 5.0 so we'll have to be patient for an official version otherwise beta builds should be out soon
Click to expand...
Click to collapse
i actually don't agree with cm on that, htc Samsung taking 90days is legitimate because they have tons of devices to maintain, but one plus only has one to maintain, it should take less time
paarthdesai said:
and within days we will have a custom rom
---------- Post added at 10:30 AM ---------- Previous post was at 10:29 AM ----------
i actually don't agree with cm on that, htc Samsung taking 90days is legitimate because they have tons of devices to maintain, but one plus only has one to maintain, it should take less time
Click to expand...
Click to collapse
You're right oneplus has one device, but its based on CyanogenMod but cm has to maintain as much devices as Samsung
90 days for cm12s release but much sooner for regular cm
Ok thats old news , op
henry0504 said:
Ok thats old news , op
Click to expand...
Click to collapse
Explain how that's old news please, it's literally just been released for aosp.
Transmitted via Bacon
timmaaa said:
Explain how that's old news please, it's literally just been released for aosp.
Transmitted via Bacon
Click to expand...
Click to collapse
Do we have a working OPO device tree for lollipop though? I don't think so.
Sent from my OnePlusOne
timmaaa said:
Explain how that's old news please, it's literally just been released for aosp.
Transmitted via Bacon
Click to expand...
Click to collapse
Think he's saying that because it started rolling out last night (around 9 I think UK time?) and that people have been talking about it in the Development thread.
So I wouldn't say old news really but that's probably why he said it.
fjsferreira said:
Do we have a working OPO device tree for lollipop though? I don't think so.
Sent from my OnePlusOne
Click to expand...
Click to collapse
No we don't, but what does that even have to do with my post that you quoted?
Transmitted via Bacon
Ok sorry for my confusing reply.... its because i have seen many posts about it so i think it is an old news. And i should not use old to describe it
fjsferreira said:
Do we have a working OPO device tree for lollipop though? I don't think so.
Sent from my OnePlusOne
Click to expand...
Click to collapse
Apart from Nexus(es) and Google Editions, no phones have a device tree specific for lollipop.
But, considering I came from a device which sources never got released (Galaxy S Advance) and devs was still able to build (not to port, to build) up to 4.4.4, that shouldn't be a problem
Just don't be in a hurry, first rule of XDA is NO ETA.
The manifest is still missing, and lots of the code is still 4.4 kitkat code..
There's still some time to go.
I just pray that our beloved Dev s can keep it or stop it rather from looking like apple os L
Sent from my One A0001 using XDA Free mobile app
All that developers really have to do to port it to the OPO is to get the patches used in CM for the OPO and apply them to Lollipop. There may be some problems that will occur during the application of the patches, but that all can be fixed.
I'll be excited to see a port and to use it dual booting until OnePlus releases the firmware for the One.
I think we will get 5.0 this month, but not the CM version. I can remember that Oneplus posted a AOSP version for the One by themselves. So why shouldn't they publish a AOSP version of Lollipop?
alex1301 said:
I think we will get 5.0 this month, but not the CM version. I can remember that Oneplus posted a AOSP version for the One by themselves. So why shouldn't they publish a AOSP version of Lollipop?
Click to expand...
Click to collapse
They may do that. But we will more likely get an unofficial build much sooner than official AOSP/CM12S.
CM12 Nightlis will also come long time before CM12S
alex1301 said:
I think we will get 5.0 this month, but not the CM version. I can remember that Oneplus posted a AOSP version for the One by themselves. So why shouldn't they publish a AOSP version of Lollipop?
Click to expand...
Click to collapse
Because their official ROM is CyanogenMod. If they will release an official AOSP 5.0 a lot of people will stop using CM11s and that would create a legal issue. It's not like Touchwiz for Samsung or Sense for HTC, the rom in the opo is not their intellectual property., they just have the right to use it.
where is that 5.0? cant see it ages
fjsferreira said:
Do we have a working OPO device tree for lollipop though? I don't think so.
Sent from my OnePlusOne
Click to expand...
Click to collapse
@fjsferreira you got a One! I was with you when you had your OG!

[Q] Now Android MM is out for while, anybody working on any new ROMS?

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

3.10.33 kernel from Nvidia Shield ported to Mi Pad

Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2...nhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2...FhQTHJIa2xVems
reserved
Artemka2008 said:
Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2ALf4H-2aBrZnhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2ALf4H-2aBrZFhQTHJIa2xVems
Click to expand...
Click to collapse
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).
drakonizer said:
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).
Click to expand...
Click to collapse
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)
Artemka2008 said:
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)
Click to expand...
Click to collapse
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.
drakonizer said:
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.
Click to expand...
Click to collapse
ok, I will delete this thread.
Artemka2008 said:
ok, I will delete this thread.
Click to expand...
Click to collapse
You don't have to delete the thread. It can be used for discussions. You can upload your kernel whenever you feel its appropriate to release your source code.
On a more helpful note: I can't say much without seeing the source code, but if you have ported the kernel drivers as well from shield, you can try using the blobs from Shield itself. You'll probably need to use blobs that match the version of the kernel you are trying to port.
so does that mean that there is a chance for cm12+?
Jahhhhhhh said:
so does that mean that there is a chance for cm12+?
Click to expand...
Click to collapse
Without camera and sound now. I tried to run Android 5.1.1 with our kernel. But I can't find working graphical blobs. I need help with it.
This is my last logcat https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U
This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?
Palm Trees said:
This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?
Click to expand...
Click to collapse
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.
Artemka2008 said:
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.
Click to expand...
Click to collapse
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.
drakonizer said:
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.
Click to expand...
Click to collapse
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.
Palm Trees said:
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.
Click to expand...
Click to collapse
Not the point. The shield developers will not be able to help us. Things will become very easy if this shield kernel port works. We will probably be able to use the newer blobs meant for the Shield, which makes development very easy, if this becomes bootable/stable. I really hope the OP manages to get it working. We either need newer blobs from Xiaomi or we need to write wrappers to use the current kitkat blobs (not easy, since Nvidia documentation is nowhere near as detailed as say, Qualcomm) or we need to get this port working well, which would enable us to use most of the blobs from the Shield (provided Xiaomi hasn't gone out of their way to screw with their blobs). The first two ways are practically impossible, which leads me to rest all my hope on this port. Unfortunately without the source code, we will just have to be silent spectators, waiting for some news.
Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks
rocky869 said:
Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks
Click to expand...
Click to collapse
I asked LuckyMeAgain to publish on the official website, so it's the same thing. I am ArtemkaVZM on 4pda and arttt on en.miui.com MiuiSmokeRom dev team.
Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia
Harrynowl said:
Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia
Click to expand...
Click to collapse
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U
Artemka2008 said:
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U
Click to expand...
Click to collapse
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?
drakonizer said:
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?
Click to expand...
Click to collapse
All the necessary blobs were taken from Shield. More no such files, which could be replaced.

Kernel Sources for Android Q Released for Mi A2

Kernel Sources for Android Q Released for Mi A2
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/jasmine-q-oss
android 10 update
so does this mean the stable update is going to be rolled out soon?
akforever said:
so does this mean the stable update is going to be rolled out soon?
Click to expand...
Click to collapse
certainly not
akforever said:
so does this mean the stable update is going to be rolled out soon?
Click to expand...
Click to collapse
Yes. Now sources are done.. they're waiting to merge January patch and they'll release it
It's sad how xda-developers has become. One posts about brand new kernel sources and other asks about OTA on a stock ROM...
Manosdocpap said:
It's sad how xda-developers has become. One posts about brand new kernel sources and other asks about OTA on a stock ROM...
Click to expand...
Click to collapse
Most people who buy Android One phones do it because they don't want to deal with the hassle of having to mod a phone to keep it updated timely, get rid of vendor crapware and so on. It should just work, be lean and updated quickly.
There are better alternatives at this price range for modding outside Android One project.
Manosdocpap said:
It's sad how xda-developers has become. One posts about brand new kernel sources and other asks about OTA on a stock ROM...
Click to expand...
Click to collapse
XDA always was in this way
Since I joined this community nothing has changed
Kernel source updated.
Does anyone know when android 10 rolling out?
This month or February?
Gak.Niat said:
Kernel source updated.
Does anyone know when android 10 rolling out?
This month or February?
Click to expand...
Click to collapse
patience
Gak.Niat said:
Kernel source updated.
Does anyone know when android 10 rolling out?
This month or February?
Click to expand...
Click to collapse
Just wait. For God sake
They even don't read a few posts above.
Another one just asked again when the update is coming. It's truly remarkable there are people who still contribute code to those gimmie-gimmie tech illiteratures.
My post as well as many others should have been removed by mods on a thread that should discuss new kernel sources.
And there is the update to Android 10 (recovery update, not fastboot):
http://bigota.d.miui.com/V11.0.4.0.QDIMIXM/miui_JASMINEGlobal_V11.0.4.0.QDIMIXM_545aa0d958_10.0.zip
Some user gets android 10. Based on screenshot i attach. Maybe russian / east europe get android 10 right now. I don't know this is valid or not.
Update : Android 10 coming to my phone. My location in Indonesia.
Gak.Niat said:
Some user gets android 10. Based on screenshot i attach. Maybe russian / east europe get android 10 right now. I don't know this is valid or not.
Update : Android 10 coming to my phone. My location in Indonesia.
Click to expand...
Click to collapse
does it buggy? might share your experience? currently using havoc 3.1

Categories

Resources