Database Users

Contacting CM to update sources to KK

Hello friends.
As all of us see, LG released their KitKat sources long time ago. Our great developers like @dr87 @Savoca @houstonn and others made it with Their hard work to merge them so we have two stable / nearly stable roms: Mahdi and PA. But what with other roms? Most of the roms are based on CM, so they still have bugs.. During months, CM doesn't seem to have done ANYTHING.
So my question is, how about to send a message (or spam, in any way u name it) by all of us to CM, to the maintainer? We have official support, but in fact it's "support without support" in my opinion. Maybe after these messages they would finally start to do something, because it's like they forgot about G2...
Regards.
EDIT: so we have a way to contact => https://jira.cyanogenmod.org/secure/Dashboard.jspa
now we should make a well, polite message so everyone would copy it and drop there.
Another way it would be to ask the maintainer directly https://plus.google.com/+RicardoCerqueira
EDIT2: I gave a comment to Ricardo on Google+ here https://plus.google.com/+RicardoCerqueira/posts/4dc8kVBYuTq feel free to do it as well

The best bet would be to create an improvement note at their so called "Bug Tracker" considering that they are doing this for free, this would be the most polite form.

I support this initiative, but today be entirely honest M6 for me is almost bug free, fast and battery efficient.
Up to date sources is great, but if a rom is working well, I don't care if the sources are old!
Inviato dal mio LG-D802 utilizzando Tapatalk

Airidas said:
The best bet would be to create an improvement note at their so called "Bug Tracker" considering that they are doing this for free, this would be the most polite form.
Click to expand...
Click to collapse
could u give a link please? so we could prepare a message and then everyone would leave it there
vittogn said:
I support this initiative, but today be entirely honest M6 for me is almost bug free, fast and battery efficient.
Up to date sources is great, but if a rom is working well, I don't care if the sources are old!
Click to expand...
Click to collapse
I personally had CM for some time, and it never was so stable as Mahdi R1 which i have now. Besides that, a lot of roms like Carbon or Slim can't be simply updated from CM sources, so they still have bugs.

reas0n said:
could u give a link please? so we could prepare a message and then everyone would leave it there
I personally had CM for some time, and it never was so stable as Mahdi R1 which i have now. Besides that, a lot of roms like Carbon or Slim can't be simply updated from CM sources, so they still have bugs.
Click to expand...
Click to collapse
Here: jira.cyanogenmod.org

Thanks, so anyone is, i would say, good in kind speaking to prepare a message?
Oh and we could also use Google+ and ask the maintainer directly https://plus.google.com/+RicardoCerqueira

Replyed 2 times to posts in his google + account with message " When LG G2 is going to have updated KK sources? A lot of people are waiting for bug-free CM and CM-based 4.4 ROMs ". I hope that all you guys do the same.Cheers
Sent from my LG-D802 using XDA Premium 4 mobile app

Just to clarify, roms that are based on CM do not need CM to upgrade to 4.4.2 sources. The upgrade is done in the device tree / vendor files and kernel. The rom source does not need any changes and each rom maintainer for the G2 has the power to upgrade their rom to 4.4.2 G2 sources without CM doing anything, they just need to figure out the specific device tree bugs for each rom and fix them.
I am under the impression you think CM needs to upgrade in order for CM based roms to upgrade, feel free to correct me if I'm wrong :good:

dr87 said:
Just to clarify, roms that are based on CM do not need CM to upgrade to 4.4.2 sources. The upgrade is done in the device tree / vendor files and kernel. The rom source does not need any changes and each rom maintainer for the G2 has the power to upgrade their rom to 4.4.2 G2 sources without CM doing anything, they just need to figure out the specific device tree bugs for each rom and fix them.
I am under the impression you think CM needs to upgrade in order for CM based roms to upgrade, feel free to correct me if I'm wrong :good:
Click to expand...
Click to collapse
apparently theres a bit of confusion, there was some one nightly where the rotation wasnt working with the jb baseband, (im gussing on that nightly he used the kk source ) because flashing the kk baseband on that build fixed the rotation issue, but im not quiet aware of what the situation is ince im back on stock. anyways ill be swinging it on the latest nightly just to clarify my doubts. and im pretty sure they just want the maintainer to switch to kk source , btw nice to see you here hope your cooking something great for us

dr87 said:
Just to clarify, roms that are based on CM do not need CM to upgrade to 4.4.2 sources. The upgrade is done in the device tree / vendor files and kernel. The rom source does not need any changes and each rom maintainer for the G2 has the power to upgrade their rom to 4.4.2 G2 sources without CM doing anything, they just need to figure out the specific device tree bugs for each rom and fix them.
I am under the impression you think CM needs to upgrade in order for CM based roms to upgrade, feel free to correct me if I'm wrong :good:
Click to expand...
Click to collapse
Well, in the past I had some Android phones, and CyanogenMod was always first with upgrading everything, and then other developers were basing their ROMs on these updates. I mean, they updated everything, end other ROMs were updated fast. They're not giving support which they were giving in the past, that's all.

reas0n said:
Well, in the past I had some Android phones, and CyanogenMod was always first with upgrading everything, and then other developers were basing their ROMs on these updates. I mean, they updated everything, end other ROMs were updated fast. They're not giving support which they were giving in the past, that's all.
Click to expand...
Click to collapse
Did you get a response from Ricardo?

LenAsh said:
Did you get a response from Ricardo?
Click to expand...
Click to collapse
Nope, i saw i got some 1+ on my comment, i shared second comment today. nothing..

reas0n said:
Nope, i saw i got some 1+ on my comment, i shared second comment today. nothing..
Click to expand...
Click to collapse
Oh

CM13 source out

Anyone want to try building? Should be easier to get CM working with 3.4 kernel than AOSP with 3.10.
https://github.com/Cyanogenmod/android/tree/cm-13.0

Sadly, I do not know how to build android from source, but I would LOVE to see CM13 built for our device too...

Does anyone think that there ever will be a CM13 version for the Z1C?
Im still on 12.1, its very cool, but CM13 would be nice anyway...

Reapy1804 said:
Does anyone think that there ever will be a CM13 version for the Z1C?
Im still on 12.1, its very cool, but CM13 would be nice anyway...
Click to expand...
Click to collapse
I don't see why not. There's already been at least 4 MM ROMs released for it. If CM13 source is available, I'm sure we'll see it before long.

I'm also quite sure it'll come eventually. I was being curious myself and built it from the CM sources just now. It builds fine, but I got stuck in a reboot loop after the whole app optimization step. Since it uses the new 3.10 kernel, it's no surprise that it's taking a bit longer as compared to other devices though

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.

CyanogenMod 14 for Desire 816 Dual Sim

When is cm 14 (unofficial) coming to this phone?

Please build a version that is suitable for D816w too...not only MTK!!!!

@bigsupersquid already started building., which is a good news..
bigsupersquid said:
Yeah, I'm working on it.
bigsuperprojects on GitHub for cm14 branches
I've only had two builds complete without crashing the build system, it's really wanky right now.
I'm not uploading any builds for now. All I've got is one semi functional build without cell service capability, and one that constantly crashes com.android.phone from setting the radio properties in init.
Click to expand...
Click to collapse

Yeah, I'm building, there's another interested in doing so too.
Still, not much luck yet, and I haven't patched the dwg init to build yet. I'll do that when I have something functional enough to release a zip.

give it another 4 month or so

[Q] when we get android 8 for our nexus 4?

hi friends,
do you know, our nexus 4s get android Oreo by nitrogen or lineage or other roms? if yes, I know stable android Oreo version will release mid august, when we get custom rom?

we can't know this

When it comes fyi: asking for an ETA is kinda rude on xda
wait till October or November probably for a decently stable ROM

Excitedly expect first android Oreo Rom for nexus 4 on september 17

and first 32bit snapdragon android oreo port, fully work
https://forum.xda-developers.com/showpost.php?p=73494285&postcount=1356
so, now we have very big chance for our nexus 4...

and first nexus 5 android oreo port, booting and wifi working now, one similiar devices too
https://forum.xda-developers.com/showpost.php?p=73538437&postcount=6286

for now has boot problem but after all the first nexus 4 oreo
https://forum.xda-developers.com/showpost.php?p=73594437&postcount=231

I have compiled android 8 and I managed to get it booting(lots of changes on kernel and device tree). Need a lot of work but mako probably will get a fully fuctional android 8 rom.

good news
thanks for good news,
and maybe co-operation accelerates this work
equlog said:
I have compiled android 8 and I managed to get it booting(lots of changes on kernel and device tree). Need a lot of work but mako probably will get a fully fuctional android 8 rom.
Click to expand...
Click to collapse

If anyone wants to try Oreo in our lovely mako.
Original thread: Android 8.0 Mako
Download: here

equlog said:
If anyone wants to try Oreo in our lovely mako.
Original thread: Android 8.0 Mako
Download: here
Click to expand...
Click to collapse
Nice! At work and don't have my N4 to try it, but interested to hear how it is running, so I can try out when I get home. Is it mostly functional?

Can you share the device and kernel tree?

equlog said:
I have compiled android 8 and I managed to get it booting(lots of changes on kernel and device tree). Need a lot of work but mako probably will get a fully fuctional android 8 rom.
Click to expand...
Click to collapse
Just for my own curiosity, how do you know what changes need to be made to the device and kernel tree? Do you use officially supported device/kernel trees as a reference, or is there a guideline posted somewhere?

ariesgodofwar said:
Nice! At work and don't have my N4 to try it, but interested to hear how it is running, so I can try out when I get home. Is it mostly functional?
Click to expand...
Click to collapse
Really I haven't tested too much, busy at work... also my n4 have the touch screen broken and doesn't works very good lol.. but almost nothing works.
Its just to try out.
Renandelfanti said:
Can you share the device and kernel tree?
Click to expand...
Click to collapse
Sure, i'll upload to github later.
TheSt33v said:
Just for my own curiosity, how do you know what changes need to be made to the device and kernel tree? Do you use officially supported device/kernel trees as a reference, or is there a guideline posted somewhere?
Click to expand...
Click to collapse
The kernel is the used one in 7.1.2 and I added the Binder changes... the device tree is fixed by trying to booting and fixing the errors showed in last_kmsg .

equlog said:
Really I haven't tested too much, busy at work... also my n4 have the touch screen broken and doesn't works very good lol.. but almost nothing works.
Its just to try out.
Sure, i'll upload to github later.
The kernel is the used one in 7.1.2 and I added the Binder changes... the device tree is fixed by trying to booting and fixing the errors showed in last_kmsg .
Click to expand...
Click to collapse
Yes, I also flashed this and it boots. As you said, nothing works... But it is not less that it boots :laugh:
I've been trying since the source of O is released and could not boot it. Your work gives all mako users hope to see a working O build :good: Thanks for the work!
Nitin

I as well got a semi-working O build, but was a bit short on time to work on it. Could we collaborate somewhere? Perhaps a hangouts group?

I've flashed from mako 7.12, kind of like upgrade from 7.12

Sources up.
I used the vendor blobs from TheMuppets.
https://github.com/MakOreo
---------- Post added at 01:42 AM ---------- Previous post was at 01:24 AM ----------
Ziyan said:
I as well got a semi-working O build, but was a bit short on time to work on it. Could we collaborate somewhere? Perhaps a hangouts group?
Click to expand...
Click to collapse
:good:
I dont have too much free time, but I always follow the status of my devices. I Hope to see a fully working O rom asap.

Ziyan said:
I as well got a semi-working O build, but was a bit short on time to work on it. Could we collaborate somewhere? Perhaps a hangouts group?
Click to expand...
Click to collapse
That's a good idea... What do you say @equlog?
Thanks a lot for sharing the sources :good:
Nitin

as good as we hoped