[Q] Gueste2x v3.6 Appdrawer lag --> please close the thread - LG Optimus 2x

I "solved" the problem. I updated to a newer version.
Hi,
maybe someone can help. I am using Gueste2x Hybrid Revolution v3.6 Rom.
This ROM is really great and works pretty smooth.
...But, sometimes the appdrawer lags terribly.
I don't know if the an app is causing the lag.
I only got the lag within the appdrawer.
I got the following log messages:
E/GraphicsJNI( 2195): VM won't let us allocate 69120 bytes
D/dalvikvm( 2195): GC_FOR_MALLOC freed <1K, 53% free 4775K/9991K, external 39117K/40895K, paused 28ms
D/dalvikvm( 2195): GC_EXTERNAL_ALLOC freed <1K, 53% free 4775K/9991K, external 39117K/40895K, paused 34ms
E/dalvikvm-heap( 2195): 69120-byte external allocation too large for this process.
I am using BB/RIL 0725. I have also attached the log file.
Thanks for your help.

Related

Blank video, bad mencoder script?

Has anyone had issues playing videos in recent CM roms? Somewhere between android 1.5 and 1.6 files I've encoded with below broke. While sound plays, the video output is blank:
Code:
mencoder "$2" -o "$2.tmp.mp4" -vf dsize=480:352:2,scale=-8:-8,harddup -oac faac -faacopts mpeg=4:object=2:raw:br=128 -of lavf -lavfopts format=mp4 -ovc x264 -x264encopts bframes=0:bitrate=512:threads=auto:global_header
ffmpeg -i "$2.tmp.mp4" -vcodec copy -acodec copy "$2.and.mp4"
I've checked and it's not the ramhack patch, and it's been tried on multiple players. Oddly a short video ripped from youtube works. I think it's an android 1.5 -> 1.6 change that requires new encoder lines. Can someone post mencoder/ffmpeg/etc commands that produce videos playable in a recent rom?
Logcat output from a failed attempt.
Code:
11-30 08:10:16.625 I/ActivityManager( 331): Start proc com.android.camera for activity com.android.camera/.MovieView: pid=1202 uid=10021 gids={1006, 1015, 2001, 3003}
11-30 08:10:21.515 I/ActivityManager( 331): Displayed activity com.android.camera/.MovieView: 5089 ms (total 5089 ms)
11-30 08:10:21.905 W/QCvdec ( 315): vdec: Creating H264 Decoder [0x9fae0]
11-30 08:10:21.905 W/QCvdec ( 315): vdec: NAL lenght [0]
11-30 08:10:21.905 W/QCvdec ( 315): vdec: START CODE....
11-30 08:10:21.975 W/ADSP_RTOS_SVC( 315): VDL_QDSP_rtos_event_cb
11-30 08:10:21.975 W/ADSP_RTOS_SVC( 315): VDL_QDSP_rtos_event_cb
11-30 08:10:23.066 W/AudioFlinger( 315): write blocked for 83 msecs
11-30 08:10:32.765 W/WindowManager( 331): Key dispatching timed out sending to com.android.camera/com.android.camera.MovieView
11-30 08:10:32.765 W/WindowManager( 331): Dispatch state: {{KeyEvent{action=1 code=66 repeat=0 meta=0 scancode=28 mFlags=8} to Window{43baf640 org.connectbot/org.connectbot.ConsoleActivity paused=false} @ 1259568605596 lw=Window{43baf640 org.connectbot/org.connectbot.ConsoleActivity paused=false} [email protected] fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{43afca90 com.android.camera/com.android.camera.MovieView paused=false}}}
11-30 08:10:32.775 W/WindowManager( 331): Current state: {{null to Window{43afca90 com.android.camera/com.android.camera.MovieView paused=false} @ 1259568632775 lw=Window{43afca90 com.android.camera/com.android.camera.MovieView paused=false} [email protected] fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{43afca90 com.android.camera/com.android.camera.MovieView paused=false}}}
11-30 08:10:34.255 I/ActivityManager( 331): ANR in process: com.android.camera (last in com.android.camera)
11-30 08:10:34.255 I/ActivityManager( 331): Annotation: keyDispatchingTimedOut
11-30 08:10:34.255 I/ActivityManager( 331): CPU usage:
11-30 08:10:34.255 I/ActivityManager( 331): Load: 4.83 / 4.41 / 3.88
11-30 08:10:34.255 I/ActivityManager( 331): CPU usage from 17087ms to 3261ms ago:
11-30 08:10:34.255 I/ActivityManager( 331): mediaserver: 58% = 39% user + 19% kernel / faults: 1703 minor 61 major
[snip: nothing useful]
11-30 08:10:34.835 I/Process ( 331): Sending signal. PID: 1202 SIG: 3
11-30 08:10:34.865 I/dalvikvm( 1202): threadid=7: reacting to signal 3
11-30 08:10:35.035 I/Process ( 331): Sending signal. PID: 331 SIG: 3
11-30 08:10:35.035 I/dalvikvm( 331): threadid=7: reacting to signal 3
[snip:more of the last line]
11-30 08:10:38.965 W/WindowManager( 331): Continuing to wait for key to be dispatched
11-30 08:10:44.245 W/WindowManager( 331): Key dispatching timed out sending to com.android.camera/com.android.camera.MovieView
11-30 08:10:44.255 W/WindowManager( 331): Dispatch state: {{KeyEvent{action=1 code=66 repeat=0 meta=0 scancode=28 mFlags=8} to Window{43baf640 org.connectbot/org.connectbot.ConsoleActivity paused=false} @ 1259568605596 lw=Window{43baf640 org.connectbot/org.connectbot.ConsoleActivity paused=false} [email protected] fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{43b0c3b8 Panel:com.android.camera/com.android.camera.MovieView paused=false}}}
11-30 08:10:44.255 W/WindowManager( 331): Current state: {{null to Window{43afca90 com.android.camera/com.android.camera.MovieView paused=false} @ 1259568644259 lw=Window{43afca90 com.android.camera/com.android.camera.MovieView paused=false} [email protected] fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{43b0c3b8 Panel:com.android.camera/com.android.camera.MovieView paused=false}}}
11-30 08:10:45.485 I/WindowManager( 331): WIN DEATH: Window{43adbe58 com.android.browser/com.android.browser.BrowserActivity paused=false}
11-30 08:10:50.045 I/ActivityManager( 331): Start proc com.android.bugreport for broadcast com.android.bugreport/.BugReportReceiver: pid=1213 uid=10034 gids={1007, 1015}
11-30 08:10:50.275 I/ActivityManager( 331): Process com.android.browser (pid 673) has died.
11-30 08:10:50.675 W/WindowManager( 331): Continuing to wait for key to be dispatched
11-30 08:10:50.675 W/WindowManager( 331): No window to dispatch pointer action 1
11-30 08:10:52.125 I/ActivityManager( 331): Killing process com.android.camera (pid=1202) at user's request
You sure that that *ever* worked? I think I tried something like that once and got the same result as you. And this would have been an older version of android, probably 1.0 or 1.1. As far as I can tell, the only limitation is the decoder chip itself -- the android version shouldn't make any difference.
Anyway, this should work: (notice the -x264encopts...)
Code:
mencoder "$2" -o "$2.tmp.mp4" -vf dsize=480:352:2,scale=-8:-8,harddup -oac faac -faacopts mpeg=4:object=2:raw:br=128 -of lavf -lavfopts format=mp4 -ovc x264 -x264encopts nocabac:level_idc=30:bframes=0:bitrate=512:global_header:threads=auto:subq=5:frameref=6:partitions=all:trellis=1:chroma_me:me=umh
lbcoder said:
You sure that that *ever* worked? I think I tried something like that once and got the same result as you. And this would have been an older version of android, probably 1.0 or 1.1. As far as I can tell, the only limitation is the decoder chip itself -- the android version shouldn't make any difference.
Anyway, this should work: (notice the -x264encopts...)
Code:
mencoder "$2" -o "$2.tmp.mp4" -vf dsize=480:352:2,scale=-8:-8,harddup -oac faac -faacopts mpeg=4:object=2:raw:br=128 -of lavf -lavfopts format=mp4 -ovc x264 -x264encopts nocabac:level_idc=30:bframes=0:bitrate=512:global_header:threads=auto:subq=5:frameref=6:partitions=all:trellis=1:chroma_me:me=umh
Click to expand...
Click to collapse
No dice, the video is still black. Which rom / device have you used this with? If CM, did you merge in the HTC recovery?
Fyi I've tried videos encoded and sucessfully played in earlier roms, still black...so either something broke in the decoder chip driver, the chip itself is kaput or there's a setting somewhere causing this.
Fnorder said:
No dice, the video is still black. Which rom / device have you used this with? If CM, did you merge in the HTC recovery?
Fyi I've tried videos encoded and sucessfully played in earlier roms, still black...so either something broke in the decoder chip driver, the chip itself is kaput or there's a setting somewhere causing this.
Click to expand...
Click to collapse
I wouldn't go near a CM-mod. Too slow/unstable/unreliable/broken. Try a stock ADP1 image. That line I gave you will *definitely* give you a compatible video.

[Q] VM heap size

ROM: CM6 from 08.12.2010
Overclocking: Interactive governor : 1000mhz : vsel 62
Launcher: Launcher Pro
Note: I disabled "keep home in memory"
I was using 800mhz with 52 vsel and vm heap size 32 and I wanted to test an app "TV Flash"
It's an app that plays tv through flash and I was keep getting app crashes everytime I played my favorite channel.
I overclocked as mentioned above (1000mhz ....) and I set the vm heap size to 50m.
I believe this is the amount of ram that can be alocated to an app. Am i right?
Now my favorite channel plays flawless.
My question is:
Is there a problem of keeping the vm heap size to 50m, 64m?
Thanks guys!
Nope, no problems. Just that you'll run out of memory very quickly if you do something intensive.
Lollipop_Lawlipop said:
Nope, no problems. Just that you'll run out of memory very quickly if you do something intensive.
Click to expand...
Click to collapse
Well then...It seems that I missunderstood what vm heap size is!
Can you please explain and recommend a way so I wont run out of ram when watching live streams?
And do you think that the release of froyo will fix this issue?
There's nothing you can really do about it. You'll just have home reloaded and other applications closed. The only solution is to buy a phone with 512mb of memory.
Froyo isn't a magical upgrade. The most we will probably see from the firmware is feature parity with the Milestone 2 (minus Milestone 2 specific features and BLUR). All performance related stuff is mostly in our hands already (think JIT).
[EDIT] JIT actually takes up a bit more of your RAM. The difference is quite noticeable if you multitask a lot.
Is there a optimal heap size we should use? What effects does it have if you set the heap size smaller or greater?
Just tried increasing the heap size on my phone. Set it to 48MB and angry birds, my text editors, etc, all finally run consistently smooth. Launcher reloads more often now, but that's not a big deal given the much improved in app experience for me.
Sworkhard said:
Just tried increasing the heap size on my phone. Set it to 48MB and angry birds, my text editors, etc, all finally run consistently smooth. Launcher reloads more often now, but that's not a big deal given the much improved in app experience for me.
Click to expand...
Click to collapse
Yes...Apps seem to not crash because they are being allocated more memory..
I was wondering:
A friend of mine said something like this "Android doesnt need more than 256mb of ram to run smoothly...but due to poor coding app developers dont seem to align or match their apps with the specifications of the android system"
Example: Dolphin HD crashes a lot when playing or viewing flash content and it seems to eat (when selecting heap size 64m) all of those 64mb that can be alocated to a process(app)...
What do you think guys?
yes, Dolphin HD really crashes more than the stock browser on my machine, with heap size set to default 32M
Dolphin HD crashes when I read some forums with very long passages, but the stock browser can display without problem.
Dolphin also occupies a lot of space for caching.

[GAME] Cut The Rope

Someone managed to play this game with MIUI ROM eybee version?
no but pcphobic managed to play it without any lag on cronos ginger 1.4.0 .. hes event posted a video on it running ..
OR you could try this .. eybee1970 posted this in his version of miui, do u have the latest version ? if not get it and try this .. ____>>>>>>
Tipps for Gaming + Navi:
I experienced over last couple of days that setting VM Heap to higher value makes the clue for large apps! So I was able to play GunBros (with standard OC) by setting VM Heap to 48 mb (and running better with balanced3 script from zeppelinrox and not with gaming script - funny ) and my Aura-navigation runs fluently with no unexpected closes also with 48 mb....you can change the heap in build.prop or download the app 'VM Heap Tool' from market. Of course your free RAM gets smaller the higher you set VM Heap - but with 48 mb I still have 50-60 mb RAM free, so good enough for multitasking
rrohanjs said:
OR you could try this .. eybee1970 posted this in his version of miui, do u have the latest version ? if not get it and try this .. ____>>>>>>
Tipps for Gaming + Navi:
I experienced over last couple of days that setting VM Heap to higher value makes the clue for large apps! So I was able to play GunBros (with standard OC) by setting VM Heap to 48 mb (and running better with balanced3 script from zeppelinrox and not with gaming script - funny ) and my Aura-navigation runs fluently with no unexpected closes also with 48 mb....you can change the heap in build.prop or download the app 'VM Heap Tool' from market. Of course your free RAM gets smaller the higher you set VM Heap - but with 48 mb I still have 50-60 mb RAM free, so good enough for multitasking
Click to expand...
Click to collapse
Yes, I have the latest version.
I changed VM Heap to 32mb (like Cronos Ginger ROM) and now I can play Cut The Rope!
Thx!
See this

Fruit Ninja and other THD games having FC problems

Hey all,
Upon no search results, this thread was created. I'm on team tiamat 1.1 and I cannot use any of my THD games like galaxy on fire and fruit ninja. I am wondering if the kernal broke this, but I do not know.
If this thread is in the wrong place, than please move it.
I did a log at and copied everything relating to fruit ninja fc here:
07-23 11:48:01.080 E/InputDispatcher( 152): channel '4108aa58 com.halfbrick.fruitninjathd/com.halfbrick.fruitninja.FruitNinjaActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
07-23 11:48:01.080 E/InputDispatcher( 152): channel '4108aa58 com.halfbrick.fruitninjathd/com.halfbrick.fruitninja.FruitNinjaActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
07-23 11:48:01.080 I/ActivityManager( 152): Process com.halfbrick.fruitninjathd (pid 28934) has died.
07-23 11:48:01.080 I/WindowManager( 152): WIN DEATH: Window{41b60f30 SurfaceView paused=false}
07-23 11:48:01.080 I/WindowManager( 152): WIN DEATH: Window{4108aa58 com.halfbrick.fruitninjathd/com.halfbrick.fruitninja.FruitNinjaActivity paused=false}
07-23 11:48:01.090 I/WindowManager( 152): WINDOW DIED Window{4108aa58 com.halfbrick.fruitninjathd/com.halfbrick.fruitninja.FruitNinjaActivity paused=false}
Thanx all!
-craby1925
Sent from my Xoom using Tapatalk

CM 10.2: How to increase user profile storage space

I set up multiple user profiles in CM 10.2 and each is only allocated just over 1GB of space. How can I increase the storage allocated to each profile? I still have plenty of space left. Thanks.

Categories

Resources