Jump to content

Trym Hansen

  • Content Count

  • Joined

  • Last visited

Community Reputation

4 Neutral

About Trym Hansen

  • Rank

Profile Information

  • Your Current Device(s)
  1. Is there any way to stop the PackageManager from "unpacking native libraries for ..." <every installed app> every boot? This would help tremendously on the boot time.
  2. Ext4, r28 kernel. Saw the same thing in GR5 if I'm not mistaken. Everything seems to work, but I guess you want to mount stuff "your" way.
  3. Yeah. LG will cut off the server at some point, cannot remember the date. Anyway: ?:??: W/?(?): --------- beginning of /dev/log/main 01-18 10:38:49.637: I//system/xbin/busybox(1050): mount: mounting /dev/block/mmcblk0p8 on /data failed: Invalid argument 01-18 10:38:49.647: I//system/xbin/busybox(1050): mount: mounting /dev/block/mmcblk0p1 on /system failed: Invalid argument 01-18 10:38:49.647: I//system/xbin/busybox(1050): run-parts: /system/etc/init.d/98mounts exited with code 255 01-18 10:38:49.797: I/logwrapper(1050): /system/xbin/busybox terminated by exit(1) ...something up with the init-scripts.
  4. Haven't tested it yet, but I can at least tell you that LG has phased out the "App Advisor", so I guess it should be removed from the kitchen as well.
  5. Most likely the latter. For the update procedure to work you need to have the stock recovery installed. If you have installed FR19, you did so by installing CWM first, which is a replacement-recovery. The original recovery can be found somewhere in this forum as a flashable CWM-zip. EDIT: The easiest way to update is to use smartflash to flash an entire stock ROM first. This will basically restore your phone to a factory-fresh state. Then update.
  6. That's only half-true. The RIL is part of the rom, it's a linux library file (akin to a .dll in windows) called lge-ril.so. (in /system/lib) The BB doesn't get touched when flashing a ROM (via CWM), that's true.
  7. The screenshot-function is disabled while the lockscreen is on, so here's a bad-quality photo instead. They look a little different along the bottom, and along the edges. This one also shows your background "through" the "glass" while charging, the old one shows only black while charging. The biggest difference is the animation though, this one is smooth.
  8. in build.prop, set user.feature.lock_andy=false user.feature.lock_sui=true
  9. Ah, ok, that makes some kind of sense then. Ok, agreed, that was a user-bug, not LGs.
  10. Really? Including the useless checkmark? Funny you say that about e-mail, because I always install the email-app from CM7, and it works perfectly. No trouble with deletions there. (There was a known bug in the AOSP 2.1 e-mail, which I think LGs e-mail app is based on. A bugfix was released by google, but not taken up by LG.)
  11. Of course. Installed 20L some hours ago. Another very strange thing is that although they've made a new lock-screen, which is both prettier and smoother, it's not enabled by default. Which seems to me like this version wasn't intended for release either, but that someone at the top just said "Do it! Now!".
  12. They've learned nothing. All the bugs present in 20j are here in 20l. 1) E-mail app doesn't delete properly from ActiveSync server. 2) USB-icon disappears when activating USB-storage. (This worked in 20c!) 3) Application manager lists all your apps on /data as installed on SD-card, with a useless checkmark next to the titles (which you cannot click or select.) 4) Used country-code instead of language-code for Norwegian (and I suspect more languages). 5) On screen phone stops working about an hour after boot. All they've done is take their existing source-code tree, including all bugs, merged it with GB and added localized keybards. They've not tried to fix a single bug, but introduced a few more instead. Don't get me wrong, GB is in itself a worthy upgrade, but LG is still useless when it comes to software.
  13. The lines we're talking about are these: on property:dev.lge.ccd.cleanup=1 rm -Rf /data/dalvik-cache mkdir /data/dalvik-cache 0771 system system chown system system /data/dalvik-cache chmod 0771 /data/dalvik-cache in the init.tegra.rc script in the ramdisk-image in the boot-image. Unfortunately editing those scripts is pretty involved, you need to uncompress the boot-image into its seperate parts, uncompress the ramdisk image, edit the files, and then put them all back together again. Believe me when I say it is much easier to download and install a version which already has those lines removed. The only other advice I can give is to make sure you wipe dalvik-cache after installing or restoring a kernel.
  14. OK, then we conclude the init.d problem is fixed. However, most kernel-installer scripts these days use the anykernel updater. It decompresses the existing kernel and takes the existing ramdisk and merges it with the new kernel. That means that after installing neoblaze or Horsepower, you still get the long boot times. EDIT: You beat me to it, Kostja. Yes, they need to bake with a custom kernel if intending to replace the kernel. Not a problem if you know about it, but if you don't...
  15. Then you have added the required line to init.rc in the the kernel ramdisk-script at some point. I was the one researching this, and the "start sysinit" line was definitely missing from the ramdisk init.rc script in GR4 some days back.(If baked with the stock kernel that is. If baked with custom kernel it was there.) Besides, it also looks like you didn't remove the dalvik-wipe lines from the init.tegra.rc when baked with a stock kernel.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.