yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G2x] Ravinxx:
Wow they are really working their butts off over in the Dev thread. Thanks a lot Devs for doing all of this for us G2X users. I'm pretty happy with tonyp's CM10 hackfest but I would really love a full fledged CM10 for my G2X.
[T-Mobile LG G2x] professorpasta:
I'm subscribed to their dev thread, checking every post to see if I can help in some way. Those guys are doing amazing work, and I can't thank them enough! :good:
[T-Mobile LG G2x] PaKii94:
same i wish i could help but my coding is nowhere near par with the devs so like 90% of the text is gibberish to me :(. but i appreciate the efforts
[T-Mobile LG G2x] Mazout360:
Thanks to everyone for the encouragements!

On my side I am still very busy trying to figure out what's not working with the radio..

I had a question for you guys: I can try to build you a super-tweaked lagless kernel and remove wake locks to get a very nice battery life (since there's no radio, I'm aiming for at least 10-12h of uptime at least, we'll see :p) for the non-hackfest CM10 or CM10.1. I had several feedbacks of users who doesn't have a data plan and/or uses their P999 with dual boot and are actively using these builds. I have many tweaks and fixes in stock and will push out a new build if there's a demand for it.

EDIT : Forget the 10-12h. I've been using my latest kernel for 3h of debugging now and lost only 9%. I think I can aim for more :p
[T-Mobile LG G2x] Core Memory:
Yes, improve the kernel. Doing that will provide you with some relief from the frustrating radio/modem problems. "A change is as good as a rest", so "they" say.
[T-Mobile LG G2x] grantusmantus:
Absolutely!!! I dont think any of us g2xers would mind a battery friendly kernel. Thank you guys so much for all your work. Hang in there. A fully working cm10 and or 10.1 four our device would be a huge "in your face" to lg wich i think most G2x users would love to see.
[T-Mobile LG G2x] huy_gm:
Thanks for your kindness. Recently I played with those builds and your kernel alot. Your latest kernel seems less smooth than your initial beta releases (17 vs 43fps in nenamark 2). I think it because we sacrifice performance to save some juices for battery since battery life is incredible.
[T-Mobile LG G2x] plarmann:
I

That would be awesome. I am looking forward to it. Great work:)
[T-Mobile LG G2x] Mazout360:
I'm building a new kernel atm :p

Since there's a LOT of fixes (some modifying memory allocation and important drivers) I will have to beta-test it for some time before releasing it. If everything goes well, you should get more RAM (everybody likes that :p Aiming for an additional ~25mb at least), smartassv2 and hotplug governors (better battery and performances) and many fixes that should increase stability.

If you want to help me working out a perfect non-radio kernel, I need to know the problematic wakelocks on the device (there's an app for that I think) and some logcats when it hangs (if it does hang, my beta tests have been very successful up to now)

That is not normal. This is on build 1219 ? and which one had good fps, the 1211 or 1213 (or both) ? I did not beta test games so I need to know such issues.
[T-Mobile LG G2x] huy_gm:
Yep on build 1219. Nenamark is just an example, you can see the difference in smoothness overal when scrolling. I'm not sure which date but it's beta3 from your build here http://xdaforums.com/showthread.php?p=35311473 and build1e in few posts below that run smooth.
[T-Mobile LG G2x] hhwong:
Yes, I know i deserved to have my balls cut off for asking this........but I just need to ask, and I hate myself for asking...... >_<

Any clue if the radio can be fixed at all? My guess is yes honestly.....so...second question now.....If so, roughly when? I am not asking an exact date of course, I understand this is no easy task and I am not trying to push anyone for an answer, I am just curious about the progression. How close are we from the functioning radio? I just want a general idea.

If my post is bothering any of the devs, i am sorry and please delete this post.
[T-Mobile LG G2x] Mazout360:
Nobody could answer you exactly right now.

Could the radio be fixed ? I'd answer that nothing proves that it couldn't...yet.

When ? Very hard to tell. We're narrowing down the potential issues one by one. The source from LG is cr*p. Only thing I could say is we are doing some progress but the main problem isn't fixed yet, and a LOT of time has been given on this (on my side, probably the others dev too). Just take a look at the dev thread, and that doesn't include the hours of work between every posts.
[T-Mobile LG G2x] Core Memory:
It's also interesting that, as far as I know, no cell phone which has a Qualcomm MDM6600 has been updated/upgraded to ICS/JB. Maybe that means something about the ability to do it.

I recently read an advert from Qualcomm India to hire a developer to write and distribute open source code which is applicable to making Qualcomm cell radios/modems work with Android. To me, that looks like Qualcomm is trying to conteract the declining use by cell phone manufacturers of Qualcomm chips. The cell phone manufacturers hate Qualcomm's virtual monopoly and the high cost of using Qualcomm chips and the development costs of making them work in their devices.

The Motorola XOOM, a tablet, which has a Tegra 2 and a Qualcomm mdm6600 in one model, is running ICS but not with voice, only data, but the code used to do that isn't useful for the G2X unless someone of super-intelligence can morph the Motorola code to work with the G2X.
[T-Mobile LG G2x] SpaceRanger69:
Just an FYI guys, but LG released V30b for the P990.

http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGP990
[T-Mobile LG G2x] PaKii94:
i think tonyp compared it to v30a and it was almost the same besides very minor differences
[T-Mobile LG G2x] SpaceRanger69:
Never saw any mention in this thread, so I was just bringing it up.
[T-Mobile LG G2x] PaKii94:
is all good lol
[T-Mobile LG G2x] quishataylor:
When i wipe my system, install rom, the custom kernal for this rom, and jb 4.2 gapps, then boot, it says setup wizards has stopped. and an error message for gapps also pop up. What went wrong?
[T-Mobile LG G2x] khanh1289:
The Xoom is on its way to have full functioning 4.2 with Verizon LTE... i bought the Xoom basically the same time as the g2x. I wish LG would make things easier for our devs. The xoom does have more developers supporting it though.

Sent from my Nexus 4
[T-Mobile LG G2x] Mazout360:
Thanks for the share! I don't know if TonyP looked at the differences for our device, maybe they did fix some more things concerning our modem...I'll update my kernel base with the new source and see whats good in this.

EDIT: Well..is THERE a difference ? I don't see anything good AT ALL in the newer source...
[T-Mobile LG G2x] EggRoll53:
I feel really dumb whenever I look at the dev threads. I don't understand anything and I wish I could help :(
[T-Mobile LG G2x] faratl:
Phew thought it was just me lol.
[T-Mobile LG G2x] towelboy:
Not only just you guys..
[T-Mobile LG G2x] tonyp:
Yes, that happens if you (in this case: me) get quoted incorrectly.

I didn't say it's almost the same, I said it's exactly the same.

Nice prank LG.
[T-Mobile LG G2x] PaKii94:
oops mybad u guys all post late at night here in the US so stuff gets jumbled... i think someone else posted something about small changes/parameters different blah blah. I think thats the 2nd time I have misquoted u sorry :o
[T-Mobile LG G2x] adamiscool:
I had a dream last night that I booted into cm10 and radio worked. I was jumping for joy. Even though I agree that the dev thread is largely gibberish, in my eyes it seems with every post they're making it one more step closer. Narrowing it down seems mighty tedious, but your work will not be in vain! I feel these types of things should be resume worthy for getting tech jobs and such. Sure you're not "certified," but there are plenty of people out there who have maybe passed their certification tests because they learned the test material, but have no real practical knowledge from that grunt work called experience.

I'll stop ranting, but I hope my message is understood as pure encouragement! :beer::beer::beer::beer: cheers to you who work hard to help us measly users.
[T-Mobile LG G2x] Core Memory:
Progress is being made but not with getting the cell radio/modem working, yet.
[T-Mobile LG G2x] Mazout360:
I will try to debug the radio furthermore tomorrow, since my kernel is pretty much up to date and seems stable.

I have a request for anybody running GB with the radio on...could somebody PM me a full boot logcat, a cat /proc/kmsg (using adb shell) and a logcat -b radio ? That might inspire me. Thanks!
[T-Mobile LG G2x] jlev31415:
Logs generated, PM sent!
[T-Mobile LG G2x] projectzro:
Any new developments. The Dev section has been silent for days now. Getting a little worried the project is dying. But I could just be paranoid. If you devs need anything from me to help please let me know. I'm saying logcat wise
[T-Mobile LG G2x] Core Memory:
Activity is ongoing.
[T-Mobile LG G2x] ssuds:
2 posts above you dude!
[T-Mobile LG G2x] joeyxl:
Sure. Let me just grab the x64 drivers...
[T-Mobile LG G2x] Mazout360:
Indeed. There's no activity in the dev thread because we are all working on big workarounds and/or brainstorming about what could be wrong. When we'll get something to share it will be updated. Debugging takes a lot of time and, after all, we do have a life and need to work also :/ On my side, I contacted some people but seemingly this issue is not in the field of knowledge of most of the programmers I've talked to, so we're still alone on this. I still have hope, but it's really time-consuming. Thanks to the G2X community, you guys are all ready to help whenever we need it and we really appreciate that!
[T-Mobile LG G2x] tigger88:
I wish mirale will happen in next few weeks.

To AdamPK and Mazouu360, I have been following this thread everyday for last few weeks. I can tell you that I almost want to cry...really! You are so close getting it to work. At times I feel like we are in tunnel seeing some light on the end, but not getting any closer. Our G2x is a great phone, it really is a waste if the firmware cannot be updated. I have tried to change to other phones like iPhone and One S, none of them can beat the G2x in terms of overall features. In the end I switched back to my G2x phone. I really wish you and the community can find a way to fix the RIL function in coming weeks, so we can have a "newborn" G2x. Best wishes and happy new year!
[T-Mobile LG G2x] apolkosnik:
Thanks, I've been trying different things almost every day, and pouring through the docs, and building experimental builds on a daily basis, but since they are not very stable or have some things evidently broken, they are not worth any attention until I there is some good progress. I had to pull crazy long shifts at work lately, so I can't experiment as much, but the situation is getting better. I think that we might be pretty close, but the problem is that we can't talk to the radio chip from the RIL for whatever reason.
[T-Mobile LG G2x] SpaceRanger69:
Thanks for the continued efforts!! I know time is valuable, as I don't have nearly as much free time as I wish I had. Thank you for sacrificing whatever time you can on the ROM :)
[T-Mobile LG G2x] bochart:
tapped my build # enough times to become a developer, but I still can't post in the dev thread :o
[T-Mobile LG G2x] Core Memory:
After 10 posts.
[T-Mobile LG G2x] projectzro:
Sorry to stir things up. but thank you for the calm and informative update. like i said i was just worried things were going south again. i have spent well over $1000 on devices that have just failed in a few months after release, but i bought them based on specs. one was the Viewsonic gTablet. basically was the same as the Moto Xoom but with the Harmony chip-set and a crap-tastic screen lol.
[T-Mobile LG G2x] Core Memory:
I will never buy Viewsonic again. Many years ago, I paid over $700 in 1998 for a large, at the time, and technologically advanced Viewsonic colour crt monitor. It lasted just over 1 year, just past the end of the warranty, and it was too expensive to repair because the main board had a fault in it and that cost almost as much as a new monitor to buy and get installed. That has happened with other things, especially when I've been an "early adopter" of unproven technology. We who bought the G2X also got suckered into buying the "first" dual processor smartphone that LG doesn't support although it easily could. Now, it is up to us, if and when we can, to do it.
[T-Mobile LG G2x] towelboy:
Hey guys so I just flashed adams build 7 rom and I'm noticing problems with the Bluetooth, it can't search for devices around, reboot button doesn't reboot, just powers off and the keyboard when typing a few words it would auto close and turn on in about 10 seconds. Will flashing mazouts kernel fix any of this?

Edit: I flashed mazout360's kernel + fixed permissions and it fixed the Bluetooth issue! I installed another keyboard and that fixed the keyboard issue :D

Does anyone get the WiFi in the status bar displaying 0 signal even though there is?
[T-Mobile LG G2x] jlev31415:
This actually belongs in the dev thread, but I don't have enough posts under my belt to do so. I have tried building CM10.1 for the p999 for a few days, to no avail. I understand that the build is currently a modded p990 build, and after sifting through the makefiles and diffing my ROM against adampks's #7, I got the hint to manually copy some of the p990 proprietary files into the p999's directories and remove LGEInfineon.java, and I was able to successfully compile a ROM, and that ROM actually booted. Unfortunately, after booting, I get infinite "com.android.phone has stopped" pop-ups, and I'm unable to do anything with the build, not even connect with adb. I'm assuming that due to the p990-hybrid status of this project, there are a few more gotcha's that I'm missing in setting up a build environment.

Adampk (or Mazout360, or any other dev who is successfully building CM10.1 p999 ROM's): Could you please summarize the unique steps involved in building this ROM vs. the standard CM10.1 build procedure? I would greatly appreciate it!

By the way, I took the liberty to update my local_manifest.xml to the following, which I believe is as current as it gets. Please confirm,

<manifest>
<project name="CyanogenMod/android_device_lge_p990" path="device/lge/p990" remote="github" revision="cm-10.1" />
<project name="apolkosnik/android_device_lge_star-common" path="device/lge/star-common" remote="github" revision="jellybean" />
<project name="apolkosnik/lge-kernel-star" path="kernel/lge/star" remote="github" revision="cm-10.1" />
<project name="apolkosnik/device_p999" path="device/lge/p999" remote="github" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.1" />
</manifest>

Thanks!
[T-Mobile LG G2x] Mazout360:
The procedures are the same for CM10 and CM10.1, and your local-manifest seems good, just remove your first project name line as it shouldn't be needed. The phone issue could be because you deleted LGEInfineon (EDIT Just compiled CM10.1 without any RIL-related .java files and I didn't have this problem)..I don't know if Adam changed the reference to LGEStarRIL in his config files. Anyways, you won't get any radio since the problem comes from the kernel, so you'd be better not touching any files related to RIL/radio or you'll get force closes.

You can try and delete rild from system/bin, that might fix your android.phone issue.
[T-Mobile LG G2x] jlev31415:
Thanks for the response, Mazout360. I removed the p990 line from my local manifest as you recommended. I tried another clean sync and build so that I could post clean results here. Once again the build errored out because it couldn't find a number of symbols referenced in LGEInfineon.java. After some digging through the thread at http://xdaforums.com/showthread.php?t=2024590, I found a build step that had since been removed from the OP, so I tried it. It involved moving the LGEInfineon.java file instead of removing it:

mv ~/android/system/device/lge/star-common/ril/telephony/java/com/android/internal/telephony/LGEInfineon.java ~/android/system/frameworks/opt/telephony/src/java/com/android/internal/telephony/LGEInfineon.java

This step, as well as removing the file, both eliminate the error mentioned above. However, the compilation now errors out with the following:

make: *** No rule to make target `vendor/lge/p999/proprietary/etc/nvcamera.conf', needed by `out/target/product/p999/system/etc/nvcamera.conf'.

This error was the reason I tried copying proprietary files (like nvcamera.conf) from the p990 proprietary dir over to the p999 dir originally. The nvcamera.conf dependency as well as many other dependencies get written to vendor/lge/p999/p999-vendor-blobs.mk from device/lge/p999/proprietary-files.txt by device/lge/p999/setup-makefiles.sh. I have confirmed that these are the same files from Adam's device_p999 repo, although none of the referenced dependencies (e.g. vendor/lge/p999/proprietary/etc/nvcamera.conf) exist. I am at a loss for how to proceed building from here. Any further help would be greatly appreciated.
[T-Mobile LG G2x] Mazout360:
I've built several CM10 and CM10.1 builds for the P999 and never had those errors. Make sure you run extract-files.sh with the phone plugged in via ADB and verify that every file gets synced.

You might need to do some touch-ups on your local repo depending on the source you used. This is done either by modifying *.mk files or by deleting the file causing the issue. Sometimes, removing references from *.xml config files is required too. Also, you will get less errors by doing a clean build of CM10.
[T-Mobile LG G2x] laquer09:
Ironically, I'm making this post so that I can get to 10 posts and be able to hit the marketplace, where I'm seeking to buy a different phone. That said, might as well add some meat to this post.

To the devs who've been working on CM10 and battling this radio issue - you guys rock. I've been an android man since the G1 and a CM man since the first stable build ever. I'm utterly impressed and proud of guys like you who have made my phoning experience not only better via the software you've produced, but also...just fun. Lets all face it, we could live with stock anything and *probably* not die. The extra features are totally a bonus, but that's not why we're here. We're here because we're the kind of people that find it incredibly fun to f*ck around with our phones. I've been lurking these forums since 2008, and only lurking because I never really had anything beneficial to say to anyone, not because I'm antisocial. So, adam and the rest of y'all, hats off...and thank you. I've been managing custom dev projects for 11 years and your work would be impressive even if it were on a salary.

Most everyone else on here seem to be pretty cool and respectful to the devs. To the 10% of the folks that spend their time on here bashing LG and demanding stuff from devs as if they were your overly pampering mother....eh you're not worth the characters I'd type so I'll sum it up - Nvidia f'd this phone up and the devs have no reason to answer to you. Done.

update posts_i_need

set remaining_posts = 6

chill out, it was a single record table, i didn't need to specify the where clause ;)
[T-Mobile LG G2x] chrisram88:
Sorry bud, Market has been closed for some time.
[T-Mobile LG G2x] vmartinez39:
yes market is close. Was shocked to find this out. Had good experience with the people I bought and traded with. Wasn't screwed over on the deals/trades. Guess thats what really brought the hammer down.
[T-Mobile LG G2x] jlev31415:
Looks like it was simply an issue with the proprietary files. I incorrectly assumed augmenting the proprietary files in Adam's p999 repo with the files in the CM p990 repo would do the trick. I pulled the proprietary files off my phone and used them in the build, and sure enough, the build works great (sans radio, of course). Thanks again, Mazout360!

One final question: I could not get adb to function with the CM10.1 build, so I had to manually copy the proprietary files off to my SD card. I still cannot get adb to find my p999 while running CM10.1. The phone doesn't even present itself to the OS (i.e. not showing up in lsusb). I enabled developer options, but still no luck. This problem is positively related to CM10.1, because as soon as I flash back to CM7, I can adb to my heart's content. What are you doing in order to use adb to debug these ROM's?
[T-Mobile LG G2x] apolkosnik:
You are doing it wrong ;) Just kidding. I've used vendor blobs from p990 (TheMuppets' repo on github) , and supplemented them with some of the ones from p999, where needed or rather overwritten the radio related blobs with the ones from p999. I think that there were no need to even make any big adjustments in the scripts. Adb just works, but I think that you have to turn it on in the developer options.

@Mazout, regarding the results from that muic.c change, I didn't notice any difference.
[T-Mobile LG G2x] astrosfan94:
Gapps problem after install

Hello, I originally was getting gapps error messages on first boot after following the installation. I then installed rom and kenel only and was able to use the rom with no problems. I then went and installed gapps, and I keep getting error messages, now its show "Setup Wizard has stop" and does not allow me to get back to the home screen. I am able to get to the settings, but I did not see anything there. Any info on how to get it working correctly? Thanks!
[T-Mobile LG G2x] Mazout360:
Same as always..format cache and dalvik cache and fix permissions in recovery. If it's not working make sure you are using the correct gapps version (4.2.1 for build 7 (I think its Gapps-20121212) and 4.1.2 for build 6). That should fix 99,9% of gapps errors. Otherwise, switch from build 6 to 7 or vice-versa.
[T-Mobile LG G2x] thehumble1:
from the dev. thread:

You'd have to give us details about what the "something about bootload" says, but the short answer is no, it should boot fine. I'd clear your cache first but you really have to clear your data partition as well. Delete everything, reinstall and retry first. Shouldn't take more than 10 minutes.

do you get the two LG logos at boot? that would show you if you installed it correctly enough to be booting the right ROM.

if not then:

Check the Md5 on your download if you can, but you might just want to redownload and reinstall again.
[T-Mobile LG G2x] astrosfan94:
Thanks! It was the wrong Gapps listed on the original post. I downloaded 20121212 and it works fine with Built 7.
[T-Mobile LG G2x] 0b095:
okay thanks a lot, I will redownload number 7 and reinstall and notice you what happens.
[T-Mobile LG G2x] 0b095:
Unfortunately, the process com.google.process.gapps has stopped.

Unfortunately, Setup Wizard has stopped

Phone always gives me those errors on #7, the error over a black screen, I can also see time. I cannot get the desktop.

Unfortunately, Wi-Fi Calling has stopped.

I got that error occasionally on V6, so #6 is working fine so far.

I installed Mazout360's Modified Kernel it is supposed to be 1.2 ghz but phone does not have 1.2 ghz option at the performance-processor menu, it has 1 ghz max
[T-Mobile LG G2x] rbryant1983:
Re: [User Thread] AdamPk's and Mazout360's Unoffical CM10 For LG-P999

The same issue was posted on the same page you posted on as far as set up crashing.. Wrong gapps

And WiFi calling won't work since there's no data/phone.
[T-Mobile LG G2x] 0b095:
guy and also, I am using cm10.1 #6 rom and Mazout360's kernel. I got 5500 from antutu with them at 1.2GHz. I used to get 8500 when I was using different combinations. I do not care about numbers so phone looks pretty smooth and fast, but just in case, is everything OK? The score seems low...
[T-Mobile LG G2x] rbryant1983:
Re: [User Thread] AdamPk's and Mazout360's Unoffical CM10 For LG-P999

IMO scores don't matter much. I've never put much faith in them. As long as everything's smooth your good.