yashsingh1/xdaforums huggingface dataset:
[G2 Original Android Development] PunkUnity:
Regular Omni nightlies my battery takes 2-3 hours to charge all the way from empty. Now it's about 8 hours. Battery drain is an even larger issue. I'll post a picture of the battery usage stats. I have like 60% battery left after 2 hours of usage. Used to have over 90% still after 2-3 hours of moderate usage. Not *****ing, just stating simple facts
[G2 Original Android Development] PunkUnity:
Android system is destroying my battery lol. Usually nothing beats the display in battery death lol. Anyways. Good luck [MENTION=3878813]jakew02[/MENTION]. Thanks for your time
[G2 Original Android Development] Gandalf:
I am well aware of this. I'm on vacation so frankly idgaf right now. As I said before, I'll fix it once I'm home.
[G2 Original Android Development] PunkUnity:
My bad bro. Just responded to Lawlrus. Just shouted out at you to say thanks for your hard work and time. Idgaf if it's ever fixed, although it's my favorite ROM.
[G2 Original Android Development] Gandalf:
Just at thought, I noticed when I use omni's launcher3 with custom hotword detection enabled that android system was killing my battery as well. You're not using that by chance, are you?
[G2 Original Android Development] daryelv:
Turning on "Ok Google" detection in Nova Launcher also had a battery hit for me, nothing drastic, but enough to notice and consider turning it off.

-Daryel
[G2 Original Android Development] Flynny75:
I'm not using any launcher voice detection, but am using Google Now Anywhere and am experiencing big Android System drains
[G2 Original Android Development] daryelv:
I had enabled that back when it was first availabe, then I saw the battery drain and disabled it immediately. Nice concept, but maybe it's designed more for phones like the Moto X. Anything that is constantly polling the sensors is going to burn battery. I'd say that if you regularly use a feature like this, then leave it enabled, but if you don't then might as well disable it.

-Daryel
[G2 Original Android Development] PunkUnity:
I use Google Now Launcher.... Should I switch to Nova or Apex?
[G2 Original Android Development] Gandalf:
Strange. I use nova with no major drains. I'm also going to add back a lot of the optimization and other services that we have on the nightlies that were lost with the kitkat sources. I'll have builds up tonight
[G2 Original Android Development] PunkUnity:
I'll switch to Nova then
[G2 Original Android Development] Flynny75:
That is sound advice, but I didn't experience big drains before. Will wait to see what changes Jakes pending updates make before disabling it.

I have also noticed the device becoming increasingly difficult to wake, needing multiple presses of the power button to wake it. Then the launcher is stopped responding, but the wait / kill dialogue isn't responsive. Yet the power button still brings up power menu. Interesting.

Although I must say... Feels super smooth
[G2 Original Android Development] PunkUnity:
I have had the same issue. Screen takes up to a minute sometimes to wake up after pressing the power button.
[G2 Original Android Development] Flynny75:
I think the drain culprit is Surface Flinger

Just trying to help ☺
[G2 Original Android Development] Gandalf:
Yep, that'd be the omni frameworks.
[G2 Original Android Development] PunkUnity:
Is there an easy work around to dumb down surface fling?
[G2 Original Android Development] Gandalf:
not that i know of. i'll basically need to start using CM's audio/video frameworks along with the CM media and display HALs that I'm currently using to clear this up.. the outdated Omni frameworks are obviously not agreeing with the updated CM display and media HALs which are required with this new kernel. I'll need to rebuild the entire ROM to clear that up,, since I'm not going to rip the kernel apart to make it work with Omni's outdated HALs (that'd be taking 2 steps back for 1 step forward :P )
[G2 Original Android Development] Lawlrus:
[MENTION=3878813]jakew02[/MENTION]

That sounds like a ton a work.

Sent from my Vs980 running CloudyG3 1.3
[G2 Original Android Development] Gandalf:
I'm just getting my rig set back up. Got a new ssd
[G2 Original Android Development] Lawlrus:
Nice. I finally got around to getting a Samsung evo 840, it was long overdue. Ridiculous how fast it is

Sent from my Vs980 running CloudyG3 1.3
[G2 Original Android Development] Gandalf:
that's what i got. picked a 250gb one up at BestBuy for $119, quite a steal if ya ask me..
[G2 Original Android Development] Lawlrus:
Hell yeah, that's a good price. I got mine for 130 on new egg I think.

Edit: holy hell, nvm I didn't see 250 gig. That's a killer deal. I paid 130 for 120

Sent from my Vs980 running CloudyG3 1.3
[G2 Original Android Development] el_tute:
Hi people, I have a problem with regular updates. every time that I flash the updates (after flashing throu recovery), the phone restart, shows the LG logo for a second and then the screen goes black, the only thing that I can do is restart and enter again on recovery to flash a preious omni rom, the last rom without problem is 03/09.

Do you know anything about this?

I have a D806, stock omni kernel, band base M8974A-AAAANAZM-1.0.190036

Recovery TWRP Custom by Dr87 version 2.7.1.0 (with the thermal thing)

thanks!!

PS: Please sorry my bad english
[G2 Original Android Development] Flynny75:
You are lucky you can get recovery, the latest 802 'official' soft-bricked me repeatably. Would avoid anything since the 3rd of sept. Would not recommend Jake's testing builds yet either, although they are promising
[G2 Original Android Development] tholmes8291:
FYI $119 on Amazon now
[G2 Original Android Development] Gandalf:
It looks like someone may have borked the omni frameworks or something somewhere because jflte is having issues too.
[G2 Original Android Development] PunkUnity:
Is XplodWild still working on Omni?
[G2 Original Android Development] Gandalf:
builds going now
[G2 Original Android Development] Flynny75:
Ooh, something to check out in the morning. Is this with the cm AV frameworks?
[G2 Original Android Development] Gandalf:
new builds up @ dirtyunicorns.hostingsharedbox.com/jake/omni/g2

use the 20140911 dated builds.

I'd recommend don't this:

backup data

ENSURE YOU ARE USING dr87's TWRP with thermal throttling

wipe system data cache dalvik

flash ROM, Gapps(if desired) and supersu(if desired)

reboot

go through setup wizard

let device sit for ~5 minutes to sync your Google account and run all the first boot scripts

update any apps that need updating via play store

reboot

enjoy

I'll be throwing out new TWRP 2.8.0.0 builds tomorrow as well
[G2 Original Android Development] Voje:
When the development has come this far, I decided to install the latest build.

Everything seems to work perfect, and it feels very stable and fast; great work jakew02!

But, for some reason I have extremely slow charging.. After having the charger connected for almost approx 45 min, it had only charged 2 percent..

Do you have any tips? And is there any info I can provide you with?

My device is a D802.

Once again, great work!

Edit: I forgot that I changed the USB cable, and when I used the old one charging was normal.

But don't quite understand it, since my tablet charged normally with that cable..
[G2 Original Android Development] Flynny75:
Has been reported before. Surface flinger is also still pretty hungry
[G2 Original Android Development] arifqur:
New TWRP version? Wow that is super
[G2 Original Android Development] Lawlrus:
[MENTION=3878813]jakew02[/MENTION]

You swapping out the kernel on the 2.8 twrp as dr87 did?

Sent from my Vs980 running Aicp 6.0
[G2 Original Android Development] Gandalf:
immediately after flashing it was for me too, until i carried out the process that i posted on the last page and it stopped after reboot, not sure if you tried that
[G2 Original Android Development] DominikHolecek:
Hi all, I used to be on this ROM but I had some issues with high temperature and slow battery charging so I flashed other ROMs. Now I'm on mahdi and I'm curious if these problems have been solved? Especially problems with overheating... - very high temperature even in graphically low-end games...

Sorry for question, I tried to find it in previous posts but no succes... (I've only found something about slow charging in the last page - and developer's answer along with advice, but nothing to overheating)
[G2 Original Android Development] HueyT:
Yes and Yes. Try it and see. Make sure you try 9/11/14 build at DirtyUnicorn website.
[G2 Original Android Development] Voje:
I think it has been talked about not long ago, but the latest build feels a bit hot to me..

Too lazy to look pages back, but if my memory serves me correct jake has said that he is on the case and I think this latest build is composed quite differently compared to the recent builds as an attempt to fix it.

But as I said, it feels a bit hot.

On the other side, on Omni I have no audio glitches when playing music with the screen off like I had on mahdi, so I'm quite happy with the shift, though I miss some small features.. Actually most noticeable is a small difference on the lockscreen and it's so annoying..

On mahdi - I've only had omni and mahdi on this device - and early omni when you had the widgets maximized, you could just hold the "minimize" button for a second and it would unlock. Here I have to first push it and then drag the "handle". I don't know why this was removed from omni about half a year ago, but I find it so annoying:p
[G2 Original Android Development] el_tute:
TWRP 2.8 is already out??

I'll need to flash another modem to this rom?

thanks
[G2 Original Android Development] Gandalf:
TWRP 2.8.0.0 builds are up at the same location as the builds, files titled accordingly.
[G2 Original Android Development] Flynny75:
Nope, wipe, flash, boot, sign in, sync, reboot, reboot... Surface flinger still thirsty.

Although, I did see a 1.6A charge speed, although it has now decreased (I presume due to increased battery temps)

Not tried the twrp 2.8 yet
[G2 Original Android Development] Gandalf:
my device just charged from 10% to 45% in about ~30 minutes wasn't paying too much attention to the clock but it seems to be charging at a normal rate. i'll keep looking at this surfaceflinger crap but i'm not seeing it
[G2 Original Android Development] Flynny75:
Have booted in safe mode (hold Restart) to make sure there is no naughty app, and its still high. In DDMS View in Eclipse with Android SDK the CPU usage looks even worse

Also, logcat is full of 'TIME: W/SurfaceFlinger(219): Ignoring duplicate VSYNC event from HWC (t=56959551127)'. (with that last number increasing every line) Do not need to be touching the screen to cause it. Hopefully this is a little more useful for you to investigate with
[G2 Original Android Development] Williek113:
I followed the instructions in the OP. Does anyone know if LS980 has support for NFC? I know its not supported in Mahdi but I've seen it work elsewhere on AOSP roms.
[G2 Original Android Development] Gandalf:
wtf i thought i fixed that... -_-
[G2 Original Android Development] Voje:
I also have an insane amount of that error in logcat..
[G2 Original Android Development] Gandalf:
omfg i had the wrong repo in my manifest.

new builds going up in a few, should fix the logcat spam and surfaceflinger wakelocks (please verify for me)

ok nice new builds going up with the PROPER display hal, as well as a nice, new updated Camera app. enjoy.
[G2 Original Android Development] PunkUnity:
Roms been much better than the FIXED builds previously. Screen wakes right up, smooth. But the battery still drains fast and charges slowly. I'll wait for your new build with the correct repo, Jake! So far it's much nicer! Thanks
[G2 Original Android Development] Gandalf:
New builds up. Have fun
[G2 Original Android Development] Flynny75:
Latest build has no logcat spam and surfaceflinger CPU time is right down. Top notch

EDIT: Charging is also fixed, my 802 is charging at 1.6A again (although, I do expect this to decrease as the battery heats up, hopefully not by much)
[G2 Original Android Development] Voje:
Build feels snappy, surfaceflinger has calmed down, and temperature feels nice; great job!

But my logcat has this sequence which ends in error every 10sec or so though ..

Spoiler content hidden.

I don't know of it causes any problems, I'm just curious :D
[G2 Original Android Development] revan17:
This is by far the best AOSP ROM out there. Smooth as butter. Only bug I see is I get a "DSP Manager has stopped" after playing any song.
[G2 Original Android Development] PunkUnity:
[MENTION=3878813]jakew02[/MENTION] I went to dirtyunicorns.hostingsharedbox.com/jake/omni/g2 and it looks like there is only the first 9/11/2014 build... I don't see an updated one or a TWRP download...

---------- Post added at 07:24 AM ---------- Previous post was at 07:23 AM ----------

I always install Viper4Android and disable DSP manager and disable Apollo music player (interferes with my BT in my car).
[G2 Original Android Development] Voje:
He has deleted the old build, so the 9/11 there is the new one.

It has a build stamp approx 20 hours later than the first one.
[G2 Original Android Development] PunkUnity:
Thought that might be the case. Download now
[G2 Original Android Development] Gandalf:
dsp manager i can up right now actually

the mpdecision stuff, if you look at it, it's not actually error messages, it's just information from mpdecision, every time you touch the screen you should see it fire off some more mpdecision messages :good:
[G2 Original Android Development] Voje:
I was thinking about the file it presumably can't open. Last message.

---------- Post added at 07:21 PM ---------- Previous post was at 07:15 PM ----------

But unfortunately I have to note that the static background noise is worse here than on mahdi...

****ty phone:(

Dr87 spent hours with that issue, but it was lowered somehow; think is was through some changes in mixer_path.xml.

What setup of sound blobs/drivers etc do you use jakew02?
[G2 Original Android Development] Gandalf:
need a logcat ASAP please.
[G2 Original Android Development] Flynny75:
09-12 18:48:25.636: E/AndroidRuntime(4210): FATAL EXCEPTION: main

09-12 18:48:25.636: E/AndroidRuntime(4210): Process: com.bel.android.dspmanager, PID: 4210

09-12 18:48:25.636: E/AndroidRuntime(4210): java.lang.RuntimeException: Error receiving broadcast Intent { act=android.media.action.OPEN_AUDIO_EFFECT_CONTROL_SESSION flg=0x10 (has extras) } in com.bel.android.dspmanager.service.HeadsetService$1@4262bcc0

09-12 18:48:25.636: E/AndroidRuntime(4210):	at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:769)

09-12 18:48:25.636: E/AndroidRuntime(4210):	at android.os.Handler.handleCallback(Handler.java:733)

09-12 18:48:25.636: E/AndroidRuntime(4210):	at android.os.Handler.dispatchMessage(Handler.java:95)

09-12 18:48:25.636: E/AndroidRuntime(4210):	at android.os.Looper.loop(Looper.java:136)

09-12 18:48:25.636: E/AndroidRuntime(4210):	at android.app.ActivityThread.main(ActivityThread.java:5001)

09-12 18:48:25.636: E/AndroidRuntime(4210):	at java.lang.reflect.Method.invokeNative(Native Method)

09-12 18:48:25.636: E/AndroidRuntime(4210):	at java.lang.reflect.Method.invoke(Method.java:515)

09-12 18:48:25.636: E/AndroidRuntime(4210):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785)

09-12 18:48:25.636: E/AndroidRuntime(4210):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601)

09-12 18:48:25.636: E/AndroidRuntime(4210):	at dalvik.system.NativeStart.main(Native Method)

09-12 18:48:25.636: E/AndroidRuntime(4210): Caused by: java.lang.IllegalArgumentException: Effect type: 37cc2c00-dddd-11db-8577-0002a5d5c51c not supported.

09-12 18:48:25.636: E/AndroidRuntime(4210):	at android.media.audiofx.AudioEffect.<init>(AudioEffect.java:411)

09-12 18:48:25.636: E/AndroidRuntime(4210):	at android.media.audiofx.StereoWide.<init>(StereoWide.java:89)

09-12 18:48:25.636: E/AndroidRuntime(4210):	at com.bel.android.dspmanager.service.HeadsetService$EffectSet.<init>(HeadsetService.java:87)

09-12 18:48:25.636: E/AndroidRuntime(4210):	at com.bel.android.dspmanager.service.HeadsetService$1.onReceive(HeadsetService.java:179)

09-12 18:48:25.636: E/AndroidRuntime(4210):	at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:759)

09-12 18:48:25.636: E/AndroidRuntime(4210):	... 9 more

Interestingly, also FCs when disabled in settings

EDIT: That may not be the same crash; I was playing with DSP Manager to see if it has any effect. It doesnt, but it looks like it couldnt do something regarding stereo widening. But it crashes like this when skipping tracks every time.

EDIT2: These lines may also be useful (they precede the runtime exception)

09-12 18:56:14.196: E/MediaPlayer(2753): Should have subtitle controller already set

09-12 18:56:14.236: E/AudioEffect(5928): set(): AudioFlinger could not create effect, status: -22

09-12 18:56:14.236: E/AudioEffects-JNI(5928): AudioEffect initCheck failed -4

09-12 18:56:14.236: E/AudioEffect-JAVA(5928): Error code -4 when initializing AudioEffect.
[G2 Original Android Development] Gandalf:
https://www.github.com/jakew02

don't worry about mpdecision for now. everything is working so i'm not fixing what isn't broken. the cores are behaving and everything is happy so i'm going to leave it as-is for now.

new builds:

back to dr87's blobs

fixed dsp manager due to stereowide library missing

optimizations
[G2 Original Android Development] Voje:
I don't know enough to extract that info from there:) Tried but have up. Saw dr87s name mentioned, so guess you use some of his work, but, well. I really don't know enough to have this talk..

I presume you had to implement his work into Omni, and that omni has different components than mahdi, an that therefor there is a different setup here.

I would f.ex guess that you don't use the same mixer_path.xml as dr87s mahdi builds?

Just trying to brainstorm on an issue I'm sort of familiar with, though not from a developers side:)
[G2 Original Android Development] Gandalf:
it should be fixed with the next build.

also dropped a little surprise in there too :good:
[G2 Original Android Development] Voje:
May I ask what blobs you changed now? And from what?
[G2 Original Android Development] Gandalf:
just changed from aicp blobs back to dr87's blobs
[G2 Original Android Development] Voje:
All of them?I might seem ignorant now, but I'm of the impression that there are specific sound blobs, graphic blobs, etc, or are they not divided and instead one big blob?

My point being that the aicp blobs worked very nice, except from this tiny sound problem, and because of this I started to inquire. Not to be ungrateful, but it wasn't my intention to get you to change vital parts of the system.
[G2 Original Android Development] Gandalf:
New builds going up shortly. Fixed dsp manager and added device settings to toggle knock on AND statusbar knock off.
[G2 Original Android Development] PunkUnity:
Battery life and charge speed are back to normal or better! I don't think I've had any issues minus DSP manager, which I always disable anyways. Awesome!
[G2 Original Android Development] Gandalf:
New builds are up with fixed dsp manager and knock off. Knock on is disabled and the toggle doesnt work but you can manually enable it.

Ill fix that next build

You can manually enable knock on by going to termibal or adb shell and enter

echo 1 > /sys/devices/virtual/input/lge_touch/touch_gesture

well i lost the last game of Madden so while my buddies are playing, I managed to add native support for tap to wake and tap to sleep to the omni frameworks and settings (integrated the checkboxes into Settings > Display at the bottom) eventually I'll move these to an entirely new part of Settings called Advanced (kind of how it is now) and add in vibration settings and screen calibration settings too like CM has. make this ROM like it *should* be.

As of now, this is basically Omni's front-end with updated HALs. i'll start slaying the kernel soon too but i want to get these UI and functionality bugs crushed with fire first.

Im seriously considering dropping support for g2 and jf once L and the new nexus handset drops, depending if its a device im interested in. I could easily trade in my 3 devices to Tmobile or sell on swappa for more than what would cover a new Nexus device, so just keeping everyone in the loop but ill make a decision once the new nexus is unveiled.

I wont leave this broken though ill make sure everything is 100% stable and host a "final stable" build. Ill leep my github trees so anyone interested can take over if they so desire[it wont be difficult since eveything is setup now]
[G2 Original Android Development] revan17:
Where is the new build located? The dirtyunicorns site has the D802 from the 11/09. DSP manager still crashes.
[G2 Original Android Development] errikosd:
Indeed, only the NEW build for D800 is currently up.
[G2 Original Android Development] Gandalf:
Whoops i forgot to run my build script. D800 d801 are up the rest are building and posting now sorry. Dsp manager crash is fixed and the knock on is back to how it was. Im going to have to completely rewrite device settings to be able to use them both

Also you should probably use google camera because the camera hardware sucks in the g2 and the aosp camera app seems to make it even worse
[G2 Original Android Development] PunkUnity:
Rom seems perfect now!
[G2 Original Android Development] Gandalf:
Do we want multirom functionality for the kernel?
[G2 Original Android Development] Lawlrus:
Yes

Sent from my Vs980
[G2 Original Android Development] xeigen:
Is there a command too for Vibration Intensity?
[G2 Original Android Development] Lawlrus:
I swear, this is the only ROM that doesn't have suck-ass auto brightness.

Sent from my Vs980 running Omni 4.4.4
[G2 Original Android Development] PunkUnity:
I've been trying out lux lite app for auto brightness. Definitely better than stock. I'm sure omni is fine but it's always at like 30%, it never changes. Otherwise this build is pretty solid. Keeps freezing and rebooting every couple hours tho... Not sure why. Still have dalvik on, should I switch to ART?
[G2 Original Android Development] Lawlrus:
Worth a shot. I just installed this, so I can't comment much on it. Grab syslog off the play store and start posting logs if you're having reboots.

Sent from my Vs980 running Omni 4.4.4
[G2 Original Android Development] PunkUnity:
Log attached due to many reboots. Not notching, just informing as I really don't care. If I did, I'd restore a known good backup. ?
[G2 Original Android Development] PunkUnity:
And another log... It's getting more frequent
[G2 Original Android Development] pulsation:
Thanks a lot :) Flashed it yesterday. Is anyone else experiencing problems with screen rotation?
[G2 Original Android Development] Gandalf:
Not if you have the right modem
[G2 Original Android Development] PunkUnity:
Does it matter which KK modem we use? My rotation and everything is fine. But, just so everyone is clear on which specific one to use.
[G2 Original Android Development] Gandalf:
Afaik it needs to be a stock kitkat modem. The modified ones to work with old kernels will cause problems
[G2 Original Android Development] Lawlrus:
All 4.4 kernel source Roms are to be using the modems in cloudyfa's android Dev thread for white line kernel fix. The thread is going to be deep in the forum but its in there.

Sent from my Vs980 running Omni 4.4.4
[G2 Original Android Development] PunkUnity:
Cool. That's the one I've been using

---------- Post added at 08:51 AM ---------- Previous post was at 08:50 AM ----------

https://www.androidfilehost.com/?w=files&flid=12880
[G2 Original Android Development] Lawlrus:
[MENTION=3878813]jakew02[/MENTION]

Builds running great. Can't wait for you to tweek it up a bit before shipping off.

A bit off topic, but I'm prying that Verizon will pick up the next nexus, though I doubt it will ever happen. If so, I'll be right behind you.

Sent from my Vs980 running Omni 4.4.4
[G2 Original Android Development] PunkUnity:
I wish I didn't owe so much on my G2.... I want a new Nexus 6 or maybe HTC ONE M9 lol... If that ever happens