[ROM][AOSP][WIP][ALPHA][M] Android M Alpha \\ 25-6-15 \\ Build I

CedArctic

Senior Member
Jun 11, 2012
861
1,635
0
Introduction:
So I see you have found my Android M Preview ROM thread. So... You all might of seen this. It's Sony announcing that it's AOSP open line of Xperia devices can now build Android M and is showing devs how to build it. Apparently things aren't exactly that way. Google created under it's source code, an alpha branch for the upcoming Android M, what that branch contains is mostly Android Lollipop code and some Android M stuff. This branch will evolve to become Android M, but at it's current state, the ROM is in between Android lollipop and M (kind of a weird mix of a sort that's why the build number is 5.1.51 and the easter egg is the one of lollipop). I will however provide weekly (hopefully) builds of Android M as it becomes more M than L. Keep in mind that the current release of the ROM (as of 25-6-2015) does not contain the new API's (for devs that are interested). You can see Sony's official explanation here. If you are still interested though in checking out the current state of Android M be my guest though keep in mind that in it's current state it is FAR from a daily driver (modem and camera are the most major of bugs currently) and most if not all of the cool features on Android M developer preview for the Nexus line probably are not currently included (as on 25-6-15).​



Warning


This works only on UNLOCKED BOOTLOADERS. Keep in mind that the ROM was built for the D6603 I don't know if it will work with any other variant of the Z3. In addition flashing this might erase recovery on some devices. Also I take no responsibility of whatever may happen by using this ROM.


Downloads (please read the Introduction if you haven't, its important :) )

Installation:
1. Backup EVERYTHING (Your SD card included. This ROM has proven to be unpredictable as of storage on some handsets).
2. Download the Kernel, System and Userdata images
3. Get yourself a working ADB/Fastboot installation (more on that on the kernel page)
4. Flash the kernel as described on it's page (Steps 1-7)
5. While still in fastboot mode enter these commands in the command prompt:
Code:
fastboot flash system (directory of system image)
fastboot flash userdata (direcotry of userdata image)
6. Reboot your device and wait for it to start up​

Bugs:
Graphical Glitches
Camera
Modem (no phone calls/messages/data etc.)
Bluetooth
Random Force Closes in most Apps
Recents (some times)
Random other stuff
Erases all storage (internal and external) on some handsets



Screenshots:
Here you go. :)


Credits:​

The rest of team Pear Crew
akateha
My Family & Friends
Sony and it's AOSP project
XDA
Google
 
Last edited:

CedArctic

Senior Member
Jun 11, 2012
861
1,635
0
Changelog:

----- Build I -----
Initial release.
Synced the latest android-m-preview branch
Most Android M features completely missing, ROM is like a hybrid of Lollipop&M
Bugs:
Graphical Glitches
Camera
Modem (no phone calls/messages/data etc.)
Bluetooth
Random Force Closes in most Apps
Recents (some times)
Random other stuff
 
Last edited:

CedArctic

Senior Member
Jun 11, 2012
861
1,635
0
@Gustavo RD78
Actually I haven't, even Sony states that Camera & Modem are guaranteed broken. Even if the modem was fixed (which I believe it will in the next few weeks) the ROM still needs a lot of work for all the other bugs. Although about the baseband, I think M requires a special version of the baseband because even when you flash the official M preview over the Nexus 5, you have to flash a new baseband that is compatible with Android M. I am currently away from my Z3 but if someone tries it out and confirms it working I would gladly add it to the main thread. :)
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,095
25,085
0
Owego, NY
@CedArctic

it may be that the flashing the rom erase the baseband
have you tried to reinstall a baseband after flash the rom?
Some modem components are stored on /system and not included for legal reasons in Sony's AOSP binary releases. https://github.com/SuperBenevolent/aosp-vendor-qcom-proprietary

At least with L-MR1, the ONLY things missing for modem to work are the blobs above. Dunno about M, I'm not bothering to mess with it until official M release.
 

Silveryard

New member
Jun 28, 2015
0
0
0
Installed a few minutes ago. Thank you for compiling the source code.

Am I wrong or can´t I flash GApps?

Edit: Also I cannot use any storage. Not internal and not sd card
 
Last edited:

Silveryard

New member
Jun 28, 2015
0
0
0
It´s because some .apk files (like the play framework) cannot be installed with adb install command and require a custom recovery kernel or root or root for writing permissions in "system"
I don´t know much about compiling a system image but is it possible to place the gapps files into the right folder right before compiling everything in one file? This would help much and would make this preview much more usable in daily life.
 

CedArctic

Senior Member
Jun 11, 2012
861
1,635
0
@squabbi Cool bro :) @M-Rom Congrats for your work bro, I saw the FlyMe OS port... simply loved it... although I'm curious how did you port it? Because I tried to do so in the past... @Aaahh I'll take a look into it. I think storage is just the storage-list.xml in the framework.... Thanks for the guide :)
 

Aaahh

Senior Member
Nov 4, 2013
1,390
1,240
0
@squabbi Cool bro :) @M-Rom Congrats for your work bro, I saw the FlyMe OS port... simply loved it... although I'm curious how did you port it? Because I tried to do so in the past... @Aaahh I'll take a look into it. I think storage is just the storage-list.xml in the framework.... Thanks for the guide :)
What? I'm not sure what your talking about
Just to repeat, those are the actual M preview apps and I "fixed" them so that you can add them to your rom
 

CedArctic

Senior Member
Jun 11, 2012
861
1,635
0
@Aaahh you posted a quote of me about storage and I said now that I think I know that the issue is in the storage-list.xml in the framework. I will include your apps in the next build, but for now I am focusing on a different project until M becomes more stable...