• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][WIP]AOSP 5.0 Beta v2.0 | OTA 1 | Lollipop for Xperia Z2 [22-11-2014]

Search This thread

cheep5k8

Senior Member
Sep 26, 2012
587
1,067
Berlin
Yes the H logo seems to be missing as an asset, but good to have confirmation that mobile data works now. Thank you.
 

cheep5k8

Senior Member
Sep 26, 2012
587
1,067
Berlin
To the proceedings

Hello everyone,

At this point just a few words regarding etiquette and the progress on the project:

The project is a Beta and marked as WIP. It is known to us that not everything works, and maybe not even everything as advertised with each release (full or OTA).

We are very sorry for stuff like that the OTA ZIP installer is broken, but you've to to cut us some slack, really, with functionality on the ROM.

First of all without starting a flamewar, the CM12 build is just mostly built from CM sources while we actively work on AOSP code. Regarding that the progress we made from the initial release on the 16th up to now, or even the progress krabappel2548 made before making an initial release is quite considerable.

Regardless, this here is not a daily driver and it will not be so until we flag it as such. You can not magically expect everything to work just because we push a new update. Some things will work, some will not.

There might be regressions (i.e. stuff that used to work doesn't again), and some things that work for some people don't work for others. Such is life and development on AOSP.

At this current point we do not guarantee any functionality (and neither do we for bricking your device, as always).

If you spend half of the night installing the OTA and then it doesn't work like Sony's ROM that will be released at some point in 2015, well, we can't really help you there. They have the magic sauce (i.e. secret source code, blobs) and additional resources.

But you are always welcome to help us. Anytime. We're hiring.
 

adyscorpius

Senior Member
Hello everyone,

At this point just a few words regarding etiquette and the progress on the project:

The project is a Beta and marked as WIP. It is known to us that not everything works, and maybe not even everything as advertised with each release (full or OTA).

We are very sorry for stuff like that the OTA ZIP installer is broken, but you've to to cut us some slack, really, with functionality on the ROM.

First of all without starting a flamewar, the CM12 build is just mostly built from CM sources while we actively work on AOSP code. Regarding that the progress we made from the initial release on the 16th up to now, or even the progress krabappel2548 made before making an initial release is quite considerable.

Regardless, this here is not a daily driver and it will not be so until we flag it as such. You can not magically expect everything to work just because we push a new update. Some things will work, some will not.

There might be regressions (i.e. stuff that used to work doesn't again), and some things that work for some people don't work for others. Such is life and development on AOSP.

At this current point we do not guarantee any functionality (and neither do we for bricking your device, as always).

If you spend half of the night installing the OTA and then it doesn't work like Sony's ROM that will be released at some point in 2015, well, we can't really help you there. They have the magic sauce (i.e. secret source code, blobs) and additional resources.

But you are always welcome to help us. Anytime. We're hiring.
I totally appreciate the effort you spent into development, and maybe I can't thank you enough for that. I know how tough it is to get things going, I've been there and done that. Look for AdyScorpius roms and you'll know.

My only point as a fellow developer is, don't mention in the OP something thats contradicting. You say calling works and sound routing fixed, and then in the fine print mention that headset works fine.

What you claim to fix with the OTA is something already fixed in the other ROM. It doesn't help much in general to do repetitive work. And I would suggest syncing with fixes done by others for the greater good.

Having said that, I didn't intend to blame you guys for my time spent or anything like that. It was my choice, and my own effort, and yes, you didn't ask or force me to do it.

I actually suggested the updater-script fix for OTA 1. So I dunno why I am being taken wrongly here..
 

cheep5k8

Senior Member
Sep 26, 2012
587
1,067
Berlin
What you claim to fix with the OTA is something already fixed in the other ROM. It doesn't help much in general to do repetitive work. And I would suggest syncing with fixes done by others for the greater good.

Somewhere in the OP it says "calling might only work with headset" but generally audio routing is fixed! Before the OTA, the device didn't even recognize a plugged in headset. Those are two not completely related issue.

As for not duplicating work, no one is really doing that here. We can't really apply CM source code 1:1 to AOSP. I mean, otherwise it would be just AOSP (or CM), right? Not because we have some kind of difference in our political stance or whatever, but because you can't really swap source code like lemonade from one jar to another. There are reasons why CM is CM and AOSP is AOSP. You should know that.

Having said that I will, once I get the time, definitely look at what the CM people have done, and see if we can in some way transfer the changes into our ROM (and add some kind of thanks or, whatever in that direction, of course).

I'm sitting here right now and am testing some patches from commits to Google's AOSP to fix the voice audio.

I'm not sure what I can do more, irrespectibly of the fact that I'm even doing this in my free time that I don't even really have. My girlfriend is waiting for me right now because she wants to go outside with me.

Which I'll probably do.
 

adyscorpius

Senior Member
Somewhere in the OP it says "calling might only work with headset" but generally audio routing is fixed! Before the OTA, the device didn't even recognize a plugged in headset. Those are two not completely related issue.

As for not duplicating work, no one is really doing that here. We can't really apply CM source code 1:1 to AOSP. I mean, otherwise it would be just AOSP (or CM), right? Not because we have some kind of difference in our political stance or whatever, but because you can't really swap source code like lemonade from one jar to another. There are reasons why CM is CM and AOSP is AOSP. You should know that.

Having said that I will, once I get the time, definitely look at what the CM people have done, and see if we can in some way transfer the changes into our ROM (and add some kind of thanks or, whatever in that direction, of course).

I'm sitting here right now and am testing some patches from commits to Google's AOSP to fix the voice audio.

I'm not sure what I can do more, irrespectibly of the fact that I'm even doing this in my free time that I don't even really have. My girlfriend is waiting for me right now because she wants to go outside with me.

Which I'll probably do.
CM source in terms of framework is different. You can use the device trees across all aosp, which is why its easy to port all aosp based roms once CM is ported.
 

brouwerchris

Senior Member
Apr 8, 2011
609
785
Westervoort
OPPO Find X3 Pro
@cheep5k8 : you said you're hiring, may I suggest :

I had the same issue on the C6603 (Xperia Z) - your kernel is probably missing uid-based routing: The missing support freaks out netd and causes incomplete routing tables.

This should do it:
https://github.com/adrian-bl-yuga/k...mmit/768ec05fd4b48ffe02c2657e3d00b27a7184e199
..and this to avoid kernel-panic-funtimes:
https://github.com/adrian-bl-yuga/k...mmit/77c0a69a00ea86ef9b1121bc8de441d56cd321d0


(cherrypicked from the google-msm kernel)

If you need any help with the device bringup feel free to PM me: I got everything working on the C6603 (http://www.blinkenlights.ch/ccms/android/yuga-l.html) and the hardware of the Z2 is almost the same anyway.

PS : maybe then you'll get more time for your girlfriend....
 
Last edited:
  • Like
Reactions: Envious_Data

cheep5k8

Senior Member
Sep 26, 2012
587
1,067
Berlin
CM source in terms of framework is different. You can use the device trees across all aosp, which is why its easy to port all aosp based roms once CM is ported.
OK thanks for the info. I should perhaps add that this is the first time I work with the AOSP source itself at this level (I work as Android app developer at daytime).
 

Envious_Data

Senior Member
Oct 12, 2012
4,869
2,280
Imagination
enviousmedia.design
I shouldent have tried lolipop

It has exited me very much and has killed my patients when it comes to CM12 or AOSP-Lolipop

Its good to see progress.

But back to topic, im quite sure cm team has a partialy working camera wrapper for cm12
 

cheep5k8

Senior Member
Sep 26, 2012
587
1,067
Berlin
The source code will be online when we get around to it, it WILL be online at some point in any case. I managed to get the non-CAF msm8974 audio hal working without any CM code, believe it or not.

And even if we did use CM code, what would be the point in trying to hide that?
 

infected_

Recognized Developer
Jul 12, 2008
5,903
14,466
OnePlus 8
The source code will be online when we get around to it, it WILL be online at some point in any case. I managed to get the non-CAF msm8974 audio hal working without any CM code, believe it or not.

And even if we did use CM code, what would be the point in trying to hide that?

no need to get upset..



(...) the CM12 build is just mostly built from CM sources while we actively work on AOSP code. (...)

if you say that you made your own AOSP fixes, i just wanted to have a look... but we're cool.

thanks anyway.. :)
 

cheep5k8

Senior Member
Sep 26, 2012
587
1,067
Berlin

I have a full time day job and a spouse. I'm not sitting in my parent's basement around the clock hacking on some AOSP source code.

It's my first time working with AOSP so I don't have a proper file layout on my machine nor did I have forked repositories until recently so that I could simply make a change and then push it, and link you to the commit.

IF that was the case, then I would understand that you're hesitant. But it is not. At this point, at least I (krabappel2548 is more experienced with that), am still just poking around in parts of the code, and once I have something that works in a solid manner I'll make commits, push them and you can view them all you want, but I will not randomly push some random code just to be then, from the other side, be ridiculed that it's not working or even a total piece of crap, because that's what it will be if you (excuse the pun) push me to push it just right now.

I hope you guys understand. There will be full source trees of everything that we're doing.
 

Envious_Data

Senior Member
Oct 12, 2012
4,869
2,280
Imagination
enviousmedia.design
<Le SNIP>
I hope you guys understand. There will be full source trees of everything that we're doing.

Honnestly i say dont put too much time into this, if you have a job and a family to work with then work with that and not this.

Also you have other devs Working on aosp too in the z2 section so working on this isnt neccisarily top priority if getting it fully working is the aim.

AOSP from what i have been told requires alot of manual work vs CM or CM based

Source~/XDA User:Letama
 

benjmiester

Senior Member
Feb 15, 2012
985
285
Sony Xperia XZ1
Google Pixel 6 Pro
Do I flash the original rom files plus OTA 1 and 2? Or just original files and then OTA 2?

---------- Post added at 12:24 AM ---------- Previous post was at 12:19 AM ----------

(I'm coming from the CM12 rom)

Wait, now I only see the OTA1 and OTA 2 files and a cache.img in the main directory. Hmm.
 
Last edited:

zawkoko

New member
Aug 23, 2013
4
0
I'm not understand how to flash system.img and boot.img. Can u guide me any idea.

I'm just useing command,

For system.img
fastboot flash system system.img

and

For boot.img
fastboot flash boot boot.img

but yet not working, looping in logo.

other way i have to use command

fastboot flash system system.img
fastboot flash system boot.img

not working too.

Pls, guide me how can I do.
 

Li-polymers

Senior Member
Apr 22, 2012
224
49
Melbourne
I'm not understand how to flash system.img and boot.img. Can u guide me any idea.

I'm just useing command,

For system.img
fastboot flash system system.img

and

For boot.img
fastboot flash boot boot.img

but yet not working, looping in logo.

other way i have to use command

fastboot flash system system.img
fastboot flash system boot.img

not working too.

Pls, guide me how can I do.

Did you wipe data before flash?
If not try flashing another kernel with recovery then wipe data and start again.

Sent from my Xperia Z2 using XDA Free mobile app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 39
    BiakxEt.png

    Hello everyone,

    We present to you Android 5.0 AOSP for Xperia Z2. This is for the people that can't wait to see how lollipop looks like on Z2.

    == Project status ==
    Working:
    - Bluetooth
    - Wifi
    - LED
    - Texting (with OTA 1)
    - Calling (with OTA 1)
    - Sound
    - Sensors
    - Auto-Brightness
    - Vibration
    - Screen/Touch
    - SELinux
    - Mobile Data (with OTA 1)

    - everything that's not in the "not working list"

    Not working:
    - Camera
    - Mic on calling??
    - Youtube Video Playback
    - GPS
    - ....

    == Updates ==

    OTA 1

    The OTA 1 is a flashable ZIP. It contains a new kernel that now has a recovery, however, in order to flash it on the base ROM without the first OTA, you will need to flash a kernel (any kernel for Z2) with a recovery, then flash the OTA (maybe via ADB sideload).

    After the OTA has been flashed you will have a kernel for this ROM with recovery, so you will not need to repeat this procedure again in the same way (but for the next OTA simply boot into the now existing recovery).

    OTA 1 will give you complete sound (with headphone jack detection and proper audio routing; sound in calls might work only via headset) and mobile data.

    THE OTA IS NOT A FULL ROM! YOU FIRST NEED TO FASTBOOT
    FLASH THE IMAGES FROM THE MAIN DOWNLOAD. IF YOU FLASH ONLY THIS,
    IT WILL NOT BOOT!


    - You have to be on the main ROM first; if you are, go to the next step, if not, see the main instructions first
    - Download the ZIP (see Download section)
    - Flash any kernel for Xperia Z2 with recovery
    - Boot into the recovery
    - Flash the OTA 1 signed zip
    - Wait until it's done (it might take a moment)
    - The update will tell you when you can reboot
    - Reboot
    - Test&Report!

    Thank you for choosing krabappel2548 + cheep5k8!

    == Download ==
    Download all files from the correct device folder, can be found in the common-files directory, system and kernel are in the version directories :)
    - ROM: Xperia Z2 AOSP 5.0 Beta v2.0
    - Gapps can be found in the main directory ;)
    - OTA 1: Xperia Z2 AOSP 5.0 Beta OTA 1

    - OPTIONAL: Sony's Unified Kernel built for Z2 (UNOFFICIAL) (includes patches for voice calling, video playback, etc.; basically, everything works except for camera)



    == Already on this rom?? ==
    No need to wipe data unless I tell it in the thread :)
    - Just flash system.img and boot.img using fastboot.
    - Don't forget to flash gapps by hotbooting a kernel with recovey ;)

    == Installation instructions: ==
    - Wipe userdata in recovery
    - flash all 3 partitions using fastboot
    Don't do this when you don't know what you are doing!!

    You can flash gapps with any kernel with recovery. Just flash back the AOSP kernel to boot into device afterwards :)

    == Changelog ==
    Code:
    [QUOTE][B]== Beta v3 (via OTA 1)==[/B]
    - Mobile Data working (RIL working, routing to modem device fixed)
    - Calls and Texts working
    - Sound routing/headphone jack detection working
    - Wifi stability improvements
    [/QUOTE]
    
    [B]== Beta v2 ==[/B]
    - Sensors are fixed
    - first Z1 compact, Z2, Z3 and Z3 compact release
    - Latest 3.5.2.2 kernel
    - Mic is working while calling????
    - Auto-brightness fixed
    - Rotation is working
    
    [B]== Beta v1.1 ==[/B]
    - Wifi is a lot more stable
    - Updated kernel
    - charging-LED is working now
    - Rom is more stable and supersmooth
    
    [B]== Beta v1.0 ==[/B]
    - Bluetooth
    - Wifi
    - LED
    - Texting
    - Calling
    - Sound
    - Brightness Slider (autobrightness doesn't work yet, turn it off to make slider working)
    - Vibration
    - Screen/Touch

    == Screenshots ==
    In the screenshot part of devdb project are more screenshots ;)

    attachment.php


    attachment.php


    attachment.php


    6weWJpM.png


    Hpl3gJ9.png


    XDA:DevDB Information
    [ROM][WIP]AOSP 5.0 Beta v2.0 | OTA 1 | Lollipop for Xperia Z2 [22-11-2014], ROM for the Sony Xperia Z2

    Contributors
    krabappel2548, cheep5k8
    Source Code: https://github.com/xperia-aosp-project?tab=repositories

    ROM OS Version: 5.0.x Lollipop
    ROM Kernel: Linux 3.4.x
    ROM Firmware Required: Unlocked bootloader
    Based On: AOSP

    Version Information
    Status: Beta
    Current Beta Version: 2.0
    Beta Release Date: 2014-11-16

    Created 2014-11-16
    Last Updated 2014-12-19
    36
    Next update is going to be a big one guys :) texting, calling, WiFi etc all working. Also some other smaller things are fixed :p

    Sent from my Xperia Z1 (AOSP) using XDA Free mobile app
    28
    To the proceedings

    Hello everyone,

    At this point just a few words regarding etiquette and the progress on the project:

    The project is a Beta and marked as WIP. It is known to us that not everything works, and maybe not even everything as advertised with each release (full or OTA).

    We are very sorry for stuff like that the OTA ZIP installer is broken, but you've to to cut us some slack, really, with functionality on the ROM.

    First of all without starting a flamewar, the CM12 build is just mostly built from CM sources while we actively work on AOSP code. Regarding that the progress we made from the initial release on the 16th up to now, or even the progress krabappel2548 made before making an initial release is quite considerable.

    Regardless, this here is not a daily driver and it will not be so until we flag it as such. You can not magically expect everything to work just because we push a new update. Some things will work, some will not.

    There might be regressions (i.e. stuff that used to work doesn't again), and some things that work for some people don't work for others. Such is life and development on AOSP.

    At this current point we do not guarantee any functionality (and neither do we for bricking your device, as always).

    If you spend half of the night installing the OTA and then it doesn't work like Sony's ROM that will be released at some point in 2015, well, we can't really help you there. They have the magic sauce (i.e. secret source code, blobs) and additional resources.

    But you are always welcome to help us. Anytime. We're hiring.
    20
    Seems @cheep2sk8 got modem working and I found a way to patch kernel to allow proper net routing for mobile data ;) I can confirm mobile data will be working on next release :)
    15
    Ok, to everyone I'm getting closer to fixing the mic bug. I'm working on my Z1 now, but if it's fixed there, it will be fixed here as well with similar code ;)

    Sent from my Xperia Z1 (AOSP) using XDA Free mobile app