Database Develop

[Q] New official JB release?

Has anybody taken a look at the new official JB release that popped up at http://sbf.droid-developers.org/cdma_maserati/list.php ? (Although, I can't access it currently)
It's been mentioned on another thread (http://forum.xda-developers.com/showthread.php?t=2277830 ) regarding the ability to root, but it doesn't look like it's been looked at in any depth whether it includes any fixes, etc. The build date has changed to the 5th April, and the version is 9.8.20-72_VZW-18-2.
Cheers,
Steve.

This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app

alex94kumar said:
This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app
Click to expand...
Click to collapse
You could be right regarding the location, apologies if people object - I just thought the ROM guys would probably be the ones most likely to be all over it.

File Mirror
FWIW - I found that droid-developers.org seemed a little hit and miss, so I've set up a private file mirror for this new release. If somebody wants access to it, then just PM me. I'm trying to sort out a public mirror too, and will update this post when/if I get that sorted out.
Cheers,
Steve,

I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc

This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.

sd_shadow said:
I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc
Click to expand...
Click to collapse
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
cellzealot said:
This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.
Click to expand...
Click to collapse
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.

It's safe for now...
StevePritchard said:
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.
Click to expand...
Click to collapse
Yes, and I just flashed the boot, system and radio images from the MR2 XML and then rerooted using razr_blade.
So, we are safe to use this file to upgrade the firmware without any loss of root or any other issues.
The secure version did not increment so it is also possible to revert to the prior -18 release without risk of soft bricking.
This follows the pattern of the update for the HD and will likely be the same for the other devices that just recieved 4.1.2 in this cycle.
The next update is the one the will include ISIS and may also have security enhancements that will need to be carefully scrutinized.
That is conjecture on my part, at this stage, we don't know.

It would be nice to know what changes the release addresses. My hope is that it sorts out the hardware keyboard problem of unsticky shift keys in some applications.
Cheers,
Steve

Guardian Rom [Secure] [Privacy] [Preview]

Guardian Rom by x942​Thanks 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.

All-In-One Thread about recent 4.3 Leak (Links, Info, and more)

Where do I get the 4.3 leak for my Nexus 4?
ROM (CREDITS: gmillz)
New baseband and bootloader (CREDITS: someone enlighten me )
What's new in 4.3?
XDA discussion thread about new changes
Changelog compiled by Sam Tate from Google+
Hands-on video from AndroidCentral using Android 4.3 on the Nexus 4
ROM developers, please make a (rom name here) with 4.3!
Wait for it guys the developers don't Iive to please you and besides, the source code has not been released yet. Give the ROM devs a break and stop filling up the threads with requests for 4.3 in new custom ROMs.
I want to stay on my custom ROM but want to enjoy some of the new stuff in 4.3. How should I go about doing this?
Th3RiddL3r has made an awesome thread including a lot of new apps and other features from Android 4.3, including the font, new camera APK, new bootanimation and other things in 4.3/GE Phones. Check out his thread here.
For the curious:
What's the whole story of this leak?
Quoted directly from AndroidCentral:
A few weeks after Android 4.3 leaked for the the Google Play edition Galaxy S4, today we're seeing the same pre-release build — JWR66N — leaking out online for the Nexus 4. The unofficial firmware comes to us from Jeff Williams on Google+, who bought his Nexus 4 on Craigslist from a Googler, only to find it running the pre-release software. With a little help from the Google+ community, IRC users and XDA, Jeff was able to create a system dump and backup of the ROM. Currently the radio and bootloader are missing from this package — word on the forums is that they'll be provided at a later date.
Click to expand...
Click to collapse
Reddit Thread about the people who helped Jeff Williams:
Quick!! Someone help this guy pull a system dump... Leaked 4.3 ROM for Nexus 4
Redditors/G+ users help a lucky craigslist buyer pull Android 4.3 off of his Nexus 4!
IRC Log from the chat where people helped Jeff Williams: (Credits to BoomChaos from Reddit)
http://pastebin.com/z3TdxjwB
I will be editing this post actively with any improvements and new things people suggest. Credits go to the awesome people on XDA, G+ and Reddit(/r/android) community.

Don't we already have a thread like this?
Sent from my Nexus 4 using Tapatalk 4 Beta

Neefy said:
Don't we already have a thread like this?
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
yes we do.
please close admin. :good:

This thread is silly
Sent from my Nexus 7 using xda premium

another one????

[INFO] Roms Fully Sprint Functional UPDATE:01/11/14 fix in second post

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.

About Android M Source

i noticed that a lot of projects on android.googlesource.com already have the android-m tag, including
plataform/system/core
plataform/build
plataform/frameworks/base
so i think if these non gpl projects are updated with M code, is the source code fully complete? can anyone check if we can already update and build M roms?

I pulled the source via repo, but I haven't got around to a build yet.

Gene Poole said:
I pulled the source via repo, but I haven't got around to a build yet.
Click to expand...
Click to collapse
Would you be able to build roms off of M source? Is it enough source or is it better to wait for new update and factory images? Since the bootloader and radio is the same as that of 5.1.1 shouldn't gapps work?

opssemnik said:
i noticed that a lot of projects on android.googlesource.com already have the android-m tag, including
plataform/system/core
plataform/build
plataform/frameworks/base
so i think if these non gpl projects are updated with M code, is the source code fully complete? can anyone check if we can already update and build M roms?
Click to expand...
Click to collapse
I couldn't get it to build (could be an issue on my side, tho). So I guess it's better to wait for the official announcement before building.

F4uzan said:
I couldn't get it to build (could be an issue on my side, tho). So I guess it's better to wait for the official announcement before building.
Click to expand...
Click to collapse
ok thanks, thanks to my "great" internet (10mbps) i didnt want to loose a full day just syncing

cell2011 said:
Would you be able to build roms off of M source? Is it enough source or is it better to wait for new update and factory images? Since the bootloader and radio is the same as that of 5.1.1 shouldn't gapps work?
Click to expand...
Click to collapse
gapps relly on the system framework (sdk), radio and bootloader rely on nothing, they control the device in a really low level state, in fact the bootloader is the lowest level, since it starts the kernel.
Sometimes radios/bootloader causes issuses depending on the combination but thats because of the blobs system wise, not because of the os version.
And gapps were updated on M

opssemnik said:
ok thanks, thanks to my "great" internet (10mbps) i didnt want to loose a full day just syncing
Click to expand...
Click to collapse
So my whole day sacrifice is worth it then (I synced for like, a day or two).
Anyway, I've seen some component gets android-m-preview tag. Google might be pushing it real soon.

F4uzan said:
So my whole day sacrifice is worth it then (I synced for like, a day or two).
Anyway, I've seen some component gets android-m-preview tag. Google might be pushing it real soon.
Click to expand...
Click to collapse
Does anyone happen to see what android ver this will be? 5.2?

cell2011 said:
Does anyone happen to see what android ver this will be? 5.2?
Click to expand...
Click to collapse
Nah, just m-preview. It's just like L, the development tag is l-preview.

F4uzan said:
Nah, just m-preview. It's just like L, the development tag is l-preview.
Click to expand...
Click to collapse
M preview is 5.1.x for sure. Look at the SDK number : 22, like Android 5.1
I'm almost sure you can build Android M from AOSP, and thats why :
I know the difference between Android 5.1.1 and M is very little, just a few adds, i seen somewhere, speaking of less than 20MB of changed files.. So, try to sync a repo with Android 5.1.1 AOSP, and add the M commits and try to build, to see.
If it builds for Nexus 5, so i can be built for any other device supported by AOSP 5.1.1.

dekefake said:
M preview is 5.1.x for sure. Look at the SDK number : 22, like Android 5.1
I'm almost sure you can build Android M from AOSP, and thats why :
I know the difference between Android 5.1.1 and M is very little, just a few adds, i seen somewhere, speaking of less than 20MB of changed files.. So, try to sync a repo with Android 5.1.1 AOSP, and add the M commits and try to build, to see.
If it builds for Nexus 5, so i can be built for any other device supported by AOSP 5.1.1.
Click to expand...
Click to collapse
Thanks for pointing out ! I totally missed the point that the SDK version is still 22.
I'll try rebuilding M again, the fault could be on my side.

So will this be a build off of 5.1.1 and M if it can be done?
---------- Post added at 06:34 AM ---------- Previous post was at 06:20 AM ----------
This is what member defconoi says about doing a port for the N4. All that needs to be done is to take the nexus 5 image and replace the binaries with the mako binaries preview and then use the nexus 4 m kernel. That's what I did when porting L. I don't know if this can be of any help pertaining to our N5

cell2011 said:
So will this be a build off of 5.1.1 and M if it can be done?
---------- Post added at 06:34 AM ---------- Previous post was at 06:20 AM ----------
This is what member defconoi says about doing a port for the N4. All that needs to be done is to take the nexus 5 image and replace the binaries with the mako binaries preview and then use the nexus 4 m kernel. That's what I did when porting L. I don't know if this can be of any help pertaining to our N5
Click to expand...
Click to collapse
just remember, the n4 dosen´t have an updated kernel source tree with M tag, just the binary, so you guys will need to update the ramdisk for M

opssemnik said:
just remember, the n4 dosen´t have an updated kernel source tree with M tag, just the binary, so you guys will need to update the ramdisk for M
Click to expand...
Click to collapse
Are you working on a build for our N5? Someone on android development has a flashable stock of M deodexed version coming soon its not out yet but the post is

cell2011 said:
Are you working on a build for our N5? Someone on android development has a flashable stock of M deodexed version coming soon its not out yet but the post is
Click to expand...
Click to collapse
im just thinkering with it, nothing for public release.
however you guys can use ext4 image unpacker to work directly with the factory images
http://i.imgur.com/T9SCUSR.png

cell2011 said:
So will this be a build off of 5.1.1 and M if it can be done?
Click to expand...
Click to collapse
I think a combo build with 5.1.1 - M is possible, adding M commits to a 5.1.1 source code, and then, try to build.