• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

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

It freezes after I spend time in a certain app. For example, I'll watch YouTube for 30mins close the app and it freezes once I touch the statusbar.
 
After hours of searching and days hearing about the 3/14 build I have finaly found it and must say its is the most stable of them all added with apex launcher. Very happy
 
Here's the deal behind the status bar freezing.

Code: 
[ 05-01 23:56:09.252   570:  602 E/ActivityManager ]

ANR in com.teslacoilsw.launcher (com.teslacoilsw.launcher/com.android.launcher2.Launcher)

PID: 12347

Reason: Input dispatching timed out (Waiting because the focused window has not finished processing the input events that were previously delivered to it.)
The app itself is crashing, which then hangs the entire system, while it restarts itself. This is either do to a permissions error, or a CPU/memory issue. I'll try and dig into it, but I'm not sure how hard of a fix this is going to be.
 
Teslacoil is the main launcher(ie the pull down menu)for CM, as far as I can tell. I'm using Nova as my home screen. Everything seems to be related though, as any time an app crashes, it's from a panic, from the program not responding for so long. At least now I have a few logs to comb through and see if there are any similarities.
 
I tried the 03/14 dirty install over the 03/07 official and no good. I'll have to try again clean install when I have time.
 
I'm sure you guys are hard at work developing these roms for us is there a way I can test any builds and provide logcats? Keep up the great work guys (:
 
I'm not sure what D2A is up to, but here is where I am at. I hate CM11 builds, past March. They became worse and worse, until we started getting issues with even the status bar. I keep looking at all these updates being pushed, and I see fixes for newer phones, but very little for older phones. This just disappoints me. Also, TDMs job seems to be keeping him very busy, so I do not know that we will be seeing him around here much anymore. This sucks, because he was one of our best source of fixes, besides D2A and myself.

With that said, I'm working on a roll back. Everyone knows that I loved my 3/14 build. I found it the most stable thing in the world. However, rolling back github to a particular date is not all that easy. Mainly, because there is not just one git you're rolling back. You're rolling back around 300 of them, and hoping you don't miss one, which will cause a build fail. I'm slowly making progress, but still keep getting BT error messages, in the builds. Once I have a roll back to 3/14, I will be splitting off my builds to a new thread. 3/14 will be focused on fixes real issues, not patching stuff that CM breaks. I'm also hoping to add some actual tweaks in. All this is contingent on my getting builds running before 5/27, as that is when school starts back up. If I don't get it figured out by then, I probably won't have much to offer until late July.

So, there you have it. My status update for the weekend.
 
I hope to see a performance fix in your build. If there is anything the Speac *really* needs, it's optimization. I found that a $48 Windows 8 phone with a slower CPU and half the RAM performs far better than this device. Alao, the Spec goes absolutely nuclear when you have it unoptimized and try to do anything.
 
In anticipation of future improvements by our in house devs and not CM, and since AOKP KK is basically an orphan, I have flashed backed to 3/14 build. Of course, my contract is almost up with VZW too. So good things on the horizon.
 
It depends on what ROM you're currently on, and what build. At some point in April, CM did big changes to telephony. If you downgrade, from one of those builds, you'll get constant force close errors.

Also, update on my end, fixed the bluetooth build issues, only to run into stagefright build issues. But at least it's progress.
 
There you go
 

Attachments

  • 1400723370240.jpg
    1400723370240.jpg
    42.5 KB · Views: 258
No dice on getting this done before 5/27, but I did discover part of my issue. For some reason, the "Make Clean" command, was undoing some of my "git reset --hard (SHA hash)" uncommits. And it was never all of them, and it was always random. I'll still keep giving this a shot, but that glitch is giving me a lot of headaches, all on its own.
 
Neph81 said:
No dice on getting this done before 5/27, but I did discover part of my issue. For some reason, the "Make Clean" command, was undoing some of my "git reset --hard (SHA hash)" uncommits. And it was never all of them, and it was always random. I'll still keep giving this a shot, but that glitch is giving me a lot of headaches, all on its own.
Click to expand...

You da man! Maybe it's a good thing to step back for awhile. It always helped me to refresh perspective.
 
LillieBennett said:
You da man! Maybe it's a good thing to step back for awhile. It always helped me to refresh perspective.
Click to expand...
Yeah. Actually, I thought about it more, and realized that I should be writing a script anyways. That way, I can hand the script to anyone, and go here, run this, and you can build where I am at. Also, it means no matter what gets messed up, I can run the script and fix it.
 
Neph: do you use a project branch? Makes things really easy. I always keep a "work" branch. Each day, I repo sync, save off the manifest, checkout work, and run a small script to rebase. To submit to gerrit you need to checkout upstream and pick the commit that you want to upload.
 
tdm said:
Neph: do you use a project branch? Makes things really easy. I always keep a "work" branch. Each day, I repo sync, save off the manifest, checkout work, and run a small script to rebase. To submit to gerrit you need to checkout upstream and pick the commit that you want to upload.
Click to expand...
TDM: At this point I am not, but it will be something I will look into today. Gerrit is still a long ways off for me as none of what I am currently working on, is not being submitted to the official CM tree.

On that note, maybe you can help me out here. How is it, that bootable/recovery calls out files, that exist in /external/busybox , but the files don't exist till months later in the BB repo? The file in question is busybox-minimal.links . When I revert the git, the files no longer exist, even though they are clearly being called out.

Jan 19th commit - Files don't exist https://github.com/CyanogenMod/andr...tree/d9e0c438e10e2155513e5d26498af472c5137d65

Apr 4th commit - Files do, but there is nothing in the commit that added them. https://github.com/CyanogenMod/andr...tree/6786b974a95ee8a263a76381074c55083faf123c
 
It's been forever since I did a new build, but I have a slow semester at college and I wanted something that did not have a lot of the security issues that have been announced since my 3/14/14 release. With that said, this is a basic CM build. I resync'd all my repos and made just enough changes to get it to compile. CM must have finally fixed a lot of their slow down issues because this one still responds well. I do recommend going into settings -> performance -> memory management -> and checking Kernel Samepage Merging . This will probably be my only build unless I fix something major while I tinker. If you find a bug that I do not already know about, let me know.

As for the link, here you go.

http://androidfiles.massivefilehost.com/cm11/cm-11-20150915-UNOFFICIAL-vs920.zip
 
You must log in or register to reply here.
Back
Top Bottom