Search results

May or may not be because of processor, but I'm assuming it's not because you're rooted?

How did you get the -240 version? Can you upload it to apkmirror.com for us if you do have it?

If disabled, your phone will still work the exact same for location and location history. The location by Android System is probably used by CarrierIQ, the nasty spyware that plagued the G3. Android System is not the same as Google Play Services. Leave everything on for Google Play Services...

App ops lets you control what permissions applications have access to.

First of all, I can guarantee you that there will not be an xposed module that will let you completely change how the quick settings work. There will be an xposed mod coming out soon that will let you change the colors and such with the quick settings. Secondly, essentially all custom ROMs for...

I think the issue needing a fix should be how LG programmed the notification bar to work. One pull brings down notifications and quick settings? Because of this, notifications cannot be expended unless you then swipe up just the quick settings and try again. IMO, LG is also bad at coding stock...

Okay that answers my question. Guess I'll just wait for a bootloader unlock/exploit to flash a custom ROM. Or a build that completely fixes the touchscreen issues. If only LG cared about the modding community and just gave us an unlock method. I mean we bought the phone, they got their money...

I'll give the situation a see if anyone else has done this and what the outcome is: Rooted 10G currently, xposed installed and all. If I flash the new updated rooted image, I'm assuming there will be no loss of data and xposed will still remain in tact. Can anyone confirm?

I've been using this for a couple days so far, and I wanna say that it has impacted slightly but I'm still unsure. For right now, I'm gonna give it another couple days and see.

I originally posted this in an existing thread, and considering other users reporting it actually helps, I figured I'd start a new thread specific for this. I want to share what I found, considering it has helped a bit with the issue. The missed taps and all still happen, just not as often...

If you back out of CPU settings and go back in, they should show as what you set them to. But, when you reboot, they do go back to default (mine does the same thing too). Not sure if its a bug with the app or something else.

I want to share what I found, considering it has helped a bit with the issue. The missed taps and all still happen, just not as often before I made these changes. WARNING, do not adjust values that you are unsure of. Setting any of the following values lower than default will cause touchscreen...

What version of TweaksBox are you using?

So two things need to be done about this: A) Does the update break root/can the update be done with root. B) Someone with the touch issues should take the update and see if it fixes said issues. I'm almost positive that at a mere 46MB that this may not include said fixes, but it's worth...

What I would prefer is that someone who has touch issues on a model with a custom recovery, to flash another ROM and see if the issue persists. Because my LG rep told me it's software and a fix is in the works, I'm gonna believe that there is no hardware issue. And hopefully because of this, a...

When you click the "flash" button to start the process, is the screen supposed to go black and stay black through the entire process?

You just made my day

So the AT&T variant doesn't have an unlocked bootloader, and can't install twrp, so can't flash xposed or a different ROM. If its software, a different ROM (ie CM) should fix it. Did you disable the stock LG launcher as well? Or any other LG apps/services?

I had the same issue you're having. If you're rooted, it's an easy fix. Download any app ops application from the play store, and go in and disable the location permission for Android System. Has no effect on the device knowing your location whatsoever, and fixes the wakelock/battery drain from...

Nope, not needed. Just turn off auto download mms in your preferred sms app and you'll be fine.

Stagefright is the name of the media player. It isn't the name of the exploit. The exploit takes advantage of the stagefright player, hence its name.

Anyone find any other changes or lines to add that help? I was gonna try these next and see what I get: debug.performance.tuning=1 - (Increases touch responsiveness) video.accelerate.hw=1 - (Increases touch responsiveness) And did anyone try tinkering with the values for the #####touch...

There's an ambient light sensor, used to detect your ambient light and adjust brightness automatically (given you have auto brightness turned on). Right next to it is a proximity sensor. The same thing that turns your screen off when you put your phone to your head when on a phone call...

Proximity sensor, FYI.

It's a grounding issue I believe. Not sure what kind of fix is needed, but I believe it could be done through software. And BTW, mine bugs when I try it on a table or other surface, but when in my lap or touching my body somehow it works flawlessly.

Just curious, but anyone here using the H810 (AT&T) model, and applied these changes?

No booting problems? And how did you go about putting it in your build.prop? Was it a simple copy/paste in the very end of the file? Or was there something extra needed? I haven't gone as far as to adding text to the build.prop before, so I want to be sure its done right.

Not sure about the sound, but you know you can double tab the notification bar to turn the screen off, correct?

I can confirm from my regional LG Rep that it's a software issue, and a fix is in the works. He says the team knows about it and a release for a fix could take about 4-6 weeks. So, if what he told me was correct, this means flashing a custom ROM should also fix the issue, cause its software...

What other values can you set it to? I'm on AT&T and it worked when switching to "OPEN", but I'd prefer the stock Android status bar. It exists in the systemui.apk, so there must be a way to enable it.

So can anyone here confirm if having a locked bootloader device, AT&T model, XT1097, running 5.0.2, will work using this method? And if so, does it work using the exact same link in the OP? Or should I use the link for the XT1097 on the CF site? I need this more than anything right now.

Mine does the same thing. I'll try with a different charger and stuff later, but just thought I'd let you inow that the two of you arent alone. It doesnt bug me. Normally when my phones charging I'm not using it.

On the lockscreen, the carrier text isnt in the correct spot. Its supposed to be all the way in the top left corner, not an inch away from it. Also, on random occassions my phone wont register touch on the lockscreen. I have to continuously tap and swipe the screen in random spots before it...

I'm on the newest nightly (11/26) and i got my first kernel crash. Usually i have bluetooth on 24/7 with my moto 360, but this time I didnt. Turned my screen off, put the phone down for 8 seconds, and when i hit the power button i got a kernel crash.

Some bugs i have so far: -Location gets stuck to high accuracy in status bar. -In quick settings, tapping the user icon doesnt open the menu to select/add a user, instead it pulls up your local profile. -NFC (we know) -Screen casting doesnt work cause devices dont shoe up (not sure if its...

Plugged phone in to wall to charge, and doesnt recognize its charging. Percent goes up, but doesnt reflect it charging anywhere on the phone (icons and such) ---------- Post added at 06:07 PM ---------- Previous post was at 06:02 PM ---------- Reboot fixed. Other than that, awesome work...

I'm gonna guess a dirty flash of the new build is good, yes?

That sync loop thing is on CM as well (which I'm running) and still connects to my device just fine. I contacted Google support just to see what it meant and the guy was extremely confused. He said he would email me in a couple days when he got an answer. Maybe if I get a definite answer as to...

Sorry, didn't know what dt2w stood for.

Is there double tap to wake in this rom?

That's actually a bug in KitKat that I've seen on my Nexus 7, Moto X, and LG G3 running both stock and CyanogenMod. Don't know why Google never really looked into this. I wonder if it's fixed in Lollipop

Care to give me some directions? Permissions for what?

So I finally did it. Flashed this bad boy and I'm up and rolling! First, the ONLY issue I have now is sometimes the Google Play Store can't download something, and displays an error. I can keep trying and it works eventually. For the things that I thought wouldn't work but do, here ya go...

Free candy for anyone who can convince me to flash this bad boy right now lol I'm impatient but trying to hold back for a bit longer (for some reason). My brain keeps saying "What if..."

Okay I gotcha. I usually enjoy testing and reporting stuff like this, it's just cause it's my primary and daily device that I don't want to run a risk if I can't return to stock. Are you gonna be the person who works on new builds? Just so I know who I should report to if/when I get this installed

Okay. I'm just a bit hesitant because of the issues everyones been having. When I backup my current rom (stock) in TWRP, what do you suggest I check to backup? I've done this before with multiple nexus devices but I've always used CWM which just has a backup option and doesn't let you check...

So since the kernel crash has been fixed, do you recommend this as some sort of a daily driver yet? Like what doesn't work that you know of?

First let me start by saying thank you so much for all the hard work you've done. Now, I'm going to assume that I can take the original ROM zip and replace the included boot.img with this new (and fixed) boot.img and flash the ROM. I haven't flashed it yet and I'm still on stock LG cause of the...

I already have that one installed. Im talking about the newer android lollipop one, not the older version.

I know there's one "Android L" nav theme, but does anyone know where I could get the newer Android Lollipop nav bar? The buttons are more spread out and a bit smaller than the original Android L build had.