[LG Optimus 2x] Topogigi:
Topogigi O2X GB Stock Mod FAQ

Ladies and gentlemen, guys and gals, experts and noobs, here you will find a F.A.Q. collection for our ROM. Hope it will help.

TOPOGIGI O2X STOCK MOD FAQ

Q1. App XXX does not work with YYY launcher. Can you please check and solve this issue?

A1. Sorry, only the apps and the launcher included in this ROM are supported. I cannot and I will not support other apps or alternative launchers. But you are naturally alowed to try any app and any launcher at your own risk.

Q2. Can you please add the XXX app (feature) to your rom [Variant: Can you please remove the XXX app (feature) to your rom?] I really love [hate] it and I cannot live without [with] it.

A2. This rom has a basic set of features available and a standard set of apps installed. These do not change between releases. Take it as it is or drop it if it does not suit your needs. No third way given. You can expect improvements and optimizations, but not fancy addons, widgets, beautiful apps. The Market is there for a reason, use it if you want to add the app you're in love with. Or use Titanium Backup, Root Explorer or similar apps to uninstall unwanted apps from /system/app.

Q3. GPS does not work on my rom. I'm actually in a room at the first floor of a 45 floor building made of steel and concrete with a narrow street in front of me and I cannot get a fix. Is there a reason for that?

A3. If you want a quick fix, you have to sit down in an open space with a large slice of visible sky above you. You should have already installed on your phone a really valuable app called "GPS Status". You haven't got it? Fire up the Market, search it and install it: it's free for everyone. Then turn off wifi and turn on wireless data. Ephemeris data download and position data based on cell triangulation are available only with wireless data enabled and they are inhibited by a special setting in the gps configuration file when wifi is on. Tap the app icon, then look at the status bar: is there a small icon radar-shaped blinking on the status bar (upper part of the screen)?

CASE 1) Yes, I see it! It's blinking continuously!

CASE 2) No, nothing changed.

If your fall in CASE 2, there is really something wrong with GPS on your phone. You can try the following workaround, but if it doesn't work there's no remedy other than filing a bug alert in the thread and patiently wait until the bug will be solved.

WORKAROUND:

- Enter Hidden menu typing 1809#*990# on the phone pad

- Select "GPS Test"

- Go to "SULP Settings" and create a new SLP Server with the following parameters:

name: Nokia

slp address: supl.nokia.com

port: 7275

leave certification file and TLS settings as blank

- go back, and flag "SLP Auto provision" as enabled

- select your APN for SLP from "APN Settings"

- go back 2 times and select "Get position"

- select menu-> start

- at this point, you could notice that no satellite appear. Dont't worry, carry on....

- select menu-> Settings then change some parameters as "Session Type" and "Oper Mode"

- go back and select Stop and Start again

- repeat the last three steps until you get a fix and the gps icon in the status bar remains steady after the fix.

If you fall into CASE 1), look at the yellow bars indicating the number and the signal level of each satellite. When the bars will be more than 4 and the length of each bar will be enough to get a fix (the longer the bars, the stronger the signal), the bars will turn into green and you have got the first fix (how lucky you are, huh?). The time it will take is not fixed, though: it depends on weather, correct download of ephemeris data, radio interferences and so on. So, the bottom line is: BE PATIENT! There is no rule of thumb for measuring the time a fix will take. In some conditions, you will get it in a few seconds, in other conditions it will take minutes. Now that you've got a fix, try to move a little bit around. The radar-shaped icon should be steady now and the bars should remain green. If you see the icon disappearing after the fix, you are falling into CASE 2). Try the workaround mentioned before and if it fails, file a complaint into the thread.

DO NOT FILE A BUG ALERT ON GPS WITHOUT HAVING ALREADY TRIED ALL THE PROCEDURES LISTED ABOVE! It will be simply ignored.

Q4. What on earth is this overclock daemon you mention on first page? Why I can't go on using PimpMyCPU [Variant: SETCPU, CPU MASTER], by Jove? It has a clean and polished GUI, it works as it should and I'm a happy camper with it.

A4. Overclock daemon has several advantages over other overclock apps. It sits down in background and it doesn't bother you, consuming a very little amount of ram (70kb, you have hundreds of Mb available on this phone) and a very few clock cycles, as it's event driven. The great advantage of this little daemon is that it wakes up on screen state change, and it allows to switch the frequency governor (only performance and powersave governors are actually available in our old venerable kernel :( ) and the lower and the highest frequencies for the cpufreq daemon accordingly to screen state. If your screen is off, it can be tuned to lower operating frequencies in order to limit battery consumption. If the screen is on, it can be tuned to give you the best user experience raising the operating frequencies to the max available, including overclock on selected kernels.

Q5.Oh, I see, and now I understand what overclock daemon is meant for. But my actual overclock app already provides profiling abilities, so I can tune CPU performances among different screen states as well if not better than what you can do with your damn overclock daemon.

A5. All the other overclocking apps available at the time I am writing this answer, will take about 5/6 seconds to switch from sleep profile to wake profile. In this little amount of time the phone interface will be sluggish and slow, depending on the max frequency you have chosen for the sleep profile. If you have chosen a low frequency to save battery as it is reasonable to do, the lag on profile change will look unbearable to you. Overclock daemon is fast as a lightning in switching profiles, as it's event driven. It takes a fraction of a second to switch from sleep profile to wake profile, and you will not experiment lags (or, at least, lags will be minimized).

Q6.But I'm still experimenting lags with overclock daemon on wakeup: how can I tune it to fit my needs at best?

A6.One of the best features of overclock daemon is that you can tune it as you like. If you don't want to see lags on wakeup, just raise a little the max frequency for sleep profile. If you want to mock SGS2 owners with astonishing Quadrant scores, raise the frequency to the max for wake profile and your phone will turn into a raging bull. It's up to you. Your interest is raising? Let's see how to do it:

Fire up ES file explorer (you will find it in my rom beginning with v. 1.6 release), open settings and check "Use Root Mode" and "Mount Filesystem" (you need to do it only once). Then exit settings and hit the highest icon on the left: you will be in the root directory of your phone. Navigate to /etc/andrev_oc, you will find six files there:

-sleep_gov: indicates which governor to use during sleep mode ("performance" or "powersave")

-wake_gov: governor for awake state ("performance" or "powersave")

-sleep(or wake)_max: max frequency to allow during sleep or wake (see frequencies below)

-sleep(or wake)_min: min frequency to allow during sleep or wake (see frequencies below)

Here there are the frequency values available on current kernel (Neoblaze 28092011):

1408000

1216000

1100000

1015000

800000

503000

389000

216000

Make your changes to the files listed above and save them.

Since overclock daemon is already up and running and it monitors these files at every screen state change, it should be enough to hit the sleep button, wait some seconds, and hit it again to wake your phone. Your new settings will be applied immediately.

You may want to check the actual CPU frequencies by using OS Monitor or SystemPanel App (download the freely from the Market).

Q7. I still don't understand why I should use an app to lower operating frequencies on sleep time to save battery. There are several tasks running in background in an Android phone, and limiting the CPU clock frequencies during sleep will lower the speed at which background tasks are executed. The lower the speed will be, the longer the task will take to be executed. So, the battery will not be saved, but wasted because idle times between tasks will be shorter.

A7. That's not true in this world. It can happen in others, maybe, but here on planet Earth energy always behaves in the same way and obeys to the same laws. Think about your car: you have to use it to have a trip from point A to point B. Do you think you will save more fuel going from A to B at 120mph or at 80mph? True, you will be there faster in the first case and your car will rest a little after the race, but fuel consumption will be higher. E=mc2 (how smart I am! :D )

Q8. I see strange files in /etc/init.d What are they used for?

A8. These files are tweaks I added to make the rom snappier and faster. If you don't know exactly what you are doing, leave them alone. If you are really interested in what each file is meant for, ask it in the thread.

Q9. I want even longer battery life. Can I do something to achieve Froyo-like battery life?

A9. No, all the GB leaks until now are not so battery friendly as Froyo was. You can try different basebands, rils, whatsoever but your battery life will be mediocre. Actual leaks are hungrier and less optimized than their Froyo counterparts, so you will be lucky if you will be able to squeeze an entire day of heavy use from them. Road warriors are warned: wireless data under 3G/HSDPA coverage will be your worst enemy if you really want to phone your wifey coming back home in the evening to check if supper's ready.

Use wifi when available, use 2G if possible and make sure your car is provided with a battery charger. But there is a way to limit a bit battery consumption with undervolt. What's undervolt? Quickly explained, undervolt has to do with the capability of CERTAIN phones to bear working voltages on different CPU frequencies lower than the default set by phones manufacturer. In our case, you can TRY to undervolt the CPU at some frequencies. Here's how:

- Fire up ES file explorer (you will find it in my rom beginning with v. 1.6 release), open settings and check "Use Root Mode" and "Mount Filesystem" (you need to do it only once). Then exit settings and hit the highest icon on the left: you will be in the root directory of your phone.

- Now try to remember the release number of the ROM you're actually using, because it will be important.

- Navigate to /etc/init.d [/system/xbin for v. 1.8 and later releases], you will find some files there. Locate S08volt_scheduler [volt_scheduler for v. 1.8 and later releases], open it and look into it. You will find a line with the following content:

'echo 0,0,0,0,0,0,0,0 .................'

This line of zeros are the values of undervolt for each CPU operating frequency, ordered from the higher to the left to the lower to the right.

Carefully edit the values, and be aware that not al phones behave in the same way, so your mileage may vary and in certain cases your phone could refuse to even boot if you lower them too much. Use steps of 25 mV, reboot and if all works fine, lower it a little bit more (values > 50 are not advised).

In the following example, an undervolt of 50mV is applied to the 4 higher frequencies.

'echo 50, 50, 50, 50, 0, 0, 0, 0 ..........?

Reboot the phone to test new frequencies (they are applied at boot) and good luck!

Q10. I really hate the stock lockscreen. Can I have my AOSP lockscreen back?

A10. Yes, you can. With ES file explorer edit the /system/build.prop file. Locate the line with the following content:

user.feature.lock_andy=true

and change it to

user.feature.lock_andy=false

Save the file, then reboot. Goodbye LG lockscreen, hello AOSP lockscreen!

Q11. A friend of mine showed me his phone with GB and he was very proud he could sync time and date with a ntp server. Why on earth your stupid rom hasn't the same feature?

A11. This is enabled by default on v.1.8 and later releases, but you can enable it on other releases simply adding this line to build.prop:

user.feature.ntp=true

Save the file, then reboot. Then go to your friend and make him envious.

Q12. A friend of mine showed me his phone with GB and he was very proud he could connect his phone to the pc without the annoying sound of USB debug on connection. Why on earth your stupid rom hasn't the same feature?

A12. This is enabled by default on v.1.8 and later releases, but you can enable it on other releases simply adding this line to build.prop:

persist.adb.notify=0

Save the file, then reboot. Then go to your friend and make him envious.

Q13. My cousin is a freaking great phone expert and he has a LG Optimus 2X just like me. He told me that there is a missing file in all LG stock roms called gps.conf. He told me that with this file he gets always instant fixes with GPS and that if I will not use it, my GPS will be broken forever and I will wait for a fix until the Day of Judgement. Why on earth your stupid rom hasn't the same file already included?

A13. There is no evidence in all my logs that this file is even read from the system nor during boot nor during runtime. It exists on other phones, but there is a reason why LG did not put it in in all stock releases. Tell your cousin something about adb logcat and smile when his face will turn into an amazed expression. (Logcat? Has this something to do with Felix the Cat?) [UPDATE 20111011] I am a stupid donkey: I found where the gps.conf is read into a logcat. Maybe your cousin is not so bad. I should listen to his suggestions from time to time.... :(

Q14. I tried to flash your rom and now I'm stuck in a bootloop. F..k the bloody day I had the idea of flashing this stupid ROM!

A14. Did I call you here? You came here with your legs, so calm down and let's see what can happen. Bricking our phone is virtually impossible, because no ROM I know is overwriting the bootloader. You can try several ways to unbrick your phone:

a) Flash 1.6 release, then upgrade. 1.6 is safer for many reasons, and it gives good results most of the times

b) If a) fails, Flash Neoblaze 28092011 over 1.6, then reboot. The last Neoblaze boots at stock speed, while othe releases have a slight undervolt at stock frequency, making some phones to bootloop.

c) Flash another rom. We are not married, I will not suffer if you choose to go otherway.

d) Flash 1.4 release and stay with it. It's the release with stock kernel. It should work in any case.

e) Back to the beginning: do you know smartflash? Have you ever tried to use it to flash a rom from the PC? Got to the general section of this forum and read about it. Then flash v10d. This is the safer option to unbrick a phone.

Q15. Tell me your truth about schedulers: are they useless?

A15. No, they have a role in how tasks are switched during runtime, so they aren't useless. Our kernel provides a bunch of different schedulers, and the default one is bfq. In my opinion, the fastest kernel scheduler and the one that copes at best with our phone is deadline. You can try to switch schedulers even during runtime, but there is no reason for not applying changes during boot [ONLY WORKING FOR V.>=1.8] . I prepared a file for your edits: it's the volt_scheduler file in /system/xbin

Open it with ES file explorer and locate all the 'deadline' word occurrencies and change them with your preferred scheduler. After a reboot, you may want to check if edits are corectly applied, so use your terminal emulator and type:

su (you will be prompted for superuser access the first time: allow it)

$ for s in /sys/block/*/queue/scheduler; do v=`cat $s`; echo "$s $v"; done

and you will see what the actual scheduler is. You will see all available schedulers too.

Q16. Pimpmycpu allows to change schedulers at boot time too. Why do you lose your time on unuseful things? Give us a good rom and stop adding unwanted stuff. Your ROM is bulky!

A16. A simple reason would be that pimpmycpu script does not work on our phone. It allows to change undervolting values but it refuses to change the scheduler correctly. The reasons why it happens are two:

1) The scheduler part of the script has reference to values that simply do not exist on our phone, so it fails to set the correct values where it should.

2) The script is executed at boot time when the scheduler values are not still ready for userspace editing. So the execution has to be delayed until the boot phase is finished.

Q17. My cousin (the freaking great phone expert we all know from another FAQ), told me that without overclock daemon my phone is faster, it gains hundreds of points in Quadrant [variant: Smartbench, Antutu, etc] score and that I am really mad if I don't get rid of it.

A17. Tell your cousin that overclock daemon has no influence on general performance and speed. Benchmark tests are influenced by many factors. If the phone is doing something in background when you fire up the benchmark your results will be lower than expected. This has nothing to do with overclock daemon. And remember that the score you can see in first page at 1.4Ghz with Quadrant was achieved with overclock daemon up and running. So, your mileage can vary.

Q18. Ok, go to hell you and your overclock daemon: I only want to go back to my normal overclocking app. Tell me please how can I get rid of this.

A18. There's no need to uninstall it, as overclock daemon is smart enough to sense if you have another overclock app already installed and commits suicide at boot in this case. So, you only have to bear 7 little unuseful files in your rom. They stay there, they do not eat, they do not drink, they do not ask money and they do not make your rom dirty. Please let them live alone and don't even worry about them. I give you a week beginning from now and you'll forget they still exist.

Q19. A friend of mine told me that you can make your launcher stick in ram, so that the evil Android will not succeed in killing it every time it needs more ram. Why your stupid rom hasn't this setting by default?

A19. Because if someone is hungry, I cannot think that the best solution would be putting a lock on the refrigerator. If ram is needed, the best thing you should do is giving it to the process that's asking for it in that moment, huh? Limiting free ram is not the best way to go IMHO, but if you want to try, drop a line like this at the end of /system/build.prop

ro.HOME_APP_ADJ=0

Launcher will stick in ram and other apps will have less ram to deal with. Bad trade? Good trade? It's a free world.

Q20. I cannot find all my apps in the Market. Some apps I've always used are now listed as incompatible. Your rom is broken, donkey.

A20. That's. not my rom, mate. It's the (broken) way the new Market uses to recognize the phones that are compatible with a certain app. But beginning from v.1.8, I found a workaround: if you let the Market upgrade by itself from the old version, the compatibility check is done better and a great amount of apps will be listed as compatible (better does not mean that ALL the apps will be listed, though).

Q21. I had a bunch of apps installed on my phone, and now the Market tells me that less than a half of them are installed if I select "My Apps". Will you ever be able to build a rom correctly?

A21. Sometimes the link between an app and the Market goes bananas during upgrades from a rom release to another. Install Titanium Backup and use the Market Doctor feature to relink all your apps with the Market.

Q22. I used CWM to backup your rom, and now i want to restore it but CWM throws out a message saying that it cannot restore. What can I do now?

A22. I don't recommend using CWM to backup/restore my rom as it conflicts with some filesytem optimization I used for this ROM. For the same reason, I don't recommend wiping partitions from CWM. Don't be surprised if all benchmark results drop sensibly or if you experiment strange behaviours after that. Use Titanium backup and restore apps and data from there, if possible.

Q23. We have all the evidences: you are sadic. You've chosen to upload your ROMS to Megaupload when you know for sure that Megaupload can't be used in some countries. Now tell me how can I download your rom from my country, silly boy!

A23. I use Megaupload because it's the faster service here and it allows to download at unlimited full speed even if you are not registered and not paying a penny. Besides that, if you register (it's free) it allows a reduced delay before download (25 secs for any file, don't matter the file size) and it allows to organize your uploads in directories. Do you know jdownloader? Go and find it, install it and try if that solves your problems. If it doesn't, someone on the board will help you for sure if you politely ask for a mirror (mirrors are always allowed, as I love free sharing).