AOSP 5.0 based News
The much anticipated Android L is now live on AOSP. That's something very exciting.
COMPLETE ANDROID 5.0 L SOURCE : HERE
Code:
repo init -u https://android.googlesource.com/platform/manifest -b android-5.0.0_r1
Google ads few more tags for the source ending with r2, r3, r4, r5, r6 and r7.
The King of Rooting "Chainfire" manages to root Android L which was earlier lot in discussions about the difficulty in rooting Android L. Head on HERE for more info.
Omnirom manages to boot on Lollipop for Nexus 7. Head on here for info
CM12 project has initiated creating msm8226 branches bringing in some more excitement to the table Official Changelogs
CHANGELOG from KitKat to Lollipop . and R1-R7
@SeannyM manages to boot lollipop CM12 for Moto G 2013 Still a work in progress. Visit ROM thread here.
More Lollipop ROM's based of CM12/AOSP by:
Code:
[B][COLOR="DarkSlateBlue"]Alberto [/COLOR][/B]:[URL=http://forum.xda-developers.com/showthread.php?t=2942491] Link [/URL]
[B][COLOR="DarkSlateBlue"]Anerik [/COLOR][/B]:[URL="http://forum.xda-developers.com/moto-g/development/5-0-cyanogenmod-12-t2950466"]Link[/URL]
[B][COLOR="DarkSlateBlue"]StrangeWeather [/COLOR][/B]:[URL="http://forum.xda-developers.com/moto-g/development/rom-aosp-code-aurora-t2943252"]Link[/URL]
[B][COLOR="DarkSlateBlue"]Matrinusbe [/COLOR][/B]:[URL="http://forum.xda-developers.com/moto-g/orig-development/rom-gzroms-validus-13-t2864662"]Link[/URL]
[B][COLOR="DarkSlateBlue"]Teamex [/COLOR][/B]:[URL="http://forum.xda-developers.com/moto-g/orig-development/rom-xperience-9-0-0-t2952466"]Link[/URL]
Lollipop Kernels by:
Code:
[B][COLOR="DarkSlateBlue"]Teamex [/COLOR][/B]:[URL="http://forum.xda-developers.com/showthread.php?t=2786336"]Link[/URL]
[B][COLOR="DarkSlateBlue"]Fermasia [/COLOR][/B]:[URL="http://forum.xda-developers.com/moto-g/orig-development/kernel-donkey-kang-kernel-v1-t2933761"]Link[/URL]
Make XT1033 adapt to CM12 single sim: Guide. Thanks @padhu1989
One of the reputed developer of Moto G "QUARX" is also working on Android L and about to be accomplished. Visit here for Info Thanks @abhifx and @Sandivisi for the info.
Extras: XDA users willing to gear up in compiling kernel can refer to the Guide by @YoshiShaPow for MotoG specific compilation. My earlier mention about "CYGWIN_guide" unfortunately can't be used to compile kernel 3.4.x
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto G -Android L stock News
Rollout for Moto X and G 2014 begins.
Release Notes information from Motorola can be found in Motorola Official Blog
Chainfire has released an easy rooting kit for MOTOROLA variants. Grab it for your Moto G. Thanks @abhi0502 for sharing this info.
Brazilian Motorola cust support website reveals 5.0 release notes for G2 and G1. Visit this post for more. To add more here goes twitter confirmation from moto brasil. Screenshot here Thanks @MarckozZ
All about soak experience. Visit HERE
SOURCE OF INFO : XDA NEWS , GITHUB and GOOGLE
Wowow this stuff is all so exciting! May not even have to restore to stock as right now I'm running CM11
Oh boy, I'm all giddy like a little kid again. This wait for Lollipop in general to come out has been so painstaking yet I know the wait will be worth it. It really doesn't help me personally since I had a port of the developer preview a few months ago on my Nexus 4 before I broke it, it was just a fleeting taste of it. xD
Now just somebody needs to build aosp rom for moto g
Theres so much that needs to be pushed yet, like A LOT...Theres simply too much hype building out there...
I was wondering whether the device tree would remain same OR it needs to be re-based as done by dhacker earlier. Hope not, else its gonna be another major milestone to reach out android L.
As per some newsfeed available at Google, the CyanogenMod team is likely to begin with L in December with CM12 nightlies. Meanwhile can't say the moto g stock may arrive as they are ready with it
==vj== said:
I was wondering whether the device tree would remain same OR it needs to be re-based as done by dhacker earlier. Hope not, else its gonna be another major milestone to reach out android L.
As per some newsfeed available at Google, the CyanogenMod team is likely to begin with L in December with CM12 nightlies. Meanwhile can't say the moto g stock may arrive as they are ready with it
Click to expand...
Click to collapse
Obviously it will have to be re-based and addapted to our device, since it has to have some tweaks for CPU, camera, audio, display, sensors, blabla etc... So it will pass some time after we can get our hands to a 5.0 build.
MarckozZ said:
Obviously it will have to be re-based and addapted to our device, since it has to have some tweaks for CPU, camera, audio, display, sensors, blabla etc... So it will pass some time after we can get our hands to a 5.0 build.
Click to expand...
Click to collapse
Guess what.... Quarx is already on the job
Check his fb page
reversegear said:
Guess what.... Quarx is already on the job
Check his fb page
Click to expand...
Click to collapse
Can you tell mw who is Quarx? Than name sound familiar
EDIT: I remember him from Defy forum....
EDIT 2: He is working on Lollipop for Defy, not for Moto G right now...
Quarx is also a developer holding CM thread here for Moto G. And kernel by Blechdose in combination.
Regarding whether he's onto Android L , no idea yet. But Anderson - N5XPA developer is onto L as of now with his first build for Nexus.
But yeah again, for Nexus its easy since everything is set readymade from Google, just compile and build. Whilst for our Moto G needs to be set first with device tree. So this is a major milestone as of now to our developers. Correct me if I am wrong at any point
Request
Guys whoever of you receives android L first over ota, please be sure to share the zip file of the new stock rom right here on XDA
MarckozZ said:
Obviously it will have to be re-based and addapted to our device, since it has to have some tweaks for CPU, camera, audio, display, sensors, blabla etc... So it will pass some time after we can get our hands to a 5.0 build.
Click to expand...
Click to collapse
So basically its following files that are needed from existing base "CM11".
/system/lib/hw
/system/lib/modules
/system/lib/soundfx
/system/lib/egl
/system/etc/firmware
/system/etc/permissions
/system/vendor
==vj== said:
So basically its following files that are needed from existing base "CM11".
/system/lib/hw
/system/lib/modules
/system/lib/soundfx
/system/lib/egl
/system/etc/firmware
/system/etc/permissions
/system/vendor
Click to expand...
Click to collapse
ñeeeeeeeeeeee nop, you need adapt the source to compatibility of motorola ****'s xD
(like sound , HW) not only the blobs isn't a fast and easy way coz isn't a Nexus device.
On nexus only download the source and make a build Easy, on others phone's not.
is some more stuff but maybe it can be more easy coz CAF are working faster on it and we can make a patches to use and build fine the rom.
TeamMex said:
ñeeeeeeeeeeee nop, you need adapt the source to compatibility of motorola ****'s xD
(like sound , HW) not only the blobs isn't a fast and easy way coz isn't a Nexus device.
On nexus only download the source and make a build Easy, on others phone's not.
is some more stuff but maybe it can be more easy coz CAF are working faster on it and we can make a patches to use and build fine the rom.
Click to expand...
Click to collapse
Thank you..! That was a great piece of information
So @Quarx works on the Defy port atm? What about us?
As I was hunting hard across github today. I suddenly came across FALCON TREE based of Android L Developer preview made by Alberto97. It has the ROM uploaded at github as well. So anyone knows about the status of this project. Was the preview booting..?
Link : Github
I checked the build status here and it ran about 2.52 min in server and it was done before two months. check details here https://travis-ci.org/Alberto97/Android-L-Falcon
pico hackr said:
I checked the build status here and it ran about 2.52 min in server and it was done before two months. check details here https://travis-ci.org/Alberto97/Android-L-Falcon
Click to expand...
Click to collapse
Thank you for the quick info. Hmmm, yes I was aware its Android developer preview and done 3months ago. But was unaware about the status of the project. So, it ran for almost 3 mins could mean of some progress
==vj== said:
As I was hunting hard across github today. I suddenly came across FALCON TREE based of Android L Developer preview made by Alberto97. It has the ROM uploaded at github as well. So anyone knows about the status of this project. Was the preview booting..?
Click to expand...
Click to collapse
Hello
Would you please post a link to this rom you speak of? Many thanks.
==vj== said:
Thank you for the quick info. Hmmm, yes I was aware its Android developer preview and done 3months ago. But was unaware about the status of the project. So, it ran for almost 3 mins could mean of some progress
Click to expand...
Click to collapse
actually build excited with status 0 , means the build is unsuccessful
Related
About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use the code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
Features
All of our features can be found on the site here:
Carbon Features
Here are some screenshots:
All screens are from the Galaxy S4 i9500
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
New builds at this link : Carbon Rom Download - jactiveltexx
Gapps
Ultra Slim Gapps
Bugs
Nil
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon and my other roms better with every release. Your support means the world to us! If you've enjoyed Carbon and my other roms, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon and my other roms!
Source:
1. Rom Source : https://github.com/CarbonDev
2. Device Tree : https://github.com/spegelius/android_device_samsung_jactivelte/tree/cm-11.0
3. Kernel Source : https://github.com/spegelius/android_kernel_samsung_jactivelte/tree/cm-11.0
XDA:DevDB Information
Carbon Rom 4.4.4, ROM for the Samsung Galaxy S 4 Active
Contributors
a2441918
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Rooted and CWM recovery
Based On: CyanogenMod
Version Information
Status: Testing
Current Stable Version: 15.0
Stable Release Date: 2014-06-29
Created 2014-03-29
Last Updated 2014-06-29
Reserved
Changelogs
Reserved
Installing...
I just Installed it... You will have news soon. Thank you for your time...
P.S. Would you like to look something special and report you ?
Bugs, video recording.
Does it mean that it doesn't record video at all or... kind of new to CM/AOSP roms so sorry if noob question
So far best custom rom to i9295 that i have used. Fast and all the options I need.
But does somebody know how to enable Lockscreen widgets on this rom? I have not found a option to do so. Lockscreen options has a place to change clock options but that does not effect on anything.
@Malous is the gps stable? (ie during navigation, I completely lost the gps symbol with 4.3 custom roms, after some minutes the icon returned and with it gps reception - it would be nice to know if this issue is fixed for s4a or not
pen² said:
@Malous is the gps stable? (ie during navigation, I completely lost the gps symbol with 4.3 custom roms, after some minutes the icon returned and with it gps reception - it would be nice to know if this issue is fixed for s4a or not
Click to expand...
Click to collapse
I'm sorry I do not have a S4 Active. Kindly test and report back so that I can add to OP.
BTW new build is up and running,.
@a2441918 I was too impatient and flashed (v2) yesterday. GPS looks good so far, if there are any issues I'll post them here. Thanks for supporting the s4a!
/Edit: Could you please include a version number or a date in your filenames? Otherwise it is diffifult to know which file to flash in recovery, if you also downloaded an older version.
Furthermore, it would be great to know the correct md5 of each download and one or two sentences in the OP regarding gapps (where to get, when to flash, do gapps need to be flashed after an carbon upgrade or not?)
pen² said:
@a2441918 I was too impatient and flashed (v2) yesterday. GPS looks good so far, if there are any issues I'll post them here. Thanks for supporting the s4a!
/Edit: Could you please include a version number or a date in your filenames? Otherwise it is diffifult to know which file to flash in recovery, if you also downloaded an older version.
Furthermore, it would be great to know the correct md5 of each download and one or two sentences in the OP regarding gapps (where to get, when to flash, do gapps need to be flashed after an carbon upgrade or not?)
Click to expand...
Click to collapse
Updated the names of the files. Appended version name at the end. I will add Gapps data during next build.
So far so good. Could you please tell me how to synchronize contacts with Facebook (for incoming photo). I love the way that battery least forever almost 1 day.
Gpx works great.
Thank you for this great ROM my friend...
Sent from my GT-I9295 using xda app-developers app
wow, i flashed this rom today. its sooo good! I hope we get official Builds of this some day. THANK YOU SO MUCH!!!
Hi guy, I'm pretty much a noob and I installed the ROM. The ROM looks good and fast.
How can I use Gmail, Google Play etc with it?
Actually there no gapps for it? Isn't there any way to bypass and install Google apps?
Thanks
OK got that working thanks to Gapps Manager : http://forum.xda-developers.com/showthread.php?t=2589167&page=5&nocache=1
moviecut said:
wow, i flashed this rom today. its sooo good! I hope we get official Builds of this some day. THANK YOU SO MUCH!!!
Click to expand...
Click to collapse
Official build will start once spegelius fixes the video recording bug. He can do it. BTW new build coming up.
One dumb question: do you confirm can we just instal each new build without any factory reset and therefore without the backup\restore of the applications? And thanks for the build!
Toncino said:
One dumb question: do you confirm can we just instal each new build without any factory reset and therefore without the backup\restore of the applications? And thanks for the build!
Click to expand...
Click to collapse
Yes it doent wipe data. Btw who wants Vanir AOSP for S4 Active? Some 50 thanks to this post and you will have it. Ask your friends, team members too.
i just noticed, how good the battery life of this rom is. it is much better that the sammy rom or cm11! How is that possible? i use the app "system panel" for monitoring. the interesting part about this is, that with carbon i get only 1% CPU base load (Samsung an CM11 give me about 3% base load). I dont know the differences or if this is just a feeling....
Hi, is this just for the i9295 or will it work on the SGH-i537 AT&T?
Hey just wanted to know is there is a way to change the display density of this rom. Tried to change from build prop but it doesn't change at all
Sent from my GT-I9295 using xda app-developers app
hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/know.../open-devices/
feel free to fork, build, fix and push back
Br
J
Is this pure Android development, apart from CM?
V4LKyR said:
Is this pure Android development, apart from CM?
Click to expand...
Click to collapse
Yes.
Sent from my D6503 using Tapatalk
Good news. My previous device was m7. Flashed continuously new roms. I bought Z2, 3 months before, still stock.
get error while compiling following the instructions on git-hub.
So now we can build more stable builds as we have device tree from sony right?
So.... How fast will Lollipop reach AOSP? After Sony released their normal ROMs?
I have successfully built it
I have successfully built this rom using Linaro ToolChain
It's so smooth butit has many bugs till now like:-
* Screen brightness always full cannot change.
* Bluetooth share force close screen appearing all time
* No Automatic screen Rotation
* Camera is Broken
* No phone service
Maybe it's just me because I used Linaro.. Anybody successfully built it too??
I will try to build it again using regular gcc toolchain and see if anything changes.
EDIT : -
A ScreenShot of it:-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I long the day omnirom will appear because of this.
mcqcdtbootimg
I've been trying to build the ROM from sources. Downloaded everything required and started to compile.
I face a problem while making the boot.img . I understand we need to use mkqcdtbootimg instead of just mkbootimg. I downloaded the sources of mkqcdtbootimg from Sony's git repo and places it under /source/system/extras. Even after doing those steps I seem to face a problem. Am I doing something wrong ? I'm still a newbie in ROM development. Any help will be highly appreciated
tejaswi.rohit said:
I've been trying to build the ROM from sources. Downloaded everything required and started to compile.
I face a problem while making the boot.img . I understand we need to use mkqcdtbootimg instead of just mkbootimg. I downloaded the sources of mkqcdtbootimg from Sony's git repo and places it under /source/system/extras. Even after doing those steps I seem to face a problem. Am I doing something wrong ? I'm still a newbie in ROM development. Any help will be highly appreciated
Click to expand...
Click to collapse
You need to place this source into external/mkqcdtbootimg of your source code and then compile it again.
Sent from my Xperia Z2 using Tapatalk
Myself5 said:
You need to place this source into external/mkqcdtbootimg of your source code and then compile it again.
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
Ah! Thanks Will do that. In the mean time I compiled it separately and replaced mkbootimg with it
P.S. If someone is facing trouble to compile mkqcdtbootimg make sure you have all your ssl libraries installed and linked properly in Ubuntu. I had to install this libssl-dev to get it to compile there was some linker issue without it in 14.04.
tejaswi.rohit said:
I've been trying to build the ROM from sources. Downloaded everything required and started to compile.
I face a problem while making the boot.img . I understand we need to use mkqcdtbootimg instead of just mkbootimg. I downloaded the sources of mkqcdtbootimg from Sony's git repo and places it under /source/system/extras. Even after doing those steps I seem to face a problem. Am I doing something wrong ? I'm still a newbie in ROM development. Any help will be highly appreciated
Click to expand...
Click to collapse
Hi,
Actually you have to download it to system/core folder not system/extra..
Hope that works for you
lol late one...
Gen1usw0rk said:
I have successfully built this rom using Linaro ToolChain
It's so smooth butit has many bugs till now like:-
* Screen brightness always full cannot change.
* Bluetooth share force close screen appearing all time
* No Automatic screen Rotation
* Camera is Broken
* No phone service
Maybe it's just me because I used Linaro.. Anybody successfully built it too??
I will try to build it again using regular gcc toolchain and see if anything changes.
EDIT : -
A ScreenShot of it:-
View attachment 2978806
Click to expand...
Click to collapse
I compiled the ROM successfully and I'm facing the same problems as you're. I didn't use Linaro tool chain. I guess it has something to do with the device drivers. Hope we get them fixed soon. The ROM is fluid though
Gen1usw0rk said:
I have successfully built this rom using Linaro ToolChain
It's so smooth butit has many bugs till now like:-
* Screen brightness always full cannot change.
* Bluetooth share force close screen appearing all time
* No Automatic screen Rotation
* Camera is Broken
* No phone service
Maybe it's just me because I used Linaro.. Anybody successfully built it too??
I will try to build it again using regular gcc toolchain and see if anything changes.
EDIT : -
A ScreenShot of it:-
View attachment 2978806
Click to expand...
Click to collapse
tejaswi.rohit said:
I compiled the ROM successfully and I'm facing the same problems as you're. I didn't use Linaro tool chain. I guess it has something to do with the device drivers. Hope we get them fixed soon. The ROM is fluid though
Click to expand...
Click to collapse
it has to do with the blobs.... sony released sources for 4.4.2_r2... and the binaries also for 4.4.2, but AOSP is on version 4.4.4_r2 ... blobs are not compatible with current AOSP version...
so if you wanna build pure AOSP for sirius for ex (this device hasn’t even received 4.4.4 official), you have to compile 4.4.2, not 4.4.4 ..
regards
infected_ said:
it has to do with the blobs.... sony released sources for 4.4.2_r2... and the binaries also for 4.4.2, but AOSP is on version 4.4.4_r2 ... blobs are not compatible with current AOSP version...
so if you wanna build pure AOSP for sirius for ex (this device hasn’t even received 4.4.4 official), you have to compile 4.4.2, not 4.4.4 ..
regards
Click to expand...
Click to collapse
That totally makes sense. I shall switch my branch and try to compile again . Thanks
Update:
Downloaded 4.4.2 source and compiled the ROM again. The issues remain the same. I think the device drivers in the kernel need to be set right.
tejaswi.rohit said:
I've been trying to build the ROM from sources. Downloaded everything required and started to compile.
I face a problem while making the boot.img . I understand we need to use mkqcdtbootimg instead of just mkbootimg. I downloaded the sources of mkqcdtbootimg from Sony's git repo and places it under /source/system/extras. Even after doing those steps I seem to face a problem. Am I doing something wrong ? I'm still a newbie in ROM development. Any help will be highly appreciated
Click to expand...
Click to collapse
cd build && git cherry-pick 612e2cd0e8c79bc6ab46d13cd96c01d1be382139 && cd ..
will fix your error
br
J
jerpelea said:
cd build && git cherry-pick 612e2cd0e8c79bc6ab46d13cd96c01d1be382139 && cd ..
will fix your error
br
J
Click to expand...
Click to collapse
Thanks for the fix @jerpelea I see the cherry pick is to fix the mkbootimg error, but is there any chance this fix helps with the other sensors to work, or will have to wait for an updated kernel for the same ? (just curiosity )
infected_ said:
it has to do with the blobs.... sony released sources for 4.4.2_r2... and the binaries also for 4.4.2, but AOSP is on version 4.4.4_r2 ... blobs are not compatible with current AOSP version...
so if you wanna build pure AOSP for sirius for ex (this device hasn’t even received 4.4.4 official), you have to compile 4.4.2, not 4.4.4 ..
regards
Click to expand...
Click to collapse
thats completely wrong
modem and camera blobs are missing
br
J
jerpelea said:
thats completely wrong
modem and camera blobs are missing
br
J
Click to expand...
Click to collapse
glad you corrected me then, after @tejaswi.rohit ruled that out.. so ... where can we find these missing blobs? can we use themuppets repo for it?
ps: @jerpelea can you explain to me how can we build 4.4.4 for Z2 per ex, if the official stock 4.4.4 hasnt been released, and with it the blobs for 4.4.4..?
Thread will be closed until further notice
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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
Source Code Status
Source Code is being pushed to github. Will take up to a day so please wait
Update; Facing problems with Github. Will try my best to upload
Wow! Something to look forward to. Best of luck. I hope you'll succeed, for sure a lot of people are excited about this.
Furrydaus said:
Source Code is being pushed to github. Will take up to a day so please wait
Click to expand...
Click to collapse
IMO It should be in original development section.
Any way, great job
Sent from XSP using my hands!
Screenshot please
please give some screen shots and list of known bugs..
Furrydaus said:
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
Click to expand...
Click to collapse
This guy is so fast. If you need tester i am there to test the first build
I'll volunteer to test your rom too
kaustav07 said:
please give some screen shots and list of known bugs..
Click to expand...
Click to collapse
Please read the damn OP before posting....
Sent from my C5303 using XDA Free mobile app
tester
I would like to test future builds of the rom!
kaustav07 said:
please give some screen shots and list of known bugs..
Click to expand...
Click to collapse
Don't ever post what you don't know noob
For god's sake read the damn OP
Lolz. What a noob[emoji13] !!
@ everyone, calm down, no need to pull someone's leg, look at the bigger picture i.e. Android l.
Sent from XSP using my hands!
+1 if u need some tester, im not a dev but i want to help. Count me in and good lucky guys
I am sure we are going to get android l with these awesome developers and community
SORRY
noahvt said:
Please read the damn OP before posting....
Sent from my C5303 using XDA Free mobile app
Click to expand...
Click to collapse
sorry..i didn't read it first..
What about LBL? Mby do it at begining?
Tapatalked via Xperia SP
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.
Quoting uberlaggydarwin from g+
[QUOTE ]
Yay
+ Code Aurora Forum released LA.AF.1.1-01110 for
Lollipop.
[/QUOTE]
Is this the CAF code we are looking for ?
Sent from XSP using my hands!
In cyanogenmod source, here is a new CAF for CM12 : http://review.cyanogenmod.org/#/q/s...nMod/android+branch:cm-12.0+topic:caf-hal,n,z
I'm having high hopes for a functional build of android 5.0 for the XSP! The Xperia L just got a reasonably stable build of android 5.0
.
.
.
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICPAndroid Ice Cold ProjectAICP is known by everyone as Ice Cold Project that started on Desire HD and since then evolved into a mature ROM with the BEST community you can find!!!
Until Lollipop, Rom has always been AOKP based. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM when it comes to hardware, drivers and some features.
With the rebrand of CM to LineageOS (LOS) we are now actually LOS based.
If there are any bugs, either we will sort them out or LOS team, if it concerns their modifications. This rom isn't LOS supported, so no need to report errors or bugs to them!!
.
.
.
.
.
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
maxwen
DU team
SlimRom team
CarbonRom team
LiquidSmooth rom team
OmniRom team
Community
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
.
.
.
We are now paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 12.1
Download link: http://dwnld.aicp-rom.com/?device=griffin
Full Changelog link: http://dwnld.aicp-rom.com/?device=griffin
Don't disable Heads-Up. You might not be able to answer phone calls otherwise.
You tell...
The ROM should contain everything you need to enjoy Android Nougat. You don't need to install any Add-Ons, simply download the latest ROM, GApps, flash it, and go!
It is STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience strange behavior.
How to flash:
Again: Don't do it if you don't know it!
TWRP is the recommended custom recovery (and needed for OTA Updates)
1. full wipe
2. flash ROM
3. flash GApps
(The ROM has GApps persistance in between dirty flashes, so you only have to flash them once!
.
KERNEL:
Kernel in this ROM follows LOS source with custom additions.
PREREQUISITE FOR OTA:
To be able to flash over OTA app, TWRP recovery is needed.
You can still use CWM/LOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. Zip gets saved under AICP_ota folder on your internal SDcard.
Please be sure that you are on the latest TWRP recovery.
If you want to contribute to the AICP or wanna see what is being worked on/merged, feel free to visit our Gerrit review system. (Link is at the bottom!!!)
AICP G+ community
ROM Gerrit
You want to see a normal night at the "DEV office", click here!!
XDA:DevDB Information
AICP, ROM for the Moto Z
Contributors
vache
Source Code: https://github.com/AICP
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked bootloader, Custom Recovery
Version Information
Status: Stable
Stable Release Date: 2017-05-07
Created 2017-05-07
Last Updated 2017-05-07
Reserved
Hey Vache, great ROM, thanks for your efforts, I was using RR since your first releases and really appreciate your work.
I want to contribute with some of my time, there's a board about what we still need to port or improve? I get a bit annoyed about the lack of efficiency mode while using the battery mode, what we need to enable it? What kind of logs and classes we need. I don't have a stock image to flash and compare the logs =/
Amazing, thanks a lot.
Does Moto mods work?
Quick (Bug)report: cant disable the charging led,settings app fc
Thanks God!!!
Nice to see this ROM here.
Thank you so much.
t0n0n said:
Hey Vache, great ROM, thanks for your efforts, I was using RR since your first releases and really appreciate your work.
I want to contribute with some of my time, there's a board about what we still need to port or improve? I get a bit annoyed about the lack of efficiency mode while using the battery mode, what we need to enable it? What kind of logs and classes we need. I don't have a stock image to flash and compare the logs =/
Click to expand...
Click to collapse
It needs some system changes, still didn't check if it's open source on Moto github.
papampi said:
Amazing, thanks a lot.
Does Moto mods work?
Click to expand...
Click to collapse
Car dock, battery mod and audio mod should be ok. Another story for projector and camara one
mstrack said:
Quick (Bug)report: cant disable the charging led,settings app fc
Click to expand...
Click to collapse
Could you grab logs after FC ?
vache said:
It needs some system changes, still didn't check if it's open source on Moto github.
Click to expand...
Click to collapse
Can you point me to it? I can give it a look and see what is missing.
vache said:
Could you grab logs after FC ?
Click to expand...
Click to collapse
How? Logcat? System offers only to restart the settings app
It will updated continuely?
Gesendet von meinem Redmi Note 3 mit Tapatalk
@vache That's the source for the battery example. I'll read @erfanoabdi app and see what we can include.
https://github.com/MotorolaMobility...motorola/samples/mdkbattery/MainActivity.java
t0n0n said:
@vache That's the source for the battery example. I'll read @erfanoabdi app and see what we can include.
https://github.com/MotorolaMobility...motorola/samples/mdkbattery/MainActivity.java
Click to expand...
Click to collapse
In my app I'm using kernel driver greybus informations (not Motorola mods api)
Theres No options in kernel to set efficiency mode
I don't know we can use Motorola mods api to set it
Because Motorola mod manager app is using moto api to set efficiency
And it's not working!
erfanoabdi said:
In my app I'm using kernel driver greybus informations (not Motorola mods api)
Theres No options in kernel to set efficiency mode
I don't know we can use Motorola mods api to set it
Because Motorola mod manager app is using moto api to set efficiency
And it's not working!
Click to expand...
Click to collapse
Just figured it out. We could use the Motorola libs, but we don't have Incipio's mod id so we can't identify it. Unless we can hack it or extract the id from somewhere else.
New build up:
ROM: http://dwnld.aicp-rom.com/device/griffin/NIGHTLY/aicp_griffin_n-12.1-NIGHTLY-20170513.zip
Changelog: http://dwnld.aicp-rom.com/device/griffin/NIGHTLY/aicp_griffin_n-12.1-NIGHTLY-20170513.zip.html
i get safetyNet cts profile mismatch in Magisk
any tips?
Thanks
FC when trying to disable battery light. But notification light works.
fersy said:
i get safetyNet cts profile mismatch in Magisk
any tips?
Thanks
Click to expand...
Click to collapse
Tip for what?
Whats not working?
Got also the mismatch, but (for exmaple) Pokemon works fine
mstrack said:
Tip for what?
Whats not working?
Got also the mismatch, but (for exmaple) Pokemon works fine
Click to expand...
Click to collapse
Tips for passing SafetyNet... By flashing a new kernel for example... You can't see Netflix in Playstore when you get safetynet mismatch
fersy said:
Tips for passing SafetyNet... By flashing a new kernel for example... You can't see Netflix in Playstore when you get safetynet mismatch
Click to expand...
Click to collapse
Magisk and Suhide will help ya.
Works for me!
New Update
Direct Download: aicp_griffin_n-12.1-NIGHTLY-20170520.zip
Change Log: aicp_griffin_n-12.1-NIGHTLY-20170520.zip.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Very excited to announce my first unofficial build for NP1
Why Paranoid Android?
Paranoid Android is probably one of the best Custom ROM with the main focus on stability and performance all while keeping the UI simple to provide an OEM like experience. PA builds are based on the Code Linaro Organization Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors have always focused on squashing existing bugs, and implementing and improving features, performance, and stability. They dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
What's Different in these builds?
To be honest, nothing major as this is the very first time that I am trying out building custom roms. Here's something to start with.
Enabled NTCam (Already present in PA Source but disabled in Official builds)
Added Google Photos spoof for unlimited backup
Click to expand...
Click to collapse
Note: I am not a developer by any means who can contribute these immensely talented and very helping team of PA. I just want to learn more about building ROMs and hopefully add along some useful features that I see fit for my daily use.
If you like the amazing work by Paranoid Android Team, you can donate to them using the link below:
Donate
Download - Sourceforge
Instructions
Unlock your bootloader, and in bootloader mode follow the next command
fastboot update aospa-topaz-1-phone1-20230305-image-UNOFFICIAL.zip
After the reboot, factory reset the device (only required for the first time you flash Paranoid Android)
Click to expand...
Click to collapse
Device-specific issues
Some features of Nothing Camera may not work as expected
You tell us
Click to expand...
Click to collapse
Kernel Source
Credits:
Whole AOSPA Team - Link to official build
Cheers and #StayParanoid
Reserved
Reserved 2
Is there a way by which it can be enabled in the existing official build?
edit: Like it doesnt make sense to have a new build if that can be done. So ignroe my question
hemanth.k said:
Is there a way by which it can be enabled in the existing official build?
edit: Like it doesnt make sense to have a new build if that can be done. So ignroe my question
Click to expand...
Click to collapse
You'll have to root and use pixelify module with magisk. The devs of the PA team have clearly mentioned they'll never add the Google photos spoof in official builds.
MakDroid said:
You'll have to root and use pixelify module with magisk. The devs of the PA team have clearly mentioned they'll never add the Google photos spoof in official builds.
Click to expand...
Click to collapse
pixelify for enabling nothing camera?
And afaik i have seen people say in Beta 1, there was spoof enabled.
hemanth.k said:
pixelify for enabling nothing camera?
And afaik i have seen people say in Beta 1, there was spoof enabled.
Click to expand...
Click to collapse
Sorry for the misunderstanding on my part. I don't know why I thought of Google photos spoof. As for the Nothing Camera, it is there in the source but not in the builds. A reference to include it is already there in the sources but just commented out. I simply removed it from comments before building.
MakDroid said:
Sorry for the misunderstanding on my part. O don't know why I though of Google photos spoof. As for the Nothing Camera, it is there but not in the builds, but a reference to build it is already there in the sources but just commented out. I simply removed it from comments before building.
Click to expand...
Click to collapse
thanks for the clarification. on the side note, is it possible to enable the spoofing part while building so rooting isnt needed?
That's exactly the reason why my build exists. My build has the spoofing and Nothing Camera. No need to root.
hemanth.k said:
thanks for the clarification. on the side note, is it possible to enable the spoofing part while building so rooting isnt needed?
Click to expand...
Click to collapse
is there a problem with the microphone when making a phone call on the latest build?
i guess it's now best time to build your unofficial PA. As PA topaz 3 have fixed almost everything for nothing phone. the actual PA is missing unlimited storage and NTcam. They have fixed mic. Even now nothing phone integrated barcode scanner in NTcam so no other Google cam required.
MakDroid said:
Very excited to announce my first unofficial build for NP1
Why Paranoid Android?
Paranoid Android is probably one of the best Custom ROM with the main focus on stability and performance all while keeping the UI simple to provide an OEM like experience. PA builds are based on the Code Linaro Organization Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors have always focused on squashing existing bugs, and implementing and improving features, performance, and stability. They dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
What's Different in these builds?
To be honest, nothing major as this is the very first time that I am trying out building custom roms. Here's something to start with.
Note: I am not a developer by any means who can contribute these immensely talented and very helping team of PA. I just want to learn more about building ROMs and hopefully add along some useful features that I see fit for my daily use.
If you like the amazing work by Paranoid Android Team, you can donate to them using the link below:
Donate
Download - Sourceforge
Instructions
Device-specific issues
Kernel Source
Credits:
Whole AOSPA Team - Link to official build
Cheers and #StayParanoid
Click to expand...
Click to collapse
Any update?