yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] TheUnladenSwallow:
Okay guys, this's getting ot, everyone calm down and wait until the dev says anything unless you're reporting a bug.
[G2 Android Development] :
Yep. I always keep inline with upstream device specific commits.

And to others, sorry for the silence...getting a very weird issue with all CM-based ROMs that only applies to a select crowd (http://xdaforums.com/htc-one-x/orig-development/compile-cm12-1-error-t3195781). I know the thread is for the HTC One X, but it applies to all devices. If anyone knows about this error or how to solve it, help would be majorly appreciated! Been messing around with it for about a week and a half with no luck.
[G2 Android Development] fLipz:
[MENTION=2332422]temasek[/MENTION] [MENTION=5236920]zg85[/MENTION]

help!
[G2 Android Development] anbinhv:
Happy to see you still here!
[G2 Android Development] :
Haha! Apparently using a small number of threads caused it to screw up the building. Using mka fixed it for me. Just finished a build. Testing and if all is good I will begin building for all variants.

EDIT: 3.4.109 just dropped so I am updating my kernel source real fast and adding some small things but nothing large enough to bork builds. Builds WILL be started tonight and hopefully finished by tomorrow. As mentioned earlier f320 support is temporarily dropped...however I've had several f320 users talking to me and I will send them some possible solutions momentarily!
[G2 Android Development] ZeNiXxX:
hey tsunamical

how is the current status of the process? I can't wait for euphoria rom :)

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] :
Bleh, I left my script running which auto-syncs after each build, and Euphoria got some updates pushed Legacy-side, but my custom repos weren't updated so it caused builds after the d802 to flop.

Restarting builds now.
[G2 Android Development] Lawlrus:
Builds or it didn't happen
[G2 Android Development] xxoscarxx28:
Just relax and enjoy waiting by watching on Youtube

Now that's a real scrub hahahahha

---------- Post added at 03:56 AM ---------- Previous post was at 03:55 AM ----------

So always double check next time?
[G2 Android Development] murdoch1:
Still building??
[G2 Android Development] goast:
Dude just wait. He would have dropped us links if he had it where he wanted for release... Plenty of other ROMs to try.. Or wait
[G2 Android Development] enzo_cz:
There's a plenty of us waiting on the update but pushing like this is worthless, pal. We simply need patiently wait.
[G2 Android Development] alexx_kidd:
What is happening??
[G2 Android Development] Lawlrus:
Not too much, enjoying the day. Glad the rain finally stopped on the east coast.
[G2 Android Development] alexx_kidd:
It rains constantly here in Greece for the last few days... Autumn is coming
[G2 Android Development] :
Well, turns out I did have a panel issue with something I picked, but all should be good now. Starting builds now.

Sorry for the slow updates, senior year is killing me on top of a job and my time is pretty limited. I'm always updating my source, just don't always get around to getting builds, for those who build for themselves using my source.
[G2 Android Development] ZeNiXxX:
thanks for the info. how can I build from your source? is it enough to read some building tutorials on xda or should pay attention to some individual settings? maybe you can pm me than :)

which system to I need for building? Ubuntu or windows 10?

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] ryukiri:
you need a linux distro so ubuntu is fine. Follow the guide on setting up ubuntu to build android (http://xdaforums.com/showthread.php?t=2639611)

at the repo init stage, use tsunamical's source instead of what was given in the link. then repo sync will take a long time since its downloading about 13-15GBs of source.

compiling may take several hours depending on your cpu specs
[G2 Android Development] slayer3032:
I pulled down what was stated on this which wasn't linked in the OP https://github.com/Euphoria-G2/android_manifest/

Followed those instructions as well as some off of the CM wiki. I had to go locate some lib files for SlimSaber but it seems like it's just requiring more and more dependencies which aren't pulled down initially. Is there something else I'm supposed to repo on top of it or?

It compiles for about an hour then dies at the following.

make: *** No rule to make target `vendor/lge/d801/proprietary/vendor/lib/libtime_genoff.so', needed by `/home/<user>/euphoria-d801/out/target/product/d801/obj/lib/libtime_genoff.so'. Stop.
[G2 Android Development] ryukiri:
did you pull the proprietary vendor files (from like the muppets or something)?
[G2 Android Development] slayer3032:
I didn't, I checked the g2-common folder and that file is in it. I'd assume that it pulled down this repo as well which contains the same files and is a fork of a repo from TheMuppets.

https://github.com/Euphoria-G2/proprietary_vendor_lge

The latest commit however removes a line which references this file, not sure if his latest changes could be causing the error.

https://github.com/Euphoria-G2/prop...639#diff-77a1db6c14bdad4d702addc48344a79eL332

Unfortunately I've never actually compiled roms before so I have no idea I should be expecting as considered normal or broken either. After I settled all the dependencies which are required do what I assume is build the kernel it gets about an hour in and fails there now if it helps any more.

Actually, there's been some commits since I last tried building it. I'll attempt again and see what happens
[G2 Android Development] :
[MENTION=5277982]slayer3032[/MENTION] This was fixed in the latest g2-common rebase. No idea why it didn't quote your post.

All is good now! Waiting for some upstream commits for device trees to be ready, but other than that all should be good.
[G2 Android Development] rancur3p1c:
d800 here I follow the guide to a T, wiping, flashing bootstack as a first timer, flashing latest zip ROM-- and my phone does nothing but sit at the LG screen.

I previously was running blastigator's LP-compatible bootstack, and I have his 2.8.7.1 TWRP. What am I doing wrong? I'm not doing anything wrong. Why is this not working? Man, I was really looking forward to this ROM :(
[G2 Android Development] slayer3032:
I've tried building for the D801 multiple times now and I keep getting the same errors. I decided to try building for the D802 and it completed all the way through just fine.
[G2 Android Development] murdoch1:
D802

I can gladly test the 802 for you if required?:D
[G2 Android Development] slayer3032:
I'm not the maintainer? It's really not my place to upload anything. You can build the D802 yourself as previously suggested in the thread if you're too impatient to wait like myself. I was just posting about other devices failing to build which he'll have to address before anything can be released anyways.

If you want to give it a shot. You'll need the library files from SaberMod and to meet all the dependacies which come with the kernel which you can get from the ubuntu-toolchain-r/test ppa or whatever. Other than that you should just need to follow the basic instructions from previously linked information of which you can find everything you need over the last few pages.
[G2 Android Development] :
That's really weird...Most likely a ccache issue. Upon your next build sync, make clobber, and then run ccache -C. There weren't any differences between the D801 and D802 specifically that should've caused a build to fail.

Getting a sod every time it goes into suspend...hoping I solved the issue with the latest commits and reverts.
[G2 Android Development] slayer3032:
Yeah, I was looking all over the place for any sort of issues in the make files for the D801 and saw nothing that I could imagine to cause it. I just deleted 100gb of everything android related and reinitialized the repo. I'll give it a shot again and see what happens.

Update:

I finally got it to compile all the way through! I flashed it and it promptly failed out on boot coming from the now discontinued PA, I remembered it used bump along with the CAF hybrid bootstacks so I flashed those like you recommended months ago. I got it to sit on the LG splash screen for a while but it wasn't heating up or anything over a few minutes so it's not booting for me. I'm using blastagator's TWRP and the CAF bootstacks, do you have any ideas what could be causing this?
[G2 Android Development] :
I haven't tried a build post this commit: https://github.com/Euphoria-OS-Devi...mmit/52a69d256fcf7c6c91eb8fc22f3af55fa7ffb4d5, but that's what may be causing an issue. Navigate to the device tree from your source (cd device, cd lge, cd g2-common, and then do git revert 52a69d256fcf7c6c91eb8fc22f3af55fa7ffb4d5 and then exit the popup (If it pops up in terminal control+x closes it out)) and revert the commit using the method previously described. If you are able to boot afterwards, then the issue relies in the version of the bootloader you are on.

That commit is responsible for removing capability with the JB bootloader. You should be on the latest hybrid caf bootstack by [MENTION=5263483]daniel.stuart14[/MENTION]. In the near future there will be an assert added which means it will not flash the ROM if you are on an incorrect bootloader, which makes it a lot harder to brick, which is incredibly nice for the average Joe.
[G2 Android Development] slayer3032:
I'll give that a shot and report back on how it goes. The bootloader check would be extremely nice, it's always really nerve racking messing around with flashing bootstacks trying to switch between roms, recoveries and what not.

So I gave it a try, if I flash the CAF bootstack or Rashed97's bump/kk bootstack I just get the LG splash screen. I tried flashing Rashed97's loki bootstack and it booted just fine but the radio didn't work and it went into a SoD soon as the screen turned off.
[G2 Android Development] :
See if you can get a log of the sod, I'm super busy for the next few days so I can't build.
[G2 Android Development] slayer3032:
Shot you a PM with a log that I logged when I turned the screen off, turning the screen off at all makes it SoD. I'm unsure if this could be because I'm only getting it to boot with the LP Loki bootstack which isn't intended.
[G2 Android Development] :
SoD issue is fixed!
[G2 Android Development] Lawlrus:
Huzzah
[G2 Android Development] slayer3032:
Can confirm it no longer SoD's everytime the screen goes off, however now it "randomly" SoD's when the screen turns off. I was able to recreate it by spamming the power button for 10 seconds or so until the screen stopped coming on.

Still hangs on the LG splash on the D801 under the bump or CAF bootstacks, works with that reverted commit. Data was default set to off or something which was strange, changed my APN to T-Mobile IPv6, tapped the quick settings tile and LTE finally sprung to life.

I'm iffy on reporting issues since it seems more like there's random issues related to my unintended bootstack, I'll send you some logs and hope they help with something at least.
[G2 Android Development] :
Was that build with or without the latest two neobuddy commits? I am running a build from before then with no issues. If the other two commits are causing more SoD's I'll revert them.
[G2 Android Development] slayer3032:
I believe I synced before you made your most recent commit to the android_manifest but after you made a SQLite related commit. Do you have any ideas on bootstack issues and radio/data issues?
[G2 Android Development] :
Flash one of daniel's hybrid caf bootstacks before next build, but don't flash any other bootstack/bootloader mods. That's exactly what I'm doing and I can boot fine. You must've synced at an odd time, or the kernel settings I switched to afterwards are stopping SoDs. It could also be related to moving dexopt to after boot rather than at boot, causing more overhead. How long did the random SoDs occur? Was it a set time after boot or did they never stop?
[G2 Android Development] slayer3032:
If I flash daniels bootstacks it just hangs on the LG flash screen. I think I did sync at an odd time, I'm getting sync errors when I attempt to sync so I'm just going to delete and init the repo again. I'll report back with a build that's most up to date. Kind of confused why I'm having so many issues with repo. I should just have to run a repo sync whenever you make changes correct?

The SoD's weren't exactly "random" but they were happening at random whenever the screen was shut off, I got into installing apps and I grabbed my phone since the screen timed out and it wouldn't come back on. That then occurred again a few times while messing around on the phone and again a couple times when I wiped data/cache and turned the screen on/off a few times until it happened. There didn't seem to be any sort of time or condition which caused it other than simply turning the screen off. Although it did seem more likely to happen if you left the phone alone for a short bit while it installed apps or sat idle.
[G2 Android Development] ZeNiXxX:
ok thansk i'm gonna try this now. But i have one question. What about the device ? tsunamical repo is for several devices ... how to i pick/use the right one (d802 for me ).
[G2 Android Development] ryukiri:
grab device trees from lg-devs
[G2 Android Development] slayer3032:
You just run brunch d802, the other device files hardly take up much space.

You'll need the sabermod toolchains and meet the dependencies from the kernel from the ubuntu-toolchain-r/test ppa.

http://xdaforums.com/android/software-hacking/toolchains-sabermod-arm-arm64-t3064459

https://gitlab.com/SaberMod/sabermod-manifest/blob/master/README.md

I just used the prebuilt files, hopefully that shouldn't be causing any of my issues.
[G2 Android Development] ZeNiXxX:
hmmm OK I've synced repo for first time it was about 10gb and takes about 6 hours. so what's the Next step? should I try to build for d802 now?

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] :
This is incorrect. The lg-devs device trees are outdated now and CyanogenMod trees are what every CAF tree stems from.

My device trees are on Euphoria-OS-Devices. From there you won't need to do any editing to get it to properly build.

Also, [MENTION=5277982]slayer3032[/MENTION] have you done a build as of the latest commits from a few days ago yet? It's the last week of the grading period so I'm swamped with schoolwork at the moment and over the next few days I have various performances for drama :crying:
[G2 Android Development] slayer3032:
Yeah I checked it out last night and I still can't boot the D801, it just hangs on the LG splash. I'd have to revert the commit that prevents loki from booting which I think I'm having other issues using that bootstack anyways. Compiles perfectly fine and what not though.
[G2 Android Development] :
Okay, I think I have an idea of what's causing the random SoDs. I remembered a commit I picked that alters some resume/suspend things that I saw a few devices pick and revert so there's a good chance it's that. Also, updated to 3.4.110 and brought some stuff over from Uber Kernel. I'll test in a bit. Thanks for your help!
[G2 Android Development] Lawlrus:
?? Post this in the q&a
[G2 Android Development] alfagama:
This is a nice rom, thinking to use it as daily driver, but have a few questions:

1) is xposed working?

2) is Xcam compatible?

3) is there quickwindow app and quickremote app to use with?

4) I am now on cloudy 3.3 with Cloudy kernel, can I use the same kernel or Xceed, or is there some other kernel?

5) If I wipe data/cache/dalvik/system can i proceed to flash the rom or have I to do something else?
[G2 Android Development] L0nelyE4rth:
1. Working but I don't know what version is it ?

3. Not sure, but it have for AOSP ( Can't using LG apps )

2,4 and 5. Not working on AOSP
[G2 Android Development] norbigazda98:
How can I do the overclock, actually? I haven't seen anything like that in the menu or settings.

My situation: I came from stock Lolli, Flashed Loki bootstack, ROM and aroma GAPPs. That's all, and I don't have overclock option bult-in and with kernel tuner tools the max CPU frequency is the stock, 2265 MHz for CPU and 450 MHz for GPU.

Thanks for help. :)
[G2 Android Development] Thesqu:
Maybe it's an app related problem? Try using Kernel Adiutor or Trickster Mod in the Play Store
[G2 Android Development] Lawlrus:
Doubt he has the ability to over clock baked in considering our phone has had heat problems and melted displays.
[G2 Android Development] norbigazda98:
I tried them, but still 2265 MHz is the maximum.
[G2 Android Development] coolerthannos:
The rom is excellent and working great so far on my LG G2 ls980 however there is one annoying bug which pops up from time to time. Sometimes the vibrate on touch doesn't stop and keeps on vibrating until and unless I press on back, home or any other context sensitive button available on the screen.
[G2 Android Development] Lawlrus:
Been documented for the five months we have been using full caf. Every ROM has it that is full caf.
[G2 Android Development] coolerthannos:
Okay thanks didn't know about it.
[G2 Android Development] reycovirt:
Can i flash this on d802???
[G2 Android Development] joeben1:
Yes, just follow the OP.
[G2 Android Development] reycovirt:
Last question is this ready to flash on lollipop based custom rom??? I mean i am alreadt in lollipop version...
[G2 Android Development] joeben1:
Just follow as it's written in the OP and you should be fine.

The link to the Loki bootstack is also there, I also got here the advice to reboot to recovery after flashing the bootstack.
[G2 Android Development] AssassinGEO:
Guys, there is a known problem in cm12.1 roms, when notification comes there is 0.5sec skip in sound. Is that bug present in this ROM?
[G2 Android Development] thename123:
Edit:

Do you have any link for the post?
[G2 Android Development] smokerman:
no screenshots of this rom? is this project dropped?:rolleyes:
[G2 Android Development] Lawlrus:
Surprise! It looks like 5.1.1
[G2 Android Development] smokerman:
what i mean is the style..like RR or Blissop..or pure 5.1.1..

Enviado do meu LG-D802 através de Tapatalk
[G2 Android Development] Lawlrus:
I don't know what you mean by "style" but, all 5.0 ROMs look the same
[G2 Android Development] thename123:
If I want back to any rom stock(like cloudyG2) (d802)

What's the steps?
[G2 Android Development] fendaris:
Ask in Q&A or try to see if your question has already been answered. And believe me, it has.
[G2 Android Development] thename123:
Not be sure..
[G2 Android Development] abby_nitewolf:
Has this rom been abandoned? If so, does anyone recommend another one that's stable for VS980?
[G2 Android Development] Lawlrus:
5.1.1? The PAC ROM in the verizon section, or exodus.
[G2 Android Development] Frappoccino:
I thought PAC is also abandoned (d802)?
[G2 Android Development] Lawlrus:
Key words of my post were. In the Verizon section.

We have someone with a vs980 that builds it for us
[G2 Android Development] Frappoccino:
Yeah, i saw :( Wished someone would do it for the d802 :/ I used Euphoria OS 1.1 for a long time and now I am looking for a new ROM, but I'm not happy with any of them. (I'm currently on SlimLP)
[G2 Android Development] Lawlrus:
Well I can say that honestly, this was his first time doing something of the sort, and he got it figured out pretty easily.

Take it upon yourself to dive into development. That's the good thing about this device, all the devs and more than willing to answer questions and help people out, just like the op here.

If no one will take it upon themselves to do it, take the reins and make it happen.
[G2 Android Development] :
Essentially, yes. Development on the Euphoria side has (mostly) ceased, and the same goes for most individual devices. I was really starting to dislike the mush that I put together with the G2 repos. A lot of work was a mash of other's work. It was also starting to grow further and further away from what Euphoria-OS was. The further and further I went, the less customization you would get (ramdisk and ROM differences would make other kernels not work). The kernel also had a lot of improperly integrated features. I've learned a lot since working with Lollipop, and I don't regret it for a moment. I do apologize for the slow updates and minimal releases, that is something that will not happen in the future. It is incredibly difficult to juggle responsibilities and I did a horrible job at it.

Which leads me into the next portion. I have begun working on my own Marshmallow project (If you've been stalking my GitHub activity you'd see a gander ;)), along with [MENTION=5263483]daniel.stuart14[/MENTION]. This time I have chosen to work with others as working solo can only lead to more issues. It is also nice to receive advice and criticism from others, which I was not open-minded to and apologize to the rejected offers in the past. There is no current ETA for release as I am slowly gathering the team and bringing up repositories. The project is CM13 based, and more information will be released at another time (Follow me on G+ for updates, I'd rather not go off-topic as much here).

The latest Euphoria-OS source brings it up to android 5.1.1_r28. I am willing to make a vanilla build (CM 12.1 kernel + default GCC) if anyone is interested in that. It should be very stable, perhaps not as speedy as earlier builds though.
[G2 Android Development] desirexel:
Great job for what we ve experienced yet. Waiting for your next step. Thanks for explaining
[G2 Android Development] Hbohd:
[MENTION=5934584]tsunamical[/MENTION]

A great new step for you and our community :) Big thanks for your earlier job btw.

However, I would be eager to see a ROM with possible RRO implementation instead of CM theme engine. Why no one base off it? :( Have we got any working MM ROM with Layers for G2? [emoji14]
[G2 Android Development] LeoPosas:
Great news, you remember me to [MENTION=1050103]sykopompos[/MENTION], started from the bottom on nexus 4 forums, now it's the lead of RRO Layers project.

I see a potential recognized developer here! Good Luck!
[G2 Android Development] :
Most ROMs are going to be CM13 based as it takes additional work to get straight AOSP booting on the G2. Many teams aren't willing to rip the theme engine out either. For now, I'll be sticking with the CM theme engine as I've found many themes I've liked, and can link you to some of my favorites :P

That's so awesome! Thanks :)
[G2 Android Development] lunafag:
Well, that's a shame. I'm still using your 06.22 build, no other ROM has quite reached that level. Some are rebooting often and drop calls, the many others are plain slow. CM13 for G2 has RIL issues that render it unusable for me, and they won't be fixed any time soon according to the devs. I was really looking forward the update, sad to see so much work just left unreleased. Maybe there's a snapshot stable enough to be considered release-worthy? There's enough vanilla ROMs.
[G2 Android Development] Holgott:
PLZ share some links ☺ each theme I can find is uglier than the other ?
[G2 Android Development] uxairmalik:
i tried to install this rom.i am comming from cloudy G2 3.3 with DorimanX kernel.

i followed all steps

wipe system,cache,data,delvik cache.than i installed bootstack from the link in the thread (bumped) and than rom and than Gapps.

but it doesnt boots up.Stuck at LG logo.No notification light blink or heating.

can anyone help me?
[G2 Android Development] lunafag:
Use loki bootstack.
[G2 Android Development] uxairmalik:
thanks it worked.

but i am facing a problem that i am unable to underclock the gpu to normal 450 mhz frequency.

when ever i underclock it to 450 it again jumps to 650mhz.

any fix?
[G2 Android Development] lunafag:
A known bug of this ROM. Likely won't be fixed.