Root [ROM] [CM11] [4.4] CM11 For the LG Spectrum

[guppy0130]

I have to say (I'm new), updating from 4.0.4 to 4.4.2 is a big jump. But definitely worth it. Wifi/GPS/camera/cell work fine. Running an official cm build from March (the NEWEST April builds might work, but the first week or something of April broke wifi). I like it, but I'm getting times when the phone lags so much that it becomes inoperable and requires a pulled battery and boot to fix it. Official PAC nightlies are also out (KK), so I think an updated root/flash guide might be in order to accommodate everything?

 

[Neph81]

First Impressions

Can't sign into google before getting past the first run wizard. Phone and messaging don't show until after the wizard, but are needed to complete two step verification and the wizard.

Performance is still subpar in terms of system responsiveness and efficiency. The phone runs nuclear to do tasks it would stay cool for on stock rom.

Wifi works fine.

Opera crashed the system trying to scroll this forum's index of phone subforums.

LG logo still shows instead of blank screen on blank screen loading moments.

Signal strength meter still reads nil no matter how good it gets.

More to come with logcats and dogs.

Any logs you can provide would be appreciated. I'm going to do another repo sync and add in Deaths fixes and additions and try for another build. I can't re-create the data or the slow down issues right now so I'm at a loss as for what is going on there.

 

[BlasterMaster5]

Also, this version no longer has the problem of not picking up 1X/3G after getting off wifi. It shuffles between the two with finesse, using the V9 baseband, which we still need a zip for.

 

[BlasterMaster5]

Here, a log cat...

Download

 

[Neph81]

OK, so some basic things I can see going on.

W/InputMethodManagerService(630): Couldn't create dir.: /data/system/inputmethod

This is one of those things I had grep looking at, and I still couldn't find an answer. When we removed the mkdir in the wifi fix, I'm not sure that mkdir /data/system exists in any other init file. I'm sure something is creating the directory, eventually, but we're not assigning it any permissions as far as I can tell.

fore  T   257315 kB: air.com.innogames.grepolis (7996) top-activity

I'm not sure what game that is, but it's taking 257MB of the RAM, which would explain the chugging you were getting. I should really get back into the kernel settings, as I know there is a patch to free up/remove the reserved "low memory".

04-12 01:10:35.936 I/chromium(10619): [10619:10659:0412/011035:2439545740:INFO:image_transport_surface.cc(63)] Using shared widget transport surface
04-12 01:10:35.936 W/Adreno200-EGL(10619): <qeglDrvAPI_eglSwapInterval:3726>: EGL_BAD_SURFACE
04-12 01:10:35.936 E/chromium(10619): [10619:10659:0412/011035:2439549188:ERROR:gl_context_egl.cc(177)] eglSwapInterval failed with error EGL_BAD_SURFACE
04-12 01:10:36.297 I/chromium(10619): [10619:10619:0412/011036:2439913843:INFO:CONSOLE(26)] "The value "device-width;" for key "width" is invalid, and has been ignored.", source: http://androidforums.com/spectrum-all-things-root/800153-rom-cm11-4-4-cm11-lg-spectrum-11.html#post6520887 (26)
04-12 01:10:36.297 I/chromium(10619): [10619:10619:0412/011036:2439914270:INFO:CONSOLE(26)] "The value "1.0;" for key "initial-scale" was truncated to its numeric prefix.", source: http://androidforums.com/spectrum-all-things-root/800153-rom-cm11-4-4-cm11-lg-spectrum-11.html#post6520887 (26)
04-12 01:10:36.297 I/chromium(10619): [10619:10619:0412/011036:2439914545:INFO:CONSOLE(26)] "The value "1.0;" for key "maximum-scale" was truncated to its numeric prefix.", source: http://androidforums.com/spectrum-all-things-root/800153-rom-cm11-4-4-cm11-lg-spectrum-11.html#post6520887 (26)
04-12 01:10:36.297 I/chromium(10619): [10619:10619:0412/011036:2439915216:INFO:CONSOLE(26)] "Error parsing a meta element's content: ';' is not a valid key-value pair separator. Please use ',' instead.", source: http://androidforums.com/spectrum-all-things-root/800153-rom-cm11-4-4-cm11-lg-spectrum-11.html#post6520887 (26)

This part really concerns me. I'll need to dig into why you were getting bad EGL surface errors.

04-12 01:10:55.866 W/Adreno200-EGLSUB(10619): <CacheInvalidateHandle:223>: PMEM_INV_CACHES undefined
04-12 01:10:55.866 W/Adreno200-EGLSUB(10619): <CacheInvalidateHandle:241>: Invalidate failed : handle 0x985840 (offs=0 len=381000)
04-12 01:10:55.866 W/Adreno200-ES20(10619): <core_glReadPixels:212>: GL_OUT_OF_MEMORY

More out of memory stuff. There is a good possibility, that my display fixes did more harm, than good, and will be removed from the next upload.

 

[death2all110]

OK, so some basic things I can see going on.

W/InputMethodManagerService(630): Couldn't create dir.: /data/system/inputmethod

This is one of those things I had grep looking at, and I still couldn't find an answer. When we removed the mkdir in the wifi fix, I'm not sure that mkdir /data/system exists in any other init file. I'm sure something is creating the directory, eventually, but we're not assigning it any permissions as far as I can tell.

We actually are assigning it some permissions in the init.rc, all of /data is. As for /data/system/inputmethod... how is it trying to make the directory? plain mkdir or mkdir -p?

fore  T   257315 kB: air.com.innogames.grepolis (7996) top-activity

I'm not sure what game that is, but it's taking 257MB of the RAM, which would explain the chugging you were getting. I should really get back into the kernel settings, as I know there is a patch to free up/remove the reserved "low memory".

I need to get in there and add some governors/OC. I'll look into the low memory things as well.

04-12 01:10:35.936 I/chromium(10619): [10619:10659:0412/011035:2439545740:INFO:image_transport_surface.cc(63)] Using shared widget transport surface
[B]04-12 01:10:35.936 W/Adreno200-EGL(10619): <qeglDrvAPI_eglSwapInterval:3726>: EGL_BAD_SURFACE[/B]
[B]04-12 01:10:35.936 E/chromium(10619): [10619:10659:0412/011035:2439549188:ERROR:gl_context_egl.cc(177)] eglSwapInterval failed with error EGL_BAD_SURFACE[/B]
04-12 01:10:36.297 I/chromium(10619): [10619:10619:0412/011036:2439913843:INFO:CONSOLE(26)] "The value "device-width;" for key "width" is invalid, and has been ignored.", source: http://androidforums.com/spectrum-all-things-root/800153-rom-cm11-4-4-cm11-lg-spectrum-11.html#post6520887 (26)
04-12 01:10:36.297 I/chromium(10619): [10619:10619:0412/011036:2439914270:INFO:CONSOLE(26)] "The value "1.0;" for key "initial-scale" was truncated to its numeric prefix.", source: http://androidforums.com/spectrum-all-things-root/800153-rom-cm11-4-4-cm11-lg-spectrum-11.html#post6520887 (26)
04-12 01:10:36.297 I/chromium(10619): [10619:10619:0412/011036:2439914545:INFO:CONSOLE(26)] "The value "1.0;" for key "maximum-scale" was truncated to its numeric prefix.", source: http://androidforums.com/spectrum-all-things-root/800153-rom-cm11-4-4-cm11-lg-spectrum-11.html#post6520887 (26)
04-12 01:10:36.297 I/chromium(10619): [10619:10619:0412/011036:2439915216:INFO:CONSOLE(26)] "Error parsing a meta element's content: ';' is not a valid key-value pair separator. Please use ',' instead.", source: http://androidforums.com/spectrum-all-things-root/800153-rom-cm11-4-4-cm11-lg-spectrum-11.html#post6520887 (26)

This part really concerns me. I'll need to dig into why you were getting bad EGL surface errors.

Assuming you're talking about the bold text, then yes that is concerning. The other chromium stuff is because of the poor programming of the mobile site.

04-12 01:10:55.866 W/Adreno200-EGLSUB(10619): <CacheInvalidateHandle:223>: PMEM_INV_CACHES undefined
04-12 01:10:55.866 W/Adreno200-EGLSUB(10619): <CacheInvalidateHandle:241>: Invalidate failed : handle 0x985840 (offs=0 len=381000)
04-12 01:10:55.866 W/Adreno200-ES20(10619): <core_glReadPixels:212>: GL_OUT_OF_MEMORY

More out of memory stuff. There is a good possibility, that my display fixes did more harm, than good, and will be removed from the next upload.

Yeah, I think its because we took the memory away from PMEM. LG actually still uses PMEM a bit on this device. At least in stock it did. Pretty sure the camera still gets memory from PMEM as the camera blobs are old... They didn't even update them for the ICS build to switch to ION. I'm actually growing quite tired of LG's crap. Which is why I haven't owned an LG device since the LG Ally. /End Rant

Doesn't mean I'll give up on this though.

Definitely need to dig. I'll dig into InputMethodManagerService code to see if I can find the mkdir code.

The EGL issues seem pretty serious too :/

Still a lot of work to be done, but I know we can do it!

Ready.... BREAK!

 

[Neph81]

Death, keep in mind, that my last upload also included some new fixes. My Git repo is up to date with what I posted, but there may have been some unintentional side effects from them. Time to start digging and testing, I guess.

 

[JPJoller]

I just wanted to say thank you to death2all, and Neph81 for keeping this thing going. I realize that our processor is only an S3 snapdragon, but combined with the wonderful display and 1g of ram, I keep thinking that KK will run smoothly on this. Thanks for all of your hard work!!

 

[BlasterMaster5]

Of note, the browser being used is Opera, and the game is Grepolis. However, overall performance is by feel, not limited to just that game, but to just daily using it. Stock debloated still feels more responsive.

 

[Neph81]

Of note, the browser being used is Opera, and the game is Grepolis. However, overall performance is by feel, not limited to just that game, but to just daily using it. Stock debloated still feels more responsive.

Yeah, I did another repo sync and build, and the kernel tweaks I put in are causing massive issues. They're being removed tonight.

On a positive note, I may have fixed some of the bluetooth issues. The next build will have them, and I'll be looking for more testers to confirm.

 

[reeseboy]

Yeah, I did another repo sync and build, and the kernel tweaks I put in are causing massive issues. They're being removed tonight.

On a positive note, I may have fixed some of the bluetooth issues. The next build will have them, and I'll be looking for more testers to confirm.

I'm ready for testing... just sayin

 

[MotoTurbo]

Any idea what time the new nightly will be released? Cuz I get a free 10gb between 2-8am lol. God I hate satellite internet haha no rush tho eagerly waiting

 

[Neph81]

http://androidfiles.massivefilehost.com/cm11/cm-11-20140415-UNOFFICIAL-vs920.zip

New build. I removed most, but not all, the stuff I added to the kernel with that last merge.

This build includes corrections to bluetooth and graphics permissions. Hopefully, this will fix some of the issues that users are having. Once I get confirmation that we have improvements, I'll update my public repo.

Edit: I did not add D2As OTG patch yet, as I want to make sure I'm back on stable kernel settings, before I go forward again.

 

[BlasterMaster5]

For grabbing the logcats, I use the free app Catlog, which not only shows it, but also exports it in text file format to the memory card. Anyone testing this rom needs to be posting logcats of things happening.

 

[George55155]

Sooner ones my vs920 just goes haywire and turns off the display when I'm doing simple tasks like texting And switching over to my music app. By haywire I mean the display turns off and won't turn back on until after a while OR sometimes it'll just turn off the whole phone and I have to forcefully power it off and turn it on again. Here's my logcat hope it's of some help https://docs.google.com/file/d/0B9yr1NmDyYuaQ2tUN2M2dVppWVE/edit?usp=docslist_api

Also I'm running Neph's latest unofficial buil with the most recent pagapps also with some xposed modules installed but I had this installed before and those didn't seem to cause issues?

 

[Neph81]

Sooner ones my vs920 just goes haywire and turns off the display when I'm doing simple tasks like texting And switching over to my music app. By haywire I mean the display turns off and won't turn back on until after a while OR sometimes it'll just turn off the whole phone and I have to forcefully power it off and turn it on again. Here's my logcat hope it's of some help https://docs.google.com/file/d/0B9yr1NmDyYuaQ2tUN2M2dVppWVE/edit?usp=docslist_api

Also I'm running Neph's latest unofficial buil with the most recent pagapps also with some xposed modules installed but I had this installed before and those didn't seem to cause issues?

Your logcat is not public, but I did send you a request to share it. When your phone went haywire, were you in a low radio signal area? This seems to be the common thread to all the issues I have with the 4-15 build. Otherwise, it's back to rock solid.

 

[George55155]

Your logcat is not public, but I did send you a request to share it. When your phone went haywire, were you in a low radio signal area? This seems to be the common thread to all the issues I have with the 4-15 build. Otherwise, it's back to rock solid.

Accepted your request and well I've been noticing that its mainly everywhere I go cause it just did it right now lol (using ipod to type) and my signal strength was 2-3 bars and it also seemed to do it as well as other places such as the bank which if I recall correctly had a good signal strength

 

[MjDaGreat]

Last time I tried to flash the rom and gaaps my play store wouldn't let me log in it would tell me connection to server lost

 

[jlove1974]

I've having similar issues after dirty flashing from the earlier April 8th build. I cleared dalvik and flashed over it yesterday. I have had freezes during incoming texts, while unplugging from charging, etc. Random goofiness that I didn't have with the March builds.

What works: Wifi, Cell data, basically everything works
What doesnt: random freezes in various apps. Maybe a memory issue?

Anyhow, I've attached my latest log.

 

[Neph81]

I've having similar issues after dirty flashing from the earlier April 8th build. I cleared dalvik and flashed over it yesterday. I have had freezes during incoming texts, while unplugging from charging, etc. Random goofiness that I didn't have with the March builds.

What works: Wifi, Cell data, basically everything works
What doesnt: random freezes in various apps. Maybe a memory issue?

Anyhow, I've attached my latest log.

I would honestly suggest doing a clean install if your current ROM is pre-4/14/14. CM made a lot of changes to the core system files, and I've been doing a fair amount of permission changes, so even I ended up wiping, to clear out some old junk.

I have a new 4-16 build, that I will be testing today. I reverted some of the new radio changes, and will be seeing if that fixes the data issues I was seeing. If so, I will push that build tonight, and let people evaluate it.

 

[jlove1974]

Yeah I was expecting that answer
I did a fresh install of 4/08 and was trying to avoid reinstalling all those apps even with Ti Backup.
Anyhow, I can live with it for now, and it is definitely better than it was. If I wipe I might just try AOKP.

This thing is still my EDC/DD so........I'm looking at new phones

 

[BlasterMaster5]

Use the backup/restore feature of CWM

 

[jlove1974]

Yeah I do backups. But putting on a fresh rom and restoring apps takes time I don't have right now, maybe on a weekend.

 

[bones420la]

*Wrong thread*

 

[Neph81]

Well, no dice on the radio changes fixing the issues I'm having at low radio strength. Back to digging through recent changes.