28 Jul Fr19: MoDaCo Custom ROM for the LG Optimus 2X with Online Kitchen (new: custom kernel)

[Guest BrumBrum74]

Will try without Car Home as that's a program I have always had in my rom, but never uses.

Thanks for the tip Trym.

[Guest d3rb3rt]

To ALL of you who suffer spantaneous REBOOTS.

Try to cook a ROM without the Car Home and F-secure applications. I had reboots and hard-locks on the stock ROM, but haven't had a single one with the baked ones, and I've always excluded the two mentioned apps. If you *do* have reboots and do not have them installed, please respond, we need to get to the bottom of this.

::Trym

instead of baking a new rom, I only uninstalled the car home with titanium (no f-secure in my rom), and as far as i can tell the rebooting stopped.

btw, if i do remember correctly, after updatimg to a new rom, the rebbooting always started after first call of the car home app ...

thanks for the advice!

Edited April 14, 2011 by d3rb3rt

[Guest Korumera]

I had reboots, and no i didnt have car home and f-secure installed in my ROM. But i havent had any reboots so far after removing juice defender and/or greenpower

[Guest mhome]

Pls guys, in the process of trying to return the LG in as much the same state as possible (that means stock system and stock recovery) - I install the stock recovery from this forum, tried to enter it (via vol_down + power) but it just hangs... :) And after that I cannot boot neither normally neither to recovery.

What should I do now?

[Guest aaww]

GOOD NEWS !!!

The LG Optimus 2X will be getting updated to Android 2.3 Gingerbread this summer. That’s according to the FAQ section of LG Denmark’s support site.

http://www.gsmarena.com/lg_optimus_2x_to_g...y-news-2516.php

[Guest wapz]

GOOD NEWS !!!

The LG Optimus 2X will be getting updated to Android 2.3 Gingerbread this summer. That’s according to the FAQ section of LG Denmark’s support site.

http://www.gsmarena.com/lg_optimus_2x_to_g...y-news-2516.php

That's not good news. That's a delay.

[Guest Paul]

Just a heads up that I'm away from Android all next week, so Fr13 will follow the week after.

Get your requests in and i'll catch up when i'm back. Thanks for your ongoing support via AdFree, Plus and the Market apps... it's much appreciated! :)

P

PS We won't have to wait until summer for Gingerbread. :)

[Guest aaww]

Just a heads up that I'm away from Android all next week, so Fr13 will follow the week after.

Get your requests in and i'll catch up when i'm back. Thanks for your ongoing support via AdFree, Plus and the Market apps... it's much appreciated! :)

P

PS We won't have to wait until summer for Gingerbread. :)

I hope you are right.

Enjoy your time off and thank you for the wonderful job you are doing !

[Guest klikli]

Was gettin' into a boot loop. No idea yet. Clean install from stock ROM. (Or should I wipe my data etc. in clockmod before I flash my ROM like my previous HD2?)

[Guest Yamas85]

Hi

Got my new LG Optimus 2x today. Got it rooted, installed your clockworkmod app (as i it gave me error messages with the "install-clockworkmod-windows.bat")

But now i got a problem after installing your ROM.

By using your app i got in recovery mode, installed the newest MoDaCa ROM. But after installing i restarted, and now it just boot-loop with the MoDaCo-LG screen and LG screen.

If I pull the battery out and turn it on using the 'volume-down' methode it says "S/W Upgrade Please wait while upgrading..." - and it doesnt seem to get further...

Anything i could do/try here??

Thx in advance!!

[Guest lilHermit]

I was looking at aosp with a view to mute the sound for usb debugging and found you can stop the notification altogether by writing persist.adb.notify=0 to your build prop

adb remount

adb shell "echo persist.adb.notify=0 >> /system/build.prop"

adb reboot[/code]


WARNING: Make sure you have two ">"!!!


I'll talk to Paul about the silent option for the kitchen when I have it.


~

[Guest Riemen]

Was gettin' into a boot loop. No idea yet. Clean install from stock ROM. (Or should I wipe my data etc. in clockmod before I flash my ROM like my previous HD2?)

Wiping is correct. But you should wipe after flashing the new ROM, not before that.

Just boot to Clockwork again, do a full wipe and reboot. Now it should start.

[Guest beeklaan]

Hi Paul,

Thanks again for FR12.

Is there a way for you to integrate the "tap the side of your phone to move the cursor" function into the gingerbread keyboard? I really love that function but it seems that it doesn't work on the gingerbread keyboard.

Greetings.

[Guest Riemen]

Hi Paul,

Thanks again for FR12.

Is there a way for you to integrate the "tap the side of your phone to move the cursor" function into the gingerbread keyboard? I really love that function but it seems that it doesn't work on the gingerbread keyboard.

Greetings.

This is strange. for me it works even with Swype, so it should not be Keyboard dependent?

(I did not include the Gingerbread keyboard, so I can't speak about this.)

[Guest OptimusStudio]

can me try it in optimus gt540??

[Guest djmcnz]

Getting a few errors like this now:

The process com.android.phone has stopped unexpectedly. Please try again.

Happened last now when trying to download a mms on stock messaging program. LG one not installed.

Can't seem to download or send mms. Settings are ok.

Clean install of Fr12 and full wipe before installing.

Baseband updated as well.

Sound like you need Mms.apk, the system app?

[Guest mattfigaro]

Anyone else got this problem with the keyboard with fr12 ?

[Guest djmcnz]

Anyone else got this problem with the keyboard with fr12 ?

How many recent pages of the thread did you read before going to the trouble of taking that shot, uploading it and posting? :)

[Guest Oxtapus]

Hmmm ok i have feeling apps like juice defender or green power makes the phone reboot when they do some stuff to the phone (turning stuff on and off). I removed the apps (didnt had them installed both at once tho). And now the reboots are gone as far as i know.

+1 to this. I had Green Power installed, which worked fine with FR10. Installed FR11 and had random reboots. Reverted to FR10, all was fine. Updated to FR12, random reboots. I have now frozen Green Power on FR12 and have yet to experience any random reboots.

Sometimes i would find that it didn't reboot, but instead I would notice the phone getting hot. When i tried to view the screen, i couldn't as the phone had become totally unresponsive. I had to battery pull and reboot.

Otherwise, excellent ROM and excellent work Paul. Thanks for all your efforts. Hope this goes some way to helping you solve this issue.

[Guest len.asdf]

Wiping is correct. But you should wipe after flashing the new ROM, not before that.

Just boot to Clockwork again, do a full wipe and reboot. Now it should start.

I didnt know that, could you be so kind and explain me why that is?

[Guest len.asdf]

Anyone else got this problem with the keyboard with fr12 ?

Read a few pages back, Paul acknowledge the error and said he would fix it. So no worries :)

[Guest maedox]

I didnt know that, could you be so kind and explain me why that is?

It doesn't matter.

[Guest djmcnz]

I didnt know that, could you be so kind and explain me why that is?

Yeah, that's not quite right.

Backup

Wipe

Flash

Boot

Is the typical order.

If you wipe (data) after flashing you will stuff up some roms.

Edited April 14, 2011 by djmcnz

[Guest len.asdf]

Yeah, that's not quite right.

Backup

Wipe

Flash

Boot

Is the typical order.

If you wipe (data) after flashing you will stuff up some roms.

Ah thanks, than i did it always right :)

[Guest Frank Sem-Jacobsen]

I am currently running FR12 with the newest baseband. I can quite consistently trigger a reboot when listening to an audio book using the audible player by pulling out the headset. Usually this should just cause the player to stop, but three out of four times this causes an instant reboot. I guess matters are slightly complicated by tasker which sets the phone into aeroplane mode when inserting the headphones, and revert back to normal mode when pulling the headphones out.

To try to figure out what the problem is in the hope that it might shed light on the general rebooting issue, I did "adb logcat" before pulling out the headphones to see if I could capture what happens. I have attached to look to this post. It would be great if any of the great minds in this forum could take a look and see if you can spot anything.

Edit:

Wrong: Relating this to a previous post I made, since reverting the sqlite changes in my latest ROM the phone no longer goes into an inconsistent state when these reboots happen.

I just completed the reboots after the crash, and the phone is again in an inconsistent state with everything FCing. This is with the revert sqlite option in the kitchen ticked off. Frustrating.

loghp.txt

Edited April 14, 2011 by Frank Sem-Jacobsen