Database Users

LiquidSmooth Test Build Xperia Z1 Compact

I have made a LiquidSmooth Test build for the Amami (Xperia Z1 Compact), I do not own this device, but it is based off of the soon to be merged Official CM tree. If all is well with the build I will make a thread in Orig Development
Rom Download
Gapps

deadman96385 said:
I have made a LiquidSmooth Test build for the Amami (Xperia Z1 Compact), I do not own this device, but it is based off of the soon to be merged Official CM tree. If all is well with the build I will make a thread in Orig Development
Click to expand...
Click to collapse
Hey there!
I think you should still make the thread in the OrigDev section, but with some tags like [Alpha]\[Beta]\[Test]\smthing. Because a lot of people (myself included), who like flashing, just ignore the General and Q&A sections, and go straight to Dev\OrigDev. You might get more testers this way
PS: Thx for the ROM, I'll try to test it later this week =)

Everething is ok

[WIP] [CM12] [DEVS ONLY] Cyanogenmod 12 for Moto G (2nd Gen)

Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:

N.K.V. said:
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
Click to expand...
Click to collapse
I love your initiative! Unfortunately I'm not a developer...
Send from my XT1068 using Tapatalk.

nice work mate.... developers are needed urgently....

Why do you think developers will find you and this thread? It works the other way. You need to find developers and ask for help. I suggest you start here and here
I keep my fingers crossed for the success of the project :highfive:

Yes, I am reading all possible guides given by the developers.
By that only i have reach this far.
But for device tree and kernel, device specific modifications are necessary, and I really need help of some one who has actually done this before.
If this is successful , we can have an alpha build of CM 12 , in 3-4 days.

@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...

k2wl said:
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
Click to expand...
Click to collapse
This is great news. A team effort can do anything.:good:

Thanks to NKV and Kewl. Great initiative. God Bless You.
Sent from my Nexus 7 using XDA Free mobile app

okay guys,
let's keep this thread clean for developers.
you can always hit like to appreciate
UPDATE: @k2wl is working on kernel and device tree, it will take him some days.

@k2wl and N.K.V.
Thx for your time and work :good:
I wait for the right Software on xt1068!

I have a little bit of knowledge and i can learn really fast, if you guys need help, you can count on me

which model will this be for? (please say xt1064)

Bobboman said:
which model will this be for? (please say xt1064)
Click to expand...
Click to collapse
Doesn't matter. It will be for all variants!

absolutely brilliant, i wish i knew a lick of programming so that i could help get this done faster (i'm tired of seeing a SU update in play store and not being able to use it because it sends my G into a bootloop)

Thanks man, lollipop official update have a bug while playing music via bluetooth when screen is lock, can you fix it on this rom?

Ha ha...Let's make the ROM first..
Bug fixing in Second task.
Now that lollipop soak has started in India....i think Work should go fast. :beer:

Waiting for it. Please keep updated though!

I'm interested in helping with this.
Sent from my A0001 using XDA Free mobile app

Hope to See this soon! Thanks guys!!

Nice intitiative...but i think making device tree and vendor for this device will not be tht easy....still hope for best

OxygenOS is now open source

OnePlus released the source code of OOS on github. Some nice news.
https://github.com/OnePlusOSS

Hmm, interesting news, thank for info :good:

This is badass!

Great news indeed.
Let's wait for an OPX device tree and vendor blobs

The github page has a 6.0.1 branch only.
Does this mean that this is a build for the oneplus 2 only?
Or does this also mean that devs can now build a 6.0.1 based oxygen os 3 rom for oneplus x as well using this before oneplus themselves do it??

Had a closer look... It just looks like it'll build AOSP... Not O2...

Ivtake the previous post back. This is awesome! We just need to get a device tree working and we can produce an unofficial port!

Now the path clears to custom oxygenOs:highfive:
Also it may mean timely access to sources, if we ever get mm

Unfortunately , I was right earlier... It is not open source O2

@crian RJDTWO is right. Confirmed by Helen yesterday. Can you change the title, please.

[DEV] CyanogenMod 14.1 - Degaswifi - [Needing Help]

A CyanogenMod DEV, is going to help me build a working CyanogenMod 14.1 build for this device. But I need someone to help me make the GitHub Project possible.
The CyanogenMod DEV. is only wanting to make 1 (one) build. So if you guys want more versions, you guys have to build it, with these code sources on GitHub.
Link To The GitHub Project:
"https://github.com/Darkestwolf98/Degaswifi-CM-14.1"
I am needing some people to build some versions for CyanogenMod 14.1 for Degaswifi, and to test these versions.

This is 230NU version right? Ill test for you, have been using cm for a long time be glad to get a new build finally on this thing.

dougyj said:
This is 230NU version right? Ill test for you, have been using cm for a long time be glad to get a new build finally on this thing.
Click to expand...
Click to collapse
Yes

I want to help, but how to build?

NATRIUM - PROJECT - "A ROM for every week day"

Hi guys,
Now that I am back into the building trend, I would like to start a project called "A new ROM for every week day".
As the title says it, that would be a project that would unite 7 existing ROMs (I'm a simple builder, not a developer) that will get a weekly update each fixed week day.
Of course, in time, I'll give everything needed for each ROM : link, ROM source, device tree source and local_manifest in case someone wants to build for himself
So I need 7 ROMs to build and I would like you to participate telling me what ROM you'd love to get for Natrium.
So far, the ROMs are :
- Validus
- Unleash
- AquariOS
- Dirty Unicorns
AOSP Extended and Resurrection Remix have been supported, but it seems that development and support for those have been dropped. I think Hlcpereira that some bad people stole Hlcpereira's mi5s Plus
So I will also try to keep those alive...
- AOSP Extended for Natrium aka mi5s Plus
So I was thinking about "Cardinal" (which would be ROM #5) and Carbon (which would be ROM #6).
But please, feel free to tell me if this project is of some interest and what ROM you'd like...
Thanks a lot

For ROM #1
Hi guys,
So after all, I'll start with Candy ROM just because this is the ROM with which I started the custom ROM building thing, back when it was KitKat
It's of course provided "as is" as it has only gone through very basic testing : boot, SIM card, Wi-Fi, Bluetooth, camera and those kind of stuff
So if you find a bug, please report gently
Link to ROM : Candy for Natrium
Of course the usual stuff in case you want to try to build and update it yourself :
- the ROM source : CandyROMs
- the local manifest : Manifest for natrium
I guess that's all you need... with a really small knowledge (if I can do it anyone can...) and a decently fast computer (mine is somewhat above decent, but that only helps with build speed).
Enjoy and please report gently in case of bugs

For ROM #2
Hi guys,
For this second ROM I've decided to go for AICP (Android Ice Cold Project).
It's full of features and really nice. But as usual : I have been able to test it more in depth.
It boots, has SIM cards, Wi-Fi, Bluetooth and camera working, which is basically the most important.
Could not check on battery life or other stuff...
Link to ROM : AICP for natrium
Of course, shoud you wish to build and update this yourself, here are the links to what you'll need :
- ROM source : AICP GitHub
- Other stuff for Natrium : local manifest
Enjoy and report bugs peacefully... I'm not doing this for myself but to keep this device alive

For ROM #3
Which will probably be Dirty Unicorns... Hope I'll get to build it.

For ROM #4
RESURRECTION REMIX
I know it's already posted somewhere else, but I think there's no new build since a long time.
You can find sources here : ResurrectionRemix
Device tree, Kernel and Vendor are here : HLC Pereira
Finally, ROM can be downloaded from here :Resurrection Remix for Natrium.
Of course, you'll probably need to install some GApps. You can find some here : http://opengapps.org/
I installed this ROM on my spare Natrium. It boots, SIM cards are working, Wi-Fi is working, looks like Bluetooth is working, camera is working for both pictures and videos.
Enjoy and report in a gentle manner if you find some bugs (and with a logcat... If there's none, it'll be difficult to try to fix).

For ROM #5
CARDINAL AOSP
Sources are here : Cardinal AOSP Github
Kernel is here : Lineage Xiaomi kernel
Vendor files are here : Xiaomi vendor
Device tree ready to build is here : Natrium Specific / msm8996 common
Finally ROM can be downloded from here : Google Drive for Natrium Cardinal
Of course, you'll need Open GApps that you can find here : Open GApps
As far as I could see :
- ROM boots ;
- SIM cards are working ;
- Wi-Fi is working ;
- Bluetooth is working ;
- Camera is working...
Now there are probably a lot of minor (or maybe less minor) bugs.
Just tell me and I'll see if I can fix those
Regards.

For ROM #6
Maybe Carbon ROM ?

For ROM #7
AS REQUESTED : AICP
Sources are here : AICP
Kernel is here : Lineage Xiaomi kernel
Vendor files are here : Xiaomi vendor
Device tree ready to build is here : Natrium Specific / msm8996 common
Finally ROM can be downloded from here : Google Drive for Natrium AICP
Of course, you'll need Open GApps that you can find here : Open GApps
As far as I could see :
- ROM boots ;
- SIM cards are working ;
- Wi-Fi is working ;
- Bluetooth is working ;
- Camera is working...
Now there are probably a lot of minor (or maybe less minor) bugs.
Just tell me and I'll see if I can fix those
Regards.

As i know RR isnt Official yet, also Unleash seems good idea.

Hi,
I know RR isn't official, but I do not want to interfere with the guy doing it already.
But of course I can add it should you wish me too... Depends on how often that guy is updating it.
Unleash : I thought I could build it, but I am facing an issue in the build final
When i say final, I mean it : it's in building the last 2 files out of almost 100k files !!!
Error is "Cannont find ro.unleash.version in build.prop".
Have to find out how to fix that... if it is an easy thing to do
Regards.

How about stick with building only one ROM and keep it updated once a week for a whole year? We already have too many ROMs and most of them have been dropped.

Do you have the opportunity to port sailfish os?

Cosmic rom port Please

I'd love to get AICP again! It was the only rom without touch lag

NexusPenguin said:
Hi,
I know RR isn't official, but I do not want to interfere with the guy doing it already.
But of course I can add it should you wish me too... Depends on how often that guy is updating it.
Unleash : I thought I could build it, but I am facing an issue in the build final
When i say final, I mean it : it's in building the last 2 files out of almost 100k files !!!
Error is "Cannont find ro.unleash.version in build.prop".
Have to find out how to fix that... if it is an easy thing to do
Regards.
Click to expand...
Click to collapse
Hey, As I know, You need to add ro.unleash.version at vendor.prop on msm8996-common side. Can u try?
Like ro.unleash.version=blahblah

jeonggeek said:
Hey, As I know, You need to add ro.unleash.version at vendor.prop on msm8996-common side. Can u try?
Like ro.unleash.version=blahblah
Click to expand...
Click to collapse
Hi,
Will try it, though I guess it will be a little more complicated than that.
But of course, it's worth a try
I'll report a little later.
Regards.

try everything a bit or it would be wrong and better than how we are that it is without anything you dale penguin DU Validus ...

Dirty Unicorns and AquariOS would be a dream for me, and I would donate to you if you keep those thing official :>

Every development project is Welcome, but 7 ROMs for a guy don't you think is kinda exagerated?

Thanks your effort very much in advanced.
I want a RR which will update weekly, so bugs won't remain for a long time.
And NOS is my dream too.:fingers-crossed::fingers-crossed: