Related
I've been running Jelly'Beans' ROM 1 through 22 since I've had my Note 2. Really have no complaints about it at all. But since he is getting ready to release his version of 4.3 soon, I started getting curious about the 4.4 ROM's. There are so many threads, and I'd just like to get some opinions from more experienced users since I have been strictly on Beans. What do people think are the most stable 4.4 ROM's? How many are out? I can't tell from all the threads titles, unless they specifically say 4.4 in them. I've only noticed the SlimRom one, but haven't spent a lot of time looking. What kernels are available, and overclockable? Do you use the same modems as in 4.1.2, I assume you would? What's the difference between 4.3 and 4.4? The one thing I like about Bean's ROM is it is based off the official Verizon release, and he does a great job in his work. I'm more reserved on just flashing myself ever since I've seen people talk about having to flash "downgrades" and other things to go back to 4.1.2 if you don't like the other ones. If it was as simple as flashing your TWRP backup I would. But I believe you can't use that in 4.3 or 4.4 either, if I read correctly. Any input or opinions is great. I don't need to get flamed or told to Google things. If you don't wanna answer don't. If you want to take a minute or two to state your opinions, great. I'm just curious about all this. This is an Q&A Help thread. Thanks.
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?
So I'll just pick one at random then? Thanks for the help...
There is a thread with links to all the stock firmware releases. But downgrading has been debated if its even possible. The procedure is detailed in a couple different posts from what I've read. I doubt you will be able to run a kk ROM with the a LL bootloader and modem.
Sent from my SM-G900T
There are still Cyanogenmod 11 (KitKat) builds in the unified development section, that's probably your best bet. As mgp53 pointed out it's difficult if not downright impossible to downgrade android versions using the official firmware, if you're already on 5.1.1
thisisapoorusernamechoice said:
There are still Cyanogenmod 11 (KitKat) builds in the unified development section, that's probably your best bet. As mgp53 pointed out it's difficult if not downright impossible to downgrade android versions using the official firmware, if you're already on 5.1.1
Click to expand...
Click to collapse
Thanks so much! I am pouring through it now... might take a bit since I don't see a column for version number http://forum.xda-developers.com/galaxy-s5/unified-development#romList but I'll just sort by latest release and click on every single link manually till I see a 4.x that isn't a buggy PoS. I was originally hoping to steer clear of AOSP/CM because I heard the battery life isn't as good as TW or "superslim" style stripped-down stock fws, but at this point I will take what I can get. I've had terrible luck getting any kind of answers across multiple subforums on this site. Your post was the most useful by far. Thanks again.
Incoming rant...
It really is a shame that 1) the download links on the 600+ Infinity ROM thread are all dead, 2) SlimROM doesn't seem to exist in any meanful/useable state for the s5 even though they have tons of devices including the s3/s4, 3) Sick n Twi5ted for 4.x is a buggy PoS, 4) Liquidsmooth has major missing features such as no camera (You thought releasing a ROM on a 16megapixel flagship device with no camera function was OK enough to start asking for donations and then never got around to adding support for the camera? At least have the decency to put a list of major bugs and missing features in the OP. It is debateably fraudulent to put a donate button where the 'Major Issues' section should be and then not even have a disclaimer.
Users of this site really ought not to have to pour through 60-600 pages to find out major flaws on a ROM. In all the dozens of threads I've sifted through over the past week there was exactly ONE who was up front and honest including a section devoted to missing features/major bugs.
/end_rant
On the bright side, all this madness had led me to seriously consider developing my own ROM and that would probably be a good thing for me in general to learn anyway. Or alternatively I could create a website devoted to archiving older ROMs since there seems to be quite a few that have gone missing here. (think oldversion.com circa 2005)
Whatever I decide to contribute, there certainly is room for a lot of it here.
android6 greatly improved idle battery life, plus you can underclock the cpu if you have root
I downgraded from 47A to 10B via TOT, then used StumpRoot and installed TWRP. Then I booted to TWRP and installed the 35B bootstack, along with CM13 and an open gapps package.
It seems that literally everything else is working fine; I can receive sms/mms, I can make and receive calls, I have mobile data.
But I just cannot send a text message. My Preferred Network Type is set to Global, and I am using the VZWInternet APN.
I have searched google and these forums but have not found a solution. I have also tried clearing the caches and using the DirtyUnicorn rom as an alternative.
Does anyone have any suggestions as to how to get this working?
EDIT: it seems that making a phonecall does something and then my texts will send. Googling around turned up nothing of use.
There are often issues on non-stock ROMs. Sometimes there's a nightly build that works reasonably well and then another later that breaks things again.
It takes a year/a year and a half minimum for any new version of CM to become kinda sorta stable. Until then it's a constant work in progress.
If you read the last posts in the CM13 thread you'll see you're not alone with issues. I've stuck with VS985 stock based ROMs for a year.
Note that sometimes when users flash either a non-stock ROM or an international-based stock ROM, sometimes they had trouble getting things working right again even when they flash a stock based ROM until they flashed the TOT again and start fresh.
roirraW "edor" ehT said:
There are often issues on non-stock ROMs. Sometimes there's a nightly build that works reasonably well and then another later that breaks things again.
It takes a year/a year and a half minimum for any new version of CM to become kinda sorta stable. Until then it's a constant work in progress.
If you read the last posts in the CM13 thread you'll see you're not alone with issues. I've stuck with VS985 stock based ROMs for a year.
Note that sometimes when users flash either a non-stock ROM or an international-based stock ROM, sometimes they had trouble getting things working right again even when they flash a stock based ROM until they flashed the TOT again and start fresh.
Click to expand...
Click to collapse
Thanks again for the reply. I did notice some people having data issues on some of the later nightlies, but didn't see any reports of sms issues so I thought I might be safe lol.
I'll probably try flashing the 10B tot again then using a stock based rom like you suggested (even though I'm not a fan of LG's ui).
Do you have any recommendations on a stock-based rom to flash? I noticed that in the 47a stock thread you posted about debloating, do you just use a debloated version of 47a? or do you go with some of the other stock based ones with maybe some more features?
inexplicability said:
Thanks again for the reply. I did notice some people having data issues on some of the later nightlies, but didn't see any reports of sms issues so I thought I might be safe lol.
I'll probably try flashing the 10B tot again then using a stock based rom like you suggested (even though I'm not a fan of LG's ui).
Do you have any recommendations on a stock-based rom to flash? I noticed that in the 47a stock thread you posted about debloating, do you just use a debloated version of 47a? or do you go with some of the other stock based ones with maybe some more features?
Click to expand...
Click to collapse
You're welcome!
Both of @xdabbeb 's ROMs are excellent. His 35B (5.1.1) based VS985 v2.0 ROM is awesome, and he took a lot of care and effort in making it. His stock rooted 47A firmware is as stock 47A as you can be while being rooted and able to get into TWRP. In the third post of the 47A thread (and in my signature below) I have a link to my debloat zips post, and also a link to @joshua70448 's really cool online customized debloat zip generator, so you can make your own debloat zip that does exactly what you want.
I flash my "All" debloat zip and for most others I recommend the "No OTA" debloat zip. 47A is just very slightly even smoother than 35B, although it has some idiosyncrasies with USB OTG access (I have to navigate to root/mnt or root/storage - I forget which, to access it in X-plore File Manager), and I consider Xposed and several modules a must. Just use the search field in the 47A thread and type in Xposed and you should find the most important info if you need it. Greenify's aggressive doze feature is helpful, too. When I've hardly touched my phone over a holiday weekend, I've truely gotten, twice no less, 120 hours on battery between charges, but this includes less than an hour screen on time, and just staying home where the signal is consistent, so don't expect that while actually using the phone.
I've been using his 47A debloated since it came out.
roirraW "edor" ehT said:
You're welcome!
Both of @xdabbeb 's ROMs are excellent. His 35B (5.1.1) based VS985 v2.0 ROM is awesome, and he took a lot of care and effort in making it. His stock rooted 47A firmware is as stock 47A as you can be while being rooted and able to get into TWRP. In the third post of the 47A thread (and in my signature below) I have a link to my debloat zips post, and also a link to @joshua70448 's really cool online customized debloat zip generator, so you can make your own debloat zip that does exactly what you want.
I flash my "All" debloat zip and for most others I recommend the "No OTA" debloat zip. 47A is just very slightly even smoother than 35B, although it has some idiosyncrasies with USB OTG access (I have to navigate to root/mnt or root/storage - I forget which, to access it in X-plore File Manager), and I consider Xposed and several modules a must. Just use the search field in the 47A thread and type in Xposed and you should find the most important info if you need it. Greenify's aggressive doze feature is helpful, too. When I've hardly touched my phone over a holiday weekend, I've truely gotten, twice no less, 120 hours on battery between charges, but this includes less than an hour screen on time, and just staying home where the signal is consistent, so don't expect that while actually using the phone.
I've been using his 47A debloated since it came out.
Click to expand...
Click to collapse
Nice, I'll look into what you're saying while I'm at work and then work on it when I get home. And holy crap 120 hours?!? On the HTC One m7 I'm coming from I could maybe get 1/10 of that (very low usage with data off and battery save on), so your 120 sounds like a made up number to me haha.
On a slightly unrelated note, and I'm not sure if you would have an answer to this, but do you have any suggestions on how to get into some more in depth android development? (kernels/bootstacks/roms etc) I believe I have the necessary skills to do so, just never really found a good entry point.
Really though, I know you probably enjoy helping people, but I want you to know that its really helpful having someone reply quickly with great answers.
inexplicability said:
Nice, I'll look into what you're saying while I'm at work and then work on it when I get home. And holy crap 120 hours?!? On the HTC One m7 I'm coming from I could maybe get 1/10 of that (very low usage with data off and battery save on), so your 120 sounds like a made up number to me haha.
On a slightly unrelated note, and I'm not sure if you would have an answer to this, but do you have any suggestions on how to get into some more in depth android development? (kernels/bootstacks/roms etc) I believe I have the necessary skills to do so, just never really found a good entry point.
Really though, I know you probably enjoy helping people, but I want you to know that its really helpful having someone reply quickly with great answers.
Click to expand...
Click to collapse
I know I took screenshots of my battery life the 2-3 times I had 100 or more hours, but I don't know for sure if I uploaded those particular screenshots although I know I commented about my success. I'm very sure I uploaded screenshots to the VS985 v2.0 thread when i was on that ROM, although might not have been quite as extreme as on Marshmallow. 100+ hours is easy with aggressive doze and not travelling/not touching your phone hardly at all.
Are you familiar with Linux? If not, start there since it makes real development easier or is necessary for some aspects. I've just barely scraped the surface - I've just recently made a version of my LG G Pad 8.3 stock ROM that has busybox and SuperSU "baked" in based on @xdabbeb 's examples with his permission. Baking those in and having made the 3MinitBatteryMod for the Sprint Galaxy S3 in the past are the extend of anything approaching real developing I've done, but still not really. Making the stock tablet ROM wasn't really developing - I just followed other's examples and the only thing I modified was a text file.
Open a stock ROM zip of @xdabbeb 's and look at the contents. Look at the updater-script and clean.sh (just text files) in the two subfolders. Open them with the free NotePad++ if you're on Windows to get them to display correctly.
I've fooled mostly with Ubuntu and a little of BBQLinux distributions of Linux for some Android work. BBQLinux is more geared towards Android developing but I'm really not experienced enough to suggest one Linux over another.
Every once in a while I play around with the idea of doing some real developing. I have to considerations I'm keeping in mind: 1. It may be easier to start with something that's already been developed, and try to re-create it as in that case there's already a working reference, such as compiling TWRP or CM13 for the VS985. Once I'm successful doing that, the experience would help me develop for another device. 2. I don't want to actually publish anything that just duplicates what everyone else is doing - there's enough of that in my opinion, so in the end, my aim would be to develop for my LG G Pad 8.3 VK810, since there's at least been *some* development in the past for it, but there's no active or at least public development going on for it currently, and I have particular desires to make the tablet work better that could be addressed by developing.
Thank you and you're welcome! I do enjoy helping people and I get the most out of it when someone has been able to do whatever it is they were trying to do. I've learned from a bunch of helpful people on here and enjoy paying it forward.
roirraW "edor" ehT said:
Are you familiar with Linux? If not, start there since it makes real development easier or is necessary for some aspects. I've just barely scraped the surface - I've just recently made a version of my LG G Pad 8.3 stock ROM that has busybox and SuperSU "baked" in based on @xdabbeb 's examples with his permission. Baking those in and having made the 3MinitBatteryMod for the Sprint Galaxy S3 in the past are the extend of anything approaching real developing I've done, but still not really. Making the stock tablet ROM wasn't really developing - I just followed other's examples and the only thing I modified was a text file.
Open a stock ROM zip of @xdabbeb 's and look at the contents. Look at the updater-script and clean.sh (just text files) in the two subfolders. Open them with the free NotePad++ if you're on Windows to get them to display correctly.
I've fooled mostly with Ubuntu and a little of BBQLinux distributions of Linux for some Android work. BBQLinux is more geared towards Android developing but I'm really not experienced enough to suggest one Linux over another.
Every once in a while I play around with the idea of doing some real developing. I have to considerations I'm keeping in mind: 1. It may be easier to start with something that's already been developed, and try to re-create it as in that case there's already a working reference, such as compiling TWRP or CM13 for the VS985. Once I'm successful doing that, the experience would help me develop for another device. 2. I don't want to actually publish anything that just duplicates what everyone else is doing - there's enough of that in my opinion, so in the end, my aim would be to develop for my LG G Pad 8.3 VK810, since there's at least been *some* development in the past for it, but there's no active or at least public development going on for it currently, and I have particular desires to make the tablet work better that could be addressed by developing.
Click to expand...
Click to collapse
I've actually spent the summer learning unix, so maybe this'll motivate me to actually put that to use haha.
Android developing is really the only thing I wanted to use linux for anyway so maybe bbqlinux is a good option.
Compiling cm13 would definitely be a good start, and I'm sure there are plenty of ways to make personal modifications to it. I guess mainly I want to do the same things as you lol, go where other devs have left or just do things for personal use.
Thanks again for all your help!
I suggest you use an aosp based ROM. Options include Tesla, Tipsy, XenonHD, BrokenOS or Exodus. All very stable options. If you want to build I would suggest linux mint. Ubuntu base, very smooth, lots of support. You can follow this guide to get it set up: https://github.com/PAC-ROM/android_vendor_pac/blob/pac-6.0/docs/PrepareForBuildLinux.md
It is made for PAC, but it is working for the ROM I am currently developing.
Hey guys I was wondering is there any upcoming Oreo roms coming to the G5? Because I was snooping through the G3 forums and found a OREO rom for the G3 not 100% working but they have a rom on there so anything upcoming to the G5 guys? I know it sounds very very demanding but im really excited to use this new update or a new rom to the G5
ZuneYT said:
Hey guys I was wondering is there any upcoming Oreo roms coming to the G5? Because I was snooping through the G3 forums and found a OREO rom for the G3 not 100% working but they have a rom on there so anything upcoming to the G5 guys? I know it sounds very very demanding but im really excited to use this new update or a new rom to the G5
Click to expand...
Click to collapse
No doubt oreo roms are coming up and since I also developed some roms I am 100% sure some oreo custom roms already exists but are disclosed for the developer himself to test and fix the issue. As you might know devs don't like to give users very experimental stuff. But you might have seen the oreo changes under the hood as one of the big things: Project Treble. (See this link for more without having to dig in google itself https://arstechnica.com/gadgets/2017/09/android-8-0-oreo-thoroughly-reviewed/2/#h1 So other devices also have issues like bluetooth, camera and so on not working but I'm sure official oreo roms will come out within a period of 1-2 months as some phones already almost have fixed all oreo bugs like the HTC M10. Don't want to wait? Compile it yourself and contribute to the community if some devs aren't working on it already due to their lives/families I don't know whether LG G5 will reach oreo despite its age we all know how good manufacturer can be look at oneplus their software support for the oneplus 2 for instance. And the LG G5 is officially supported by LineageOS 15.0 if I'm correct. So just a little more patients
wulsic said:
No doubt oreo roms are coming up and since I also developed some roms I am 100% sure some oreo custom roms already exists but are disclosed for the developer himself to test and fix the issue. As you might know devs don't like to give users very experimental stuff. But you might have seen the oreo changes under the hood as one of the big things: Project Treble. (See this link for more without having to dig in google itself https://arstechnica.com/gadgets/2017/09/android-8-0-oreo-thoroughly-reviewed/2/#h1 So other devices also have issues like bluetooth, camera and so on not working but I'm sure official oreo roms will come out within a period of 1-2 months as some phones already almost have fixed all oreo bugs like the HTC M10. Don't want to wait? Compile it yourself and contribute to the community if some devs aren't working on it already due to their lives/families I don't know whether LG G5 will reach oreo despite its age we all know how good manufacturer can be look at oneplus their software support for the oneplus 2 for instance. And the LG G5 is officially supported by LineageOS 15.0 if I'm correct. So just a little more patients
Click to expand...
Click to collapse
Thats true. I can wait for the oreo roms to come up, Can't wait for the devs to make one thanks for telling me about whats going on means a lot
Weve got to let sweet rom cookies bake in the kitchen for a bit first