• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

Android M Developer Preview for Xperia Z1 [July-04]

Sidebar
A

aquaboy11

Senior Member
Jul 13, 2014
148
88
0
www.g2a.com
Jun 26, 2015 at 12:04 PM
Introduction
Hello,
Recently Sony released their source binaries for the Android M Developer Preview, so I decided to build and share it :). Keep in mind this is a Developer Preview. It's just to give an idea of how the new Android M looks like. Both the camera and modem aren't included by Sony, so you can't use those.
Click to expand...
Not included
  • Modem
  • Camera
Click to expand...
Installation instructions
  1. Make a back-up and store it outside of your phone.
  2. Connect the device to your computer in Fastboot mode, by pressing volume up while inserting the USB cable.
  3. In the terminal on your computer type the following commands:
  4. Code: 
    fastboot flash boot boot.img
  5. Code: 
    fastboot flash system system.img
  6. Code: 
    fastboot flash userdata userdata.img
  7. Now when you disconnect your device from the computer and start it, it will be running AOSP.
Click to expand...
XDA:DevDB Information
AOSP M, ROM for the Sony Xperia Z1

Contributors
aquaboy11
Source Code:
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/list-of-devices-and-resources/
https://android.googlesource.com/platform/manifest/+/android-m-preview
https://github.com/sonyxperiadev/

ROM OS Version: Android M
ROM Firmware Required: C6903
Based On: AOSP

Version Information
Status: Testing

Created 2015-06-26
Last Updated 2015-07-04
 
Last edited:
  • Like
Reactions: munged, ScatteredHell, catbass113 and 7 others
jos_031

jos_031

Senior Member
Feb 21, 2011
393
201
0
London
Jun 26, 2015 at 12:54 PM
good for trying how M looks but hope some one will come with a patch to make modem work... I tried to build it too.. but reposync will take for ever
 
T

threader

Senior Member
May 31, 2010
189
123
0
Jun 26, 2015 at 1:19 PM
Think the modem is intentionally disabled from the article i read, interesting that its using the 3.4 kernel though, i would have thought 4.x or at least a newer 3.x.. Did not spot a link to the sources(?), i really like the way Sony Ericsson has managed these projects ( the Z series), not only will it benefit us in the future when they eventually deprecate the project, but actually including the community and promoting development rather then hampering it by all means possible, reason enough for me to recommend the series, me like :>
 
A

aquaboy11

Senior Member
Jul 13, 2014
148
88
0
www.g2a.com
Jun 26, 2015 at 1:28 PM
threader said:
Think the modem is intentionally disabled from the article i read, interesting that its using the 3.4 kernel though, i would have thought 4.x or at least a newer 3.x.. Did not spot a link to the sources(?), i really like the way Sony Ericsson has managed these projects ( the Z series), not only will it benefit us in the future when they eventually deprecate the project, but actually including the community and promoting development rather then hampering it by all means possible, reason enough for me to recommend the series, me like :>
Click to expand...
Oops, I forgot to include the sources :eek:. Will add them now :).
 
AndropaX

AndropaX

Senior Member
May 18, 2014
351
1,019
0
San Escobar
Jun 26, 2015 at 4:20 PM
I tested it, and think it's only more buggy lollipop, which sony/google called "m". Any new features like multiwidow from m preview, API 22 (from 5.1), old lockscreen, lollipop easter egg, and strange android version 5.1.51
Bluetooth sharing gives FC. When Sony give us a full working clear aosp ?

Wysłane z mojego Xperia Z1 przy użyciu Tapatalka
 
drakonizer

drakonizer

Retired Forum Moderator
May 10, 2013
1,126
2,340
113
Death Star
Jun 26, 2015 at 8:38 PM
It's not Sony's fault. Google hasn't made the new APIs open source yet. They have just given build instructions for the aosp M preview branch.
I wouldn't recommend using this, as there's absolutely no difference from Lollipop as far as I've seen.
 
T

threader

Senior Member
May 31, 2010
189
123
0
Jun 28, 2015 at 12:47 AM
aquaboy11 said:
Oops, I forgot to include the sources :eek:. Will add them now :).
Click to expand...
Read trough the build guide.
It's supposed to use the 3.10 kernel. I'm having all sorts of problems with this kernel though, i havent gotten it booting on the device yet.. .Just says missing dtb no matter what i do .. even creating the zImage-dtb trough config or manually results in fastboot saying no dtb...
<project path="kernel/sony/msm" name="kernel" groups="device" remote="sony" revision="aosp/AU_LINUX_ANDROID_LA.BF64.1.2.1_RB1.05.00.02.019.067" />
 
O

optimumpro

Senior Member
Jan 18, 2013
6,266
13,594
113
Jun 28, 2015 at 12:58 AM
threader said:
Read trough the build guide.
It's supposed to use the 3.10 kernel. I'm having all sorts of problems with this kernel though, i havent gotten it booting on the device yet.. .Just says missing dtb no matter what i do .. even creating the zImage-dtb trough config or manually results in fastboot saying no dtb...
<project path="kernel/sony/msm" name="kernel" groups="device" remote="sony" revision="aosp/AU_LINUX_ANDROID_LA.BF64.1.2.1_RB1.05.00.02.019.067" />
Click to expand...
You can try to put the kernel sources into a build environment, i.e., any cm based rom, do build envelope, launch your device, then do mka bootimage and see what happens. But generally, this development has been nothing short of grossly pathetic. Linux now has fully working 4.x kernels. I don't necessarily blame developers primarily, as the main culprits are Sony and Google. However, oems are not more cooperative with linux developers than with android devs, yet linux is ages ahead not only in terms of kernels, os, but also in creating open source firmware...
 
Last edited:
T

threader

Senior Member
May 31, 2010
189
123
0
Jun 28, 2015 at 2:42 AM
optimumpro said:
You can try to put the kernel sources into a build environment, i.e., any cm based rom, do build envelope, launch your device, then do mka bootimage and see what happens. But generally, this development has been nothing short of grossly pathetic. Linux now has fully working 4.x kernels. I don't necessarily blame developers primarily, as the main culprits are Sony and Google. However, oems are not more cooperative with linux developers than with android devs, yet linux is ages ahead not only in terms of kernels, os, but also in creating open source firmware...
Click to expand...
True, replacing the kernel directory and running a script to remake the headers from that kernel used to build android is the way to port android to a new kernel. I'm not building a rom atm though, i'm building the kernel only (bellow). I suspect the 3.10 kernel and newer require an updated bootloader.. However, in what way updating this would affect my ability to boot 4.4.4 i do not know, so im a bit weary.

Code: 
ARCH=arm CROSS_COMPILE="$home"/dev/sdk/linaro-gcc-4.9-abe-gnueabihf/bin/arm-none-linux-gnueabihf-  make -j8

dtbTool -o dt-0.img -s 2048 -p/scripts/dtc/ arch/arm/boot/ ( changed arch/arm/boot/ to arch/arm/boot/dtb in later kernels)

mkbootimg --cmdline "androidboot.hardware=qcom user_debug=31 maxcpus=2 msm_rtb.filter=0x37 ehci-hcd.park=3 lpj=192598 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y vmalloc=400M" --base 0x00000000 --kernel "$home"/dev/nix/xperia/xperia-c6903-z1-source-final-4.4.4-0/arch/arm/boot/zImage --ramdisk "$home"/nix/xperia/boot-xperia-c6903-z1-sony-kernel-0/157/kernel_S1-SW-LIVE-6732-PID1-0005-MMC.elf.ramdisk --ramdisk_offset 0x02000000 -o boot-0.img --dt dt-0.img --tags_offset 0x01E00000
Also spotted this (Recovery mode now available for a range of unlocked Xperia devices) http://developer.sonymobile.com/201...for-a-range-of-unlocked-xperia-devices-video/ , however, my device (thankfully) runs Customized NCB_1276-9897 ( scandinavia ), so i dont know how well it would take to a UK rom, which has been updated.

As i mentioned before elsewhere, porting to a newer kernel ought be relatively easy, 4.1 would be a natural choice, its LTS and i suspect Android M or so will probably land there..
 
Last edited:
  • Like
Reactions: aquaboy11
O

optimumpro

Senior Member
Jan 18, 2013
6,266
13,594
113
Jun 28, 2015 at 7:29 PM
threader said:
True, replacing the kernel directory and running a script to remake the headers from that kernel used to build android is the way to port android to a new kernel. I'm not building a rom atm though, i'm building the kernel only (bellow).
Click to expand...
I know you are not building a rom, but my point is it is much better to compile a kernel in a native (to your device) environment with all the tools already there. You also have your native ramdisk, as opposed to some generic one. I have built quite a few kernels using this method and it has yet to fail once...
 
T

threader

Senior Member
May 31, 2010
189
123
0
Jun 29, 2015 at 8:54 AM
True, as it stands now, the way im assembling the boot.img it's incompatible with certain installers for Multibot, using the method you described would avoid that entirely.

Spotted the nexus 5 and 7 are on 4.2.2 for android m. I guess 3.10 is just a step.
 
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone