In the developers setting there's a function called smallest width. And I've accidentally set it to about 1000 plus. And I can't get into settings because it crashes. Don't want to hard reset any advice?
Everybody now rushes to do the same...
Actually I can't even find that setting.
Sent via open market LG US998 V30/V30+
Related
I am wondering if anyone has successfully used an app to set screen density? I used the app "LCD Resolution" to change from 160 to 190 dpi. I know about the Play Store quirks, etc.
My problem is: This seemed to work fine, all looked good for a while. Now whenever it's set to 190 I cannot connect wifi, and I get certain apps saying I have lost root. Such as the LCD Resolution app, when on 190 and I try going back to 160 tells me I have no busybox and I must be rooted. Root Explorer also will not come on line at this time, even though Superuser grants it access. A reboot, or Backup-restore sets everything back to 160 (cause I never check "set on boot").
I'm trying to figure out why it worked well for about 2 weeks, now I lose wifi and other tasks. Can anyone offer any help or info about how to change density successfully? I mainly need the text larger in the Kindle app. On 160 density and the largest text available, I find marginal on my old eyes! Thanks in advance for any pointers you may have.
Edit: I wiped, and flashed rom again (CM7),, and started over. Uninstalled/reinstalled the density app & all seems back to normal.
I have a weird problem with brightness on one of my devices. Bear with me while I explain.
The device in question is a Nexus7 v2. Android 4.4.4. It's unlocked and rooted, but otherwise stock.
I have this automation app installed called "Llama" - it let's you run certain actions conditionally(kinda like Tasker, but free). (I've looked at both and it seems Tasker is probably more powerful, but I only needed it for a few trivial things like making sure my devices are quiet at night, so I never looked further. Anyway, back ontopic.)
Recently I toyed around with this app and looked at what actions it could do - one of those being Adjust Brightness.
The problem is ever since the first time the app executed this action Android is basically internally always on manual brightness mode even when it's set to automatic.
This is becoming a rather significant usability issue because two of my main use cases for the device are reading books and watching media(videos). Both of these require the app to be able to force brightness levels.
Now however they refuse to do so because they think that Android is on a manual brightness setting.
See the screenshot to get an idea of what I'm talking about.
Things I've tried in increasing order of radicality are: Toggle auto-brightness manually, set brightness to auto via Llama, restart tablet, uninstall Llama.
I've also received no response from the developer, so by now I'm becoming open even to the idea of reinstalling the whole OS.
Of course I'd rather it not get to that as it's rather involved. So I'm open to other ideas.
Bumpity-bump-bump.
martixy said:
I have a weird problem with brightness on one of my devices. Bear with me while I explain.
The device in question is a Nexus7 v2. Android 4.4.4. It's unlocked and rooted, but otherwise stock.
I have this automation app installed called "Llama" - it let's you run certain actions conditionally(kinda like Tasker, but free). (I've looked at both and it seems Tasker is probably more powerful, but I only needed it for a few trivial things like making sure my devices are quiet at night, so I never looked further. Anyway, back ontopic.)
Recently I toyed around with this app and looked at what actions it could do - one of those being Adjust Brightness.
The problem is ever since the first time the app executed this action Android is basically internally always on manual brightness mode even when it's set to automatic.
This is becoming a rather significant usability issue because two of my main use cases for the device are reading books and watching media(videos). Both of these require the app to be able to force brightness levels.
Now however they refuse to do so because they think that Android is on a manual brightness setting.
See the screenshot to get an idea of what I'm talking about.
Things I've tried in increasing order of radicality are: Toggle auto-brightness manually, set brightness to auto via Llama, restart tablet, uninstall Llama.
I've also received no response from the developer, so by now I'm becoming open even to the idea of reinstalling the whole OS.
Of course I'd rather it not get to that as it's rather involved. So I'm open to other ideas.
Click to expand...
Click to collapse
Just wipe data from tablet's recovery mode.
Access Lock is basically a lite version of App Ops, which has existed since Android 4.4.2. It allows you to restrict an app from using some permissions, such as contacts, call log, camera, audio, sms/mms, location, etc. I say lite because it doesn't ask for permissions in real time, but requires that you install an app, open Access lock, and customize permissions before use.
To use Access Lock, you'll need a way to make a shortcut to it's hidden menu. Many alternate Launchers can do this. I used this method:
Install QuickShortcutMaker from Play Store (doesn't require any special permissions)
Top left: change "Incremental search" to "Normal search"
Search for "Access"
Open Settings; look for "Access lock"
Click it, name it, create the shortcut
Open your new shortcut to Access lock and manage your phone
I hear that also works on the G4 and G3, but I can't personally verify that.
Credit: forums.androidcentral.com/lg-g4/544464-app-ops-access-lock-works-g4.html
<rant>
One of the big reasons I'd like root is for Xposed and XPrivacy. I don't like the idea of giving carte blanche to sleazy companies to scrape all my data and sell it to advertisers. If we ever get Marshmallow, it has app permissions management (thanks Google; took you long enough), which should do the trick. Of course the problem with that plan is it hinges on Verizon not being a bunch of goddamn bastards and delaying the update under our Sun consumes this tiny blue dot we call home.
</rant>
I like the idea of using a firewall with root too. I used to do that with my Galaxy Note 2. That phone kicked ass with root!!
Sweet thanks!
Verizon LG V10
I used the procedure in this thread to "debloat" my phone:
https://forum.xda-developers.com/lg-v30/how-to/gadgethacks-com-how-to-remove-bloatware-t3701464
In that thread, I list all of the apps / services I deleted.
I'm about to reset my V30 a second time. This time, it seems I've I lost my Always On Display.
In other threads I've referenced, the lists of "safe to delete" apps from previous LG phones list the LG Clock, com.lge.clock.
However, I'm now suspecting the AOD is reliant on the LG Clock since all of the AOD layouts feature a clock.
I suppose I'll know for sure after I reset again, but can anybody verify this?
Haven't disabled anything on my phone but it would only make sense that the AOD is talking to the/a clock app/service somewhere.
You should use package disabler to figure out which apps are safe to disable or debloat based on your phone setup. It'll save you from having to do a hard reset to get the app back.
Also, would the Clock app be available in LG Smartworld?
Japultra said:
You should use package disabler to figure out which apps are safe to disable or debloat based on your phone setup. It'll save you from having to do a hard reset to get the app back.
Also, would the Clock app be available in LG Smartworld?
Click to expand...
Click to collapse
I searched but didn't find the right version, but no matter. I'm ok with doing the reset again, but exchanged my phone today, starting fresh.
Huh!
It's not LG Clock that's responsible, it's LG Setup Wizard!
I ended up buying and using LG Package Dialer from the as Play Store, but after I disabled everything and rebooted a few times, I never lost Always On Display functionality.
So I began removing one app at a time through adb, rebooting after each command, to identify the culprit.
Now, LG Clock is safely deleted, and my AOD clock continues to work as advertised.
The Nord N100 was found to have a history with the T-Mobile and Metro versions of software to force updates even if "Automatic system updates" is togged off in Developer Options.
Does the XT2093 ever do that? Anyone ever heard of it doing that?
I haven't had any problems with forced system updates per se. While devops option to disable automatic updates COUPLED with the moto system update app set to disallow automatic installation, I find when there is an update it tells me so and I can then perform a manual download and installation. So it works.
Thank you very much for this tip. I need to go in and find that moto system update app and disallow it.
I am having a hard time finding this moto system update app. I see the "Moto" app on my phone but don't see anything in there about system update.
I think I figured it out. You mean this screen, right?
bouyakasha said:
I think I figured it out. You mean this screen, right?
Click to expand...
Click to collapse
Yep that's the screen. I should had mentioned it's a menu option within the Android Settings menu screen and not a launchable app.
Keep in mind as is noted as a footnote in the Smart Update screen, security updates will download and install automatically even if the option is turned off. You might end up seeing a notification saying there's an update ready to be installed and suggesting you reboot the device. Outside of disabling the moto software update app altogether I've found no explicit method of blocking these security updates from auto installing.