• 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

-Currently Unavailable-

Furrydaus

Elite Member
Jul 6, 2014
1,888
4,402
0
21
Singapore
Thread will be closed until further notice

Let me make this clear; This project is meant for developers who are willing to pitch in and help create a succesful build for Android L. This is an early take on the Android L Platform and it WILL have a LOT of Bugs. If you are willing to help out and is someone who isn't a noob in the development sector, please feel free to continue. (If you are a noob, I do not condone you reading on but all I ask is that you do not request assistance for small tiny things that can be self learnt through Google)

What is this project about?
This project aims to continue to improve the Android L source code that is optimized for the Xperia SP. The code, which will be shown later, is in an experimental stage and I am not responsible for any bricked devices that are generated from MY CODE. It is your choice and liberty to try it out. With the code shown, developers can pitch in to improve it and fix many small to even major things that I might have missed.

More info....
The Code can be found here: https://github.com/Furrydaus/huashan_lollipop
Fork or Clone, its all up to you, just be sure to help out by submitting changes to the repo.
Repo Info: Android L - Initial Build. Codes built from AOSP for ARM Devices
Estimated Size: 14GB+
Object Count: 51242+
Object Type: Proprietary Files, Includes things from the system.img to the folders that are filled with all the proper apks
About: Just the proprietary files that have been generated through source building. Requires major overhaul to actually be optimized for the device.

Discuss more by replying. Do be warned that this code has 50% chance of working. It worked on my emulator but not quite sure about whether it'll run on my device (Need my phone for this week and have no time to reflash and stuff)

Good luck developing! Be sure to check in the git once in a while and sync to obtain the latest changes!

XDA:DevDB Information
Android L - Initial, ROM for the Sony Xperia SP

Contributors
Furrydaus, David Makarove, Ηλίας Μπουτσικάρης
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: AOSP

Version Information
Status: Testing

Created 2014-11-09
Last Updated 2014-11-09
 
Last edited:

RoXzAn

Senior Member
Jan 27, 2014
140
32
0
chennai

Let me make this clear; This project is meant for developers who are willing to pitch in and help create a succesful build for Android L. This is an early take on the Android L Platform and it WILL have a LOT of Bugs. If you are willing to help out and is someone who isn't a noob in the development sector, please feel free to continue. (If you are a noob, I do not condone you reading on but all I ask is that you do not request assistance for small tiny things that can be self learnt through Google)

What is this project about?
This project aims to continue to improve the Android L source code that is optimized for the Xperia SP. The code, which will be shown later, is in an experimental stage and I am not responsible for any bricked devices that are generated from MY CODE. It is your choice and liberty to try it out. With the code shown, developers can pitch in to improve it and fix many small to even major things that I might have missed.

More info....
The Code can be found here: https://github.com/Furrydaus/huashan_lollipop
Fork or Clone, its all up to you, just be sure to help out by submitting changes to the repo.
Repo Info: Android L - Initial Build. Codes built from AOSP for ARM Devices
Estimated Size: 14GB+
Object Count: 51242+
Object Type: Proprietary Files, Includes things from the system.img to the folders that are filled with all the proper apks
About: Just the proprietary files that have been generated through source building. Requires major overhaul to actually be optimized for the device.

Discuss more by replying. Do be warned that this code has 50% chance of working. It worked on my emulator but not quite sure about whether it'll run on my device (Need my phone for this week and have no time to reflash and stuff)

Good luck developing! Be sure to check in the git once in a while and sync to obtain the latest changes!

XDA:DevDB Information
Android L - Initial, ROM for the Sony Xperia SP

Contributors
Furrydaus, David Makarove, Ηλίας Μπουτσικάρης
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: AOSP

Version Information
Status: Testing

Created 2014-11-09
Last Updated 2014-11-09
This guy is so fast. If you need tester i am there to test the first build
 

MrSteve555

Elite Member
Nov 30, 2013
1,028
2,010
0
Just some loose things:
1. We need CAF code to be released and integrated in the sources by CM maintainers. CyanogenMod is compilable now, but only with Nexus devices and others that have AOSP kernels. Ofc, if we wanted to use AOSP code, transition from CAF to AOSP isn't easy(maybe it's even impossible). So yeah, we have to wait.
2. One step that we could do before working on L - testing encryption. If it's working, there's a big chance that we are set with 5.0. Could someone backup everything(internal storage also counts) and test this out? Just backup EVERYTHING, then go to Settings->Security->Encrypt your device.
3. Most of the changes are on the user-device interaction layer - chance of getting this working on LBL skyrockets :) We only have to confirm that ART and encryption work(and we can be sure that ART works).
4. Btw, one more thing about LBL - I don't really know how CAF names their repos, but I assume that the master branch is now for Lollipop. If it is, we don't even have to rewrite the specific patches.