Related
I know this is yesterday's news but I felt compelled to post this and get other users input on this topic.
http://www.cyanogenmod.org/blog/releases-11-12-final
What I don't understand is Cyanogen's priorities when it comes to which devices get 11, 12 or 12.1. I completely understand about phasing out CM11/KitKat as that is now a rather "old" version of android. However what I don't understand is why a device as new/old as ours (Aug 2013 is not THAT old) is stuck on CM12 (and now a final Snapshot build as of 6/25)? I mean, the Galaxy S3 is even getting 12.1 builds. I'm wondering if its because that was a far more popular device than the G2 was?
Just wanted to put this out there and see what other people think and find out what they're running currently on their G2 variant. I own the US T-Mobile D801 variant and do NOT want to run stock (LG) Lollipop since my device tends to run extremely HOT on it. I know not everyone was complaining about their G2 overheating on stock LP but I notice a considerable difference running CM12.
So, how do you guys feel about this? Do you even care or what?
t3chn0s1s said:
I know this is yesterday's news but I felt compelled to post this and get other users input on this topic.
http://www.cyanogenmod.org/blog/releases-11-12-final
What I don't understand is Cyanogen's priorities when it comes to which devices get 11, 12 or 12.1. I completely understand about phasing out CM11/KitKat as that is now a rather "old" version of android. However what I don't understand is why a device as new/old as ours (Aug 2013 is not THAT old) is stuck on CM12 (and now a final Snapshot build as of 6/25)? I mean, the Galaxy S3 is even getting 12.1 builds. I'm wondering if its because that was a far more popular device than the G2 was?
Just wanted to put this out there and see what other people think and find out what they're running currently on their G2 variant. I own the US T-Mobile D801 variant and do NOT want to run stock (LG) Lollipop since my device tends to run extremely HOT on it. I know not everyone was complaining about their G2 overheating on stock LP but I notice a considerable difference running CM12.
So, how do you guys feel about this? Do you even care or what?
Click to expand...
Click to collapse
We haven't had nightlies for a while now. What you see as nightlies aren't really worthwhile builds, they didn't have any device or kernel fixes for the g2.
A new 11 build is coming probably because half the android userbase relies on kitkat at the moment.
As for the s3, it's not getting CM12 nor 12.1, not the international version at the least. Archi is maintaining an unofficial version, but it still carries the bugs from 10.0/10.1.
Lastly, this is the commit that requires to be merged in order for the builds to even be considered started:
http://review.cyanogenmod.org/#/c/93181/
Without it, nothing CAF related can be merged, and as such, no CM12.1 builds can be had for our device. I believe the reason it's not merged because not all of the variants have a lollipop release, if they ever will get one. Also the whole bootstack/amount of users who don't reed is astonishingly dangerous to handle, so rashed simply preferred to skip building for now.
Finally, it's not that popular of a device. It's a nexus without being a nexus with a locked bootloader, which is a pain in the ass and not too many maintainers have it left (they either went with G3 or skipped LG entirely, as did a whole bunch from the exynos team back in the day).
t3chn0s1s said:
I saw you responded to my post about CM12 nightlies not continuing for the G2. Wanted to ask you (since you didn't mention) what 5.1 (CAF source) ROM you're running? What would you suggest for a stable AOSP ROM that has device/kernel specific updates for our G2s?
Click to expand...
Click to collapse
Why not reply to me in this thread then?
I'm running official euphoria builds. Any caf roms run fine. They are all based on the same LG-devs CAF device source + kernel source. Some roms have specific tweaks, but as far as functionality, they all work the same way (ie: if bluetooth deep sleep is broken, it's most likely broken in every rom).
Choristav said:
Why not reply to me in this thread then?
I'm running official euphoria builds. Any caf roms run fine. They are all based on the same LG-devs CAF device source + kernel source. Some roms have specific tweaks, but as far as functionality, they all work the same way (ie: if bluetooth deep sleep is broken, it's most likely broken in every rom).
Click to expand...
Click to collapse
Sorry - was on my phone when I saw your replies and it was just easier for me to respond in the other thread.
Anyways.. thanks for the info. I've done some research and I'm a bit more informed about CAF and what it means to device specific sources, ROMs, etc. Are you just using the stock Euphoria kernel or something else?
On this forum @varund7726 builds his rather excellent ResurrectionRom from the latest CM code release. I suggest you use that. For the D803, @zr239 has beaten all odds including LG not releasing CAF code, to build a fully functional pure CM 12.1 ROM that closely tracks official CM repos.
Lg G2 has it pretty good !
@Choristav
I wanted to clarify something you said in your initial response to my OP. You said the S3 wasn't going to get CM12 or 12.1 but when I navigate to the CM downloads page for ANY S3 variant - they ALL have CM12.1 nightlies still being generated. What exactly did you mean?
t3chn0s1s said:
@Choristav
I wanted to clarify something you said in your initial response to my OP. You said the S3 wasn't going to get CM12 or 12.1 but when I navigate to the CM downloads page for ANY S3 variant - they ALL have CM12.1 nightlies still being generated. What exactly did you mean?
Click to expand...
Click to collapse
I checked, you are right, several of the qualcomm variants have cyanogenmod support. This means that they have active maintainers, but they also don't have to deal with locked bootloader crap, which is why the bump commit is so important for our device.
I only mentioned the international version, which support was dropped because it had a lot of issues thanks to its closed source exynos processor (it requires extra work, and some stuff doesn't end up working anyway).
Not really much to say, the commit is already in CM's gerrit, it's just waiting for review. Maybe it's a CTS-side issue?
Aside from that, being a maintainer doesn't really require much, just effort and presence. It's not an easy task, I'm just saying anyone can apply to be a maintainer and get nighties rolling for a device you might not even have heard of.
@Rashed97 is the man for our G2 when it comes to CM. Dont mind nightlies as long as Rashed is around
Note: he is currently busy with the One M9 but we will hopefully see some cool stuff from him in the future.
Not really a big deal, last I remember those nightlies were still using outdated jellybean components. I wouldn't use them, I would use something on the G2 forums like Rashed97 builds like someone else said.
I don't think that the availability of nightlies has to do with the device itself so much as it has to do with someone maintaining the g2 and building roms, so nightlies could come back at any time if someone steps up and does it.
Ploxorz said:
Not really a big deal, last I remember those nightlies were still using outdated jellybean components. I wouldn't use them, I would use something on the G2 forums like Rashed97 builds like someone else said.
I don't think that the availability of nightlies has to do with the device itself so much as it has to do with someone maintaining the g2 and building roms, so nightlies could come back at any time if someone steps up and does it.
Click to expand...
Click to collapse
And it appears you're correct as there is another nightly build up with today's date. I apparently posted this thread prematurely.
Guys I wouldnt worry to much about CM, its not like they are the only (or even best) option in the forums. If you guys want development then dig in and make some for it.
zelendel said:
Guys I wouldnt worry to much about CM, its not like they are the only (or even best) option in the forums. If you guys want development then dig in and make some for it.
Click to expand...
Click to collapse
You are absolutely right. I had no idea until I posted this thread that CM nightlies did not contain any device specific updates. I honestly NEVER used to like CM at all. I honestly hated it... until owning a OnePlus One. I originally had the G2 right when it came out in 2013 and sold it off long ago & moved on to better devices - but when my OPO got stolen about 2 months back or so - I had to find a relatively cheap, but decent device and the G2 was the best bang for the buck (5.2" display, quick charge 2.0, 3000 mAh battery) and no other phones in 2013 came close to the specs the G2 had at the time.
So, now that I know CM is basically a sh*t ROM for this device I'll be moving on to a ROM that is compiled using CAF sources. Thanks everyone for your input!
Somehow doesn't look too good so far:
https://jira.cyanogenmod.org/browse/CYAN-6556
But why oh why?
The LG G2 still is such a modern and powerful device. It might be almost two years "old", but it's way better than a lot of other current devices.
I am using AICP on my g2. It is based on CM(5.1.1).
What's the best place to follow updates / changes to the CAF stuff?
I know there's a handful of ROMs based on CAF sources, I'm not too interested in the changelogs of those ROMs, more following the progress of CAF before it eventually all gets merged into CM12.1.
Is this it? https://github.com/lg-devs/android_device_lge_g2-common/commits/cm-12.1-caf
seanp25 said:
What's the best place to follow updates / changes to the CAF stuff?
I know there's a handful of ROMs based on CAF sources, I'm not too interested in the changelogs of those ROMs, more following the progress of CAF before it eventually all gets merged into CM12.1.
Is this it? https://github.com/lg-devs/android_device_lge_g2-common/commits/cm-12.1-caf
Click to expand...
Click to collapse
I would watch the Code Aurora forums where CAF comes from.
zelendel said:
I would watch the Code Aurora forums where CAF comes from.
Click to expand...
Click to collapse
It's better to watch public activity on Rashed97's github. He is CM maintainer for LG G2 and he brought up CAF sources for our devices.
adamz667 said:
It's better to watch public activity on Rashed97's github. He is CM maintainer for LG G2 and he brought up CAF sources for our devices.
Click to expand...
Click to collapse
No. It's far better to watch the main code base. Cm messes too much up by not testing code before merging.
zelendel said:
No. It's far better to watch the main code base. Cm messes too much up by not testing code before merging.
Click to expand...
Click to collapse
Okay, but @seanp25 probably want to follow source changes for our device, not common CAF source.
Just saw this:
Çetin ÇÖNE wrote on Jul 26 11:18 AM:
Why there is no nighlies it's really stable. Merge it please
Seth Shelnutt wrote on Jul 26 1:26 PM:
There are no nightlies because SELinux is not enabled. Sensors break with it enabled and I don't have time to address it yet.
Click to expand...
Click to collapse
Source:
http://review.cyanogenmod.org/#/c/103673/
Some days after that there came this:
http://review.cyanogenmod.org/#/c/103674/
So maybe there soon will be 12.1 nightlies?
I know this is going to be a somewhat complicated process, but I'm willing to stick with it.
I'm willing to upgrade to any ROM, really, I'm not picky. If nobody suggests anything different, I'll just go with Cyanogenmod. What I really want is Android M running on the device as soon as possible. Which ROM gets that update out the quickest? I'm a complete beginner at everything you can think of, but I can read and I have a computer, so I can follow tutorials just fine.
Any ideas which ROM I should upgrade to when the time comes? (I mean, if any developers have announced the update to M and their support for the Mate2). If not, my main question is when will Cyanogenmod developers start building on Android M? And when do you think it will get over to the Mate2?
EDIT: I know it hasn't come out yet, but sometimes developers announce that their ROM will be based on some new version of android before it even comes out.
Both PAC and CM are nice. I run CM because I prefer the stick android experience . PAC has more bells and whistles. Personal preference really. SuperBass has made videos on both of them. As well as installing each one.
M will probably never make it to the HAM2. CM works great and is easy to install. Just jump in there with both feet.
kimtyson said:
M will probably never make it to the HAM2. CM works great and is easy to install. Just jump in there with both feet.
Click to expand...
Click to collapse
Well, to get there, I'd have to downgrade to Jellybean, upgrade to Lollipop, and then start the CM install, which I'm likely to **** up. It's gonna be more like a couple of slow hops in different directions.
kimtyson said:
M will probably never make it to the HAM2. CM works great and is easy to install. Just jump in there with both feet.
Click to expand...
Click to collapse
Yeah, I was wondering about M. So the official Huawei devs won't update to Android M, but won't CM be updated to be based on it? Is that how it works, or am I mistaken?
I am under the impression that CM has official developers who actually work on the ROM. Then other developers use that and make it available for different devices. Therefore, Android M will be coming to the Mate2 as long as CM is updated by the official developers and it gets support for the device, right?
Mackks said:
Yeah, I was wondering about M. So the official Huawei devs won't update to Android M, but won't CM be updated to be based on it? Is that how it works, or am I mistaken?
I am under the impression that CM has official developers who actually work on the ROM. Then other developers use that and make it available for different devices. Therefore, Android M will be coming to the Mate2 as long as CM is updated by the official developers and it gets support for the device, right?
Click to expand...
Click to collapse
No, that's not how it works, actually. Huawei would have to release the HAM2 specific M code for other ROMs to use it. I am about 99.9 percent sure that Huawei will not build M for the HAM2 so it dies on the vine, so to speak.
kimtyson said:
No, that's not how it works, actually. Huawei would have to release the HAM2 specific M code for other ROMs to use it. I am about 99.9 percent sure that Huawei will not build M for the HAM2 so it dies on the vine, so to speak.
Click to expand...
Click to collapse
So CM isn't a base that device developers tweak to work with specific devices? Do you mean that CM is developed over what the phone manufacturers release?
Mackks said:
So CM isn't a base that device developers tweak to work with specific devices? Do you mean that CM is developed over what the phone manufacturers release?
Click to expand...
Click to collapse
Devs need manufacturer kernel source to build off of. Someone can PORT M to this phone. But I seriously doubt that happens. Huawei will surely NOT release M. They barely managed L. And that was only due to so many complaining about no support.
Mackks said:
So CM isn't a base that device developers tweak to work with specific devices? Do you mean that CM is developed over what the phone manufacturers release?
Click to expand...
Click to collapse
Yes, CM is often used as a base that other devs use to add their stuff on top of. But, if the manufacturer doesn't release their code (which includes drivers and such), then there will be no CM. Yes, CM is developed over what the phone manufacturers release.
If you want to see CyanogenMod for this device...start here:
https://www.gofundme.com/j2ja89xs
And follow here:
http://forum.xda-developers.com/lg-v10/general/discussion-cm-12-lg-v10-g4-cm12-t3241897/page26
Once we have Base... Ports are next.
Fingers crossed. Waiting patiently.
Bumping this as we are more then half way there.
I'm excited for a CM base, I don't know about the rest of you...
Even though everyone is excited for a cm based rom, we have too keep in mind that this phone is amazing because of its camera and I'm pretty sure in order to run those features it'll require alot of lg files so in the end , most of us will most likely adhere to stock than cm , at least IMO
tavito05 said:
Even though everyone is excited for a cm based rom, we have too keep in mind that this phone is amazing because of its camera and I'm pretty sure in order to run those features it'll require alot of lg files so in the end , most of us will most likely adhere to stock than cm , at least IMO
Click to expand...
Click to collapse
Yep, and in addition to that there's also the HiFi DAC/Amp and the secondary screen. With such specialized hardware I feel like a debloated stock-based ROM is probably gonna always be the best bet, though of course more development and more options are never a bad thing
Working CM 12 is posted in the development section. Flash away.
Sent from my LG-H901 using Tapatalk
Wow. Amazing! Hoping for CM 13
But having CM 12 is also good ofc!
Thx
No data
Has anyone had any problems with no data I installed 12.1 the latest version with the gapps everything works I can send and receive text messages and phone calls just have no data any answers would be appreciated my data switch is on
Anyone else see this:
https://9to5google.com/2016/09/19/zte-is-working-to-bring-an-official-cyanogenmod-rom-to-the-axon-7/
Yes, it's been discussed in the CM dev topic.
xtermmin said:
Yes, it's been discussed in the CM dev topic.
Click to expand...
Click to collapse
What most are not realizing, is that there are two versions of Cyanogen built operating systems. Cyanogen OS is built by Cyanogen Inc. for the device manufacturer and the other is community driven and is open source. These two operating systems may be identical in how they operate once on the device, but how they are developed is different. The question is which one is actually being developed?
jim262 said:
What most are not realizing, is that there are two versions of Cyanogen built operating systems. Cyanogen OS is built by Cyanogen Inc. for the device manufacturer and the other is community driven and is open source. These two operating systems may be identical in how they operate once on the device, but how they are developed is different. The question is which one is actually being developed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/axon-7/development/cyanogenmod-13-a2017u-t3457410/page10
If it is a true CyanogenMod rom, that means ZTE would have to release proprietary source codes for open source development. They have not done that as of this writing. So more than likely a Cyanogen operating system will be created for this device totally in house, thereby not allowing for future development by the "open source" community of devs.
jim262 said:
If it is a true CyanogenMod rom, that means ZTE would have to release proprietary source codes for open source development. They have not done that as of this writing. So more than likely a Cyanogen operating system will be created for this device totally in house, thereby not allowing for future development by the "open source" community of devs.
Click to expand...
Click to collapse
From what I'm gathering from the discussions on the ZTE Community forums and the Cyanogenmod dev topic I linked, it seems that ZTE is sending their code to Cyanogen employee Steve Kondik to create an official cyanogenmod github for the A7, not that Cyanogen the company is going to create a CyanogenOS for the device.
Only for USA.
rikin93 said:
Only for USA.
Click to expand...
Click to collapse
Correction: Only for unlocked bootloaders, as it will not be officially signed by ZTE.
xtermmin said:
From what I'm gathering from the discussions on the ZTE Community forums and the Cyanogenmod dev topic I linked, it seems that ZTE is sending their code to Cyanogen employee Steve Kondik to create an official cyanogenmod github for the A7, not that Cyanogen the company is going to create a CyanogenOS for the device.
Click to expand...
Click to collapse
Based on what I have seen and heard, the difference between OS and Mod is nill. They are exactly the same. The difference between the two is how they are developed. One is open source and can be shared by the general public, the other is developed in house for the device manufacturer and proprietary information is kept in house and not shared. The two are quite often just referred to as CyanogenMod, although they are different.
jim262 said:
Based on what I have seen and heard, the difference between OS and Mod is nill. They are exactly the same. The difference between the two is how they are developed. One is open source and can be shared by the general public, the other is developed in house for the device manufacturer and proprietary information is kept in house and not shared. The two are quite often just referred to as CyanogenMod, although they are different.
Click to expand...
Click to collapse
There's a huge difference between CyanogenOS and CyanogenMod behind the scenes though. Like you said, CyanogenOS is in-house, but most importantly it tends to include bloatware, especially now that Cyanogen the company is owned by Microsoft. And since it's closed source, people who want to develop custom ROMs will still have no access to the sources that would speed up development. Plus, if there are bugs or features that people want to implement, they can't, and have to wait for Cyanogen to release them. This also means that things such as security patches will have to wait for official rollout by Cyanogen.
Cyanogenmod, however, is open source, not controlled by Cyanogen the company at all, bug fixes / features can be added and addressed by the community, security patches can be applied to nightlies quickly, etc.
jim262 said:
If it is a true CyanogenMod rom, that means ZTE would have to release proprietary source codes for open source development. They have not done that as of this writing. So more than likely a Cyanogen operating system will be created for this device totally in house, thereby not allowing for future development by the "open source" community of devs.
Click to expand...
Click to collapse
It's been clarified multiple times on the ZTE forum that it will be CyanogenMod, not CyanogenOS. Unless there's some weird, first-time-in-history NDA regarding the HALs / overlay that ZTE provides for the development of CM, they will be open source.
If they did offer open source at least it would alleviate concerns on the Chinese state-sponsored company reputation
Finally, the best hardware of 2016 and all it needs is aosp love... I hope this helps to spur more development or makes it easier for our fantastic developers at XDA.
From what I read from the Employees at ZTE Forums, ZTE currently doesn't want to deal with setting up a place for Devs to access the needed resources for things, so they're basically going to just dump it all on CyanogenMod for them to sort it out. It's easier for the ZTE higher-ups to swallow that way.
Do we have any ETA on this ?
I fear than the OP3 will get more love from the dev, and that the Axon 7 will be forgotten :/
rczrider said:
It's been clarified multiple times on the ZTE forum that it will be CyanogenMod, not CyanogenOS. Unless there's some weird, first-time-in-history NDA regarding the HALs / overlay that ZTE provides for the development of CM, they will be open source.
Click to expand...
Click to collapse
Don't count on anything "open" from ZTE. It really doesn't matter what they may say, the reality this phone doesn't have much more than the day it was released.
Araewuir said:
Do we have any ETA on this ?
I fear than the OP3 will get more love from the dev, and that the Axon 7 will be forgotten :/
Click to expand...
Click to collapse
The oneplus one still gets more dev support than the Nexus 6p. Oneplus devices get pretty much the best dev support period. That being said, more devs are starting to get the axon 7, but we're never going to be at the oneplus 3 level of support. The oneplus 3 is supported by SultanXDA, flar2, Franco, despair, and dozens more. It had official cm13 support as soon as it was released. It has official support from paranoid Android, elemental x, Franco kernel, PAC rom, dirty unicorns, and pretty much every other rom and kernel you've ever heard of. I love the Axon, but I don't it's ever going to get that kind of support.
jim262 said:
Don't count on anything "open" from ZTE. It really doesn't matter what they may say, the reality this phone doesn't have much more than the day it was released.
Click to expand...
Click to collapse
Okay.
xxBrun0xx said:
The oneplus one still gets more dev support than the Nexus 6p. Oneplus devices get pretty much the best dev support period. That being said, more devs are starting to get the axon 7, but we're never going to be at the oneplus 3 level of support. The oneplus 3 is supported by SultanXDA, flar2, Franco, despair, and dozens more. It had official cm13 support as soon as it was released. It has official support from paranoid Android, elemental x, Franco kernel, PAC rom, dirty unicorns, and pretty much every other rom and kernel you've ever heard of. I love the Axon, but I don't it's ever going to get that kind of support.
Click to expand...
Click to collapse
I feel like the last phone I owned with that level of support was the Nexus 4.
rczrider said:
Okay.
I feel like the last phone I owned with that level of support was the Nexus 4.
Click to expand...
Click to collapse
One Plus released everything before the phone even hit the market, so there was development for the One Plus 3 from the beginning. The Axon, in my opinion, is a very good device, but ZTE has limited development of this product. It is almost as though they are perfectly happy being an iPhone/Apple wannabe.
japzone said:
From what I read from the Employees at ZTE Forums, ZTE currently doesn't want to deal with setting up a place for Devs to access the needed resources for things, so they're basically going to just dump it all on CyanogenMod for them to sort it out. It's easier for the ZTE higher-ups to swallow that way.
Click to expand...
Click to collapse
Which is never a good thing. Especially when they admit they don't care.
As a Sprint subscriber I'm locked out of the Axon7 until Sprint stop being dickbags about BYOD, which most likely will be never. If that changes, I'll probably buy an A7 if CM actually appears in a timely fashion since Shamu is being dropped by Google very shortly.
...but dumping code on the community and expecting them to make it right is massively annoying at best. It is exactly what Google does with AOSP....The Nougat AOSP is seriously broken and takes a ton of effort to fix enough just to get to compile. The stock AOSP GApps packages are all in varying stages of brokenness as of now. Sure they release the source, but what you get doesn't compile without a ton of forensic work.
Nougat has been on Nexus for over a month (minus Shamu)...and it is not going well.
Hello developers and LG G5 users,
I recently got the LG G5, and everything has been great! Performance is top-notch, display is stunning, and camera takes amazing pictures.
I have the RS988 model, which is the United States carrier unlocked model (not tied to any carrier). It is available at Amazon here: https://www.amazon.com/gp/aw/d/B01DJE22C2/ref=cm_cr_arp_mb_bdcrb_top?ie=UTF8.
I ask with respect and courtesy, does anyone have plans for supporting this model with custom ROMs? I see that the H850 and H830 models are supported, but not the RS988. This model is officially supported by LG for a bootloader unlock, and a working TWRP build is available.
Again, I would like to ask if anyone has plans for supporting the RS988 model with a custom ROM. Fulmics o), Resurrection Remix, AOSPA, Dirty Unicorns, OwnROM, AICP, AOSPExtended, Lineage, ANTHING!
I could even do some light testing, and I'm sure other people feel the same way.
Sincerely,
An LG G5 RS988 user,
Unscedeo
Unscedeo said:
Hello developers and LG G5 users,
I recently got the LG G5, and everything has been great! Performance is top-notch, display is stunning, and camera takes amazing pictures.
I have the RS988 model, which is the United States carrier unlocked model (not tied to any carrier). It is available at Amazon here: https://www.amazon.com/gp/aw/d/B01DJE22C2/ref=cm_cr_arp_mb_bdcrb_top?ie=UTF8.
I ask with respect and courtesy, does anyone have plans for supporting this model with custom ROMs? I see that the H850 and H830 models are supported, but not the RS988. This model is officially supported by LG for a bootloader unlock, and a working TWRP build is available.
Again, I would like to ask if anyone has plans for supporting the RS988 model with a custom ROM. I could even do some light testing, and I'm sure other people feel the same way.
Sincerely,
An LG G5 RS988 user,
Unscedeo
Click to expand...
Click to collapse
It would be nice, I have the same model. I was thinking about getting into Android development and working on this phone but that'll take a good while, most developers probably looked over this phone since it for unlockable so late and really I think stock is enough. I have it modified for my needs and it's alright. And you would think this model would get some development since it's not tied to a carrier but I guess not. If I find where to start and everything I might work on this device and of somehow I figure things out I'll be in development for at least 2-3 years for this device.
Please make custom ROM for rs988
You're to late Guys. The G5 is almost completely abdoned and the Most Devs (Who had a Choice) are gone. Outdated 7.0 Stock Firmware and a lack of good Sources are killing the Rest. Besides that is asking for any Development on it just crazy. You don't need to ask! If there is nothing, there will come nothing....
Never LG again! To many mistakes and not a piece Developer friendly at all. Try to sell Your G5 and You will See what i mean!
He's right about the lack of good sources I had an H830 and the roms for it take away useful features for the lg g5. And all have the same bugs. I tried them but kept going back to stock.
There used to be a time when custom roms made the phone better. That time seems to have passed, it is getting harder and harder to root carrier phones, not just lg.
The rs988 is a smooth running phone, with root we get full control of our phone. If you are not happy with that feel free to port over a rom, but please stop asking for dev support.
We are on our own with this phone.
I'm kinda glad this phone has been abandoned and looked upon so poorly.
I bought a brand new rs988 build date 3/17 for 249.00 B&H Photo about 6 weeks ago. The build quality is better, the screen is better, and no gps issues.
Since the Nougat update the phone is so much improved but if you don't like Nougat you can always downgrade back to marshmallow. (benefit of unlocked bootloader)
I bought genuine batteries from NewEgg recently for 5.99 a piece.
It's one of the few unlocked phones that work on Verizon.
But for me the "always listing" (just like the pixel) very few phones have that feature. The removable battery, the IR blaster, expandable storage are requirements.
If I need waterproofing I throw on my fre lifeproof I bought new for 20 bucks.
Just because something is hard doesn't mean it's not worth it. This phone has been given up on too quickly.
At the current price I wouldn't be surprised if some come back to it.
Peace
Yes, I understand everyone's thoughts about development stopping for the LG G5. I am rooted and the stock ROM is excellent, I was just simply inquiring about custom ROM status. Didn't mean to bug or annoy any developers. It would just be nice if there was support, that's all.
wolfu11 said:
I bought genuine batteries from NewEgg recently for 5.99 a piece.
Click to expand...
Click to collapse
By the way, could you send me the link to this? That price is just insane. The lowest I've seen is $11 at Walmart.
Tbh even though I have an h850 I don't see development stopping for custom ROMs on G5, it's being worked on. Slowly yeah,it's summer time,can't expect anyone to give up on some holiday and enjoyment to tinker around. Most of the stuff is already there to support RS988. LineageOS is official for G5,Mokee is official for G5 (2 versions on both for now), besides NFC bug(that's being worked on and there's already a half working solution) Bluetooth bug (not syncing to some products but working) and video saving( just a matter of time when it will be fixed) G5 in general is a fully supported by custom ROMs.We have a lot of unofficial builds too. Getting an official build instead of unofficial one is an advantage not a deal breaker and building your own build isn't that hard anyway. I've studied that for 5 days and have a build for H850 already. And it just took me 5 days cause of my slow internet speed. So a negative attitude won't do any good, positive thinking,catlogs, sharing your findings, sharing your fixes, might see a change.
If you can't wait, build
onestyle007 said:
Tbh even though I have an h850 I don't see development stopping for custom ROMs on G5, it's being worked on. Slowly yeah,it's summer time,can't expect anyone to give up on some holiday and enjoyment to tinker around. Most of the stuff is already there to support RS988. LineageOS is official for G5,Mokee is official for G5 (2 versions on both for now), besides NFC bug(that's being worked on and there's already a half working solution) Bluetooth bug (not syncing to some products but working) and video saving( just a matter of time when it will be fixed) G5 in general is a fully supported by custom ROMs.We have a lot of unofficial builds too. Getting an official build instead of unofficial one is an advantage not a deal breaker and building your own build isn't that hard anyway. I've studied that for 5 days and have a build for H850 already. And it just took me 5 days cause of my slow internet speed. So a negative attitude won't do any good, positive thinking,catlogs, sharing your findings, sharing your fixes, might see a change.
If you can't wait, build
Click to expand...
Click to collapse
Hiya, have you got any good guides I can possibly use to start building from source? I would love to do this.
Thanks
seraphism said:
Hiya, have you got any good guides I can possibly use to start building from source? I would love to do this.
Thanks
Click to expand...
Click to collapse
I'm on my phone now,but have some bookmarked on my laptop. When I get home I'll pass some. For starters search XDA and use Google building Android from source, plus go on LineageOS manifest GitHub. Repo sync first,it will take a while. By the way, you'll need a stronger PC or laptop if you want to build fast also Linux or osx or on Windows you'll need Linux in virtual PC. SSD drive recommend.
Unscedeo said:
Yes, I understand everyone's thoughts about development stopping for the LG G5. I am rooted and the stock ROM is excellent, I was just simply inquiring about custom ROM status. Didn't mean to bug or annoy any developers. It would just be nice if there was support, that's all.
By the way, could you send me the link to this? That price is just insane. The lowest I've seen is $11 at Walmart.
Click to expand...
Click to collapse
Unfortunately they are sold out now....
View attachment 4212964
View attachment 4212965
Don't get Me wrong. I've put much efforts into this Phone since i still think it's a good piece of Hardware. I'm also Out of Money so i have to stick with it. But it makes Me crazy sometimes as a Ex Samsung, HTC, SONY and Nexus User/Dev to have a LG.
-The Sources
-The Community (XDA)
-The Bootloader (Recovery Access, Bootloader Message)
-The Build Quality (Light Shadows on the Display, the bottom Gap, Volume Rocker Stucks)
And the most Important Thing - UPDATES
We are using a 2016 Flagship and No Android 7.1? Still?
What about Android 0? Do we get a real Update or just a Copy OS from the V20? Like with the actual/past Updates?
I'm really done with LG. That they ditched us with the Modules is another Big Point for Me as G5 User. I would at least be more happy with a V20 since it wasn't a Joke like the G5....
For those interested, the following LG G5 variants have the same FCC ID of ZNFVS987:
Code:
VS987 - Verizon Wireless variant
US992 - U.S. Cellular variant
RS988 - General North America variant
Presumably, the variants are of the same hardware, but have different firmware.
Okay,let's start with the basics. First we are going to make the device tree so at least devs without your phone version would try to build a custom rom ( non stock based) for rs988.
Following parts of this tutorial extract boot.img and share it here.
https://forum.xda-developers.com/showpost.php?p=45721523&postcount=1
Then after that, following this tutorial we'll make your device tree.
https://forum.xda-developers.com/showpost.php?p=69576711&postcount=1
onestyle007 said:
Okay,let's start with the basics. First we are going to make the device tree so at least devs without your phone version would try to build a custom rom ( non stock based) for rs988.
Following parts of this tutorial extract boot.img and share it here.
https://forum.xda-developers.com/showpost.php?p=45721523&postcount=1
Then after that, following this tutorial we'll make your device tree.
https://forum.xda-developers.com/showpost.php?p=69576711&postcount=1
Click to expand...
Click to collapse
OK, great! Thank you for starting the development train.
I am new to this kind of stuff, but I am willing to do it. Is have some knowledge of ADB/Fastboot and looking at partitions. So basically what I need to do is extract the boot.img from my phone, and then create a device tree for the phone. Where should I put the tree when it's done?
Unscedeo said:
OK, great! Thank you for starting the development train.
I am new to this kind of stuff, but I am willing to do it. Is have some knowledge of ADB/Fastboot and looking at partitions. So basically what I need to do is extract the boot.img from my phone, and then create a device tree for the phone. Where should I put the tree when it's done?
Click to expand...
Click to collapse
When all that is done,well then you or any other developer uses that tree with already synced repo from any of the custom ROMs along with the G5 repos to try and make a build.
First thing's first,to get a device tree. Building a rom from the source comes later, and luckily there's more than one tutorial on how to get it done. Then it's figuring out what doesn't work and how to fix it.
Source?
So I extracted boot.img, have the file. When I go to the link you gave me for creating a device tree, it says that I need the source code. Sorry if I'm acting like a noob, but where do I get that? I found this link: http://opensource.lge.com/osSch/list?types=NAME&search=lgrs988, but I don't know if I should use it.
Unscedeo said:
So I extracted boot.img, have the file. When I go to the link you gave me for creating a device tree, it says that I need the source code. Sorry if I'm acting like a noob, but where do I get that? I found this link: http://opensource.lge.com/osSch/list?types=NAME&search=lgrs988, but I don't know if I should use it.
Click to expand...
Click to collapse
Can you screenshot what exactly it's asking from you? And by the way, I doubt it's lg open source, probably just google android source. But let me see it first.
By the way, another tut on how to make a device tree
https://forum.xda-developers.com/showthread.php?t=2010281
onestyle007 said:
Can you screenshot what exactly it's asking from you? And by the way, I doubt it's lg open source, probably just google android source. But let me see it first.
By the way, another tut on how to make a device tree
https://forum.xda-developers.com/showthread.php?t=2010281
Click to expand...
Click to collapse
Never mind, I figured out how to unpack the boot.img. I now have the basic files created, including AndroidBoard.mk, AndroidProducts.mk, etc. I just created the files that are listed in this tutorial (the one you gave me): https://forum.xda-developers.com/showthread.php?t=2010281
So I also found this on Github, which states that it is the device tree for the RS988: https://github.com/jcadduono/android_device_lge_rs988. I don't know if that is what you want me to make, and if it is, can we use that? If that isn't the right tree, I am currently on writing the BoardConfig.mk file, which is one of the steps in the tutorial mentioned above. it says to use a "cousin device" tree. What should I use for that?
Thanks
Thanks for this..
Again.. thanks for the heads up on how to get the ball rolling on this.. I should have some time to unlock my bootloader and post the boot.img and other necessary files this weekend..
Cheers!
onestyle007 said:
Okay,let's start with the basics. First we are going to make the device tree so at least devs without your phone version would try to build a custom rom ( non stock based) for rs988.
Following parts of this tutorial extract boot.img and share it here.
https://forum.xda-developers.com/showpost.php?p=45721523&postcount=1
Then after that, following this tutorial we'll make your device tree.
https://forum.xda-developers.com/showpost.php?p=69576711&postcount=1
Click to expand...
Click to collapse
Any luck with our rs988? ?
Sent from my SM-G950N using Tapatalk