Frequently Asked Questions LG Optimus One Device Family
This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.
Q1: How do I root my LG Optimus One?
Rooting can be accomplished with Gingerbreak.apk 1.20 for most devices running stock Froyo ( 2.2 ) and Gingerbread( 2.3 ). There is also Z4Root and SuperOneClick for those instances when GingerBreak doesn't work.
Q2: How do I install a custom recovery?
This is too broad a topic to cover in detail in this FAQ. Please refer to any of the methods listed below...
Install ROM Manager from Play Store. To use ROM Manager you MUST be rooted. Use ROM Manager to install a custom recovery.
Most P500 and P505 models got their official updates. Choose the Optimus One item
The P506 and P509 did not get official updates. Choose the Optimus One (OldBB) item
Device models not mentioned, old baseband models choose the "Optimus One (OldBB)" item. New baseband models choose the "Optimus One" item.
There is also my utility Android Flash Recovery to flash a recovery via fastboot and fastboot mode.
Q3: Why do I have to "trim" my ROMs?
The allocated system partition on any of these devices is only 190 MB. Not really huge. However since Android 4.0, the space required for everything has increased to a point that it will almost completely fill the system partition only leaving a few KB free. OOne ROM Editor is a Windows utility designed specifically for this task.
Q4: I've flashed ( any ICS or JB ) ROM and Google Apps. Why doesn't my Home and or Search button work?
Did you trim the ROM prior to installation? If not, see question #3 above.
Did you wipe your /cache and Dalvik cache prior to the ROM installation?
Q5: Why doesn't Link2SD work with CM10+?
There are several reasons. There is an actual procedure required in order to get Link2SD to work properly with these devices.
The ROM must be trimmed prior to installing or immediately after installing on to the device. See question #3 above.
The biggest issue with Link2SD is the lack of free space on the devices system partition. I recommend a minimum 1024 MB ( 1 GB ) partition on the sdcard, formatted as ext4.
Now install Link2SD. After it installs, open it and let it create it's mount scripts.
Reboot device. On this first boot Link2SD will create it's symlinks and move whatever files it needs to move.
Reboot device once more for good measure.
From here, assuming that you have removed enough from the ROM when trimming it, the Google Apps package should be installed via your preferred recovery.
Reboot. You should see a "Android is updating apps" notification as the ROM starts.
Q6: How can I get rid of Link2SD before migrating to another *2SD script?
Link2SD installs scripts etc. in 2 places
/system/etc/init.d
/system/etc/install_recovery.sh
Delete both mounting scripts and delete the /data/sdext2 folder to get rid of Link2SD. For credit and more details please see this post.
Q7: I have installed CM10.1. What happened to the Developer Options?
On the device, go to Settings -> About Phone. Scroll to and tap on the build number 7 - 8 times until you get a toast notification that states that Developer Options are enabled. Press the "Back" button. A Developer Options item should appear in the main settings list, usually just before About Phone. Press the Developer Options item and then enable Developer Options with the toggle at the top of the page.
Q8: I'm running CM10.1. Where is the advanced power menu?
If Developer Options are not enabled, see question #7 above. Go to Settings -> Developer Options and enable "Advanced Reboot".
Q9: I just flashed a ROM and I have no network. What should I do?
All ROMs from CM7 and newer are built for new baseband. This is more than likely because of the wrong baseband. The P509 and P506 are old baseband devices. P500 and P505 devices that didn't get the official update are also old baseband. You can flash the old baseband patch via CWM or any other recovery to remedy this problem. Please see post #8 for the old baseband patch.
It is also possible the the APN for your carrier is either not set up or is incorrectly set up.
Q10: What is the best method for installing a ROM?
In my opinion it is always best to perform all wipes, even when upgrading the same Android version, although it is not really required when upgrading. The following steps are assuming that you are using CWM.
Boot device in to Recovery. If you don't have a custom recovery, please see question #2 above.
Perform "Wipe data/factory reset". This will format the /data, /cache, /sdext, and .android_secure
Select the "Advanced" option and on the next screen select "Wipe Dalvik Cache". Confirm the wipe.
Not necessary but I do it anyway, in the "Advanced" screen select "Wipe battery stats" and the confirm that wipe
For a clean installation I recommend formatting the system partition too. From CWM home screen select "mounts and storage". On the next screen select "format /system" and then confirm the format.
Press the back button until you are back in the CWM home screen. Select "Install zip from sdcard" and then select "Choose zip from sdcard". Browse your sdcard for the ROM to install and select it. Confirm the installation. Now wait for the install to finish.
Go back to CWM's home screen. Select "reboot system now" option and let the device boot. The initial boot will take a couple of minutes. Don't panic.
If you intend to install any patches or Google Apps, reboot device into recovery and repeat step 6 for each additional package to install.
Q11: How can I make Voice Search work with Google Now in JB roms?
I have gathered links to several posts regarding this, and they can be found here
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum. A special thanks to everyone who contributed to the production of this FAQ
Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread. More Frequenty Asked Questions and their answers are welcome here and I will add them to the OP.
"Those who know don't need to be told and those who don't seldom listen."
Q: How can I get rid of Link2SD, before migrating to another *2SD script?
A: Link2SD installs in 2 places, /system/etc/init.d & /system/etc/install_recovery.sh
You need to delete them both mounting scripts, and also delete the /data/sdext2 folder to get rid of link2sd...
XDA-Developers was founded on the simple principal that SHARING IS GOOD and when many people SHARE what they know, EVERYONE benefits. We exist upon this Ethos, we RESPECT each other, we SHARE with each other, we do not judge one another and we HELP all who ask. We believe that while some may have more knowledge than another, none are more important.
----------
We need a list of working *2sd with cm10/10.1
Does this F.A.Q. meant to be only for cm10/10.1?
No. It's not meant for any specific Android version at all. This FAQ is still a WIP. This FAQ is intended to be a starting point for new members. It is not designed or intended to go in to too much detail about anything. Questions with lengthy answers are answered in short form when possible. If more explanation is needed, then a link or links will be included to direct the member to the correct thread.
As for what you have stated, I will see what I can come up with. Some of the *2SD scripts can be problematic setting up and require special details. Link2SD and Mounts2SD are two problematic ones right off the top of my head.
Thanks for the suggestion.
"Those who know don't need to be told and those who don't seldom listen."
Hey Bill, I just now figured out what dovidhalevi was talking about. The link that I posted above works. But the copied link that you posted does not. Gotta love this great software. Got no choice.
The default boot animations on any device, no matter whichmanufacturer, are generally pretty … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?