https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-MPI24.65-24
nice, just saw this on android police.
Finally! Would love to see some custom 6.0 kernels now.
@squid2 @Alberto97 @Carlos Arriaga
Related
Moto x pure 2015 6.0 source kernel released. Would anything be able to come of this for our phone?
There is no (stock) 6.0 and never will be for our phone.
ok :v
Moto G 2015
[SIZE=+2][INDEX][/SIZE] [SIZE=+2]
Helpful Information
[/SIZE]Welcome, this thread has been created to make it easier for you to scroll through a wide range of options for our beloved device. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread, or pm me, or create your own thread in the Q&A forum. Do not use this as a general help thread.
Also, don't forget to Hit Thanks button if this thread was helpful to you.
Regards,
PoseidonKing
Basic Device Information
Wikipedia
Specifications
Codename: Osprey
Resolution: 720×1280, 294ppi
CPU: 1.4GHz quad-core Qualcomm Snapdragon 410 processor
RAM: 2GB
Official Stock Firmware
[INDEX][Osprey][Merlin] Moto G Factory Firmw… | Moto G 2015
Device Tools
Tools
[TOOL] WinDroid Toolkit | Unlock | Root | Fl… | Moto G 2015
Guides
[GUIDE] [OSPREY] [MM] Install TWRP, Root and… | Moto G 2015
[GUIDE] [Osprey] Advanced Interactive Govern… | Moto G 2015
[GUIDE][Osprey] Fastboot Flashing Factory Firmware Images
Custom ROMs
Official
[ROM][6.0.1][Osprey][OFFICIAL]BlissPop
[ROM][MM/6.0.1_r17][OFFICIAL] BeanStalk 6.08 (UBERTC)[9th MARCH][Osprey]
[ROM][6.0.1][OSPREY][OFFICIAL][NIGHTLY] CyanPop v6.1
[ROM][6.0.1][OSPREY] Android Ice Cold Project 11.0 [Official Nightlies]
[ROM][osprey][Official][6.0.1] crDroid Android
[ROM][OFFICIAL][5.1.1] MaxiCM 5.1.1 OFFICIAL for osprey
[ROM][OFFICIAL][Lollipop 5.1.1][osprey] PAC-ROM LP-MR1
[ROM][OFFICIAL][5.1.1]Tesla Rom
[ROM][5.1.1_r18]Team Radium 1.4[OFFICIAL][Osprey]
Unofficial
[ROM][6.0.1][osprey] Unofficial CyanogenMod 13
[ROM][6.0.1_r22] XenonHD [UNOFFICIAL][RRO][21ST MARCH]
[ROM][6.0.1/MM] XPerience-10.0.1_r16 [5TH MARCH][UNOFFICIAL][OSPREY]
[ROM][6.0.1][UNOFFICIAL]Android Open Kang Project(AOKP)
[ROM][6.0.1][UNOFFICIAL]Android Open Kang Project MODIFIED (AOKPM )
[ROM][osprey][5.1.1][UNOFFICIAL] SlimLP 5.1.1 for Moto G 2015 (20150825)
[ROM][UNOFFICIAL][5.1.1] OwnRom 5.1.1_r9 for Moto G3 (osprey)
[ROM][Unofficial][5.1.1]Candy5
[Unofficial] Paranoid-L 5.1 osprey
[ROM] [5.1.1] [UNOFFICIAL] Euphoria-OS 1.1 [OSPREY] [29-09-15]
Kernels
Kernels
[KERNEL][LINARO][6.x] Optimus Kernel R7 [OSPREY][23/3/16]
[Kernel][osprey][DT2W][6.0.X][CM/AOSP/STOCK] X-Infinity Kernel For Moto G 2015 [-O3]
[Kernel][Uber 5.2] INAZUMA [Overclocked][Osprey][6.0.X][CM/AOSP]
[Kernel][CM-13.0][osprey] Ultra Kernel for Moto G 2015 [R4] 22/02/16
[KERNEL] [blu_spark r92] [Lollipop 5.1.1]
Recoveries
TWRP
[TWRP][osprey] TWRP for Moto G 2015
Reserved
reserved
hey i dont know what the problem is but my moto g always stays warm and heats up quickly when it's running on a custom rom. I tried cm12 , cm13 , resurrection remix, z5g. But when i run it on stock rom it stays cool . I also tried stock optimised rom and there was no heating issue
ajul_raj said:
hey i dont know what the problem is but my moto g always stays warm and heats up quickly when it's running on a custom rom. I tried cm12 , cm13 , resurrection remix, z5g. But when i run it on stock rom it stays cool . I also tried stock optimised rom and there was no heating issue
Click to expand...
Click to collapse
If you are using a custom kernel, then refer to my thread for some kernel tweaks that might help your device cool down a little bit.
Hit Thanks if I Helped!
Regards,
PoseidonKing
Hey Guys,
I have made a compilation for the roms of motorola 3rd generation as well as the moto g turbo. Links are provided for each and every rom.
Lineage OS 15 (unofficial)
https://forum.xda-developers.com/2015-moto-g/orig-development/rom-lineageos-15-0-t3667902
Lineage OS 14.1(official)
For Osprey:
https://forum.xda-developers.com/2015-moto-g/orig-development/rom-unofficial-cyanogenmod-14-t3466246
For Merlin:
https://forum.xda-developers.com/2015-moto-g/orig-development/rom-unofficial-cyanogenmod-14-t3470500
MIUI 8(for merlin)
https://forum.xda-developers.com/2015-moto-g/development/patchrom-miui-8-merlin-t3665220
Cyanogenmod 13(official)
https://forum.xda-developers.com/2015-moto-g/orig-development/rom-cyanogenmod-13-t3254236
Resurrection Remix 6.0.1
For Merlin:
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-t3478845
For Osprey:
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-5-5-t3197371
Pure nexus rom(Unofficial)
For Osprey:
https://forum.xda-developers.com/2015-moto-g/development/rom-pure-nexus-moto-g-2015-t3603002
For Merlin:
https://forum.xda-developers.com/2015-moto-g/development/rom-pure-nexus-moto-g-2015-t3608819
CrDroid official 6.0.1
For Osprey:
https://forum.xda-developers.com/2015-moto-g/development/crdroid-moto-g-2015-t3175804
For Merlin:
https://forum.xda-developers.com/2015-moto-g/development/rom-crdroid-v3-4-t3624455
AOSP 7.0
https://forum.xda-developers.com/2015-moto-g/orig-development/rom-android-source-project-t3457061
Viper OS:
For Osprey:
https://forum.xda-developers.com/2015-moto-g/development/rom-viperos-v1-0-moto-g-2015-t3610138
For Merlin:
https://forum.xda-developers.com/2015-moto-g/development/rom-viperos-v1-0-moto-g-2015-t3613218
Nougat Xperience:
Osprey:https://forum.xda-developers.com/2015-moto-g/development/nougat-xperience-11-1-0r07-t3504890
Stock roms:
7.1.1 port from moto g4 play and moto x play
For Osprey:
https://forum.xda-developers.com/2015-moto-g/development/rom-stock-rom-6-0-1-optimized-t3609991
For Merlin:
https://forum.xda-developers.com/2015-moto-g/development/merlin-stock-rom-moto-g-turbo-t3629419
Stock 6.0.1 Optimized:
https://forum.xda-developers.com/20...m-stock-motorola-6-0-1-rom-optimized-t3355938
Stock 5.1.1 Optimized:
https://forum.xda-developers.com/20...m-stock-motorola-5-1-1-rom-optimized-t3352643
I'll update this forum with new roms in the future.'
For now enjoy these roms.
you missed many roms, even if they arent popular someone may want that
bluedragon12 said:
you missed many roms, even if they arent popular someone may want that
Click to expand...
Click to collapse
Will be uploading more by tomorrow.
This thread is based on: https://forum.xda-developers.com/moto-maxx/general/oreo-8-0-t3660752
But for Android 9 Pie, Who wants the new Android in this phone?
lat94084 said:
This thread is based on: https://forum.xda-developers.com/moto-maxx/general/oreo-8-0-t3660752
But for Android 9 Pie, Who wants the new Android in this phone?
Click to expand...
Click to collapse
1) We just got Oreo on Quark. I think you should learn to use that first.
2) That Quark Oreo thread you referenced was started in August 2017. When did Quark get Oreo? July 2018.
It's now August 2018, and you are asking for Pie. So, look for Quark Pie in July 2019.
3) Also, like before only @bhb27 can code the necessary kernel for any Quark Pie. It's not who "wants" it, it's WHO can actually do it. Maybe @bhb27 wants to just work on his new Oreo kernel and ROM for awhile. Maybe he wants a different phone...
4) If you read the other thread you say this is based on, discussing it didn't really help bring Oreo any faster to Quark. It still all depended on @bhb27 actually doing the work, and doing it right. See point #2.
_______
Just so I don't have to type everything over from the first thread, read this. In your mind just substitute "Pie" every time "Oreo" is mentioned, and substitute "Oreo" when "Nougat" is mentioned. SAME EXACT SITUATION A YEAR AGO:
AUGUST 24, 2017
jeffkahlo777 said:
I want Android 8.0 Oreo for Motorola Moto Maxx/DROID TURBO, waiting for LineageOS 15, Resurrection Remix 5.9, etc.
Click to expand...
Click to collapse
ChazzMatt said:
It will take @bhb27 coding the current Motorola Marshmallow Quark kernel to Oreo -- the same way he coded it to work for Nougat.
Our previous CM dev @Skrilax_CZ did the original work back in early 2015, first coding Quark Motorola Kitkat kernel to work with Lollipop. Then when Lollipop Motorola source code was finally published he used actual Lollipop kernel in the CM releases. Once CM had a kernel for Quark, THEN other devs could "port" ROMs and just plug in the CM kernel.
@bhb27 started doing dev work about this time and released his own "custom" kernel with more features to complement the "stock" CM kernel @Skrilax_CZ coded. You could use 12.1 ROM (with Lollipop 5.1) with CM kernel or even RR Lollipop with CM kernel -- or use those ROMs and install @bhb27's custom kernel. But all the ROMs uses the CM (now LOS) kernel as "stock" kernel. It's what makes ALL the Quark ROMs possible in the first place.
(For our Quarks, even AOSP ROMs -- ALL ROMs -- use the CM kernel. They have to. There are no others. When Sunshine unlocked the Droid Turbo bootloader @Skrilax_CZ re-coded the Quark CM kernel to also work with XT1254 -- otherwise these custom ROMs would NOT be compatible for all Quarks. The kernel is the foundation.)
Then, when Motorola Marshmallow got released in late 2015, same thing. First a Lollipop kernel was coded to work with Marshmallow, then MONTHS later (July 2016, for XT1225) when Motorola released Marshmallow for Quark and then the kernel source code (September, October?) finally an actual Marshmallow kernel to work with Marshmallow. (Lollipop custom ROM for Quark beat official Motorola Lollipop and Quark Marshmallow custom ROM beat official Marshmallow by MONTHS.)
By this time @bhb27 had taken over all the kernel work, coding the basic "stock" kernel for all the Quark ROMs as well as his name-sake custom kernel.
When Nougat arrived, there was no official Nougat Quark kernel from Motorola -- so we had to keep using Marshmallow kernel. And @bhb27 did the work to let Nougat ROMs use that kernel.
Will be the same thing with Oreo. But @bhb27 still has to code it to work smoothly with Oreo.
Also, there is no more CM. We now have LOS as the "base". @bhb27 does not release official LOS ROMs, but that's where the device kernel files go that all devs pull from.
So, @bhb27 will use Marshmallow kernel in LOS Oreo tree to make a stock kernel for all ROMs. At that point he will release an Oreo ROM based on that work. (Right now he's the dev for both RR and crDroid ROMs. Last year he surprised us by releasing then-new Nougat crDroid first, whereas he had been dev for Marshmallow RR and Mokee, and RR was his favorite.)
@bhb27 will also probably release an advanced "standalone" custom kernel with more options, like he does now, but it's that base stock LOS kernel which is most important.
After he releases his Oreo kernel work, then other Quark devs can use that stock LOS Oreo Quark kernel to release their Oreo ROMs.
The kernel will be the foundation of any Oreo ROMs and it will all depend on @bhb27.
But don't pester him. It will be ready when it's ready.
__________
TLDR: @bhb27 is the man. He'll do the Oreo-compatible stock kernel first and then the first Oreo custom ROM. Everyone else will then follow with other ROMs.
Click to expand...
Click to collapse
lat94084 said:
This thread is based on: https://forum.xda-developers.com/moto-maxx/general/oreo-8-0-t3660752
But for Android 9 Pie, Who wants the new Android in this phone?
Click to expand...
Click to collapse
Hope @bhb27 works on Android 9 pie as well.
once more Thanks @bhb27 your knowledge and Hard work never cease to amaze me :good::victory::victory:
I think it best to focus on android Oreo.
This thread is based on: https://forum.xda-developers.com/moto-maxx/general/android-9-pie-t3825923 (which is based on: https://forum.xda-developers.com/moto-maxx/general/oreo-8-0-t3660752)
But for Android 10 "Queen Cake", Who wants the new Android version on this phone?
@ChazzMatt wrote last year (edited for Android 10 "Queen Cake"):
It will take @fgl27 coding the current Motorola Marshmallow Quark kernel to Android 10 -- the same way he coded it to work for Nougat, Oreo and Pie.
Our previous CM dev @Skrilax_CZ did the original work back in early 2015, first coding Quark Motorola KitKat kernel to work with Lollipop. Then when Lollipop Motorola source code was finally published he used actual Lollipop kernel in the CM releases. Once CM had a kernel for Quark, THEN other devs could "port" ROMs and just plug in the CM kernel.
@fgl27 started doing dev work about this time and released his own "custom" kernel with more features to complement the "stock" CM kernel @Skrilax_CZ coded. You could use CM 12.1 ROM (with Lollipop 5.1) with CM kernel or even RR Lollipop with CM kernel -- or use those ROMs and install @fgl27's custom kernel. But all the ROMs uses the CM (now LOS) kernel as "stock" kernel. It's what makes ALL the Quark ROMs possible in the first place.
(For our Quark, even AOSP ROMs -- ALL ROMs -- use the CM kernel. They have to. There are no others. When SunShine unlocked the DROID TURBO bootloader @Skrilax_CZ re-coded the Quark CM kernel to also work with XT1254 -- otherwise these custom ROMs would NOT be compatible for all Quark. The kernel is the foundation.)
Then, when Motorola Marshmallow got released in late 2015, same thing. First a Lollipop kernel was coded to work with Marshmallow, then MONTHS later (July 2016, for XT1225) when Motorola released Marshmallow for Quark and then the kernel source code (September, October?) finally an actual Marshmallow kernel to work with Marshmallow. (Lollipop custom ROM for Quark beat official Motorola Lollipop and Quark Marshmallow custom ROM beat official Marshmallow by MONTHS.)
By this time @fgl27 had taken over all the kernel work, coding the basic "stock" kernel for all the Quark ROMs as well as his name-sake custom kernel.
When Nougat arrived, there was no official Nougat Quark kernel from Motorola -- so we had to keep using Marshmallow kernel. And @fgl27 did the work to let Nougat ROMs use that kernel.
When Oreo arrived, there was no official Oreo Quark kernel from Motorola -- so we had to keep using Marshmallow kernel. And @fgl27 did the work to let Oreo ROMs use that kernel.
When Pie arrived, there was no official Pie Quark kernel from Motorola -- so we had to keep using Marshmallow kernel. And @fgl27 did the work to let Pie ROMs use that kernel.
Will be the same thing with Android 10. But @fgl27 still has to code it to work smoothly with Android 10.
Also, there is no more CM. We actually have LOS as the "base". @fgl27 does not release official LOS ROMs, does release unofficial LOS ROMs, but that's where the device kernel files go that all devs pull from.
So, @fgl27 will use Marshmallow kernel in LOS Android 10 tree to make a stock kernel for all ROMs. At that point he will release an Android 10 ROM based on that work. (Right now he's the dev for both RR and LOS ROMs. This year he surprised us by releasing then-new Pie RR first, then LOS, where as he had been dev for Lollipop RR, Marshmallow RR and Mokee, Nougat RR and crDroid, Oreo RR, Pie RR and LOS, and RR was his favorite.)
@fgl27 will also probably release an advanced "standalone" custom kernel with more options, like he does now, but it's that base stock LOS kernel which is most important.
After he releases his Android 10 kernel work, then other Quark devs can use that stock LOS Android 10 Quark kernel to release their Android 10 ROMs.
The kernel will be the foundation of any Android 10 ROMs and it will all depend on @fgl27.
But don't pester him. It will be ready when it's ready.
__________
TLDR: @fgl27 is the man. He'll do the Android 10-compatible stock kernel first and then the first Android 10 custom ROM. Everyone else will then follow with other ROMs.
Thanks for the info.
until 2030 I have this working