Related
I'm not in any way asking for an ETA, or stating that I could do anything that our Devs do better or quicker. Simply asking.
Is there a current set back that there have been no aosp updates while other devices like the d855 are receiving updates? I have a GREAT running Bliss pop ROM that I have been using, but has some issues already posted by others in there perspective threads.
Really just trying to feed the curiosity in my flashaholics mind at this point.
Thank you again for all that you do!
Purely guessing on my part that the stock LG Lollipop being available first via leaks and as of now via KDZ has been keeping most everyone busy and/or satisfied. I think that Lollipop was received by the other G3 variants before now, so maybe that's why they're still/resumed making AOSP/CM builds.
By the way, have you looked to see if there's automatic official new CM builds of 12.x?
They are having issues with data for 5.1, that's why updates seem to have stopped.
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?
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
Through it, it is possible https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
I see our partition “/system/vendor” 1.3G size
@erfanoabdi
liushangrong said:
Through it, it is possible https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
I see our partition “/system/vendor” 1.3G size
@erfanoabdi
Click to expand...
Click to collapse
I'm curious. What good would some self-hacked Treble do unless LG gives it to us? LG isn't going to say, "Oh XDA users made a Treble for V30. We'll use that to give them faster updates." No, they will keep giving us updates THEIR way.
Tell me what else Treble is good for? Nothing for the V30, that I can think of.
Treble is designed to theoretically give faster updates from the manufacturer/carrier. Treble only affects custom ROMs and devs if you have bootloader unlocked device with a way to get root. And right now those are open market US998 V30, European H930, and European H930G -- because those are the ones approved by LG. And those already have ROMs, TWRP, etc because they are bootloader unlocked and have full flash commands.
So...
Self-hacked Treble won't help the variants that don't have bootloader unlock and/or full flash commands.
And Treble would only help the three LG Developer website variants by possibly giving them AOSP ROMs. At the expense of losing quad DAC and AI camera functionality.
Please tell me what I am not understanding or missing?
We can, and we will, eventually ?
First need to find out what causes my los15.1 to be so unstable (the rest all works... cam, nfc, audio, ril, bt, wifi,...)
Have the same problem on all aosp based roms (tried LOS and GZOSP so far), so its either device tree, blobs or kernel fault
afterwards i can try to get a real vendor partition (repartitioning basically, possible on the g6/5/v20, so hopefully for us too)
And then some Treble, after i haxed some blobs that force link to /system instead of using the linker ... ? (e.g. vibrator has 2 libs that do that, and some others that search configs only in /system/etc )
Atleast thats the plan so far....
I personally dont care about the AI cam, but DAC is possible, with enough work, according to rashed atleast ?
SGCMarkus said:
I personally dont care about the AI cam, but DAC is possible, with enough work, according to rashed atleast ?
Click to expand...
Click to collapse
Is there a thread discussing, how and if the DAC is possible that you can link here please
ChazzMatt said:
I'm curious. What good would some self-hacked Treble do unless LG gives it to us? LG isn't going to say, "Oh XDA users made a Treble for V30. We'll use that to give them faster updates." No, they will keep giving us updates THEIR way.
Tell me what else Treble is good for? Nothing for the V30, that I can think of.
Treble is designed to theoretically give faster updates from the manufacturer/carrier. Treble only affects custom ROMs and devs if you have bootloader unlocked device with a way to get root. And right now those are open market US998 V30, European H930, and European H930G -- because those are the ones approved by LG. And those already have ROMs, TWRP, etc because they are bootloader unlocked and have full flash commands.
So...
Self-hacked Treble won't help the variants that don't have bootloader unlock and/or full flash commands.
And Treble would only help the three LG Developer website variants by possibly giving them AOSP ROMs. At the expense of losing quad DAC and AI camera functionality.
Please tell me what I am not understanding or missing?
Click to expand...
Click to collapse
I own the US998 and I want to get high pitches to get AOSP ROMs (I believe many people would also like to get). I don't have the ability to get it. But I am looking forward to it! In the future there will certainly be an AI camera running on Aosp (perhaps not as good as LG). The DAC will also have a balance, maybe.
SGCMarkus said:
We can, and we will, eventually
First need to find out what causes my los15.1 to be so unstable (the rest all works... cam, nfc, audio, ril, bt, wifi,...)
Have the same problem on all aosp based roms (tried LOS and GZOSP so far), so its either device tree, blobs or kernel fault
afterwards i can try to get a real vendor partition (repartitioning basically, possible on the g6/5/v20, so hopefully for us too)
And then some Treble, after i haxed some blobs that force link to /system instead of using the linker ... ? (e.g. vibrator has 2 libs that do that, and some others that search configs only in /system/etc )
Atleast thats the plan so far....
I personally dont care about the AI cam, but DAC is possible, with enough work, according to rashed atleast
Click to expand...
Click to collapse
Looking forward, this means that there will be more AOSP ROMs. I am willing to pay for this. Because other people can do nothing.
liushangrong said:
Looking forward, this means that there will be more AOSP ROMs. I am willing to pay for this. Because other people can do nothing.
Click to expand...
Click to collapse
Working on this same ******* bug for over a month now, ask many other devs with more experience... Nobody has a clue wth is going wrong there xD
Logs are basically empty, theres no pstore/ramoops created either... .-.
all im doing is guessing here..... and that not really successful xD
And Treble would only help the three LG Developer website variants by possibly giving them AOSP ROMs. At the expense of losing quad DAC and AI camera functionality.
Click to expand...
Click to collapse
This is EXACTLY what Treble is good for, but you misunderstand. On a device that natively supports Treble, it is insanely easy to build AOSP with everything working just like the stock ROM.
Now, on a phone that you can hack it in, if you get it working ONCE, then you can pretty much upgrade to new versions of AOSP and still have a fully functional phone -- THAT is why you would want to convert a phone to Treble. Hack hard once, and enjoy it for the long run
You are correct that you need a rooted phone to take advantage of it. Even phones that ship with Treble are pretty much useless -- because as you said, they still don't ship updates in a timely manner, and if you don't have an unlocked bootloader with full fastboot, then you won't be getting AOSP.
Treble is awesome, don't think that it isn't. However, it is only awesome on developer friendly phones.
TL;DR: Hacking in Treble support on the H930/G and US998 is most definitely worth the effort in the long run. You can bet your rear that I will be hacking it into the V20 *IF* LG doesn't break the engineering aboot with the Oreo update.
-- Brian
runningnak3d said:
This is EXACTLY what Treble is good for, but you misunderstand. On a device that natively supports Treble, it is insanely easy to build AOSP with everything working just like the stock ROM.
Now, on a phone that you can hack it in, if you get it working ONCE, then you can pretty much upgrade to new versions of AOSP and still have a fully functional phone -- THAT is why you would want to convert a phone to Treble. Hack hard once, and enjoy it for the long run
You are correct that you need a rooted phone to take advantage of it. Even phones that ship with Treble are pretty much useless -- because as you said, they still don't ship updates in a timely manner, and if you don't have an unlocked bootloader with full fastboot, then you won't be getting AOSP.
Treble is awesome, don't think that it isn't. However, it is only awesome on developer friendly phones.
TL;DR: Hacking in Treble support on the H930/G and US998 is most definitely worth the effort in the long run. You can bet your rear that I will be hacking it into the V20 *IF* LG doesn't break the engineering aboot with the Oreo update.
-- Brian
Click to expand...
Click to collapse
Exactly, and about the V20, i think (on discord) rashed mentioned something about treble for the g6/5/v20, and that its almost done
also something about repartitioning ?
Might wanna work with him?
btw, you dont have by chance a clue what could cause my issues stated above ??
runningnak3d said:
This is EXACTLY what Treble is good for, but you misunderstand. On a device that natively supports Treble, it is insanely easy to build AOSP with everything working just like the stock ROM.
Now, on a phone that you can hack it in, if you get it working ONCE, then you can pretty much upgrade to new versions of AOSP and still have a fully functional phone -- THAT is why you would want to convert a phone to Treble. Hack hard once, and enjoy it for the long run
You are correct that you need a rooted phone to take advantage of it. Even phones that ship with Treble are pretty much useless -- because as you said, they still don't ship updates in a timely manner, and if you don't have an unlocked bootloader with full fastboot, then you won't be getting AOSP.
Treble is awesome, don't think that it isn't. However, it is only awesome on developer friendly phones.
TL;DR: Hacking in Treble support on the H930/G and US998 is most definitely worth the effort in the long run. You can bet your rear that I will be hacking it into the V20 *IF* LG doesn't break the engineering aboot with the Oreo update.
-- Brian
Click to expand...
Click to collapse
You said it in a way better than me.
I'm very skeptical Treble will give much faster updates from carriers/OEMs to non-rooted phones, when they have no financial incentive to provide faster updates. In fact, one regional carrier I used to be with basically said "You want a new OS, then you need buy a new phone."
Yep .. disposable phones.
Hopefully in Treble 2.0, Google will require an update mechanism be in place for users to pull (or Google to push) OS updates directly. Then having a rooted phone is just a bonus, but not needed to get timely updates.
If you look at the updates that are pushed to phones currently, the firmware is actually updated very rarely, and it is mainly the modem.
-- Brian
runningnak3d said:
Yep .. disposable phones.
Hopefully in Treble 2.0, Google will require an update mechanism be in place for users to pull (or Google to push) OS updates directly. Then having a rooted phone is just a bonus, but not needed to get timely updates.
If you look at the updates that are pushed to phones currently, the firmware is actually updated very rarely, and it is mainly the modem.
-- Brian
Click to expand...
Click to collapse
It seems that we still need to wait. There is no news at all.
LMFAO.
Sorry, but you must be a new LG owner. LG is one of the WORST OEMs.
-- Brian
So Android P rolled out, and I was wondering, we've been blessed with devs work and got every great update and tons of rom for this device. And was wondering is there by any chance getting Android P based roms in future. Also I was specially wondering about RR, because I like that a rom alot.
Well will we be getting android P, or I shouldn't get my hopes up?
Just wait patiently. The sources are available, just wait until a dev cooks a build for kenzo. Or when proper GSIs will be available.
Sure thing buddy, by any chance you also want VoLTE and 10 hours SOT?
Nobody maintains Kenzo for income, just because they feel like sparing time, for crying out loud it was just formally announced today, so if you want P go ahead and build it on your own.
Just stop this kind of threads, they are just spam.
BusterBg_18 said:
Sure thing buddy, by any chance you also want VoLTE and 10 hours SOT?
Nobody maintains Kenzo for income, just because they feel like sparing time, for crying out loud it was just formally announced today, so if you want P go ahead and build it on your own.
Just stop this kind of threads, they are just spam.
Click to expand...
Click to collapse
Could like please take your hate and get the hell out of this thread.
Like seriously, I'm just genuinely asking a question, so its not a spam, and I asked BECAUSE P came out today. If you don't wanna answer just ignore this, not a hard thing to do.
-shashankpatel- said:
Could like please take your hate and get the hell out of this thread.
Like seriously, I'm just genuinely asking a question, so its not a spam, and I asked BECAUSE P came out today. If you don't wanna answer just ignore this, not a hard thing to do.
Click to expand...
Click to collapse
Sorry, the devs need income and now the devs like @rocknegi have started p**n for ₹50/day or ₹200/month cause the users aren't donating enough money.
If they get enough income from p**n selling, they will develop Android P for you.
Daruwalla said:
Sorry, the devs need income and now the devs like @rocknegi have started p**n for ₹50/day or ₹200/month cause the users aren't donating enough money.
If they get enough income from p**n selling, they will develop Android P for you.
Click to expand...
Click to collapse
Yeah I saw that as well. Look I just wanted to know of there was a possibility of kenzo getting a p, coz yk, this is pretty old device.
-shashankpatel- said:
Yeah I saw that as well. Look I just wanted to know of there was a possibility of kenzo getting a p, coz yk, this is pretty old device.
Click to expand...
Click to collapse
I know but just use some sense? We are not devs, we are normal users like you. How do we all users know if a dev can develop Android P. Plus, do you think a dev will announce 'Hey Niggas, I'll develop Android P rom for you all niggas asking for it, wait for few hours:. No?
The dev need to look into the source, need time to see what all bugs needs to be fixed, else users like you will come here and say it's buggy, that doesn't work, this doesn't work right?
Another sensible answer: Android P sources are just released. It's not like magic to develop rom directly from the source. Needs a lot of hack, back port blobs and things we don't even understand.
Summary: it's a redundant question as of now. Please wait, if there's a Android P rom, you will see it here. Till than, enjoy other roms.
Daruwalla said:
Sorry, the devs need income and now the devs like @rocknegi have started p**n for ₹50/day or ₹200/month cause the users aren't donating enough money.
If they get enough income from p**n selling, they will develop Android P for you.
Click to expand...
Click to collapse
Disaster! Time to join negi ?
Nick_gunale said:
Disaster! Time to join negi
Click to expand...
Click to collapse
Free p**n sites aren't enough for you? ?
Daruwalla said:
Free p**n sites aren't enough for you?
Click to expand...
Click to collapse
need income lol
As a user of redmi note 3 . i just hope dev make android p for this device.
As one of the lineage 15.1 maker for Redmi Note 3, yep, we will do bringup after 9.0 source code release, and should be easier than Oreo, as Pie impacted a lot of backport comparable, please don't ask lots of annoying OTA, follow XDA rule, P will be coming to Kenzo/Kate after sometimes, but for Treble is more harder as blobs are old, we need to wait hydrogen and suzu devices etc updates for new blobs, for more Treble working, and even CAF for msm8952 board not impacted treble, unlike msm8953 board, so treble now is experimental and don't expect stable treble in a short time.
---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------
And for my lineage 15.1 long time no updates because I teams with @Carlos Arriaga, and he is back in July so I and other team members need to do some updates, my 15.1 new build will release soon
LokManSiu said:
As one of the lineage 15.1 maker for Redmi Note 3, yep, we will do bringup after 9.0 source code release, and should be easier than Oreo, as Pie impacted a lot of backport comparable, please don't ask lots of annoying OTA, follow XDA rule, P will be coming to Kenzo/Kate after sometimes, but for Treble is more harder as blobs are old, we need to wait hydrogen and suzu devices etc updates for new blobs, for more Treble working, and even CAF for msm8952 board not impacted treble, unlike msm8953 board, so treble now is experimental and don't expect stable treble in a short time.
Click to expand...
Click to collapse
Thanks for this reply. Won't be asking for annoying updates, just wanted to know that is all.
Well, speaking of Android Pie development, I've found a Pixel Experience ROM that is based on Android Pie through a Telegram channel
Known broken features:
• Bluetooth
• VoLTE
• Stock camera app, but the camera works for stills and video (Open Camera)
(link: http://t.me/TheStrechh) t.me/TheStrechh (the author)
(link: http://t.me/KenzoRoms_News) t.me/KenzoRoms_News
(link: http://t.me/kenzoromnews) t.me/kenzoromnews
NOTA BENE: Try it at your own risk, as it is not developed by me, but if you want to download it and try it, here's the link: https://drive.google.com/open?id=1KqyUEdUgtW5coyoTlHuuN0Y2Jt1aKnn-
Yep. I've been using the Pixel Experience 9.0 from @thestrechh as my daily driver for a couple days now.
It's usable if you can get by without VoLTE and Bluetooth.
Gcam works, but can't change the settings and it crashes a lot. Front and back camera stills and video all working.
The rom feels pretty buggy and a bit sluggish to me. CPU operations seem to take an unusually long time. Maybe all the cores are not being utilized optimally. (Don't know. I haven't actually tested.)
I'm sure this rom will continue to get better and better in the coming days. I'm anxious to dirty flash the coming updates.
Excellent work by @thestrechh.
kazekiri said:
Yep. I've been using the Pixel Experience 9.0 from @thestrechh as my daily driver for a couple days now.
It's usable if you can get by without VoLTE and Bluetooth.
Gcam works, but can't change the settings and it crashes a lot. Front and back camera stills and video all working.
The rom feels pretty buggy and a bit sluggish to me. CPU operations seem to take an unusually long time. Maybe all the cores are not being utilized optimally. (Don't know. I haven't actually tested.)
I'm sure this rom will continue to get better and better in the coming days. I'm anxious to dirty flash the coming updates.
Excellent work by @thestrechh.
Click to expand...
Click to collapse
I've not noticed sluggish performance here, but I have noticed bugs here and there, which is par for the course, considering the infantile state of Android Pie development.
Still though, for an early release, it works almost excellently
aha360 said:
I've not noticed sluggish performance here, but I have noticed bugs here and there, which is par for the course, considering the infantile state of Android Pie development.
Still though, for an early release, it works almost excellently
Click to expand...
Click to collapse
I decided to do a benchmark with antutu. The score seems fine. Guess I must be mistaken.
kazekiri said:
I decided to do a benchmark with antutu. The score seems fine. Guess I must be mistaken.
Click to expand...
Click to collapse
It happens. Either way though, the coming weeks will be interesting in terms of Android Pie ROM development
The bug of battery drain in standby (mobile network) apear in Android PIE like Oreo?
Can you share battery stats?
Thanks
aha360 said:
I've not noticed slugogish performance here, but I have noticed bugs here and there, which is par for the course, considering the infantile state of Android Pie development.
Still though, for an early release, it works almost excellently
Click to expand...
Click to collapse
did you have the Pixel Setup crashing after flashing this rom? if you do, what's the solution?