CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=vs985&type=nightly
Google apps addon:
Download: http://wiki.cyanogenmod.org/w/Google_Apps
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] CyanogenMod 12.0 Nightlies for the Verizon LG G3 (vs985), ROM for the Verizon LG G3
Contributors
invisiblek
Source Code: http://www.github.com/CyanogenMod
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Created 2015-01-09
Last Updated 2015-01-09
Its been good so far.
So far so good, GPS/Data/Battery have all been great so far.
This mine ..thanks
Enviado desde mi LG-VS985 mediante Tapatalk
Anyone having an issue not being able to get into Language & Input in Settings? Every nightly so far Settings FCs when I try to open that. It's the only thing I can find that's weird. I dirty flashed from 01/04 invisiblek to the Jan 5th, 8th and now 9th nightlies. Every one has that issue.
phobos512 said:
Anyone having an issue not being able to get into Language & Input in Settings? Every nightly so far Settings FCs when I try to open that. It's the only thing I can find that's weird. I dirty flashed from 01/04 invisiblek to the Jan 5th, 8th and now 9th nightlies. Every one has that issue.
Click to expand...
Click to collapse
No problems here, what GAPPS did you flash? Might have something to do with the keyboard.
I've been on the same GApps (PA, 25 Dec) and keyboard (Swype) since December. Issue only started when I flashed the first official nightly for CM12 (previously was using the unofficial build by OP).
phobos512 said:
I've been on the same GApps (PA, 25 Dec) and keyboard (Swype) since December. Issue only started when I flashed the first official nightly for CM12 (previously was using the unofficial build by OP).
Click to expand...
Click to collapse
If I were a betting man I'd say a clean flash will do you well, as I rarely enter that menu so had to try it before I commented, but just did so and mine works fine as well. I just re entry had a kernel panic on the 1/9 build, but that's honestly the first one of those I've ever had while running these cm12 builds, so that's doing pretty well I'd say. I know other people saw them as they seem to have mellowed out a bit, so I really can't complain. Proximity bug is an annoyance still, but I'm finding myself getting used to that haha, so my only other issue is the occasional disconnect sounds mid call, and having to toggle speakerphone on and off to be able to hear the caller again. Outside of these two things off the top of my head, the general stability right now seems pretty solid.
phobos512 said:
Anyone having an issue not being able to get into Language & Input in Settings? Every nightly so far Settings FCs when I try to open that. It's the only thing I can find that's weird. I dirty flashed from 01/04 invisiblek to the Jan 5th, 8th and now 9th nightlies. Every one has that issue.
Click to expand...
Click to collapse
I've had absolutely no problems with this either. When the CM 12.0 nightlies went official I did do a clean install of the first nightly and then dirty flashed each one after. Using the 12/25 stock Gapps package and Google keyboard.
Thanks all. Going to do a clean flash now. I will report back.
Do you know if any of the features lg has made for this phone will be added or embedded like the ir blaster and or the split screen?
Sent from my iPad using Tapatalk
digitallure said:
Do you know if any of the features lg has made for this phone will be added or embedded like the ir blaster and or the split screen?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Probably not into CM at least. Maybe other 5.0 ROMs
Sent from my Sump'd and Bump'd G3, Thanks to Team Codefire
---------- Post added at 02:46 PM ---------- Previous post was at 02:37 PM ----------
Here is a nice, clean, long list of commits.
http://www.cmxlog.com/12/vs985/
Dan's first commit on the 1/10 build is funny af
Sent from my Sump'd and Bump'd G3, Thanks to Team Codefire
ohlin5 said:
If I were a betting man I'd say a clean flash will do you well, as I rarely enter that menu so had to try it before I commented, but just did so and mine works fine as well. I just re entry had a kernel panic on the 1/9 build, but that's honestly the first one of those I've ever had while running these cm12 builds, so that's doing pretty well I'd say. I know other people saw them as they seem to have mellowed out a bit, so I really can't complain. Proximity bug is an annoyance still, but I'm finding myself getting used to that haha, so my only other issue is the occasional disconnect sounds mid call, and having to toggle speakerphone on and off to be able to hear the caller again. Outside of these two things off the top of my head, the general stability right now seems pretty solid.
Click to expand...
Click to collapse
I'm having earpiece issues as well where I also have to cycle speakerphone.
Sent from my LG-VS985 using XDA Free mobile app
digitallure said:
Do you know if any of the features lg has made for this phone will be added or embedded like the ir blaster and or the split screen?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Qmote is working right now http://forum.xda-developers.com/showthread.php?t=2929146
You have to reflash after any update and readjust the build.prop. but it's working quite nicely
Sent from my LG-VS985 using XDA Free mobile app
digitallure said:
Do you know if any of the features lg has made for this phone will be added or embedded like the ir blaster and or the split screen?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
It says you joined XDA in 2010. It's now 2015. By now you ought to know that IN GENERAL it is HIGHLY UNLIKELY that OEM specific features will make it into AOSP based ROMs. If you want those features, you will more than likely need to stick with a stock based ROM.
---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------
phobos512 said:
Thanks all. Going to do a clean flash now. I will report back.
Click to expand...
Click to collapse
All goodness. Working just fine now. Hopefully the battery life estimate I was seeing before the clean flash will carry forward. Said I'd be needing to recharge on JAN 17TH lol!
jco897j said:
I'm having earpiece issues as well where I also have to cycle speakerphone.
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
Try disabling tap2wake and see if this continues to happen (testing a theory).
Having a continuous issue here. Whenever I call a person, it hangs up about 10 seconds into the call. Switching to speaker phone and back doesn't work.
Sent from my Sump'd and Bump'd G3, Thanks to Team Codefire
invisiblek said:
Try disabling tap2wake and see if this continues to happen (testing a theory).
Click to expand...
Click to collapse
Running the most recent nightly I'm having trouble replicating the issue.
Sent from my LG-VS985 using XDA Free mobile app
Figured I would just post this on this thread since it is a prominent issue. Cm updater doesn't work.
Sent from my Sump'd and Bump'd G3, Thanks to Team Codefire
phobos512 said:
It says you joined XDA in 2010. It's now 2015. By now you ought to know that IN GENERAL it is HIGHLY UNLIKELY that OEM specific features will make it into AOSP based ROMs. If you want those features, you will more than likely need to stick with a stock based ROM.
---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------
All goodness. Working just fine now. Hopefully the battery life estimate I was seeing before the clean flash will carry forward. Said I'd be needing to recharge on JAN 17TH lol!
Click to expand...
Click to collapse
Really? Why is it that CM incorporated Dot View case from functionality into their M8 builds? Why did they work on hover events when the S4 came out? Why did they build an FM radio app for phones that had this feature built in?
gparmar76 said:
Really? Why is it that CM incorporated Dot View case from functionality into their M8 builds? Why did they work on hover events when the S4 came out? Why did they build an FM radio app for phones that had this feature built in?
Click to expand...
Click to collapse
"Highly unlikely"
And every aosp ROM utilizes lazer af
Sent from my Sump'd and Bump'd G3, Thanks to Team Codefire
Related
About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Gapps Downloads (Banks)
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Bugs
Same as CM11...
Thanks
Carbon Team
Cyanogenmod
Bbelos
Device-specific Changelog:
Code:
16-05-14:
- Ramdisk compression changes
- Fixes for google camera
19-04-14:
- 720p Video recording (and 480p fix)
- Fixed Camera tile preview
- Fixed Headphone button (for play/pause)
23-03-14:
- Fixed GPS and Bluetooth
- Touchscreen now works in recovery
- Misc improvements
07-03-14:
- Initial Release
Awesome! Thanks for building Carbon, you continue to do some great stuff here for the 4.0.
EDIT: I ran across three force closes, 2 of which are the same as CM11.
Like CM11, messaging force closes, so I deleted mms.apk and now it's all good. Also the same as CM11, settings/storage force closes on initial boot but after a reboot it's fixed.
One other force close I got was acore process has stopped. I've seen that one before on other roms/devices, it's fixed by clearing cache/data of contacts storage in apps.
Just finished setting up and restoring my apps with Titanium and overall this is running really well, smooth and feels pretty quick. Really nice work on this, thanks again.
Btw, camera front and back work fine, just as in CM.
Mike T
Awesome, I'll have to try it out when I get some time
Just curious, do you have any figures on how it compares with CM11 when it comes to RAM usage?
Zaclimon has done it again lol. BTW how's battery life compared to CM 11?
Sent from my YP-G1 using xda app-developers app
trainman261 said:
Awesome, I'll have to try it out when I get some time
Just curious, do you have any figures on how it compares with CM11 when it comes to RAM usage?
Click to expand...
Click to collapse
The general RAM usage is simillar to CM11. (about 165-180 MB)
obscuresword said:
Zaclimon has done it again lol. BTW how's battery life compared to CM 11?
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
I haven't played with it enough time to judge but it looks simillar (I would need to get ART running on it soon because I was trying to get down an issue related to hardware tunables...)
zaclimon said:
The general RAM usage is simillar to CM11. (about 165-180 MB)
I haven't played with it enough time to judge but it looks simillar (I would need to get ART running on it soon because I was trying to get down an issue related to hardware tunables...)
Click to expand...
Click to collapse
So don't use ART yet lol. Also does impulse work on this?
obscuresword said:
So don't use ART yet lol. Also does impulse work on this?
Click to expand...
Click to collapse
LOOL indeed. And no impulse doesn't work yet on it, I haven't updated impulse to work with it.
Envoyé de mon Nexus 7 en utilisant Tapatalk
zaclimon said:
LOOL indeed. And no impulse doesn't work yet on it, I haven't updated impulse to work with it.
Envoyé de mon Nexus 7 en utilisant Tapatalk
Click to expand...
Click to collapse
All right man. I installed it and it runs great. The only issue I ran into was that the setting forced closed, but I opened it back up and it ran fine. This has almost all the customization of PAC-rom, but runs much better. Now I have to find a way to mod the browser, because in Kitkat Google decided to remove some critical API's for flash. When you click on an video (for instance .mp4) the browser doesn't do the pop up that lets you select a video lol.
Does this Carbon ROM also work with YP-G70 The 5.0 version?
@zaclimon Holy cow that's good battery life. WiFi is on + being fully awake + no under clocking and it stl got 90% in an hour lol.
Sent from my YP-G1 using xda app-developers app
MRLARGE said:
Does this Carbon ROM also work with YP-G70 The 5.0 version?
Click to expand...
Click to collapse
Nope only with the 4.0. However I can build a 5.0 version if there's enough interest.
@obscuresword ohh I didn't expected that. That's nice!! I do have a little feeling that graphics performance is not as good as cm.
Envoyé de mon Nexus 7 en utilisant Tapatalk
Browser has that rendering problem again lol
Also this minor lockscreen glitch lol
Sent from my YP-G1 using xda app-developers app
Sent from my YP-G1 using xda app-developers app
I decided to take a plunge and upgrade from CM 10.02 (or something like that) and i can't believe how freakin amazing and professional this process and ROM's have become. Normally my upgrades and installs are plagued with teething issues (I literally have had to brute force a ROM once or twice) and painful bugs which have no easy workaround. This on the other hand was mindblowing.... I followed your CM 11 install instructions and it worked like the butter this system is made with no problems, easy and just superb.
As of yet i haven't found any bugs, the interface is smooth and honestly this has progressed so far since the times that it seemed we would never have a working camera/ anything.... I definitely suggest this to anyone that got a bit bored with CM (me, I could have upgraded to CM11 but this was something different).
Thankyou SO MUCH Zaclimon for another awesome ROM and I promise if i run into any unreported bugs I'll alert you happily! Thanks again!!!
Is There Anyway This Could Come To The YP-G70? The US Galaxy Player 5.0?
Sent from my YP-G70 using XDA Premium 4 mobile app
Bluetooth Problem
There appears to be a problem with bluetooth in CarbonRom that makes the player unable to connect to or even be found by other devices.
FlinderMouse said:
There appears to be a problem with bluetooth in CarbonRom that makes the player unable to connect to or even be found by other devices.
Click to expand...
Click to collapse
Yeah I'm aware of it, the same thing happens with CM at the moment. While making some internal changes, I've broken GPS and Bluetooth. Both should be fixed in the next build.
Envoyé de mon Nexus 7 en utilisant Tapatalk
Alright folks, new build released in my devhost folder.
23/03:
Fixed GPS and Bluetooth (broken earlier due to some internal changes I made)
Fixed vibrator intensity at boot
The touchscreen can now be used in recovery
There's now slim pie and the progress bar tweaks
Misc. improvements
Enjoy!!
zaclimon said:
Alright folks, new build released in my devhost folder.
23/03:
Fixed GPS and Bluetooth (broken earlier due to some internal changes I made)
Fixed vibrator intensity at boot
The touchscreen can now be used in recovery
There's now slim pie and the progress bar tweaks
Misc. improvements
Enjoy!!
Click to expand...
Click to collapse
Does Misc. improvements mean that ART can be used yet lol. Also are you on Spring Break yet?
As there doesn't seem to be a PA 5.1 Build thread and zero official builds around since the 02/02 I thought I would start up my old build machine and TRY to do daily builds of PA 5.1.1 for everyone.
IMPORTANT
I am not responsible if your phone blows up or turns into a gremlin after midnight.
If there are NO changes to gerrit there will be no updates to the OP
For anyone coming from 5.0.x to 5.1.x please refer to the thread below for bootloader etc.
http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
Please read before asking any questions.
Any issues do a FACTORY RESET and CLEAN INSTALL
I am NOT a dev just a guy doing builds of PA so any requests for code changes or cherry picking will be ignored
GAPPS
http://forum.xda-developers.com/android/general/gapps-lp-gapps-pa-gapps-aroma-installer-t3010798
SOURCE
All source code is taken directly from PA with zero modifications.
https://github.com/AOSPA-L (Legacy Builds for Shamu based on CM 12.x)
https://github.com/AOSPA (AOSP Builds for Shamu)
KERNEL SOURCE
https://android.googlesource.com/device/moto/shamu-kernel/
AOSP BUILDS (01/09)
https://www.androidfilehost.com/?fid=24052804347805815
Definitely gonna try this! Thanks
I'm in
Any new features? Last time I tried it there was only themer
dex2grigg said:
Any new features? Last time I tried it there was only themer
Click to expand...
Click to collapse
It's pretty much stock with themes right now with very few features compared to other roms.
GREAT!
Hell yeah!! I'm in too!
Not knocking your efforts but PA updates things like once a week, what's the point of daily builds?
akellar said:
Not knocking your efforts but PA updates things like once a week, what's the point of daily builds?
Click to expand...
Click to collapse
if u read topic u can see that say paranoid is not update rom from 02/02
akellar said:
Not knocking your efforts but PA updates things like once a week, what's the point of daily builds?
Click to expand...
Click to collapse
thats not necessarily true. I had a few devices when the updates only came every other month. It really depends on the maintainers and the developers for said devices.
pornogeroc said:
if u read topic u can see that say paranoid is not update rom from 02/02
Click to expand...
Click to collapse
the_rooter said:
thats not necessarily true. I had a few devices when the updates only came every other month. It really depends on the maintainers and the developers for said devices.
Click to expand...
Click to collapse
I'm referring to github not how often they push builds. For example, there has been very little activity since the middle of February. Building daily is going to result in the exact same rom 4 or 5 days a week.
akellar said:
I'm referring to github not how often they push builds. For example, there has been very little activity since the middle of February. Building daily is going to result in the exact same rom 4 or 5 days a week.
Click to expand...
Click to collapse
If you took the time to read the OP I stated "If there are NO changes to gerrit I will update this thread accordingly."
This means if there are no changes I won't be doing any builds and will state this on the OP so people know.
daleski75 said:
If you took the time to read the OP I stated "If there are NO changes to gerrit I will update this thread accordingly."
This means if there are no changes I won't be doing any builds and will state this on the OP so people know.
Click to expand...
Click to collapse
I did read the OP. And I also read the thread title. I was in no way rude to you so I am unsure why you feel the need to be a jerk but carry on.
akellar said:
I did read the OP. And I also read the thread title. I was in no way rude to you so I am unsure why you feel the need to be a jerk but carry on.
Click to expand...
Click to collapse
Sorry if I came across a jerk and I have amended the thread title so people won't expect daily builds.
The curse of any PA thread, people whining and complaining @daleski75 thank you for bringing PA to shamu
i dnt care if its daily, weekly, monthly or yearly lolll...happy to see pa for nexus 6.
i still have pa on my note2.
before I can't life without CM but now I hate CM don't ask me why
now really can't life without PA I like it so much any very sad cuz no update from 2/2
now I'm very happy to see PA back to life again
Sent from my Nexus 6 using Tapatalk
PA is gonna die a slow death I think because most of the brain trust is gone to the other OS.. At least the other one will probably get the best features. They are getting ready to release the first version of there operating system on the one plus and all this is really is a mildly improved version of aosp without any paranoid features. Kind of sad for all their rabid PA or die followers. Finaly get a phone that runs PA and development grinds to a halt.
---------- Post added at 08:52 PM ---------- Previous post was at 08:50 PM ----------
akellar said:
I did read the OP. And I also read the thread title. I was in no way rude to you so I am unsure why you feel the need to be a jerk but carry on.
Click to expand...
Click to collapse
I see what your saying. Since the PA creative team left the building PA development has grinded to a halt.
gamewarden234 said:
PA is gonna die a slow death I think because most of the brain trust is gone to the other OS.. At least the other one will probably get the best features. They are getting ready to release the first version of there operating system on the one plus and all this is really is a mildly improved version of aosp without any paranoid features. Kind of sad for all their rabid PA or die followers. Finaly get a phone that runs PA and development grinds to a halt.
---------- Post added at 08:52 PM ---------- Previous post was at 08:50 PM ----------
I see what your saying. Since the PA creative team left the building PA development has grinded to a halt.
Click to expand...
Click to collapse
says who? you? they have already answered this, the 6 members going to ONE+ is no different than them having jobs in the US while working with PA. Stop spreading this fud people, PA is not going away. The team has been getting hounded left and right and is really discouraged because people are so upset a rom isn't being pushed out daily/weekly/whatever they want. Development is continuous, look at their gerrit and youll see daily they are working on stuff but everyone is busy with life. Pirate just started a new job. Andre goes to school and has a life, you guys just need to relax a little. Ill repeat this again for the special kids on this forum, no one has left PA, again NO ONE HAS LEFT PA.
---------- Post added at 01:22 PM ---------- Previous post was at 01:17 PM ----------
akellar said:
I'm referring to github not how often they push builds. For example, there has been very little activity since the middle of February. Building daily is going to result in the exact same rom 4 or 5 days a week.
Click to expand...
Click to collapse
you are very wrong, look at gerrit there are changes made DAILY and if they aren't made daily its every few. You are looking at github wrong if you are seeing changes only from middle of feb. If you are going to try and jump down someones throat at least understand what you are looking at.
Circaflex said:
you are very wrong, look at gerrit there are changes made DAILY and if they aren't made daily its every few. You are looking at github wrong if you are seeing changes only from middle of feb. If you are going to try and jump down someones throat at least understand what you are looking at.
Click to expand...
Click to collapse
First off, the conversation was over. Stop trying to be the internet white knight. I didn't jump down anybody's throat.
2nd off, there have been 19 commits merged since Feb 19th and almost all have been theme related cherry picks from CM. If you're going to attempt to call someone out you should probably make sure that person is wrong.
Sorry OP, I will not be responding to the XDA kiddies in your thread anymore. I wish you luck with your rom.
akellar said:
First off, the conversation was over. Stop trying to be the internet white knight. I didn't jump down anybody's throat.
2nd off, there have been 19 commits merged since Feb 19th and almost all have been theme related cherry picks from CM. If you're going to attempt to call someone out you should probably make sure that person is wrong.
Sorry OP, I will not be responding to the XDA kiddies in your thread anymore. I wish you luck with your rom.
Click to expand...
Click to collapse
19 commits shows development is still going, whether its 1 or 2, its still work being done. You said they only seem to update things once a week, which is again wrong if you look at their gerrit. You guys make it seem like they are doing nothing and not updating. Hopefully all these children move to different roms so we can enjoy PA
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?
SlimRoms is a custom android operating system. Our main goal is to offer users a slimmed down yet feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by our public Gerrit to submit patches of any type.
Slim6 is the project name for SlimRoms based on Android 6.0.1 Marshmallow and offers the following original features:
Slim Navbar & Hardware key rebinding
Single tap action, long press action, double tap action!-We’ve got you covered.
Slim Actions & Chamber of secrets
Customise your device to the fullest -You’re a wizard!
SlimRecents
A Faster alternative to stock recents -Your device, your choice.
SlimLauncher
An Open source, feature filled launcher! -Make yourself at home
Status bar customisations
Clock and Date? Battery? -More fun than you can shake a stick at.
Important links:
slimroms.org - Our official website and your source for anything SlimRoms related.
Downloads - Slimify your device!
Installation instructions - Follow these steps if you want SlimRoms on your device.
FAQ - Have a question? Consider reading our FAQ first, you might find your answer there!.
Report-bugs - Found a bug? Send it our way!
Kernel Source - The source of your device's kernel.
Get in touch! - You can contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Disclaimer: We are not responsible for any damages to your device.
XDA:DevDB Information
[Slim6] SlimRoms Nexus 6, ROM for the Nexus 6
Contributors
Yank555, prbassplayer, dankoman
Source Code: https://github.com/SlimRoms/kernel_moto_shamu
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Alpha
Created 2016-06-17
Last Updated 2016-10-11
XDA:DevDB Information
[Shamu][official][2016/OCT/07] Slim6 weekly 1.6, ROM for the Nexus 6
Contributors
Perseus
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2016-10-12
Last Updated 2016-10-12
Reserved 1
Reserved 2
and there is slim... congrats.. shamu born again
Any known bugs yet? Always been a fan of slim.
Sent from my Nexus 6 using Tapatalk
warfenix said:
Any known bugs yet? Always been a fan of slim.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
See for yourself. Make a backup and run it through its paces.
Sent from my Nexus 6 using XDA-Developers mobile app
Glad to see Slim coming back to the scene. It was always a great project on hammerhead and mako back in the day. Can't wait to see what you have in store.
reyscott said:
and there is slim... congrats.. shamu born again
Click to expand...
Click to collapse
Yep. All due to Yank! Thanks Bro. Yet, Yank's YAOSP is my daily d on several devices. Flawless work on that ROM. Can't wait for Slim to equal.
Sent from my Nexus 6 using XDA Free mobile app
I'm in... Such an awesome ROM. Thanks!
Apn is still janky for vzw. Alex from tipsy got the issue fixed for tipsy, but he has no idea what fixed it as he was doing multiple things at once.
Doesn't do anything to help the fact but it can be fixed somehow so is hope.
Lawlrus said:
Apn is still janky for vzw. Alex from tipsy got the issue fixed for tipsy, but he has no idea what fixed it as he was doing multiple things at once.
Doesn't do anything to help the fact but it can be fixed somehow so is hope.
Click to expand...
Click to collapse
Can you be more specific on the issue, what exactly happens ?
Thx, JP.
Sent from my Nexus 6P using XDA Labs
@Yank555 , any plans for one of your great kernels for this Rom ?
Yank555 said:
Can you be more specific on the issue, what exactly happens ?
Thx, JP.
Click to expand...
Click to collapse
May not help, but I'm in a really low signal area myself. Mine jumps around on roaming a lot. I've never seen that before on any phone at my home plus I thought there wasn't any real "roaming" on Verizon.
fares70 said:
@Yank555 , any plans for one of your great kernels for this Rom ?
Click to expand...
Click to collapse
Have you checked the kernel ? It's already in there, full blown
JP.
Sent from my Nexus 6P using XDA Labs
bond32 said:
May not help, but I'm in a really low signal area myself. Mine jumps around on roaming a lot. I've never seen that before on any phone at my home plus I thought there wasn't any real "roaming" on Verizon.
Click to expand...
Click to collapse
Ok, roaming on Verizon is sth I've heard of ...
JP.
Sent from my Nexus 6P using XDA Labs
Yank555 said:
Have you checked the kernel ? It's already in there, full blown
JP.
Click to expand...
Click to collapse
Perfect ! Did not know because i havent flashed it now , but will do when download finished . Thank you !
Yank555 said:
Can you be more specific on the issue, what exactly happens ?
Thx, JP.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
As soon as the ROM boots up it shows LTE for a couple seconds then shows roaming.
You can go into networks settings and change preferred network to LTE and it will switch over to lte but then the APN gets borked and you can't send SMS.
I tried switching it to Verizon internet, which is the proper APN, go to send a text and it boots it back to the top listed APN which won't send texts. I tried to delete the additional apns but that ended up leaving no signal at all when I tried to manually add the proper one
---------- Post added at 04:06 PM ---------- Previous post was at 04:03 PM ----------
bond32 said:
May not help, but I'm in a really low signal area myself. Mine jumps around on roaming a lot. I've never seen that before on any phone at my home plus I thought there wasn't any real "roaming" on Verizon.
Click to expand...
Click to collapse
Oh there really is a roaming, but this isn't making it roam, the idea of seeing it is cosmetic, but after testing it for a few days (different ROMs obviously) it seems like it does make the radio over work itself where it normally wouldn't.
Lawlrus said:
As soon as the ROM boots up it shows LTE for a couple seconds then shows roaming.
You can go into networks settings and change preferred network to LTE and it will switch over to lte but then the APN gets borked and you can't send SMS.
I tried switching it to Verizon internet, which is the proper APN, go to send a text and it boots it back to the top listed APN which won't send texts. I tried to delete the additional apns but that ended up leaving no signal at all when I tried to manually add the proper one
---------- Post added at 04:06 PM ---------- Previous post was at 04:03 PM ----------
Oh there really is a roaming, but this isn't making it roam, the idea of seeing it is cosmetic, but after testing it for a few days (different ROMs obviously) it seems like it does make the radio over work itself where it normally wouldn't.
Click to expand...
Click to collapse
I see, I figured the radio would overwork anyway in my area. For example, my Note 4 will constantly jump from 1x to 3g then to nothing, many times.
Kinda why the MM update for the Note 4 was awesome, because it allowed WiFi calling. I digress...
Doubt it will help but I'll provide a log if needed. I'll be happy to test anything too.
bond32 said:
I see, I figured the radio would overwork anyway in my area. For example, my Note 4 will constantly jump from 1x to 3g then to nothing, many times.
Kinda why the MM update for the Note 4 was awesome, because it allowed WiFi calling. I digress...
Doubt it will help but I'll provide a log if needed. I'll be happy to test anything too.
Click to expand...
Click to collapse
I have Alex a modem log when he was looking into it but it didn't come up with much I don't think. If yank wants one I can reflash and get one too.
It only seems to be an issue with vzw too, sprint also uses CDMA, but it doesn't seem to have the issue. That's why I'm thinking its linked to the APN slim six is using versus the CDMA type itself.
I'm sure yank will get it squared away, will more than likely just take a few builds, that is as long as he's willing / can look into it
Lawlrus said:
I have Alex a modem log when he was looking into it but it didn't come up with much I don't think. If yank wants one I can reflash and get one too.
It only seems to be an issue with vzw too, sprint also uses CDMA, but it doesn't seem to have the issue. That's why I'm thinking its linked to the APN slim six is using versus the CDMA type itself.
I'm sure yank will get it squared away, will more than likely just take a few builds, that is as long as he's willing / can look into it
Click to expand...
Click to collapse
Yep, I agree it can't be much. Also it's cosmetic from what I gathered, it doesn't consider the current network as "home" network, hence shows the roaming "R"...
Will be addressed, hope it's not much.
JP.
DISCLAIMER
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Unofficial LineageOS 14.1 builds for the Samsung Galaxy S5 Sport (SM-G860P)
What works:
SIM aka RIL
Mobile Data and Hotspot
Audio
SMS and Phone calls
Everything else that should work
What doesn't work:
NFC
Bugs you find!
TWRP can be downloaded here and flashed via Odin if you are starting from stock https://www.androidfilehost.com/?fid=457095661767152528
All other downloads are available from the Downloads tab of this thread!
XDA:DevDB Information
LineageOS 14.1 for SM-G860P Galaxy S5 Sport, ROM for the Sprint Samsung Galaxy S5
Contributors
SJR (Sam), evilarceus, javelinanddart
Source Code: https://www.github.com/kltesprsportsdev
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Stable
Created 2017-09-23
Last Updated 2017-11-30
Reserved
Builds are UP!!
Latest build is from 11-30-17 in the Downloads section
-flash from clean along with the new TWRP
Bug list and To-Do
*NFC does not work
*Flashlight and Camera don't work from notification bar
To-Do
Make a build with OMS (Substratum) Support
Looking forward to this!
Might seem like a rude question but have any idea on ETA?
FanboyStudios said:
Might seem like a rude question but have any idea on ETA?
Click to expand...
Click to collapse
Yes, sorry, have been busy, I'll post a build from Very late August as currently I have issues with building that I need help resolving. Mainly because LineageOS moved to new kernel configs for the regular S5 and so I need to modify one in with the Sport stuff...
Also I currently took my dad's S5 Sport back to stock so I cannot test myself at the moment. If anyone has a spare S5 Sport for testing, I'd gladly take it to finish this ROM and make it official
Sam
SJR (Sam) said:
Yes, sorry, have been busy, I'll post a build from Very late August as currently I have issues with building that I need help resolving. Mainly because LineageOS moved to new kernel configs for the regular S5 and so I need to modify one in with the Sport stuff...
Also I currently took my dad's S5 Sport back to stock so I cannot test myself at the moment. If anyone has a spare S5 Sport for testing, I'd gladly take it to finish this ROM and make it official
Sam
Click to expand...
Click to collapse
No need to apologise, I appreciate what you're doing and I understand it takes some time.
If you need another S5 Sport, you can get one here https://m.ebay.com/itm?itemId=112560349301&fdback=1
I bought mine from the same seller, no issues. It even arrived days early!
FanboyStudios said:
No need to apologise, I appreciate what you're doing and I understand it takes some time.
If you need another S5 Sport, you can get one here https://m.ebay.com/itm?itemId=112560349301&fdback=1
I bought mine from the same seller, no issues. It even arrived days early!
Click to expand...
Click to collapse
Nice! My father is considering a new phone here so I'll probably hold out for a bit of time and see if that happens. If not, I'll try and scrape some extra money together for another phone... I have a few to many because of other projects, AKA Android 4 Lumia so I have like 7 windows phones
Anyway, I'll get that build posted tonight and update the OP
SJR (Sam) said:
Nice! My father is considering a new phone here so I'll probably hold out for a bit of time and see if that happens. If not, I'll try and scrape some extra money together for another phone... I have a few to many because of other projects, AKA Android 4 Lumia so I have like 7 windows phones
Anyway, I'll get that build posted tonight and update the OP
Click to expand...
Click to collapse
Alright great? Is there any issues with that build that i should know about?
FanboyStudios said:
Alright great? Is there any issues with that build that i should know about?
Click to expand...
Click to collapse
NFC does not work, everything else seems good
build is up!
Substratum OMS Overlay Support?
SJR (Sam) said:
NFC does not work, everything else seems good
build is up!
Click to expand...
Click to collapse
It would be great if you could add Substratum support. I just flashed a CM14 build and Substratum in Legacy Mode left me with a bootloop.
Link below may provide some info on how you can do this...
https://forum.xda-developers.com/apps/substratum/reference-lineageos-substratum-support-t3580276
FanboyStudios said:
It would be great if you could add Substratum support. I just flashed a CM14 build and Substratum in Legacy Mode left me with a bootloop.
Link below may provide some info on how you can do this...
https://forum.xda-developers.com/apps/substratum/reference-lineageos-substratum-support-t3580276
Click to expand...
Click to collapse
Sorry about that mate! I should update the OP to mention this for now. I'll try my best to add support but right now I need to make the trees build able again with a new kernel defconfig. The current build is good in everything else?
SJR (Sam) said:
Sorry about that mate! I should update the OP to mention this for now. I'll try my best to add support but right now I need to make the trees build able again with a new kernel defconfig. The current build is good in everything else?
Click to expand...
Click to collapse
Don't know quite yet... I flashed cm13 for the time being from an older thread.. I'm a hardcore themer... Everything i have is themed. It's nice to have device info on my desktop with my channel branding.
FanboyStudios said:
Don't know quite yet... I flashed cm13 for the time being from an older thread.. I'm a hardcore themer... Everything i have is themed. It's nice to have device info on my desktop with my channel branding.
Click to expand...
Click to collapse
I personally just go with a Stock Google AOSP look myself, dose not match my YouTube
SJR (Sam) said:
I personally just go with a Stock Google AOSP look myself, dose not match my YouTube
Click to expand...
Click to collapse
To me the biggest issue is the white background though... and since this phone has a AMOLED screen well the benefits of a black theme to me are higher... 1 Eats less battery (turns pixels off), 2 Easier on the eyes, especially in dark places, 3 to me it just looks cool.
FanboyStudios said:
To me the biggest issue is the white background though... and since this phone has a AMOLED screen well the benefits of a black theme to me are higher... 1 Eats less battery (turns pixels off), 2 Easier on the eyes, especially in dark places, 3 to me it just looks cool.
Click to expand...
Click to collapse
Yeah, I know what you mean. Nougat got better with the black interface but Oreo went to white so yeah...
SJR (Sam) said:
Yeah, I know what you mean. Nougat got better with the black interface but Oreo went to white so yeah...
Click to expand...
Click to collapse
I've decided to put up with default theme for a while... CM13 build from other thread was too buggy.
Camera and Flashlight from the pull down notification bar don't work. Got a Substratum Theme to function in Legacy Mode, but it had some bugs.
The built-in root is adb only. I have the file to enable apps you may want to share it. I'll upload it here sometime, also will give you a logcat..
Also I got ViPER Audio working with the IO fix.. Had to set SELinux Permissive to install the drivers.
And lastly, Changing the GPU Governor in Kernel Auduitor causes a reboot.
Here is a zipped Logcat, Bug report, and the SU Addon to add root access for apps.
SU Addon gets flashed in TWRP.
If anyone needs root, then you can find it on the Extras tab of the LineageOS downloads page. I'll try to work on the phone today but my knowledge is not very good still
SJR (Sam) said:
If anyone needs root, then you can find it on the Extras tab of the LineageOS downloads page. I'll try to work on the phone today but my knowledge is not very good still
Click to expand...
Click to collapse
The root I uploaded works just fine, i haven't ran into any issues.