[BETA][5.1.1] CyanogenMod 12.1 by tank0412 [A500CG][A501CG] - Zenfone 5 Original Android Development

{
"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"
}
Bug list:
GPS & FM
What is working:
Media (IT IS FIXED) But Youtube can be dead
Audio (IT IS FIXED)
RIL (baseband) (IT IS FIXED)
Touchscreen xD
Image decoding
MTP
Webview
Camera
Sensors
Houdini
Wi-FI
Rom features:
It was build from fresh CM12.1 source (November stagefright patch is included)
I used proprietary files from WW 3.24.40.87
I used device tree by quanganh2627 for building so this way community will get all fixes
Custom kernel which was built from X Anwar sources so it has underclock, DT2W, million governors and i/o stuff.
How to flash it:
Step 1:
You should download files for flashing:
File with CM12.1 rom:
Google Drive
ADB v1.0.32: Download from Google Drive
TWRP 2.8.7.0 recovery by quanganh2627 (new December build): Download from Google Drive
Step 2:
1) Unpack archive with ADB and put TWRP image there.
2) Copy file with rom and gapps to internal/external memory of your phone.
3) Then you should reboot your phone in the droidboot mode. (turn off you gadget then press Turn off button and volume + button)
Then go to the ADB folder and hold Shift + Right Mouse button and write this command:
Code:
fastboot flash recovery new-zen5-reco.img
Then you should reboot your phone in the recovery mode. (turn off you gadget then press Turn off button and volume - button)
Step 3:
Then you phone will reboot in the recovery. In the recovery you should instal package with rom.
Step 4:
After flashing, you should format (not wipe) data and cache in the TWRP.
Then you should reboot to system.
Bug reporting:​Attach logcat and detailed describe the issue. Send this to me (tank0412)
Credits:​@quanganh2627 (i used his device tree for building)
USING MY ROM AS BASE FOR YOUR ROM IS DENIED
IF YOU IGNORE IT, I WILL ASK MODERATOR TO DELETE YOUR THREAD
But you can use my kernel only without any problems.
XDA:DevDB Information
CyanogenMod 12.1 by tank0412, ROM for the Asus Zenfone 5
Contributors
tank0412
Source Code: https://github.com/tank0412/android_device_asus_a500cg-1
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked bootloader
Based On: CM
Version Information
Status: Beta
Current Beta Version: 2.3
Beta Release Date: 2016-03-16
Created 2016-01-04
Last Updated 2016-03-21

Changelog(16.03.2016):
Trying to update Stagefright patch
Re-add Google Camera
Fixing writing to external memory card using Pixelmaster Camera.
Changelog(14.03.2016):
Apply vibrator.patch by @quanganh2627
Re-add camera app
P.S. I applyed patch but i do not know is it work. (hardware of vibrator is dead on my phone)
Changelog(13.03.2016):
Camera was fixed so it can make video without any problem
More fixes for media
Changelog(12.03.2016):
Audio was fixed
Media was fixed (but you can have few troubles with Youtube)
Changelog(04.02.2016):
Using blobs files from WW V3.24.40.87
And more
Changelog(10.01.2016):
DT2W was enabled
Unsuccessful attempt to totally fix Camera
Unsuccessful attempt to fix audio & media
Anyway, i am working on it.
Changelog(06.01.2016):
Latest fixes from quanganh2627s repo were applyed (commit #b953942e748b4d88f27b202abfc318dbd49161ea)
Changelog(05.01.2016):
Using fresh CM12.1 source
Minor fixes and improvements for audio, (i built libtinycompress and libtinyalsa libs from source, but audio is stay partly dead.)
Removed trash from Asus stock (only Asus Camera is included)
A tonn tweaks by @TecnoTailsPlays was added. (commit #56f91ca1fd3dc3e58d02d48b136a97c3a62567a1 )
Chagelog(04.01.2016):
Initial release

Reserved
Hot-fixes​Fix of MTP:
https://drive.google.com/file/d/0B-Fin8UxrD6PZWt6UWIxQmdMT3M/view?usp=sharing
Flash it via fastboot (drodiboot)

awesome, i waiting for upload good luck tank0412

milano88 said:
awesome, i waiting for upload good luck tank0412
Click to expand...
Click to collapse
I uploaded it few minutes ago. xD

tank0412 said:
I uploaded it few minutes ago. xD
Click to expand...
Click to collapse
i started download , after finish will immediately install thanks for your work

edited:
Anyone review?
Sent from my ASUS_T00J using Tapatalk
Running on Recreated Remix Ultra 7.2
Dont know,this is the most suitable CM 12.1 based for me,after trying almost all of cm12.1 rom here.
Less freeze after few days using...
Just 3 or 4 times freeze while charging

ShuviterDjogja said:
edited:
Anyone review?
Click to expand...
Click to collapse
Just trust me.

tank0412 said:
Just trust me.
Click to expand...
Click to collapse
Always trus the dev sir
[emoji106]
Always follow the threads..
Sent from my ASUS_T00J using Tapatalk

Thanks for this. I assume this is compiled from the latest source code (as of 2016-01-03), right?
Would you mind putting this on the OP, especially when you has an update version in the future.
I haven't tried this rom, waiting for audio fixed.
One thing that I don't understand, I see other offical cm12.1 rom size is about 250MB, but why zen5 get double size?
Firstly, I thought we will get a very small minimum rom size but it seems not that much different to Asus stock (after remove bloatware).

baszu said:
Thanks for this. I assume this is compiled from the latest source code (as of 2016-01-03), right?
Would you mind putting this on the OP, especially when you has an update version in the future.
I haven't tried this rom, waiting for audio fixed.
One thing that I don't understand, I see other offical cm12.1 rom size is about 250MB, but why zen5 get double size?
Firstly, I thought we will get a very small minimum rom size but it seems not that much different to Asus stock (after remove bloatware).
Click to expand...
Click to collapse
I could not download latest CM source so it was built from October source.
Many trash from Asus stock were added by quanganh2627's device tree.
I agree that this trash must be removed.

tank0412 said:
I could not download latest CM source so it was built from October source.
Many trash from Asus stock were added by quanganh2627's device tree.
I agree that this trash must be removed.
Click to expand...
Click to collapse
why you can't download the lastest CM source ?
i wait for the bug fixed, and will download this ROM. But right now is to much CM12.1 build for Zenfone 5 so i'm confused which one i must flash on my devices.

Awesome. Hope u will build CM13

Is it really that hard to fix GPS and FM Radio for AOSP based ROMs?
I'm dying for a clean AOSP based ROM but I can't flash it in these circumstances; no audio and no GPS :/

gusbalaa said:
why you can't download the lastest CM source ?
i wait for the bug fixed, and will download this ROM. But right now is to much CM12.1 build for Zenfone 5 so i'm confused which one i must flash on my devices.
Click to expand...
Click to collapse
Threre are only THREE CM12.1 builds. First build was made by Tran Huu Tin, second build was made by KnoneNull and third build was compiled by me.
If you find build by other author, you must understand that it was not built from source. It is a just modificated build by Knone or Tran Huu Tin with a minor changes.
So it is an easy choice.
By the way, i can not download latest source due to my Internet provider. I mean i can not use repo tool to sync sources due to it.

Parliamert said:
Is it really that hard to fix GPS and FM Radio for AOSP based ROMs?
I'm dying for a clean AOSP based ROM but I can't flash it in these circumstances; no audio and no GPS :/
Click to expand...
Click to collapse
I plan to fix audio but nobody can fix GPS because Broadcom and Asus have not published enough source code for this yet.

tank0412 said:
Threre are only THREE CM12.1 builds. First build was made by Knone, second build was made by KnoneNull and third build was compiled by me.
If you find build by other author, you must understand that it was not built from source. It is a just modificated build by Knone or Tran Huu Tin with a minor changes.
So it is an easy choice.
By the way, i can not download latest source due to my Internet provider. I mean i can not use repo tool to sync sources due to it.
Click to expand...
Click to collapse
Okay thanks, so i will prepared for download your build if stable versions is released, with fixed bugs.
But what about this one ?
http://forum.xda-developers.com/showthread.php?p=63910968

tank0412 said:
Threre are only THREE CM12.1 builds. First build was made by Tran Huu Tin, second build was made by KnoneNull and third build was compiled by me.
If you find build by other author, you must understand that it was not built from source. It is a just modificated build by Knone or Tran Huu Tin with a minor changes.
So it is an easy choice.
By the way, i can not download latest source due to my Internet provider. I mean i can not use repo tool to sync sources due to it.
Click to expand...
Click to collapse
I'm confused now. Do you mean your compile is also based on Tran's and Knone's source.
If this the case, it is not different to those then.
For sync source code, do you mean your internet provider block github or it is too slow to download latest source?
If it is latter, maybe, someone can help sync source and upload it to other website?

baszu said:
I'm confused now. Do you mean your compile is also based on Tran's and Knone's source.
If this the case, it is not different to those then.
For sync source code, do you mean your internet provider block github or it is too slow to download latest source?
If it is latter, maybe, someone can help sync source and upload it to other website?
Click to expand...
Click to collapse
I denied using my build as base for other custom roms. So nobody will use my build as base for their custom rom.
My build was really compiled from CM source like Knones build or Tran Huu Tins build.
My provider block repo tool so i can not use it. If somebody upload latest CM12.1/AOSP 5.1.1 code to other website, i will download it and this way i will use it for custom rom building.

gusbalaa said:
Okay thanks, so i will prepared for download your build if stable versions is released, with fixed bugs.
But what about this one ?
http://forum.xda-developers.com/showthread.php?p=63910968
Click to expand...
Click to collapse
It is just modificated build by Knone. It was not built from source.

Related

[Kernel][Mokee]CM11 kernel repack for mokee

As everyone knows mokee official release uses a old kernel build from month of may, while the latest kernel is from sept. So I have made a repack of the latest kernel. As far my primary tests everything is working so just flash it and enjoy the latest one, incase xiaomi updates their kernel and anyone uses it but mokee, I will repack again and update the thread.
Enjoy!
ps: Sorry no flashable zip available. please report any bug you may find!
Steps:
1. enable usb debugging
2. connect to pc and open adb
3. copy the downloaded boot.img file to the adb folder.
4.open cmd, navigate to adb folder and type these lines one by one.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
5. after reboot, just copy the 2nd downlaoded file "pronto_wlan.ko" to /system/lib/modules/pronto and replace the existing file,
6. change the permission to rw-r-r
7. reboot and enjoy the latest kernel.​
If anyone can make a twrp/cwm flashable zip, you can share here.
Download
Screenshot:
{
"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"
}
thnx to the help from
kapil.git
Thanks for the Wake Up!!
saurabhrck said:
As everyone knows mokee official release uses a old kernel build from month of may, while the latest kernel is from sept. So I have made a repack of the latest kernel. As far my primary tests everything is working so just flash it and enjoy the latest one, incase xiaomi updates their kernel and anyone uses it but mokee, I will repack again and update the thread.
Enjoy!
ps: Sorry no flashable zip available. please report any bug you may find!
Steps:
1. enable usb debugging
2. connect to pc and open adb
3. copy the downloaded boot.img file to the adb folder.
4.open cmd, navigate to adb folder and type these lines one by one.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
5. after reboot, just copy the 2nd downlaoded file "pronto_wlan.ko" to /system/lib/modules/pronto and replace the existing file,
6. change the permission to rw-r-r
7. reboot and enjoy the latest kernel.​
If anyone can make a twrp/cwm flashable zip, you can share here.
Download
Screenshot:
thnx to the help from
kapil.git
Click to expand...
Click to collapse
deadlyindian said:
Thanks for the Wake Up!!
Good Work Brothers !!!!:laugh::laugh::laugh:
Keep it up.....:good::good::good:
But, if I am not wrong Xiaomi has not released any kernel sources and so all of our Devs are using only headers for compiling the ROM and so they are just changing the date in headers. Does this matters in performance, or stability?
Please do correct me, if I am wrong anywhere. I am always ready to learn new things.
Best Regards
BOND
Click to expand...
Click to collapse
SuperDroid-BOND said:
Good Work Brothers !!!!:laugh::laugh::laugh:
Keep it up.....:good::good::good:
But, if I am not wrong Xiaomi has not released any kernel sources and so all of our Devs are using only headers for compiling the ROM and so they are just changing the date in headers. Does this matters in performance, or stability?
Please do correct me, if I am wrong anywhere. I am always ready to learn new things.
Best Regards
BOND
Click to expand...
Click to collapse
xiaomi has not released kernel source dts right, but they are updating kernel while they update miui rom(secure source), devs are actually using that updated kernel which is made by xiaomi. Mokee on the other hand was using a old kernel and they were not updating , so I took the liberty to update it.
saurabhrck said:
xiaomi has not released kernel source dts right, but they are updating kernel while they update miui rom(secure source), devs are actually using that updated kernel which is made by xiaomi. Mokee on the other hand was using a old kernel and they were not updating , so I took the liberty to update it.
Click to expand...
Click to collapse
You did the right thing brother and thanks (I already pressed it for both of you) for keeping us updated.
So, you mean to say that Xiaomi has updated the kernel and sources but its secured only, not public. If it is like this, would you mind linking us to those sources, because there are so many ROMs waiting for some fixed kernel sources or if you can tell us what things have been fixed, can we use single SIM with this code "
Code:
setprop persist.radio.multisim.config none
".
We, all the users, can get several ROM with almost all utmost and best features available. Please do let me know about the kernel, best if we could talk on PM.
Best Regards
BOND
The Kernel gets updates by new Miui releases...i'll give a notable example to prove that !
Before v41.1 there isn't built in Zram implemented but with new kernel (v41.1+) there is Zram Support !
SuperDroid-BOND said:
You did the right thing brother and thanks (I already pressed it for both of you) for keeping us updated.
So, you mean to say that Xiaomi has updated the kernel and sources but its secured only, not public. If it is like this, would you mind linking us to those sources, because there are so many ROMs waiting for some fixed kernel sources or if you can tell us what things have been fixed, can we use single SIM with this code "
Code:
setprop persist.radio.multisim.config none
".
We, all the users, can get several ROM with almost all utmost and best features available. Please do let me know about the kernel, best if we could talk on PM.
Best Regards
BOND
Click to expand...
Click to collapse
The source is secure to xiaomi, they are not releasing to public as of now. Don't know whats the reason for this idiotic move. Anyway I don't have the source, like anyone else, I just repacked with proper module. dts all! Will update when xiaomi releases a new update
saurabhrck said:
The source is secure to xiaomi, they are not releasing to public as of now. Don't know whats the reason for this idiotic move. Anyway I don't have the source, like anyone else, I just repacked with proper module. dts all! Will update when xiaomi releases a new update
Click to expand...
Click to collapse
so is it repack of old ramdisk and new zimage... btw can u please give me link/info about the tool which u have used to repack kernel.. i tried to make kernel unsecure once but cant make it boot... kernel size reduced ~4 mb....
deadlyindian said:
Thanks for the Wake Up!!
Is no need to set permission at pronto wlan ?
Click to expand...
Click to collapse
pgreed said:
Is no need to set permission at pronto wlan ?
Click to expand...
Click to collapse
Nope its automatically set when phone boots...
What are the features of the kernel? This for mokee only? Any version??
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small (as density is around 400dpi!!) and after app is launched phone reboot.
pgreed said:
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small and after app is launched phone reboot.
Click to expand...
Click to collapse
ofcourse it will not work with unofficial version. unofficial version is based on cm11 source and uses that prebuilt kernel. you have to repack it separately for that. This one is only for mokee official release which uses mokee kernel/device files not from cm11, mentioned in OP!
saurabhrck said:
ofcourse it will not work with unofficial version. unofficial version is based on cm11 source and uses that prebuilt kernel. you have to repack it separately for that. This one is only for mokee official release which uses mokee kernel/device files not from cm11, mentioned in OP!
Click to expand...
Click to collapse
No it use the 8 May kernel! (is the sychost unofficial)
Shahi00 said:
The Kernel gets updates by new Miui releases...i'll give a notable example to prove that !
Before v41.1 there isn't built in Zram implemented but with new kernel (v41.1+) there is Zram Support !
Click to expand...
Click to collapse
So you mean Roms above 41.1 have zram implemented? before that it was not available?
Shahan_mik3 said:
So you mean Roms above 41.1 have zram implemented? before that it was not available?
Click to expand...
Click to collapse
Yep...even though we have 1GB RAM it is done that way !
I am very sure that V36 don't have ZRAM and V41.1 and above have it...that's the way they found to currect RAM management !
it causes a bit battery drain & and performance regression !
pgreed said:
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small (as density is around 400dpi!!) and after app is launched phone reboot.
Click to expand...
Click to collapse
link for mokee unofficial plz..
RohanAJoshi said:
link for mokee unofficial plz..
Click to expand...
Click to collapse
Because from Mokee site was deleted all unofficial and experimental version (I dunno why) I've upload the file elsewhere:
Shahi00 said:
Yep...even though we have 1GB RAM it is done that way !
I am very sure that V36 dont have ZRAM and V41.1 and above have it...thats the way they found to currect RAM management !
it causes a bit battery drain & and performance regression !
Click to expand...
Click to collapse
Also I wanted to know. How is it possible to get a stable cm/aosp Roms on Redmi but not on mi3?
Shahan_mik3 said:
Also I wanted to know. How is it possible to get a stable cm/aosp Roms on Redmi but not on mi3?
Click to expand...
Click to collapse
Our developer is good enough for tracking bugs that causes Random Reboots !!
Kra always did that (on previous phone too)
:good:

[UNOFFICIAL][ROM][NIGHTLY][5.0.2] Liquid Smooth Lollipop v4 d2tmo (01/29/2015)

Liquid Smooth Lollipop 5.0.2 for d2tmo (and other variants)
{
"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"
}
*** Disclaimer ***
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Please make a full backup of your phone before flashing this, especially if coming from Kitkat 4.4.4 builds (factory reset is then HIGHLY recommended!), if you loose something then it's on you, you've been warned.
Make sure you are running an updated modem firmware (latest is probably safest) and update your recovery to latest available before flashing this ROM (links at bottom).
Click to expand...
Click to collapse
Introduction
I am no expert developer by any means, in fact this is THE FIRST ROM I have built from public sources (thanks TheGeekyNimrod for all the help and inspiration!) ... well, at third attempt I was able to make it work with mobile data on d2tmo, hence why I'm sharing this with you
This ROM is now fully based on official Liquid Smooth Lollipop sources (LiquidSmooth tree from github) with hardware repos (all available) pulled from LiquidSmooth-Devices github tree, repo android_hardware_samsung comes from CM12 tree. Proprietary Vendor Samsung stuff was pulled from TheMuppets github tree.
To make it clear, I do not develop this ROM as modifying it nor I take credit for what's in it, no, that is the hard work (and well deserved credit) of LS maintainers. I build it from LS sources to provide more frequent LiquidSmooth Lollipop builds to all. On my part I was only able to fix source code of d2tmo which was broken, but all the changes in nightly releases you see here come straight from Liquid Smooth (or CyanogenMod in some cases).
Official LS-v4.0-Liquid-v4.0 d2 variants release links:
d2att
d2vzw
d2spr/d2bst
Features
Liquid Smooth Lollipop features based on nightly releases
Comes with latest CM kernel
fixed CM12 d2tmo baseband issue (d2tmo source code commited to LS)
Performance tab in Settings is enabled
LiquidSmooth menu
SuperSU included
SlimLauncher
SlimPIE navigation
Images
attached to this post
Installation Instructions
1. Full backup of whatever you have
2. Copy the ROM and gapps to your external SD card (links at bottom)
3. Perform a factory reset from recovery mode (this does NOT delete user data, but mind that PhilZ Recovery may and will wipe the SD card too...)
4. Flash the LS-LP-v4.0-Liquid_d2, then the gapps 5.0 package
5. Wipe Cache & Wipe Dalvik/ART cache
6. Reboot System - NOTE: First boot may take up to 10 minutes!!!
7. ENJOY!
Bugs
-Camera Video does not work, disable the stock Camera app and use Open Camera app for pictures
Troubleshooting
If you end up with no mobile data connection after flashing lollipop then try upgrading your modem firmware to newer revision. Alternatively you can first upgrade modem firmware before flashing lollipop, great repository for all d2tmo modem revisions is in this thread
To get ViperFX audio working you must change SElinux from Enforced to Permissive. You can do that by installing app SElinux Mode Changer - Currently this app doesn't work with BMS and LK lernels (works fine with inline CM kernels)!
If you get problems with GPS (especially if upgrading from 4.4) try using the play store app called GPS Status Test & Fix, in it hit Reset then Get Xtra Data then go outside and see if your phone is able to get a satellite lock. Once that done app can be uninstalled.
If you use F2FS partitions then you must flash the kernel that works for you after flashing this ROM! This ROM no longer contains a kernel supporting F2FS.
Official Development News
You can check news on development of Liquid Smooth on Google+:
Liquid Smooth Google+
Downloads
LS-LP-v4.0-Liquid_d2tmo ROM
LS-LP-v4.0-Liquid_d2att ROM
LS-LP-v4.0-Liquid_d2spr ROM
LS-LP-v4.0-Liquid_d2bst ROM
LS-LP-v4.0-Liquid_d2vzw ROM
LS-LP-v4.0-Liquid_d2cri ROM
gapps-lp-20141109-signed.zip
UPDATE-SuperSU (only if updating, 2.40 is included in ROM)
Philz Touch Recovery 6.58.9 d2lte (by RoryB)
TWRP Recovery (easiest to get from Flashify app through Download option)
Optional Kernels with above average performance:
BMS Kernel (min 01/06/2015) by Ed Chan
Lean Kernel (min. v10.0t1) by @Imoseyon
Shift-D2 Kernel by @rogersb11
Github sources
LiquidSmooth github
LiquidSmooth-Devices github
CM Kernel d2 github
TheMuppets Proprietary Vendor Blobs github
Changelog
Code:
2015/01/29
-merging commits
Code:
2015/01/27
-merging commits
2015/01/25
-merging commits
-Theme Manager removed
-AV libs updated
-requires a clean flash
2015/01/22
-merging commits
2015/01/21
-merging commits (SlimPIE navi added)
2015/01/20
-merging commits
-bundled with inline CM12 kernel (no more F2FS support!)
2015/01/18
-merging commits (Theme manager works, Dark Liquid theme not included yet)
2015/01/17
-merging commits (Themes)
2015/01/16
-baseband fingerprint set to match 5.0.2 android
-merging commits, e.g. Theme Manager inclusion (warning, this reverts to default white theme)
2015/01/15
-cleanup and merging commits
-SlimLauncher added to Homescreen options (warning, this resets the Homescreens!)
-d2tmo baseband fingerprint updated to latest stock official android 4.3 (was one by last before)
2015/01/14
-merging commits
2015/01/13
-Re-compiled ROM from all available Liquid Smooth Device sources
-Updated baseband fingerprint in d2tmo sources to latest available from CM12 vendor blob
-Advanced Reboot to Recovery now works
2015/01/12
-Edited mk files in CM12 d2tmo sources to enable baseband, tested working with UVUENC2
Credits
* LiquidSmooth team (especially Sean Hoyt and Tony Malagisi) for awesome Lollipop ROM and updates to sources
* TheGeekyNimrod for all the help and inspiration with source compilation
* jackeagle for awesome guide on building android from scratch
* RoryB for d2lte compilation of latest Philz Recovery (with f2fs support)
XDA:DevDB Information
LS-LP-v4.0-Liquid_d2tmo, ROM for the T-Mobile Samsung Galaxy S III
Contributors
fenixus, mtb3000gt
Source Code: https://github.com/LiquidSmooth/android
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: LiquidSmooth
Version Information
Status: Nightly
Current Beta Version: 4.0
Created 2015-01-12
Last Updated 2015-01-29
Reserved
Reserved
Thanks for this! downloading now and will report back if there are any issues. I know you are a new dev but are you looking for us to provide logcats and bugreports for you?
jonesin said:
Thanks for this! downloading now and will report back if there are any issues. I know you are a new dev but are you looking for us to provide logcats and bugreports for you?
Click to expand...
Click to collapse
Thanks and hopefully all works well for you just as it does for me
Yes, I am fresh meat totally. I'm afraid I wouldn't even know what to do with logcat and bugreports ...
Since this ROM is based on unmodified LS-LP-v4.0 sources, I believe the android OS problems would refer to code in LS tree, unless that is related to Samsung hardware strictly then it would point at CM12 source code. In short, unless CM or LS update their sources there is not much I can fix myself anyways, sadly.
I did this ROM build only to run true d2tmo and fix/enable the baseband issue in original CM sources (which didn't work, you'd get no baseband). After modification all works for me normally!
I promise to build a fresh copy from time to time, after LS-LP updates their code to keep it fresh
Way to go dude! Noob or not, you did some things to make it work that I still hadn't figured out in a couple of weeks of trying. A big tip of the cap to you on that one.
TheGeekyNimrod said:
Way to go dude! Noob or not, you did some things to make it work that I still hadn't figured out in a couple of weeks of trying. A big tip of the cap to you on that one.
Click to expand...
Click to collapse
Thanks man! Worth noting, that I wouldn't even start making it if not for your help with initial compilation errors
no more volunteers to test out LS-LP on d2tmo? It works great for me, no bugs whatsoever except for 2 mentioned in first post
Camera problem is widespread. The Advanced Reboot to Recovery might be my fixable by me if I get to look into it.
Will be uploading more screenshots soon. So far it's an awesome 5.0.2 d2tmo lollipop
Great, changing my TWRP to tmo, give it a run!:laugh:
Sugartibbs said:
Great, changing my TWRP to tmo, give it a run!:laugh:
Click to expand...
Click to collapse
go for it, I love it and it runs great!
I've been running LS-LP d2att builds (since 5.0.0) for weeks without issues, but got tired of editing build props to match my T999 after every update from d2att branch. The official d2tmo build from LS-LP (dated 12/21/2014) had a broken baseband, so it broke my heart too LOL ... This one here fixes it and is built from official sources, nothing else modified
fenixus said:
no more volunteers to test out LS-LP on d2tmo? It works great for me, no bugs whatsoever except for 2 mentioned in first post
Camera problem is widespread. The Advanced Reboot to Recovery might be my fixable by me if I get to look into it.
Will be uploading more screenshots soon. So far it's an awesome 5.0.2 d2tmo lollipop
Click to expand...
Click to collapse
I'd like to give it a run, are there any features that I would have access to that aren't included in the 5.0.2 Validus ROM I'm running?
I'm willing to test it out, hell I thought LiquidSmooth for d2 was done, since I hadn't seen a build since December, but I really appreciate you doing this! Do you plan on making weekly builds or just whenever you have time?
cresch07 said:
I'd like to give it a run, are there any features that I would have access to that aren't included in the 5.0.2 Validus ROM I'm running?
Click to expand...
Click to collapse
not sure, I don't know Validus ROM or what if has. This build here is built from full Liquid Smooth sources, so if you tried it in past then this is what it is . Mind that not all LS features (e.g. as known from v3.2) might be yet available in LS-LP-v4.0 as Lollipop is still fairly new and LS devs are updating it frequently.
Refer to screen shots I attached to first post to see what is in settings.
ad.hoc said:
I'm willing to test it out, hell I thought LiquidSmooth for d2 was done, since I hadn't seen a build since December, but I really appreciate you doing this! Do you plan on making weekly builds or just whenever you have time?
Click to expand...
Click to collapse
Thanks!
I can make those builds as often as official LS-LP releases some commits, once a week shouldn't be a problem, it takes about an hour to build it from sources and some minutes to upload it ... that is if no problems happen heh
fenixus said:
not sure, I don't know Validus ROM or what if has. This build here is built from full Liquid Smooth sources, so if you tried it in past then this is what it is . Mind that not all LS features (e.g. as known from v3.2) might be yet available in LS-LP-v4.0 as Lollipop is still fairly new and LS devs are updating it frequently.
Refer to screen shots I attached to first post to see what is in settings.
Click to expand...
Click to collapse
eh what the hell I'll give it a whirl lol. Downloading now!
cresch07 said:
eh what the hell I'll give it a whirl lol. Downloading now!
Click to expand...
Click to collapse
That's the spirit!
fenixus said:
That's the spirit!
Click to expand...
Click to collapse
Does the AOSP Keyboard work out of the box? I assume the camera doesn't, most LP ROMs have broken cameras for some reason.
cresch07 said:
Does the AOSP Keyboard work out of the box? I assume the camera doesn't, most LP ROMs have broken cameras for some reason.
Click to expand...
Click to collapse
Keyboard works, I like Liquid better than Valadius. FWIW, I use Swiftkey
cresch07 said:
Does the AOSP Keyboard work out of the box? I assume the camera doesn't, most LP ROMs have broken cameras for some reason.
Click to expand...
Click to collapse
works OK for me, no probs.Yes, camera broken is a widespread issue on d2. Disable the stock Camera app and download Open Camera from Play Store - it works very well for pics (just don't use tap to focus LOL), video recording is still broken.
fenixus said:
works OK for me, no probs.Yes, camera broken is a widespread issue on d2. Disable the stock Camera app and download Open Camera from Play Store - it works very well for pics (just don't use tap to focus LOL), video recording is still broken.
Click to expand...
Click to collapse
ok sweet continuing with flashing.
Loving it! Only 5.0 rom without problems for the t-mobile so far! Thanks. Hope to see more features and camera fix soon. For now ima stick with it. ?
Sent from my SGH-T999 using XDA Free mobile app

[BETA][5.0.2][LRX22G] AOSP Lollipop by tank0412 [A500CG][A501CG]

{
"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"
}
What is AOSP?
The Android Open Source Project is the original unmodified version of android. It's the base ROM that all other ROM's work on. There are a few changes from CAF (code aurora forums) and cyanogenmod to get this working for non-nexus devices like ours.
Bug list:
GPS & FM
What is working:
Media (IT IS FIXED) But Youtube can be dead
Audio (IT IS FIXED)
RIL (baseband) (IT IS FIXED)
Touchscreen xD
Image decoding
MTP
Webview
Camera
Sensors
Houdini (stable)
Wi-Fi
Rom features:
The main target of this rom is to provide opportunity to use custom roms for people, who have a screen freezes after bootloader unlock. (My AOSP rom use stock kernel)
First Lollipop AOSP rom
I used proprietary files from WW V3.24.40.87
I used device tree by quanganh2627 for building so this way community will get all fixes
How to flash it:
Step 1:
You should download files for flashing:
IMG file to flash it via drodiboot: (system_20032016.img)
XDA
Stock boot.img (boot_3.24.40.87.img)
http://forum.xda-developers.com/devdb/project/dl/?id=16818
ADB v1.0.32
https://drive.google.com/file/d/0B-Fin8UxrD6PUmN6SkVPMXR3UTA/view
Step 2:
1) Unpack archive with ADB and put image with rom and kernel there.
3) Then you should reboot your phone in the droidboot mode. (turn off you gadget then press Turn off button and volume + button)
Then go to the ADB folder and hold Shift + Right Mouse button and write this command:
Code:
Code:
fastboot flash system system_20032016.img
fastboot flash boot boot_3.24.40.87.img
Do not forget to wipe cache and data.
Bug reporting:​Attach logcat and detailed describe the issue. Send this to me (tank0412)
Credits:​@quanganh2627 (i used his device tree)
morrey from 4PDA for RIl fix
USING MY ROM AS BASE FOR YOUR ROM IS DENIED
IF YOU IGNORE IT, I WILL ASK MODERATOR TO DELETE YOUR THREAD
XDA:DevDB Information
AOSP Lollipop by tank0412, ROM for the Asus Zenfone 5
Contributors
tank0412
Source Code: https://github.com/tank0412/aosp_device_asus_a500cg
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 3.1
Beta Release Date: 2016-03-20
Created 2016-01-03
Last Updated 2016-03-20
Changelog(20032016):
Fixing video recording using camera app
Using AICP device tree by @quanganh2627 with my bring up to AOSP
Using another libmultidispaly source
Changelog(12032016):
Problem with hardware buttons was fixed
Fixes for second SIM (it have not tested yet)
Use old AOSP device tree from Github
Changelog(08032016):
Audio is fixed
Media is fixed (but Youtube can be dead)
RIL fix is applyed
Using img file for drodiboot
New bugs/issues:
Problem with Hardware buttons. (Maybe it is only on my phone) Use Back button only. Or install Xposed to enable sreen buttons.
Changelog(29022016):
RIL was fixed. Using otapackage. (flashable zip for TWRP)
Changelog(14022016):
Using blobs files from WW V3.24.40.87
Using stock kernel from WW V3.24.40.87 (boot_3.24.40.87.img file)
Using another RIL class (Unfortunatly, RIL is stay dead)
Changelog(06012016):
Wi-Fi was fixed
Houdini was fixed
Rom become much stable
Camera was totally fixed
Minor fixes for audio
Removed many apps from Asus stock.
Changelog(03012016):
Initial release
Good project thank you @tank0412
So this rom just 5.0 and cant update to 5.1.1 because u want to lock bootloader?
Great work again @tank0412 !
But I have question mark in my mind, which version of these AOSP roms will get stable release?
adamilmanns said:
So this rom just 5.0 and cant update to 5.1.1 because u want to lock bootloader?
Click to expand...
Click to collapse
Nope.
Many users which have a screen freezes asked me to create a rom, where bootloader unlock is not needed.
So i published this rom for them,
Personally i prefer to use 5.1.1.. Moreover i plan to build AOSP 6.0 Marshmallow.
this AOSP is something like training for me.
Parliamert said:
Great work again @tank0412 !
But I have question mark in my mind, which version of these AOSP roms will get stable release?
Click to expand...
Click to collapse
When quanganh2627 reply on my messages.
I need help of other devs to fix RIl and Houdini.
tank0412 said:
When quanganh2627 reply on my messages.
I need help of other devs to fix RIl and Houdini.
Click to expand...
Click to collapse
Yeah, Houdini makes it really tough for x86 users like us :/
Anyways, waiting for the progress mate!
We have to unlock bootloader to install this ROM or not ?
Ghi98 said:
We have to unlock bootloader to install this ROM or not ?
Click to expand...
Click to collapse
No.
What is the difference from 5.1.0?
TongYabgu said:
What is the difference from 5.1.0?
Click to expand...
Click to collapse
Look on the official android web site the changelog
TongYabgu said:
What is the difference from 5.1.0?
Click to expand...
Click to collapse
Read OP more carefully.
The main target of this rom is to provide opportunity to use custom roms for people, who have a screen freezes after bootloader unlock because these Rom use stock kernel.
Ghi98 said:
Look on the official android web site the changelog
Click to expand...
Click to collapse
I will
tank0412 said:
Read OP more carefully.
The main target of this rom is to provide opportunity to use custom roms for people, who have a screen freezes after bootloader unlock because these Rom use stock kernel.
Click to expand...
Click to collapse
I cant understand bootloader.Which roms we can unlock and which rom ıt can stay lock. and what is bootloader provide?
Pardon my english
tank0412 said:
Moreover i plan to build AOSP 6.0 Marshmallow.
this AOSP is something like training for me.
Click to expand...
Click to collapse
Is already possible?
Aquati said:
Is already possible?
Click to expand...
Click to collapse
I think it is, tank tryed to build a aosp 6.0 but no sucess, but now.....
thank you for dev work to continue fixing bugs and that the only rom we have that freezes can use @tank0412
Can i ask something? What is RIL and Houdini?
akiralee said:
Can i ask something? What is RIL and Houdini?
Click to expand...
Click to collapse
RIL is a baseband.
Houdini is a virtual machine which is vital for x86 chips.
Rom is very unstable due to it so you can not use me rom for daily driver.
Please fix WiFi and RIL bugs, thank you for work.

AOKP MM 6.0.1 unofficial + nightly + official

AOKP MM 6.0.1 unofficial + nightly + official
DISCLAIMER
You need to have an unlocked bootloader to use this ROM & kernel. Also I or any contributor in the software DOES NOT take responsibility of damages caused to your phone due to this ROM.
{
"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"
}
1. Copy ROM zip and gapps zip to sdcard
2. Flash any kernel which has recovery (Use the boot.img in this ROM - It has TWRP)
3. Reboot device and go to recovery by pressing Vol-UP when LED is pink
4. If coming from 5.1 or below ROM wipedata/factory reset your phone
5. Flash ROM zip
6. Flash OpenGapps ARM zip
7. Reboot and enjoy.
Official NIghtlies (automatically built every 4-5 days) :
Basketbuild
Unofficial Test Builds (will contain experimental changes for testing) :
Mirror : Uploaded.to
Mirror : self hosted
Gapps :
http://opengapps.org
We spend countless of hours doing this for next to nothing. Posts, views, and donations encourage me, and everyone else who helps out.
Donate to AOKP
Every donation is cherished and loved.
If you'd like to help contribute by writing code, feel free to stop by IRC and talk to us!
Latest merges on Gerrit
http://gerrit.aokp.co/#/q/sony+status:merged,n,z
Check out the ROM source on github. Open source, in the spirit of community kangage.
CREDITS
Thanks to all device maintainers of Sony devices on CM/AOKP/Omni/PA/PAC as everyone working on the device helps each other into making better ROMs.
Also thanks to Sony Mobile for being so helpful to developers.
XDA:DevDB Information
AOKP MM 6.0.1 unofficial + nightly + official, ROM for the Sony Xperia Z1
Contributors
championswimmer
Source Code: http://github.com/AOKP
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: AOKP
Version Information
Status: Alpha
Created 2016-02-09
Last Updated 2016-03-10
thanks for your works
Good work brother keep it up
I`ve found a unreleased cm13 build in your server can i use it?
built in twrp included in that version? @championswimmer
Luncer said:
Good work brother keep it up
I`ve found a unreleased cm13 build in your server can i use it?
built in twrp included in that version? @championswimmer
Click to expand...
Click to collapse
That cm13 build does not have TWRP.
feel free to download and use camera doesn't work on it though
@championswimmer can you tell me which kernel did you use as I have built bliss 6.1 and temasek 4.0 both based on Android 6.0.1 using cm13 kernel and everything is working except for WiFi.
markakash said:
@championswimmer can you tell me which kernel did you use as I have built bliss 6.1 and temasek 4.0 both based on Android 6.0.1 using cm13 kernel and everything is working except for WiFi.
Click to expand...
Click to collapse
Even camera ?
championswimmer said:
Even camera ?
Click to expand...
Click to collapse
@championswimmer No no camera is not working yet . Only working on aosp 6.0.1 built by crdroid but it lags a lot on camera. In my Roms I m having WiFi issue as it wont turn on. Can you help me to solve this issue if u have time?
I m sure its kernel issue as I flashed crdroid boot.img n WiFi worked but it stopped detecting my simcard.
Unfortunately I have bad news
1.In your aokp build camera doesn't work for me
2.Can't turn WiFi on
3.Auto brightness is buggy when screen turns on after phone lock (lock screen)
ROM Installed with twrp3.0.0
From cm12.1 nightly latest build
@championswimmer
Sent from my Xperia Z1 using Tapatalk
Luncer said:
Unfortunately I have bad news
1.In your aokp build camera doesn't work for me
2.Can't turn WiFi on
3.Auto brightness is buggy when screen turns on after phone lock (lock screen)
ROM Installed with twrp3.0.0
From cm12.1 nightly latest build
@championswimmer
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
-Sony camera blobs for marshmallow not released
-getting a dmesg log for OP would probably help him fix WiFi if it's a kernel issue
Sent from my C6903 using XDA Forums
Wifi shall be fixed in next release.
It is an selinux issue. It has been fixed.
We are working on open source camera
Hello, thanks for the rom.
The pros for now : very smooth, all my apps work, very good.
The cons (not repeat previous said) : i can't pair with my bluetooth car.
Thanks a lot to give MM to my Z1.
championswimmer said:
Wifi shall be fixed in next release.
It is an selinux issue. It has been fixed.
We are working on open source camera
Click to expand...
Click to collapse
New build up. Wifi and Bluetooth should be working now
championswimmer said:
New build up. Wifi and Bluetooth should be working now
Click to expand...
Click to collapse
I have installed the new version, and i have the message 'no sim card', the wifi doesn't activate.
Thanks
Same here WiFi and bt not working
Same here Wifi not activating and no Sim Card shown.
okay folks, next update will have wifi/sim/bt/cam all working BUT I am holding out on next update till some new changes get merged on CM.
There area lot of changes pending on CM tre. cdesai and kali- are testing a whole bunch of changes to move to using AOSP blobs instead of Sony vendor blobs for many parts.
You can check topic:aosp on review.cyanogenmod.org.
Once they are tested and merged, we will have a lot of things working then,
championswimmer said:
okay folks, next update will have wifi/sim/bt/cam all working BUT I am holding out on next update till some new changes get merged on CM.
There area lot of changes pending on CM tre. cdesai and kali- are testing a whole bunch of changes to move to using AOSP blobs instead of Sony vendor blobs for many parts.
You can check topic:aosp on review.cyanogenmod.org.
Once they are tested and merged, we will have a lot of things working then,
Click to expand...
Click to collapse
Great news buddy
If you want a tester im in[emoji6]
Sent from my Xperia Z1 using Tapatalk
Luncer said:
Great news buddy
If you want a tester im in[emoji6]
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
Just to correct the record: there is no such thing as AOSP vs Sony blobs for rhine devices. All blobs are vendor (Sony) blobs. What was switched is 3.4 to 3.10 kernel and CM tree to Sony AOSP tree. And they are attempting to make it fully work with Sony blobs. Note that the reason nothing works on AOKP is that they are using CM tree. Everything is already working on Sony AOSP tree, but camera's quality is horrible, not to mention freezes, simcard issues etc....
optimumpro said:
Just to correct the record: there is no such thing as AOSP vs Sony blobs for rhine devices. All blobs are vendor (Sony) blobs. What was switched is 3.4 to 3.10 kernel and CM tree to Sony AOSP tree. And they are attempting to make it fully work with Sony blobs. Note that the reason nothing works on AOKP is that they are using CM tree. Everything is already working on Sony AOSP tree, but camera's quality is horrible, not to mention freezes, simcard issues etc....
Click to expand...
Click to collapse
Thanks for being a smartass.
The reason Wifi/BT did not work in the AOKP builds is Selinux (using permissive kernel will make them work).
What I mean by AOSP blobs is using blobs extracted from FXP's aosp releases.
What was switched is 3.4 to 3.10 kernel and CM tree to Sony AOSP tree.
Click to expand...
Click to collapse
I don't even know what you mean by that.
Now next time you try to act like an encyclopedia, you better know the **** you are talking about.
championswimmer said:
Thanks for being a smartass.
The reason Wifi/BT did not work in the AOKP builds is Selinux (using permissive kernel will make them work).
What I mean by AOSP blobs is using blobs extracted from FXP's aosp releases.
I don't even know what you mean by that.
Now next time you try to act like an encyclopedia, you better know the **** you are talking about.
Click to expand...
Click to collapse
First, please forgi-i-i-ve me for offending your ego. Second, if you don't know what others are talking about (like the difference between cm and sonyxpdev device trees), then you might do well educating yourself. Third, extracting FXP blobs does not make them AOSP blobs, since AOSP stands for android OPEN source, as opposed to blobs being CLOSED/PROPRIETARY. For this reason the term "aosp blobs" is absurd. And fourth, xda rules require you to post sources for kernel and I haven't seen those anywhere in this thread or on AOKP github.
Best regards

[ROM][7.1][NOUGAT][NIGHTLY] Official Mokee Open Source Project

{
"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"
}
Code:
About
MoKee OpenSource is based on the Cyanogenmod. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion…
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Read here for developer application: http://www.mfunz.com/en/developer-application, you can host your unofficial MoKee builds on our server!
Features:
(I will mention only that which does not take into CyanogenMod)
Listview animation
Interpolation anmação listview
Update over the air can download the download website only incremental, it helps lower faster update and upgrade more easily:
Some icons and own layouts
Manager for Google services, so no need to use a large gapps, you can only download necessary at MokeeCenter
Ringtones, Alarms, Notification, UI sounds are all different CyanogenMod, thus bringing a beautiful charm to rom
bootianimation own
information integrated into MokeeCenter
Settings to add speed data network
Settings for navigation bar
Settings for Statusbar
Intelligent control settings to configure the newer apps and others.
What is the difference?
RELEASE: Tested after integrating new features, more stable than NIGHTLY. (Odexed builds)
NIGHTLY: Built daily with newest code and experimental features, might contain undiscovered bugs. (Deodexded builds)
HISTORY: Final odexded builds once a newer Android version is out and being built.
EXPERIMENTAL: Released when a new device is added or when a new feature is added for public beta testing and feedback. (Deodexded builds)
UNOFFICIAL: Maintained separately by individual developers, usually involves modification of shared code which cannot be merged (affects other devices), therefore maintained by the developer himself.
Note: We always test the shared code for bugs, however sometimes we may not be able to detect device specific bugs. If you have such issues, it will be better to report to the device maintainer.
Downloads oficiais:
TITAN
GAPPS (Google Apps)
RELEASES = stables / no problems
NIGHTLYS = ???
Changelog:
HERE
Installation mode :
To install the clean rom:
Download the rom
enter the recovery
make all wipes (expect internal storage)
choose zip from SD and install
you can use a gapps any of its taste since it is for android 7.0.x
or you can go MokeeCenter after starting rom, there you can download the small gapps integrated into the system and have a lighter and clean rom.
To install upgrade:
Method 1:
just download the complete package via OTA
enter the recovery
only to wipe cache and dalvik (optional, I do not)
install the complete package downloaded via OTA
Method 2:
Download the complete package over the air and go to install update
let install automatically for you
Method 3:
Download only incremental updates
for that you need to donate 30 CNY for the team to release the feature on the device directly
But you can do this update without donation
just go on the site and click below build itself where it is written (upgrade: OTA to MK ...)
there will be the incremental free for you, this will save on your data package or in your spare time.
Big Thanks @martincz for development
Please DONATE if you like my work
Click on my signature for donation.
XDA:DevDB Information
Mokee Open Source , ROM for the Moto G 2014
Contributors
[email protected], EsromG5
Source Code: https://github.com/MoKee
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Custom Recovery
Based On: Cyanogenmod
Version Information
Status: Nightly
Beta Release Date: 2016-11-22
Created 2016-11-22
Last Updated 2017-02-28
Reserved
prerooted?
Is the kernel really 3.10.x? @[email protected]
Ota working fine.
Enviado desde mi Pixel XL mediante Tapatalk
Pretty fast and the annoying mk tips&help shortcut from settings/launcher is gone
No 3.10. kernel ...
Gapps 7.1
I installed the gapps 7.1 and it worked perfect!
Hello, I have two questions:
-Is video recording working? (not with 3rd party apps)
-Battery backup is nice?
Thanks :good:
Not working feature!
I have noticed that the circle icon for the battery status does not work. I would be very pleased if you would fix it because I really want it. Otherwise, it is a great and stable rom
moto-john said:
I have noticed that the circle icon for the battery status does not work. I would be very pleased if you would fix it because I really want it. Otherwise, it is a great and stable rom
Click to expand...
Click to collapse
Video recording working?
maximuns said:
Video recording working?
Click to expand...
Click to collapse
Like a charm !
moto-john said:
Like a charm !
Click to expand...
Click to collapse
and how about battery? If it is good ill flash it
maximuns said:
and how about battery? If it is good ill flash it
Click to expand...
Click to collapse
Well.....In my opinion it is ok but you have to try and see. Also the best thing about the rom is that it has an ota updater. A huge plus for me. And ofcourse it is pretty stable. Came here after having issues with roms like beanstalk and crdroid.
moto-john said:
Well.....In my opinion it is ok but you have to try and see. Also the best thing about the rom is that it has an ota updater. A huge plus for me. And ofcourse it is pretty stable. Came here after having issues with roms like beanstalk and crdroid.
Click to expand...
Click to collapse
I think I'll give it a try, the gapps option after boot is awesome btw.
What build you have?
Thanks for the feedback man
maximuns said:
I think I'll give it a try, the gapps option after boot is awesome btw.
What build you have?
Thanks for the feedback man
Click to expand...
Click to collapse
I use the latest build 24/11. Glad to see I helped you. Btw I didnt find any option to install gapps through the system's app (mokee center) so I flashed them by my self
moto-john said:
I use the latest build 24/11. Glad to see I helped you. Btw I didnt find any option to install gapps through the system's app (mokee center) so I flashed them by my self
Click to expand...
Click to collapse
Oh ok, what gapps you used?
maximuns said:
Oh ok, what gapps you used?
Click to expand...
Click to collapse
I am not sure but I think that I used the pico 5/11 ones.
moto-john said:
I am not sure but I think that I used the pico 5/11 ones.
Click to expand...
Click to collapse
why 5/11?
maximuns said:
why 5/11?
Click to expand...
Click to collapse
I had those already downloaded. But I think that every version would work fine
moto-john said:
I had those already downloaded. But I think that every version would work fine
Click to expand...
Click to collapse
Ok thanks ill try it

Categories

Resources