08-07-2017 10:49 PM
1,625 ... 4950515253 ...
tools
  1. syguyice's Avatar
    Took a while to backup and prepare, but finally did the dalvik patch (thanks) while resizing partitions. Have not noticed freezes yet; no improvements to other issues. Another thought after big's reply; the major difference between our phones is that mine is sprint. I would likely need to wait for the updated sprint patch for fix my wifi issues.
    bigsupersquid likes this.
    10-04-2014 09:39 PM
  2. bigsupersquid's Avatar
    Does anyone know why Google+ keeps force closing?
    yes, google proprietary builds are somewhat crap nowadays. Mostly armv7 stuff. earth never ran on armv6; google+, maps need old versions; search doesn't completely work without turning off voice controls;
    buried in this thread is a link to the last working (armv6) release of G+ mentioned by the p500 guys.
    10-05-2014 03:24 AM
  3. bigsupersquid's Avatar
    ugh
    bringing skinny gapps up to date totals 42MB. The current gms core the phone updates to is over 25MB alone.
    It'll just fit on internal on a V but I dunno how to do it on an S. Probably have to use the oldest skinny gms core and just let it update manually after signing in.
    10-05-2014 09:41 PM
  4. siryoink's Avatar
    sprint patch is messed up, but it should only mess up messaging.
    Can you post a logcat to pastebin?
    oh, and thewraith420 would know better, but maybe you need the zvd-zvj patch:
    I'm currently running the ZVJ radio, but I've had to switch between the two to try various roms. From the mention of it in the OP, I assumed yours was using the ZVJ baseband? I'm currently running ZVJ based Danterom. Also, I've already flashed back, but if there's a log file needed I can try again and post the log here. What directory is the logfile stored in?

    My post count isn't high enough to link it here, but I'm going to PM you a link to a fix I've used when I've broken MMS messaging on my sprint phone flashing other ROMs. Might be what's needed to fix it in yours for Sprint phones.
    10-06-2014 01:29 AM
  5. bigsupersquid's Avatar
    Ah, baseband.
    Optimus V runs on zv4 zv5 and zv9 or can be forced to sprint basebands with much hassle.
    Zvj needs new ril system files i think.

    The sprint/verizon/ting etc mms fix, if you want to patch it in manually before i get around to fixing it:

    Use the old fix as a donor. Put eri.xml from data zip folder to /data (and copy system/usr/keylayout over too if your menu/home buttons are reversed.)

    delete /data/data/com.android.providers.telephony/databases/telephony.db

    Open your current build.prop and only change the carrier lines to match the build.prop in old fix.
    Sprint version:

    ro.cdma.home.operator.alpha=Sprint
    gsm.sim.operator.alpha = Sprint
    gsm.operator.alpha = Sprint
    ro.cdma.home.operator.numeric=310120
    gsm.sim.operator.numeric=310120
    gsm.operator.numeric=310120

    Make sure to chmod 644 the fixed build.prop before rebooting.

    Anyone willing to post working prop settings for ting or others, I'd be appreciative.
    I have plans to put carrier in the settings instead of this hassle but need more complete info to minimize debugging.


    newest sync fixes lockscreen text centering that was bugging y'all. internal running fine. release soon.
    10-06-2014 07:02 AM
  6. BradN2's Avatar
    I *think* the main difference between sprint and ting is picture messaging settings: https://help.ting.com/entries/229455...nlisted-Device

    Then again I'm probably not the best person to ask; I don't remember ever having it fully working correctly
    bigsupersquid likes this.
    10-06-2014 08:16 AM
  7. nitestalkr's Avatar
    I made the switch to os2sd a couple weeks ago, and after using f2fs for sometime now ive noticed the RAM becomes completely used up after installing a small handful of apps. At most I see an average of 8-15mb free RAM space, and this causes some serious sluggishness. I'm OC'd at 864/640/performance, and threw on Pure performance, but haven't had much of an improvement. Is there anything I can do to severely clean up some RAM space without having to uninstall any apps, or manually stopping apps from 'manage apps' in settings(only able to reach ~40mb free after stopping everything), any mods/zip fixes i can use?

    Sent from my LG-VM670 using Tapatalk 2
    10-11-2014 06:09 AM
  8. bigsupersquid's Avatar
    I made the switch to os2sd a couple weeks ago, and after using f2fs for sometime now ive noticed the RAM becomes completely used up after installing a small handful of apps. At most I see an average of 8-15mb free RAM space, and this causes some serious sluggishness. I'm OC'd at 864/640/performance, and threw on Pure performance, but haven't had much of an improvement. Is there anything I can do to severely clean up some RAM space without having to uninstall any apps, or manually stopping apps from 'manage apps' in settings(only able to reach ~40mb free after stopping everything), any mods/zip fixes i can use?

    Sent from my LG-VM670 using Tapatalk 2
    it's not just f2fs, the internal I've been trying has the same ram hogging issue.
    try this zip forlatest f2fs version.
    http://forums.androidcentral.com/opt...ml#post3929137
    not perfect but helps a little.
    10-11-2014 07:56 AM
  9. badblue1__'s Avatar
    I made the switch to os2sd a couple weeks ago, and after using f2fs for sometime now ive noticed the RAM becomes completely used up after installing a small handful of apps. At most I see an average of 8-15mb free RAM space, and this causes some serious sluggishness. I'm OC'd at 864/640/performance, and threw on Pure performance, but haven't had much of an improvement. Is there anything I can do to severely clean up some RAM space without having to uninstall any apps, or manually stopping apps from 'manage apps' in settings(only able to reach ~40mb free after stopping everything), any mods/zip fixes i can use?

    Sent from my LG-VM670 using Tapatalk 2
    Have you tried the Fast Reboot app? https://play.google.com/store/apps/d...tes.fastreboot Makes my phone much snappier, helping the low ram problems with our phone, andy swore by this little app and was a requirement using the [MOD] Bean_Whiz .
    nitestalkr likes this.
    10-11-2014 12:33 PM
  10. bigsupersquid's Avatar
    Have you tried the Fast Reboot app? https://play.google.com/store/apps/d...tes.fastreboot Makes my phone much snappier, helping the low ram problems with our phone, andy swore by this little app and was a requirement using the [MOD] Bean_Whiz .
    +1
    when using play it's one of the first things I grab. or sideload it from backup.
    watching ram meter, fast reboot is at least as effective as manually closing all running apps.
    badblue1__ and nitestalkr like this.
    10-11-2014 01:09 PM
  11. nitestalkr's Avatar
    I started usimg RAM Booster from Xposed Installer, but I guess it wasnt really doing much. I forgot about fast reboot. I'll try it out again and see how well it works out with my usage.

    Sent from my LG-VM670 using Tapatalk 2
    badblue1__ likes this.
    10-11-2014 02:50 PM
  12. bigsupersquid's Avatar
    I started usimg RAM Booster from Xposed Installer, but I guess it wasnt really doing much. I forgot about fast reboot. I'll try it out again and see how well it works out with my usage.

    Sent from my LG-VM670 using Tapatalk 2
    that post I linked to a couple back has a fix of sorts.
    again:
    http://forums.androidcentral.com/opt...ml#post3929137
    dalvik props, oom settings, minfree settings to mostly match v6 supercharger.
    it holds my ram 35-45% with no apps open. ram over 75%, oomkiller actually starts working, see it in logcat.

    like I said, not perfect, but helps a little. flash over last f2fs rom in recovery at any time. any other rom version, the build.prop in zip will bork it up. you can use it with older f2fs version if you pull build.prop and just manually copy dalvik props over to the build.prop in that rom.
    remember chmod 644 after any manual kitkat build.prop changes to avoid bootloop. the zip does it automagically.

    I believe that some MB of that used ram is gobbled persistently, immediately by system at boot, as loop-device ramdisks.

    and fast reboot, has been great since ics. in jb, I pretty much had to have it to avoid major lags.
    gotta run it whenever you notice issues, though.

    on the same note, long-press the home button and either swipe away background apps (or press the 3-bar button in the upper right corner to clear them all.) I see the ram usage immediately go down by nearly as much as fast reboot gives.
    fast reboot, however, restarts hidden apps like gms services and such, so can do a better job... or make your device crash if it's OC'd too high for its britches.
    badblue1__ and nitestalkr like this.
    10-11-2014 04:52 PM
  13. nitestalkr's Avatar
    I flashed that zip, and I will report back in a couple days of use.
    I also assigned fast reboot to a pie control through GravityBox from Xposed installer for convenience.

    Sent from my LG-VM670 using Tapatalk 2
    bigsupersquid and badblue1__ like this.
    10-11-2014 06:26 PM
  14. bigsupersquid's Avatar
    Google really has it in for low-storage devices.
    [APP] [SHARE] Google Play Services 6.1.71 | Android Development and Hacking | XDA Forums

    the latest is a whopping 32MB for the armeabi version. Not even caught up to the 160 dpi armeabi version yet! be bigger.

    there is just no way that internal installs will be able to keep up with gapps. huge even to sideload.
    even with link2 stuff, you need a tolerable card or you'll get slowdown linking gapps.

    on the bright side, the newer gmscore uses less RAM. like, 10% less. Yay!
    10-11-2014 06:57 PM
  15. nitestalkr's Avatar
    Thats one of the reasons why i dropped the internal build for the os2sd. It began to look like the end of the road for it the way gapps was going.

    I'm running off a 32GB class 10 UHS-1 Samsung microSD card that i picked up for ~$26 at wally world. I had to make a choice between this and a sandisk card of the same class and UHS boost. Only a 1 dollar difference, so i went for the samsung which had slightly faster read speeds (48mb/s vs 42mb/s).

    Sent from my LG-VM670 using Tapatalk 2
    bigsupersquid likes this.
    10-11-2014 07:28 PM
  16. omgitsMATT's Avatar
    I gave my phone away to a 14 year old sister who still lives at home and I think she either dropped it or got it wet, but just in case it's software related does this sound familar to anyone?

    When the phone turns on it shows the LG screen, then powers off immediately. Then powers on, then off, then on. Always showing the LG logo when powering on for only a moment. It won't even charge.

    Is it perhaps the ''Art'' that was enabled and talked about in the original post, or is it that she dropped it or got it wet or both?

    Edit,

    I can't even boot into the recovery. I'm going to Google how to unbrick a hard bricked phone like this, hopefully some older threads will come up. I might get to learn something while I'm at it
    10-12-2014 06:31 AM
  17. nitestalkr's Avatar
    It sounds like 1 of 2 things:

    1: sounds like the charger cable or the phone port may be damaged. Try either wrapping the wrapping over the screen of the phone, or pushing slightly, in any direction, till it boots further, and wrap the cord around the phone in that direction. You can also try other chargers.

    2: it might be water damage to the battery. There is a water damage indicating sticker near the metal connectors on the battery(if it's pink/red there's water damage). You can try purchasing a spare battery from amazon, and see if it fully boots. There are some inexpensive batteries that you can find there.

    If neither of those work, then the phone may be damaged beyond repair.

    Sent from my LG-VM670 using Tapatalk 2
    bigsupersquid and omgitsMATT like this.
    10-12-2014 07:36 AM
  18. bigsupersquid's Avatar
    I gave my phone away to a 14 year old sister who still lives at home and I think she either dropped it or got it wet, but just in case it's software related does this sound familar to anyone?

    When the phone turns on it shows the LG screen, then powers off immediately. Then powers on, then off, then on. Always showing the LG logo when powering on for only a moment. It won't even charge.

    Is it perhaps the ''Art'' that was enabled and talked about in the original post, or is it that she dropped it or got it wet or both?

    Edit,

    I can't even boot into the recovery. I'm going to Google how to unbrick a hard bricked phone like this, hopefully some older threads will come up. I might get to learn something while I'm at it
    lg logo good. means not bricked.

    battery too low to boot.
    unless you have another way to charge it you'll have to be tricky.

    plug it in.
    hold recovery keys as it reboots.
    don't let go until recovery starts.

    that trick should work even if the battery is so fried out it won't hold a charge, or even if it's flat dead and won't even power on. As long as the battery is present it should boot to recovery this way.

    let it charge in recovery to at least 15%.
    nitestalkr and omgitsMATT like this.
    10-12-2014 08:20 AM
  19. bigsupersquid's Avatar
    I have adblocking working with CrossBreeder!
    turns out dnsproxy2 was only built for armv7 all the sources I could find (not many, either.)
    I fixed sources (at least enough to build and run, not sure how perfect that really was)
    Now I have kitkat CrossBreeder adblocking with blank pixels instead of ads. It's beautiful.
    I will share soon.
    Plus I tweaked fivefour's CrossBreeder app to handle three more switches. It fixes the usb tethering, too. If it was broken?

    CrossBreeder with armv6 dnsproxy2 here.
    the app is here. install CB first. then the app.
    click the switches instead of swiping them or it won't change the settings.

    oh, and don't bother trying to install CB on internal unless you aren't using gapps or it won't all fit, then it'll cause a bunch of glitch-ues.

    //edit edit
    after running this for about a day, I highly recommend giving it a try on os2sd.
    the browser improvements alone make it worthwhile. the adblock affects apps as well as the browser.
    my ui isn't lagging anymore either.
    ram usage doesn't seem affected.
    10-12-2014 04:16 PM
  20. bigsupersquid's Avatar
    ...
    on the bright side, the newer gmscore uses less RAM. like, 10% less. Yay!
    and, no gapps installed at all, ram sits steady at 33% and hangs under 50% with several background apps.
    eek.
    10-12-2014 04:32 PM
  21. omgitsMATT's Avatar
    New battery fixed it, you still got it
    10-13-2014 05:39 PM
  22. omgitsMATT's Avatar
    Yep, water damage to the battery. Thanks
    bigsupersquid likes this.
    10-13-2014 05:40 PM
  23. bigsupersquid's Avatar
    I thought the CB tetherboost fixed the usb tethering but it was a recent repo sync that did that instead.

    I really need to get y'all a new set of builds up.
    The amount of rampaging I had to do on /system/app to make the internal fit, though, I'm afraid it's going to be the last internal build until I integrate enough multirom to fallback to the internal partitions when the card isn't right. Making something that can't even support all the hardware in the phone bugs me.
    10-14-2014 08:36 AM
  24. BradN2's Avatar
    Did you look into UPX'ing at all?
    10-14-2014 12:51 PM
  25. bigsupersquid's Avatar
    Did you look into UPX'ing at all?
    well, it's not already android native, and I can't really justify porting something into the system just to maintain an older format I don't even use myself...
    It does look interesting, but there's a kitkat/ (L? if aav6 ever touches up ART the rest of the way) issue:
    from the docs
    In SELinux "strict enforcing" mode (the most restrictive), generating
    new instructions at runtime is not allowed at all: any page with
    PROT_EXEC permission must be mapped from a file in a mounted filesystem
    that has 'x' [eXecute] permission, and the generation of such files is
    also tightly controlled. A program that was compressed by UPX will not
    run in SELinux strict enforcing mode. Attempts will fail with exit
    code 127, and a record will be added to the history file
    /var/log/audit/audit.log.

    In "targeted enforcing" mode, SELinux pays close attention mostly to
    designated processes that run with elevated privileges: web server,
    print server, login server, etc. Ordinary user executables receive
    much less scrutiny. However, one of the eventual goals of SELinux is to
    eradicate runtime generation of instructions because of the possibility
    for exploitation by malware (virus, trojan, key logger, privilege
    elevation exploit, etc.) Thus targeted enforcing mode notices and
    logs the use of "execmem" capability that is used by a program which
    was compressed by UPX. In keeping with the goal of eventual prohibition,
    SELinux ordinarily would deny execmem. However, most current SELinux
    systems, including Fedora Core 5 [set for release March 15, 2006],
    override this with "allow_exemem=1" in /etc/selinux/targeted/booleans.
    Thus a program compressed by UPX will run in the default installed
    configuration (targeted enforcing, allow_execmem=1) of SELinux under
    Fedora Core 5. Each invocation will add a few lines to the log file
    /var/log/audit/audit.log, one line for each use of execmem. If the
    SELinux policy becomes more restrictive in the future, then a special
    SELinux class or other mechanism must be created for compressed programs,
    or else UPX-compressed executables will not run then.

    In its "permissive" modes, SELinux just logs the potential problems,
    but otherwise does not interfere. A program compressed by UPX will run
    in any permissive mode.
    I lost permissive mode a while ago... it starts that way but the system takes over and turns it enforcing, even with the kernel config set to non-enforcing.
    10-14-2014 01:08 PM
1,625 ... 4950515253 ...

Similar Threads

  1. Is moto x camera good for a vacation?
    By AImbriano in forum Moto X (2013)
    Replies: 19
    Last Post: 02-09-2014, 09:21 AM
  2. Case for Note 3 with the wireless charging battery/back cover
    By DocGo in forum Samsung Galaxy Note 3
    Replies: 1
    Last Post: 01-31-2014, 08:45 AM
LINK TO POST COPIED TO CLIPBOARD