[ROM][BETA] CyanogenMod 10 for the LG Lucid

[MustardSeedPon]

I just tried two things to get my phone detected my ADB. I tried the USB Tether, fail, I got out of options and tried USB Mass Storage and nothing. Yes I did turn on Debugging. I went in cmd and did "adb devices", it brung up a list, that was empty meaning that it isn't detected.
I installed the LG Lucid drivers from the LG site, tried the tether, it was a fail. I put it in mass storage...and I got a strange device on my list named "52338c4 device". I did "adb logcat" and I brung up a whole bunch of stuff. I rebooted it, then the SAME device showed up, so I think I got ADB working properly. Did anything go wrong?

EDIT: Don't think anything went wrong, I'm not so good with adb, but this seems to be working properly.

You did one better than I could. I couldnt get that far. My computer installed drivers for the ADB upon plugging in the phone, but it wont show up in ADB devices nor can any programs see it. I would think my unit was defective if not for the fact that it works perfectly on stock. JB isnt that much of a deal for me now that I found a version of ICS that is rootable.

 

[JJPR97]

You did one better than I could. I couldnt get that far. My computer installed drivers for the ADB upon plugging in the phone, but it wont show up in ADB devices nor can any programs see it. I would think my unit was defective if not for the fact that it works perfectly on stock. JB isnt that much of a deal for me now that I found a version of ICS that is rootable.

Hm...well I'm not exactly sure how I did it, I know in SDK Manager I downloaded 4.1.2 and platform tools. After that I took cmd, put it in platform tools. I installed LG Lucid drivers from the LG site and I kept trying and opened cmd (In Platform tools) and kept doing adb devices until I got something. Your Lucid definitely isn't defective nor is the ROM causing this issue, It's just harder to access adb with this ROM, not sure why, but I can tell it works.

 

[xxwhynotxx]

Hm. Couldn't get my phone to turn on after a battery pull then plugged it in. Had to unplug it, turn it on, then plug it in.

 

[JJPR97]

Hm. Couldn't get my phone to turn on after a battery pull then plugged it in. Had to unplug it, turn it on, then plug it in.

Did you have the screen on while charging for about 25+ min?

If yes, then that's the Sleep of Death.

 

[xxwhynotxx]

Nah, it died, then when I plugged it in, waited 5 min, it refused to turn on.

 

[JJPR97]

Nah, it died, then when I plugged it in, waited 5 min, it refused to turn on.

Oh, that happened to me once, think of it as stock ROM (ICS), the phone only lights up the keys until sufficient enough charge to boot.

 

[stcarlso]

Hm. Couldn't get my phone to turn on after a battery pull then plugged it in. Had to unplug it, turn it on, then plug it in.

There still seems to be an issue with power-off charging. You found the workaround as best I know it, so I won't go into detail on that. But since it isn't a game breaker, it's in the big pile of things that will get fixed down the road after the random reboots are gone.

As for the EGL, I've tried 3 sets of drivers and they all reboot. So I think it's kernel related. It afflicts the spectrum too so it's not a problem with something we added or changed. I'm going to try and give egl a few MB of extra memory to see if it eliminates the issue or just forestalls it.

 

[JJPR97]

Someone help me out please.

http://androidforums.com/lucid-all-things-root/718893-help-fastboot-stuck.html

 

[xxwhynotxx]

I wondered if its what was mentioned before thanks.

Any thoughts on the volume problem shockey and I have besides reinstalling to see what that does?

 

[stcarlso]

I wondered if its what was mentioned before thanks.

Any thoughts on the volume problem shockey and I have besides reinstalling to see what that does?

I can't repro it, so a log maybe? It looks like you've tried wiping cache. Can you reflash dirty (i.e. no factory wipe) first and check that before backing up and wiping?

 

[xxwhynotxx]

Yeah I can do that!

When I do that, I need to flash the OS (obviously) then gapps. But do I need to reflash BB? Assuming yes?

Only two things I care about:

app data won't be touched right? Games etc?

But I'm assuming my custom brightness settings will be wiped? Any way to save that?

 

[stcarlso]

Yeah I can do that!

When I do that, I need to flash the OS (obviously) then gapps. But do I need to reflash BB? Assuming yes?

Only two things I care about:

app data won't be touched right? Games etc?

But I'm assuming my custom brightness settings will be wiped? Any way to save that?

You don't need to reflash baseband. You should fully backup in CWM anyways, but in theory absolutely nothing preference or data wise should be wiped.

 

[xxwhynotxx]

Sweet! Do I need to reflash Gapps?

Will do a backup before anyways.

 

[stcarlso]

Sweet! Do I need to reflash Gapps?

Will do a backup before anyways.

Maybe. They are supposed to stay through flashes of the same ROM. But I've had times where they FC and need reflashing.

 

[MustardSeedPon]

Hm...well I'm not exactly sure how I did it, I know in SDK Manager I downloaded 4.1.2 and platform tools. After that I took cmd, put it in platform tools. I installed LG Lucid drivers from the LG site and I kept trying and opened cmd (In Platform tools) and kept doing adb devices until I got something. Your Lucid definitely isn't defective nor is the ROM causing this issue, It's just harder to access adb with this ROM, not sure why, but I can tell it works.

If you manage to find a way to reproduce this, let me know. Also, I found something else to be weird. I just noticed (because I forgot to reflash) that upon putting stock back on that data was working fine still. So, I know now that I dont have to reflash my data settings for them to work. Which begs the question, why does CM not allow me to use my data? I went to the mobile network settings on CM and set everything properly. I think it has something to do with an error that shows up on initial setup of the ROM (where you set up Google account/wifi, etc) where it says "SIM card missing or invalid. Some phone features will be unavailable" But the dialer works fine and so does texting. Maybe something in JB or CM is blocking access to data whilst a bad SIM is inserted? ICS lets me use data fine, so IDK.

 

[stcarlso]

If you manage to find a way to reproduce this, let me know. Also, I found something else to be weird. I just noticed (because I forgot to reflash) that upon putting stock back on that data was working fine still. So, I know now that I dont have to reflash my data settings for them to work. Which begs the question, why does CM not allow me to use my data? I went to the mobile network settings on CM and set everything properly. I think it has something to do with an error that shows up on initial setup of the ROM (where you set up Google account/wifi, etc) where it says "SIM card missing or invalid. Some phone features will be unavailable" But the dialer works fine and so does texting. Maybe something in JB or CM is blocking access to data whilst a bad SIM is inserted? ICS lets me use data fine, so IDK.

This is probably to be expected since the RIL and APNs on this ROM are verizon based. You'll be more likely to get working data when the folks in the LG Connect 4G forums get working data, and they're having a hard time.

 

[xxwhynotxx]

Dirty flash did nothing for me.

 

[stcarlso]

Dirty flash did nothing for me.

I guess it's time for a wipe. While I'd look at your issue there are bigger problems to fry.

Speaking of which: tdm, does CM 10.1 on spectrum have the same out-of-memory crash that CM 10 has for us? If it doesn't crash in this way, I think that moving us up to 10.1 might fix several problems.

 

[Connorh333]

the talk about cm10.1 is making me nervous... Dropped my phone in a river... she is being treated with rice and might make a full recovery.

 

[tdm]

I guess it's time for a wipe. While I'd look at your issue there are bigger problems to fry.

Speaking of which: tdm, does CM 10.1 on spectrum have the same out-of-memory crash that CM 10 has for us? If it doesn't crash in this way, I think that moving us up to 10.1 might fix several problems.

The gl system crashes sometimes due to memory. I think the kgsl or adreno stuff has a leak.

 

[xxwhynotxx]

I guess it's time for a wipe. While I'd look at your issue there are bigger problems to fry.

Speaking of which: tdm, does CM 10.1 on spectrum have the same out-of-memory crash that CM 10 has for us? If it doesn't crash in this way, I think that moving us up to 10.1 might fix several problems.

Haha yeah I'm quite aware. Its really not that big an inconvenience right now so I'll probably wait until exams are over.

When I do, what all do I need to wipe? /system and /data?

 

[stcarlso]

The gl system crashes sometimes due to memory. I think the kgsl or adreno stuff has a leak.

In 10.1 the same issue occurs? I'm currently using diff to compare the kernel kgsl with the lg source looking for problems.

 

[tdm]

In 10.1 the same issue occurs? I'm currently using diff to compare the kernel kgsl with the lg source looking for problems.

Yeah in 10.1 also.

 

[xxwhynotxx]

Shoot just got the SoD.

 

[JJPR97]

Shoot just got the SoD.

Yeah it's very irretating, my phone is going to overheat soon haha damn screencast, I failed at a video 3 or 4 times, with full overclock settings it strains the phone and makes it so hot, no crash and yet the SoD happens over nothing -_-.