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...
Click to collapse
Not included
Modem
Camera
Click to expand...
Click to collapse
Installation instructions
Make a back-up and store it outside of your phone.
Connect the device to your computer in Fastboot mode, by pressing volume up while inserting the USB cable.
In the terminal on your computer type the following commands:
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata.img
Now when you disconnect your device from the computer and start it, it will be running AOSP.
Click to expand...
Click to collapse
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
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
jos_031 said:
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
Click to expand...
Click to collapse
I don't think anyone wants to port the modem and camera to a Developer Preview. We will have to wait for Sony to do that.
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 :>
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...
Click to collapse
Oops, I forgot to include the sources . Will add them now .
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
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.
aquaboy11 said:
Oops, I forgot to include the sources . Will add them now .
Click to expand...
Click to collapse
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" />
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...
Click to collapse
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...
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...
Click to collapse
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..
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...
Click to collapse
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...
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.
no links?
OptidroidPlus said:
no links?
Click to expand...
Click to collapse
Downloads tab on XDA Website (not app)...
I see an update...any changes yet? Or is it still lollipop?
drakonizer said:
Downloads tab on XDA Website (not app)...
I see an update...any changes yet? Or is it still lollipop?
Click to expand...
Click to collapse
give me links please? i am new in xda.. thanks
drakonizer said:
Downloads tab on XDA Website (not app)...
I see an update...any changes yet? Or is it still lollipop?
Click to expand...
Click to collapse
No, it's still a buggy Lollipop version. The update just includes the latest commits and changes made to the project.
OptidroidPlus said:
give me links please? i am new in xda.. thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/devdb/project/?id=10518#downloads
Thanks!!
Android M Preview 2 is coming ? http://www.droid-life.com/2015/07/09/android-m-developer-preview-2-now-available/
Sent from my Xperia Z1 using Tapatalk
danny19901 said:
Android M Preview 2 is coming ? http://www.droid-life.com/2015/07/09/android-m-developer-preview-2-now-available/
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
I doubt Google is going to update AOSP sources...one can only hope. @aquaboy11 Could you post a changelog of any noticeable difference when you update your builds? Thanks...
Related
if cm11 out i will buy one
Sent from my Moto G using Tapatalk
I'm currently working on unofficial build CM10.2.
Kernel is done
device tree is done
vendor setup is done
Android sources currently downloading
testing not yet.
Riyal said:
I'm currently working on unofficial build CM10.2.
Kernel is done
device tree is done
vendor setup is done
Android sources currently downloading
testing not yet.
Click to expand...
Click to collapse
Not CM11, but still very exciting =)
TheQwertiest said:
Not CM11, but still very exciting =)
Click to expand...
Click to collapse
I will try cm11 once i get cm10 running. Thing is we don't have official android 4.4 roms yet I don't have any sources for 4.4 binaries and kernel
Riyal said:
I will try cm11 once i get cm10 running. Thing is we don't have official android 4.4 roms yet I don't have any sources for 4.4 binaries and kernel
Click to expand...
Click to collapse
We wait for CM11!
Xperia V, T doesn't have official 4.4 ROM too, but they have CM11.
Also, I think it's possibile developing CM11 or other CM11 based (KitKat) AOSP ROM.
Unfortunatelly I can't develop it...
I just will use it :fingers-crossed:
u guyz are lucky...u have munjeni wid u now. just be patient.. his hardwork brought cm11 novathor devices... which were abondoned on ics.
two reason i see z1compact as my next phone is that i dont like large phones and master munjeni has z1c also...
We can use CM11 from Z1 since Z1 CM11 on Z1C is working but there is no display available since CM kernel on MSM8974 need some changes related to the Z1C display Bad news is we can not use stock kernel since gralloc, copybit ..etc is not working than. I started working on CM kernel but hmmm CM kernel and stock kernel is a lot diferent so hard work is needed If we get CM kernel working we will get CM11 working with no big modifications
Edit:
Compared now stock Sony kernel source code from Z1 and stock ekrnel source code from Z1C, there is absolutly no diferencie, only one line is diferent in defconfig, line is CONFIG_MACH_SONY_*****_ROW, source is totaly identic. I'm confused now since have no idea why CM kernel working on Z1 but no on Z1C. Maybe I have downloaded wrong kernel for Z1 ??? I have downloaded https://github.com/CyanogenMod/android_kernel_sony_msm8974 branch cm-11.0 . Maybe these kernel not working on Z1 too ???
Can't wait to try CM
kernel config from boot.img
munjeni said:
Compared now stock Sony kernel source code from Z1 and stock ekrnel source code from Z1C, there is absolutly no diferencie, only one line is diferent in defconfig, line is CONFIG_MACH_SONY_*****_ROW, source is totaly identic. I'm confused now since have no idea why CM kernel working on Z1 but no on Z1C. Maybe I have downloaded wrong kernel for Z1 ??? I have downloaded{removed} branch cm-11.0 . Maybe these kernel not working on Z1 too ???
Click to expand...
Click to collapse
Hello,
I am not sure if this is helpfull, but I'll give it a try: You are right - there is absolut no difference between the two kernel configurations, beside that one line. Since there are already nightlies available for the Z1(honami) I thought there might some helpfull informations inside that nightly. Of course there was a boot.img inside the nightly and I found that script to extract the kernel.config from that boot.img. Using the extract-ikconfig from my xperia z(yuga) kernel located in ./kernel/sony/apq8064/scripts/extract-ikconfig.
If the extracted config is reliable, there are indeed many differences.
I attached the extracted config. Maybe you remove the Lines starting with # and the blank lines for a better compare.
Let me know if I can help in some way.
Kind Regards
I don't know whats going on or why CM kernel is working on Z1 and not on Z1C but I think these fails on Z1C is related to the baseband and bootloader? Just asking, DO NOT FLASH THEM!!!
And another thing is maybe dtbs is a thing related to the fail since I can see some things in dmesg related to the pingpong command in mdss_mdp_intf_cmd.
Error log -> http://pastebin.com/9zgcWd4a
Thanks to the developers who are trying to make CM11 working on this phone. I will buy this phone if CM11 is available
@munjeni
Guys I have compiled a CM10.2 kernel here. Who's willing to try it against Z1's CM10.2 ROM?
http://forum.xda-developers.com/showthread.php?t=2461282
I'll provide the source if it works.
Riyal said:
@munjeni
Guys I have compiled a CM10.2 kernel here. Who's willing to try it against Z1's CM10.2 ROM?
http://forum.xda-developers.com/showthread.php?t=2461282
I'll provide the source if it works.
Click to expand...
Click to collapse
You can try! You no need to install, simple boot them without installing! On next reboot your phone will boot normaly! So boot these image temporary by command:
fastboot boot boot.img
Nope, doesn't seem to boot :/
munjeni said:
You can try! You no need to install, simple boot them without installing! On next reboot your phone will boot normaly! So boot these image temporary by command:
fastboot boot boot.img
Click to expand...
Click to collapse
Yeah but I just relocked my bootloader yesterday. I won't be unlocking it till I get more time in development.
crytic said:
Nope, doesn't seem to boot :/
Click to expand...
Click to collapse
Weird then... The patch I applied to port z1 kernel to z1 compact made a fully working stock kernel. But when I applied it to CM kernel it doesn't even boot. Can you by chance get a copy of /proc/last_kmesg and upload it somewhere or here?
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # ←[6nuname -r
uname -r
3.4.0cyanogenmod-g77098c0-dirty
~ # ←[6n
Click to expand...
Click to collapse
munjeni said:
Click to expand...
Click to collapse
Woot! There it goes Now I don't have to port CM haha!
Sweet, with or without display?
crytic said:
Sweet, with or without display?
Click to expand...
Click to collapse
With! Investigating between commits on git since using old working commits, need to find which commit broke display init. There is ~100 commits between but I will try every 20.th When commits get located than will try to fix upstream kernel . There is a lot of work but thats a only way by now.
munjeni said:
Click to expand...
Click to collapse
munjeni said:
With! Investigating between commits on git since using old working commits, need to find which commit broke display init. There is ~100 commits between but I will try every 20.th When commits get located than will try to fix upstream kernel . There is a lot of work but thats a only way by now.
Click to expand...
Click to collapse
git bisect to the rescue Well, if you need any help, just drop me a line!
hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
feel free to fork, build, fix and push back
Br
J
PS.
in case latest software does not appear just press "all Services"
flash latest software available and on top new loader
Custom ROM We Want! (Xperia T3 D5102)
jerpelea said:
hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
feel free to fork, build, fix and push back
Br
J
Click to expand...
Click to collapse
Good news for T3 devices!
All we need now is cwm/twrp recovery and the show may begin!!
great lollipot binaries... so android 5.0 will finally come to T3 ;p
updated guide and blobs for android Lollypop version 5.0.1
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
How do we set up?
Berkant Ayhan Karabudak said:
How do we set up?
Click to expand...
Click to collapse
if you read the guide you will see
jerpelea said:
if you read the guide you will see
Click to expand...
Click to collapse
I am in turkey. My english is not so good.
Do you make installation guides?
AOSP 5.0.2 is published
http://developer.sonymobile.com/kno...ld-aosp-lollipop-for-unlocked-xperia-devices/
http://developer.sonymobile.com/kno...ld-aosp-lollipop-for-unlocked-xperia-devices/
- updated L build guide published
- new blob zip
- wifi is built into kernel
- media is built from source now
- NFC built from source
- audio built from source
- GPS built from source
enjoy
J
Error in sony.xml
<project path="device/sony/kernel" name="kernel" groups="device" remote="sony" revision="aosp/LNX.LA.3.5.2.2-03010-8x74.0 " />
Click to expand...
Click to collapse
You have a space after 8x74.0 and the "
jerpelea said:
hi all
we have included this device in open devices project
...
feel free to fork, build, fix and push back
Click to expand...
Click to collapse
It seems to be fine idea before (or instead?) official release will come.
How much unstable is it?
Ok. Checked.
Git fetched 32GB of data. The laptop wheezed ~9 h but finally it is done.
The system itself works fine. But.
It is completely nude. I've been trying to insert Google Play Services. Defeat.
So. There is no possibility to connect it with Google account and services.
I'm afraid aosp is going to be always to
experimental for regular use. As it is development version.
lalotche said:
It seems to be fine idea before (or instead?) official release will come.
How much unstable is it?
Ok. Checked.
Git fetched 32GB of data. The laptop wheezed ~9 h but finally it is done.
The system itself works fine. But.
It is completely nude. I've been trying to insert Google Play Services. Defeat.
So. There is no possibility to connect it with Google account and services.
I'm afraid aosp is going to be always to
experimental for regular use. As it is development version.
Click to expand...
Click to collapse
AOSP is intended to be a stable base for custom ROMs and developers
you can make your own ROM with all the apps you desire
br
J
build guide has been updated for easy reading
http://developer.sonymobile.com/kno...evices/how-to-build-and-flash-a-linux-kernel/
br
J
jerpelea said:
AOSP is intended to be a stable base for custom ROMs and developers
you can make your own ROM with all the apps you desire
br
J
Click to expand...
Click to collapse
That sounds better.
I have not enough time to make it seriously and full time but I've got a few ideas to try and of course - I'm going to check new aosps and new GServ. releases.
As Google services are essential for android functionality until I get it stable I won't try to build more complex set.
Sent from my D5103 using XDA Free mobile app hurray
First shot.
So. It was little trouble for google made geek.
After a few hours of hard fight (I mean hard googling) I've got rooted system and gaps working.
I decided to root it to easier play with system apps. I did not want to hack source tree as well.
Curious - make_ext4fs changes file privileges (I've needed to add some stuff into system.img).
I had to add some lines to init.rc to correct it.
There are some minor issues appearing in dmesg - could live with that.
And the one major problem - internal speaker is dumb.
Ear phones works right, but speaker is necessary - this is my only phone
l
custom rom for sony T3 D5102
please port custom rom for sony xperia T3 D5102:good::good::good::good:
So, considering I'm a new owner of a Xperia T3, we can say that 5.0.2 ROMs are working "ok" except from speaker and camera that are not working?
I'm considering install an AOSP ROM because I love pure android but I guess I'll give a try to Sony's one until this ROM is perfectly stable.
Have nice day!
Enviado desde mi XT1032 mediante Tapatalk
gbueno6 said:
So, considering I'm a new owner of a Xperia T3, we can say that 5.0.2 ROMs are working "ok" except from speaker and camera that are not working?
Click to expand...
Click to collapse
Yes. It looks, that everything else for D5103 is ok.
I checked headphones, microphone, gps and wi-fi.
I did not check bt, nfc and others (accelerator?) but nobody reported its faults.
For me speaker is necessary but if you like I've got even rooted 5.0.2 with gaps (git 2015-02-15).
l
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
jerpelea said:
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Click to expand...
Click to collapse
Will Open Devices recovery work with unlocked bootloader and Stock ROM? Or is it intended for Custom ROMs only? I ask because Stock ROMs are using recovery partition for FOTA and the only Stock that brings new partitioning scheme - the new Concept UI ROM - uses nasty security measures against changing either recovery or system partition...
Sent from my D6603 using Tapatalk
ondrejvaroscak said:
Will Open Devices recovery work with unlocked bootloader and Stock ROM? Or is it intended for Custom ROMs only? I ask because Stock ROMs are using recovery partition for FOTA and the only Stock that brings new partitioning scheme - the new Concept UI ROM - uses nasty security measures against changing either recovery or system partition...
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
I think this link would indicate that it is meant for UB at this stage.
However I am building the AOSP android M preview, and will report back with my findings.
shoey63 said:
I think this link would indicate that it is meant for UB at this stage.
However I am building the AOSP android M preview, and will report back with my findings.
Click to expand...
Click to collapse
I meant combination UB+Stock. That UB alone is required is clear
Sent from my D6603 using Tapatalk
ondrejvaroscak said:
I meant combination UB+Stock. That UB alone is required is clear
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
The link says to first install generic software on your device, so yes when released, UB+Stock will work.
But obviously, it will be different to the android concept scenario which (by my reckoning), is just a test by Sony on how to prevent people from rooting their phones on locked bootloader under the guise of providing a minimalistic Sony AOSP like experience. It is my opinion that they will implement it in their future devices.
Edit: I misread you post. Quite clear you were talking about UB
shoey63 said:
The link says to first install generic software on your device, so yes when released, UB+Stock will work.
But obviously, it will be different to the android concept scenario which (by my reckoning), is just a test by Sony on how to prevent people from rooting their phones on locked bootloader under the guise of providing a minimalistic Sony AOSP like experience. It is my opinion that they will implement it in their future devices.
Edit: I misread you post. Quite clear you were talking about UB [emoji14]
Click to expand...
Click to collapse
Anyway, if Sony would mean it seriously with security restrictions in Concept, then we have to go on at least with custom kernels. As soon as Z3 will be in Open devices, majority of problems like fish-eye camera problem may disappear. I think unified kernel sources for 3.10 are already online.
Sent from my D6603 using Tapatalk
Built it, flashed it, bootloops on kernel splash screen
shoey63 said:
Built it, flashed it, bootloops on kernel splash screen
Click to expand...
Click to collapse
With which fw you use it?
Sent from my D6603 using Tapatalk
Flashed back to pure stock. Version doesn't matter I think. Fastbooted the images and got stuck in an hypnotic bootloop. Kernel splash screen over and over...
Sent from my C6603 using XDA Free mobile app
ondrejvaroscak said:
Will Open Devices recovery work with unlocked bootloader and Stock ROM? Or is it intended for Custom ROMs only? I ask because Stock ROMs are using recovery partition for FOTA and the only Stock that brings new partitioning scheme - the new Concept UI ROM - uses nasty security measures against changing either recovery or system partition...
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
recovery is intened for unlocked bootlaoder and custom roms only
br
J
shoey63 said:
I think this link would indicate that it is meant for UB at this stage.
However I am building the AOSP android M preview, and will report back with my findings.
Click to expand...
Click to collapse
i will update build guide for m-preview1 and publish new zip soon
the old blobs from m-preview are incompatible with new m-preview1!
br
J
I'm interested in building an AOSP (5.1.1) firmware for myself. However I lack the knowledge to do so. So bear with me as I ask a few stupid questions while I'm trying to learn something new.
First of all, if I were to follow the instructions on the link on the OP, does that mean that I'm able to build a perfectly working AOSP (5.1.1) firmware?
Secondly, I'm assuming that I need Ubuntu or Linux?
Thirdly, I don't quite understand how does one flash the firmware once it's built. I mean does it provide a kernel with a recovery or do I have to use the unified kernel?
Lastly, is root possible? (Not important)
Sent from my D6653 using Tapatalk
LeParkour012 said:
I'm interested in building an AOSP (5.1.1) firmware for myself. However I lack the knowledge to do so. So bear with me as I ask a few stupid questions while I'm trying to learn something new.
First of all, if I were to follow the instructions on the link on the OP, does that mean that I'm able to build a perfectly working AOSP (5.1.1) firmware?
Secondly, I'm assuming that I need Ubuntu or Linux?
Thirdly, I don't quite understand how does one flash the firmware once it's built. I mean does it provide a kernel with a recovery or do I have to use the unified kernel?
Lastly, is root possible? (Not important)
Sent from my D6653 using Tapatalk
Click to expand...
Click to collapse
For the second question.. You need any environment that supports git and compiling. The instructions are given for Ubuntu and I would stick with that. Ubuntu or compatible Debian based distro.
You get kernel, system and data images at the end. Those you flash in fastboot mode. See instructions. So far it doesn't provide recovery, but recovery may already be available for supported Open Devices. Once you flash recovery, it's kept in separate partition so you can boot it regardless of kernel.
As for rooting, you can do it with recovery or you can include su in your aosp system.
Sent from my D6603 using Tapatalk
jerpelea said:
recovery is intened for unlocked bootlaoder and custom roms only
br
J
Click to expand...
Click to collapse
Hi, I would paraphrase the Apollo 13 - "It is not important what it is intended for, but what it actually can do"
ondrejvaroscak said:
For the second question.. You need any environment that supports git and compiling. The instructions are given for Ubuntu and I would stick with that. Ubuntu or compatible Debian based distro.
You get kernel, system and data images at the end. Those you flash in fastboot mode. See instructions. So far it doesn't provide recovery, but recovery may already be available for supported Open Devices. Once you flash recovery, it's kept in separate partition so you can boot it regardless of kernel.
As for rooting, you can do it with recovery or you can include su in your aosp system.
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
I tried following the instructions to setup Ubuntu. Used VMWare since for some reason I can't install it on a different partition on my Hard Drive (it gets stuck at login and black screen and loops). I get errors. I give up. Maybe I can use my other PC for Ubuntu.
LeParkour012 said:
I tried following the instructions to setup Ubuntu. Used VMWare since for some reason I can't install it on a different partition on my Hard Drive (it gets stuck at login and black screen and loops). I get errors. I give up. Maybe I can use my other PC for Ubuntu.
Click to expand...
Click to collapse
Nobody can help you or provide you with any guidance if you write just "I get errors" ... Compiling AOSP is not for newbies, it expects you to have profound knowledge of Linux kernel based systems, working with source code, compiling and cross-compiling and not least Linux administration. There is no such thing like a spoon feeding / cook book for compiling own system.
ondrejvaroscak said:
Nobody can help you or provide you with any guidance if you write just "I get errors" ... Compiling AOSP is not for newbies, it expects you to have profound knowledge of Linux kernel based systems, working with source code, compiling and cross-compiling and not least Linux administration. There is no such thing like a spoon feeding / cook book for compiling own system.
Click to expand...
Click to collapse
I think you misunderstood me here. I'm not asking for help. That's why I wasn't specific on the errors. I wanted to try on my other PC later on. To be honest I have no idea why I replied to you but I guess that's my mistake. Sorry
Sent from my D6653 using Tapatalk
LeParkour012 said:
I think you misunderstood me here. I'm not asking for help. That's why I wasn't specific on the errors. I wanted to try on my other PC later on. To be honest I have no idea why I replied to you but I guess that's my mistake. Sorry
Sent from my D6653 using Tapatalk
Click to expand...
Click to collapse
OK, I was bit referring to your first post, it seemed you expect step-by-step instructions to get "perfectly working" AOSP. Such thing doesn't exist.
When setting up building environment, be sure to provide generous space, not less than 200 GB.
ondrejvaroscak said:
OK, I was bit referring to your first post, it seemed you expect step-by-step instructions to get "perfectly working" AOSP. Such thing doesn't exist.
When setting up building environment, be sure to provide generous space, not less than 200 GB.
Click to expand...
Click to collapse
Ah I thought Sony released a fully functioning AOSP firmware. My bad.
200gb? That's huge. I guess using my other PC for Ubuntu is a good choice.
Sent from my D6653 using Tapatalk
LeParkour012 said:
Ah I thought Sony released a fully functioning AOSP firmware. My bad.
200gb? That's huge. I guess using my other PC for Ubuntu is a good choice.
Sent from my D6653 using Tapatalk
Click to expand...
Click to collapse
Sony releases support files for building AOSP, and yes, if you build from Sony sources, you will get pure Sony AOSP. However, the main intention of AOSP is customization, it is not intended as general purpose daiy use system.
Hello,
As some people heard, i really try to get Android Wear 2.0 for our beloved SmartWatch 3.
And it's possible, sources, device trees, all exist to build a working own compiled Android Wear 2.0.
So this thread tells about the current process of the port
PROGRESS
Code:
Repo synced
First build finished (not buildable yet due no blobs included
GAPPS Porting in progress
Fixed to 99% the device tree
Updating Blobs to M1D64T in progress
Using own Device tree
SOURCES
Device Tree for tetra:
https://github.com/Sony-SmartWatch-3-OSS/android_device_tree_tetra_eng_prerelease
Device Kernel for tetra (unmodified):
https://android.googlesource.com/kernel/bcm/+/android-wear-6.0.1_r0.99
(we can use MM kernel on Nougat too, maybe some patches needed but that's okay)
Prebuilts/Blobs for tetra:
https://github.com/Sony-SmartWatch-3-OSS/vendor_prebuilts_tetra
For Discussions go to this thread please: https://forum.xda-developers.com/smartwatch-3/general/companion-thread-android-wear-2-0-t3565693
If you want to help me on this project, write to me via telegram: https://t.me/PDesire
I need that so much any ETA ?
By the way keep up the good work !
Nice to see someone is working on this :victory:
Sent from my Sony Xperia Z5 using XDA Labs
Thanks for your job.
Enviado desde mi Redmi Note 3 mediante Tapatalk
great!!! thanks
Dear PDesire,,
My support can be only moral..... :crying:
And I hoping good news soon from you
Thx again for your great hard work :good:
thankx you great hard work and good luck my friend
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Certain components of Android (and therefore Wear) come from third parties and have licenses which require the source code to be made available (e.g. the Linux kernel). The components made available via the AOSP repositories for releases like Wear are, afaik, the components which have that type of license.
Wear is a release which has taken the same path as Honeycomb. I can understand that for open source fans and people looking to tinker with a working system it’s somewhat disappointing to see, but those are the choices Google has made.
Click to expand...
Click to collapse
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
drakonizer said:
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
Click to expand...
Click to collapse
Yeah I've seen these, and already fixed. Patch comes soon.
Things for WLAN and BT for example are on google repo too and if a library or something is missing we can use it from M1D64T
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
Click to expand...
Click to collapse
Lel then I can't understand why the build is working xD at least I am building in time and already 14% finished
I know some libs we have to grab from the Marshmallow FW but that shouldn't be a big deal
At least we also need some things from Preview 2 so we can get our AW 2.0 Preview 2 working
So I try my best to grab much from source and if required also from FW, but all in all its possible for our SmartWatch 3 to get Android Wear 2.0
Your PDesire
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
xpatze85x said:
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
Click to expand...
Click to collapse
Because there aren't any sources of the final version.
@PDesire :
You're the man...keep up a good work ???
Hey @PDesire , any news? I'm sooooo hyped!!!
Thank bro I hope
Thanks for this!
So current status is:
Code:
Repo synced
First Test build stopped to fix things on device tree
Expected in future:
Code:
Blobs dump
Fully fixed Device tree
Creating vendor for tetra
Adding overlays for framework to device tree
Some mix with armv7-a-neon generic
Gapps Dump
Expected in far future:
Code:
Creating an OSS project for tetra (like sonyxperiadev but for tetra)
So guys I will do more tomorrow as I am awake already from Friday 7AM - 3AM Saturday (right now GMT +1) and working on it and I need my sleep xD
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Your PDesire
PDesire said:
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Click to expand...
Click to collapse
And I can confirm my donation is coming when a working build is ready, and I suppose others are coming, isn't it guys? ???
Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app
Neo Cortex said:
Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app
Click to expand...
Click to collapse
No. That'll only work on an official firmware, unfortunately...
Thank you very much, hope you will finish it without problems~!
I just can't wait anymore
Deemooo said:
I just can't wait anymore
Click to expand...
Click to collapse
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
sorry, i don't understand the system domain, i just a normal xperia user, just want to use native android likes los,dotos,rr etc. I'm sorry i can't help you, All i can do is wait, that's some sad.
PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
Yes I see xperia merge fix in sources actually for kernel sources issue compile . I will create custom kernel for start . lineage later
PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android
vurg_usk said:
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android
Click to expand...
Click to collapse
I guess we can create repo vendor and extract proprietary blobs from stock vendor...
I tested phh gsi lineage and its fully stable guy - in bonus green tint is fixed -
Nice
And it's good that there is no green screen in custom roms
I can't wait for DotOS or other roms. XperiaUI is boring.
@ada12 Are you also building recovery?
Kyrimeas said:
Nice
And it's good that there is no green screen in custom roms
I can't wait for DotOS or other roms. XperiaUI is boring.
@ada12 Are you also building recovery?
Click to expand...
Click to collapse
for now no . I run actually gsi phh in daily use for stability . for sources I still work on it I have worked for compile kernel xperia https://github.com/Aarqw12/kernel_PDX213/commits/aosp/LA.UM.9.12.r1 but no luck actually its bootlop only for unknow reason.
Kyrimeas said:
Are you also building recovery?
Click to expand...
Click to collapse
You can try doing it yourself
[GUIDE]Porting TWRP without source
Yes, I know XDA is filled with such guides. But you can only port a TWRP if you implement parts of all the guides. This guide is a summation of all those guides. NOTE: I would be using AIK-Linux in this tutorial, since I don't recommend Windows...
forum.xda-developers.com
No actual programming required.
zpk787 said:
You can try doing it yourself
[GUIDE]Porting TWRP without source
Yes, I know XDA is filled with such guides. But you can only port a TWRP if you implement parts of all the guides. This guide is a summation of all those guides. NOTE: I would be using AIK-Linux in this tutorial, since I don't recommend Windows...
forum.xda-developers.com
No actual programming required.
Click to expand...
Click to collapse
for stability build-in is very recommanded
vurg_usk said:
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android
Click to expand...
Click to collapse
no need vendor image, need only flash oem.img xperia give really everything . lena sodp is no completly done for now , new features need to be implemented team sodp work on it. I guess just wait more
now xperia 10 III is officially added to open-source programm
Xperia 10 III added to Sony's Open Devices program - Sony Developer World
developer.sony.com
software binary released now we can compile rom
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
At the moment, we do not have lineageOS and recovery. There are only aosp sources that we can build.
Ada12 is currently building a custom kernel.
We will have roms for sure in the future.
xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
yeah，i also think we can have roms in the furture，im waiting
Kyrimeas said:
At the moment, we do not have lineageOS and recovery. There are only aosp sources that we can build.
Ada12 is currently building a custom kernel.
We will have roms for sure in the future.
Click to expand...
Click to collapse
at the moment aosp sony custom rom boot . I have tried and its no booted Haxk20 have confirmed recently its have booted finally and guide compile sony is updated. actually they are no lineage custom rom in this devices ( need adapt trees ) but lineage GSI is already available for this phone. for recovery sources bringup its no finish.
xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
You can check "e foundation" GSI. It's ungoogled phones
ada12 said:
at the moment aosp sony custom rom boot . I have tried and its no booted Haxk20 have confirmed recently its have booted finally and guide compile sony is updated. actually they are no lineage custom rom in this devices ( need adapt trees ) but lineage GSI is already available for this phone. for recovery sources bringup its no finish.
Click to expand...
Click to collapse
I'm sorry I have no idea what you're saying. There are already available custom AOSP roms, no? What a "lineage gsi" and how do I compile it (on a Windows)? All I need until a custom rom is released is too remove google from the phone entirely. This is possible?
xinniethewuflooh said:
I'm sorry I have no idea what you're saying. There are already available custom AOSP roms, no? What a "lineage gsi" and how do I compile it (on a Windows)? All I need until a custom rom is released is too remove google from the phone entirely. This is possible?
Click to expand...
Click to collapse
GSI is no a custom rom its a Generic System image , its update only /system ( os framework ) and use blobs,drivers from your /vendor , GSI is universal and run in all devices treble .
They are no custom rom available in public actually for this devices , source for custom rom is availlable but unstable in use ( sound only in headset , ril bug ... )
actually if you want run lineage or other custom android os use PHH GSI , or wait for custom rom ( NO ETA ).