yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G2x] Core Memory:
The LGE RIL checks the battery. Did you look at this?

https://bitbucket.org/EaglesBlood_Development/eb-kernel/src/51802dd8f0ff/drivers/spi/spi_mdm6600.c

---------- Post added at 11:04 AM ---------- Previous post was at 10:54 AM ----------

And, look at this.

https://bitbucket.org/Vork/lge-kern...dm_query_discovery_starsmartphone_addresses.h

---------- Post added at 11:19 AM ---------- Previous post was at 11:04 AM ----------

Here's some more.

lge-kernel-star / arch / arm / mach-tegra / include / star_hw_definition.h

https://bitbucket.org/Vork/lge-kern...h/arm/mach-tegra/include/star_hw_definition.h

Edit:

Look at line 499 onwards.

And.

lge-kernel-star / arch / arm / mach-tegra / include / star_pinmux_definition.h

https://bitbucket.org/Vork/lge-kern...m/mach-tegra/include/star_pinmux_definition.h

#define STAR_IFX_SPI_SRDY AP20_GPIO_PO5

#define STAR_IFX_SPI_MRDY AP20_GPIO_PO0
[T-Mobile LG G2x] xBIGREDDx:
:(

I took a look around Mazout's repo, you are correct, it's just calculating battery level from voltage, through the PMIC.
[T-Mobile LG G2x] Core Memory:
He got the voltages/percent of charge from the service manual.
[T-Mobile LG G2x] King-Nai:
Has anyone else noticed this? https://github.com/CyanogenMod/lge-....6.32/arch/arm/mach-tegra/board-nvodm.c#L2225

https://github.com/CyanogenMod/lge-...h-tegra/odm_kit/star/query/nvodm_query.c#L891

It would return s_Spi1Cs0Info_IfxRil and s_Spi1Cs0Info. Are we only setting up the mdm? Or do we set up tegra ones too. It's loading tegra spi and not the tegra spi slave

Edit:

The tegra SPI calls NvRmPowerRegister in gb. Seems like it handles power in ICS too. Possibly why the radio is off.....

So does this kernel ever have a tegra spi probe?
[T-Mobile LG G2x] xBIGREDDx:
If you check out the log in this post, tegra_spi_slave.c grabs SRDY1 (PJ6) and SRDY2 (PO0) as outputs, and then spi_mdm6600.c grabs MRDY1 (PU6) as an interrupt pin:

<4>[ 9.919896] tegra_spi_probe : name(tegra_spi), id(0), num(0)
<4>[ 9.919931] gpioDebug: drivers/spi/tegra_spi_slave.c : tegra_spi_probe Line: 536
<4>[ 9.919941] gpioDebug: hPin[pdev->id] Port: 9 , Pin: 6
<3>[ 9.919956] NvRmSpiOpen() Opening channel Inst 0 and IsMaster 0
<3>[ 9.920687] BRCM_LPM: host_wake_isr schedule
<3>[ 9.920711] BRCM_LPM: BRCM_WAKELOCKTIMEOUT host wake=1
<4>[ 9.921443] tegra_spi_probe : name(tegra_spi), id(1), num(0)
<4>[ 9.921478] gpioDebug: drivers/spi/tegra_spi_slave.c : tegra_spi_probe Line: 536
<4>[ 9.921487] gpioDebug: hPin[pdev->id] Port: 14 , Pin: 0
<3>[ 9.921498] NvRmSpiOpen() Opening channel Inst 1 and IsMaster 0
<4>[ 9.923025] ifx_spi_init
<4>[ 9.923453] GPIO handle = d8184004, MRDY = 20-6
<4>[ 9.923467] mdmDebug: drivers/spi/spi_mdm6600.c : ifx_spi_probe Line: 582
<4>[ 9.923476] mdmDebug: spi_data->hMrdyPin Port: 20 , Pin: 6
<4>[ 9.923484] mdmDebug: drivers/spi/spi_mdm6600.c : ifx_spi_probe Line: 590
<4>[ 9.923492] NvOdmGpioSetState(spi_data->hGpio,spi_data->hMrdyPin,0);
<4>[ 9.923501] mdmDebug: drivers/spi/spi_mdm6600.c : ifx_spi_probe Line: 593
<4>[ 9.923509] NvOdmGpioConfig(spi_data->hGpio, spi_data->hMrdyPin, NvOdmGpioPinMode_InputData);

I think some of the confusion has come from the fact that the modem in the P990 (ifx n721?) was SPI Slave (with the Tegra as SPI Master), and the modem in the P999 (mdm6600) is SPI Master (with Tegra as SPI Slave), but the modem driver code didn't change the wording in a few places where it should have.

EDIT: Even I can't keep this Mrdy/Srdy thing straight

EDIT2: Somewhat unrelated, but my Ubuntu VM just crashed with this error:

Apparently none of my NVidia products are allowed to work right.
[T-Mobile LG G2x] King-Nai:
But this is the old kernel. It;s using NvOdm. I'm asking if the NEW kernel is actually loading spit_tegra. spi_tegra seems to be what controls the power, so without it the mdm won't be turning on.
[T-Mobile LG G2x] tonyp:
[YOUTUBE]_36yNWw_07g[/YOUTUBE]
[T-Mobile LG G2x] apolkosnik:
star_p999_defconfig has CONFIG_SPI_TEGRA=y, so it should be linked.
[T-Mobile LG G2x] King-Nai:
It's linked but there's never a register device. Where it should be registering spi_tegra it's registering spi_tegra_slave. Try it as

#ifdef CONFIG_MACH_STAR_P999
platform_device_register(&tegra_spi_device1);

#ifdef CONFIG_DUAL_SPI
platform_device_register(&tegra_spi_device2);
#endif
[T-Mobile LG G2x] apolkosnik:
This is an excerpt from board-star-baseband.c :

static int spi_init(void)
{
#ifdef CONFIG_MACH_STAR_P999
platform_device_register(&tegra_spi_slave_device1);

#ifdef CONFIG_DUAL_SPI
platform_device_register(&tegra_spi_slave_device2);
#endif

spi_register_board_info(spi_bus1_devices_info, ARRAY_SIZE(spi_bus1_devices_info));

#ifdef CONFIG_DUAL_SPI
spi_register_board_info(spi_bus2_devices_info, ARRAY_SIZE(spi_bus2_devices_info));
#endif
#else
platform_device_register(&tegra_spi_device1);
//platform_device_register(&tegra_spi_device3);

spi_register_board_info(spi_bus1_devices_info, ARRAY_SIZE(spi_bus1_devices_info));
#endif
return 0;
}

So, we do register the spi-master device. Also according to http://en.wikipedia.org/wiki/Serial_Peripheral_Interface_Bus there shouldn't be more than one SPI master.
[T-Mobile LG G2x] apolkosnik:
Re: CM10.1 based ROM #7 - Works: Camera, HWA, wifi, sdcard, Broken: radio, batt indic

This is weird that we are trying to call spi_register_board_info twice with the same parameters
[T-Mobile LG G2x] xBIGREDDx:
That's just if they are on the same bus. Typically you might have one master and a bunch of different devices you choose from with a chip select line.

However, in the P999, there are two separate SPI busses running parallel between the Tegra and the MDM6600. (Possibly for speed? The SPI bus in the Tegra 2 maxes out at 50 Mbps.)

What has me sort of confused is that the P999 service manual has the connections drawn to indicate that the Tegra is SPI master in one section, and then in another section it shows the connections indicating Tegra is SPI slave. I think possibly this is because they were just porting over from the P990 service manual and didn't change things where the should, or something.

(See the relevant parts here)
[T-Mobile LG G2x] xBIGREDDx:
spi_register_board_info isn't called twice with the same parameters, the first time it's called with bus1 is still inside the #ifdef CONFIG_MACH_STAR_P999. The second time it's called with bus1 is in the #else of that statement.

Also, based on what the GB code does, I'm pretty sure this is the GPIO order we should have (I know, it keeps changing, but this should be the final actual setttings):

MRDY1 (PU6) Input (Interrupt)

SRDY1 (PJ6) Output

MRDY2 (PO5) Input (Interrupt)

SRDY2 (PO0) Output

(Building with those set that way doesn't change anything though.)
[T-Mobile LG G2x] Core Memory:
Here's something to ponder:

//20100424, , RIL code from firenze [START]
#if defined (CONFIG_MACH_STAR)
static const NvOdmIoAddress s_lge_SpiAddresses[] =
{
#if defined (CONFIG_MACH_STAR_REV_F)
{ NvOdmIoModule_Gpio, 'o' - 'a', 5, 0 },
{ NvOdmIoModule_Gpio, 'o' - 'a', 0, 0 },
#else
//20100729-1, , Crazy!!, it changed [START]
{ NvOdmIoModule_Gpio, 'u' - 'a', 6, 0}, //SRDY1 //{ NvOdmIoModule_Gpio, 'o' - 'a', 5}, //SRDY2
{ NvOdmIoModule_Gpio, 'j' - 'a', 6, 0}, //MRDY1//{ NvOdmIoModule_Gpio, 'o' - 'a', 0}, //MRDY2
//20100729, , Crazy!!, it changed [END]
#endif
//20100711-1, , Add spi controller 0 and chip select 0 [START]
{ NvOdmIoModule_Spi, AP20_SPI1, 0x0, 0 }, /* Spi Controller 0 and Chip Select 0 */
//20100711, , Add spi controller 0 and chip select 0 [END]
//20100809-1, , Add SPI2 for AP-CP IPC [START]
#ifdef CONFIG_DUAL_SPI
{ NvOdmIoModule_Gpio, 'o' - 'a', 5, 0}, //SRDY2
{ NvOdmIoModule_Gpio, 'o' - 'a', 0, 0}, //MRDY2
{ NvOdmIoModule_Spi, AP20_SPI2, 0x0, 0}, /* Spi Controller 1 and Chip Select 0 */
#endif
//20100809, , Add SPI2 for AP-CP IPC [END]
};
#endif
//20100424, , RIL code from firenze [END]

// Bluetooth
[T-Mobile LG G2x] xBIGREDDx:
Yes, what I'm saying is that the comments there are wrong.

EDIT:

Does anybody know where this PO6 came from? I'm thinking it should be PV3? It's only used during shutdown and doesn't really change anything, but I think it's correct.
[T-Mobile LG G2x] apolkosnik:
You are looking at code adopted from star tablet... You should probably look at CyanogenMod's repo instead...
[T-Mobile LG G2x] Mazout360:
Yeah don't consider those settings as if they were 100% exact. Some startablet GPIO settings were identical to those in our device but not all of them.

Yet, I don't think this CP_STATE GPIO has an incidence over the modem's boot process.
[T-Mobile LG G2x] xBIGREDDx:
Ah. I was using Mazout's repo. I'll switch over to CyanogenMod.
[T-Mobile LG G2x] apolkosnik:
Tried that, but there was a little snag, it would fail registering the device, since it wouldn't be able to get the clock source named "spi", and in tegra2_clocks.c this happens:

#if defined (CONFIG_LU6500) ||defined (CONFIG_LU8800) || defined(CONFIG_KS1001) || defined(CONFIG_KS1103) || defined(CONFIG_MACH_STAR_P999)
#ifdef CONFIG_SPI_SLAVE_TEGRA
PERIPH_CLK("sbc1",	"spi_slave_tegra.0",NULL,	41,	0x134,	0x31E,	160000000, mux_pllp_pllc_pllm_clkm,	MUX | DIV_U71 | PERIPH_ON_APB),
PERIPH_CLK("sbc2",	"spi_slave_tegra.1",NULL,	44,	0x118,	0x31E,	160000000, mux_pllp_pllc_pllm_clkm,	MUX | DIV_U71 | PERIPH_ON_APB),
#endif
#else
PERIPH_CLK("sbc1",	"spi_tegra.0",	"spi",	41,	0x134,	0x31E,	160000000, mux_pllp_pllc_pllm_clkm,	MUX | DIV_U71 | PERIPH_ON_APB),
PERIPH_CLK("sbc2",	"spi_tegra.1",	"spi",	44,	0x118,	0x31E,	160000000, mux_pllp_pllc_pllm_clkm,	MUX | DIV_U71 | PERIPH_ON_APB),
#endif
[T-Mobile LG G2x] Core Memory:
All Tegra 2 SOC share many common GPIO settings which are pre-determined by NVIDIA. There are some GPIO which are particular to T-Mobile, TMUS, which are hardwired/predetermined in the G2X.
[T-Mobile LG G2x] Core Memory:
Relevant?

http://www.chiark.greenend.org.uk/~theom/riscos/docs/Tegra2_TRM_DP04508001v01p.pdf

Page 768

23.1.2 SPI Controller as a Slave

SCK, SS_N
[T-Mobile LG G2x] apolkosnik:
Excellent find Core Memory! Thanks for sticking around and sharing all these things you find. I think that this doc might be able to help us out a bit more with our quest to get this thing working.
[T-Mobile LG G2x] King-Nai:
Does it work if you remove the def for MACH_STAR?

Old GB never set it up for spi_slave_tegra: https://github.com/CyanogenMod/lge-...ics/arch/arm/mach-tegra/tegra2_clocks.c#L1212
[T-Mobile LG G2x] apolkosnik:
Still fails. Something to play with ;) 4.2.2 :)

cm-10.1-20130221-UNOFFICIAL-p999.zip - 154.37 MB
[T-Mobile LG G2x] creepinm3:
Re: CM10.1 based ROM #7 - Works: Camera, HWA, wifi, sdcard, Broken: radio, batt indic

Same issues as before?
[T-Mobile LG G2x] dEris:
Re: CM10.1 based ROM #7 - Works: Camera, HWA, wifi, sdcard, Broken: radio, batt indic

Radio and indicator issues still?
[T-Mobile LG G2x] Core Memory:
Here's a different tegra2_clocks.c which has 0x31E changed.

http://gitorious.org/trimslice-kern...d4f9658a6/arch/arm/mach-tegra/tegra2_clocks.c

2236
#define PERIPH_CLK(_name, _dev, _con, _clk_num, _reg, _max, _inputs, _flags) \

2237
{	\

2238
.name = _name,	\

2239
.lookup = {	\

2240
.dev_id = _dev,	\

2241
.con_id	= _con,	\

2242
},	\

2243
.ops = &tegra_periph_clk_ops,	\

2244
.reg = _reg,	\

2245
[B].reg_shift = 0x31E,[/B]	\

2246
.inputs = _inputs,	\

2247
.flags = _flags,	\

2248
.max_rate = _max,	\

2249
.u.periph = {	\

2250
.clk_num = _clk_num,	\

2251
},	\

Which has 0x31E, removed (see below) from the tegra2_clocks.c which we've been examining :

2281
PERIPH_CLK("sbc1",	"spi_tegra.0",	NULL,	41,	0x134,	160000000, mux_pllp_pllc_pllm_clkm,	MUX | DIV_U71 | PERIPH_ON_APB),

2282
PERIPH_CLK("sbc2",	"spi_tegra.1",	NULL,	44,	0x118,	160000000, mux_pllp_pllc_pllm_clkm,	MUX | DIV_U71 | PERIPH_ON_APB),
[T-Mobile LG G2x] PaKii94:
lol if those werent there i dont think he would just link it without fanfare. Its prolly just 4.2.2 vs the cm10.1 4.2.1
[T-Mobile LG G2x] dEris:
Cool beans
[T-Mobile LG G2x] justjackyl:
haven't heard that saying for awhile.

"if you let him into your heart, god saves all...well...except for your bricked device"
[T-Mobile LG G2x] apolkosnik:
Yeah, that stuff is still broken.
[T-Mobile LG G2x] creepinm3:
I was asking for reassurance. Not for someone to comment and be silly.
[T-Mobile LG G2x] justjackyl:
awww

we silly by nature!

"if you let him into your heart, god saves all...well...except for your bricked device"
[T-Mobile LG G2x] xBIGREDDx:
PSA: You have to update your Android SDK before you can use ADB with the new 4.2.2.

From the SDK Readme:

Otherwise, you'll just keep getting "error: device offline" when you try to do ADB things.

You also have to accept a dialog on the phone screen when you plug in:
[T-Mobile LG G2x] :
So just to confirm, still no radio?
[T-Mobile LG G2x] tonyp:
Hint: Just read a couple posts up.
[T-Mobile LG G2x] :
I did. :P I saw one person who was not the developer of this ROM say they were broken. Asking for confirmation is bad? Got it.
[T-Mobile LG G2x] G2xer:
He is a Dev. He changed his name. But yeah don't ask twice.
[T-Mobile LG G2x] noahk423:
The key to being a fantastic member on xda: read, read, and when you think you've read enough, read a little bit more. :)
[T-Mobile LG G2x] :
Wise words. And I'm not here to be an idiot and bug you guys, so off to the user thread I go! >.>

*flies away*
[T-Mobile LG G2x] noahk423:
I'm off topic now, so here's my last post here, anyways, we're not pushing you away, just by reading everything yourself, eventually youll be where I am at, able to help people easily and do some stuff development related, and if you continue you'll be amazing and a far more important member than me, and an awesome member of this community :thumbup:

Its like school, study it, and excel in it.
[T-Mobile LG G2x] daygen4545:
Hey, kinda off topic for the current radio development, but i just saw an article about the Android team testing out a new 3.8 kernel, which would mean less memory management, and "support for open source NVIDIA Tegra and Samsung Exynos DRM drivers". Would this help any of this development as far as hardware acceleration goes? I doubt it would help the radio issue, because from what i've read on this thread it's obviously much deeper than upgrading a kernel would solve.
[T-Mobile LG G2x] LostInNorth805:
I think this is a qualcomm not nvidia problem. I could be wrong lol
[T-Mobile LG G2x] towelboy:
Didn't maz fix the battery indicator in his dual boot cm10.1? Then why is it still broken for adam's cm10.1?
[T-Mobile LG G2x] apolkosnik:
Because I'm not using his kernel. His "fix" extrapolates battery percentage from battery voltage, once the spi issue gets fixed not only radio will work, but also the battery gauge, since that's all read through the radio using the AT commands like in the old school modems.
[T-Mobile LG G2x] Core Memory:
Yes, the battery is read through the vendor RIL via AT commands. The RIL does a lot.
[T-Mobile LG G2x] netsnation:
This may or may not be a stupid question; but if we use Mazout's Kernel with your ROM, will it fix the battery indicator, or is that only on Mazout's ROM/Kernel combination?
[T-Mobile LG G2x] xBIGREDDx:
Yes, Mazout's Kernel will fix the battery indicator.
[T-Mobile LG G2x] towelboy:
Weird, does it really fix it? I'm on it and it stays at the same percentage until I reboot it, but then it'll just show the battery percentage at boot until I repeat the process
[T-Mobile LG G2x] monte666:
Without access to the radio I believe that is the only time it can get a measurement. Battery stats go through the radio doesn't make sense but that's hire it works
[T-Mobile LG G2x] xBIGREDDx:
With this ROM #8 and Mazout's Kernel 0122 my device does have battery readings that update. You might try reinstalling or something.
[T-Mobile LG G2x] towelboy:
Okay thank you, I'll try that!
[T-Mobile LG G2x] netsnation:
ROM Flashed with Mazout's CM10 Kernel. So smooth, very nice. Battery works to a degree. Much better than the 4.1.1 ROM I was on. Of course no Radio, so I will have to use my slider phone for texts, because Dual Booting is just too complicated. Hope the Radio is fixed soon though.
[T-Mobile LG G2x] plarmann:
Any help needed?
[T-Mobile LG G2x] apolkosnik:
Some things that differ...

In GB kernel arch/arm/mach-tegra/board-nvodm.c line 1879:

//20100613-1, [email]syblue.lee@lge.com[/email], add spi slave [START]
#if defined(CONFIG_SPI_MDM6600)
#include <linux/spi/spi.h>

static struct spi_board_info tegra_spi_board_info[] __initdata = {
{
.modalias = "mdm6600",
.bus_num = 1,
.chip_select = 0,
.mode = SPI_MODE_1,
.max_speed_hz = 24000000,
// .platform_data = NULL,//<B0><CB><C5><E4>
.irq = 0,
},
//20100809-1, [email]syblue.lee@lge.com[/email], Add SPI2 for AP-CP IPC [START]
#ifdef CONFIG_DUAL_SPI
{
.modalias = "mdm6600",
.bus_num = 2,
.chip_select = 0,
.mode = SPI_MODE_1,
.max_speed_hz = 24000000,
// .platform_data = NULL,//<B0><CB><C5><E4>
.irq = 0,
},
#endif
//20100809, [email]syblue.lee@lge.com[/email], Add SPI2 for AP-CP IPC [END]

in CM JB kernel arch/arm/mach-tegra/lge/star/board-star-baseband.c

uses

.bus_num = 0,

.chip_select = 0,

and

.bus_num = 1,

.chip_select = 1,

no wonder radio doesn't respond ;)

Additionally, N_TS0710 is not defined for some reason, diff bellow.

diff --git a/include/linux/tty.h b/include/linux/tty.h
index 3961715..92c7471 100644
--- a/include/linux/tty.h
+++ b/include/linux/tty.h
@@ -51,7 +51,7 @@
#ifdef CONFIG_MACH_BSSQ
#define N_GSM0710 21 /* GSM 0710 Mux */ // [email]seokjae.yoon@lge.com[/email], 2012-02-13, restore the definition for KS1103
#else
-#define N_TS2710 21 /* GSM 0710 Mux */ //jisil.park@lge.com
+#define N_TS0710 21 /* GSM 0710 Mux */ //jisil.park@lge.com
#endif
[T-Mobile LG G2x] Core Memory:
Evidence that LG has the most incompetent cell phone firmware programmers.
[T-Mobile LG G2x] capncybo:
OMG Adam nice find is this perhaps, at last the missing link :angel: and the angels sing (crossing fingers & toes)...
[T-Mobile LG G2x] Mazout360:
Yes that was awkward, but we already worked on this months ago I think. Changing it for as much as I remember didn't fix anything.

That works for the P990 radio
[T-Mobile LG G2x] apolkosnik:
With these changes the spi transactions are not stuck in the queue, as it was the case before, but at least now they get sent somewhere. I think that it brings us a bit closer.
[T-Mobile LG G2x] capncybo:
Thank you for your perseverance & patience...
[T-Mobile LG G2x] G2xer:
Don't want to get too off topic but thanks you guys. This phone sucks and you guys are really doing your best to make it awesome and that itself is awesome.My best wishes go to y'all!
[T-Mobile LG G2x] netsnation:
Not trying to sound too noobish, but what exactly do the SPI transactions control? Or does it have anything to do with the Radio?
[T-Mobile LG G2x] apolkosnik:
Through SPI, the Application Processor (AP) communicates with the Communication Processor (CP) , of course there's more to it.
[T-Mobile LG G2x] CrazyDelta:
This is one of the most interesting projects I've seen on XDA. The persistence and expertise of the developers here is amazing. I recommended T-Mobile's G2x to my sister when it first came out. It has not been ideal at all, but she still uses it. And up to today, I am hoping for a turn around that will make this phone great. Wish you all the best and thanks for the hard work.
[T-Mobile LG G2x] vaina001:
Does anyone need the service manual for this phone LG P999DW

Hi guys, i was doing spring cleaning on my HD and found the service manual for this phone, im not a programmer just an android enthusiast. I can imagine you guys already have it but just in case someone needs it for further development the link is below.

https://www.dropbox.com/s/2z2g1fn4yab43x3/LG P999 P999DW T-Mobile G2x service manual.pdf
[T-Mobile LG G2x] netsnation:
So do we know at all if maybe there is just an error in the code, or is it that code is missing? (Radio)
[T-Mobile LG G2x] justjackyl:
ahahahahaha

man that's great

Sent from my glorified LG pet rock™
[T-Mobile LG G2x] gggirlgeek:
I know it's a noob question and I hope I'm not annoying anyone but:

How difficult is it to get back to a Gingerbread rom after testing this Feb 2013 rom?

I have Nandroid backups and also stock Gingerbread roms saved on my SD card. I also use G2xScrubber.zip before any new Rom. If I need to do more than this to get back to one of my Gingerbread roms please instruct or point me to the link? (My searches provided no crystal clear answer and I don't want to dive into a mess.)

Thanks in advance.
[T-Mobile LG G2x] JHaste:
just nandroid restore...
[T-Mobile LG G2x] netsnation:
When I reverted back to Gingerbread I just wiped data, cache, battery, and dalvik cache. Then I just restored the backup and that should work for you
[T-Mobile LG G2x] gggirlgeek:
Thanks guys. Will take the plunge today then. I succesfully reverted back from ICS to Gingerbread today, doing exactly what you said (both nandroid restore, and CWM flash after clearing the stuff mentioned.) Added thanks to both of you.
[T-Mobile LG G2x] gggirlgeek:
OK, tested pretty thoroughly and honestly, if phone and GPS were working this would be my default.

I set up Voip calling with my Sipgate account. Works like a champ over my fast cable wifi. I tested it while maps and a couple of other resource eaters were running in the background too. No skipping, good quality audio.

Tested camera and was very impressed because it captured more detail in the threads of my jeans than I can see with the naked eye. So no quality problems here! :laugh: Video recording worked great too.

Maps and navigation actually did work wonderfully... uh, in the house over wifi. But of course that's useless. :crying:

Thanks for the effort and I'll be watching eagerly to see if the phone and GPS drivers get fixed. When I'm in the mood I might even try the dual boot trick to use this along side my favorite stable rom.

Thank you so much! :cool:
[T-Mobile LG G2x] tonyp:
Oh btw, as the P990 bugs will be present here as well I'll link our dev discussion thread here:

Let's fix up CM10.1 (bugs + discussion)

As we're using the same base you guys probably have the same problems on CM10.1.

While the focus will be on the radio of course, we'd be glad if you have ideas about Bluetooth accellerating or the issues with Autobrightness :good:
[T-Mobile LG G2x] King-Nai:
Just a quick question, what basebands are you guys using? Did the update for P990 come with a baseband update?
[T-Mobile LG G2x] tootone:
I believe the p999 is on v21, and the p990 s v30.
[T-Mobile LG G2x] gggirlgeek:
What do you mean? Cell phone and GPS don't work with Jellybean on this phone so no baseband is needed I thought. (I did try flashing my reliable old March 2011 (for_old_bb.zip) just to make sure but no service.)
[T-Mobile LG G2x] xp99:
Maybe we should try to figure out the difference of the P990 baseband between ics and gingerbread. They must have updated it for a reason.
[T-Mobile LG G2x] tootone:
I mean I know you're trying to help, but do you really think these guys haven't done that very thing.

Firstly, the p990 is useless to us because it has a different radio. Which is why we can't just pull the RIL over from it.

Secondly, they have been working on this for months and have done their research.
[T-Mobile LG G2x] bluenote73:
Where's mustang Tim when you need him to ride in and talk about his secret knowledge and brag about RC's contacts at LG that would be willing to give a helping hand?
[T-Mobile LG G2x] monte666:
Probably working on a bad ass mustang the stuff lg gave rc was for the p990 he couldn't get the radio working either on the 999 lg didn't give anyone anything for the g2x.
[T-Mobile LG G2x] grantusmantus:
From what I can gather that would take decompiling the ril, and if I'm not mistaken it would take some MONSTER hardware to do it, well, better computers than most of us have anyway.

Sent from miui
[T-Mobile LG G2x] djvoleur:
He's in the Nexus 4 forums :p

Ohai tonyp :p

I have an extra g2x...I wonder if I should dabble with it again...ooh you RIL issues...still there...I'm surprised no one has figured it out yet...