Database Users

CM 7 nightlies ,UPDATED weekly

I know this is a development forum,but I wanted to raise attention for the new build of CM 7 with continuous update,I like the CM 9.10 work here but I think they need more work to be ready for daily use.
so I strongly recommend the new CM 7
download:
http://get.cm/?device=legend

Any important changelog? The last 7.2 stable is quite stable

http://changelog.bbqdroid.org/#legend/cm7/next
but it is till 15/11

I am using the nightlies for some time now, from http://download.cyanogenmod.org/?type=nightly&device=legend. However, I was wondering what the changes in the last nightly are, filesize is different from previous,but changelog says No changes.
Anybody knows?

wim69 said:
I am using the nightlies for some time now, from http://download.cyanogenmod.org/?type=nightly&device=legend. However, I was wondering what the changes in the last nightly are, filesize is different from previous,but changelog says No changes.
Anybody knows?
Click to expand...
Click to collapse
This site shows more info:
http://review.cyanogenmod.org/#/q/status:merged+branch:gingerbread,n,z

Last nightly from March 1st, it's no longer building them?

There's really no more point in CM7 nightlies if no more features are going to be announced and added to CM7 legacy devices. Unfortunately, users of these devices are content with CM7 as they are or else they'd buy a more powerful device, given how it's >3 years old.
I guess the nightlies until March were meant as flexibility to those unable to run the CM7 stable series.
As much as I'd hate to say it, if you want more out of Android and custom ROMs, I guess you're going to have to upgrade.

CM 12: in GitHub Account of CyanogenMod

Dear friends the account of CyanogenMod show an early source of the CM12,
hope that some one build a CM12 for us, till i get new laptop to do that.
https://github.com/CyanogenMod/android_system_core/tree/cm-12.0
https://github.com/CyanogenMod/android_vendor_cm/tree/cm-12.0

sycolon said:
Dear friends the account of CyanogenMod show an early source of the CM12,
hope that some one build a CM12 for us, till i get new laptop to do that.
https://github.com/CyanogenMod/android_system_core/tree/cm-12.0
https://github.com/CyanogenMod/android_vendor_cm/tree/cm-12.0
Click to expand...
Click to collapse
trying to build now..fetching repos at the moment. I dont think this will work out but we'll see
Edit: didnt work out. what a surprise

@hutilicious sadly that it didn't work!

sycolon said:
@hutilicious sadly that it didn't work!
Click to expand...
Click to collapse
cyanogenmod hasnt any working device specific configuration and code for yuga in cm12 at the moment.
i tried using pabx yuga.xml and TheMuppets blobs, but got errors with conflicting repos I couldnt resolve, may be due to that I have only basic knowledge about all of that.
I guess as for now, we have to wait until CM starts building nightlies (a leaked document says dez. first) or use pabx/thomas AOSP port for yuga, which can be used as a daily driver already.

@hutilicious i'm already using @pabx ASOP port

you seems to be crazy over lollipop anyway for CM12 as far as I know the popping sound will be finally be fixed it was due to qcom introducing of deep buffer, anyway as far as I know that's all but you can expect nightly before 2015

CyanogenMod

Do you guys think cyanogen will eventually add this phone to its official supported devices?
Coming from a Nexus 5 with endless rom development It'd be a shame if this phone didn't see as much. Especially since it has such potential

No I don't think that oneplus two will get official cyanogen support, as oneplus dropped cyanogen and started using there own OxygenOs. In fact, I think that even future devices from oneplus will also never get official cyanogen.
So, unfortunately we will need to stay at unofficial builds only.
Hit thanks If I helped!!!

kishan12345 said:
No I don't think that oneplus two will get official cyanogen support, as oneplus dropped cyanogen and started using there own OxygenOs. In fact, I think that even future devices from oneplus will also never get official cyanogen.
So, unfortunately we will need to stay at unofficial builds only.
Hit thanks If I helped!!!
Click to expand...
Click to collapse
yes cm13 will be officially available soon!And you are wrong ! one plus had a bad breakup with cyanogen but theirs a diiference between how people work on cynogenos and cyanogenmod !It depends on the devolepers of each community on how they work on devolepment on a particular device but one plus two devolepment is insane so cm13 is on the way and if u are still concerned look at the devs of HTC 826 they made thier device get official support and dont worry as far as i know the devolpement for this device will be booming shortly !And theirs already a thread on CM 13 !

Hope that your words come true. But still I don't think so that cm13 will be available OFFICIALLY.
Sent from my ONE A2003 using Tapatalk

kishan12345 said:
Hope that your words come true. But still I don't think so that cm13 will be available OFFICIALLY.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
lol bro if they get unofficial builds perhaps in a week ..then tell ME why wont they make it official after a month !what one plus one had is the cyanogen os and not cyanogenmod !To make a device official in cyanogenmod u have to have good devolpment for a particular device and the works for cm13 is already started for op2 !Check out cm12.1 thread garak is working on cm13 and threres another thread called cm13

As i understand, in order to get an official support from cyanogen to our device there must be unofficial CM build, witch can be sent to CM team for a review. If it passes, has most things working, then they add it to their device tree and officially supports it. In other words, anyone there can take CM vendor and framework codebase and then go and start adding the code necessary to make CM work properly on OPT device. When developer gets far enough along, he can then submit that code back to CM for inclusion into CM's github. If that code passes the checks that the CM team has, then the CM team will merge that code into its own device tree and add official support for that device.
Also there are chance of CM team taking this step by their selves .. but there is probably no hope for that. So the only hope is Grarak
This information is found in the official CM forum so i doubt it is false.

LineageOS 15

Any idea when we might get lineage os 15 for Moto G4 Play[harpia]?

Unofficial builds of LineageOS 15 for the G4 play:
http://www.lineageosroms.org/forums/topic/lineage-os-15-moto-g4-play-android-oreo-8-0-rom/
I need my phone during the next weeks, therefore I can not take the risk to test this build.

hero66 said:
Unofficial builds of LineageOS 15 for the G4 play:
http://www.lineageosroms.org/forums/topic/lineage-os-15-moto-g4-play-android-oreo-8-0-rom/
I need my phone during the next weeks, therefore I can not take the risk to test this build.
Click to expand...
Click to collapse
As far as I know it boots - but camera and RIL aren't working. This was the 0709 build however, I'm not sure about the latest build. It's certainly a start though!

What is RIL?

jcolongo said:
As far as I know it boots - but camera and RIL aren't working. This was the 0709 build however, I'm not sure about the latest build. It's certainly a start though!
Click to expand...
Click to collapse
This ROM doesn't boot for me. Can you pls try it once.....Thank You

pusansen99 said:
This ROM doesn't boot for me. Can you pls try it once.....Thank You
Click to expand...
Click to collapse
Sorry, I meant the 0905 build, not 0907. RIL = Radio Interface Layer, pretty much mobile networking.

pusansen99 said:
What is RIL?
Click to expand...
Click to collapse
Radio interface layer. The software layer that interfaces with the device drivers and hardware that connects to the mobile phone network. Basically the stuff that makes your smart phone a phone.

Apart from lineage os is there any other Oreo ROM for harpia?

I found some more ROMs on AFH that I think are based on 8.0 but I don't have time to test them now.
https://www.androidfilehost.com/?fid=889764386195931059
https://www.androidfilehost.com/?fid=745425885120763329
Gapps:
https://www.androidfilehost.com/?fid=961840155545597004
EDIT: AOSCP (the 2nd one) doesn't seem to have RIL working, but AOSPExtended (the 1st one) does, but the camera doesn't work unfortunately.

bsevcenk said:
I found some more ROMs on AFH that I think are based on 8.0 but I don't have time to test them now.
https://www.androidfilehost.com/?fid=889764386195931059
https://www.androidfilehost.com/?fid=745425885120763329
Gapps:
https://www.androidfilehost.com/?fid=961840155545597004
EDIT: AOSCP (the 2nd one) doesn't seem to have RIL working, but AOSPExtended (the 1st one) does. I'm installing Google Apps right now so I can test everything else.
Click to expand...
Click to collapse
Thanks for this, been looking for an Oreo build that has RIL only thing that isn't working for me is the camera so if that breaks the experience for anyone I wouldn't recommend flashing this AEX build

Any updates guys?

A new build is up
https://www.androidfilehost.com/?fid=745425885120765286

pusansen99 said:
A new build is up
https://www.androidfilehost.com/?fid=745425885120765286
Click to expand...
Click to collapse
I'll try it out and let you know what works when I get the time.

bsevcenk said:
I'll try it out and let you know what works when I get the time.
Click to expand...
Click to collapse
I tried it... it's very buggy
Can't be used now

pusansen99 said:
I tried it... it's very buggy
Can't be used now
Click to expand...
Click to collapse
Yeah, RIL works but the camera doesn't and there are lots of graphical glitches.

bsevcenk said:
Yeah, RIL works but the camera doesn't and there are lots of graphical glitches.
Click to expand...
Click to collapse
Yeah certain portions of the screen keeps flashing...:silly:

still better than not booting

Any updates on the Official Lineage OS 15?

pusansen99 said:
Any updates on the Official Lineage OS 15?
Click to expand...
Click to collapse
Please don't cross post the same question in multiple threads: https://forum.xda-developers.com/g4-play/help/custom-rom-8-0-moto-g4-play-t3681229/post74178549

Lineage os 16 build

Im thinking of making an unofficial lineage os 16 build for shamu will you be interested??

Wajdi Muhtadi said:
Im thinking of making an unofficial lineage os 16 build for shamu will you be interested??
Click to expand...
Click to collapse
yes it will be amazing to try it before the official release please make it and ican test it with you

I'm sure many users would be happy to test it if you did get build out.

Wajdi Muhtadi said:
Im thinking of making an unofficial lineage os 16 build for shamu will you be interested??
Click to expand...
Click to collapse
Please don't do it!
There is a reason why I haven't published any build yet.

deleted because maintainer asked to

Wajdi Muhtadi said:
guys this is only for testing purposes
https://www.androidfilehost.com/?fid=11410963190603895206
Click to expand...
Click to collapse
Nice, beeing asked by the maintainer not to do unofficial builds and post them nevertheless.
Perhaps you are going to be the new LineageOS maintainer for shamu if I drop support.

Elektroschmock said:
Nice, beeing asked by the maintainer not to do unofficial builds and post them nevertheless.
Perhaps you are going to be the new LineageOS maintainer for shamu if I drop support.
Click to expand...
Click to collapse
im sorry didnt know you are the aminyainer ill delete it now

deleted because maintainer asked to

Wajdi Muhtadi said:
deleted because maintainer asked to
Click to expand...
Click to collapse
Thanks!
I didn't want to sound rude, but it's not ready yet. Yes it works, but some things like offmode-charging are still broken with selinux enforcing.
And I really don't need unexperienced users who can't help themselfs or grab a proper log right now.
Official LineageOS builds will start soon, and shamu might be in the first batch of devices if I find some time to fix the remaining bug.

Elektroschmock said:
Thanks!
I didn't want to sound rude, but it's not ready yet. Yes it works, but some things like offmode-charging are still broken with selinux enforcing.
And I really don't need unexperienced users who can't help themselfs or grab a proper log right now.
Official LineageOS builds will start soon, and shamu might be in the first batch of devices if I find some time to fix the remaining bug.
Click to expand...
Click to collapse
I PM'd you a little while ago, but any progress with VoLTE? If not will this not be looked into? And I'd be happy to contribute, to help solve this. Thanks for everything and the continued support Kim.

wavedashdoc said:
I PM'd you a little while ago, but any progress with VoLTE? If not will this not be looked into? And I'd be happy to contribute, to help solve this. Thanks for everything and the continued support Kim.
Click to expand...
Click to collapse
To be honest I haven't spent any time trying to fix VoLTE for following reasons:
- I don't use VoLTE
- Volte isn't popular in my area
- I have no SIM in my shamus
- I have no way to test VoLTE
- I don't use my shamus anymore
- I'm busy with Pie bringup
So alltogether the changes you'll get a fix for it from me is close to zero.
But if someone comes up with a fix for it I'll happily apply it.

Elektroschmock said:
To be honest I haven't spent any time trying to fix VoLTE for following reasons:
- I don't use VoLTE
- Volte isn't popular in my area
- I have no SIM in my shamus
- I have no way to test VoLTE
- I don't use my shamus anymore
- I'm busy with Pie bringup
So alltogether the changes you'll get a fix for it from me is close to zero.
But if someone comes up with a fix for it I'll happily apply it.
Click to expand...
Click to collapse
Thanks for the response, yeah that's the vibe I've been getting about VoLTE. The angler users are also having the same issues. I'm going to dive into it more this weekend. See what I find now after a couple of months have passed.
Looking forward to 16.0 ?

wavedashdoc said:
Thanks for the response, yeah that's the vibe I've been getting about VoLTE. The angler users are also having the same issues. I'm going to dive into it more this weekend. See what I find now after a couple of months have passed.
Looking forward to 16.0 ?
Click to expand...
Click to collapse
FWIW this is what another Shamu LOS Developer, npjohnson1, had to say.
Shamu is already fully brought up to Lineage 16.0 (minus IMS functions like VoLTE/VoWiFi, which likely won't ever be fix-able).
Click to expand...
Click to collapse
https://old.reddit.com/r/LineageOS/...rting_shamu_to_80_or_later/ecg7bj8/?context=3
So wishing you the best of luck in a search for solution.

wavedashdoc said:
I PM'd you a little while ago, but any progress with VoLTE? If not will this not be looked into? And I'd be happy to contribute, to help solve this. Thanks for everything and the continued support Kim.
Click to expand...
Click to collapse
That's the open source spirit. The other devs seem to fallback to kanging me, making me the top contributor in any device_shamu repository.

Elektroschmock said:
That's the open source spirit. The other devs seem to fallback to kanging me, making me the top contributor in any device_shamu repository.
Click to expand...
Click to collapse
The problem is the error log for the VoLTE bug is difficult to read. I've posted it multiple times in search of someone who knows more. I tried fixing all paths in the IMS.apk and I also tried back porting the old IMS implementation from Oreo as well. But the ROM failed to build.
Here's the log once more:
10-24 23:04:04.303: D/RadioInfo(2183): setImsVolteProvisioned state: on
10-24 23:04:04.306: E/RadioInfo(2183): setImsConfigProvisioned() exception:
10-24 23:04:04.306: E/RadioInfo(2183): com.android.ims.ImsException: getConfigInterface()(131)
10-24 23:04:04.306: E/RadioInfo(2183): at com.android.ims.ImsManager.getConfigInterface(ImsManager.java:1809)
10-24 23:04:04.306: E/RadioInfo(2183): at com.android.settings.RadioInfo$15.run(RadioInfo.java:1292)
10-24 23:04:04.306: E/RadioInfo(2183): at android.app.QueuedWork.processPendingWork(QueuedWork.java:258)
10-24 23:04:04.306: E/RadioInfo(2183): at android.app.QueuedWork.access$000(QueuedWork.java:49)
10-24 23:04:04.306: E/RadioInfo(2183): at android.app.QueuedWork$QueuedWorkHandler.handleMessage(QueuedWork.java:278)
10-24 23:04:04.306: E/RadioInfo(2183): at android.os.Handler.dispatchMessage(Handler.java:106)
10-24 23:04:04.306: E/RadioInfo(2183): at android.os.Looper.loop(Looper.java:193)
10-24 23:04:04.306: E/RadioInfo(2183): at android.os.HandlerThread.run(HandlerThread.java:65)
Maybe a Google Dev could chime in as they were working on a test Pie build for Shamu a while back.

Hey Elektroschmock,
Will the pie version of lineageos for the Nexus 6 have additional features to the camera like the Pixel? ie. the ability to take lowlight pictures.
Thanks for your work? Looking forward to the release.

blackshoes said:
Hey Elektroschmock,
Will the pie version of lineageos for the Nexus 6 have additional features to the camera like the Pixel? ie. the ability to take lowlight pictures.
Thanks for your work? Looking forward to the release.
Click to expand...
Click to collapse
Those features are in the updated Google camera app from the Pixels. And no the Nexus 6 won't have them since it's a 32bit processor. The updated GCam has been ported to other devices with 64bit processor though like the OnePlus 6.

can someone tell me why other roms like Carbon rom with PIE are running on the nexus 6 and LineageOS not? Are the roms so different? (Off screen charging bug/voLTE bug)

Darius thebrain said:
can someone tell me why other roms like Carbon rom with PIE are running on the nexus 6 and LineageOS not? Are the roms so different? (Off screen charging bug/voLTE bug)
Click to expand...
Click to collapse
If you look at the other ROM's sources you'll see that most of the commits are taken from me (LineageOS).
Other ROMs can decide when they feel it's ready to release something. We have higher standards in stability and security.
We won't ship something half assed with deactivated selinux or selinux policies which grant nearly everything.

Elektroschmock said:
If you look at the other ROM's sources you'll see that most of the commits are taken from me (LineageOS).
Other ROMs can decide when they feel it's ready to release something. We have higher standards in stability and security.
We won't ship something half assed with deactivated selinux or selinux policies which grant nearly everything.
Click to expand...
Click to collapse
Best of luck man. This is a very tough nut to crack. I quit building this for the same reason. I cant get anything but a mostly working somewhat buggy build with piss poor battery life. Thats nothing Im putting the Velocity name on. I actually rolled all the way back to my Nougat build.