SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimKat, ROM for the Moto E
Contributors
cybojenix
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2014-06-27
Last Updated 2014-06-27
Latest Build
V1.0, SlimKat 4.4.4 Build 6
Mobile data Doesn't work Confirmed
Auto Brightness doesn't work confirmed SlimRoms bug. It's only being polled every 10 seconds.
As far as I know, everything else is fine
I will upload the device folders at a later point closer to when SlimKat goes official for condor.
The kernel is pretty much stock, with minor edits to make camcorder work, and modules load.
Information and Requests
Firstly I'd like to massively apologise for not uploading this till now.
As some of you will already know, I have been somewhat ill due to the amount of work I have been putting in to my projects (no not for moto e).
To make up for this, I am posting a build now as a taster on the aosp qcom sources, rather than the newer caf based qcom sources. It's a daily usable rom, however later builds will have better performance.
I am also releasing a build of cm11 shortly.
XT1022 Is not supported as neither sim will work.
Now for the requests. at some point in the future (a few days, maybe a week), I will need access to the dual sim variant of the Moto E running stock. Ideally I will need access via TeamViewer to a windows or linux based pc with adb already set up, and an unlocked/rooted device that wants cm11.
I repeat.
Dual Sim is coming soon. Please stop asking
Thank you for being patient with me, but it will all soon pay off
from now on, If a question is asked that is answered already in the first page, or the last ten posts, or one that is easy to find with the search bar, please link this post to them.
Yay!! Thanks for your hard work! Will try this tomorrow
Just one question: Dual sim is supported?
Gogeta said:
Yay!! Thanks for your hard work! Will try this tomorrow
Just one question: Dual sim is supported?
Click to expand...
Click to collapse
Please read the third post.
Also SlimRoms does not support dual sim, and has no intention to any time soon.
Thanks for the work
Thanks for the work... can you send me patches for this..
xperiafan13 said:
Thanks for the work... can you send me patches for this..
Click to expand...
Click to collapse
No but I'll say the approach you should take to fix it.
To build, there is an error that shows from qcom/media. To fix that you had to patch a kernel header. Use git to find the commit the definition is made, and that will fix camera.
To fix bt, check the bt loading script in etc. You will notice there are two blobs missing. Running these blobs will show there is another blob missing.
What other bugs do you have?
cybojenix said:
no but i'll say the approach you should take to fix it.
To build, there is an error that shows from qcom/media. To fix that you had to patch a kernel header. Use git to find the commit the definition is made, and that will fix camera.
To fix bt, check the bt loading script in etc. You will notice there are two blobs missing. Running these blobs will show there is another blob missing.
What other bugs do you have?
Click to expand...
Click to collapse
ok thanks... Im check this... Thanks in advance
you rockss!!!
Mobile data
cybojenix said:
Mobile data untested but probably works (can't test as no sim in)
Auto Brightness doesn't work confirmed SlimRoms bug. It's only being polled every 10 seconds.
As far as I know, everything else is fine
I will upload the device folders at a later point closer to when SlimKat goes official for condor.
The kernel is pretty much stock, with minor edits to make camcorder work, and modules load.
Click to expand...
Click to collapse
Mobile data doesn't work, good work on everything else.
Kind Regards.
First of all congrats man
Here are some of the doubts
Since I have a Indian version moto e (dual sim) as per the given information it won't support so my doubt is if I install this ROM will at least one sim work I don't care about other sim and hate dual sim and do I need to replace any files from stock ROM?
Thanks in advance
cybojenix said:
Firstly I'd like to massively apologise for not uploading this till now.
As some of you will already know, I have been somewhat ill due to the amount of work I have been putting in to my projects (no not for moto e).
To make up for this, I am posting a build now as a taster on the aosp qcom sources, rather than the newer caf based qcom sources. It's a daily usable rom, however later builds will have better performance.
I am also releasing a build of cm11 shortly.
Now for the requests. at some point in the future (a few days, maybe a week), I will need access to the dual sim variant of the Moto E running stock. Ideally I will need access via TeamViewer to a windows or linux based pc with adb already set up, and an unlocked/rooted device that wants cm11.
Thank you for being patient with me, but it will all soon pay off
Click to expand...
Click to collapse
I've got the dual sim version.
Also, have team viewer, adb, fast boot, and a rooted stock ROM (not by choice) ready. Let me know when you need access.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
im always ready to help!!
Hetalk said:
I've got the dual sim version.
Also, have team viewer, adb, fast boot, and a rooted stock ROM (not by choice) ready. Let me know when you need access.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
cybojenix said:
Firstly I'd like to massively apologise for not uploading this till now.
As some of you will already know, I have been somewhat ill due to the amount of work I have been putting in to my projects (no not for moto e).
To make up for this, I am posting a build now as a taster on the aosp qcom sources, rather than the newer caf based qcom sources. It's a daily usable rom, however later builds will have better performance.
I am also releasing a build of cm11 shortly.
Now for the requests. at some point in the future (a few days, maybe a week), I will need access to the dual sim variant of the Moto E running stock. Ideally I will need access via TeamViewer to a windows or linux based pc with adb already set up, and an unlocked/rooted device that wants cm11.
Thank you for being patient with me, but it will all soon pay off
Click to expand...
Click to collapse
i do have Teamviewer, Windows 8.1 (ADB), Moto E XT1022 (Stock, Rooted, TWRP)
Hetalk said:
I've got the dual sim version.
Also, have team viewer, adb, fast boot, and a rooted stock ROM (not by choice) ready. Let me know when you need access.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same as above here ^
Contact anyone of us who are online.
not even single sim working in Moto E XT1022
cybojenix said:
Please read the third post.
Also SlimRoms does not support dual sim, and has no intention to any time soon.[/Q]
woah woaaah woaahhh.... its awwwesommmeeee... loved it but sad thing not even single sim working
atleast make single sim to work!!!
anyway awesome work :good::good::good:
Click to expand...
Click to collapse
iblaziner786 said:
cybojenix said:
Please read the third post.
Also SlimRoms does not support dual sim, and has no intention to any time soon.[/Q]
woah woaaah woaahhh.... its awwwesommmeeee... loved it but sad thing not even single sim working
atleast make single sim to work!!!
anyway awesome work :good::good::good:
Click to expand...
Click to collapse
Slim builds are always awesome.
I use them a lot on my gnexus.
Sent from my XT1022 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok thankyou to all the people who replied regarding dual sim. You truly are the best community I've been in so far.
Once I've got cm11 rolling I'll contact one of you to set up a build.
I know the fact that slim doesn't support dual sim is a disappointment, so here's the deal. If I get hold of a dual sim moto e, I will bring support for dual sim devices to Slim (probably unofficially).
cybojenix said:
Ok thankyou to all the people who replied regarding dual sim. You truly are the best community I've been in so far.
Once I've got cm11 rolling I'll contact one of you to set up a build.
I know the fact that slim doesn't support dual sim is a disappointment, so here's the deal. If I get hold of a dual sim moto e, I will bring support for dual sim devices to Slim (probably unofficially).
Click to expand...
Click to collapse
Exactly, you can do a weekly(or bi-weeklies) unofficial builds and post them in the same thread.
That would be awesome.:good:
Ok before any mods start messaging me/closing thread, I forgot to push the patched kernel source last night. I get on a computer in an hour or so. Sorry for the inconvenience.
Does it support dual Sim variant as no ROM support dual sim variant
Sent from my XT1022 using XDA Free mobile app
gtsfreak said:
Does it support dual Sim variant as no ROM support dual sim variant
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Please read first page or at least few previous posts always before posting. It should answer your questions.
Related
Guardian Rom by x942Thanks to:
The Guardian Project
Cyanogen Mod
Android Open Source Project
Open-Pdroid Project
Any one else I am missing
Click to expand...
Click to collapse
What is Guardian Rom?
Guardian ROM is a custom android ROM multiple devices. The ROM is completely Open Source and based off of the CM10.1. While this build is stable because it's based on CM10.1 it is a preview so please expect some bugs, & missing features (i.e updater).
What Features does Guardian Rom have?
Kernel is hardened with SecDroid Tweaks.
ROM is patched with and includes OpenPdoird for
permissions management.
Guardian Project apps are pre-installed – These include Orbot (Tor), Gibberbot (Secure IM),
and more.
CSSimple and OStel (https://guardianproject.info/wiki/Ostel) are included as replacements to the
built calling apps. providing encrypted communications.
If encryption is enabled and password is entered wrong 10 times the phone wipes user data.
Click to expand...
Click to collapse
Coming Soon:
Including support for Deniable Encryption (similar to Truecrypt hidden volumes).
Including GRSecurity for exploit mitigation and more secure phone.
Including SQLCipher to ensure all data is encrypted whenever possible
Including a customer “app store” for our repos.
Different lockscreen pin and Pre-Boot authentication password.
Auto-Prompt for encryption setup on first boot.
Click to expand...
Click to collapse
How to use:
Simply flash the flashable zip through your favorite custom recovery. (TWRP is recommended as it supports encrypted devices). Once flashed you should enable Full Disk Encryption by doing the following (may very depending on device):
Code:
Settings --> Security ---> Password [enter a strong 8-16 char password]
Than
Code:
Settings --> Security ---> Encryption --> Enable Encryption
Downloads:Downloads are over here.
Please verify the downloaded file with the attached GPG signature to ensure is is a legit copy.
GAPPS
Google Apps are NOT included and before you flash them you may want to read this article.
UPDATES:
Since this is a preview I have not had a chance to remove or modify the CM Updater. Please do NOT use it as you will be flashing a stock CM10.1 build and not Guardian Rom. This will be fixed shortly.
Reserved.
you could cherrypick some stuff from here
selinuxproject.org/page/SEAndroid
baz77 said:
you could cherrypick some stuff from here
selinuxproject.org/page/SEAndroid
Click to expand...
Click to collapse
I may use SeAndroid. Right now I am focusing on the encryption side of things instead of the exploit mitigation side. That will come later.
Been following your work on sec Droid, this looks like a very very good start! May I know which version of CM that you used for this? Or it is based on the latest repo when you built it.
Thanks!
Flowed from my Nexus⁴
azrash said:
Been following your work on sec Droid, this looks like a very very good start! May I know which version of CM that you used for this? Or it is based on the latest repo when you built it.
Thanks!
Flowed from my Nexus⁴
Click to expand...
Click to collapse
Awesome! Thanks! It's is based off the latest repo. I simple pulled and than modified the sources. I am currently getting some hosting for our own repo and Tor Hidden service for downloading. Stay tuned much more to come.
TimeAndroid said:
Look'in good, might try.
Click to expand...
Click to collapse
The next build will have an AOSP 4.2.2 base with Mobiflage built in. Also Lock screen PIN and Pre-Boot PINs are now separated. So you can use a simple 4 digit pin on the lock screen and a 32 character pin at boot.
Also for more security you have to passwords one for the "outer volume" which you use as you daily usage and one as "hidden volume" which is your hidden os. You use the second for anything sensitive. That way if an attacker tries to force you to give up your password you just give up the outer volume (decoy) password. There is no way to prove the hidden volume exists.
Encryption also uses AES-256-XTS now instead of AES-128-CBC. Better key length and protection against watermarking attacks.
EDIT: If anyone wants early access please PM. The build is not ready for prime time as there is no GUI for encryption but can be used as a daily driver.
SecUpwN said:
No, I'm sure you're right. But since he explicitly stated that he won't build an ('unofficial') AOKP version, I'm looking for a way to get in the favor of the securiry modifications without gaving to switch to another ROM. It's just that AOKP has so many cool simplifications compared to CyanogenMod, I'd like to avoid a switch backwards. Maybe he could create an unsupported AOKP version every month? Possible?
Click to expand...
Click to collapse
Or you could compile your own. Not trying to sound like a d**k but he had already stated numerous times he is only doing Cm base and yet u and others keep saying do this for aokp. There is a reason he is using cm as a base.
Sent from my Nexus 4 using Tapatalk 4 Beta
DontPushButtons said:
I'm guessing the modifications he has been making go a little further beyond a flashable zip. Otherwise he would've done that instead of making a whole rom around privacy.
Could be wrong..
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes. I custom kernel is needed at the very least. Not to mention removal of Google Apps and tweaked UI for encryption (mobiflage). All of these are OS level tweaks and cannot be made into a ZIP.
droidkevlar said:
Or you could compile your own. Not trying to sound like a d**k but he had already stated numerous times he is only doing Cm base and yet u and others keep saying do this for aokp. There is a reason he is using cm as a base.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
This. AOKP will NOT be supported. EVER. If anyone wants a different base download the source code from my github and compile it yourself. Build documentation is on there. Furthermore AOKP and CM10.1 are both great roms, however there are too many variables. Both have a ton of unneeded binaries and settings. We cannot guarantee security are these builds. We choose CM10.1 because it's fully open source and has fewer complications then AOKP. On NEXUS devices we are using AOSP modified with our security tweaks. On non-nexus we use CM10.1 for now for simplicity.
I am hoping with the recent Google Edition devices it will be easier to port/compile AOSP onto those devices.
TL;DR:
WE WILL NEVER OFFICIALLY SUPPORT AOKP.
Thanks for understanding.This message is only meant to stop these requests, not to be rude so please don't take it that way.
Cleaning
This thread is in the DEVELOPMENT section. And is for the "Guardian Rom [Secure] [Privacy] [Preview]".
If you need to report an issue or bug then READ THIS POST ABOUT BUG REPORTS
Keep ALL posts aimed at the ROM development.
This thread is NOT A Q&A thread.
So don't ask why the WiFi won't work, post a LOGCAT of the actual event or it did not happen.
I have cleaned this thread.
If you repeatedly make junk posts, then INFRACTIONS will follow.
~JAB
Hey @x942, where is our Android 4.3 version of this funky ROM?
SecUpwN said:
Hey @x942, where is our Android 4.3 version of this funky ROM?
Click to expand...
Click to collapse
We are working toward this. The issue we are having is that while 4.3 is latest 5.0 may be just around the corner. We don't want invest a ton of effort just to have re-port everything to 5.0 if it's released 2-3 months from now. That's not to say 4.3 won't happen. It's just we are focusing on adding more security. For now stable is 4.2.2.:good:
Am I missing where to find the flashable zip?
Sent from my Nexus 4 using xda app-developers app
Will this ever come to a Samsung Galaxy 3, or are your plans only for Nexus devices?
koz said:
Will this ever come to a Samsung Galaxy 3, or are your plans only for Nexus devices?
Click to expand...
Click to collapse
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Request
Hi,
Please add the new moto g xt1032 to your list of planned devices - it would be a great way to get more people secured as it is a very popular handset
Thanks for all your hard work!
x942 said:
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Click to expand...
Click to collapse
Has this ever been developed for the Galaxy S3? I haven't been able to find a download anywhere...
@X942 gaurdian rom sounds very interesting to me. would also like the att slll i747 to be added on list for consideration for dev.
am not a dev myself.
thank you for your work/time/energy. :thumbup:
err on the side of kindness
good
Sent from my Nexus 4 using XDA Premium 4 mobile app
x942 said:
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Click to expand...
Click to collapse
I cant find a download for the Note 3 ROM. The only thing I read about it is an update on http://shadowdcatconsulting.com/blog/ saying that support will come soon.
Hey guys so this was brought to my attention by another user, @daftlush . Dating back to my OGEvo4g we were conditioned to believe Update PRL/Profile could not be done in AOSP, specifically on Sprint. This was somewhat debunked when the Nexus came out to Sprint because it had this feature in AOSP. @daftlush brought up in another thread asking about this and I assumed like before it just wasnt in AOSP, except Google has it working. So I wanted to compile a list of roms that are fully Sprint functional that include Update PRL/Profile.
First, I noticed on roms where it does work it will finish Activating Data you dont have to press skip. I dont know if it is just a coincidence but the one rom I found this feature actually working, I did not have to hit skip once i saw LTE instead it finished and moved onto the next step.
If you know of a rom where this does work, please list it and I will update the list. I am hoping we can track down the necessary code to get this fully working on all AOSP roms.
UPDATE: 01/11/14
I was able to get the fix from team slim it is located in the second post
UPDATE 01/09/14
Newest Slimkat build has the feature confirmed working. (http://forum.xda-developers.com/showpost.php?p=49278373&postcount=3240)
I have sent a PM to the OP of the AOSPA thread to see if they can work on getting this going as well. Still waiting to hear back from AOKP since the first conversation. Lets help spread this info so we can enjoy our hammerhead! If you can help find the code needed on gerrit please let me know I have been looking but I dont have much experience in reviewing code, if it is found I can update post #2 with the detail for all devs to utilize.
UPDATE 01/06/14
I have passed on this information to a few days and so far, AOKP, SLIM, CNA have stated they will look into the code from Vanir and Cyanogenmod to see what they did in order to get these options working. Slim says it is a current WIP for them and last I talked to someone from AOKP they said they would look into it and we should have it working. CNA also said they would look into it.
Unfortunately OMNI doesnt look to be working on it, I did not get this info from someone on team omni but many posts have stated they dont want to include any closed source items from stock, i didnt know sprint hidden menu and prl/profile updates were closed source but that is unfortunate as I know a lot of us Sprint users would love to run OMNI, but for me no prl/profile updates make it hard to run as a DD (fellow Sprint users probably understand as prl updates sometimes fix our data issue)
Full working on Sprint (Activate data works, Update PRL/Profile works):
Vanir
Cataclysm
Stock Google
Anything based off Stock Image
Cyanogenmod
CM Based Variants
Slimkat (fixed per dev http://forum.xda-developers.com/showpost.php?p=49226687&postcount=3155) / now confirmed working as of 1/9 (http://forum.xda-developers.com/showpost.php?p=49278373&postcount=3240)
BobcatRom - confirmed working (http://forum.xda-developers.com/showpost.php?p=49284722&postcount=18)
AOKP 1/12/14 (http://forum.xda-developers.com/showpost.php?p=49340913&postcount=306)
AOSPA - the fix has been merged but no build put out since then, this is as of 1/11/14 future builds after this date should work (http://forum.xda-developers.com/showpost.php?p=49343381&postcount=303) (http://forum.xda-developers.com/showpost.php?p=49346234&postcount=313 confirmed Update PRL/Profile works as well)
Custom Raskat by @soccerfan6768 (http://forum.xda-developers.com/showpost.php?p=49412543&postcount=2624) he said hell pass on the fix to the raskatdevs for officials
Purity
Sprint data works w/o APN hack, but no update PRL/Profile(once you see LTE icon you must hit skip on activating data):
OMNI
Codename Android
Sprint data works with APN hack only:
PSX
First and foremost I want to give a very big THANK YOU to @cordell12 for putting up with my constant nagging surrounding this subject and to @kufikugel from slimteam for figuring it out. I hope cordell12 doesnt mind me posting their fix.
Per cordell12 "yes, it is blobs. those who do not have it(prl/profile update) working are using blobs from google website. those who do(prl/profile update) are using extracted blobs from stock build/device"
here is a link to the slimteams gerrit with the fix that made it work on their rom: https://gerrit.slimroms.net/#/c/1714/
i was told by another member that this fix also needed to be implemented https://gerrit.slimroms.net/#/c/1717/
Help me spread the word to the devs of non-fully functional roms on sprint.
So i have updated the list again today, CM has it working as do a few others. I am not good with git or code, does anyone know what the commit is that fixes this so i can help spread the word to other devs?
whats the sprint hack?? im on sprint and i always wanted to try rastakat rom
P.Mobile said:
whats the sprint hack?? im on sprint and i always wanted to try rastakat rom
Click to expand...
Click to collapse
The sprint. Zip file that allows you to get past the welcome screen on some roms and have data connection enabled, i few roms will be unusable if you don't flash this after the rom and the gapps,i think
Sent from my Nexus 5 using Tapatalk
On the fully compatible ROMs are you also able to access the Sprint Hidden Dialer Menu(*#*#3282#*#*)? I really hope Sprint users can get full compatibility across all ROMs.
AndrasLOHF said:
On the fully compatible ROMs are you also able to access the Sprint Hidden Dialer Menu(*#*#3282#*#*)? I really hope Sprint users can get full compatibility across all ROMs.
Click to expand...
Click to collapse
The roms that are fully working, have the hidden menu. I just checked for you and it does work, this is only tested on those that PRL/Profile update work!
MY goal of this thread is to figure out what code is missing from the roms so we(sprint users) can enjoy all the goodies.
P.Mobile said:
whats the sprint hack?? im on sprint and i always wanted to try rastakat rom
Click to expand...
Click to collapse
The Sprint hack enables the correct APNs for Sprint so you can have data, otherwise you get no data which makes our phones useless
Just a heads up, Update PRL/Profile is FIXED on SlimKat and will be included in our next Official build :good:
cordell12 said:
Just a heads up, Update PRL/Profile is FIXED on SlimKat and will be included in our next Official build :good:
Click to expand...
Click to collapse
That's great, Thanks. I have a Sprint-purchased Nexus 5 and I haven't ran into any problems so far, which is amazing. I'm glad it's the same phone hardware-wise as the unlocked version.
nerv8765 said:
That's great, Thanks. I have a Sprint-purchased Nexus 5 and I haven't ran into any problems so far, which is amazing. I'm glad it's the same phone hardware-wise as the unlocked version.
Click to expand...
Click to collapse
I really hope this catches on, one device = all providers.
cordell12 said:
I really hope this catches on, one device = all providers.
Click to expand...
Click to collapse
I do too, it's so nice to know that I have the option of going with a prepaid service like T-Mobile or At&t. Basically, anything except Verizon will fully work (and I don't really miss Verizon any.)
thanks to this thread i found about Vanir and will never turn back to anything else!
Tons of great info here, thanks OP!
Thank you cordell for giving us an update!!
I have sent a message to the hammerhead maintainer of AOSPA to see if they will also implement this "fix"
Has anyone been able to see the code from either CM, Slim, or Vanir? I want to update post #2 with that info so the other devs can easily access them.
BobcatRom works flawlessly on sprint, and is an amazing ROM. I highly recommend people to check it out. Its beautiful.
sent from my Hammerhead Nexus
CRIME INC. said:
BobcatRom works flawlessly on sprint, and is an amazing ROM. I highly recommend people to check it out. Its beautiful.
sent from my Hammerhead Nexus
Click to expand...
Click to collapse
can you confirm Update PRL/Profile work?
Circaflex said:
can you confirm Update PRL/Profile work?
Click to expand...
Click to collapse
Yes I can:thumbup:
sent from my Hammerhead Nexus
CRIME INC. said:
Yes I can:thumbup:
sent from my Hammerhead Nexus
Click to expand...
Click to collapse
thanks added to the list
cordell12 said:
I really hope this catches on, one device = all providers.
Click to expand...
Click to collapse
@cordell12: is it at all possible for you to link me to the changes on gerrit that were made to get this feature working, i have receieved answers from a few other rom devs asking me for the code, i tried looking on slimsgerrit but i have no experience in reviewing code and i am not sure what i am looking for exactly. thank you for any help you can provide.
CM12.{0,1} (Lollipop) official/unofficial builds for the Droid 4
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0/5.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
These are WIP builds of porting CM12.{0,1} to the Droid 4 (and also other devices using the same device/motorola/omap4-common-infrastructure). They probably won't work, so don't expect too much. Use on your own risk!
Builds:
Last official build:
http://droid.cs.fau.de/cm-12.1/official/
Old manual builds:
http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/
Changes (only device/family specific, CM base is always synced before build and contains more changes):
2015-04-16:
Switched CM build-target, new nightlies will now be 12.1: http://review.cyanogenmod.org/#/c/94693/
2015-02-01:
No more unofficial builds! See: http://review.cyanogenmod.org/#/c/87596/
2015-01-28:
Mobile data fixes
Remaining com.android.phone crashes on VZW finally fixed (thanks @joojoobee666)
2015-01-24:
Fixed sw-keyboard popup when hw-keyboard is used (thanks @joojoobee666)
Fixed reboot to recovery
Fixed sepolicy for whisperd (dock service)
2015-01-22:
Fixed su-permissions
Crashes on Verizon most likely fixed, please report back
2015-01-20:
Fixed flashlight
2015-01-18:
SELinux updates.
This requires manual action for applications to continue being able to access their own files when upgrading from 2014-01-14 or 2014-01-15 (older versions are fine)!
Due to SELinux-bugs in 2014-01-1{4,5}, you have to relabel your data-partition on the first boot when upgrading from 2014-01-14/-15. This only needs to be done once. To do this, enable adb/usb debugging and grant root to adb (both in developer settings) and execute via an adb shell:
Code:
su -c 'for i in /data/*; do echo "${i}"; restorecon -DFrv "${i}"; done; sync; reboot'
2015-01-1{4,5}:
More fixes for {,umts_}spyder
sepolicy updates
GSM fixes
notable CM changes: su integration fixed
2015-01-11:
Updated SELinux policies (mostly for spyder/umts_spyder)
Added kernel stability fixes
Video decoding fixes
2015-01-09:
Enabled SELinux enforcing
Add SELinux-policies for motorola services
Enable ro.telephony.get_imsi_from_sim on VZW devices (thanks @joojoobee666)
2015-01-02:
Sync CM changes
2014-12-23:
Fixed stock camera
2014-12-22:
Sync CM changes
Fix build due to P2P changes (fix pushed into CM)
Enabled security for adb (keys/not root by default)
2014-11-30:
Added APN fixes for CDMA/LTE
Enabled multiuser mode (might not work yet)
Last update for a couple of weeks
2014-11-27:
Fixed graphics glitches
2014-11-26:
Fixed HW video-decoding
Enabled doze mode (no pickup sensor in the devices!)
CM resync as always
2014-11-23:
Probably fixed mobile data on LTE
Fixed WiFi-tethering
2014-11-22:
Requires a recovery supporting SELinux
What's working:
Phone (tested on Verizon and on GSM/UMTS in Europe)
Mobile data (at least on GSM/UMTS in Europe)
WiFi
WiFi-tethering
GPS
Camera
Playback of DRM-protected content (using Widevine from OnePlusOne)
What's not working:
Probably most everything else, including, but not limited to:
Some connectivity issues (should be solved now)
Data encryption
Gapps (CM-12.0):
Dhacker29 provides gapps for Lollipop:
http://d-h.st/YQG
http://d-h.st/jzr
http://droid.cs.fau.de/cm-12.0/gapps/ (Mirror)
Gapps (CM-12.1):
https://github.com/cgapps/vendor_google/releases/
Installation:
You need a new recovery supporting SELinux
An updated Safestrap (3.75) which supports SELinux can be found here: https://github.com/stargo/android_packages_apps_Safestrap/releases/tag/v3.75
Please read the instructions on how to install this version and follow the order of the steps in it.
GSM users:
To use this CM12.{0,1}-ROM on GSM-networks you should install Mentor.37's GSM patch
Source / Repositories:
maserati device-support: https://github.com/CyanogenMod/android_device_motorola_maserati
omap4-common device-support: https://github.com/CyanogenMod/android_device_motorola_omap4-common
omap4-common kernel: https://github.com/CyanogenMod/android_kernel_motorola_omap4-common
local manifest to build cm-12 for the Droid 4: http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/local_manifest.xml
XDA:DevDB Information
CM 12.{0,1} on Motorola Droid4, ROM for the Motorola Droid 4
Contributors
stargo, Hashcode, Dhacker29
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Created 2014-11-23
Last Updated 2016-02-16
thank you @stargo, I am so pleased to see this thread, I was wondering when this thread is going to appear. Looks like I will continue to cling onto my droid 4 for a while, no virtual keyboard can beat a droid 4 keyboard.
Is data encryption enabled by default like on the nexus 6? I read that it greatly reduces the performance of the device. I meant this: http://www.xda-developers.com/android/disable-data-encryption-nexus-6/
Once again, thank you so much for your efforts in keeping this device alive.
sharptv said:
thank you @stargo, I am so pleased to see this thread, I was wondering when this thread is going to appear. Looks like I will continue to cling onto my droid 4 for a while, no virtual keyboard can beat a droid 4 keyboard.
Click to expand...
Click to collapse
Is data encryption enabled by default like on the nexus 6? I read that it greatly reduces the performance of the device. I meant this: http://www.xda-developers.com/android/disable-data-encryption-nexus-6/
Click to expand...
Click to collapse
No, data encryption is not enabled by default (and still doesn't even work for us).
Cheers,
Michael
Flipping sweet thanks y'all rock i love xda
Cast Screen
Hey stargo. thanks a lot for this! :good:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Thanks again!
G'day,
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Or do you mean boot to stock ROM, in stock slot?
I'm guessing it's the former, but I'd like to be sure before taking the plunge =)
thanks for your work! I gave the 2011 version a run over the weekend, it worked pretty well all things considered =)
gabhroo123 said:
Hey stargo. thanks a lot for this! :good:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Thanks again!
Click to expand...
Click to collapse
May not ever work, IIRC, chromecasting the screen requires hardware we just don't have. :[
Shobai said:
G'day,
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Or do you mean boot to stock ROM, in stock slot?
I'm guessing it's the former, but I'd like to be sure before taking the plunge =)
thanks for your work! I gave the 2011 version a run over the weekend, it worked pretty well all things considered =)
Click to expand...
Click to collapse
assuming that cm11 is currently installed in your stock slot and you want to update to the new test safestrap by stargo:
uninstall the existing safestrap using the original safestrap, for instance, if the existing safestrap is 3.73, you should install safestrap 3.73 and uninstall the recovery.
DO NOT REBOOT YOUR PHONE IN THE PROCESS
after you have uninstalled the existing recovery, uninstall safestrap(3.73), and then install the new safestrap by stargo, and install the recovery.
your safestrap is now updated, and nothing will be wiped.
YOU MUST NOT REBOOT YOUR PHONE DURING THE PROCESS, you can only reboot after a recovery has been installed.
hope you find this useful
thelolotov said:
May not ever work, IIRC, chromecasting the screen requires hardware we just don't have. :[
Click to expand...
Click to collapse
It need some kernel changes... but it should work...original gnex have the same cpu/gpu and they make it work... @lucize was seeing that but i dont know what happend with that
---------- Post added at 07:38 AM ---------- Previous post was at 07:37 AM ----------
By the way....thanks michael for your great work!...please make a donation link to send you some beer money!
Cheers, sharptv, much obliged =)
gabhroo123 said:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Click to expand...
Click to collapse
Yes, our GPU driver does not support WFD. And in contrast to the GNEX, Motorola added much stuff to our version, so it's not easy to sync it back with the upstream kernel. Last time I tried that, I ended up with a non-working display and couldn't figure out why...
Shobai said:
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Click to expand...
Click to collapse
Just boot to whatever you currently have installed in the stock slot. And I have to underline what @sharptv said, never reboot your phone in the process (it might work when you have the stock ROM in the stock slot, but it will surely break in every other case).
Cheers,
Michael
Will cm12 be pre-rooted in future? I can't seem to find anything solid on this, hopefully someone will be able to shed some light on this.
This App Camera work fine: https://play.google.com/store/apps/details?id=com.radcam.camera
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
sharptv said:
Will cm12 be pre-rooted in future? I can't seem to find anything solid on this, hopefully someone will be able to shed some light on this.
Click to expand...
Click to collapse
See this thread: http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
Download and install with recovery
I can confirm that at least on my phone that LTE is working. Great work .
flash these zips in recovery for root i got the from my nexus 7 root toolkit
HOPE IT WORKS FOR YOU :good::cyclops:
TheXG6HD said:
I can confirm that at least on my phone that LTE is working. Great work .
Click to expand...
Click to collapse
Yay! Thanks for confirming
It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845
Cheers,
Michael
stargo said:
Yay! Thanks for confirming
It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845
Cheers,
Michael
Click to expand...
Click to collapse
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<
It does come up a lot quicker, however.
thelolotov said:
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<
It does come up a lot quicker, however.
Click to expand...
Click to collapse
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
stargo said:
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
Click to expand...
Click to collapse
LTE was working on first build, just took 10+ mins to connect then worked good.
Sent from my XT907 using Tapatalk
stargo said:
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
Click to expand...
Click to collapse
The deal is, the data works at first, then at random intervals it breaks and needs to be manually reset. I'm travelling right now so I can't really risk using CM12 right now, but I'll get you some logs when possible. JJB is having the same issue, I'll ask him to try and get you some details.
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Website:
http://androidarmv6.github.io/
Source code:
https://github.com/androidarmv6
You can watch development as it progresses, or you can sign in and participate here:
http://review.androidarmv6.org/#/q/status:merged
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
sent from my towelrooted LG L34C using daishi4u bumped twrp 2.8.3.0 and bumped key-boot-recovery kernel
...as he looked back on the sleeping giants, exhausted from their long journey, the wizard Androidmeda new that he had taught them all that he could, and they had all that they needed. But he also knew that they would never be able to survive crossing the mountains into the new land. Only their child would be able...
Well I guess this is it my brothers. Seems that all has been tried, and CM-12 will not be released for armv6 devices. But many thanks to our devs for trying. It's been a long run. Amazing, just amazing.
ibub said:
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Source code:
https://github.com/androidarmv6
ROMs:
http://jenkins.androidarmv6.org
sent from my towelrooted LG L34C using tapatalk
Click to expand...
Click to collapse
Congrats! Nice preface wording, bro! :good:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Dovidhalevi said:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Click to expand...
Click to collapse
Thanks, link updated to View/All.
sent from my towelrooted LG L34C using tapatalk
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
D3oDex3D_AyusH said:
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
Click to expand...
Click to collapse
Just to be clear, this is not my work. Androidarmv6 team (mainly androidmeda for p500) compiles these ROMs. Thanks belong to them (him).
sent from my towelrooted LG L34C using tapatalk
Wut? ART isn't compatible with ARMv6, AFAIK.
Casserole said:
Wut? ART isn't compatible with ARMv6, AFAIK.
Click to expand...
Click to collapse
We shall soon see.
sent from my towelrooted LG L34C using tapatalk
CyanogenMod announces official CM12 Nightlies!
http://phandroid.com/2015/01/05/cyanogenmod-cm12-nightlies/
Do not even expect P500 on the list!
EDIT:
CyanogenMod 12 nightlies now available for 31 devices, based on Android 5.0.1 Lollipop (LRX22C). LG Optimus One is out of the list to be sure
http://blog.gsmarena.com/cyanogenmo...able-31-devices-based-android-5-0-1-lollipop/
While in other hand, our devs are working to port experimentally newer version of CM12 (Android 5.0.2 LRX22G) on armv6 obsolete devices, though! :good:
You can look at development of android_art as it progresses here:
http://review.androidarmv6.org/#/q/status:merged
and here:
http://review.androidarmv6.org/#/c/7676/
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
xu3sno said:
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
Click to expand...
Click to collapse
Trimmed>>Flashed>>Stuck at CM bootlogo
CCXAlex said:
Trimmed>>Flashed>>Stuck at CM bootlogo
Click to expand...
Click to collapse
+1K
GERRIT_CHANGES: 7676 7748 7693 7651 7751 7792
Code:
7676: * runtime : make entrypoints ARM; if the target arch is lower than
armv7, set armv6.
* compiler: add a new define: ARM_MODE_WORKAROUND, enable it if
the target cpu is arm11. Use ARM assembler and replace
Thumb{1-2} opcodes with ARM ones. Update some code to
support new opcodes
NOTE: kArm is not implemented, probably it use to work only in
portable mode.
7748: Compatibility work around for bad graphics driver dependency
7693: legacy OMX: squashed commit for legacy OMX support for LP
7651: Revert "Revert "Turn on BLE, GATT, and SMP of Bluetooth stack""
7751: msm7x27-common: Initial cm-12 bringup
7792: jemalloc: Force gcc for atomic functions
GCC built-in functions provide advanced things like prefetch, expected, synchronization...
Bootloog attached.
It seems bootloop's culprit is regarding with dynamic shared libraries (lib*.so) which must be fixed first.
It does not work on any device arvm6.
Link
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Also, a reminder of some things you shouldn't do (now or ever): don't ask for ETAs, don't spam the dev thread, and don't PM me asking for information that isn't on a public post.
There are many things that need to be fixed for armv6 devices. I've sorted out the major issues specific to Broadcom hardware, but there are more important issues that need solving for ARMv6 devices in general that are being working on by several people (assembly errors, ART compatibility, build system integration, etc.). It's going to take time. Thanks for your understanding.
Click to expand...
Click to collapse
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
xu3sno said:
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
Click to expand...
Click to collapse
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Any PlayStore said:
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Click to expand...
Click to collapse
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Quote:
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Click to expand...
Click to collapse
Yes, yes, we know or should know. But, hey, who does not want to be the first to see this play? The only reason I am staying off is because of the CM tricks with switching system and data partitions meaning recoveries are not compatible.
Anyway, diehards within the CM universe, once in that bootloop if ART had indeed done its thing, check remaining system space and contents of those /system/app/... folders. My (un-) educated guess is that this may become the big problem.
xu3sno said:
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Click to expand...
Click to collapse
I also attempted to install this. Initially my trimming method seems to have broken update binary, so flash failed. Next installed full ROM (/system =189MB) using @HardLight twrp 2.7.0.0 TLS (successfully flashed). Stuck at boot animation. No log (flashing while driving).
sent from my towelrooted LG L34C using tapatalk
MoKee Open Source is the biggest non-profit Android Open Source development team in China, with members from all parts of the world. We follow the latest development from Google closely and improve various parts of Android according to the user habits. Being a non-profit organisation, we utilise our spare time and own funds to keep this passion alive. Therefore, the costs for the forum and servers are solely beared by us. In order to provide a good user experience, we only included a few preinstalls in the ROM. Along with the advertisements in the forum; we hardly get enough to pay for the bandwidth. The point is, those are our only source of income, however many developers choose to exclude them when releasing unofficial builds. Unlike CyanogenMod, we did not accept monetary help at the early stages, as in China, most people do not understand the meaning of “making a donation”. They would think of it as buying a service, which is conflicting with our objectives. Anyways, we still made it until today, and even started to provide third party developers a chance to utilise our OTA system. All of these are the fruit of our hard work and passion. We are proud of the happy users, and we are also proud of the support given to MoKee Open Source. Most importantly, we are proud of the improvements we have achieved all these while, and the advancements never stop.
Hit thanks if you like my work.
Downloads : "removed by moderator"
Gapps :== "removed by moderator"
Nano recommended
Twrp :== "removed by moderator"
Don't flash magisk, right now root not supported.
What's working ---
WiFi
Mobile data
bluetooth
mobile data
hotspot
gcam
magisk
If you want to root your pie rom
just simply flash the magisk zip file via twrp.
then install the magisk manager apk manually and open that then you can the installed magisk version.
also you can check your rooot via rootchecker apk
Test this build and let me know the issue, so we could fix those issue.
Special thanks to all oxygen team and all group mates, who provides logs.
Testing thanks
@Cirno
@remicaa
@luciano Henrique
@Mario Resurrected
Credits:
MactavishAO
Hard_rock83
Mokee Development Team
LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: Mokee Open Source Project
Version Information
Status: stable
First android 9? Things are coming! Thank you for the hard work.
Android-9.0(Pie)
It's just first build which booted properly. So there would be lots of bugs.
Let me know the bugs, so we could work on fixing bugs.
fgaurano said:
First android 9? Things are coming! Thank you for the hard work.
Click to expand...
Click to collapse
It's just first build, so there would be lots of bugs, let me know the bugs, so we could fix them.
Gapps?
MI MAX 2 cihazımdan Tapatalk kullanılarak gönderildi
OTA uptades avaible?
Appreciate the effort of developers who bought us PIE flavor for our beloved MAX2
Finally Pie on the Max 2, this is what so many have been waiting so long for. Can't wait for Gcam 6.1.
not
finger print,
double click open the screen
not blutouth
not xposed
Theseusperse said:
Finally Pie on the Max 2, this is what so many have been waiting so long for. Can't wait for Gcam 6.1.
Click to expand...
Click to collapse
GCam 6.1 working on oreo
Which twrp to be used?
ridershahmir said:
GCam 6.1 working on oreo
Click to expand...
Click to collapse
How?!?! What APK are you using for the Mi Max 2? I've tried everything, even wiped my phone and used every ROM out there and can't get anything to work. I'm specifically talking about the latest 6.1 GcCam from the Pixel 3 (Pixel3Mod) with the latest low light enhancement features from the new photo core. I'd love to know how you got it working on the Mi Max 2 on Oreo.
None of the ones on this list work for me so far:
https://www.celsoazevedo.com/files/android/google-camera/
And that's literally all of them as far as I know, including highly specialised device variants. As far as I'm aware it's Pie only.
cem_uar said:
not
finger print,
double click open the screen
not blutouth
not xposed
Click to expand...
Click to collapse
What can you expect from an alpha build .lol. isn't it enough you got pie.
scissordragonboy said:
What can you expect from an alpha build .lol. isn't it enough you got pie.
Click to expand...
Click to collapse
Is camera working on pie?
reversegear said:
Appreciate the effort of developers who bought us PIE flavor for our beloved MAX2
Click to expand...
Click to collapse
If you want to handle this Pie project you can compile from source.
My trees are open on GitHub.
Downloading. Is there a problem with IMEI?
Hucksley said:
Downloading. Is there a problem with IMEI?
Click to expand...
Click to collapse
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.
scissordragonboy said:
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.
Click to expand...
Click to collapse
Camera? Totally not working?
scissordragonboy said:
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.
Click to expand...
Click to collapse
I'm already using rom and I want to thank you for your great work.
I will use it until the next updates come out and I will notify any unknown bug so far.
Thanks again for the work!
(Sorry for the English)
hard to download