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

[Guest ralli1300]

I think the bluetooth support in Fr15 is buggy.

First connect to a Nissan-Connect-System after booting of LGOS is ok but always without access to phone-book or to call-lists. After the LGOS is disconnected and bluetooth is made off and on no connect is possible any more.

With stock-ROM there are no problems so I think it's a bug in the MoDaCo-Custom-Kernel.

[Guest Frank Sem-Jacobsen]

I think the bluetooth support in Fr15 is buggy.

First connect to a Nissan-Connect-System after booting of LGOS is ok but always without access to phone-book or to call-lists. After the LGOS is disconnected and bluetooth is made off and on no connect is possible any more.

With stock-ROM there are no problems so I think it's a bug in the MoDaCo-Custom-Kernel.

I also am experiencing problems with my regular Bluetooth headset. It usually connects without issues, but after a while the sound stops working, even though every icon indicates that the connection is still valid

[Guest federicoc]

Hello,

Fr15, no problem with BT connection to my Ford (Sony Audio & Hands-free kit System).

F.

[Guest maedox]

What a piece of s*** this phone is! Amazing!

Yesterday at work, while charging from the included wall charger, it shut down and I had to pull the battery to get it going again. Today the same thing happened ten minutes ago, and then again just now. It has happened before, but it's a long time ago and very seldom. It gets warm and is very warm when I notice it's dead. I've seen it show battery temp of ~ 40 degrees C. Now after a reboot the temp keeps climbing again, so I'll keep an eye on it. Running Fr15 by the way, not that I think it matters anyway. It seems like a hardware problem, even though it's so random.

[Guest djmcnz]

What a piece of s*** this phone is! Amazing!

Yesterday at work, while charging from the included wall charger, it shut down and I had to pull the battery to get it going again. Today the same thing happened ten minutes ago, and then again just now. It has happened before, but it's a long time ago and very seldom. It gets warm and is very warm when I notice it's dead. I've seen it show battery temp of ~ 40 degrees C. Now after a reboot the temp keeps climbing again, so I'll keep an eye on it. Running Fr15 by the way, not that I think it matters anyway. It seems like a hardware problem, even though it's so random.

This has also happened to me once (and recently) with Fr15 but I haven't had it otherwise since Fr4 (except the not-so-awesome Fr14).

My phone was also hot.

This leads me to believe it's not in fact off, rather it's CPU bound, running at 100% and therefore can't respond to user input... effectively appearing dead and requiring a battery pull.

Since your temps rise again after a reboot (mine do not) it would be interesting to see what frequency the CPU is running at. Can you install SetCPU, and see if the CPU is constantly at 1000Mhz after a reboot when the temps climb?

[Guest MeX_DK]

This leads me to believe it's not in fact off, rather it's CPU bound, running at 100% and therefore can't respond to user input... effectively appearing dead and requiring a battery pull.

I can supoort that and I think you are right. So far I have been able to watch my phone as it went from working, to slowly grinding to a halt. Going as far as not responding to any user input at which point it spontaniously rebooted. At a point DropBox kept making my phone reboot in that way so that is why I know. If I downloaded a file through dropbox (ie one of Pauls MCR roms) then at about half way done the phone would slow down a lot and then grind to a halt and reboot.

I have reason to suspect its that "behaviour" that might happen while we charge and thus causing the phone to reboot. So as far as I see it its either related to the phone burning through its memory and not clearing it fast enough and thus rebooting as it reaches a "catastrophic" memory state. OR simply that the CPU gets bugged down at 100% and leaving the phone dead, or seemingly dead to the user, and thus rebooting shortly thereafter due to conditions set in the software to "safe" the phone from burning out perhaps.

[Guest djmcnz]

I can supoort that and I think you are right. So far I have been able to watch my phone as it went from working, to slowly grinding to a halt. Going as far as not responding to any user input at which point it spontaniously rebooted. At a point DropBox kept making my phone reboot in that way so that is why I know. If I downloaded a file through dropbox (ie one of Pauls MCR roms) then at about half way done the phone would slow down a lot and then grind to a halt and reboot.

I have reason to suspect its that "behaviour" that might happen while we charge and thus causing the phone to reboot. So as far as I see it its either related to the phone burning through its memory and not clearing it fast enough and thus rebooting as it reaches a "catastrophic" memory state. OR simply that the CPU gets bugged down at 100% and leaving the phone dead, or seemingly dead to the user, and thus rebooting shortly thereafter due to conditions set in the software to "safe" the phone from burning out perhaps.

It interesting that you say that because I have two specific logcat logs from this occurrence that I have posted previously:

CPU pegged: here - "CPU may be pegged. trying again."

No memory left: here - "Low Memory: No more background processes."

Both of which are of course fatal... and apparently not possible with Android... :unsure:

[Guest maedox]

It interesting that you say that because I have two specific logcat logs from this occurrence that I have posted previously:

CPU pegged: here - "CPU may be pegged. trying again."

No memory left: here - "Low Memory: No more background processes."

Both of which are of course fatal... and apparently not possible with Android... :unsure:

Until LG got their hands on the code. :)

[Guest 1nf3rn0]

What a piece of s*** this phone is! Amazing!

Yesterday at work, while charging from the included wall charger, it shut down and I had to pull the battery to get it going again. Today the same thing happened ten minutes ago, and then again just now. It has happened before, but it's a long time ago and very seldom. It gets warm and is very warm when I notice it's dead. I've seen it show battery temp of ~ 40 degrees C. Now after a reboot the temp keeps climbing again, so I'll keep an eye on it. Running Fr15 by the way, not that I think it matters anyway. It seems like a hardware problem, even though it's so random.

I have the same issue and i hope is software related because it' really annoying.

Sometimes i feel its warmy shell in my pocket and think "i hope it will not explode"...

Edited May 12, 2011 by 1nf3rn0

[Guest Droid800]

Would flashing MCR for the Optimus 2X work on the G2X? As sick as it sounds, I'm interested in flashing the LG skin onto my G2X to try it out and see what its like.

Edited May 12, 2011 by Droid800

[Guest MeX_DK]

Would flashing MCR for the Optimus 2X work on the G2X? As sick as it sounds, I'm interested in flashing the LG skin onto my G2X to try it out and see what its like.

It would not work and you would end up with an expensive DualCore Brick :unsure:. Or at least semibrick as far as I understand.

[Guest Droid800]

It would not work and you would end up with an expensive DualCore Brick :unsure:. Or at least semibrick as far as I understand.

Well, I mean, I flashed it but it wouldn't boot past the LG logo.

I was just of the understanding, after reading the G2X warning thread, that ROMs like MCR should still be able to be flashed to the G2X, even though baseband should be avoided at all costs.

[Guest maedox]

Well, I mean, I flashed it but it wouldn't boot past the LG logo.

I was just of the understanding, after reading the G2X warning thread, that ROMs like MCR should still be able to be flashed to the G2X, even though baseband should be avoided at all costs.

They are NOT the same! The partitions are different.

[Guest maedox]

Today when I was ready to troubleshoot the battery charging heating issues, it doesn't get warm at all. Typical :unsure:

It's at 28˚C now and 93 %, charges from 30-something.

[Guest TsunKit]

Just wanted to say that after wiping battery stats, battery life did improve.

Thanks for the tip Paul!

[Guest GaLaReN]

For some odd reason Wi-Fi does not automatically reconnect after screen saver/sleep. I have to manually reconnect :unsure: Any clues to solving this, please?

Here are my phone details:

[Guest Paul]

I'll be starting the Fr16 kitchen upload tonight. A few tweaks first and some further changes tomorrow / Monday, then general release. :unsure:

P

[Guest masi0]

I'll be starting the Fr16 kitchen upload tonight. A few tweaks first and some further changes tomorrow / Monday, then general release. :unsure:

P

awesome :)

[Guest GaLaReN]

For some odd reason Wi-Fi does not automatically reconnect after screen saver/sleep. I have to manually reconnect :) Any clues to solving this, please?

Here are my phone details:

I'll be starting the Fr16 kitchen upload tonight. A few tweaks first and some further changes tomorrow / Monday, then general release. :unsure:

P

Excellent, would Wi-Fi reconnect be a part of the "tweaks"?

Thanks

[Guest Paul]

Tough one as I don't see this issue. I'll look into it tho.

P

[Guest gaeng4665]

Hi Paul, what do you think about including an option to the kitchen where you can select which sdcard (internal or external) will be mounted as "primary" sdcard, on which apps-data will be installed. It would make it much easier to switch back to any frxx-rom from i.e. cm7 without having to copy over the whole sdcard content....

[Guest MeX_DK]

Hi Paul, what do you think about including an option to the kitchen where you can select which sdcard (internal or external) will be mounted as "primary" sdcard, on which apps-data will be installed. It would make it much easier to switch back to any frxx-rom from i.e. cm7 without having to copy over the whole sdcard content....

So CM forces external SD to be internal SD?

[Guest gaeng4665]

So CM forces external SD to be internal SD?

Yes true. External sdcard is the primary one (/sdcard). Internal sdcard is mounted as /mnt/emmc...

[Guest Paul]

Hi Paul, what do you think about including an option to the kitchen where you can select which sdcard (internal or external) will be mounted as "primary" sdcard, on which apps-data will be installed. It would make it much easier to switch back to any frxx-rom from i.e. cm7 without having to copy over the whole sdcard content....

I could add that, it would quite seriously screw up though it you changed from one to the other without wiping...

P

[Guest MeX_DK]

Yes true. External sdcard is the primary one (/sdcard). Internal sdcard is mounted as /mnt/emmc...

EEwww is all I can say to that. Thankfully I found out that there is a patch to that so I can get it at least in a better state :unsure:.

But the true way "I Want It" would be to merge both Internal SD and Internal Storage into one, which would also mean that External SD would be the primary SD. And all that without loosing any storage :). But I figure doing that would require a full repartitioning of the phone as well as a possible rewrite of the phones software.

Edited May 12, 2011 by MeX_DK